There are issues if the fairly old SSL libraries in Mercury 4.74 and earlier if used together with clients that follow newer SSL standards. For that reason v4.80 of Mercury, that is in release candidate state at the moment, will switch to use OpenSSL.

paul- thank you.

Rolf, I am using xampp control panel 1.8.1  Mercury is one of component in xampp package.  I do not understand third-party tool-xampp?. thank you

Hi Rolf

Thanks for the info, that explains that. Will wait for the update before using the service.

Rolf, I see. I think that I am going to keep it as default. It is good to know that there is no bug here. thank you! have a great day! 

If a client isn't allowed to establish a connection to the server it won't even be able to try to authenticate. To prevent unwanted relaying I would suggest checking both "Use strict local relaying restrictions" and "Authenticated SMTP Connections may relay mail" to have all clients connecting from a mobile device or otherwise from a not trusted IP address authenticate. If you want users on your trusted IP ranges to be able to send mail without authenticating you can check "Connections from this address range may relay mail through this server" for each trusted range.

[quote user="bryroller"]

Sounds like a viable option because (I believe) there is much less administration than I currently have to do and it is free. Change my MX records and it should start working - sounds similar to Postini, et al.

I currently use transaction filters, content filters, blacklisting, DNSBLs, SpamHalter, ClamWall (with optional spam definitions) and my Mercury/32 system processes 69,000+ messages daily. Keeping on top of the spammers is still difficult. I cannot block delivery from any part of the world (I add that because I am sure someone will offer that as a "solution"). GrayWall has caused me some issues due to form messages (PHP, etc.) not being able to "retry" delivery so I have it turned off.

Very interested in any opinions or alternatives anyone has to offer.

[/quote]

Like you I have turned GrayWall off and that appears to have made little difference - my spam levels remain very low.  DNSBL & transaction filters stop the majority from even entering the server, and ClamWall & SpamHalter stop most of those that are accepted.  I don't bother with content filters.

I have not used MX Guarddog but it seems a novel way to provide a free solution.

Oalf, thank you!

 I checked the three options under "compliance" tab.

1) limited maximum number of failed RCPTS to 4  

2) require clients to use an ESMTP size declaration.

3) Refuse messages that have not "date" field.

Thank you for helping!!!

To be able to use MercuryS to receive mail you will first need to verify that your ISP allows access to port 25 (SMTP). If this is the case you will then need to point the MX record for your domain to the public address of your mail server. The MX record is expected to contain a hostname (like mail.mydomain.com), not a numerical IP address.

[quote user="bfluet"][quote user="PaulW"]Usually STARTTLS is offered by a server to a connecting client.  If the client doesn't want to use it, it can ignore it and just use plain text.  Do you know how Printboss uses the mailserver - in, out, or both?[/quote]

Print Boss is primarily a Quickbooks check printing app but has the capability to email and fax documents from other apps.  From what I can determine, it only sends documents.[/quote]

OK, but the info you quote from Wellspring Software is puzzling as STARTTLS is nothing to do with authentication or authorisation.  I'm guessing that what they mean is that Print Boss can't authenticate to a relay server (MercuryS config / Connection control - Relaying control, last 2 checkboxes).   You will have to allow relaying through the IP address in the top part of that tab.

Rolf, I see. thank you for helps!!!

I don't think there is any option for this, Mercury will always minimize to system tray.

Hallo Rolf,

have to answer myself, because I should have known, there's a logical error:

[quote user="FJR"]If header "S" contains "Bounced Message (Was:" Copy "Postmaster@mydomain.de"[/quote]

"Copy" is only to local users ... so should be one of these:

• If header "S" contains "Bounced Message (Was:" Forward "Postmaster@mydomain.de"
• If header "S" contains "Bounced Message (Was:" Copy "admin"

The last one got the price [:)]

Thanks

    Olaf

I get these addresses as the 3 first mail handlers for gmail.com:

A-record for gmail-smtp-in.l.google.com:    IP address = 173.194.71.27

A-record for alt1.gmail-smtp-in.l.google.com:    IP address = 173.194.64.27

A-record for alt2.gmail-smtp-in.l.google.com:    IP address = 74.125.193.27 

Maybe one of your name servers has some old records cached that aren't valid any more? 

I have exactly the same problem, but not with GMail but one customer. We do not get mails from our customer (and that is very naughty).

As I have seen it will be fixed in Release 4.80. What can I do in the meantime?

Thank you in advance

Chris

A filter rule to catch the hotmail replies and MOVE the msg to the user folder will not trigger the FORWARD file.

Thank you.  I will try turning on the Session Logging and looking there.

The working solution

... FORWARD "spam%nb"

That was it.

In the Mercury D configuration the POP3 account information is set up with a default user set to junk. Which I am assuming anything that comes in that is not addressed to a local user then gets sent to the default user.

Thanks for all you help, Ron

Hi Rolf,

Yes did the trick for at least my testmessages. Will see how it holds for real mailing list stuff but if your analysis is 100% correct it should also solve it for those.

Tnx a lot, and happy 2014,

<Erik>

Thanks for all your help. The "Accept mail for invalid local addresses" is unchecked and after testing a second time does seem to be working. Not sure why my first test didn't get the failure notification but the second test did get the expected "Delivery failure notification" message.