On Thu, May 14, 2020 at 11:51:08AM +0200, Oswald Buddenhagen wrote:
On Wed, May 13, 2020 at 08:03:02PM -0700, Kevin J. McCarthy wrote:
However, in order to reduce the risk of extracting garbage, insist that message-id's outside of angle brackets at least have an '@'.

well, guess what, the message-ids from aliexpress are just bare hex numbers (md5s?).

That's hilarious.  Come on aliexpress...

i think a reasoanble heuristic would be to just accept anything as long as it's a single string with no whitespace.

Well, it's not hard to pull the '@' check out. I was just worried we might miss the real message-id if someone started generating garbage outside of a comment:
  Mesage-ID: lkjsdflk <1...@example.com>

If you all think that's unlikely, I'll just accept the first non-comment token, and for references/in-reply-to accept all the non-comment tokens.

By the way, Mutt is now internally adding <> to those without. Replying will generate in-reply-to/references with angle brackets, as will <link-threads>.

I'm not keen on displaying warning messages to users that they can do nothing about, but I think adding the brackets is an appropriate response, especially if it breaks the original sender's threading. :-)

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to