mark david mcCreary wrote:
I'm running mailing lists with Smartlist, and running into valid
emails addresses that get caught by the FROM_DAEMON regexp.
For example, markdavid(_at_)hushmail(_dot_)com, or
mark91010-mail(_at_)yahoo(_dot_)com(_dot_)
Looks like FROM_DAEMON expands to
(^(((Resent-)?(From|Sender)|X-Envelope-From):|>?From
)([^>]*[^((_dot_)%(_at_)a-z0-9])?(Post(ma(st(er)?|n)|office)|(send)?Mail(er)?|daemon|mmdf|n?uucp|ops|r(esponse|oot)|(bbs\.)?smtp(error)?|s(erv(ices?|er)|ystem)|A(dmin(istrator)?|MMGR))(([^).!:a-z0-9][-_a-z0-9]*)?[%@>
][^<)]*(\(.*\).*)?)?$([^>]|$))|^(((Resent-)?(From|Sender)|X-Envelope-From):|>?From
)([^>]*[^((_dot_)%(_at_)a-z0-9])?(LIST(SERV|proc)|NETSERV|bounce|autoanswer|echo|mirror)(([^).!:a-z0-9][-_a-z0-9]*)?[%@>
][^<)]*(\(.*\).*)?)?$([^>]|$)
so my first thought is to tweak this regular expression, and then
replace FROM_DAEMON with my new version in the Procmail recipe. That
way I won't have to touch the Procmail source code.
If you have any wisdom your want to share on this endeavor, or have
tweaked this yourself, I'm all ears.
In the years I ran Smartlist I never had a failure like that (the other
way around, yes). What makes you think that this regexp is triggered on
those addresses and, if you are going to mess with it, which part of the
regexp is matching those addresses?
When I had to get into the guts of Smartlist's rules I spent a fair
amount of time adding debugging log output to make very certain I was
where I thought I was and why; it paid off more than once.
Rich
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail