It's my understanding (which may be faulty) that spamdyke always creates
a 0 byte file the first time it gets mail from the domain. When it sees
another email from that domain (after the prerequisite graylist-min-secs
delay) then it puts the sending server into the file and allows the mail
to go through as long as mail comes from that exact server. This is why
you sometimes see multiple servers listed in the graylist file. Spamdyke
does clean up these files periodically (as set by graylist-max-secs)
My guess is that this file was protected, preventing spamdyke from doing
it's job. This could happen if someone changed the owner of the file or
it's permissions.
Gary
On 11/19/2013 05:29 AM, Faris Raouf wrote:
Can someone remind me please: under what circumstances would a
spamdyke-created graylist file be 0 bytes?
I used to know this but it has totally escaped my memory.
This came to light when we saw a sender who appeared to be permanently
graylisted when sending to a specific recipient (but not to another
recipient, where the sender was graylisted for the appropriate amount
of time then let through as expected).
On investigation, I found a 0 byte graylist file for the problem
sender/recipient pair dating back to October.
Deleting it resulted in the email being delivered normally to the
recipient shortly after.
The sender, incidentally, was a human, sending from a normal smtp
server with rDNS and IP visible in the logs.
Thanks,
Faris.
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
