3 ms·
I looked briefly at procmail, but it seems to only have a primitive mechanism for identify bounce messages. There does not appear to be a way to extract meta da
by snprbob86 18y ago
I looked briefly at procmail, but it seems to only have a primitive mechanism for identify bounce messages. There does not appear to be a way to extract meta data from them.
"""
If the regular expression contains ‘^FROM_DAEMON’ it will be substituted by ‘(^(Mailing-List : |Precedence :.(junk |bulk |list) |To : Multiple recipients of |(((Resent-)?(From |Sender) |X-Envelope-From) : |>?From )([^>][^(.%@a-z0-9])?(Post(ma?(st(e?r)? |n) |office) |(send)?Mail(er)? |daemon |m(mdf |ajordomo) |n?uucp |LIST(SERV |proc) |NETSERV |o(wner |ps) |r(e(quest |sponse) |oot) |b(ounce |bs\.smtp) |echo |mirror |s(erv(ices? |er) |mtp(error)? |ystem) |A(dmin(istrator)? |MMGR |utoanswer))(([^).! :a-z0-9][-_a-z0-9])?[%@>\t ][^<)](\(.\).)?)?$([^>] |$)))’, which should catch mails coming from most daemons
"""
I still need a way to get meaningful information from the bounce messages.
For example, my system sometimes emails a file on behalf of a user. If I receive a "mailbox does not exist" bounce, all I can do is notify the user that they may have mistyped an email address. However, if I receive a "mailbox full" bounce, I want to try again without the attachment and only with a web download link.