> Greylisting is a doubled edged sword, although beneficial in defering > illegitimate messages it also breaks misconfigured mail servers and the > users scream bloody murder when they dont get email at the speed of IM. > Sad to say this is my case here. We did however have it turned on > (SQLgrey) for a month before it got voted off because of the latency it > incurred.
I have seen very few servers break based on this, but agree that it does happen occasionally. I set my "ok" threshold to just a single email though - my thoughts were that if the mailserver does actually retry at all then it looked real enough to keep it. This way there is just a small one time penalty for each mail server and stuff comes through with just a small delay generally Also you can add some rulesets so that only certain domains (which look like they might be dialup IPs) get greylisted and that way it's mainly only spammers who get hit anyway. I see very little stock spam slip through greylisting right now - that which does comes in via my backup MX which doesn't greylist... I also grepped the log files and for the dialup domains which are just huge spam nests I block them with a notice that they should use their ISP's mailserver... Not quite as harsh as using an DUL dsbl, but hits the bit offenders Ed W ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
