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. 

To avoid being an open relay please verify that "Use strict local relaying restrictions" is checked in MercuryS configuration / Connection control. See Mercury help for other options regarding SMTP relaying. (Relaying is switched off by default.)

/Rolf 

For SMTP forwarding of messages in a domain mailbox you can use WSMTPEx.exe, as mentioned in the link I posted before:

Thomas R. Stephenson:

The third one is the program WSMTPEx.exe (SMTPEX.NLM for Netware)  and this a a separate program that takes mail for a email account and forwards it to any port and any hostname/IP address.  I use this with my domains to forward the mail to a Linux system (must use high ports as non-root) and to a second instance of Mercury/32 running on my system (can't share port 25)  Here's a sample of the ini file I use for forwarding all mail to Mercury/32 running on Ubuntu v8.10 and Wine.  

 #  You can rename this tool, but name of following section must remain [WSMTPEx]
[WSMTPEx]
Version=0.10
#  TCP port, on which SMTP server listens
Port=8025
#  Number of seconds to delay between searches for emails
LoopDelay=30
#  Folder, under which is most of user's mailboxes
UserFolder=
Domains=1
# Users mail address domain part
Domain1=linux-tstephenson.com
LogName=c:\Mercury\WSMTPEx.log
SMTPServer=192.168.1.4
MailBoxes=1
Badmails=c:\pmail\mail\BadMail

[linux-tstephenson.com]
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mb1addr=dm:ubunto
Mb1dir=c:\pmail\mail\ubunto


This takes all the mail in the domain account "UBUNTO"  and sends it to port 8025 on 192.168.1.4 to be received by MercuryS.  The directory BADMAIL I have specified must exist.  You can run multiple instances of this tool and and it can be run as a service.  If run as a service and running multiple instances the name of the program should be changed.  I use WSE-UBUNTO to rename the program and ini file for this one.  

Many thanks to Petr Jaklin for the development of these tools.  You can get these tools at the community download areas or directly from Petr Jaklin's site   

/Rolf 

None was working; file was available, and the whole Mercury folder is excluded from antivirus scanning, file indexing, etc.

Anyway, the problem showed up no more...

Best regards

Filippo

Hi there! I'm having the same problem with Schorsch, and I thank you for the info shared...I really appreciate it...it's now working!

ok,

thank you 

Thanks for help :-)

stanneo 

Hi all.

Can we set Mercury up to operate as a store and forward agent?

In this case, it will be sitting in a DMZ like env, ideally with no users defined, and forward to the real SMTP server (where the real users are defined).

Being based on Windows, I'm hoping that in addition to it's RBL support, that things like Kaspersky SPAM filtering can also be used to advantage.

Can Mercury be set up in this manner? Basically, a SMTP server, in a store and forward manner (ie a mail relay)?

Thanks,

-Chris 

And where do you see that error number? Is it in your email client, is it sent from the receiving server? Check log files for more details.

/Rolf 

Okay, I did restrict the relaying stuff now, I did find some of the blacklists' homepages and I did do some of the removing of my domain from their lists, but some of them wanted me to pay them for being "whitelisted" permanently, which is not what I would expect a technology, an idea like the internet to be like (I bought my domain didn't I...), but that's a different issue.

There's a way bigger issue for me now, which is that Strato does something in their system that prevents me from being contacted by other mail servers, as strato told me in an answer to my email (dyndns is the problem i guess...). So I'm probably gonna be happy with SENDing mails for now till I get a static IP. Thanks for all the help!!

Hello,

 To start with:

Thanks for answering and taking the time to look at our issue. That by itself is very much appreciated.!

but we found the problem right before your nose and we all overlooked it.

The square brackets around the e-mail address are incorrect, change to <...@...>

 From: -------------------------- <info@----------------->

 et voila,.... problem solved.