On 15/05/2014 1:00 PM, Russell Coker wrote:
On Thu, 15 May 2014 11:57:02 Nic Baxter wrote:
3. Able to authenticate as above if using ip number instead, which makes sense, since in office wifi and mail server on same subnet (192.168.1.X)
Hi Daniel I suggest this is not an issue with the server but with the client. My suggestion would be to ping the mail server using the domain name and see if it resolves. It might also be a good idea to run ipconfig /flushdns
It sounds like the DNS has the external IP address and the routers aren't setup to allow connections to the external address from inside the organisation.
Using the Windows machine, see what returns for the MX lookup, check the A record. Try pinging the A record. If you are using port 25, it might be hijacked or blocked. I use SSL connections and go with IMAP on ports 465 for SMTPS and 993 for IMAPS. So long as the office firewall and the ISP is not blocking ports, you should be fine. Given that this is a recent issue, perhaps a change in firewall or ISP is the difference.
The best thing to do is to configure NAT on a router to redirect the external IP to the internal IP. It will be tempting to have separate internal and external views in the DNS, but don't do that, it causes lots of pain in the long term.
If you want a public mail server and it doesn't /own/ it's public IP address, then, yes you will need Nat and port forwarding. I don't think having internal/external DNS views should be an issue.... Cheers A.