On 01/19/2018 12:48 PM, Grant Edwards wrote:
Yep, and it looks like the Postfix equivalent is a custom pipe transport. Once you know what phrases to google for, it's a lot easier.
*nod* I figured that you would be able to find something. Hence why I mentioned the terms. ;-)
I could live with queueing/retrying as long as the eventual failures generated messages that are sent back to the sender. Those failure messages would need to be sent via a normal SMTP smarthost/relayhost (with AUTH) and not via the custom mailer.
I would expect that it is possible to fulfill those requirements.
Yes, I've been thinking about that. I think I'll try that first -- if my understanding of the failure mode is correct, it should work.
The simpler solution is usually nicer.
I wrote the server I'm using now, but it uses somebody else's snmpd module, and that's where the SSL breakage is. I've filed a bug, and I've been doing some reading toward attempting a fix, but it looks like it might be a bit hairy: it involves Python's asyncore/asynchat framework (and process pools). What's missing is handling for ssl "want read" and "want write" exceptions.
"snmpd" or "smtpd"?You lost me at Python. (I know it's a personal prejudice. But I think I'm allowed to have it as long as I acknowledge them as such.)
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
