Milter-greylist

Tom Hedges <tom@...> wrote:

> The idea that any SMTP transaction that fails to call EOM (which probably
> means calls abort), cause milter close call to flush all records in either
> the gray-list or the auto-white- list for that relay IP address.

My problem with that is that if sendmail tempfails because it got
overloaded, the message will not be in the greylist. When the message
will get back later, it will have to get greylisted again.

> 2) The second proposal, which I have not shown to Emmanuel yet, is an
> extension on his idea for pruning envelop user names for mailing lists. I
> have found machine-generated user names, often with many more digits than
> letters, occur when certain automated e- mail's are sent by non-mailing
> list daemons. These can clutter the auto-white-list and never will match
> another e-mail.
> 
> My proposal, which is still in the works, is to identify these envelop
> sender user names and completely replace them by generic text, e.g.
> AUTO_GENERATED_USER. This results in a whitelist entry that _may_ match
> and is not something that would let span through. I am still trying to
> refine my heuristic here. I have nearly ever non-spam e-mail sent to me
> for the last 8 years and I need to do data reduction to refine the
> heuristic. As I said before, a long name with lots of digits versus
> letters seems to be the key.

Perhaps we can thing about a more generic scheme. For instance a way to
override a typle before it gets inserted in the greylist or whitelist
database.

acl greylist default from /@mailfarm\.example\.net/  \
        greytuple "%i","AUTO_GENERATED_USER","%r"

And there would be a awtuple clause to override the autowhite tuple

That way it's possible to implement your idea, and many others tricks.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...