Hello

Yes it is a strange business model, but the postfix must run on are vessels.
So they sail over the world and because of the time difference we can't help 
them ride away.

Therefore we use a person onboard the vessel to look at the first problems when 
mail issen't send from the vessel.

They depend on mail for food orders and crew changes sow a delay of 8 hours 
until IT is open isent an option.
That's the strange business model :)

Now we have dell servers running intel E5 at 2.5 ghz at core.

And we use the dell perc controllers. They don't give I/O problems on the rest 
of the windows and linux servers.


We just see the problem when many mails are been transferred on the interface.

Met vriendelijke groeten                         
Kind regards                                                  
De Petter Mattheas                                   
Technical support engineer - projects team     
IT-Department Jan De Nul Dredging N.V.
T +32 (0)53 73 95 53                                          
F +32 (0)53 21 00 31                                          
www.jandenul.com                                            

-----Original Message-----
From: patpro <pat...@patpro.net> 
Sent: 06 March 2019 12:49
To: De Petter Mattheas <mattheas.depet...@jandenul.com>
Cc: Postfix users <postfix-users@postfix.org>; owner-postfix-us...@postfix.org
Subject: Re: stress tested postfix

> About 31000 are in are postfix que and the rest is gone, on are 
> exchange we=  see the confirmation of postfix that he has received the 
> mail is not in th= e postfix que.
> 
> We see a very high I/O on the disk but still writing...

../..

> Witch parameter do I have to change to start throttling sow my mails 
> aren't=  lost?
> 
> 45000 mails a hour is a real situation where we use the postfix in 
> case of = problems with machines and the alerts they send.

My setup is quite different from yours, but I can handle more emails in less 
time. Latest peak: +61000 email messages received in 6 minutes. 
It's a unique VM running postfix-multi with 3 postfix instances. Those 
+61K messages where received by one of these postfix instances, most
were coming from one of the other local instances (so read queue and write 
queue on the same virtual disk).
The VM has 10 GB RAM, but is also running a huge Amavisd-new+clamav setup, I 
could easily downsize to 6 GB RAM without this antispam.
The VM has 4 vCPU running @ 3GHz.

My guess is: you need proper storage IO.


> Second. A good web based gui for postfix, the people that are to use 
> the po= stfix relay aren't IT people and they need to see how many 
> mails that are s= till in que and flush them easily.

I don't know any good GUI for postfix.
This is a strange business model to pay people doing manually what postfix will 
do automatically.
You could just add a queue monitoring (munin, or whatever) that displays a 
graph of queues, and escalate to IT if and only if a real problem occurs (queue 
that won't decrease after 4-6 hours).

Patrick
************************************************************
Any reaction to this e-mail or any other mail, including any
files transmitted therewith to sender's e-mail address(es)
shall be dealt with not as private, but as business
communication(s) and shall be registered as such.
************************************************************

Reply via email to