Pegasus Mail & Mercury

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

We are currently having an issue with our Mercury/32 Server where it seems to forget about NDS users at random while accepting mail via MercuryS.  We have a Netware 6.5 SP5 Server where user's home directories are.  Local Domains looks like: LMC.PCB         merc.pbu.edu LMC.PCB      ...

Ben, most likely you're suffering a reverse lookup problem. To my knowledge, both Google and Microsoft require valid reverse lookups as to accept inbound e-mails. As stated above, youre HELO or EHLO needs to match your actual sending IP that in turn resolves when doing a reverse lookup. Check up on your own host and mailer, to see how it complies ...