• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

substancelab / activemodel-email_address_validator
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: dependabot/add-v2-config-file
DEFAULT BRANCH: master
Repo Added 17 Oct 2015 09:40AM UTC
Files 4
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH umlaut
branch: umlaut
CHANGE BRANCH
x
Reset
  • umlaut
  • 1.0.0
  • active_model_5_support
  • dependabot/add-v2-config-file
  • dependabot/bundler/activemodel-gte-4.0-and-lt-7.0
  • dependabot/bundler/bundler-tw-2.0
  • dependabot/bundler/rake-tw-12.3
  • dependabot/bundler/rake-tw-13.0
  • master
  • more-badges
  • out_with_the_old
  • relax_requirements
  • rubies
  • rules
  • tilde-domains
  • v0.1.0
  • v1.0.0
  • v1.0.1
  • v2.0.0

pending completion
78

Pull #11

travis-ci

web-flow
Clarify support for UTF-8 characters in email addresses

First of all, we already validate those as valid, so this is just a codification
of that expectation.

Second of all, it is a valid email address - at least according to RFC6532
<https://tools.ietf.org/html/rfc6532>. It still needs to be encoded properly
before actually being delivered. The Mail gem added support for this in v2.7.0:
https://github.com/mikel/mail/pull/1103.

That said, actually finding services that support this is still hard (in 2019).
Neither Gmail nor Hotmail supports this for their own local accounts, but can
send to email addresses with non-US ASCII characters. Exim has added
experimental support, it seems (https://bugs.exim.org/show_bug.cgi?id=1516).

Firefox, Chrome, and Safari rejects email addresses with non-US ASCII characters
when validating email fields. Mailguns email validation API says the address is
invalid (or rather it gives `"result": "unknown", `).

Regardless of the lack of widespread support we allow these addresses because
the guiding principle is:

> Don't reject a valid email address realistically in use by a potential user.
> Err on the side of accepting too much.

An email address with non-US ASCII characters can realistically be in use by a
potential user, even though the major international players doesn't support
that.
Pull Request #11: Clarify support for UTF-8 characters in email addresses

2 of 2 new or added lines in 1 file covered. (100.0%)

115 of 115 relevant lines covered (100.0%)

17.29 hits per line

Relevant lines Covered
Build:
Build:
115 RELEVANT LINES 115 COVERED LINES
17.29 HITS PER LINE
Source Files on umlaut
  • List 0
  • Changed 2
  • Source Changed 1
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
78 umlaut Clarify support for UTF-8 characters in email addresses First of all, we already validate those as valid, so this is just a codification of that expectation. Second of all, it is a valid email address - at least according to RFC6532 <https://too... Pull #11 02 Aug 2019 09:38AM UTC web-flow travis-ci pending completion  
77 umlaut Clarify support for UTF-8 characters in email addresses First of all, we already validate those as valid, so this is just a codification of that expectation. Second of all, it is a valid email address - at least according to RFC6532 <https://too... push 02 Aug 2019 09:38AM UTC koppen travis-ci pending completion  
69 umlaut Clarify support for UTF-8 characters in email addresses First of all, we already validate those as valid, so this is just a codification of that expectation. Second of all, it is a valid email address - at least according to RFC6532 <https://too... Pull #11 02 Aug 2019 09:12AM UTC web-flow travis-ci pending completion  
68 umlaut Clarify support for UTF-8 characters in email addresses First of all, we already validate those as valid, so this is just a codification of that expectation. Second of all, it is a valid email address - at least according to RFC6532 <https://too... push 02 Aug 2019 09:10AM UTC koppen travis-ci pending completion  
See All Builds (79)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc