Hello Rob, > Henri, that does sound like it would work.
Sounds like it but there seems to be a glitch somewhere cause I wasn't receiving *any* mail anymore... Bummer, and that on a day like Valentine's day ;) I need to take a closer look at my script cause outgoing mail goes through that script of mine too... Hadn't thought of that. One of the problems is that CustMapsList checking and my script take a while to complete. Quite a while even which in fact makes the problem worse. At times I have up to 25 servers connected to XMail trying to deliver mail to users who don't even exist! I want to get rid of those connection as quickly as possible to free smtp threads so they can receive valid mails... I was thinking, is setting SMTP-RDNSCheck to "1" in server.tab going to be helpfull? > The only thing to watch with your method, is that you block > legitimate users that happen to key in the wrong address. True. I was thinking of constantly tweaking the list of ip addresses in spammers.tab to a maximum of 100 or so. > I've had great success with greylisting (glst from Davide). > I did have to tweak it a bit to deal with the likes of > hotmail/yahoo/etc because of their many sending MTAs. I'll have a look but it seems I need GDBM and stuff for it... > Rob :-) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Henri van Riel > Sent: Tuesday, February 14, 2006 9:23 AM > To: Jeff Buehler > Cc: xmail@xmailserver.org > Subject: [xmail] Re: Spammers - How to block them. > Hi Jeff, >> You can run ASSP on a different server than XMail. Also, you can use >> it simply to verify that the address being sent to is a valid one - it >> does not need to perform Bayesian -filter based SPAM blocking unless >> you want it to (you could open up the ruleset, or you can have it >> simply tag the email that goes through with something if it thinks >> it's SPAM). If what you need is to be able to close sessions to >> invalid addresses quickly, that is the only way I know how to do it. > I'll certainly look into it but I don't like the idea of having to run > something in front of XMail... Also, I'd need to install Perl on my > mailserver which is *strictly* a mailserver. >> What you suggest might work, but spammers domains and addresses change >> very rapidly, so I'm not certain you would actually cut down the >> volume much, and you would end up having to process all of that email. >> ASSP will simply terminate the session more or less immediately if it >> doesn't like the email, the sender, or the address, or any combination >> of those things. > I don't have to process that much email though. First of all, my new > CustMapsList filters out a lot of spam. If the sender seems ok, XMail first > checks if the recipient is known. If not, it redirects it to my catch-all > account. While it is doing that, the filters.pre-data.tab filter kicks in > *before* the data command, only the headers have arrived so far. Next, my > script will get the ip address from those headers and exits with code 3 > which makes XMail to terminate the connection. Mail with a valid recipient > will still go through the filter but that's not a problem. > Sounds to me that it could work! ;) > -- > Henri. > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] -- Best regards, Henri mailto:[EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
