View Issue Details

IDProjectCategoryView StatusLast Update
0006314OXID eShop (all versions)4.06. Language and translationspublic2016-03-08 15:37
Status acknowledgedResolutionopen 
Product Version4.9.6 / 5.2.6 
Target VersionFixed in Version 
Summary0006314: Non endoded "Umlauts" in Email not working
DescriptionIf the shop specific emails contain any (german) umlauts like äöü, the email sending fails and produces an error in the current frontend controller.

Steps To Reproduce1. set the shop info email to a value containing an umlaut, e.g. [email protected]ä
2. go to contact controller.
3. insert valid contact data into contact form.
4. send form -> you will receive an error msg.

Trying the above steps again with [email protected] will result in successful sending.
Additional InformationIf you use the encoded domain like e.g.
[email protected] = [email protected]ä as email address, it works.

Did not inspect the error, but it might possibly be an issue with the phpmailer lib, that's why i've chosen
3rd party libs as bug category.
TagsNo tags attached.
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
Database VersionNot defined


related to 0005085 resolvedSven Brunk adding attachments to order email for customer does not work 
related to 0005896 resolvedsaulius.stasiukaitis Deprecated: Function set_magic_quotes_runtime() is deprecated in ......./class.phpmailer.php on line 1350 
related to 0004200 resolvedsaulius.stasiukaitis Update phpmailer to latest revision 



2016-01-19 10:57

reporter   ~0011441

Last edited: 2016-01-19 10:59

View 2 revisions

If this is really a bug within phpmailer, it might already be fixed there. I already opened a bug-ticket for upgrading that lib:

From the changelog of that lib (
Version 5.2.14 (Nov 1st 2015)
* Allow addresses with IDN (Internationalized Domain Name) in PHP 5.3+, thanks to @fbonzon


2016-03-08 15:34

reporter   ~0011485

This exact case does not depend from PHPMailer version. I was able to reproduce the error with PHPMailer 5.0.2 and 5.2.14.

This error is triggered by the UTF setting which is written in the ``. If the UTF-8 mode is turned on ('1') there will be no error thrown. If the UTF-8 mode is turned off ('0') then the error will be thrown.