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.

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.