Propor calm down. I'm using greylisting since ages and have no problem with gmail and such. Google uses mailnly 2, maybe 3 IPs. Mails may sometime arrive a bit later, it's true but it's not a serious issue...
Andrea Brancatelli Inviato da iPad Il giorno 30/dic/2010, alle ore 18:54, "Tomas Kuliavas" <[email protected]> ha scritto: > 2010.12.30 19:29 Gordan Bobic rašė: >> Tomas Kuliavas wrote: >> >>>>> Can I collect opinions here about favorite/least favorite spam >>>>> filtering packages, for use in a dbmail environment? >>>>> >>>>> What have you had luck with? What works best? What's your opinion? >>>>> Which should a happy dbmail (postfix) user, now getting too much >>>>> spam, use for filtration? >>>>> >>>>> TIA, Lou Picciano >>>>> >>>>> I'm using sqlgrey (postgrey implementation with database (mysql)) and >>>>> spamassassin. So far so good. sqlgrey is the best tool (to my >>>>> knowledge) >>>>> for front-line protection against spam before spamassassin takes over >>>>> the job. I'm welcome for other suggestions. >>>> So, you don't mind not receiving mail from multi-homed hosts (*cough* >>>> gmail *cough*)? Greylistting's very concept is broken by design. >>> >>> So using myriad of outgoing email servers is not something unusual. >> >> You are missing the point. Consider this scenario. A server has multiple >> NICs on different networks, all routing to the internet. The default >> route gets rotated around (when it expires, after a few minutes) in >> order to load balance. This sort of a setup is fairly common on big >> installations (helps with resiliency, too). >> >> So, such a server gets a message in it's outbound spool. It tries to >> deliver it to you via one of it's several routes/NICs. You see the >> connection, greylist it and temporarily reject. Server goes away for a >> bit. By the time it retries, the route has expired, and you get an >> incoming connection from the same server but from a different source IP. >> Your greylist hasn't seen that IP, so you temporarily reject again. This >> can go on forever. Some of your mail might get lucky and get through. >> Most will probably get massively delayed, and some will likely keep >> bouncing in the outgoing spool until it expires and bounces back, >> several days later. > > So network design with routes that last less than couple of hours is > perfectly ok? Trying to feed same email from different locations is > exactly what spammer would do. > >>> Anyone who does not like some tool can call it broken by design. >> >> You are mixing up cause and effect. I dislike tools if they are broken. >> I don't call them broken because I dislike them. > > If you have information that tool has problems with some types of > networking setups, you should say that it has problems with such setups. > Tool works fine with other servers. Design is not broken. Calling > something broken by design does not show what is broken in design. It only > shows that you dislike the tool. > > -- > Tomas > > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
