Tip #4 - Validating an Email Address with Ruby on Rails
April 14th, 2008
Did you know that Rails has inbuilt a strong email handling library called (ahem) TMail? I just so happen to maintain this now (Minero Aoki wrote it), but it gives you a great way to validate email addresses…
If you have ever tried to handle the validation of email addresses in your Rails app, you have probably ended up trying to use something like this to validate the address:
1 2 |
validates_format_of :email, :with => /^([^@\s]+)@((?:[-a-z0-9]+\.)+[a-z]{2,})$/i |
Now, this works… in most cases, but there are a few specifics that won’t.
So some of you out there decide that you want a REAL email validation process and so you go for this regular expression instead:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
EmailAddress = begin qtext = '[^\\x0d\\x22\\x5c\\x80-\\xff]' dtext = '[^\\x0d\\x5b-\\x5d\\x80-\\xff]' atom = '[^\\x00-\\x20\\x22\\x28\\x29\\x2c\\x2e\\x3a-' + '\\x3c\\x3e\\x40\\x5b-\\x5d\\x7f-\\xff]+' quoted_pair = '\\x5c[\\x00-\\x7f]' domain_literal = "\\x5b(?:#{dtext}|#{quoted_pair})*\\x5d" quoted_string = "\\x22(?:#{qtext}|#{quoted_pair})*\\x22" domain_ref = atom sub_domain = "(?:#{domain_ref}|#{domain_literal})" word = "(?:#{atom}|#{quoted_string})" domain = "#{sub_domain}(?:\\x2e#{sub_domain})*" local_part = "#{word}(?:\\x2e#{word})*" addr_spec = "#{local_part}\\x40#{domain}" pattern = /\A#{addr_spec}\z/ end |
And then your validates_format_of becomes:
1 2 |
validates_format_of :email, :with => EmailAddress |
Which is neat, but you have to stuff that Regex away somewhere. When I used this, (by the way) I would make a file in /lib called ‘rfc822.rb’ and then put this in it:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
# # RFC822 Email Address Regex # -------------------------- # # Originally written by Cal Henderson # c.f. http://iamcal.com/publish/articles/php/parsing_email/ # # Translated to Ruby by Tim Fletcher, with changes suggested by Dan Kubb. # # Licensed under a Creative Commons Attribution-ShareAlike 2.5 License # http://creativecommons.org/licenses/by-sa/2.5/ # module RFC822 EmailAddress = begin qtext = '[^\\x0d\\x22\\x5c\\x80-\\xff]' dtext = '[^\\x0d\\x5b-\\x5d\\x80-\\xff]' atom = '[^\\x00-\\x20\\x22\\x28\\x29\\x2c\\x2e\\x3a-' + '\\x3c\\x3e\\x40\\x5b-\\x5d\\x7f-\\xff]+' quoted_pair = '\\x5c[\\x00-\\x7f]' domain_literal = "\\x5b(?:#{dtext}|#{quoted_pair})*\\x5d" quoted_string = "\\x22(?:#{qtext}|#{quoted_pair})*\\x22" domain_ref = atom sub_domain = "(?:#{domain_ref}|#{domain_literal})" word = "(?:#{atom}|#{quoted_string})" domain = "#{sub_domain}(?:\\x2e#{sub_domain})*" local_part = "#{word}(?:\\x2e#{word})*" addr_spec = "#{local_part}\\x40#{domain}" pattern = /\A#{addr_spec}\z/ end end |
And then in my model:
1 2 3 |
include RFC822 validates_format_of :email, :with => EmailAddress |
Which is getting better. But the problem with that now is that you need to maintain that email address regular expression… which is quite… umm… “complex” I think is a good word :)
Enter TMail!
TMail has an “Address” class. It will throw an invalid address exception if given an address it can’t handle (and it has about 2,000 test cases of email addresses it can handle, so you are pretty safe.)
Plus, as the maintainer, whenever I find a valid email that TMail can not handle, I fix it, and then you benefit at the next gem install tmail… so it all turns out good :)
To use it, dump this in your user model somewhere (assuming your user model has the attribute ‘email_address’)
1 2 3 4 5 |
def valid_email? TMail::Address.parse(email) rescue errors.add_to_base("Must be a valid email") end |
Then your validates_format_of becomes:
validate :valid_email? |
Which is even nicer.. as in… less code == nicer :)
Next tip => How to validate the address fully before accepting it…
blogLater
Mikel
May 12th, 2008 at 05:00 AM
What advantages does the TMail Address class have over the RFC regexp shown in terms of validation? The format of email addresses hasn’t changed in years, and is unlikely to change for the forseeable future, so for me maintenance of the Regexp isn’t an issue.
The only thing I can see the regexp missing is that it doesn’t check the domain’s TLD to see if its one of the valid ones issued by ICANN.
May 12th, 2008 at 03:01 PM
Dan, I think the biggest thing is that you don’t have to maintain or keep your own RFC on it.
TMail handles some nasty email addresses that can trip up other regexs as it uses a parser to figure out what is good and bad.
You could use the RFC regex, I do on one ruby script where I don’t want to include TMail, but if you are using other mail functions of TMail, the free verification stuff in TMail works and works well.
May 12th, 2008 at 10:26 PM
Can Tmail operate behind Gmail? I want to be able to track all the email that the app sends by passing it through Gmail. If I do this, I get all the cool Gmailness that allows me to have conversations.
Thanks!
May 12th, 2008 at 10:38 PM
@James: Sure, TMail just handles the Raw email. You need to use something like Net::POP3 or Net::IMAP etc to get the email down, and then you can parse it with TMail.
Let me know how you go with it :)
Also, you can try the TMail Talk mailing list (go to the tmail.rubyforge.org website to find it). Bunch of hard cord TMail users there.
Mikel
May 16th, 2008 at 01:18 AM
What would be the best way to use TMail and also validate that the email address is just A-Za-z0-9+._- ?
Because TMail accepts accent chairs.
May 29th, 2008 at 09:43 PM
Hi,
Nice tip on using TMail, thanks Mikel.
Note you don’t need to wrap the rescue in a begin/end block. You can just do this:
def valid_email? TMail::Address.parse(email) rescue errors.add_to_base(“Must be a valid email”) end
Two lines fewer!
Cheers, Dave
May 29th, 2008 at 09:56 PM
Gah! Sorry, it’s eaten the linebreaks and I don’t know what formatting engine you’re using. Try this:
def valid_email?
end
June 20th, 2008 at 01:02 PM
nice tip, thanks!
June 27th, 2008 at 03:43 AM
I have tmail installed and have followed the instructions above and it seems to be working for detecting some invalid addresses, but not all. For instance it knows that ‘sdf sdf’ is an invalid email address, but ‘sdfsdf’ is passed through as valid.
Shouldn’t anything with out exactly 1 ’@’ and at least 1 ’.’ be rejected as invalid? Am I missing something?
Thanks.
July 14th, 2008 at 09:15 AM
Problem is that there are many things in the RFC that you specifically don’t want to accept as valid email addresses – such as local addresses (in fact ‘’ is valid by RFC822 – but certainly one of the most common things you want to exclude as a valid email address), invalid public domains (eg. _@._ is valid RFC822 but not something you want to accept as a valid email address), and silly things like ’”
"!.+’.Better to require valid addresses because of your business process (eg. by requiring the user to validate their email by clicking a link you send to their address) than to attempt to validate them with regex or against the very liberal RFC822.
July 14th, 2008 at 10:41 PM
@Jason – Good points.
I usually do both. I validate with TMail to make sure it has a chance of arriving at a mailbox and then send it to get the user to click on it.
The point is though that you can get some down right weird mail addresses out there – especially if you deal with non English email addresses…..
And I’d like to be able to at least send a note back to the user saying ‘hey, it looks like you mis typed your email address’ when they put a non quoted space in it, than say ‘thanks!’ and attempt to send it and have that fail due to the space.
Regards
Mikel
January 4th, 2009 at 07:56 AM
I’d like to see a method in the TMail::Address interface that provides validation without depending on exception handling.
January 22nd, 2009 at 12:08 AM
Your parse method allows emails with no @ ??
ie: abcdefg passes.
Is that expected?
February 1st, 2009 at 05:25 AM
Excellent point Travis. TMail::Address.parse just doesn’t work they way we want for validating email. Look at this: >> email = TMail::Address.parse(“Mikel Lindsaar <mikel>“) => #<tmail::address mikel>
February 3rd, 2009 at 04:04 PM
Yeah like Travis noted, why is ‘abcdefg’ considered a valid email address? I most certainly do not want users registering on my site with an email address of ‘abcdefg’.
February 3rd, 2009 at 04:29 PM
Also I’ve noticed that TMail approves email addresses like ‘user@domain’
February 25th, 2009 at 09:48 PM
I’m relatively new to Rails and am attempting to use TMail to validate email addresses. I’m having what the rudimentary problem of getting the TMail::Address.parse() method to parse the attribute I want it to. Was wondering if you could mercifully give me a quick pointer to get me rolling.
Here is my model:
require ‘tmail’
class Contact < ActiveRecord::Base validate :valid_email_address?
end
I have an attribute called :email_address – however, it doesn’t seem to be getting validated. Any pointers?
Thanks!
March 2nd, 2009 at 08:25 AM
Can you show me the way to validate url and show alert pop up for invalid url onclick submit button with ROR?
June 11th, 2009 at 08:43 PM
Totally useless as a validation tool! If it accepts email address without the @, then whats the point.