Announcement

Collapse
No announcement yet.

Second SMTP VS to ISP

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

  • Second SMTP VS to ISP

    Here is the issue I am experiencing, I have two exchange 2k3 servers at two different sites with a slow wan link between them. They have been connected with a route group connector and there is an SMTP connector at site A for internet mail through the ISP smarthost. Recently the ISP changed from port 25 to 587 so I need to change my config to get mail flowing out again. I created a second SMTP virtual server on the exchange box at site A and set it up to send out to port 587 and then I changed the SMTP connector to only use that new virtual server local bridgehead but when I send a message they get stuck in a queue with the name of the SMTP connector and a source of the default SMTP VS, NOT the one I selected as the local bridgehead. Am I missing something to have inter route group traffic over port 25, inbound internet traffic on port 25 and outbound internet traffic on port 587?

  • #2
    Re: Second SMTP VS to ISP

    Try swapping them round.

    However part of the problem is that controlling which VS Exchange will use is almost impossible. The selection of virtual server in the SMTP connector is really just telling Exchange which physical server to use. All Exchange does is ask IIS for an SMTP connection, it doesn't say which one it will use.

    If you want to be really picky you could tell your ISP that port 587 is now depreciated and SSL over SMTP is supported on port 25.

    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


    • #3
      Re: Second SMTP VS to ISP

      Is there a better design I could implement for this implementation?

      Comment


      • #4
        Re: Second SMTP VS to ISP

        Any reason why you cannot use direct delivery instead of a smart host?

        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


        • #5
          Re: Second SMTP VS to ISP

          Cause my lovely ISP (the only affordable one in the area) blocks port 25. The other option I was thinking of today was to configure a mail relay box and configure it as the smarthost in exchange and then have it send out to the ISP smarthost. This means one more box to maintain and seems kind of a clunky solution. Does that seem like a viable solution? I was thinking a small sendmail build but I am even sure if it will work, I need to research more. Any sugestions?

          Comment


          • #6
            Re: Second SMTP VS to ISP

            They probably will allow port 25, but you will have to pay double the cost for a "business class" connection.

            This is where a frontend server would be ideal. The inter-server traffic would go direct, but the frontend server could be configured to send email on the second port.

            Another option, as you say, would be another server that can do port translation for you.

            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

            Working...
            X