6.0.0-git
2019-03-19

[#3022] text attachments with very long lines get broken
Summary text attachments with very long lines get broken
Queue IMP
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners
Requester adrieder (at) sbox (dot) tugraz (dot) at
Created 2005-11-22 (4865 days ago)
Due
Updated 2005-12-10 (4847 days ago)
Assigned 2005-11-22 (4865 days ago)
Resolved 2005-12-10 (4847 days ago)
Milestone
Patch No

History
2005-12-10 14:40:05 adrieder (at) sbox (dot) tugraz (dot) at Comment #8 Reply to this comment
Thanks. It works......!
2005-12-10 08:11:43 Michael Slusarz Comment #7
State ⇒ Resolved
Reply to this comment
We will encode text parts with 998+ character long lines in 
quoted-printable to avoid issues with truncated lines.  Fixed in HEAD 
and 4.1.0.
2005-12-01 23:23:56 Jan Schneider Comment #6 Reply to this comment
It happens on sending mail, so performance is not a huge issue.
2005-12-01 23:12:11 Chuck Hagenbuch Comment #5 Reply to this comment
I think it's fine to show non-MIME readers ugly characters at this 
point. My question is what kind of performance impact is scanning 
large text files to see if they have long lines going to have?
2005-11-23 02:07:38 Michael Slusarz Comment #4 Reply to this comment
What we could do is quoted-printable encode any line longer than x 
amount of characters (i.e. 500) since quoted-printable lines must be 
wrapped at 76 characters.  We are supposed to avoid quoted-printable 
encoding as much as possible although the reason why - so that 
non-MIME MUA's don't see a message with a bunch of ugly encoding 
characters - is kind of becoming pointless because quite-honestly: how 
many non-MIME MUA's are out there?
2005-11-22 23:51:54 adrieder (at) sbox (dot) tugraz (dot) at Comment #3 Reply to this comment
When attaching a text file (e.g. xml) which has very long lines, the
file will be broken at the recepient side. This is because the SMTP
server (e.g. sendmail) will break lines after 990 characters in the
following way:
And what should *we* do about it, if the *SMTP server* is breaking it?
Good question :-)

Maybe base64 encode the such attachements. This could be a config option.



I see the problem and it really seems not to be *your* fault, but I guess

sendmail is widely used. So a work arround would help in many cases.




2005-11-22 23:26:23 Jan Schneider Comment #2
State ⇒ Feedback
Priority ⇒ 1. Low
Reply to this comment
When attaching a text file (e.g. xml) which has very long lines, the
file will be broken at the recepient side. This is because the SMTP
server (e.g. sendmail) will break lines after 990 characters in the
following way:
And what should *we* do about it, if the *SMTP server* is breaking it?
2005-11-22 23:08:56 adrieder (at) sbox (dot) tugraz (dot) at Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 3. High
Summary ⇒ text attachments with very long lines get broken
Queue ⇒ IMP
Reply to this comment
When attaching a text file (e.g. xml) which has very long lines, the 
file will be broken at the recepient side. This is because the SMTP 
server (e.g. sendmail) will break lines after 990 characters in the 
following way:

   [1...990 characters]!

   rest of the line

This is critical, because applications (e.g. maple) can't read/parse 
the resulting files.



This is an example of the relevant parts of the raw message:

[...headers...]

Subject: test 01

MIME-Version: 1.0

Content-Type: multipart/mixed;

        boundary="=_48ql1hbg4s8w"

Content-Transfer-Encoding: 7bit

User-Agent: Internet Messaging Program (IMP) H3 (4.2-cvs)

X-Scanned-By: MIMEDefang 2.52 on 129.27.3.25

X-Scanned-By: milter-sender/1.5.882 (mail [129.27.3.25]); Tue, 22 Nov 
2005 22:56:02 +0100

X-Scanned-By: MIMEDefang 2.52 on 129.27.10.19



This message is in MIME format.



--=_48ql1hbg4s8w

Content-Type: text/plain;

        charset=ISO-8859-1;

        format="flowed"

Content-Disposition: inline

Content-Transfer-Encoding: 7bit



Test Text Body



--=_48ql1hbg4s8w

Content-Type: text/xml;

        charset=ISO-8859-1;

        name="mime-maple.mw"

Content-Disposition: attachment;

        filename="mime-maple.mw"

Content-Transfer-Encoding: 7bit



<?xml version="1.0" encoding="UTF-8"?>

<Worksheet>

<Version major="7" minor="0"/>

<Label-Scheme value="2" prefix=""/>

<View-Properties presentation="true"></View-Properties>

<MapleNet-Properties warnlevel="3" longdelim="true"  [........]

Saved Queries