Milter-greylist

Below is the log which I happened to be watching with a tail -f.   Is this 
an anti-greylisting strategy? It continued for the full 5 minutes that I 
have greylisting set for and then it was gobbled by Spam Assassin so I 
don't suppose it really matters.  I wonder if it would continue for hours 
if I had greylisting set up like that.

Hmm, I just noticed that it started 3 minutes after the first attempt and 
then it was continuous for the full 5 minutes.

One thing I find slightly disconcerting is that the number in square 
bracket was the same for the whole 5 minutes, viz [13989].  I assume this 
is the sendmail process id and I should have thought it would be different 
for each attempt?



Jun  7 23:03:17 malander milter-greylist: l57M3GxK013975: addr 
mta10.adelphia.net[68.168.78.202] from <conactme@...> to 
<alan@...> delayed for 00:05:00 (ACL 128)
Jun  7 23:03:17 malander sm-mta[13975]: l57M3GxK013975: Milter: 
to=<alan@...>, reject=451 4.7.1 Greylisting in action, please come 
back later
Jun  7 23:03:17 malander sm-mta[13975]: l57M3GxK013975: 
from=<conactme@...>, size=1597, class=0, nrcpts=0, proto=ESMTP, 
daemon=MTA, relay=mta10.adelphia.net [68.168.78.202]
Jun  7 23:06:43 malander milter-greylist: l57M6gvn013989: addr 
mta7.adelphia.net[68.168.78.193] from <conactme@...> to 
<alan@...> delayed for 00:05:00 (ACL 128)
Jun  7 23:06:43 malander sm-mta[13989]: l57M6gvn013989: Milter: 
to=<alan@...>, reject=451 4.7.1 Greylisting in action, please come 
back later
Jun  7 23:06:43 malander sm-mta[13989]: l57M6gvn013989: 
from=<conactme@...>, size=1597, class=0, nrcpts=0, proto=ESMTP, 
daemon=MTA, relay=mta7.adelphia.net [68.168.78.193]
Jun  7 23:06:43 malander milter-greylist: l57M6gvp013989: addr 
mta7.adelphia.net[68.168.78.193] from <conactme@...> to 
<alan@...> delayed for 00:05:00 (ACL 128)
Jun  7 23:06:43 malander sm-mta[13989]: l57M6gvp013989: Milter: 
to=<alan@...>, reject=451 4.7.1 Greylisting in action, please come 
back later
Jun  7 23:06:44 malander sm-mta[13989]: l57M6gvp013989: 
from=<conactme@...>, size=1597, class=0, nrcpts=0, proto=ESMTP, 
daemon=MTA, relay=mta7.adelphia.net [68.168.78.193]
Jun  7 23:06:44 malander milter-greylist: l57M6gvr013989: addr 
mta7.adelphia.net[68.168.78.193] from <conactme@...> to 
<alan@...> delayed for 00:04:59 (ACL 128)
Jun  7 23:06:44 malander sm-mta[13989]: l57M6gvr013989: Milter: 
to=<alan@...>, reject=451 4.7.1 Greylisting in action, please come 
back later
Jun  7 23:06:44 malander sm-mta[13989]: l57M6gvr013989: 
from=<conactme@...>, size=1597, class=0, nrcpts=0, proto=ESMTP, 
daemon=MTA, relay=mta7.adelphia.net [68.168.78.193]
Jun  7 23:06:45 malander milter-greylist: l57M6gvt013989: addr 
mta7.adelphia.net[68.168.78.193] from <conactme@...> to 
<alan@...> delayed for 00:04:58 (ACL 128)
Jun  7 23:06:45 malander sm-mta[13989]: l57M6gvt013989: Milter: 
to=<alan@...>, reject=451 4.7.1 Greylisting in action, please come 
back later



-- 
Alan


( Please do not email me AS WELL as replying to the list.  Please
   address personal email to alan+1@ as lists@ is not read. A
   password autoresponder may be invoked if this email is very old. )

> Below is the log which I happened to be watching with a tail  -f.   Is
this 
> an anti-greylisting strategy? It continued for the full 5  minutes that I 
> have greylisting set for and then it was gobbled by Spam  Assassin so I 
> don't suppose it really matters.  I wonder if it would  continue for hours

> if I had greylisting set up like that.

  That looks like your typical maliciously clueless cable company.  They've
decided that a Temp Failure means they should hammer your server into the
ground until it becomes a Permanent Failure or you accept their spam.