Danke vielmals, Olaf! - and to Han also, of course! That's most helpful and makes me feel somewhat more comfortable about deployment.

> I mark this thread as finished although mail transmission without encryption is not very secure.

Mail transmission with encryption just between client and server does not help all that much anyway sense it's been traveling over the internet unencrypted.  ;-) To make e-mail secure the content must be encrypted.

If the settings file MERCURY.INI has been damaged it can usually be restored from the backup copies in MERCURY.BAK or MERCURY.BK2 (all in the main Mercury directory).

/Rolf 

I'm trying to write a script that adds IP addresses to the MercuryS Access Control List by appending them to the file mercurys.acl.  However, Mercury seems to keep a copy of that file in memory and flushes it out when it exits, overwriting my updates. I could shut down Mercury, update mercuryS.acl and restart Mercury but I'd rather not. Is there any way for an external program to notify a running Mercury that the mercurys.acl file has been changed?

Alternatively, since Mercury exits and restarts nightly (using loader.exe), is there any way to have loader.exe run a script before it restarts Mercury? That would allow me to update the ACL when mercury is being bounced.

I use a custom subscription account for Mercury. However, I thought the default address was maiser@ not postmaster@. To achieve this I did the following:

“Drive:\Mercury\mercury.ini” must be edited so that the [Maiser] header appears as follows:

[Maiser]
Maiser:          <Account-name>   # 'Username' of mail server account
Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file
Notify:          C:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands
NoList:          N   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

Where the string ‘maiser’ appears in the *.mer files in the “C:\Mercury” folder, ‘maiser’ must be replaced with ‘<Account-name>’.

Edit your templates accordingly.

That's irritating for my clients - isn't it? Should be fixed! Most people are not IT-specialists. They need simple, clear answers - even by maiser!

Mercury/NLM didn't have that bug! Errormails have been FROM maiser and with informative text.

bye   Olaf

Hallo Thomas,

thanks for your answer! Depreciated or not ... would be nice if Mercury would support direct SSL with all modules. Have to test a lot if there is any mailreader especially on notebooks (and even Smartphones) of my clients, that need direct SSL. No ... you don't want a discussion with a professor about changing his mailreader or even updating the existing one. :-(

The desktops are not that problem ... they have Pegasus. But notebooks and especially private notebooks are not under my control. I know there's a wide range of mailreaders and even differnet versions of them (Thunderbird, Seamonkey, Outlook, Outlook Express, Opera ...). OK ... I'll kick the one client with Outlook Express ... isn't even capable opening WINMAIL.DAT ;-)

STunnel ... had some tests in context with other software a while ago ... and massive problems. Don't want that hack again.

bye   Olaf

 P.S. A hint in help and/or documentation, which modules are capable which encrytions, would be nice!

Hi Olaf,

Thanks for your reply. Without the astersisk wildcard in front of the "@" it works. Great

Brgds

Joerg

> Each copy of Mercury sends its own mail directly with MercuryE.
>
> This all works perfectly well and is easy to maintain.

Personally I would use MercuryC at the branch offices to deliver all mail to the main site.  Otherwise the main site becomes the gateway host sending/receiving all mail from the domain, including the branch offices.  I do not know if this will fix the problem but since one site gets all the mail and local mail never leaves the local company LANs then it may help.  

I do not normally setup branch offices like this, I normally have all users mail delivered to local mailboxes and use Domain mailboxes to collect all the mail from the users at the branch sites.  I then use MecuryD to pull the mail for the branch offices.   

One real advantage to this is that the branch offices do not have their domain registered in the DNA since they are not getting anything directly from the internet.  You have one IP address and host name seen by the outside word.

YMMV ;-)

[quote user="Thomas R. Stephenson"]

Did not like my answer???  Why do you want to get us to answer again,

[/quote]

I did not dislike your answer; simply put, as I'm a novice, I did not understand that your answer implicitly said that my solution was not advisable...

[quote user="Thomas R. Stephenson"]

your method could work but it's not something I would do nor can I test it.

[/quote]

This is an answer that - as novice - I can understand.

Thank you and sorry for having bothered.

Best regards

Filippo

> The ISP is a University system that we send a lot of mail to.

What server???  I could try from my side if I knew what server you are talking about.  Please do not make us guess about the problem.

> I had turned session logging on for a bit and didn't see anything that stood out and basically the same as the MercuryE module window.

Could you post the session log?

> I did increase my timeout setting but that didn't seem to improve
> things.

To what?

> I don't have trouble sending mail to other domains and according to one of their email admins they have 25 inbound smtp servers.

No big deal, a lot of places have multiple mail servers.

> I just thought it was odd that MercuryE only seems to try 4 before it stops and puts the message back in queue.

I doubt it unless the first 4 servers in the list are bogus and are there to stop spammers.  What happens when you telnet in port 25 of these hosts?

If you have to access a Netware file system, then you should NOT use Mercury from a service running.

We start Mercury in a scheduled task (Windows Task Scheduler) with the special Netware and Windows account after every boot.

To access the user interface of this instance you must stop this scheduled task. Then you can start Mercury with user interface.

Torsten

Disable the configurations like Mercury B and Mercury E to start Mercury C vis versa directly in the mercury.ini before you hit mercury.exe. There is a conflicting configuration in there, that I think is a bug in the software. 

> Sir it worked already... thanks a lot!!!! Uhm just additional inquiry
> is there a way to speed up Mercury's mail sending capabilities? like
> when I press send in Pegasus, Mercury is triggered to send the mail
> immediately, not like what happens now in which I need to wait
> sebveral seconds before Mercury sends... Thanks!!!!


Mercury is going to take at least a few seconds to send.  Mail is first put in the queue by the mail client, it takes a few seconds (10 is the default) for Mercury core to see the 101 file in it queue and process it as a MO*.QCF/QDF file pair for processing by either MercuryC or MercuryE.  MercuryC/E also takes a few seconds (again 10 seconds) to see the queued mail and sent it.  This is all by design.

This can be caused by logging off the client and then shutting down Mercury before HIERARCH.PM has saved properly. It takes a minute or two on my system. The lock file MAILBOXM.LCK in the same folder disappears at that time.

The fix is as Thomas says (as is everything else!).

 Chris

# is the comment character for the ini file where Mercury stores a lot of its settings. This means that the # itself and anything after that on the line will be considered a comment rather than part of the password.

I'll bring the matter to David's attention and we'll see if there is some easy solution.

/Rolf

Here, this says it in a different way, see if it helps:

I do that with rules at the top of the list that filter for those users on the basis of the To header and exit from rule processing.

Configuration > Filtering Rules > Edit Global Rules

but you say you've checked global filters?

Hmm ... if there are replicas of NDS on that server or not should not make any sense.

Netware should have NSS or TFS as filesystem. Which filesystem did you choose for OES2? Maybe the problem is in behaviour of filesystem, if it is linuxlike.

lg   Olaf

Thanks for your help, Paul. As ever, it is appreciated.