Hi, I've also tried turning Windows firewall off and turning my router firewall off. And I've confirmed that my ISP does not block email servers from resolving MX lists. Any idea why nslookup can resolve MX addresses through DNS addresses 8.8.8.8 and 208.201.224.11 while Mailenable generates this er...

Hi, nslookup successfully resolves MX addresses through 8.8.8.8 as wells a my ISP's DNS address 208.201.224.11. I've tried both in SMTP Properties/General/DNS address(es), and I receive the same error: Error (9005): Could not resolve MX list for domain [mailenable.com] Thanks for your help. nslookup...

Thanks. Under SMTP Properties\General\DNS address(es) I've tried: local host IP address, router IP address, 8.8.8.8 8.8.4.4, blank, and four IP addresses for my domain host Within CMD on the local host nslookup, set type = mx returns 5 mail exchanger servers by name (not IP address) for example.com....

Thanks. I've tried these values in the DNS address(es) field under SMTP Properites/General: local PC IP address, blank, 8.8.8.8 8.8.4.4 (suggested above), four IP addresses for mydomain host (mxtoolbox.com originally resolved mydomain.com to these IP addresses, but now resolves to local PC IP addres...

My ISP now says port 25 is only blocked for outbound traffic and is not blocked for inbound traffic, which is the third answer their tech support has provided to this one question. Should mailenable use port 587 for outbound traffic if "Listen on alternate port" is checked in SMTP "Port Settings" an...

Hello, I'm attempting to setup a simple MailEnable server on a dedicated Windows 7 Pro PC. What is the workaround if port 25 inbound is blocked by my ISP? What is the workaround if port 25 outbound is blocked by my ISP? Is there anything I can say to my ISP that will convince them to unblock port 25...