New E-mail/Address creation causes disruption to Postfix

[Nuxwin]

(08-12-2010 06:57 PM)kilburn Wrote:  

Quote:normally - if a mail is not sent successfully (always a good answer (like "200 OK") after every sent part), then it should be send again....
If it's not spam then the same mail should come again...

That's right. Further, if the mail has already been accepted, postfix makes sure to not lose it afterwards. Hence, the rewrite error can be safely ignored (postfix will resume mail processing after restart).

Quote:Joxi, I've not tested but maybe we should simply do a reload postfix (SIGHUP) when a new mail account is added and not do a restart (stop - start so SIGTERM) ? have you the time to test the behavior ?

What's more, we don't even need to send a sighup when managing mail accounts. On the one hand, since we are only changing the postfix lookup tables but not any configuration values, there's no need to reload the configurations. On the other hand, postfix automatically detects changes in lookup tables and restarts the corresponding processes automatically. Hence, there's no need to reload nor restart nor anything!

Source (from postfix lookup tables docs):

Quote:If you change a local file based database such as DBM or Berkeley DB, there is no need to execute "postfix reload". Postfix uses file locking to avoid read/write access conflicts, and whenever a Postfix daemon process notices that a file has changed it will terminate before handling the next client request, so that a new process can initialize with the new database.

Cheers!

Ok Marc. Thanks. Are you nervous today ? I'll make some tests and remove the stop - start calls in the ispcp-serv-mngr engine script. Note, After thinking, I know that you have right. When we use postfixadmin, it's the same behavior. Don't need to reload postfix.