Re-Post: 550 - Sender Not Allowed

From: Dave Woolley (dvwool_at_ix.netcom.com)
Date: 08/19/04

  • Next message: Dave Woolley: "Re-post: SMTP 550 - Sender not allowed" 
    Date: 18 Aug 2004 17:15:09 -0700

    I posted this back on 6/17/04 but didn't get any response... still
    experiencing the problem... does anyone have any thoughts?...

    Hello,

    I'm trying to figure out a sporadic e-mail problem that has been
    occurring for us for a few months now. Here's our setup...

    - one Exchange 2000 server
    - single AD domain environment
    - e-mail routed through Internet T1 by default
    - Exchange is configured to route e-mail to some specific domains
    through a backend T1... a partner has a WorldSecure server that acts
    as a mail hub for all of those domains.

    About 25% of the time, sending e-mail to one of the "specially-routed"
    domains results in the undeliverable message at the end of my post.
    I've done some testing and the problem doesn't seem to be related to
    time of day, content, or length of message. In researching newsgroup
    postings, I read about reverse DNS being a possible issue, but I'm
    sure that reverse DNS is set up properly for us.

    Something that dawned on me... the partner that acts as the mail hub
    switched us from a frame relay to a T1-VPN around the time that the
    problems started occurring... is it possible that it's a problem with
    the access list on their new router or something like that?

    Any thoughts would be much appreciated.
    Thanks!
    -Dave

    ===================================================================
    Your message did not reach some or all of the intended recipients.

          Subject: Test
          Sent: 6/10/2004 12:49 PM

    The following recipient(s) could not be reached:

          'user@otherdomain.com' on 6/10/2004 12:49 PM
                There was a SMTP communication problem with the
    recipient's email server. Please contact your system administrator.
                <mailserver.mydomain.com #5.5.0 smtp;550 Requested action
    not taken - Sender not allowed>
    ===================================================================

  • Next message: Dave Woolley: "Re-post: SMTP 550 - Sender not allowed"

    Relevant Pages

    • Re: Re-post: SMTP 550 - Sender not allowed
      ... a partner has a WorldSecure server that acts ... > as a mail hub for all of those domains. ... > postings, I read about reverse DNS being a possible issue, but I'm ...
      (microsoft.public.exchange2000.protocols)
    • Re-post: SMTP 550 - Sender not allowed
      ... a partner has a WorldSecure server that acts ... as a mail hub for all of those domains. ... postings, I read about reverse DNS being a possible issue, but I'm ...
      (microsoft.public.exchange2000.protocols)
    • SMTP 550 - Sender not allowed
      ... Exchange is configured to route e-mail to some specific domains ... a partner has a WorldSecure server that acts ... as a mail hub for all of those domains. ... postings, I read about reverse DNS being a possible issue, but I'm ...
      (microsoft.public.exchange2000.protocols)
    • Re: Comcast Email Problems
      ... Our ISP needs to have reverse dns entries ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... Please run command "ipconfig /all" on the server ...
      (microsoft.public.windows.server.sbs)
    • Re: Cannot email to Gmail accounts
      ... All looks well, and yeah, the headers still had google's rdns resolving to smtp.robertsonmfg.com so the rDNS change you requested had not propogated to google's cached version. ... And because google used the cached lookup and the email wasn't rejected, it doesn't explain why it worked for my acocunt and not your other gmail accounts. ... The problem does not seem to be your server in any way. ... Regarding the answer to your reverse DNS question, no, ...
      (microsoft.public.windows.server.sbs)