-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/24/10 09:30 , Chris Withers wrote: > Tres Seaver wrote: >> The misconfiguration of the mail host in transactional mode *does* cause >> the server to go into a "lockdown" mode (because errors are not supposed >> to be raised in 'tpc_finish'). There is *no* database corruption, but >> the transaction manager can't know that, and so it deliberately refuses >> to commit more transactions until the admin un-futzes the problem (in >> this case, by fixing the mailhost configuration) and restarts the server. > > Yeah, what he said...
It's not as easy as that, though. Mailhost misconfiguration is just one reason why errors may be raised during the actual sending. The receiver address may be wrong, which is where I tend to see it. This is not a condition I could reasonably test for in my code before attempting to send though the MailHost. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwjDWUACgkQRAx5nvEhZLKf9ACgjfp7Nxf5B+2BwT6Egp6mhuVV yGIAoKhuD8sEGT+mn6NcbTvqlWxduYsi =LIL8 -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
