I have more information, that brings it all more in focus. F'ing CLIENTS!!
They set up a damn nobody address, then redirected it to a non-existing info@ address.
Aha! That would explain it.
There's also another player here, as you can see there's also a "[EMAIL PROTECTED]" address which appears to be the original recipient, way at the very beginning of the entire message trace (all the way at the bottom). Now I'm really unsure of the full incident path, but feel like we're getting closer. With the new information provided above, anyone wanna take another crack at it while I do the same?
Sure.
The original E-mail was a spam, and apparently sent to [EMAIL PROTECTED], an address that doesn't exist. However, the client had a "nobody" alias set up, so IMail accepted the E-mail and prepared to deliver it to the info@ account (the one the nobody alias points to). It was then scanned for spam, and then passed off to IMail for delivery. However, since the info@ account doesn't exist, IMail then bounced it (since it assumed that the nobody alias pointed to a valid account, and didn't check it before originally accepting the E-mail). The bounce went to the E-mail address that the spammer chose, which turned out to be someone who complained to Spamcop.
By removing the nobody alias, or having it point to a good E-mail address, it should ensure that there are no more problems. :)
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
