This is true, however a LARGE amount of spam is sent from IP's with no RDNS. By not blocking those e-mails, you're certainly forcing your mail server to deal with a MUCH larger amount of mail, most of which would be spam. I guess if you don't have a resource issue, and don't mind wasting resources on handling spam, that may or may not be rejected by SpamAssassin down the road, then that's fine.
I agree that, if the customer wants the spam, I'm more than happy to let them have it. However, I won't do it at the detriment of other users. If you've never had a "Spam Attack", where your server is constantly bombarded by spammers, then when you do, you'll wish you had SpamDyke. :-) When your server (Or the OP's server) is being hammered by a spammer, and comes here to complain about how his server is overloaded and legit e-mail is timing out because all of his SMTP ports are being bogarted, the first suggestion is going to be "Are you running SpamDyke". And, yes... When a client is not getting e-mail because the sender's mail server (Usually an internal Exchange server) does not have an RDNS, I tell them that's why. I even have a form e-mail I send them to send the blocked person. I've actually picked up several consulting gigs (Fixing their RDNS issue) and spam filtering customers from this... Lack of RDNS is becoming a much more common antispam check. So, if you're blocking it, others are also likely blocking it, and, in the end, the offending server's admin is going to have to resolve the issue... Mike -----Original Message----- From: Peter Peltonen [mailto:[email protected]] Sent: Tuesday, May 03, 2011 10:38 AM To: [email protected] Subject: Re: [qmailtoaster] Re: SPAM Designation Option Hi, On Tue, May 3, 2011 at 7:31 PM, Eric Shubert <[email protected]> wrote: > that. Spamdyke false positives are practically nonexistent though, so you > might want to just leave spamdyke active and not tell him about it. Then > again, if he insists on receiving spam, I'd charge him extra for the load > it'll cause on your server as well as the trouble of configuring spamdyke. > ;) Even if Spamdyke is correct, it does not mean that the end behaviour is what the customer expects. I have ran into issues where customers haven't received email they were expecting because of Spamdyke rejecting a message because of missing reserve dns. And it does not help telling the customer that the sending server is not properly configured, if they can receive the same email with their Gmail or some other account... I have been playing around with an idea that I should create a page for each customer where they could check the sending addresses for denied messages. So if there is a "real" message denied I could then offer an option to white list that mail server or sending address, so that the customer could try contacting the sender again. Best, Peter ---------------------------------------------------------------------------- ----- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! ---------------------------------------------------------------------------- ----- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
