On Tue, Apr 17, 2012 at 12:12:53PM +0200, Reindl Harald wrote: > > > Am 17.04.2012 12:09, schrieb Robert Schetterer: > > Am 17.04.2012 11:50, schrieb Reindl Harald: > >> > >> Am 17.04.2012 11:48, schrieb Claudius: > >>> Hi, > >>> > >>> as nobody seems to have a working solution I built a little Perl script > >>> that adds the IP of the server receiving outgoing mail to > >>> postgrey_clients.db > >>> > >>> It's still a little unfinished but working fine on my server. There's > >>> room for improvement though (IPv6 missing, rsyslog spawning and lastline > >>> fetching is non-optimal). Maybe I will improve this with piping and a > >>> fifo. > >> > >> are you aware that you are whitelisting this way > >> servers which sent spam to a user with autorply? > >> > > > > what about using > > some tecs from here > > http://mailfud.org/postpals/ > > this all will not work in most cases > > how do you act with us as example? > you are sending a message to me to MX "barracuda.thelounge.net" > well, you whitelist "barracuda.thelounge.net" > but you will never receive any message from our spamfirewall > > this is a typical business case
Stop spreading stupid FUD. It works in _majority_ of cases. "For a certain large organization, 28% of total traffic matched a known entry and only 0.1% of those were spam. Most of that spam originated from large relays that should not be rejected directly at MTA anyway." And yes this was from my government organization with several thousands of users across many domains. If you don't understand what benefits such whitelisting achieves, then just be silent and don't use it.
