Milter-greylist

Thomas Cameron wrote:

>I added this to greylist.conf:
>
>from /.*@usaa\.com/
>
>I restarted milter-greylist to be sure.
>
>Then I noticed these in my maillog:
>
>Apr 21 10:13:34 wintermute milter-greylist: j3LFDYUs025713: addr 
>167.24.99.202 from <USAA.CUSTOMER.SERVICE@...> to 
><THOMAS.CAMERON@...> delayed for 00:00:44
>
>Apr 21 10:13:34 wintermute sendmail[25713]: j3LFDYUs025713: Milter: 
>to=<THOMAS.CAMERON@...>, reject=451 4.7.1 Greylisting in action, 
>please come back in 00:00:44
>
>Apr 21 10:13:34 wintermute sendmail[25713]: j3LFDYUs025713: 
>from=<USAA.CUSTOMER.SERVICE@...>, size=43922, class=0, 
>nrcpts=0, bodytype=8BITMIME, proto=ESMTP, daemon=MTA, 
>relay=oak2-int.usaa.com [167.24.99.202]
>
>So is whitelisting case sensitive or am I not understanding how it works?
>  
>

Regular expressions should be case insensitive, unless you're using a
version older than 1.3.6.

Is there any chance you're starting milter-greylist with -T (which
inverts the entire sense of greylist.conf)?

If you're using a version newer than 1.7.2, you probably want to switch
to using ACL syntax.

acl whitelist from /@usaa\.com/

note: I removed the leading .*, because it's superfluous.

 Regexes are inherently substring matches, so a leading and trailing .*
is implied for all entries. While recent changes have modified the
non-regex rules to support exact matches, regexes are still regexes.

If you need an exact match in a regex, add the < and/or > to your regex,
as the line sendmail feeds to the milter will look like:
<milter-greylist@yahoogroups.com>