The SMTP connection died, possibly a bad network link.

Does it work from your LAN?

Can you test from a SMTP client outside your LAN?

I recall using emails to give poll / pause commands to various modules using MercX, maybe this could be used for your purpose.

It was a long time ago on dial up, so the details are fuzzy, but should be in the MercX docs.

Edit: there is a bug with MercX in the 4.72 release, such that on startup some other modules are started in paused mode, but I suppose that could be worked around by sending unpause commands as above by a startup script. [:)]

[quote user="dilberts_left_nut"]

Where it has the address of your ISP server, put the address of your Mercury server.

[quote]it does not recognize smtp.my domain[/quote]

Does smtp.my.domain resolve to your Mercury box (locally)?

If not, just use its (local) IP address.

[/quote] OK,,, thanks for all the help... I was still having probs and I finnaly found the "generate test messages" option under file and it created a FF Error... I must of messed the last install so I reverted back to a previous install and all is fin with MercC...

Thanks

Thanks a lot but i'm looking for a mercury32 daemons c++ examples..

the sdk documentation is very nice but not enough for a novice :)

regards

VG

If you put that rule in the standard filter rules instead of the outgoing rules it will be applied to all messages.

To exempt incoming messages you could change the trigger from 'Always' to matching on your local domain in the sender address.

Hello all,

 I have just moved my Mercury32 to Ubuntu 9.10 with wine. All looks good and seems to be working, but, when i send a email i get the following in SMTP client.......

"NS Error: resolv: sethtent() could not open hosts file etc\hosts, errn

NS Error: resolv: gethtent() could not open hosts file etc\hosts, errn"

This repeats a few times, then it says...."processing job MO0000?? Resolved MX for '??????.com'"

Then email sends fine, it happens on every email being sent.Emails being recieved are processed no problem.

Thanks for any help,

Troy

In our local network we using Pmail and Mercury also for transmitting of local mails. To do so I have to type only the initials of an user e.g. "jm" for Joerg Mueller and the mail finds its way.

But for sending mails to the internet the sender name would be: "jm@company.mbh", where "jm" as well as "company.mbh" is wrong. The synonym.mer file contains the real valid internet e-mail addresses of each user in the following format:

j.mueller@company.com == jm

So mercury knows what "jm" means, and it works. 

I have also tried to achive this goal by Alias Names, but without success. I never understand the difference between synonym and aliases.  :-)

So far.

Regards from Rostock/GERMANY

Joerg

is authentication a ESMTP feature?

You should stop returning fails for spam.

This is backscatter and most of the time goes back to forged addresses.

It will get you on some blocklists.

Also, bounces should be done at SMTP time and this mail has alredy been accepted via SMTP by your ISP.

Solved [:)] - I've been at this all afternoon.

I took out the modules one at a time and traced it to X. Then I found that turning off the Win98 dialling functions resolved it. I'm not sure why they were on, and even less sure why changing a network adaptor would lead to their causing a problem.

Is it possible to learn if PM can be set up for use on the

Verizon Android ?

Nope. That format is required by RFC821.

Failed RCPT restriction is per SMTP session. If the short-term blacklist option isn't switched on previous problems won't affect the next send attempt (and if it is the IP blacklisting will expire after 30 minutes). Could it be that there is some other issue with the settings in her email client?

/Rolf 

I assume that you want to prevent out-of-office replies being forwarded to the whole mailing list. I haven't tested but presumably you can find something common in these messages (perhaps sent by outlook/exchange and containing certain words) and build a filter to delete them rather than deliver them to the mailing list.

As DLN says. 

[quote user="safpiper"]Due to a change to uncapped ADSL I seeming cannot use my previous providers of smtp services.[/quote]

Have you changed provider? Are they not offering a different relay?

Thank you, Paul.  I had made these assumptions in my design of the policy definitions and associated scripts, but I am pleased to hear this confirmation.

Gordon

That really has nothing to do with Mercury.

It is a Mail Transfer Agent that provides mail transfer services in an efficient & configurable manner.

It is not an all singing and all dancing "groupware solution".

1. Yes. The loader is not required as the service performs the monitor & restart functions. Also a daily restart is not usually required on a recent OS, earlier versions of Windows sometimes had issues with memory management and leaks that a daily restart would overcome.

2. As stated above, a known bug.

3. This could be a result of the user account Mercury is running under. I have been using NTWrapper for some time (since before Mercury could do it) to run as a service and this is working fine, so I have not changed to using the built in service functionality.

Let me check it. I didnt check that part. Thanks.

There is a fine manual that is installed with mercury and contains (mostly) all you need to know about configuring Mercury.

If you then have some specific questions about anything in particular, come back and ask.