Loading

Salesforce Email Address Format Technical Standards Validation

Publiseringsdato: May 11, 2026
Beskrivelse

Note: Information in this article applies to both Classic and Lightning Experience.
RFC, or "Request for Comments," refers to a set of technical standards that define the rules for email formatting and transmission. RFC standards govern the structure of an email address and its headers, ensuring compatibility between different email systems across the internet.
Salesforce makes every attempt to conform to the latest RFC standards related to email. There are some areas where Salesforce diverges from these specifications, though in the majority of use cases this does not impact customers' ability to send email to specific addresses.
The following sections describe the supported email address formatting standards in Salesforce, including known areas of RFC compliance gaps.

 

Løsning

Supported Email Format Standards

  • Allowed Characters: Salesforce supports the full range of characters as documented in the RFCs. Salesforce also supports Email Address Internationalization (EAI), which allows the use of non-Latin based characters in email addresses. See Email Address Internationalization Setup.
  • Maximum Address Size: Per RFC standards, an email address can be 256 characters in length. Most email address fields in Salesforce are currently limited to 80 characters, which is sufficient for most addresses. 
  • Case Storage: Salesforce stores email addresses in lower case. The RFC standard is somewhat ambiguous on case sensitivity, but conversion to lower case does not cause email delivery issues in practice.
  • Consecutive Periods: Consecutive period characters (..) are allowed in the middle and at the end of the local part of an email address (e.g., a..a@test.jp and a..@test.jp) but not at the beginning (e.g., .a@test.jp). This diverges from RFC standards but was specifically requested by customers in Japan due to local email provider practices.
  • Comments: Comments, denoted by matched parentheses, are allowed in both the domain and the local part of an email address. Comments are not shown when viewing the address and are ignored when sending email. For example, john.doe@(comment)example.com and john.doe@example.com are equivalent.

Known RFC Compliance Gaps

The RFC specification contains gray areas — including features marked as obsolete but kept in the specification. Salesforce is likely out of full compliance with:

  • Comments in email addresses
  • Quoted local parts

Both of these are less commonly used features, and Salesforce Support receives very few issues related to them.

Reporting Email Address Format Issues

If a specific email address format causes unexpected behavior in your Salesforce org, document the exact address format and contact Salesforce Support with the following information:

  • The exact email address causing the issue
  • The Salesforce field where the address was entered
  • The exact error message received, if any

Note: Salesforce does not provide regex or sample code that covers all email address validation rules.

Additional information:

Knowledge-artikkelnummer

000384328

 
Laster
Salesforce Help | Article