[quote user="Tim W Young"]I think that solved it![/quote]

Good to hear! 

You have posted in the Mercury support forum but reference a Pegasus Mail version number.  Perhaps you meant to post in the Pegasus Mail support forum?  It will be important to include reference to what tool you are using to detect spam.

Hi, I'm currently using Mercury with this scenario.

User11

       ======>Connect to ip1 instance1 Mercury (localdomain1) and all the outgoing mail it's send with MercC via Smart Relay Host with my provider (externaldomain1.com)

User12

 -------------------------------------------------------------------------------------------------------------------------------------------------------------------

User21

       ======>Connect to ip2 instance2 Mercury (localdomain2) and all the outgoing mail it's send with MercC via Smart Relay Host wtih my provider (externaldomain2.com)

User22

 -------------------------------------------------------------------------------------------------------------------------------------------------------------------

The problem is to connect email from User11 to User21 currently i use wSMTPEX

But I'm thinking in connect all the user to "NewInstance" of mercury and handle the users as locals.  The problem is howto "Re-Handle" to the correct queue in the previos instances

Example:  

    User11@localdomain1 send message to User21@localdomain2  with alias deliver to local recipient.

    User21@localdomain2 send message to User22@localdomain2 with alias deliver to local recipient.

Example How to:

     User11@localdomain1 send message to jhon@gmail.com how to transfer to  queue in ip1 instance1 Mercury and send it wiht MercC smart host relay1. (Not just forward to another recipient)

     User21@localdomain2 send message to jhon@gmail.com how to transfer to  queue in ip2 instance2 Mercury and send it wiht MercC smart host relay2. (Not just forward to another recipient)

It's possible?

Thank you very much

Roberto Navarro from Mexico

Since Mercury32 moved to using OpenSSL, I've never had any problem updating to the latest compatible version of OpenSSL.  I am currently using OpenSSL 1.0.2t released in 10-Sep-2019.
I just make sure I use a 32-bit build without external dependencies to the Microsoft Visual Studio Runtime DLLs, except for the system provided msvcrt.dll.
I don't build OpenSSL myself.  I download it from one of the Windows 32/64 precompiled binaries sites listed on the OpenSSL wiki.
Before I made the switch, a few years ago, I did verify that every function exported in the version that came with Mercury was available in the one I was switching too.
Now I just shut down Mercury, update the affected fields and restart.
Hoping that the next version of Mercury updates to use Open SSL 1.1.1 since 1.0.2 which was a LTS release is approaching EOL.

I file them automatically in a 'postmaster' folder, and only refer back to them if there's a query.

They're mostly bounces or mistyped addresses. 

Hi Jeff,

Sorry for late reply this works for me;

Begin
Name: Spamcop
Enabled: Y
QueryType: Blacklist
QueryForm: Address
Hostname: bl.spamcop.net
Strictness: Range 127.0.0.2 - 127.0.0.10
Action: Tag
Parameter: X-Blocked: Spamcop Rejected
End

I remember the Strictness took some tweaking.

I Tag all mine Then use the global spam to pull the tag that way if it blocks a gmail type server if the address is in my white list its honored rather than rejected.

Regards.

Mark.

Stephen: A download link is on its way to you!

Unfortunately I do.  I've requested access to the beta.  Thanks!

I'm posting this just to make a record of the fact that my POPFile has started crashing about once a week for the last couple of months after being rock solid for many years.  Spam starts showing up in mailboxes due to popfileib.exe not running.  There isn't any consistency in occurrence times; no event is logged that I can via Event Viewer. 

At first I thought someone was doing a reclassification and mistakenly hitting the "Shutdown POPFile" link but it has now crashed a couple of times in the middle of the night when the office was closed (it's not accessible remotely).  It runs on a Win7 PC that is dedicated to Mercury, POPFile, and online banking.  Vipre Enterprise is the AV product; IBM Trusteer Rapport is also as a requirement of online banking.  The machine is in a server room where it gets accessed twice a day for online banking and as needed for Windows and Firefox updates.  The POPFile crashes don't coincide with any of these times.  A cold boot hasn't solved the problem.

There is nothing to go on for troubleshooting, at least not that I can find.  Any thoughts are welcome.

Just to close the thread: The poster has discovered that the problem was that by mistake an old version of Mercury with an outdated SSL library had been installed.

A side affect of trying to understand the SmtpEvt daemon is that I now have a better understanding of the options in the MercuryS Compliance tab and of the potential value of transaction filtering as way to immediately blacklist an IP address that has been identified as repeated trying to gain access.  My "refuse" entries in Connection Control have been removed opting for transaction filtering rules instead. 

I've standardized the rules as per below with only the IP address changing but welcome suggestions on a better or more appropriate way of doing this. 

H, "*192.156.225.99*", BS, "554 Relaying not allowed - connection dropped" 

I'm anxious to see the effects of this change in conjunction with SmtpEvt.

From the command line, you can run the following commands to create firewall rules that ban all traffic to and from an address:

netsh advfirewall firewall add rule name="From 1.2.3.4" dir=in interface=any action=block remoteip=1.2.3.4/32
netsh advfirewall firewall add rule name="To 1.2.3.4" dir=out interface=any action=block remoteip=1.2.3.4/32

That would be a good option to check.

Another would be to see if the FQDN in a HELO resolves.

Wow!  You've done considerable work on this since 2014 when I last downloaded it.  I'm looking forward to digging into it. 

Thank you!

I have to admit that I have never used Pegasus Mail to set up an IMAP client. However, I assume the procedure is the same.

[quote user="GordonM"]

Thank you for the clarification. The fact that John from the UK was able to connect to Rogers' SMTP service presumably means that his ISP is not blocking port 25 connections from "foreign" sources. This is, perhaps, surprising these days.

Gordon 

[/quote]

Indeed - I'm with Zen Internet, and they do not block or otherwise interfere with anything. I have a /29 IP block which is fully configurable from my ISP dashboard, so I can create DNS records for my IP range without having to bother anyone at Zen.

John.

thanks!

How are you running Mercury - as an app or a service?

Also, I had an issue some time ago when it was on a multi-core processor and I had to tie it to 1 cpu.  See if that helps at all.  (I have to say this problem hasn't affected me for some years with the latest Mercury version.)

Not sure but maybe try  ~D

The manual says it is the date in proper RFC822 format