Viktor, I'll report your answer internally and so we'll decide next step.
Timo, also your suggestion is right; the problem is that we must teach to our
Customers the guide line to use, and it's not an easy task. But we can do
something with it.
I'll back on this thread as soon I have news
Than
On Mon, Apr 15, 2013 at 01:20:58PM +0200, Giorgio Luchi wrote:
> How can we implement round-robin by sender ip/authenticated user
> and to preserve the memory constraint too?
>
> - "sender" is the sender's ip address or the authenticated user
>name (i.e. "80.93.143.50" or "giorgio.luchi")
>
Coming back to original example of a one-million message queue:
Postfix is designed to survive extreme overload, but all mail will
be delayed. This is no different than the road to the airport:
when it becomes full, all vehicles will be delayed. Both the Postfix
scheduler and the road to the airpo
Hi,
I'm sorry for the delay, but I'm very busy in some projects.
I continue the discussion with my opinion and some details.
No virtual machines and no multi instance solution: we have more than 10.000
customers, so these solutions are not applicable. We don't want to classify
them (in order to
Simone Caruso:
> > I just simulated the performance hit of 256 incoming queues by setting
> >
> > hash_queue_names = incoming
> > hash_queue_depth = 2
> >
> > and running smtp-source, sending mail to an alias for /dev/null.
> >
> > Postfix queue performance for small messages already droppe
> I just simulated the performance hit of 256 incoming queues by setting
>
> hash_queue_names = incoming
> hash_queue_depth = 2
>
> and running smtp-source, sending mail to an alias for /dev/null.
>
> Postfix queue performance for small messages already dropped by
> 30%, with the write cach
Simone Caruso:
> On 06/04/2013 15:01, Wietse Venema wrote
> > There must be other solutions that can work with a fixed memory
> > budget and that can push excessive mail to a "low-priority" queue
> > that is processed when it does not interfere with other delivery.
> >
> > Any solution that require
On 06/04/2013 15:01, Wietse Venema wrote
> There must be other solutions that can work with a fixed memory
> budget and that can push excessive mail to a "low-priority" queue
> that is processed when it does not interfere with other delivery.
>
> Any solution that requires knowledge of THE COMPLETE
On 4/8/2013 12:31 PM, Wietse Venema wrote:
> Giorgio Luchi:
>> I agree with you and with the sentence "Postfix is designed to
>> work on a mail queue of any size. This is possible because Postfix
>> works with a fixed memory budget.", and we don't want to break the
>> architecture.
...
> How does P
Giorgio Luchi:
> I agree with you and with the sentence "Postfix is designed to
> work on a mail queue of any size. This is possible because Postfix
> works with a fixed memory budget.", and we don't want to break the
> architecture.
Good. The use of unbounded memory came up recently in a differen
"right procedure".
Regards
Giorgio Luchi
-Messaggio originale-
Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Per conto di Wietse Venema
Inviato: sabato 6 aprile 2013 15:01
A: Postfix users
Oggetto: Re: R: Scheduling policies for outgoing smtp se
Giorgio Luchi:
> Thanks for your reply.
>
> We are an Italian Telco/ISP company, so we offer outgoing SMTP
> service to our customers.
> For this service, we have always thought that the best way to pick
> up messages from the queue, it is to do round-robin based on IP
> (or authenticated user if
Thanks for your reply.
We are an Italian Telco/ISP company, so we offer outgoing SMTP service to our
customers.
For this service, we have always thought that the best way to pick up messages
from the queue, it is to do round-robin based on IP (or authenticated user if
used) of the sender, to ob
13 matches
Mail list logo
