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

that wasn't it.  I had to go in and manually clear the queue in order for it to open properly. 

Thanks guys.  I'll check around to see what I can find.  I appreciate your help.

Glad you got it working (or at least on the way [:)]).

For future debugging, and for anyone else finding this thread, turning on SESSION LOGGING in MercuryS will give a COMPLETE TRANSCRIPT of the SMTP session between the client (your PHP script) and the server (MercS). This can be very useful in pinning down any errors, and where they are occuring.

Yes, that makes sense.  Anyway, at least I know how to fix the problem with OE now.

Gordon

I saw a suggestion somewhere that to help mitigate the problem of spam senders looking for the secondary MX you could set up a 3rd MX that is the same as your first MX thus possibly causing the spam sender to really send to your primary MX.  Of course this does not guarantee that a spam sender won't figure out that you are trying to circumvent his attempt to send to your true secondary MX.

[quote user="Thomas R. Stephenson"]If the PMail and Mercury mailboxes are split then you setup the POP3 downloads using the PMail POP3 setup.[/quote]How do I split them?

[quote user="Thomas R. Stephenson"]If you want PMail to send via the built-in mailer instead of the Mercury queue then setup the Tools | Internet options |  Sending (SMTP) to use the built-in mailer regardless of address.[/quote]Yes, that's what I meant.

T

C

Did you install the most recent version of Mercury? Did you read the Mercury help and/or manual on how to set up the system (especially local domains)? Do please not rely on any xampp documentation for this.

/Rolf

Additionally you can allow clients from specific network addresses to relay, again from Connection control settings (can be individual addresses or a range of addresses).

/Rolf 

[quote user="flim"]

The IronPort MTA will receive messages from internal Domino server, by

default the messages are send to internet gateway (192.168.1.1), but

for some domain it will sned to VPN gateway (192.168.1.2).  Is Mercury support custom domain list to route message to VPN gateway?

 [/quote]

[quote user="flim"]

As there are many different domain (branches of company), like "abc.com", "def.com", if the receipent domain match those domain, the MTA will route the e-mail to a central VPN MTA, and the VPN MTA will route the email to target domain.

[/quote]

I'm still not sure I understand your setup. The Domino server sends all outgoing mails to a MTA (Mercury). This MTA will then deliver all external mail normally, but should deliver messages for a number of special domains via VPN connections instead of according to the public MX records for those domains. Is there then another "central VPN MTA" that receives the messages and relays them to the destination MTA for each domain, using VPN connections??

/Rolf 

Another alternative is to get an offsite provider to provide just the relay host and mail forwarding to you server via alternative ports.  It's a lot easier to do rather than use the alternatives.  The people at DynDNS.com can do this by domain.   Costs a couple hundred dollars a year or less.