Tim Legant wrote:
> Since the 'to*' rules match against the SMTP envelope receiver, the
> specific example you give above wouldn't work anyhow. However, you
> can accomplish the effect you want today.
Ah, good point.
> First, set the default action, ACTION_INCOMING, to 'drop'. Then add a
> rule similar to the following to the very end of your incoming filter.
> Use your email addresses in your regular expression. This one matches
> two of my base addresses ('tim' and 'thl') and any extensions
> following those bases.
>
> headers '^To:.*(?:\n[ \t]+.*)?(?:tim|thl)(?:-.*?)[EMAIL PROTECTED]'
> confirm
Right, it's possible to write general negating regular expressions, but
it gets progressively more and more difficult the more complicated the
expression is. And, it seems to me, with multiple negation tests that
you want to perform, it gets rapidly beyond control.
It just seemed to me that negation for most of the sourcing patterns
seemed like an obvious feature that wasn't present.
But your suggestion for getting that functionality now is a reasonable
one.
--
Erik Max Francis && [EMAIL PROTECTED] && http://www.alcyone.com/max/
__ San Jose, CA, USA && 37 20 N 121 53 W && &tSftDotIotE
/ \
\__/ A father is a thousand schoolmasters.
-- Louis Nizer
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
