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

"õ" =~ EXTRACT_FIELD_NAME_RE yields error #1

Closed
ZJvandeWeg opened this issue Feb 27, 2015 · 7 comments
Closed

"õ" =~ EXTRACT_FIELD_NAME_RE yields error #1

ZJvandeWeg opened this issue Feb 27, 2015 · 7 comments

Comments

@ZJvandeWeg
Copy link

For sup-heliotrope/sup#205 the proposed fix was gauteh@2ee5086. The equivalent is yet incorporated on this fork.

@ZJvandeWeg ZJvandeWeg changed the title EXTRACT_FIELD_NAME_RE error on "õ" =~ EXTRACT_FIELD_NAME_RE yields error Feb 27, 2015
@terceiro
Copy link
Owner

terceiro commented Mar 2, 2015

Hi, can you provide a concrete test case containing the actual header that causes the issue?

@ZJvandeWeg
Copy link
Author

I might have been to fast with this issue.
Will look into it this weekend again. Sorry for wasting your time.

@gauteh
Copy link

gauteh commented Apr 7, 2015

Test message and tests for sup that currently fail are here: sup-heliotrope/sup#214

@gauteh
Copy link

gauteh commented Apr 7, 2015

An incorrect fix is here: sup-heliotrope#3

@terceiro
Copy link
Owner

I tried feeding those messages to rmail and they are handled without issue, because rmail will not try to parse them. Even properly quoted non-ascii header values are returned as is with no parsing.

However the unquoted utf-8/latin1 data in header values will come back encoded as ASCII-8BIT, and that needs to be handled properly by whoever is using rmail.

In short, this does not look like something that can be fixed in rmail without breaking its API.

@maxmeyer
Copy link

maxmeyer commented Jan 9, 2016

@maxmeyer
Copy link

maxmeyer commented Jan 9, 2016

This is quite an annoying bug. :-(

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

No branches or pull requests

4 participants