jscott1979
asked on
smtp and native Pop3 setup problems with exchange server 2003 500 POINTS.....
Helo experts,
I'm have just started a contract on a domain with 2 2003 DC's and a stand alone 2003 exchange server behind a sonic firewall.
Problem is that some one prior to me setup the mx record from their web domain host to point at the exchange server which caused 2 main problems.
1. They had many problems mostly due to ISP dropping connection and mail being redirected to the domain host mail servers. Therefore they had mail on the exchange and the mail host servers. I had the domain host to change the mx record back and currently have all the client setup via outlook pop3 mail.
2. I'm getting weird smtp errors in the App. log which I am going to post in a little bit when I get over there. It seems like they setup different smtp virtual servers and moved away from the MS defualt. I am not sure how to get rid of those and just use the MS defualt setup to route outgoing mail via DNS.
So to remedy situation 1 I install MapiLabs Native Pop3 connector on exchange box and setup a test client to try it out.
I'm not receiving any incoming mail and I know port 110 is open on the firewall because all the pop3 outlook client are recieving fine.
When I get there in about an hour I'm going to post the DNS error and the native pop3 log for review.
I'm have just started a contract on a domain with 2 2003 DC's and a stand alone 2003 exchange server behind a sonic firewall.
Problem is that some one prior to me setup the mx record from their web domain host to point at the exchange server which caused 2 main problems.
1. They had many problems mostly due to ISP dropping connection and mail being redirected to the domain host mail servers. Therefore they had mail on the exchange and the mail host servers. I had the domain host to change the mx record back and currently have all the client setup via outlook pop3 mail.
2. I'm getting weird smtp errors in the App. log which I am going to post in a little bit when I get over there. It seems like they setup different smtp virtual servers and moved away from the MS defualt. I am not sure how to get rid of those and just use the MS defualt setup to route outgoing mail via DNS.
So to remedy situation 1 I install MapiLabs Native Pop3 connector on exchange box and setup a test client to try it out.
I'm not receiving any incoming mail and I know port 110 is open on the firewall because all the pop3 outlook client are recieving fine.
When I get there in about an hour I'm going to post the DNS error and the native pop3 log for review.
ASKER
The outgoing mail is not working. How do I check if the smtp virtual server is configured correctly?
ASKER
Is there no expert out there that can help? I guess I'm waisting my money on this site......I have this question and anther open hear in exchange and have recieved little help.
Should I be posting this question somewhere else or what?
Should I be posting this question somewhere else or what?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry guys, I know you are volunteers but I had another question posted in exchange with no comments for weeks and usually they are cleared up in days and was feeling kind of forgotten.
I set up the smtp connector how it describes to through the link Sembee and setup the smart host to point at the IP of their web host company mail server.
Everything seems to be working fine..........1 more question though
Do I need the Virtual SMTP server under->protocols->SMTP to be running?
It seems to me that is not needed when you use the SMTP connector.
What do you guys think, should I leave it alone or can I stop it?
I set up the smtp connector how it describes to through the link Sembee and setup the smart host to point at the IP of their web host company mail server.
Everything seems to be working fine..........1 more question though
Do I need the Virtual SMTP server under->protocols->SMTP to be running?
It seems to me that is not needed when you use the SMTP connector.
What do you guys think, should I leave it alone or can I stop it?
The SMTP Connector is NOT a replacement for the SMTP Virtual Server. You have to leave the Default SMTP Virtual Server in place as it is used by the SMTP Connector.
Why would you want to stop it? What makes you think that it isn't used?
Simon.
Why would you want to stop it? What makes you think that it isn't used?
Simon.
If you are not sending mail, or don't have multiple servers in your environment, then no, it is not needed. I had a client that disabled theirs to prevent all internet mail from routing (it's a long story, but it had to do with attachments). Ultimately I convinced them to let it run and simply deny port 25 at their firewall. With more than 1 server, or to send messages to the internet, you need it.
In your case, the SMTP Connector uses the Default Virtual SMTP server as its, well, Default SMTP Virtual server.
Not to be rude...but you may want to dig into the guts of Exchange. This is a link with some great, and free, information:
Http://www.microsoft.com/exchange/library
In your case, the SMTP Connector uses the Default Virtual SMTP server as its, well, Default SMTP Virtual server.
Not to be rude...but you may want to dig into the guts of Exchange. This is a link with some great, and free, information:
Http://www.microsoft.com/exchange/library
ASKER
Source: MSExchangeTransport
Category: SMTP Protocol
Event ID: 7002
This is an SMTP protocol warning log for virtual server ID 1, connection #68. The remote host "65.89.139.10", responded to the SMTP command "rcpt" with "450 4.7.1 <oem-sales@cablestogo.com>
and
Source: MSExchangeTransport
Category: SMTP Protocol
Event ID: 7004
This is an SMTP protocol error log for virtual server ID 1, connection #62. The remote host "66.194.158.200", responded to the SMTP command "xexch50" with "504 Need to authenticate first ". The full command sent was "XEXCH50 2488 3 ". This will probably cause the connection to fail.
Whats causing this?