Pegasus Mail & Mercury

Thanks, Thomas. I do not think it is a firewall or DNS problem as MS-Office Outlook 2003 is able to connect to the account from the same machine. I can also ping all forms of the address, including the real POP3 server addresses you quote above. Cheers!

I think it's worth mentioning that Mercury doesn't include the reverse-DNS of the connecting host in the Received: lines it generates, only the client greeting.  That's often forged, so depending upon it is inadvisable, although it might work (as might just checking for the presence or absence of DKIM-Signature: lines on mails you know ought ...

Vague... Sorry. 503C charity has been using Merc for several years. I have just started as their IT and have used the Mercury interface and like it. WHAT I want to do: Currently use a 'mail forwarding/filtering' company that I'm not happy with... they provide about ten IP addresses which I've entered into Mercury as ''allowable'' PrimMX ...

Peter Strömblad:...this is dependent on what dns call is being used from mercury - you can programmatically call dns like: DNS_QUERY_NO_HOSTS_FILE - but I don't know which windows call David uses... Hopefully if it is coded to not use the hosts file then it can easily be changed to use the hosts file. Peter Strömblad:There are also angry ...

It appears that the MecuryE SMTP Client bypasses the local host table when resolving the IP address for MX records.  It is only using the IP address from a DNS lookup of the URL obtained from the MX records. I have two different email servers on my internal network, Mercury and another one.  When a user on a domain on the other ...

There is absolutely no necessity to get complicated. The more complicated the solution, the more difficult it is to implement. And few of the ''anti-spam technologies'' tackle the problem where it occurs, which is actually where it must be tackled. Once it gets past the SMTP layer, i.e. at the mail clients, all the ''anti-spam technologies'' are ...

Start by clearing your resolver-cache. (enter the dns-mmc, and clear the server cache). Then retry nslookup - if the answer is the same, turn on full logging of your dns-server - so that you can trace what is going on with your specific query. If your server relays the dns query off-host, and the answer is wrong, and you have set up a special ...