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

Posted on 2005-03-21
Medium Priority
Last Modified: 2008-01-09
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?
Question by:RBECKMN
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 104

Accepted Solution

Sembee earned 1000 total points
ID: 13663373
I think you need to look at your Watchguard. While I was researching another issue I found a number of people reporting that this is caused by an SMTP filter on the Watchguard. If that feature is enabled, turn it off (can't tell you exactly what it is called as I don't have a Watchguard to refer to).


Author Comment

ID: 13672634
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.

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question