There have been a bunch of threads about non-working xampp configurations on the forum, so you might start by searching them out and see if the answers there can help you. If not, please post the contents of your mercury.ini file (hide any password but please leave other stuff unchanged) and we'll see what we can suggest.

/Rolf 

Well, the simplest solution would be to create 10 filters, each screening out a single digit?  Are the domain names always the same?  If so... hmm, this is complicated.  If you do this, ANY email with even a single digit will be snagged, which you may not want.

[quote user="cmolloy"]Only one mercy process running, I stopped the service, closed the Mercy32 Console, Opened the Mercy32 Console and tested, mail flow now showing in the status windows..... I started the service and mail flow still showing....

Thanks for your help.[/quote]

Did I misread this - is it now fixed?

wow thank you so much, this did the job, as you can tell im totally new to this software and I wasn't aware of the security options I had to configure first.

It appear so be working fine now, thanks again :)

I'm not clear about exactly what the rule is though. [If header To contains "colleen.kelly@student.college.edu"] should trigger the rule. Remember that global filtering rules look at the message headers, not the SMTP envelope information.

/Rolf 

As you provided few details I quoted what the Wiki says about locked mailboxes in general. The part about IMAP access says:

"multiple IMAP client sessions against the same mailbox through MercuryI are allowed" 

If you have a situation where there is a problem with this, please post a MercuryI session log (or relevant parts of one).

/Rolf 

Rolf, got it. thank  you!!!

Assuming you can get some sort of connection for your server while your ADSL is down, the simplest solution is to get a Dynamic DNS (maybe no-ip.org as dyndns.org now charges for new accounts) and set up the update client on your Merc server.

Then set that dynamic domain name as your secondary MX.

Under normal conditions both MX records point to your static ADSL IP.

When the ADSL is down, get your other connection up and the update client will point your dynamic name at the new IP and mail deliveries will fail on the primary and fall back to the secondary, which is now pointing at your Mercury via the temporary connection IP.

No need to enrich google with all your data. :)

1. Maybe.

2. Lots.

3. No.

4. Yes.

I've been using Outlook as my IMAP client to Mercury for a number of years, with few problems.  But this weekend my Mercury disk ran out of space, and now I always get error messages that "Your server reported a UID that does not comply with the IMAP standard.  This typically indicates a server bug.  Your program may not function properly after this", with the following details:

MsgSeqNum 12250, New UID 179, Prev UID: 12168, Next UID: 0.

Can anybody shed any light what went wrong?

I already tried deleting the local Outlook IMAP cache and rebuilding it.  It made no difference.

Thanks, Eric 

Assuming that it worked normally before I would start by running Chkdsk to check for NTFS errors on the disk, and then make sure that no antivirus software or similar is intervening with Mercury's access to files.

/Rolf 

I second this!!  A number of our users now use Outlook either by personal choice or because it works well with other software we use.  Renaming folders would also be a big plus.

Good Morning: 

I've tried posting a private message but am not sure if it was successful.

My name is Bruce Knack and I can be reached at: bknack@siliconsurfers.com. If my private message is trapped in the ether, please feel free to email me.

Cheers,

Bruce. 

Drivers were not the answer...

Also tried refreshing the DNS and turning off Semantic email scanning.  One of these two did the trick.  I'm leaning toward turning off Semantic as the answer - even though SEP was disabled as soon as the server started having issues.

When I upgrade I just take a straight copy of the whole mecury directory.

The upgrade to 4.74 was straight forward.

Thanks very much, Rolf!  I have set Mercury to run as a service and will wait for the next restart to see if it functions as expected.

I'm with Rogers, and I've been running Mercury with a different port for years (I use a number in the 20,000 range) on MercuryS.  But I do use MercuryC SMTP client and MercuryD 

POP3 client and let Rogers forward all my emails -- partially because they don't allow static IP addresses.  I use EasyDNS to have all my email addresses forwarded to my rogers address.  Every 30 seconds my POP3 client picks up the mail from Rogers and distributes internally.  My email clients send to MercuryS on the funny port, and then the SMTP client forwards that to Rogers, which in turn sends it to wherever.  Hope this helps.

This is what Mercury help says about creating new users:

When you are using Mercury/32 in an environment for which it has no network support module, the option to create and manage local users becomes available on the Configuration menu. This option allows you to manage the Pegasus Mail user configuration file PMAIL.USR, which is used by both Mercury/32 and Pegasus Mail to define and locate the users who exist on the system.

Important note:  Mercury reads the Pegasus Mail system file PMAIL.USR to obtain local user information, and caches it in memory while it runs. If you make changes to PMAIL.USR using Pegasus Mail or via any other process that manipulates the file directly, you will need open the Mercury user administration dialog while holding down the CTRL key, to force it to re-scan the list. Restarting Mercury will also work in this situation. Until Mercury refreshes its cached copy of the user list, it will not be able to deliver to users added via the alternative method. Mercury saves changes made by its own user dialog as soon as you click OK, so we recommend that you do all your user administration from within Mercury.

Username  the name the user will give to identify himself to Pegasus Mail. By default, this is also the user's address. In order to remain compatible with the DOS and Win16 versions of Pegasus Mail, usernames are limited to eight characters total length (because they are used as the name of a directory).

Personal name  the "familiar name" by which the user is known to the rest of the world. This is the name that appears in the Pegasus Mail Local user list function, and which Mercury uses when responding to mail server VERIFY and LOOKUP commands.

POP3 password  The password the user needs to enter when retrieving mail via POP3. If a user does not have a POP3 password, or has a blank POP3 password, he or she cannot retrieve mail from Mercury/32 using the POP3 protocol. The password can be from 1 to 48 characters in length

The dialog for creating users is found under Configuration / Manage local users...

/Rolf

[quote user="Quantos"]07:16:57.984: --- Tue Aug 14 07:16:57 2012 ---
07:16:57.984: Connect to '65.55.37.72', timeout 60.
07:17:20.000: 15: Peer connect failure"

 Now, from what I understand, this might be an issue at the network side of things, as it seems to go through port 25 correctly, and is unable to connect the server for the email domain I'm trying to send to (in this case Gmail, but I've tried Hotmail and a company email as well and both do the same thing).

I am unable to ping or trace to any of these email addresses. Shouldn't I be able to? Also, am I right in assuming that the issue is somewhere on the network itself, and not necessarily on my side (i.e. some security configuration blocking access to a local smtp server?).

 Thank you for any assistance! :)

[/quote]

Check your firewall to make sure Mercury is allowed.

Otherwise, something is blocking your outgoing access to hotmail servers on port 25 - probably your ISP, but it might be that you have a non-static IP address and few big companies will take email from those.

Try changing to MercuryC instead of MercuryE and relay your emails through your ISP/gmail/whoever.

May I ask to confirm that this issue is still current and causing problems for mail managers?

I ask because we recently changed ISPs and the change of circumstances obliged us to use the End-to-End client instead of the Relaying client. Within a short time, we encountered the "multiple destination domains per transaction is unsupported" problem when sending traffic from the list server. Currently, my workaround involves splitting lists into chunks to separate suspect domains, so they don't clash and provoke the error from Google's mail servers. Obviously, this is cumbersome and time-consuming. I'm asking because perhaps the problem has gone away and I don't need to carry on doing this ;)

I believe Exim has an option "multi_domain" to tweak the sending client, to cope with Google, and sendmail is talking about something similar. Does anyone have a suitable workaround for Mercury? While people have strong opinions about Google setting standards of their own and expecting the world to fall into line, I wonder if having a consolidation switch in the SMTP Client settings might prove useful in several ways (Consolidate at most "X" messages).

Bob.