connection issues



We are still having this issue for the PTR record, where our incoming and
outgoing email goes out from different mail connector
to recap the issue, we have two Exchange (v2000, sp3) mail SMTP connectors
setup, one is the default SMTP connector, and the other one setup to route
mail into a IPSec tunnel we have with one of our client which only suppose
to handle emails (should be both incoming and outgoing in this case) with
that specific client domain name

Recently for the past 3-4 months we been getting report that our people
having problem sending to any AOL and now HOTMAIL accounts, but we receiving
from AOL accounts ok

I contacted AOL's postmaster, they have me sent a test email to their mx
test email address, and I got a replied finding out that we are getting
incoming mail from one IP address (mail.mycmpany.com <--> 2xx.1xx.2xx.83)
and sending mail out from the tunnel (2xx.1xx.2xx.85), thus the reverse DNS
for the outbound mail does not match to the mail.mycompany.com, looks like
AOL has recently setup their mail receiver to lookup reverse DNS

Per our last conversation, I will do the following resolve our issue above

1.. Create a new IP address on the Exchange server box itself so it uses
two different IP addresses (internally)
2.. In the Exchange system manager create a new virtual server that points
to this new IP address in step 1,
3.. Pointing the connector we created for our partner to this new virtual
server as its local bridgehead
4.. Start the VS (virtual server)
In the existing VS (default) we have set the specific IP to access the VS,
that includes several of our client's IP addresses for their mail server as
well as our Barracuda, should I move the client's IP addresses to this new
VS's access list and leave only the Barracuda address in the default VS ?

go back to the question I had about PTR, say if we successfully forced the
emails from/to that specific domain name into this VS/connector pair we just
create, do we still need a generic PTR like partner1.mycompany.com for this
tunnel ?




.



Relevant Pages

  • PTR record issues
    ... setup, one is the default SMTP connector, and the other one setup to route ... In the Exchange system manager create a new virtual server that points ... go back to the question I had about PTR, say if we successfully forced the ...
    (microsoft.public.exchange2000.connectivity)
  • AOL issues
    ... setup, one is the default SMTP connector, and the other one setup to route ... In the Exchange system manager create a new virtual server that points ... go back to the question I had about PTR, say if we successfully forced the ...
    (microsoft.public.exchange2000.connectivity)
  • Re: Two SBS exchange servers one Internet Domain
    ... You could also setup a Windows 2003 Terminal at Corporate ... DNS points to this server to send emails. ... > I setup a POP3 connector with these users pointing them to my corporate ...
    (microsoft.public.exchange.admin)
  • Two SBS exchange servers one Internet Domain
    ... Corporate server: I have exchange setup with all the users from both ... DNS points to this server to send emails. ... I setup a POP3 connector with these users pointing them to my corporate ...
    (microsoft.public.exchange.admin)
  • Two small business 2k3 servers one domain
    ... Corporate server: I have exchange setup with all the users from both ... DNS points to this server to send emails. ... I setup a POP3 connector with these users pointing them to my corporate ...
    (microsoft.public.exchange.connectivity)