There is lazy HTML detection in Mercury content control, though, and there is a whitelist function there as well.

/Rolf 

Thanks Thomas for your quick reply.

You were right about the files being locked. I've couldn't identify which process locked it. But I tried rebooting the Mercury server and it didn't help. I then rebooted the Netware server containing the user PMAIL folders (after requesting all users to shutdown their pc's), and that did the trick.

On behalf of my clients many thanks...

As for the other two fields (Sender: and X-Envelope-To:), neither

are in the headers section. It might help if I clarified that I'm using

Mercury's POP3 D connector for retrieval on these accounts, not SMTP.

Should not make any difference unless you are delivering directly to a users mailbox instead of allowing Mercury core to do this.  

As for 4.01b, I just noticed the new version of Mercury and I have

put upgrading on my todo list. Will the new version install on top of

the old and maintain configurations or will it need to be a clean

uninstall/reinstall with a manual reconfiguration of all options?

Just install as an upgrade over the current setup.  Have to shut down Mercury while you do the upgrade but other than that it should take seconds to do.

 

[quote user="caraudiovideo"]Thanks, that is leading me in the right direction. Would it be easier for me to simply set up multiple instances of Mercury? I only have 1 external IP and can only forward traffic to one internal IP.

instance1: domain1.com on ip 192.168.1.2

instance2: domain2.com on ip 192.168.1.2[/quote]

Multiple instances of Mercury is required but the servers should be running on different ports if all are on the same system.  One of the servers would be the gateway server and puts mail into domain mailboxes for the domains not served on the system.  The other systems would get the mail via SMTP to the different SMTP ports (i.e. 8025, 2525, 1025, etc) using WSMTPEx.exe or pulled from the gateway system via MercuryD.  I like the push via WSMTPEx but the pull via MercuryD works as well as long as you use the X-Envelope-To: header for mail delivery.

Really strange, you do not have over half of the sections in the normal mercury.ini file.  Try just adding the following to this file and see what happens.

[MercuryC]
Host :
Failfile : C:\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : C:\MERCURY\Mercury
ReturnLines : 15
Timeout : 300
ESMTP : 1
Server_Port : 587
SMTP_Username:
SMTP_Password:
SMTP_ConnFlags : 4
POP3_Auth : 0
Logfile : c:\mercury\logs\mercuryc\MercuryC.log
Log_Verbose : 0
Session_logging : c:\mercury\logs\mercuryc
Session_logmode : 1

[MercuryE]
Poll : 15
Timeout : 60

[MercuryD]
Scratch : C:\MERCURY\scratch
Timeout : 300
Poll : 100

[MercuryS]
Debug : 1
Logfile : C:\MERCURY\Logs\MERCURYS\mercuryS.LOG
Timeout : 300
Relay : 0
Strict_Relay : 1
Alt_Server_Port : 587
Allow_Illegals : 0
SMTP_Authentication : 1
Auth_File : c:\mercury\pass.txt
Session_logging : c:\mercury\logs\mercurys
Session_logmode : 1
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 0
No_VRFY : 0
SMTP_ConnFlags : 0

You will have to go through and reconfigure all of the protocols but this may not work even then.  If it does not then you will have to re-install as new over the current program to get a valid mercury.ini file.  You might though want to check the mercury.bak and mercury.bk1 files to see if these are good mercury.ini files . 

 

[quote user="Mann07"]

I don´t understand why real data would help. The Mercury-Machine is inside our network, no way to access it from the internet. Also no public DNS-Records for it. Its just fetching mail from our exchange-server and should deliver it through our exchange-server...

You did not make that clear at all.  If this is true then the data you have provided is real data.

I get the same error (sender adress is invalid) when I enter

Local host or server                      Internet name
computername                             computername
computername                             publicdomain.com[/quote]

I assume you are getting the mail via POP3 from the exchange host and are trying to have this mail sent to a mailing list.  If so the domain of the message must match the domain set in Configuration | mercury core | Internet name for this system.  That is, if info is a mailing list and not a user then the system name must be publicdomain.com before this will be sent to maiser to check to see if there is a mailing list called info. One problem may arise though since the sender address is going to be using the domain publicdomain.com the exchange server may reject the mail do to an invalid sender domain.

It would help a lot if you were to provide your mercury.ini and lists.mer file for analysis as well. 

 

You appear to have set your client to use APOP authentication.

Either set your client to use regular POP3 user/pass authentication or set the APOP secret in Mercury.

MercUpW.exe offers some extra functionality (sending email notifications etc), but unless you need that loader.exe should do. You should not run both, anyway. With the upcoming 4.71 release of Mercury it will as well be possible for registered users to run Mercury as a service that can be automatically restarted by the service handler in Windows in case of unexpected stops.

/Rolf 

[quote user="yuni_asih"]

outgoing email is doesn't work, there is an error message in mercuryE "553 we do not relay non local mail"

[/quote]

[quote]

hi Thomas,

 when i tried to send email from outlook express, there is an error message from symantec Email Proxy

"your email message was enable to be sent because your mail server rejected the sender : 421 Service not available,closing channel"

please advice

thanks

[/quote]

These are error messages from MercuryS, your SMTP server, that receives the message from your mail client and other mail servers.

MercuryE is the SMTP client module that sends outgoing mail to external mail servers.

The "421 Service not available,closing channel" is because you have MercS paused.

the "553 we do not relay non local mail" is because you have not set up Authentication to allow relaying or a Connection Control exemption to allow relaying.

[quote user="KJATL"]

Hello,

 This is my first foray into the world of Mercury. I was following a tutorial that involved testing a mail() PHP function using Mercury as the mail server. I believe the script is okay because it echos feedback  "Message has been sent". Currently I have 28 items "pending" This is what i'm working with where xxx is the first part of my email address:

I ass-u-me that use are using XAMPP.

php.ini :

 [mail function]
SMTP = localhost
smtp_port = 25
sendmail_from = Admin@192.168.1.10

This form of the address is invalid, the IP address must be enclosed in [] to make it a literal address. Use Admin@[192.168.1.10]

MercuryS output:

Connection from 127.0.0.1, Wed Apr 29 23:26:41 2009
HELO kkk

Should be a host name like [192.168.1.10] instead of kkk   It will work here since Mercury/32 really does not care.

MAIL FROM:<localhost>

Should be Admin@[192.168.1.10] instead of localhost

RCPT TO:<xxx@gmail.com>
DATA
DATA - 6 lines, 185 bytes.
QUIT
0 sec. elapsed, connection closed Wed Apr 29 23:26:41 2009

Connection from 127.0.0.1, Wed Apr 29 23:30:36 2009
HELO kkk

MAIL FROM:<Admin@192.168.1.10>
RCPT TO:<xxx@gmail.com>
DATA
DATA - 6 lines, 185 bytes.
QUIT
0 sec. elapsed, connection closed Wed Apr 29 23:30:36 2009
 

 Mercury Core:

 Wed 29, 23:27:03: Job MG000041: from postmaster@[192.168.1.10] (non-local)
   Created outgoing job with ID MO000042
   To: Admin@[192.168.1.10] (non-local) -OK

Job was accepted and since [192.168.1.10] is not in the domains list then it's sent to the queue for delivery off server.  Can't go anywhere though since the address is a non-routable IP address.

Wed 29, 23:30:43: Job MG000043: from Admin@192.168.1.10 (non-local)
   Created outgoing job with ID MO000044
   To: xxx@gmail.com (non-local) -OK

Job accepted and sent to queue for processing by MercuryC

 Does anyone have any idea what I need to work on first?

Probably the outgoing protocol MercuryC used to send SMTP to the outside world via a relay host.  MercuryE will not work since you have no fixed IP address and host name.  Without a fixed IP address and host name 90% of the receiving SMTP hosts will reject your connection as spam.[/quote]

The problem I am having is that marksmobile@ is being utilized by

Windows Mobile 6 and I can't find an area to set a "reply-to:" header

so that responses go to the smithm@ account.  So, said user complains

that he gets email on his phone that does not show up on his laptop.  I

tried to utilize IMAP with just one account but he was not happy with

this and requested two POP3 accounts with the forward. He wants both

accounts to be mirrored, so I thought maybe setting an outgoing filter

that would catch "marksmobile@" and add a reply-to: header.  Am I on

the right track, or should I be approaching this from another direction?

It looks like he wants all mail from markmobile@ to be replied to smithm@ then the client should be sending using that address.  If he sets the email address of his mobile system to smithm@ as the From: address it should work.  

Released now.

I hope you can help because this stuff goes beyond my knowledge and

it's going to take lots of time for me to solve this, if ever.

The lack of connection to port 110 can be caused by:

1.   MercuryP is not running and bound to port 110.

2.   Port 110 to the local system is being blocked by the Windows firewall.  Turn off the firewall and try again to test.

3.   MercuryP is blocking the IP address.  Allow the local addresses in the MercuryP connection control and whitelist them.

 

 

 

Haven't seen any similar behavior here, but here are a few things you can check:

- Make sure  the SCRATCH and QUEUE directories exist in your Mercury directory, and that Mercury has full access to them.

- If you have any real-time antivirus software running, exclude at least SCRATCH and QUEUE directories from scanning.

- Check that the MERCURY subfolder exists (..\MERCURY\MERCURY\) and contains the failure.mer file (error notification template). Mercury will need full access to this directory and the files in it as well.

/Rolf 

 

Help,  I have been have a problem with retreiving emails using MercuryD.  Certain emails with a Word or Excel attachment will not be retrieved.

My latest example is an email with an Excel attachment.  It is not every Excel attachment though.

here is a protion of the log file

13:43:27.875: --- Fri Apr 24 13:43:27 2009 ---
13:43:27.875: Connect to 'mail.****', timeout 30.
13:43:28.875: >> +OK go ahead<cr><lf>
13:43:28.875: << USER ******<cr><lf>
13:43:28.906: >> +OK Tell me your password.<cr><lf>
13:43:28.906: << PASS *******<cr><lf>
13:43:28.968: >> +OK Welcome aboard! You have exactly one message.<cr><lf>
13:43:28.968: << STAT<cr><lf>
13:43:28.000: >> +OK 1 12600<cr><lf>
13:43:28.000: << LIST<cr><lf>
13:43:29.046: >> +OK Scan list follows:<cr><lf>
13:43:29.281: >> 1 12599<cr><lf>
13:43:29.281: >> .<cr><lf>
13:43:29.296: << RETR 1<cr><lf>
13:43:29.328: >> +OK Message follows<cr><lf>
13:43:29.328: >> X-Envelope-To: >
13:43:29.328: >> Return-path: <*****><cr><lf>
13:43:29.328: >> Envelope-to: *******<cr><lf>
13:43:29.328: >> Delivery-date: Fri, 24 Apr 2009 12:43:21 -0700<cr><lf>
13:43:29.328: >> Received: from [66.6.63.20] (port=34347 helo=mail4h.hosting.************)<cr><lf>
13:43:29.328: >>  by cluster01.**********with ESMTP id 1LxRIu-000Pny-5p <cr><lf>
13:43:29.328: >>  for ********; Fri, 24 Apr 2009 12:43:21 -0700<cr><lf>
13:43:29.343: >> Received: from exim by mail4h.hosting.******** with spam-scanned (Exim 4.69)<cr><lf>
13:43:29.343: >>  (envelope-from <**********>)<cr><lf>
13:43:29.343: >>  id 1LxRIs-00052i-3h<cr><lf>
13:43:29.343: >>  for *************; Fri, 24 Apr 2009 19:43:19 +0000<cr><lf>
13:43:29.343: >> X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail4h<cr><lf>
13:43:29.343: >> X-Spam-Level: <cr><lf>
13:43:29.343: >> X-Spam-Status: No, score=0.1 required=5.0 tests=ALL_TRUSTED,AWL,HTML_MESSAGE,<cr><lf>
13:43:29.343: >>  MIME_HTML_MOSTLY shortcircuit=no autolearn=ham version=3.2.4<cr><lf>
13:43:29.343: >> Received: from s142-59-18-230.ab.**************** ([142.59.*******] helo=********)<cr><lf>
13:43:29.343: >>  by mail4h.hosting.************* with esmtpa (Exim 4.69)<cr><lf>
13:43:29.343: >>  (envelope-from <***************>)<cr><lf>
13:43:29.343: >>  id 1LxRIq-0004yg-UN<cr><lf>
13:43:29.343: >>  for *************; Fri, 24 Apr 2009 19:43:18 +0000<cr><lf>
13:43:29.343: >> From: "**********" <**************><cr><lf>
13:43:29.343: >> To: <**************><cr><lf>
13:43:29.343: >> Subject: rsc claim <cr><lf>
13:43:29.343: >> Date: Fri, 24 Apr 2009 13:43:10 -0600<cr><lf>
13:43:29.343: >> Message-ID: <****************><cr><lf>
13:43:29.343: >> MIME-Version: 1.0<cr><lf>
13:43:29.343: >> Content-Type: multipart/mixed;<cr><lf>
13:43:29.343: >>  boundary="----=_NextPart_000_00F1_01C9C4E2.9F30FA90"<cr><lf>
13:43:29.343: >> X-Mailer: Microsoft Office Outlook 11<cr><lf>
13:43:29.343: >> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579<cr><lf>
13:43:29.343: >> Thread-Index: AcnFFOYnDKc5ao4HTliHS/J2UdyYyA==<cr><lf>
13:43:29.343: >> X-Auth: <cr><lf>
13:43:29.343: >> X-Local-ID: 1LxRIu-000Pny-5p<cr><lf>
13:43:29.343: >> X-GeoIP-Code: CA<cr><lf>
13:43:29.343: >> X-GeoIP-Country: Canada<cr><lf>
13:43:29.343: >> X-GeoIP-Region: ON<cr><lf>
13:43:29.343: >> X-GeoIP-City: *****<cr><lf>
13:43:29.343: >> X-GeoIP-PostalCode: *****<cr><lf>
13:43:29.343: >> X-GeoIP-Latitude: ***********8<cr><lf>
13:43:29.343: >> X-GeoIP-Longitude: -75.699997<cr><lf>
13:43:29.343: >> X-GeoIP-MetroCode: 0<cr><lf>
13:43:29.343: >> X-GeoIP-AreaCode: 0<cr><lf>
13:43:29.343: >> X-PEP: build Mar 24 2009 10:46:34<cr><lf>
13:43:29.343: >> X-UIDL: 8577cf02b353bd623a6b7cae177f1e44<cr><lf>
13:43:29.343: >> X-Filename: new/49f21659.000183c6.cluster01.*************:2,Z<cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> This is a multi-part message in MIME format.<cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> ------=_NextPart_000_00F1_01C9C4E2.9F30FA90<cr><lf>
13:43:29.343: >> Content-Type: multipart/alternative; boundary="----=_NextPart_001_00F2_01C9C4E2.9F30FA90"<cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> ------=_NextPart_001_00F2_01C9C4E2.9F30FA90<cr><lf>
13:43:29.343: >> Content-Type: text/plain; charset="us-ascii"<cr><lf>
13:43:29.343: >> Content-Transfer-Encoding: 7bit<cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >>  <cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> ------=_NextPart_001_00F2_01C9C4E2.9F30FA90<cr><lf>
13:43:29.343: >> Content-Type: text/html; charset="us-ascii"<cr><lf>
13:43:29.343: >> Content-Transfer-Encoding: quoted-printable<cr><lf>
13:43:29.343: >> <cr><lf>
13:43:29.343: >> <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =<cr><lf>
13:43:29.359: >> xmlns:w=3D"urn:schemas-microsoft-com:office:word" =<cr><lf>
13:43:29.359: >> xmlns=3D"http://www.w3.org/TR/REC-html40"><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> <head><cr><lf>
13:43:29.359: >> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =<cr><lf>
13:43:29.359: >> charset=3Dus-ascii"><cr><lf>
13:43:29.359: >> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)"><cr><lf>
13:43:29.359: >> <style><cr><lf>
13:43:29.359: >> <!--<cr><lf>
13:43:29.359: >>  /* Style Definitions */<cr><lf>
13:43:29.359: >>  p.MsoNormal, li.MsoNormal, div.MsoNormal<cr><lf>
13:43:29.359: >>  {margin:0in;<cr><lf>
13:43:29.359: >>  margin-bottom:.0001pt;<cr><lf>
13:43:29.359: >>  font-size:12.0pt;<cr><lf>
13:43:29.359: >>  font-family:"Times New Roman";}<cr><lf>
13:43:29.359: >> a:link, span.MsoHyperlink<cr><lf>
13:43:29.359: >>  {color:blue;<cr><lf>
13:43:29.359: >>  text-decoration:underline;}<cr><lf>
13:43:29.359: >> a:visited, span.MsoHyperlinkFollowed<cr><lf>
13:43:29.359: >>  {color:purple;<cr><lf>
13:43:29.359: >>  text-decoration:underline;}<cr><lf>
13:43:29.359: >> span.EmailStyle17<cr><lf>
13:43:29.359: >>  {mso-style-type:personal-compose;<cr><lf>
13:43:29.359: >>  font-family:Arial;<cr><lf>
13:43:29.359: >>  color:windowtext;}<cr><lf>
13:43:29.359: >> @page Section1<cr><lf>
13:43:29.359: >>  {size:8.5in 11.0in;<cr><lf>
13:43:29.359: >>  margin:.5in .5in .5in .5in;}<cr><lf>
13:43:29.359: >> div.Section1<cr><lf>
13:43:29.359: >>  {page:Section1;}<cr><lf>
13:43:29.359: >> --><cr><lf>
13:43:29.359: >> </style><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> </head><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> <body lang=3DEN-US link=3Dblue vlink=3Dpurple><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> <div class=3DSection1><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> <p class=3DMsoNormal><font size=3D2 face=3DArial><span =<cr><lf>
13:43:29.359: >> style=3D'font-size:10.0pt;<cr><lf>
13:43:29.359: >> font-family:Arial'><o:p>&nbsp;</o:p></span></font></p><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> </div><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> </body><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> </html><cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> ------=_NextPart_001_00F2_01C9C4E2.9F30FA90--<cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> ------=_NextPart_000_00F1_01C9C4E2.9F30FA90<cr><lf>
13:43:29.359: >> Content-Type: application/vnd.ms-excel; name="RSC Claim1.xls"<cr><lf>
13:43:29.359: >> Content-Transfer-Encoding: base64<cr><lf>
13:43:29.359: >> Content-Disposition: attachment; filename="RSC Claim1.xls"<cr><lf>
13:43:29.359: >> <cr><lf>
13:43:29.359: >> 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAAQAAAAAAAAAA<cr><lf>
13:43:29.375: >> EAAAIAAAAAEAAAD+////AAAAAAAAAAD/////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ///////////////////////////////////////////////////////////////////////////9<cr><lf>
13:43:29.375: >> ////HwAAAAMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAACwAAAAwAAAANAAAADgAAAA8A<cr><lf>
13:43:29.375: >> AAAQAAAAEQAAABIAAAATAAAAFAAAABUAAAAWAAAAFwAAABgAAAAZAAAAGgAAABsAAAAcAAAAHQAA<cr><lf>
13:43:29.375: >> AB4AAAD+////KgAAAP7///8iAAAAIwAAACQAAAAlAAAAJgAAACcAAAAoAAAAKQAAACsAAAD+////<cr><lf>
13:43:29.375: >> LAAAAC0AAAD+////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> ////////////////////////////////////////////////////////////////////////////<cr><lf>
13:43:29.375: >> /////////////////////////////////////////////////////////////////////////1IA<cr><lf>
13:43:29.375: >> bwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA<cr><lf>

.....

13:43:29.562: >> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA<cr><lf>
13:43:29.562: >> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA<cr><lf>
13:43:29.562: >> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA<cr><lf>
13:43:29.562: >> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA<cr><lf>
13:43:29.562: >> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA<cr><lf>
13:43:29.875: 7: Socket read error 10054 (connection aborted by remote host)
13:43:29.875: << QUIT<cr><lf>
13:43:29.875: 9: Socket write error 10054 (connection aborted by remote host)
13:43:29.875: --- Connection closed normally at Fri Apr 24 13:43:29 2009. ---
13:43:29.875:

I can create a new excel file and copy the info from this file and then send the new file as an attachment and it will go thru.

Even if we delete all the contents of this excel sheet and attach it the same problem.

We have seen the same problem with some MS Word files but a lot less often.

We can send this email from an internal account thru Mercury and it will be delivered, it just seems to be with how MercuryD is handling it.

Anyone have any ideas?

 

Thanks for your help Rolf and Thomas. 

It was a firewall that was preventing any emails with VBA content.  It did not matter if the attachment had an actual macro in it, only that if the creator of the file had macros enabled in their version of Microsft Word or Excel that would be enough of a VBA flag for the firewall to stop it.

 Barry

 

 

They've just back to me - last time they could send mail was March 6th.

That explains it.

Thanks again for helping me sort this out, it was really frying my brain.

4. You could set to use Mercury as http://en.wikipedia.org/wiki/Smarthost for local users on same domain and allow Relay Non-local mails thrum using single relay mail account.

Hopefully that some experienced user can explain how to set it up. I've been able to set it up when using MercE but with little bit more settings it should be manageable with MercC.

 Additionally in my case I was using 2 mercury servers inside two separate network workgroups of same LAN with 12 users in one workgroup and 53 in second where second Mercury server relayed all domain emails to first Mercury server using MercC where first one has done final delivering using MercE. So other way around First gets all mails for domain then all unknown emails for addresses not in first users group are saved in relay account that second Mercury server get using MercD and distribute to user accounts.

 Sorry again for complex description but when you get it done it works :( hopefully you will get an idea how to solve.

 Again: None of these methods would solve the problem where there is a user with the same name on both systems.

[quote user="cynist"]

I am running V 4.62 on an XP Pro machine.  Everyone connects through IMAP.  I have only created one certificate in MercuryS.[/quote]

I don't know of any issues with that combination.  It may be the sending server at fault. 

[quote]If I turn this feature off then servers who send TLS messages will not be able to connect, correct?[/quote]

No, as Rolf says, it's always optional. 

> There isn't an easy way to exempt a range of IP addresses from blacklist lookups, but Mercury help suggests this:
>
> Whitelists
>
> The same technique used by blacklist query servers could also be used to create "whitelists" - servers listing machines that are always
> acceptable. At the time of writing, no public whitelists exist on the Internet that we know of, but if you control your own local domain
> name server, there is nothing to prevent you from entering addresses in the proper form within that database then creating a Mercury
> definition to query it. This approach could be useful if you need to correspond with a site that has somehow become blacklisted, without
> turning off blacklist controls for other sites.

From "Robert Croson, Jr" <robert@arcm.com>

You don't really need to run your own DNS server to support a MercuryS whitekist. It is possible to do it using HOSTS file entries.  



You can also use a DNS caching utility, such as haneWIN DNS, TreeWalk, or FastCache, instead of a DNS server. These programs simply remember all of your DNS requests, and cache the answers. It could possibly speed up your browsing if you have a slow DNS server. These tools also let you add your own permanent entries as well.  

Once you have a DNS cache running, you can do all sorts of funky-cool stuff, including whitelisting domains, IP addresses, controlling what servers are used to deliver your mail (useful if you have access to a relay server, and a specific domain refuses to take mail from your own (i.e. you run a server from your home and are rejected because you are on a dynamic IP)), etc.  

You can also add your own DNS blacklist for domains, IPs, etc.

http://email.arcm.com/wiki/index.php/DNSWhiteLists