Is there any tutorials out there to set up mercury to run as a mailing

system, that is not local? What I'm aiming to do is take my domain so I

can create emails for others, as in, not just local can grab it. I want

it so it is similar to sending/recieving lets say, from one computer,

to another computer, etc, while still being pretty secure (Aka not smtp

sending mail unless they login first, something like that.)

Like it was said, it's the same as running locally and the manual is quite good about setting up Mercury/32.  The knowledgebase at http://kbase.pmail.gen.nz/mercury32.cfm provides a lot of help as well.  Here's a few of my recommendations.

1.   Always run any MS Windows system behind at least a NAT router.

2.   Always run some sort of firewall so that you have some sort of control over the programs sending outbound mail. [This is a case of do as I say not as I do though since I'm not currently running a firewall. ;-)]

3.   If you are planning on hosting other peoples domains I would recommend using "Domain" accounts where the people on the outside would pull their mail using something like MercuryD from your system.

I use GoDaddy  for three of my domains and I have a fixed IP address so it's quite simple to me to setup the MX hosts.

[quote user="GordonM"]

1. Can I associate several aliases with a single Mercury user account (so far as I can see, there is nothing to prevent this),?
2. Is there any practical limit to the number of aliases that can be associated with each Mercury user account?
3. Can aliases be subjected to the Mercury Filtering and Content Control capabilities (it would provide considerable flexibility if alias-addressed messages could be individually re-directed, or modified in some way by the filtering process)?[/quote]

Short Answer: 1. Yes, 2. No, 3. Yes.

I am sure there are some overlapping tests.  It may be time to tidy things up.  Thank you for the suggestions.

Gordon

Wow......

now it's ok

that was my problem -_-"

I dont know about local/non-local

thank you everybody for helping

Is there a way to disable the vrfy and/or expn commands in

Mercury/NLM 1.48. . .what line should I add to MercuryS in

mercury.ini.  Yes, I know I should upgrade to Merc 32, and I"m in the

process of doing that as I get time, but right now I'm trying to get my

isp (state of Utah systems) to unblock port 25 so we can do

authenticated relaying, and they won't until I can disable these

commands.

The EXPN is not implemented in either Mercury or Mercury/32.  The VRFY cannot be disabled in MercuryS.nlm as far as I know and I've been running it since it came out and still do.  You can of course run Mercury/32 delivering directly to the users if you wish.  You do not need to shut down MercuryS.NLM but you'll probably have to swap domain names. 

I'm currently running Mercury/32 in front of Mercury.NLM pushing to the MercuryS.NLM host.  I also send via MercuryC.NLM on the server.  I use a simple BASIC program and a batch file to do this.

[quote user="Carsten"]

What does Mercury want to know here?

[/quote]

Your password. [:)]

If you use IMAP in Pegasus you will get the same question.

If you cannot remember it, have a look at the PASSWORD.PM file in your users new mail folder.

If you really did leave it blank, you should set one, then you can tell Tbird to remember it, and you can forget it again [:P]

It's no problem when someone asks intelligent questions, rather than "how do I set up Mercury" [:)]

FWIW you can add the direct SMTP receipt of mail (just forward port 25 to the merc machine) without altering your current ISP setup (I presume you currently receive with MercD?)

If you get a domain name (or a free dyndns or no-ip one) to point to your external IP then you can send and receive as you@your.isp.com or you@yourdomain.com etc.

Best of both worlds.

[quote user="Peter Strömblad"]

Out of curiosity: Why do you detest RDP?

[/quote]

I have found it very slow, and lacking in configuration options.

By contrast ultraVNC is very easy to adjust the encoding & compression among many other options like screen scaling, colour depth etc so it can be tuned to be very fast over most connections (I have used over dial up quite successfully). It also includes a remote file transfer facility & is dead easy to put through an SSH tunnel.

The "single-click" executable version (~160k one .exe no installation, I have it on my webserver for people to click on [:D]) is runnable by 'support clients' to call back to me, bypassing firewall configuration issues if I had to try and connect to a server running on their machine.

I used it to fix an email issue on a client's laptop on a public wireless link in North Carolina from my lounge room in New Zealand :)

Over an enterprise, or Local LAN, RDP may be perfectly adequate, but it doesn't fit my needs.

Thanks...  Missed that !

But what happens if that message is finally delivered. Here's the

situation: We are currently set up to retry a message once an hour for

10 times (10 hours). Our VERP, as previously mentioned, is set to three

times in a week. If I understand the above correctly, after three times

of trying to deliver, it will VERP. What happens if the message is

delivered on the fourth, fifth, etc. time? Does it 'un-VERP'?

Nope, the third bounce blocked it.  It never gets anything from a successful delivery.  It's only tracking failures.

It seems to me that the retries and the VERP settings need to be in

sync with each other. For my case, if I want to capture all the

addresses that are not delivered in three days out of a week, I would

set it to 30 (three days times 10 attempts a day). While this would not

be perfect, it would be a lot closer. Right?

That's probably a lot closer.  However with a really good mailing list I would not expect so many temporary failures.  I really would set MercuryE to timeout in not less than 600 seconds (you might get by with somewhat less but 600 is a good place to start) to ensure that you are not simply trying to deliver to busy servers that timeout on you.  I use 300 seconds currently and almost never get one of these multiple delivery failures and then one that succeeds.  If I get a VERP bounce it's either because the the account is blocking, there is a problem on the server or the account is bad.  The account blocking and mailbox too fill are my most common errors.

Is it possible to delete the email with our external daemon, when we append the mail to another inbox?

 Yes, no and maybe.  MercuryI does not support deletion of a message via IMAP4 when there are multiple connections.  It will be marked for deletion but will not actually be purged until the last connection is closed.  You of course can use a daemon to delete the actual CNM file but I'm not all that sure how the IMAP4 clients will handle deletion of the message file without cache corruption of some sort.

[quote user="kfreeborn"]What does Delivered-to do? [/quote]

Generally this is the way an ISP passes the original SMTP RCPT TO: address to the body of the message when delivering to the users mailbox.  Every ISP that provides a "domain" type POP3 mailbox should do something like this so that the receiving POP3 mail client can separate and deliver the messages based on the original SMTP addresses.

Well, that's a lot easier than the way I finally figured out. Mercury writes the VERP address and the actual TO: address in the logs, so I was searching for the VERP address and then searching for the message number to find the e-mail address.

I like your way better!

Thanks.

[quote user="Barius"]Hmm, who's definition of 'soon' are we going by here...?[/quote]

Where did you get 'soon' from?  Did you read the original thread?  Nobody made any promises of when it would be done.

Not that I know off Thomas. But I fully agree something must have happened, since my current situation is Merc/Peg's default behaviour !

On another location, users have RF rights on their PXMF.INI as well, but are able to change (and save) the extended features in Peg.

But I'll stop bugging you, this is clearly not a Merc/Peg problem, but a filesystem thing.

Thanks for your help!

Ron

PLEASE add IMAP filtering

Please knock it off.  He's answered you a long time ago and knows you want this.  If you want to do this put it into the wish list forum that's ok since I do not follow that one.

Interesting Morten,

Among my utilities (downloadable here: ) you can invoke delay.exe for x-number of seconds prior to running loader.exe

Have a look at http://community.pmail.com/forums/post/4965.aspx

Someone wants to know what your favourite choice of MTA is.  I'm well aware that Mercury is in the definite minority, but I'm pleased to see that it's explicitly represented in the survey.  Perhaps you can add your voices and give a genuine figure on Mercury usage; it seemed a post here (someone please advise the mailing list, too) would provide an opportunity for those not already aware of this.  The URL is:

I can't be surprised that Postfix is taking the beauty spot nowadays.  Two years back it was definitely Sendmail; nowadays Postfix is pretty much all there, copycat as it is; fast, flexible and secure.  But, for sure, Sendmail is still my top choice of power MTA when a Unix-like OS is available.  Mercury is the best I can find for Windows-only or Windows-majority situations.  I would sooner use Mercury on Windows than try to convert an existing Exchange into a usable MTA, either by proxy, modification or fronting using a Unix mailer if clients are all ready to go on Windows direct to an all-in-one piece-of-cake mailer like Mercury.  (If there's any doubt, that's no insult, David, in case you read this.  Mercury rocks and is NEEDED.)

Cheers,

Sabahattin

"Subject:" is not one of the SMTP envelope headers, which is what gets logged.

You could probably use a policy to call a batch file or other program to parse the message body and extract any info you want to a file.