Pegasus Mail & Mercury

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

oaneadp: I’ve been doing some testing, when “Authenticated SMTP connections may relay mail” is checked, the setting of “Do not permit SMTP relaying of non-local mail” seems to become irrelevant; because regardless of its state - as long as I authenticate whilst sending a mail, I can send make the “FROM:” header anything, for example ...

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

MercuryS SMTP Server MercuryP POP3 Server MercuryC SMTP Client MercuryI IMAP Server  I have been in contact with our ISP since setting refuse email to invalid local addresses to off again and they have admitted that they think the problem was at their end and said that the Queue on their server is clear. That said this morning Mercury ...

I'm starting to see an increasing amount of spam get through where the MAIL FROM on the header is a valid local user (usually the same as the RCPT TO).  But the from address within the DATA portion is a different address.  Since the MAIL FROM is a valid local user, I cannot add it to the killfile.  Is it possible to reject these ...

After creating new users, they are getting a login dialog box when trying to set up their email client and subsequently when trying to retrieve email. Their mailbox folder \Mercury\Mail\username has the PASSWD.PM file in it and I have verified I am using the correct password and username. I can send an email to them and it ends up in this folder ...