Tip

Beware of firewalls that block Exchange Server's SMTP/POP3 communications

Many proxies and firewalls are sensitive to SMTP and POP3 conversations because of the potential for a buffer

    Requires Free Membership to View

overflow or denial of service (DoS) attack.

In fact, at least one attack using a proprietary Exchange Server verb has already been enumerated.

That said, it doesn't make sense to block all the custom Exchange Server verbs that are used in this context, since that can break needed functionality.

Exchange Server uses three proprietary verbs: X-EXPS, X-LINK2STATE and XEXCH50. None of these Exchange Server verbs are as well-documented as they could be, and they are often blocked by firewalls or proxies that aggressively manage SMTP/POP3 traffic.

When this happens, a number of symptoms can manifest:

  • Exchange servers can't authenticate each other.

  • Seemingly commonplace commands are responded to with the 500 Unrecognized command error or one of its analogues.

  • Normal commands produce completely unexpected responses.

One of the most common offenders creating these issues is the Cisco's PIX firewall software, specifically their Mailguard feature. Since it allows only seven basic SMTP commands and no custom Exchange Server verbs to travel in either direction, it has been implicated in creating numerous problems with Exchange server communications. Symantec's Raptor Firewall has also been a culprit.

In short, any firewall or proxy that screens SMTP/POP3 verbs needs to be given a careful once-over when used with Exchange Server.

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter.

Do you have comments on this tip? Let us know.

Related information from SearchExchange.com:

  • Expert Advice: Cisco PIX firewall causing Exchange connectivity problems
  • Tip: Firewall policies and SMTP line lengths
  • Tip: How HTTP verbs can 'hang' Outlook Web Access
  • Reference Center: Exchange Server firewall tips and resources

    Please let others know how useful this tip was via the rating scale below. Do you have a useful Exchange Server or Microsoft Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a nifty thank-you gift.

    This was first published in October 2006

  • There are Comments. Add yours.

     
    TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

    REGISTER or login:

    Forgot Password?
    By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
    Sort by: OldestNewest

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.