Because SpamCop is a big thorn in spammers' sides, they will often try to cause trouble by sending out spam that appears to be from SpamCop, but which is actually not. Because most of an email can be forged (including who it is "from"), spammers can send email from addresses @spamcop.net in an attempt to discredit us. However, now that you are here, you can look around and learn what you can do to stop these low-lifes from invading your inbox with their junk - or not.

SpamCop has begun requiring that spam containing HTML is submitted with the HTML codes intact (funny codes in the body of the message). This prevents erroneous complaints and allows SpamCop to find sites referenced within the HTML. Just because you don't see pretty pictures and colorful text does not mean the email you are viewing does not use HTML coding. The HTML tags contain the email and web site addresses, which may not be contained in the plain text.

SpamCop will not send reports for any spam it detects is more than 48 hours old, as indicated by the first accepted Received: line. SpamCop uses the date of the topmost useful Received: line. This is usually information direct from your own email server, not the spammer's email system. The date used is actually appended by your own ISP and indicates the amount of time the email has been sitting in your inbox waiting for you to retrieve it.

They do find spam and plenty of it. We did notice that for some customers, the function seemed not to work. But a look at their log showed the problem right away. Assuming your DNS is working right, in almost every case, the firewall or proxy was to blame. What happens is that some of these proxies pose as the sending SMTP mail server to XWall or any other SMTP receiver down the line. That means the spam relays check the address of your proxy or SMTP firewall, not the original sender.