In that case you would normally get a rejection message from the server, but from your description it appears that the connection is blocked at networking level. But it could be that gmx are a bit over-ambitious in their anti-spam measures. Try contacting them about it, it might work.

/Rolf 

what values do you recomend?

Neither of these are material.  A TCP/IP time out of 300 seconds in MercuryC is a good place to start.

It would also pay to implement an Outgoing filter rule to prevent mail from internal users ("user@sob.intern" or just "user" etc as per their mail client setting) from being sent out to the world.

These would get rejected by anyone checking for MAIL FROM validity (most servers) and any bounces or replies would have nowhere to go.

You could set a rule to delete and/or a reply with template if users need reminding [:)]

You need to upgrade the daemons as well - a lot of changes to the daemon interface occured between 4.5x and 4.6x.

Always make a backup of your system setup before doing an upgrade, so you easily can downgrade if something should arise.

[quote user="Addis"] The problem is that our ISP is rejecting some mailings with 452 #4.5.3 Too many recipients.[/quote]

Start using mailing lists within Mercury. Set to enable VERP processing, and the list submission is split into one message per subscriber. If you enable MercuryB your users can handle the lists via the built in web interface.

Thomas;

Thank you.  While it took a bit to set up this is going to work well for the time being.  Eventually we will turn off acceptance of email for invalid local addresses, but for now this is the answer I was looking for.

Thank you for your help,

Brad Johnson

Hi, I have installed on my Windows XP PC an old Mercury version

(4.01). I want to upgrade to 4.62 version but I have another problem.

One

of Mercury mailbox file is about 2Gb and I noticed that Mercury 4.01

doesn't work correctly. So I tried to deleted mail from Outlook but the

folder doesn't change size. How can I do ?

Install Pegasus Mail on the Mercury/32 server using the same mailbox structure as Mercury/32.   That is if Mercury/32 is use c:\mercury\mail\~n in Configuration | Mercury core "Local mailbox directory path" then Pegasus Mail should be installed to c:\pmail and use c:\mercury\mail when asked for the directory.

You can now access the folders and compress the folder to remove all deleted space.  FWIW, if you install WinPMail Public beta 1 it comes with a utility called mbxmaint.exe that can do this for any mailbox directory you specify.

This (internet name for this system, and local domains) has unfortunately always been rather confusing. Mercury uses the internet name for this system to shape outbound system messages. That fact often creates a "conflict" in response to the answer if MercuryS host (announce myself as) is not entered. The help file is also quite vague here, since the help for MercuryS announce myself as refers to "value in the Mercury My Name field" - that field doesn't exist - but I guess David refers to the Internet name.

What we have done is the following:

Internet name is: mail.praktit.se
MercuryS announce myself is: mail.praktit.se

DNS domain is praktit.se
Host is mail.praktit.se
MX pointer is set to incoming gateway (currently another host)

Domains section therefore read:
mail    praktit.se
mail    mail.praktit.se

The problem is, the bounce messages, that will not return unless the domains section has both entries.

I would have preferred if Internet Name was split into a global setting of Host name, and, server domain be specified separately - but it works the way it is, though ... not clear enough.

The EuroUnion is something else. We have a monetary union (Euro), passport union (Schengen) and the European Community (EC).

The EC doesn't legislate, it is the job of each nation. The EC Council issues directorates, that the countries adopt (to different degrees).

I haven't investigated if the logs are sufficient, but as I recall it they do not. I will meet with Rolf L. to discuss if we can pull the connecting information in a more timely fashion. Since David also said he would re-work the logs I've put this on hold for a more thorough discussion among the testers.

Edit: But in any case, within the EC only ISPs (defined as anyone providing a service for anyone else, in this case an email service for a domain they do not own themselves), have to store this information for x nbr of months.

 Since after patching my Xp home with Service Pack3 I can no longer start Mercury as a service.

Not at all sure what to tell you.  I am running Mercury/32 v4.62 as a service with NT Wrapper Pro on two WinXP SP3 systems. One is Pro and the other MCE.  Could be a problem with the home edition though since I've found it flaky with TCP/IP. 

11:43:56.411: --- Wed Oct 29 11:43:56 2008 ---

11:43:56.421: Connect to 'mail.domain.com.au', timeout 30.

[quote user="drossall"]

I've used Spamhalter for a bit with Pegasus Mail, but never with my Mercury/32 system. I can't find a description of what it actually does.[/quote]It just adds a header to spam mails that you can set up a filter (in Mercury or the client) to perform what action you want, typically moving to a SPAM user for review/deletion.[quote]I believe that it probably sends the passes to the intended recipient and the fails to a special mail account that I create. Then my mail users can forward wrong passes to a second account (to train the database).[/quote]I have 3 accounts setup, CRAP for Spamhalter hits to be

filtered into via a global filter rule, SPAM for sending missed mails

to as corrections & NOSPAM for sending False Positives to as

corrections.[quote] Fails can be forwarded back to the intended user (if I can tell which user that was, because not all mail has the recipient in the header as opposed to the envelope).[/quote]That can be an issue if you get a lot of newsletters etc. I generally use the smtp log & timestamp info to pin down the offending ones[quote]

As I don't have a large collection of spam to hand to train the system, I'd also like to copy my words4.db3 database from Pegasus Mail and use it with Mercury.[/quote]Never tried but should be possible, AFAIK they are the same[quote]

Can I find documentation to help with all this, and can I do the forwarding in the way I have suggested?[/quote]The doc is installed with spamhalter or at ararat.cz (from memory) also quite a few posts on the forum.

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.