Just wondering if there are any known bugs with milter-greylist 1.4 using the "subnetmatch" and "attr" greylist.conf keywords? I have tried "subnetmatch /24" and "subnetmatch 24" in greylist.conf, and "-L 24" from the command-line, and none of them seem to be working. Even after one machine gets through the waiting period, is autowhitelisted, and can send without being greylisted... another machine in the same class C still get greylisted for the exact same sender and recip. The IP addresses in greylist.db are complete (they don't end in .0) -- not sure if that's as it should be. Also, I have added "attr 192.168.0.0/16" to my greylist.conf, but machines in that class B are all still forced through greylisting anyway. Is there any way other than "verbose" on greylist.conf to get it to log more -- show details while it's parsing greylist.conf, display errors, etc.? Anything more I can do to troubleshoot? Thanks. -- Brent J. Nordquist <b-nordquist@...> N0BJN Other contact information: http://kepler.its.bethel.edu/~bjn/contact.html
Message
1.4 with subnetmatch and addr
2004-11-02 by Brent J. Nordquist
Attachments
- No local attachments were found for this message.