<<< Date Index >>>     <<< Thread Index >>>

Re: Mutt folds subject lines but Outlook doesn't properly unfold



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, November 27 at 04:31 PM, quoth Frank Bulk:
> For example, what was:
> Subject: A DSL modem belonging to username 'username' is constantly 
> reconnecting (112 times) 
> in the headers is now:
> Subject: A DSL modem belonging to username 'username' is constantly 
>       reconnecting (112 times)
>
> That wouldn't be so bad because this behavior is compliant with RFC 2822, 
> but Outlook 2003 and 2007 don't unfold it nicely, only removing the 
> CR/LF and not the tab. It really looks quite awful in my inbox.

Wait, it adds a TAB? That's not compliant with RFC 2822. According to 
section 2.2.3:

     Unfolding is accomplished by simply removing any CRLF
     that is immediately followed by WSP.

Translation: inserting tabs for "prettiness" is *wrong*. It doesn't 
say that when folding you're allowed to insert arbitrary whitespace. 
In fact, it only says in order to wrap a header you're allowed to 
insert a CRLF before any (pre-existing) WSP. For once, Outlook is 
right, and mutt is wrong.

> I haven't found a way for Outlook to deal with this correctly, 
> though I'm open to suggestions. 

Technically, Outlook *is* dealing with it correctly.

> Failing that, is there a way I can revert mutt's behavior to the 
> earlier release?  I don't see any command-line option or anything 
> describing how mutt even decides what length the subject line needs 
> to be before folding.

Unfortunately no... I suggest filing a bug report. :(

~Kyle
- -- 
If an elderly respected expert in a given field tells you that 
something can be done he is almost certainly right. If an elderly 
respected expert in a given field tells you that something is 
impossible, he is almost certainly wrong.
                                                  -- Robert A. Heinlein
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFHTKQTBkIOoMqOI14RAsz5AKCc+KuOtCXDRrWjbVkbwWds0t7v1wCglkvJ
5ezwbBDecFH4Dv6ZVgyAfXE=
=2+RZ
-----END PGP SIGNATURE-----