Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle a wide variety of non-rfc Message-Id formats #607

Closed
wants to merge 2 commits into from

Conversation

peterkovacs
Copy link
Contributor

Handle Message-Id formats such as:

  • <id_left@id_right...
  • <id_left...
  • <id_left>
  • id_left@id_right
  • id_left

Handle comma separated message ids.

Handle Message-Id formats such as:

  * <id_left@id_right...
  * <id_left...
  * <id_left>
  * id_left@id_right
  * id_left

Handle comma separated message ids.
@peterkovacs
Copy link
Contributor Author

Exchange, in particular will truncate long References fields with "..." leading to some message-ids ending with that string.

Also, in practice, I see comma-separated lists of message-ids in the References field as often (or more often) than the correct space separated lists.

:local_dot_atom_s,
:qstr_s, :qstr_e,
:local_quoted_string_e,
:comment_s, :comment_e
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like the indentation is different in your change?

@bpot
Copy link
Contributor

bpot commented Sep 12, 2013

This looks pretty good at first glance. Is there any reason to include "," in message_id instead of using the solution you used in #606? I think I prefer only having the comma in message_ids, it's a little more clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants