Exactly which version of spamdyke are you using? The graylist filter has undergone a lot of changes since version 3.x, so it's possible this issue has already been addressed.
In general, you can test this by checking the timestamp on a graylist file, sending a message and checking if the timestamp was updated? If the timestamp is not updated, spamdyke could be having permission problems (or your disk could be out of inodes). It should log errors if it can't write to a graylist file. The "config-test" feature may also be able to identify the problem. If the timestamp is updated and spamdyke is still graylisting the recipient, this might be a configuration problem or you may have found a bug. I would recommend testing version 4.0.10 to see if it has the same problem (that version also fixes a number of other bugs, so upgrading is not a bad idea). -- Sam Clippinger Marcin Orlowski wrote: > Hi, > > I use spamdyke 3 and got graylisting enabled. My expiration > time of graylisting "token" is set to one week. However, > despite continous mail exchange between two email addresses > I still see graylisting to take place. What I used to believe > was that once user A sent mail to B, then A's server retried > once graylisted the "token" spamdyke created for that pair > is valid for one week. But I also believed that on each new > delivery from A to B this token is touch'ed, so my cron invoked > clean up script would remove all tokens older than one week > while "older than one week" means that there was no mails from > A to B for a week, not "one week since graylisted". > Anyone could please confirm my findings? If I am right, does > spamdyke 4 fixes that issue? > > Regards, > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
