Note that this problem does not refer to an apostrophe used in the friendly name field for an e-mail address, but the e-mail address itself. For instance, a TO: field in an e-mail that reads:
To: Phil L'Honor [email@example.com]
would be okay.
But, the following would not:
To: Phil L'Honor [firstname.lastname@example.org]
Older e-mail servers that are not entirely compliant with RFC821 (the Internet standard for SMTP messages) will experience this problem more often. In other words, Exchange 2000 or 2003 may not have a problem with an apostrophe character, but another remote host might.
Sometimes the problem does not lie with the e-mail server per se, but with the firewall. Many firewalls are programmed to intelligently parse traffic on certain ports (such as port 80, 25 or 110). Upon seeing the apostrophe character as part of the e-mail address, the firewall may reject it as being non-RFC821 compliant.
If you are having trouble receiving e-mail from a third party that has an apostrophe in the e-mail address, there are a few options on how to handle this. One is to disable the firewall rule that governs RFC821 formatting (if it's available, and
As a general rule, make sure that no e-mail addresses in your own organization contain an apostrophe. One quick way to find out if any of them do would be to export a list to a CSV file and search it, then make changes as needed.
Serdar Yegulalp is the editor of the Windows 2000 Power Users Newsletter.
Do you have a useful Exchange tip to share? Submit it to our monthly tip contest and you could win a prize and a spot in our Hall of Fame.
This was first published in September 2004