Milter-greylist

Hi Jim


A few years ago I patched milter-greylist to support spamassassin. But because
I had similar requirements like the ones you just posted I finally replaced
milter-greylist with my own milter called mopher.


> from its own country (say, we favor ".ru", ".su" and ".com").
> We thus believe that messages from .de, .tr, .br, .fr, .bg, .pl
> and the other two hundred TLDs are most likely spam - for this
> server at least. So we want them delayed until a MUCH later retry
> (8 hours? 24?) and if by then they are not in a DNS RBL - accept.

Good Idea. It should be very easy to implement this with mopher.


Mopher also supports relay and sender/recipient accounting for automatic
long-term whitelisting. This is especially useful if you apply harsh
greylisting in a business environment.


> Logically, one way would be with conditionals (if source is trusted;
> then racl ... ; ELSE racl continue set spam_score+=1; fi), or with
> negations (racl continue NOT list "good_source" set spam_score+=1).

Mopher has firewall like filter expressions and supports logical operators
(and, or, not). Have a look at dynamic greylisting here:

http://badblog.ch/2012/11/11/filter-email-with-mopher/


The user base is still quite small and there is probably a lot of documentation
missing. But if you want to give it a shot I gladly assist you to get your
installation up and running.


More resources:

  - Configuration examples: http://badblog.ch/2012/11/13/my-mail.acl-explained/

  - Source Code: https://github.com/badzong/mopher


Cheers, Manuel


p.s.

It's off topic - I know