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

Any update on UTF8 characters in addresses? #1014

Closed
njt1982 opened this issue Jul 17, 2016 · 9 comments
Closed

Any update on UTF8 characters in addresses? #1014

njt1982 opened this issue Jul 17, 2016 · 9 comments

Comments

@njt1982
Copy link

njt1982 commented Jul 17, 2016

I see this was mentioned and closed off in #39... I am still getting:

Mail::Field::ParseError: Mail::AddressList can not parse |"Matija Marohnić" <notifications@github.com>|
Reason was: Only able to parse up to "Matija Marohnić

Are these characters still out?

@nickrivadeneira
Copy link

@njt1982 Did you find a workaround? I'm receiving this error as well.

@njt1982
Copy link
Author

njt1982 commented Apr 5, 2017

@nickrivadeneira nope 😞

@jeremy
Copy link
Collaborator

jeremy commented Apr 5, 2017

To address this, we'll need to implement RFC 6532 support: #39 (comment)

Or implement internationalization "downgrading"—see RFC 5504.

@jeremy jeremy closed this as completed Apr 5, 2017
@duane
Copy link

duane commented May 9, 2017

@jeremy What's the plan? Do I need to invest in my own parser? #39 is from 2010. Mikel's been giving ambivalent responses as to when this will be addressed at least since then; I've found remarks in 2012, 2014, 2015, 2016, and of course this year. I can live with slow timelines; but the lack of any firm direction for seven straight years seems like a sign it's not going to land anytime soon.

Is there any hope of RFC 6532 support this calendar year? Where are the ongoing efforts so I can contribute? Should we interpret lack of movement as lack of plans?

@jeremy
Copy link
Collaborator

jeremy commented May 9, 2017

@duane, it sounds like you've dug into the history a good bit. What's your take on the feasibility of implementing RFC5504 downgrading vs adding RFC6532 support?

Explicit social cue: I get where you're coming from, but hold up a sec. This is the way people talk to (aka push on) their account reps at Oracle and IBM and BigSupportContractCo, and it's likely their only chance to get action there. In open source, it burns people out and thickens their skins. No need for that dynamic.

@jeremy
Copy link
Collaborator

jeremy commented May 15, 2017

Fixed by #1103 😊

@nickrivadeneira
Copy link

@jeremy Thanks for the fix 😁

@duane
Copy link

duane commented May 17, 2017

@jeremy, thanks for the tip, I'll keep it in mind; I can certainly see what you mean.

My instinct is that parsing is distinct from downgrading, and ultimately Mail::Address should probably support both, but parsing should assist with the downgrading. Furthermore, RFC 6532 seems to be part of a broader RFC 6530 which obsoletes RFC 5504.

More broadly, RFC 5504 seems to be SMTP specific whereas RFC 6532 specifically addresses the mail address—I'd guess that'd be greater value for your effort.

@jeremy
Copy link
Collaborator

jeremy commented May 17, 2017

I took a closer look at downgrading, and doing it properly is a LOT more work! Who knew 😊

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