Comments you submit will be routed for moderation. If you have an account, please log in first.

Opened 5 years ago

Closed 4 years ago

#232 closed bug (fixed)

Unexpected EOF

Reported by: Raziel Owned by:
Priority: normal Milestone: YAM 2.7
Component: MIME handling Version: 2.6p1
Severity: minor Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:


An eMail which keeps the order information of a recently bought product is truncated prematurely cutting off important information.

Error message:

Unexpected EOF while decoding multipart
message in file

The message seems to be truncated.

(08.11.2010 14:07:18)

Thore: Ein schneller Blick auf die Mail hat auf jeden Fall schon gereicht. Die Mail
besteht aus zwei alternativen Teilen (reiner Text und HTML), die durch die
Zeichenkette "------" getrennt sind. Dummerweise wird genau diese Zeichenkette
aber auch im normalen Text verwendet, was dann die Fehlermeldung von YAM

(A quick glance at the mail was in any way sufficient. It consists of two alternative parts (pure text and HTML) which are seperated through the line "------". Unfortunately exactly this line is also used in the normal text which triggers the error message from YAM)

I hope i didn't overdo the translation? ;-)

Attachments (1) (6.6 KB) - added by tboeckel 5 years ago.
The mail that YAM complains about

Download all attachments as: .zip

Change History (5)

comment:1 Changed 5 years ago by tboeckel

  • Component changed from undefined to MIME handling
  • Milestone set to YAM 2.7
  • Priority changed from undecided to normal
  • Status changed from new to accepted

Changed 5 years ago by tboeckel

The mail that YAM complains about

comment:2 follow-up: Changed 5 years ago by tboeckel

Added the file for raziel_nosgoth. Don't you have an account here?

comment:3 in reply to: ↑ 2 Changed 5 years ago by anonymous

Replying to thboeckel:

Added the file for raziel_nosgoth. Don't you have an account here?

Nope, normally YAM just runs perfect :-)

comment:4 Changed 4 years ago by damato

  • Resolution set to fixed
  • Status changed from accepted to closed

(In [5748]) * YAM_RE.c: modified the MIME boundary checks to make sure that the boundary

is placed on a single line with a final '\0' and only white spaces between
the boundary and the final NUL char. This should fix problems with slightly
broken mails where the boundary was not chosen unique enough and where in
the text it might partly show up. Previously YAM was just comparing the
beginning of a line with the defined boundary string. However RFC 2046
defines that the boundary should be on a single line with only white
spaces and the final CRLF. Thus, this fix should close #232.

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Hubert Maier(Reporter)