Thanks, Gordon, very useful. 10 accounts is plenty for me, I only need 4.

Chris

Aha - thanks for that.

I have to confess that I am completely in the dark about this.

I have 4 'Move' rules set up. They move messages with specific email addresses to designated accounts. I have looked at all the accounts and none of them contain the eBay message.

I'm happy to leave this as I'm not getting anywhere with it and I simply printed the message that was required and gave it to the person who requested it. However, I don't know what I'll do if someone outside our orgainisation requests a message which is also killed.

The good thing is learning about the Log to concole option - that may come in handy the future.

Thank you for all your help.

[quote user="rogu"]I tried to set up Mercury by following this guide:

[/quote]

I'm surprised anyone can get that configuration to work on the internet!  Read the help or the manual for better set-up.

[quote]I set smtp.gmail.com as my SMTP "Smart" host.

But when I try to  send a mail message to my gmail account this error appears: Error FF servicing queue job# [/quote]

Have you entered your gmail account details to authorise the relaying?

Details here: http://support.google.com/mail/bin/answer.py?hl=en&answer=22370

If you are still having problems, Mercury allows you to see the TCP detail (called 'session logging') which you can turn on in each module's configuration.  But note, this is meant for temporary use only as the log files can get very big, and if you are going to post any logs here, make sure you blank out any password (or encoded password).

Will someone please explain how one interfaces with Mercury running as a service under Win7?

In particular, must I go to the services desktop (UI0) to see it?  How much can be seen and done from the ordinary user desktop (admin under UAC)?

Thanks.

Hey guys! I'm a new comer to this place looking for answers that are related to Mercury.  I'm starting to learn more in here.  

BTW just wanted to say thanks!  

The help was my first port of call but it didn't work on my machine.

However your answer inspired me to look further and if it helps anyone else, just click on the link that comes up when you try and access Help. It will take you to a page where you can download and install the help files.

 I will have another go and hopefully next time my questions won't be quite so green :-)

 Many thanks for all the pointers so far, they helped a lot! 

Warnings about incompatibility have been seen on some Windows 7 systems during installation, but at least in those cases Mercury has in fact been correctly installed and there has been no need to re-install. Then only real problem is that Mercury mustn't be installed in the Program Files directory as it's write-protected in Windows 7.

/Rolf 

You could run an outgoing filter looking for a specific header generated by that client only, and copy it to your user.

It would appear in the INBOX rather than SENT, but you would at least have a copy.

First of all, you seem to have lost the square brackets around the IP address in the local domain definition, it should be [192.168.1.185].

As for replying to received mail, please check Mercury logs to find out what happened. If it was an external recipient it has nothing to do with local domains, anyway.

/Rolf 

[quote user="PaulW"]

[quote user="Vincent Fatica"]P.S. As far as I can tell, it's either Outlook or the MS Exchange server that's providing the info "From: Maiser@... on behalf of ...".  That's not the real "From:" header in the emails.  There's no real consequence (other than upsetting folks when they see it) because replies to such emails go to the "on behalf of" person (who is also named in the real "From:" header).  All that said, perhaps the behavior isn't so bad; Maiser really was the sender, and did send the message on behalf of the person who submitted it to the list.[/quote]

I disagree that Outlook's behaviour is totally neutral.  I had considerable difficulty on my lists with some members' replies going to (and being rejected by) maiser.

I now suppress the outgoing 'Sender: header in a policy.  On a low volume mailserver that works fine, with busier servers a daemon may be better.

[/quote]

Thanks for the tip Paul.  I'll try a policy.  I haven't seen replies going to maiser (yet).  My problem is that the gals who work in the dept office of the small math dept for which I work are alarmed by it and keep harping at me.  They are the ones who use the few mailing lists and they often get replies to their messages.  I haven't the time to track down the offending clients (and am probably powerless to change their behavior).  Yet it's good policy to stay on the good side of those gals.

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