Open Bug 1334511 Opened 8 years ago Updated 2 years ago

Feed messages should comply with RFC 821 and not exceed a max. line length of 1000 characters

Categories

(MailNews Core :: Feed Reader, defect)

x86
Windows 8.1
defect

Tracking

(Not tracked)

People

(Reporter: jorgk-bmo, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #958393 +++ Our attaching mechanism in https://dxr.mozilla.org/comm-central/rev/1994d82f97322ab5fc42601ad49a859a6844e96b/mailnews/compose/src/nsMsgAttachmentHandler.cpp#461 will attach any message "as is" since it can't change the CTE to base64. Feed messages should comply with RFC 821 and not exceed a max. line length of 1000 characters.
For an example produced by TB, see attachment 8831051 [details].
(In reply to Jorg K (GMT+1) from comment #1) > For an example produced by TB, see attachment 8831051 [details]. Sorry, RFC821 (and successors) deal with outbound SMTP specs, meaning behavior of compose, for an MUA. Meaning it's irrelevant for enforcing anything upon a source of data which *may* be used for SMTP submission. That's like saying a clipboard has to format to 821 *before* pasting into compose editor - which is pretty silly. Unless you can provide a specification which makes it illegal to store to berkely mbox format with lines over a certain length, like I've already hinted, this is gonna be invalid..
Well the messages we store on disk are supposedly following the rfc822 format, and 999 is a hard limit. https://tools.ietf.org/search/rfc5322#section-2.1.1
The correct one is RFC4155: https://tools.ietf.org/html/rfc4155 ;) "The Law should be Code, and not Code the Law"
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.