| Summary | 76 char line breaking causes gmail's smtp server to reject mail |
| Queue | IMP |
| Queue Version | Git master |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | q0107 (at) cuba (dot) ionum (dot) ch |
| Created | 09/19/2011 (5037 days ago) |
| Due | |
| Updated | 09/20/2011 (5036 days ago) |
| Assigned | |
| Resolved | 09/20/2011 (5036 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Priority ⇒ 1. Low
Ticket #10122State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ 76 char line breaking causes gmail's smtp server to reject mail
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
mails are bounced. quoted-printable mails must not exeed line length
over 76 chars.
if a line has exactly 76 chars and ends with a point and this line get
a quote-prefix (like '>') this point goes (as a single char) to the
next line. but a single point on a line marks the end of the mail, so
gmail thinks that this mail violates mail-rfcs
original mail line [76 chars]:
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy ei.
in a reply, the above mail line looks like this: