3.1 (beta 4) Max line length exceeded

Found a serious/minor bug in PopTray? Tell me about it.

Moderators: KY Dave, jojobear99, Rdsok

Locked
User avatar
rsleegers
Enthusiast
Posts: 49
Joined: Fri Apr 02, 2004 4:34 pm
Location: Ontario, Canada
Contact:

3.1 (beta 4) Max line length exceeded

Post by rsleegers » Fri Apr 02, 2004 4:43 pm

I was going to attach a message sample, but thought better of it! The line is 31620 columns wide. :o Looks like the entire HTML mail was sent on a single line in the DATA area.

3.1 (beta 3) did not have this limitation. It could scan the message fine. (I have the same batch of messages sitting in an e-mail account). Beta 4 would not download messages until I unchecked "Retrieve Body while checking". I could the double click the offending message to determine which one was causing it.

A secondary message "connection reset by peer" is caused presumably because the connection is not closed properly after the first error.
Richard
PopTray 3.2 (beta 5) RC1
http://ca.geocities.com/rsleegers/PopTray/

User avatar
Renier
Site Admin
Posts: 1957
Joined: Mon Oct 15, 2001 12:54 pm
Location: Cape Town, South-Africa
Contact:

Post by Renier » Fri Apr 02, 2004 5:58 pm

I already increased the max line lenght to someting like 16kb. Don't know what the RFC says.

User avatar
rsleegers
Enthusiast
Posts: 49
Joined: Fri Apr 02, 2004 4:34 pm
Location: Ontario, Canada
Contact:

Post by rsleegers » Mon Apr 05, 2004 4:06 pm

I don't see any limitations in either http://www.faqs.org/rfcs/rfc822.html or http://www.faqs.org/rfcs/rfc1939.html so I guess it's up to you what to do.

I imagine increasing the limit would eventually hit another message which exceeds it. How about one of these:
  • 1. split the line at the space character previous to the limit
    2. printing an error inside the message, but allowing the downloading of headers to continue
    3. non-modal error message, which allows downloading of headers to continue
    4. counting number of errors and displaying in status bar when finished
Richard
PopTray 3.2 (beta 5) RC1
http://ca.geocities.com/rsleegers/PopTray/

GaryGo
Enthusiast
Posts: 48
Joined: Mon Mar 29, 2004 7:37 pm
Location: Upstate NY, USA

Post by GaryGo » Thu Apr 29, 2004 3:45 am

RFC2822 supercedes RFC822.
RFC2822 specifies a maximum line length of 1000 characters, including the CRLF.

Gary

User avatar
rsleegers
Enthusiast
Posts: 49
Joined: Fri Apr 02, 2004 4:34 pm
Location: Ontario, Canada
Contact:

Post by rsleegers » Thu Apr 29, 2004 9:32 pm

GaryGo wrote:RFC2822 supercedes RFC822.
RFC2822 specifies a maximum line length of 1000 characters, including the CRLF.
Indeed it does. I hadn't scrolled to the end, and RFC822 was higher up in the search return list. The RFC recommends handling larger than 1000 chars, so I would recommend leaving the limit as is, and handling the error non-modally so the downloading of headers continues, and doesn't cause another error (time out) following.
Richard
PopTray 3.2 (beta 5) RC1
http://ca.geocities.com/rsleegers/PopTray/

GaryGo
Enthusiast
Posts: 48
Joined: Mon Mar 29, 2004 7:37 pm
Location: Upstate NY, USA

Post by GaryGo » Sun May 02, 2004 2:40 am

rsleegers wrote:The RFC recommends handling larger than 1000 chars
Oops, I was so intent on pointing out RFC2822 that I forgot to mention that the RFC makes that recommendation. I agree with rsleegers post.

User avatar
NO CARRIER
Fanatic
Posts: 82
Joined: Sat May 10, 2003 1:52 pm
Location: Bulgaria
Contact:

Same situation here. PopTray v3.1b5

Post by NO CARRIER » Wed May 05, 2004 1:52 pm

I received a "failure notice" message with wide body, here is link to the file:
http://f13.zadnik.org/files/failure%20notice.eml
PopTray says "Max Line Length Exceed" and should be restarted to work again. Until restart on every check shows Socker Err #0, if I remember correctly, because I delete the message.

Locked

Who is online

Users browsing this forum: No registered users and 4 guests