---
schema_version: "1"
id: 21deb78daded364234f0191d52e8bed537e156616c0c4d49bf695682e76b6e6f
title: Allowed Characters in Email Addresses
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/pardot_emails_allowed_characters.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.pardot_emails_allowed_characters.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a8fda9ff049d64ce8174b4bb1fc26ea52eb1adb2ca315865e11533979bdc2574
description: Account Engagement complies with the RFC’s 2822 standard for email address verification for both prospect and user email addresses. Addresses with non-UTF8 characters, such as Japanese or Russian characters, can’t be validated.
products:
  - Marketing
  - Marketing Cloud Account Engagement
release: "264"
---
# Allowed Characters in Email Addresses

Account Engagement complies with the RFC’s 2822 standard for email address verification for both prospect and user email addresses. Addresses with non-UTF8 characters, such as Japanese or Russian characters, can’t be validated.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span>All Account Engagement Editions</span></td></tr></tbody></table>

Account Engagement validates addresses only with these characters, which can appear in any part of the email address.

- 0–9
- a–z
- A–Z
- !#$%&'\*/=?^\_+-\`{|}~

The period character (.) is supported as long as it’s not the first or last character in the unique part that appears before the @.

For more information, see [RFC’s 2822](https://datatracker.ietf.org/doc/html/rfc3696#section-3) documentation.