thanks. I've checked some of that and will keep digging.
 
assuming it's a process within mercury, would turning on some of the logging options tell me where/how the redistribution to multiple users is occuring when the message with a specific address comes in?

and get 4.52 'cos it stops nasty people taking over your server if you have 4.51

I see.

I understand how to create and use a filter .rul file but how would you include the instruction to respond with a auto-reply template and forward the original file to the intended recipient? Can anyone provide an example of this please?

I cannot see any examples of this in the Mercury documentation.

.... or mouth I would hope [:P]

Thanks Bart.  Will give it a try.

Thanks. . it works, and it's far easier to edit list properties with a text editor, and from another PC!

 However, you must restart Mercury for it to be picked up.

It might be worth mentioning this in the next docs. 

[quote user="tuaris"]

How can I prevent mercury from generating delivery failure notifications for non-local users?

See the following: http://www.backscatterer.org/?target=backscatter 

[/quote]

Make your domain a domain type account in the domains setup and then set aliases to a local domain for all good users.  

For example, suppose you have the domain example.com.  You domains setup would look like

[Domains]

server : server
dm=example :  example.com
server : local.example.com

where example is a local user account.  Now all mail for example.com goes to the user example.   You can now setup alias for the users so that tuaris@example.com goes to tuaris@local.example.com instrad of the domain account since the aliased are processed before the domain.

 With this setup everything for the domain example.com is received, nothing is rejected.

 
That said this is a pain in the rear to manage and rejecting the non-local users at the MercuryS server is a much better idea and is what is desired by the people at backscatter.org in the first place.  This is very difficult to do in a large corporate setup using mail gateways in multiple world-wide locations.  There is no way in the world that the corporate mail gateway server will ever be able to maintain a complete listing of the users on all the internal mail servers so that mail for bad user rejected at the local server may or may not bounce back to something other than the original sending system.

Update.

My ISP uses standard headers. I've made the recommended changes so I'm not rewriting the X-Envelope header. It works perfectly.

Many thanks again for all your help. 

Thank you for your answers.

[quote user="Keith Urry"][quote user="Thomas R. Stephenson"]

This is somewhat of a OOPS since this was never added to Mercury/32  This was just discussed in the testers group and David said this was easy to add and will probably get into v4.5x.Wait for the next version and check it out,

[/quote]

 Thanks Thomas. Unfortunately I can't wait - I need this to work right away. I'm thinking of cobbling something together using the command-line tools from the NLM version (makembox etc). Is there any reason these wouldn't work with mercury/32?

Keith

[/quote]

Don't see why it would not.  These are only working with the Netware host to create a mailbox and once the mailbox is created them Mercury/32 can use it.  I do not know how many users you have but you may be able to use an alias as well to forward the incoming mail via the MercuryS.NLM.

[quote user="Addis"]

Hi,

 I'm running Mercury/32 version 4.52 and I'm getting the following errors on MercuryE

Network write failure during data transmission to xxx.xxx.xxx.xxx

TCP/IP error during processing

It is causing about 50% of all mail to fail when sending, Mercury doesn't seem to retry either.

Could someone please suggest what may be wrong?

Thanks
 

[/quote]

Hard to say what is going on, we need more info.  You need to turn on session logging in MercuryE and see exactly what is happening between MercuryE and the receiving servers.  That said, if you have a randomly assigen IP address I really think you'll find that there are servers dropping connection because this is not a fixed IP address.

afaik, mailing list signatures only work with plain text messages and not multipart boundary ones.

Further to Peter's reply, here is what the Mercury help file says about list title and the From: field:

List title  Every list must have a title -- a descriptive name that Mercury will use to form the "from" field of messages sent to the list. Try to keep the title short and descriptive and avoid international or accented characters. On rare occasions, you may wish to include address details as part of the title (Mercury usually adds the proper address to the list title automatically): in this case, you should ensure that the address you enter conforms to RFC822 addressing rules and includes a fully-qualified domain address appropriate for the list, then check the control labelled Is a full address next to the list title. NOTE: This feature is extremely specialised and is not normally required; because it can cause problems with mail delivery, we recommend that you only use it if you are very sure of what you are doing.

I'm glad you have this sorted.

Sending separate attachments dates back to earlier standards, and the default for new installs changed some time ago to embedded attachments.

Nope, no limit on the user count.

Restart, and if it doesn't help, send me your ini file privately and I'll have a look.

[quote user="Francisco6x"]

But, how to configure Mercury to receive localhost email from Thunderbird?

Thank You, Francisco 

[/quote]

If you are running the MercuryS SMTP server then you tell Thunderbird it as the server.

UID calculation in MercuryP and MercuryI have been overhauled in the upcoming release.

> Thanks for the help, your instructions were clear and worked for me.
> Now I am trying to determine a way to mass populate some of my
> larger mail lists, hopefully I will find it soon. The config file
> itself doesn't look formatted in a way this would be easy with an
> editor. If you know of a way to mass populate a mail list, I'm all
> ears.

Here's a utility from James Haley that makes this pretty easy.  I can't pass you a URL for his site since the one I have does not work.  I can provide a copy of the ZIP file though. It should be attached, if it is not contact me directly.

BuildMLF is a freeware utility program for use with Mercury Mail.

BuildMLF builds MLF files from text files.  In Mercury Mail, MLF files hold information about people subscribed to mailing lists.  

If you have previously used LIS2MLF for converting text files to MLF files, this does the same thing but adds some additional functions.  

This program is free, on the condition that you help support Mercury or Pegasus Mail. If you find this program useful, you use Mercury extensively and have a interest in seeing its success continue.  Here are several ways you could support Mercury and Pegasus Mail:  

* Buying a Pegasus Mail or Mercury Manual
* Not using Pegasus Mail or Mercury for uses against the Terms and Conditions, such as sending unsolicited bulk e-mail.
* Helping other Pegasus Mail or Mercury users.
* Writing and making available your own Pegasus utilities.

>
> Thanks again,
>
> Travis Wineinger  

OMG how simple it can be! I've noticed that i can also remove the filtering in global filtering rules.

It works like a charm! We are most happy now!

Thanks for that, Pingu. the page is now bookmarked :)