R: Scheduling policies for outgoing smtp server

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

Re: Scheduling policies for outgoing smtp server

Am 2013-04-05 12:36, schrieb Giorgio Luchi: - User A [...] sends 1 different email to 1 million of different domain destinations [...] - User B [...] sends an email to a different more domain destinatio Doesn't this scream for two different postfix instances? - One high priority instance with

Re: R: Scheduling policies for outgoing smtp server

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") >

Re: R: Scheduling policies for outgoing smtp server

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

R: Scheduling policies for outgoing smtp server

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

Re: R: Scheduling policies for outgoing smtp server

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

Re: R: Scheduling policies for outgoing smtp server

> 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

Re: R: Scheduling policies for outgoing smtp server

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

Re: R: Scheduling policies for outgoing smtp server

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

Re: Scheduling policies for outgoing smtp server

Am 08.04.2013 21:08, schrieb Stan Hoeppner: > Isn't this a class of problem that can be fairly easily solved using > virtual machines? Dedicate a VM and Postfix per customer, without > needing to hack up the MTA. If the issue is "queue fairness" then one > virtual machine per customer should ad

Re: R: Scheduling policies for outgoing smtp server

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

Re: R: Scheduling policies for outgoing smtp server

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

R: Scheduling policies for outgoing smtp server

"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

Re: R: Scheduling policies for outgoing smtp server

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

R: Scheduling policies for outgoing smtp server

cision. Best regards Giorgio Luchi -Messaggio originale- Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] Per conto di Wietse Venema Inviato: venerdì 5 aprile 2013 15:02 A: Postfix users Oggetto: Re: Scheduling policies for outgoing smtp server Giorgio Luchi: &

Re: Scheduling policies for outgoing smtp server

Giorgio Luchi: >I've read the article at "http://www.postfix.org/SCHEDULER_README.html >The question is about a specific scenario to understand the behaviour >of the scheduler: - The scheduler makes decisions primarily based on destinations and recipient email addresses; not on sender email addr

Scheduling policies for outgoing smtp server

Hi, I've read the article at "http://www.postfix.org/SCHEDULER_README.html ". The question is about a specific scenario to understand the behaviour of the scheduler: - User A, with ip address IP_A, sends 1 different email to 1 million of different