Open Bug 36797 Opened 24 years ago Updated 2 years ago

Mail folders saved with Windows line breaks

Categories

(MailNews Core :: Backend, defect, P3)

x86
Linux

Tracking

(Not tracked)

Future

People

(Reporter: akkzilla, Unassigned)

References

Details

I save my outgoing mail in the local folder "Sent".  It is saved with Windows
line breaks, i.e. CRLF instead of just LF, which makes it annoying to read in
other Unix apps (even if mozilla itself doesn't care).  

Probably, some code somewhere should be using NS_LINEBREAK to get the right line
breaks for each platform.
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Target Milestone: M17 → M18
Minor UI fixups to M18.  If this is incorrect, please adjust.
This is reall a hassle to deal with when using other Linux apps to
view/edit/copy from these folders, and the longer it goes on, the more bad
folders are going to be out there.  Besides, it should be a one-line change
(just change a "\r\n" to NS_LINEBREAK wherever it's doing the writing).  Adding
nsbeta3 keyword, though really I think we ought to think about it for nsbeta2.
Keywords: nsbeta3
Summary: Outgoing mail saved with Windows line breaks → Mail folders saved with Windows line breaks
Rich, any ideas?
If you are talking about the applications Sent folder (i.e. the Berkeley mail 
folder) these should be saved with CRLF line endings per the standards for 
RFC822 messages. This is not a platform specific issue. Now, if we save files 
to disk from the File-> Save menu and they are not platform specific, that 
would be the bug.

- rhp
RFC822 does specify CRLF as a separator for things like message headers, but it
doesn't say that this applies to saving local files, and it also includes the
proviso:

     3.4.10.  NETWORK-SPECIFIC TRANSFORMATIONS
 
        During transmission through heterogeneous networks, it may  be
        necessary  to  force data to conform to a network's local con-
        ventions.  For example, it may be required that a CR  be  fol-
        lowed  either by LF, making a CRLF, or by <null>, if the CR is
        to stand alone).  Such transformations are reversed, when  the
        message exits that network.

which seems to indicate fairly explicitly that it is not intended to conflict
with machine or local network linebreak standards.

In any case, our folders should be compatible with other mailers, editors and
other software on the platform, which means it should use platform line breaks,
just like we always did in previous versions of netscape.  Otherwise it seems
like we're trying to lock people into using our mailer by making our output
format nonstandard.
4.x stores local mailbox files using platform-specific linebreaks. Compatibility 
with other mail clients would be harmed on Mac if we were to do otherwise.
Keywords: mail2
+ per mail triage
Whiteboard: [nsbeta3+]
second pass: - per mail triage
Whiteboard: [nsbeta3+] → [nsbeta3-][cut 8/28]
removing mail2 keyword.
Keywords: mail2
reassigning jefft's bugs to naving
Assignee: jefft → naving
Status: ASSIGNED → NEW
Keywords: nsbeta3nsbeta1-
Whiteboard: [nsbeta3-][cut 8/28]
Target Milestone: M18 → Future
moving to future milestone.
Depends on: 70728
mass re-assign.
Assignee: naving → sspitzer
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: lchiang → backend
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.