I'm still not excited about this idea because I believe it will cause more problems than it will solve. Personally, I use a lot of automated tools that send me reports/etc using my address and this kind of filter would block all of those. Determining whether an rDNS/IP is authorized to send email is tricky (SPF was designed for this purpose). I'm open to debate, however.
In the short term, could you stop this kind of spam by configuring spamdyke to require authentication for all of your local domains? -- Sam Clippinger Joe Canner wrote: > > Dear Spamdyke community, > > A month or two ago there was a thread about spam where the FROM > address is the same as the TO address (both referring to the recipient > of the spam). At the time, this issue was dismissed without much > discussion. This has, within the last month, become a very serious > problem for us. Because the FROM address is local, it bypasses > graylisting, which up until now had been a very effective method of > protection. > > Can anyone suggest a solution to this? Please don’t suggest > SpamAssassin or blacklists, I am not interested in those right now > (too many false positives for one thing, too many unsophisticated > users for another). > > Surely there must be a way in Spamdyke to block mail with a FROM > address that is different from the RDNS address. Or, alternatively, to > block mail where the TO and FROM addresses are the same and the RDNS > address is not local. > > Thank you all for your assistance. > > Best Regards, > > Joe Canner > > Casablanca, MOROCCO > > ------------------------------------------------------------------------ > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
