How about these: -- CR & NL char in rfc2047-encoded header...

How about these: -- CR & NL char in rfc2047-encoded header...

[tomi.ollila]

In thread starting from id:08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.com
David wondered in id:87y58xv71x.fsf@zancas.localnet what filtering
is done by CLI and what by lib.

But where should the "problem" presented in the Subject: header should
be handled. I did some hacks to emacs client to drop the ^J (newline)
characters from Subject: and From: headers but should these be filtered
in CLI (or in lib) instead?

Tomi

Re: How about these: -- CR & NL char in rfc2047-encoded header...

[David Bremner]

tomi.ollila@iki.fi writes:

> In thread starting from id:08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.com
> David wondered in id:87y58xv71x.fsf@zancas.localnet what filtering
> is done by CLI and what by lib.
>
> But where should the "problem" presented in the Subject: header should
> be handled. I did some hacks to emacs client to drop the ^J (newline)
> characters from Subject: and From: headers but should these be filtered
> in CLI (or in lib) instead?
>

Eventually we decided this was a front-end isssue. The emacs front-end
fixed this  with commit 0.16-111-ga7964c8

d

Re: How about these: -- CR & NL char in rfc2047-encoded header...

[Patrick Totzke]

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

Quoting David Bremner (2013-10-27 12:48:24)
> tomi.ollila@iki.fi writes:
> 
> > In thread starting from id:08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.com
> > David wondered in id:87y58xv71x.fsf@zancas.localnet what filtering
> > is done by CLI and what by lib.
> >
> > But where should the "problem" presented in the Subject: header should
> > be handled. I did some hacks to emacs client to drop the ^J (newline)
> > characters from Subject: and From: headers but should these be filtered
> > in CLI (or in lib) instead?
> >
> 
> Eventually we decided this was a front-end isssue. The emacs front-end
> fixed this  with commit 0.16-111-ga7964c8


I agree that this should be an issue for the MUA.
FYI: alot also normalizes newlines and tabs in subject lines..
https://github.com/pazz/alot/blob/master/alot/db/utils.py#L369
I cannot reproduce the original issue with the escaped UTF8 header not being interpreted.
This works fine for me in alot.

Best,
/p

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iEYEABECAAYFAlJtE+kACgkQlDQDZ9fWxaqq4ACfXq9YfOQnT5g4U5StYY5xbm/v
vUcAn3BCQrEV5XIzVb4U3eC/78/eljRd
=CHQd
-----END PGP SIGNATURE-----