Announcement

Collapse
No announcement yet.

Relay issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Relay issue

    Hello

    I have sbs2003 & GFI.

    Today i've noticed that i cant send mail to a particular recipient.
    The error i'm getting is "SMTP Communication problem..."
    "5.5.0 smtp; 550 relay not permitted"

    I'm not listed in any RBL lists. (on those that i've checked).

    * Any idea what should be the problem ?
    * Any idea how can i debug or check that issue ?

    Thanks

  • #2
    Re: Relay issue

    One thing i've noticed now ..

    In the NDR message at the bottom my domain is mentioned, doesn't it be my mail server name ?

    There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
    <XXX.com #5.5.0 smtp;550 relay not permitted>

    It's not supposed to be servername.xxx.com ?

    Is that gives a clue about hte problem ?

    Thanks again

    Comment


    • #3
      Re: Relay issue

      The exchange server is doing a reverse lookup.
      http://support.microsoft.com/kb/297412
      [Powershell]
      Start-DayDream
      Set-Location Malibu Beach
      Get-Drink
      Lay-Back
      Start-Sleep
      ....
      Wake-Up!
      Resume-Service
      Write-Warning
      [/Powershell]

      BLOG: Therealshrimp.blogspot.com

      Comment


      • #4
        Re: Relay issue

        Sorry but i didn't understood your link relevance.

        Can you explain please ?

        Comment


        • #5
          Re: Relay issue

          In the NDR the servername is the name on the FQDN field in the SMTP virtual server. That will be set to server.domain.local by default (where domain.local is your internal Windows domain). All that error is showing is what server generated the NDR.
          If you have it set to server.domain.com but that name doesn't resolve on the internet - for example you are using mail.domain.com then you need to correct it. As already outlined you should have a matching reverse DNS record.

          However saying all of the above, if this is happening with one domain I would suspect that the problem is with the remote domain. Use some internet tools to test the remote domain and see if those show the same error.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: Relay issue

            OK

            I've tried to send that message with my private home account (connected through the same ISP) and ..... i've got the same NDR error regarding "relay not allowed".

            So i presume it's a probblem with our common ISP.

            I'll see if i can get some aswers from them tommorow.

            BTW - where can i check my DNS & Reverse DNS records published to the world ??

            TNX Again

            Comment


            • #7
              Re: Relay issue

              If you want to see your own records then use any one of the number of MX record and DNS lookup tools that are available on the internet. MXTOOLBOX is one I can think of immediately, but there are loads.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Relay issue

                There is a quick way around this. Depending on how your exchange is configured to relay mail, if your public IP address doesnt have a PTR record on a public DNS server then try re routing the email via a smarthost with a lower cost. Add the desired email address to the address space of the SMTP connector thats pointing to your ISP`s SMTP server and the email will be delivered. You can presume as a rule that most ISP`s mail servers are configured with a PTR record. If there not get a new ISP!!!

                If this doesnt work try sending it directly from your exchange using DNS but ensure you have a PTR record configured already. in order to do this you will require a static IP and your service provider to create a reverse record for your IP address.

                Comment

                Working...
                X