Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - header not compliant with rfc2822?
  FAQ FAQ  Forum Search   Register Register  Login Login

header not compliant with rfc2822?

 Post Reply Post Reply
Author
guest View Drop Down
Guest Group
Guest Group
Post Options Post Options   Thanks (0) Thanks(0)   Quote guest Quote  Post ReplyReply Direct Link To This Post Topic: header not compliant with rfc2822?
    Posted: 27 June 2006 at 5:16am

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)

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

 

Back to Top
lyndonje View Drop Down
Senior Member
Senior Member
Avatar

Joined: 31 January 2006
Location: United Kingdom
Status: Offline
Points: 192
Post Options Post Options   Thanks (0) Thanks(0)   Quote lyndonje Quote  Post ReplyReply Direct Link To This Post Posted: 27 June 2006 at 5:39am

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.

Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4106
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 27 June 2006 at 1:14pm
Bug confirmed.
Build 3.01.1.579 is now available in the registered user area with a fix for this issue.
Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
lyndonje View Drop Down
Senior Member
Senior Member
Avatar

Joined: 31 January 2006
Location: United Kingdom
Status: Offline
Points: 192
Post Options Post Options   Thanks (0) Thanks(0)   Quote lyndonje Quote  Post ReplyReply Direct Link To This Post Posted: 28 June 2006 at 3:54am
Hi Roberto?

Do you mean 3.0.2.579??
Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4106
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 28 June 2006 at 8:03am
yes... sorry. 3.0.2.579.
Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.324 seconds.