According to Mac OS X Hints, if you're trying to send an email to someone with a spamcop.net email address with your MobileMe account, chances are the message will never arrive, and you won't be notified.

What's worse, apparently if you're sending the message to a distribution list, and only one of those recipients has an address at spamcop.net, nobody will receive the message.

Apparently the problem has been happening for months, since Apple moved everyone from .Mac to MobileMe. A participant in the Apple Discussions thread notes that it's common for service providers to filter their outgoing mail by domain in order to avoid being blacklisted. So far, only spamcop.net appears to be affected.

A workaround for now would be to try to send the message using a different email account. We'll let you know if Apple offers a fix in the meantime.

Update: Friendly reader Jason sent me a detailed explanation about why this might be. In a misguided attempt to control their individual load of spam, some users choose to forward all their MobileMe mail to a spamcop.net address. Spamcop, unfortunately, thinks the "spam" originated at MobileMe, not the actual origin of the spammy badness. So, MobileMe, to combat this, forbids forwarding to domains like Spamcop in order to avoid being blacklisted. There's nothing sinister going on here, just honest network administrators doing what they can with what they've got. Thanks, Jason!

Yesterday, Erica posted in her state of the iPod touch jailbreak that a hacker named "Martyn" had obtained a broken iPod touch, and was planning to dive in and download every bit of code on it in the increasingly complicated effort to put 3rd party applications on the iPod touch. He didn't plan to release the code to the public, but he did plan to upload the code to a secured area of his site in order to let the other touch hackers have a crack at it.

But even before his upload finished, we're told, his ISP showed up, with a takedown notice in hand. Apple had somehow found his site, had contacted his ISP, and let them know that it would be against copyright law for him to upload that code to the Internet. Martyn isn't interested in breaking the law (and it would be illegal to share that code), so he pulled the page off. But what's amazing here is how fast Apple moved on this-- either they've got someone listening in on the development wiki, or they're taking cues from us on how things are going over there (hi, Apple!).

Despite what we've heard before, clearly they are very, very interested in making sure the iPod touch doesn't get hacked. Martyn tells me, as has Erica, that Apple has clearly gone out of their way to keep hackers out of their latest iPod. We're also told that progress continues despite all that, but Apple is apparently bending over backwards to do everything they can to keep the iPod touch closed.