Thank you :)

Point taken...I have re-installed with these corrections...now I am working on getting the relay to internet address working.

Thanks.

> I would be grateful to anyone who can help me with configuring
> Mercury Mail for a LAN based network without internet connection.
> The mailing system is only intended for exchanging mail with
> attachments between clients on a LAN network without being connected
> to the internet. I would request full setup and configuration
> procedure.

1.  Install WinPmail in the multiuser mode on the "server".  Use c:\pmail
    for the program; c:\pmail\mail for the mail directories.

2.  Run PCONFIG.exe from the WinPMail program directory and change the HOME and
    NEW mail directory specification to the \\server\vol\pmail\mail\~8
    format.

3.  Go to the remote workstations and install a shortcut to the common
    program.

Ok, now you have the basic mail system setup.  You can send mail to each other using Pegasus Mail and the Pegasus Mail username as the e-mail address.   

4.  Install Mercury/32 on this same server pointing to the Pegasus Mail
    directory structure.  Use MercuryP, MercuryS, MercuryC at least. Use
    \\server\vol\mercury\queue for the mail spool directory.

You now can send and receive SMTP mail via Pegasus Mail.  The mail is delivered to the Pegasus Mail directories automatically.  You send mail simply by putting the output files into the Mercury/32 mail spool directory.  This is accomplished automatically with a Pegasus Mail User Defined Gateway.  Your e-mail address for sending the mail is username@<internet name for this system>

6.  If you want to maintain other POP3/IMAP4 clients, point the client
    at the at your Mercury/32 host as a POP3 and SMTP host using the IP
    address of the mercury system for the server name and Pegasus Mail
    username and password to pickup the mail.

You can do a complete inbound and outbound mail archive with this setup using a simple Mercury/32 "Always" filter that put a copy in a users mail directory.

This might help if you have lots of users to process.

It steps through the user folders, if there is a forward file it extracts the destination address and queues up any existing CNM's for delivery to that, then moves them out of the way.

Adjust the paths to suit.

(no warrantee etc. :))

[quote]

@echo off
set queue=c:\mercury\queuetest
set store=c:\mercury\mailstore
set FROM=slave@mydomain.com

cd %store%
for /f %%D in ('dir /a:d /b') do (
    if exist %%D\FORWARD (
        mkdir %%D\done
        echo $$ %FROM%>> header.txt
        for /f "delims=<> tokens=2" %%T in ('findstr /B "Forward-To:" %%D\FORWARD') do echo T %%T>> header.txt
        echo.>> header.txt
        for %%a in (%%D\*.cnm) do (
            copy /A header.txt + %%a %queue%\%%~na.101
            move %%a %%D\done
        )
        del header.txt
    )
)

[/quote]

[quote user="Kevin Hastings"]This makes me wonder if there is a way to limit the 501's to 1 or 2 before the 554 is returned.[/quote]

No, it is built-in to Mercury.

[quote]Am I loosing the plot?[/quote]

Only you can answer that!!  But I wouldn't spend any time chasing down these connections - there are more important mail-admin tasks to do. :)

Thanks for the explanation about Gmail's sending options - I must have seen that some time ago but didn't use it.

Anyway, I'm glad you found a solution to the problem.  I assume that something has changed with Gmail's use of TLS and Mercury's Cryptlib library is no longer compatible.  When Mercury switches over to using OpenSSL these sorts of issues should disappear!

The hostname for your mail server isn't valid: (192.168.1.4)

It's a private net IP address which can't be used on the Internet, there must be square brackets not parenthesis, and it should be a proper domain name, not a numeric IP.

/Rolf 

Why not set your webserver to send it directly to xmail.com?

Having a second mail server seems redundant.

Anyway, set your Mercury relay server to be called relay.xmail.com or such and set a Connection Control entry in the MercS config to allow relaying for your webserver.

To switch on session logging please go to Configuration / MercuryS SMTP Server / Logging. Make sure there is a path for a directory for session logging, and check Enable session logging.

After sending the two test messages, remember to switch session logging off again.

The session log will be placed in the specified directory and will contain an exact copy of everything received and sent by the mail server.

/Rolf 

You should be able to convince Windows to prefer a certain gateway or interface by setting a lower metric for it:

/Rolf 

I have a domain mailbox. In the course of investigating another matter, I moved a group of CNM files to a different folder. I've now moved some of them back into the domain mailbox folder. However, when queried by a pop3 client, Mercury reports that there are no messages.

07:43:00.032: << +OK Welcome! 0 messages (0 bytes)<cr><lf>
07:43:00.250: >> UIDL<cr><lf>
07:43:00.250: << +OK unique IDs follow...<cr><lf>
07:43:00.250: << .<cr><lf>
07:43:00.469: >> LIST<cr><lf>
07:43:00.469: << +OK 0 messages, 0 bytes<cr><lf>
07:43:00.469: << .<cr><lf>
07:43:00.688: >> QUIT<cr><lf>

 How do I get Mercury to see the messages?

Regards

Richard

That's great guys, I'm just not sure now how to mark both answers as the answer

> Thomas,
>
> I believe your is a good practice, but for users is more simple to
> have the same account for incoming / outgoing, so this method was
> preferred (also if involves in more workload for postmaster).
>
> Alex.

Simpler makes is easier for the spammers to get your server on the black list when one of your users gets his credentials hacked.  Getting access to your files on the server that contains the SMTP authorization credentials is a whole lot harder.

You can also use group SMTP AUTH credentials that will reduce the workload on the users and postmaster a bit.

>  I'm trying to configure Mercury to fetch my mails send to my dyndns Adress. But it doesn' work at all.
>
> Can you give me some advice, please?

Not sure what you are looking for but DynDNS can forward mail sent to that address using the IP address of the system running Mercury.  If Mercury is behind a router then you send it to the IP address of the router and then use NAT to forward port 25 to the system running Mercury's internal address.

Your ISP may be blocking all port 25 actions and so you may have to have the DynDNS system forward to something like port 587 and set MercuryS to receive on that port as well

[quote user="fabrizio"]when I receive a message from a specific address I would like to redirect to a specific user and forward it to an external email address..[/quote]

Use a global rule to do that (Configuration / Filtering rules).

Have you tried that already?

From Mercury help, Core module configuration:

Username of postmaster  Every system capable of receiving Internet mail must have a user called postmaster, to whom problem and status reports are sent. The postmaster account is usually an alias to a real user on your system, and this is the expectation within Mercury. Enter in this field the username of the user on the machine where Mercury is running who is to act as your postmaster. While it is permissible to have a non-local address as your postmaster address, we strongly recommend you do not do this, since it can create real problems and mail loops when the remote machine is unreachable. This setting is mandatory - Mercury cannot run properly without it.

OK, blind as well as dumb.

Found it just after posting.

Installing WinPMail and Mercury/32 for multi-user standalone mode

Your right, Thomas, I forgot to add the session log.  The reason was that I couldn't find a file for any of the failed messages, only successful ones.  As you can see from my follow-up post, I may have found the problem.

GordonM

Adding custom header lines with a "content-type" to the mail only seems to work if I use the AREPLY.CFG method. While this does add more options, it is also more error prone to setup for the user. (The thread you referenced also mentions the "Web Tools for Mercury 32". While they might work great in some circumstances, they do not work at all if the mailbox directories are on Novell NetWare, i.e. Mercury in eDirectory mode.) Using AREPLY.CFG also requires us to switch our SMTP and Core server from MERCURY.NLM to Mercury32 (though we need to do this anyway).

If I use the standard AREPLY.PM, the text is just added as the content of the e-mail, I wish I could set a content-type somewhere.

Greetings

Markus Borst

Found the problem: Not the new MercuryD.dll causes the crash but polling the hotmail account itself. Polling the hotmail with the original dll causes Mercury to crash as well. Maybe you can pass that to David. If he needs anything from me to debug/reproduce this, I'm more than happy to help...

Konrad