SMTP and POP3 issue after changed webmail vendor

[ntm]

Hi

FYI, we just changed our webmail vendor and our smtp and pop3 server settings have been changed to new seetings. As such, we have changed the settings accordingly at clients site. Below are the issues that we 're facing.

[1]. Why most of the users cant send or recieve when their smtp & pop3 server name is set as host name like smtp = smtp.company1.com,
pop3 = mail.company1.com, if set server name based on IP then go throught smoothly.

[2]. Another issue is previous webmail address set as (example) http://mail.company1.com and after the changed process, it's still http://mail.company1.com but with different IP. Our users tried to access webmail service by type in the http://mail.company1.com but system routed them to the old webmail address.

Thus, I would like to know is there any settings that we need to add or change in wingate ?

Urgently need the solution as now most of the users cant send or receive mail.

Thanks in advance.

[adrien]

This sounds like a DNS configuration issue with the domain.

Who is hosting your DNS records? You will need to contact them to have them update the records for pop3.xx and smtp.xx to point to the correct new IP addresses.

Adrien

[ntm]

Hi Adrien,

Our vendor already done this part. As we tested the connection through VPN or connection that not direct connect through wingate to get out, smtp and pop3 work fine. Once connected through wingate, all the mail with smtp and pop3 configured with host name will have problem to receive and send.

[adrien]

OK

That makes me think that either

a) WinGate DNS resolver has cached the old IP addresses - either restart WinGate, or flush the DNS cache
b) WInGate is configured to use a DNS server that still has cached records of the old IPs. Check your DNS resolver settings and DNS settings on the adapters in the WinGate machine to make sure they are pointing to the correct DNS server.

Regards

Adrien

[ntm]

Hi

We have restarted the wingate and flushed out the dns cache but smtp and mail host name yet to be used. We also found out that some of the clients able to use host name instead of IP to send/receive. This really puzzled us.

We have routed clients connect to our windows 2003 server's dns through wingate dns/wins resolver but situation stil unchange.

What else should we do now ?

Thanks.

[adrien]

on a client that doesn't work, try running nslookup to search for the DNS config problem.

who did the changeover? Can you ask them to help?

[ntm]

ok..thanks.