From: Patrick Totzke <patricktotzke@gmail.com>
To: David Bremner <bremner@unb.ca>,
tomi.ollila@iki.fi, notmuch@notmuchmail.org
Subject: Re: How about these: -- CR & NL char in rfc2047-encoded header...
Date: Sun, 27 Oct 2013 13:23:53 +0000 [thread overview]
Message-ID: <20131027132353.5125.14023@brick> (raw)
In-Reply-To: <87hac23mnb.fsf@zancas.localnet>
[-- 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-----
prev parent reply other threads:[~2013-10-27 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 19:17 How about these: -- CR & NL char in rfc2047-encoded header tomi.ollila
2013-10-27 12:48 ` David Bremner
2013-10-27 13:23 ` Patrick Totzke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131027132353.5125.14023@brick \
--to=patricktotzke@gmail.com \
--cc=bremner@unb.ca \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).