3 ms·
Do what ezmlm does with bounce messages: use a different envelope sender for each outgoing mail and encode the message ID in that address. If you get a mail to
by aaronsw 18y ago
Do what ezmlm does with bounce messages: use a different envelope sender for each outgoing mail and encode the message ID in that address. If you get a mail to the envelope sender you can typically assume it's a non-delivery report of some kind.
For finer-grained information, you can search the resulting message for HCMSSCs: http://cr.yp.to/proto/hcmssc.txt http://cr.yp.to/proto/hcmssc.txt
Further reading:
http://cr.yp.to/proto/verp.txt http://cr.yp.to/proto/verp.txt
http://support.kavi.com/khelp/kmlm/user_help/html/bounces.html#automated_bounce_handling http://support.kavi.com/khelp/kmlm/user_help/html/bounces.ht...
- snprbob86 18y agoThis is certainly interesting. In the grand problem of making sense of bounce messages, there seems to be three sub-problems: 1) Determining if the message is in fact a bounce. VERP doesn't seem to solve this. 2) Correctly linking a bounce message to the original message. VERP seems to solve that via encoding the message ID into the return path. I could implement VERP with "plus addressing". Thanks! 3) Identifying the error that the bounce message represents. Unfortunately, the presence of HCMSSCs in the hash format does not seem common. Even Gmail's bounce messages do not provide them.