Summary
The validity of an email address with a dot immediately before the @ symbol for Gmail is inconsistent and debated. RFC standards, Flanker library and MSDN deem such addresses invalid. However, anecdotal evidence suggests Gmail might accept them, but this isn't guaranteed and other ESPs are likely to reject them, leading to deliverability issues. Experts at Email Geeks offer conflicting views, with some seeing successful delivery and others recommending treating such addresses as invalid. Most email marketing resources flag these addresses as syntactically incorrect, highlighting the importance of adhering to standard syntax and validating email addresses.
Key findings
- RFC Invalid: According to RFC 5322, Flanker Library and MSDN documentation, email addresses with a dot directly before the @ symbol are invalid.
- Gmail Ambiguity: While some evidence suggests Gmail might accept these addresses, this is not definitively confirmed and could change.
- ESP Rejection: Other ESPs are likely to reject such addresses, leading to deliverability problems.
- Non-Standard Format: Most email marketing resources consider this format syntactically incorrect and not compliant with standard practices.
Key considerations
- Validation Importance: Validating email addresses is crucial, regardless of anecdotal evidence suggesting Gmail's potential acceptance.
- Syntax Compliance: Adhering to standard email address syntax is essential for optimal deliverability and compatibility.
- ESP Variability: Recognize that even if Gmail accepts these addresses, other ESPs might reject them, affecting the overall campaign reach.
- Potential List Hygiene Issues: Including these addresses in mailing lists can lead to long-term list hygiene problems and affect sender reputation.
- Unreliable Format: Do not rely on this format as standard. Even if it does work on a particular platform, it is not reliable, and practices may change in the future.
What email marketers say
8 marketer opinions
The validity of an email address with a dot immediately before the @ symbol for Gmail is complex and somewhat contradictory. While RFC standards generally deem such addresses invalid, Gmail's behavior is more lenient. Some sources suggest Gmail may accept these addresses, ignoring the period as it does with others in the local part. However, this behavior isn't guaranteed and might be unintentional. Several email marketing resources flag such addresses as invalid due to deliverability concerns and non-standard syntax. It's best practice to validate email addresses and adhere to standard formats, even if Gmail appears tolerant.
Key opinions
- RFC Invalid: RFC standards generally consider email addresses with a dot directly before the @ symbol invalid.
- Gmail Lenient: Gmail might accept these addresses and still deliver email, though this behavior is inconsistent and could change.
- Non-Standard: Many email marketing tools and resources flag these addresses as invalid or syntactically incorrect.
- Deliverability Issues: Using these addresses may lead to deliverability problems, even if Gmail initially accepts them.
Key considerations
- Validation: It's crucial to validate email addresses before using them, regardless of Gmail's potential leniency.
- Syntax Adherence: Adhering to standard email address syntax improves deliverability and reduces the risk of issues.
- Provider Differences: Even if Gmail accepts these addresses, other providers might reject them, affecting overall campaign reach.
- Future Changes: Gmail's behavior could change, rendering previously 'valid' addresses invalid, impacting list hygiene.
Marketer view
Email marketer from Reddit comments that Gmail often allows invalid email addresses, but this can vary. They don't recommend relying on this behavior, as it could change. It's best to validate email addresses properly before using them, even for Gmail.
22 Feb 2024 - Reddit
Marketer view
Marketer from Email Geeks states that technically local.@domain.com is invalid according to RFC and should be assumed as such everywhere. Even if some email apps or SMTP servers allow it. He also adds that even though Google may accept it at their MX (mail exchanger), it doesn't mean it will get there via other MTAs (Mail Transfer Agents) and Google also doesn't deem it valid in their own apps, so you should assume it's invalid.
4 Jun 2022 - Email Geeks
What the experts say
4 expert opinions
The provided answers present a mixed view on the validity of email addresses with a dot before the @ symbol for Gmail. One expert from Email Geeks successfully tested sending an email to such an address from Yahoo to Gmail, suggesting acceptance by Gmail's inbound mail processing. However, another expert from Email Geeks received mail at such an address but cautioned that other ESPs may block these addresses due to invalid SMTP syntax and recommends treating them as invalid. Spam Resource and Word to the Wise don't directly address this specific scenario.
Key opinions
- Gmail May Accept: Gmail's inbound mail processing might accept email addresses with a dot before the @ symbol.
- ESP Restrictions: Other Email Service Providers (ESPs) may block these addresses due to invalid SMTP syntax.
- Inconclusive Resources: Spam Resource and Word to the Wise do not provide a definitive answer to the question.
Key considerations
- ESP Compatibility: Consider compatibility with different ESPs, as some may block these addresses despite Gmail's potential acceptance.
- Potential Deliverability Issues: Be aware of potential deliverability issues if using these addresses, as they may be considered invalid by many systems.
- Address Validation: It is advisable to validate email addresses and use only those that conform to standard syntax.
Expert view
Expert from Email Geeks received an email at an address with a dot right before the @ symbol. She explains that Gmail accepts the email, but your ESP may block such addresses because they are invalid SMTP. Even if the ESP accepts it the SMTP may put quotes around it. She says the fact direct emails are accepted into gmail does not mean other providers will work. She recommends treating those addresses as invalid if you were a client.
1 Jun 2022 - Email Geeks
Expert view
Expert from Word to the Wise does not directly address whether a dot before the @ sign in an email is valid. They mainly focus on general deliverability issues and list management rather than email address syntax.
25 Aug 2023 - Word to the Wise
What the documentation says
3 technical articles
The documentation sources consulted (RFC Editor, Mailgun's Flanker library, and MSDN) generally indicate that an email address with a dot immediately before the @ symbol is technically invalid. RFC 5322 specifies restrictions on the placement of periods in the local part, prohibiting them as the first or last character and ruling out consecutive periods. While Flanker library doesn't directly address this specific scenario, its restrictions imply invalidity. MSDN notes restrictions on the local part of an email address as well, with no allowance for that type of syntax.
Key findings
- RFC Invalidity: According to RFC 5322, an email address with a dot before the @ symbol is not valid.
- Flanker Implication: Mailgun's Flanker library's restrictions suggest that such an address would be considered invalid.
- MSDN restrictions: MSDNs documentation restricts the local part of the email address, not allowing for that syntax.
Key considerations
- Standard Compliance: Adhering to RFC specifications ensures broader compatibility and reduces the risk of deliverability issues.
- Validation Tools: Use validation tools that adhere to RFC standards to identify and correct invalid email addresses.
- Potential for Issues: Even if some systems accept these addresses, relying on non-standard syntax can lead to unforeseen problems.
Technical article
Documentation from MSDN notes that in general, the local part of an email address has specific restrictions regarding periods. It does not list that this is acceptable in email addresses.
23 Jul 2021 - MSDN
Technical article
Documentation from Mailgun's Flanker library indicates that dots at the beginning or end of the local part are not permitted. While this doesn't explicitly address dots immediately before the @, it implies that it would likely be considered invalid.
16 May 2022 - GitHub
Can 'invalid recipient' bounce messages be false positives and what should I do about it?
How can I accurately verify my email list and identify potentially harmful domains?
How do I validate the structure of an email account and what are some valid email address examples?
How does Gmail handle dots in email addresses and can it cause issues?
What are the best ways to check for and prevent email typos on signup forms?
What special characters are allowed in email address syntax according to RFC 5322 and how do different email providers handle them?
