Skip to content
This repository has been archived by the owner. It is now read-only.

Mails broken if /accounts/user/name contains umlauts #321

Closed
macosforgebot opened this issue Feb 7, 2011 · 3 comments
Closed

Mails broken if /accounts/user/name contains umlauts #321

macosforgebot opened this issue Feb 7, 2011 · 3 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Feb 7, 2011

mail@… originally submitted this as ticket:413


Hi,

I have an Umlaut in my name: ö.

The mailgateway will send mails like the following:

2011-02-07 09:50:08+0100 [-] [mailgateway]    From: =?utf-8?q?Felix_M=C3=B6ller_=3Cmail=40felixmoeller=2Ede=3E?=

Removing the Umlaut it gets back to:

2011-02-07 10:01:06+0100 [-] [mailgateway]    From: Felix Moeller <mail@felixmoeller.de>

I guess this should allready be encoded in Quoted Printable at:

            formattedFrom = "%s <%s>" % (cn, fromAddr)

Workarround is to remove the Umlaut...

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Apr 20, 2011

@cyrusdaboo originally submitted this as comment:1:⁠ticket:413


The ?q? encoding piece should only be applied to the "comment" portion of the From address and not the mailbox portion. i.e. it ought to have been:

From: =?utf-8?q?Felix_M=C3=B6ller?= <mail@…>

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jul 13, 2011

mail@… originally submitted this as comment:2:⁠ticket:413


With current head it sends a mail out like this:

2011-07-13 07:05:25+0200 [-] [mailgateway]     From: Felix Möller <mail@felixmoeller.de>

Is this valid? I often read on the internet that headers must be encoded in 7/8 bits no matter what the characterset of the mail is.

Whats about http://tools.ietf.org/html/rfc2047 ?

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Jul 13, 2011

@m0rgen originally submitted this as comment:3:⁠ticket:413

  • Status changed from new to closed
  • Resolution changed from to Software changed

Correct, the From needs to be encoded (the Subject already was being properly encoded), fixed in https://trac.calendarserver.org/changeset/7784/CalendarServer/trunk

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.