my employer uses v3.0.1.561 of your product.   recently a couple of spam made it thru to my inbox.   i attempted to report these spam to spamcop, spamcop would not accept them due to their error "This email contains no date".    

further research seems to indicate that the "received" line that your product  inserts into the email header is not compliant with paragraph 3.6.7 of rfc2822 with regard to the date/time.  (ref. http://www.faqs.org/rfcs/rfc2822.html - http://www.faqs.org/rfcs/rfc2822.html )

specifically this paragraph states The "Received:" field contains a (possibly empty) list of name/value pairs followed by a semicolon and  a date-time specification.".  

however,  the "received" line that you insert into the header has no semicolon e.g.  Received:  from 71.134.215.4 by myserver.mydomain.com (LogSat Software SMTP Server) Mon, 26 Jun 2006 21:30:28 -0700

(note that i have edited the server/domain name in this example for the sake of anonymity, but nothing else is edited in this example)

please advise what must be done to resolve this error so i may forward the resolution to our email adminstratiors - thank you

I've had the same problem reporting to spamcop of late, however havn't looked into why this was an issue.

I thought it may have been the way spammers were formatting the headers to avoid being reported.

This used to work, so assume this problem has crept in with a more recent version of SF? Or spamcop has tightened their belt when accepting RFC complient emails.