Pegasus Mail & Mercury

We recently upgraded to Mercury 4.72 and Windows 2008 R2 on 32 bit architecture. Occasionally , under high volumes our Mercury mail Queue is failing to process correctly. The Mercury service seems to be CPU bound, consuming 12%CPU on a Quad CPU for hours. No email is delivered. A restart of  the service un-hangs it and the queue is quickly ...

Thanks for your tipps. I have found the error and it was in the MercuryS setup where I had the localhost IP 127.0.0.1 instead of ASUS desktop IP 192.168.178.28 as IP interface to use! Now I can receive the test message and hopefully also the status messages from my Linkstation without any additional changes on port settings or opening ports in ...

Other than the Windows networking properties, Is there any way to specify the DNS servers that MercuryS uses, in particular for checking the RBLs listed in the Spam Control?  I have three DNS servers listed in the Windows networking properties, and the third one has problems with RBLs, such that MercuryS times out for any good RBL ...

hi all I am wondering if anyone had any idea or pointers for me  I have mercury/32 and after spending some time setting up it worked fine, I can send mail normally but I can not receive mail only locally. If you have any clue as to where i should look first or any idea as to what the problem may be please let me know.  I've got a ...

Hi Folks Today we received some spam which came in from an address that is in a banned range. MercuryS SMTP Server's connection control is set up so that 0.0.0.0 to 255.255.255.255 is refused. The only address ranges allowed are those which are used by MessageLabs and a single address for a separate domain. None of the allowed address ranges ...

Peter Strömblad:I'm having a hard time following your question. Is it IMAP that doesn't work? If so, try enabling session logging in MercuryI, and see what goes wrong from one of your client computers. If you see no activity at all, I'd say you have a firewall problem with your 2008 server, not allowing connections over TCP port 143 to Mercury, ...

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 ...

Can't connect to 213.180.114.52 on port 25: Timed out   Firewall?  TCP port 25 incoming needs to be opened.  Check your router.  Check your software firewall configuration.  In the Windows firewall, allow mercury.exe.   Tip: if you only have one mail server, it is easy to do away with a large volume of ...

Greenman:   I don't understand how Mercury was able to accept the mail from 61.145.143.171 when it is outside the allowed range of IP addresses. Am I missing something here? Is there any further configuration I need to carry out to ensure that Mercury only accepts SMTP connections from the allowed ranges?   It's not clear ...

Hi Folks I have a question about SMTP mail from allowed IP ranges. All mail we receive goes through MessageLabs. This means that all email has a banner inserted at the end of the message stating it has been scanned by MessageLabs. Today we received an email which was classified as spam, and which did not include the banner. The MercuryS log ...