Wrap In-Reply-To and References in <>'s

[frioux]

No description provided.

[rjbs]

I wonder why it parses the headers, instead of just using them.

Anyway, seems reasonable, maybe. Maybe should use Email::MessageID instead.

Want some comaint?

[frioux]

You would know better than I would how to deal with the headers, so I defer
to you in those matters.

And no I don't want comaint.

sent from a rotary phone, pardon my brevity
On Mar 24, 2016 6:25 PM, "Ricardo Signes" notifications@github.com wrote:

I wonder why it parses the headers, instead of just using them.

Anyway, seems reasonable, maybe. Maybe should use Email::MessageID instead.

Want some comaint?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#5 (comment)

[pali]

I wonder why it parses the headers, instead of just using them.

It is wrong to try parsing Message-Id headers with parser for addr-list structures. It is even worse to try parsing them via Email::Address module.

And yes, you can just return those Message-Id headers as you are not interested in its content. I fixes it in pull request: #6