Closed Bug 1283895 Opened 10 years ago Closed 10 years ago

Support for non-ASCII char emails addys

Categories

(Websites :: Basket, defect)

Product:
Websites
Component:
Basket
Version:
Production
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jdavis, Assigned: pmac)

Details

Basket's throwing errors when someone tries to submit an email address that uses a non-ASCII char email. Examples: señior@example.com møtörheåd@example.com The short answer is "These types of emails are not supported by Salesforce Marketing Cloud". Long answer …. SFMC, two issues: 1) invalid email error - "special" character like ñ, ø, ö, å can't be used in the emailaddress value in the All Subscribers list. 2) can-spam filter - Salesforce Marketing Cloud has a can-span filter that prevents specific domains form being imports a subscribes. This list of domains is not visible via the user interface, but apparently @example.com is on this list. SFDC, one issue: 1) Invalid data error – The email field on the Contact record will not allow these characters to be used either. If we were to accept those emails, and add them to SFDC - would SFDC/SFMC be able to send an email to it? Pmac has cleverly come up with a fix to update our email address validation basically along these lines. Basket will soon return an "invalid email address" error for requests where a non-ascii character is in the username portion (before the @) of the address. This change will also add support for international domain names via a feature of the DNS system that allows us to convert the domain portion of the address (after the @) to an ascii representation of the domain that will resolve correctly. This is called IDNA[1] and should allow us to support users with email addresses at these domains (some of which we've seen as errors already). For example: düdé@example.com would return an error dude@éxåmplë.com would be converted to dude@xn--xmpl-qoawt.com and should work fine. Basket will do the conversion to the IDNA version before storage and lookup of email addresses so that it's all seamless for the users. [1] https://en.wikipedia.org/wiki/Internationalized_domain_name This bug is to track this work.
Assignee: nobody → pmac
In production!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.