houseofcats Posted February 18, 2004 Posted February 18, 2004 I have a secondary MX that spammers are using to target my domain. However, both my host and my secondary MX host are on residential DSL spaces, and our reverse DNS is not congruent with our forward DNS. (I think this is the root cause, but please read on) MOST of the spam reports I process with SpamCop are finding the original sender, as well as the valid secondary MX, and testing them as possible spammers. When analyzing the secondary MX, SpamCop properly identifies this host as a valid MX for the destination domain, and moves on to the next host. When it looks at the original sender, it does the analysis for the reverse DNS of the secondary MX host IP. It finds that the IP is not a valid MX for this DNS domain. SpamCop identifies this examination as a forgery, and stops processing the analysis for the real spammer or open relay. Can SpamCop be adjusted to exclude a host it finds as a valid MX for the final destination? Here is a sample: http://www.spamcop.net/sc?id=z300794669z80...93da1f642a364fz Thanks! -andy
StevenUnderwood Posted February 18, 2004 Posted February 18, 2004 I don't hve a grasp of what is happening here to comment, but you left that report open for reporting, which means anyone who went to that link could have approved it. I have cancelled it. You will need to resubmit it if you want to report it.
turetzsr Posted February 18, 2004 Posted February 18, 2004 Hi, house, ...My suggestion would be to send an e-mail to deputies <at > admin.spamcop.net (replace the "<at>" with "[at]" and eliminate spaces), forwarding the full internet headers of a spam that causes this problem. They may be able / willing to help you.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.