View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002755SOGoBackend Mailpublic2014-05-08 17:362014-05-14 14:24
ReporterJens Erat Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version2.2.3 
Summary0002755: SOGo is not able to handle non-ASCII characters in mail addresses correctly
Description

SOGo has problems with non-ASCII-characters (Unicode >127) in mail addresses. One of our users ran in this problem with a mail address containing the umlaut "ü". Lots of Unicode characters are allowed following current RFC proposal 6531: http://tools.ietf.org/html/rfc6531

There are different ways to reproduce the issue, either by the recipient having unicode characters in it or the sender's address. The result is always some encoding hint appearing in front of or instead of the mail address, and SOGo seems to fail saving the sent message (at least, although the mail gets send, there's never saved one and also the send request times out without any warning / the send window doesn't close).

Steps To Reproduce

Sender having umlaut:

  1. Add a user with mail address containing an umlaut to the user database
  2. Logon as this user
  3. Send new mail to any user (can also be a "normal" address)
  4. Receiver will see garbled sender address

Recipient having umlaut:

  1. Logon as a normal user
  2. Send new mail to user like müller@example.net
  3. Mail will be sent with the correct recipient, but in the mail header the "To:" field is garbled ("To: =?utf-8?q?@smtp.example.net"), where smtp.example.net is the mail host SOGo is using for sending
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2014-05-08 17:36 Jens Erat New Issue