BLOG

Blocking mail to spamcop.net

Josh reports mail from MobileMe to spamcop.net addresses is being filtered somewhere and isn’t being delivered or actively bounced. He asserts that Apple is blocking all mail to Spamcop addresses

because they were having problems getting blacklisted on SpamCop and implemented this as a way of reducing their number of SpamCop spamtrap hits.

That makes no sense. Spamcop spamtraps are rarely hosted on spamcop.net. I won’t say never because there may be some, but I know that some spamtraps are on different domains and different SMTP servers. Senders who try to avoid Spamcop problems by filtering all mail to Spamcop are doomed to failure.

The problem is being discussed both on the Apple forums and the Spamcop forums. There is some confusion about what is going on. Some posters seem to be having problems mailing addresses at spamcop.net addresses, other posters seem to be having problems forwarding spam to the spamcop reporting address.

One poster reported that Apple support is claiming that Spamcop is blocking mail from MobileMe. In response ae Spamcop admins posted:

SpamCop does not block ANY email at all that is sent to spam.spamcop.net addresses. We do not use our own blocking list. We might bounce emails to certain addresses, but we do not block anything that comes our way.

The same applies for the SpamCop Email Service. However, they do use greylisting, which delays acceptance from some servers until the server tries again. Continuing to try to deliver email is standard behavior for legitimate mail servers, but not for spammer servers, which only try once and give up.

I suppose it is possible that Apple is seeing the greylisting delay when they try to send mail to spamcop.net, cqmail.net, or cesmail.net addresses and thinks it is a rejection.

If the problem really is forwarding spam to the Spamcop reporting address, it could be Apple filtering outgoing mail to prevent spam from leaking out their servers. If the problem really is sending mail to Spamcop.net addresses it could be a bad interaction between MobileMe and Spamcop’s greylisting scheme. Without seeing the actual transactions between the two servers it is difficult to determine what is happening.

In any case, this demonstrates some of the challenges involved in troubleshooting mail problems. People are poking the system from the outside, but there seems to be some one along the line silently discarding email, leaving senders (and receivers!) in the dark about where the email went.

Comment:

Your email address will not be published. Required fields are marked *

  • HE.net DNS problems

    Hurricane Electric had a significant outage of their authoritative DNS servers this morning, causing them to return valid responses with no results for all(?) queries. This will have caused delivery problems for any mail going to domains using HE.net DNS - which will include some of their colocation customers, as well as users of their free services - but also will have caused reverse DNS to fail for most servers hosted by Hurricane Electric worldwide, so if any of your mail is being sent from HE hosted machines you may have seen problems. (We're HE customers so we noticed. Still happy with them as a vendor.)No Comments


  • 65.0.0.0/8 DNS issues

    If you're sending email from any address beginning with a 65 - in 65.0.0.0/8 - it's possible you'll see some delivery problems. Something appears to be broken with dnssec signatures for the reverse DNS zone, leading queries for reverse DNS to fail for anyone using a dnssec aware DNS resolver (which is almost everyone).1 Comment


  • Our green bar certificate is going away

    Later today we'll be switching from an Extended Validation ("green bar") SSL certificate to a Domain Validation certificate. This isn't exactly a planned change but I'm waiting for responses from Comodo before I go into it too much. I'll share some more details next week.3 Comments


Archives