<div>
I thought I had adjusted the SMPT filter on the firewall, but I forgot to write the configuration change back to the firewall, so it was still set at the default, which does excludes apostrophes, quotes, and several other characters.
</div>


I thought I had adjusted the SMPT filter on the firewall, but I forgot to write the configuration change back to the firewall, so it was still set at the default, which does excludes apostrophes, quotes, and several other characters.

<div>
<div class="content wysiwyg-content">
I have the same problem as several others who have reported this problem. &nbsp;An outside sender cannot send to us, and this sender has an apostrophe in their email address .. I'm running Exchange 2000 under W2K with a Watchguard FB1000. &nbsp;All of our email goes to an outside service that supplies spam filtering; anything not filtered out is passed through to our firewall. &nbsp;The firewall is set to use SMTP proxy for incoming, and I've set that to allow apostrophes. &nbsp;The spam service reports the 553 message to the outside sender, and reports that it came from our server. &nbsp;In other words, the spam service is not trapping these emails. It looks like Exchange is rejecting them, not the firewall. &nbsp;An earlier response to someone who had this problem with Exchange 5.5 suggested upgrading to Exchange 2000, but I have the same problem. &nbsp;Is there a setting in Exchange that I've missed?
</div>
</div>


I have the same problem as several others who have reported this problem.  An outside sender cannot send to us, and this sender has an apostrophe in their email address .. I'm running Exchange 2000 under W2K with a Watchguard FB1000.  All of our email goes to an outside service that supplies spam filtering; anything not filtered out is passed through to our firewall.  The firewall is set to use SMTP proxy for incoming, and I've set that to allow apostrophes.  The spam service reports the 553 message to the outside sender, and reports that it came from our server.  In other words, the spam service is not trapping these emails. It looks like Exchange is rejecting them, not the firewall.  An earlier response to someone who had this problem with Exchange 5.5 suggested upgrading to Exchange 2000, but I have the same problem.  Is there a setting in Exchange that I've missed?

Apostrophes result in Error 553: mailbox name not allowed or chunk too large

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.