It seems to be an error generated directly by mercury.
The message headers indicate:
From: postmaster@[203.26.##.##]
To: admin@[203.26.##.##]
The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem:
*** Error connecting to primary server '210.9.177.134'. 556 Too many invalid recipient requests. Closing connection.
This is Mercury/32 message back to you reporting it could not deliver the message and the error message sent by the mail.universalmagazines.com.au server.
Now if there were only one RCPT TO: in this particular message then I suspect that they are storing the IP addresses of the connecting hosts that send to
It was a filter. The original address does not exist on our system and a filter is used to move the message with that address in the To: and Cc: fields to 'user'.
So, each time Mercury/32 encountered it, the filtering rule kicked in.
Man, another one! D'oh! Thanks a lot for your help.
[quote user="lieven23"] If I want to run Mercury it loads for a second then it closes [/quote]
Locate Mercury.Ini, and remark the modules loaded, so that only the core loads. Try then to start Mercury. Mercury should not close itself immediately unless something is interfering and telling Mercury to close.
Doesn't look good, I'm afraid. With invalid entries for local user, default user and postmaster there is no place for MercuryD to deliver the mail so it will not be saved - just as you probably already realized. I hope all the messages were spam...
By the way, with a correct local account entered as local user there is no need for a default user in MercuryD as everything will be delivered to the local user anyhow.
I kept fiddling and it seems that, despite there were no real configuration issues, MercuryC wouldn't work while the end-to-end client worked like a charm from the first unconfigured start. Odd but... it's fine to me for now :)
Thanks for pointing me out that there are actually TWO distinct smtp client daemons in Mercury.
where within Mercury I ammend these settings so that it makes use of spamhaus and spamcop?
Configuration | MercuryS | Spam control Here's my blacklist configuration file that I use that you can copy to Notepad (or any other ASCII editor) and save to the Mercury directory to see how this is done. You can use tagging for awhile ( I watched for a couple of months) like I did for each list until I was sure there were no false positives. If you use tagging you can use a Mercury/32 filter to move these messages to a spam user account. I created the user "blacklist" and filtered mail with the tags to that user.
# Mercury/32 SMTP server block query definitions data file. # Mercury/32 Mail Transport System, Copyright 1993-2006, David Harris.
Begin Name: SpamHaus-Zen Enabled: Y QueryType: Blacklist QueryForm: Address Hostname: zen.spamhaus.org Strictness: Range 127.0.0.2 - 127.0.0.8 Action: Reject Parameter: Blocked by SpamHaus.org See http://spamhaus.org for removal instructions End
Begin Name: PSBL Enabled: Y QueryType: Blacklist QueryForm: Address Hostname: psbl.surriel.com Strictness: Normal Action: Reject Parameter: X-Blocked: by PSBL See http://psbl.surriel.com for removal instructions End
Begin Name: SpamCop Enabled: Y QueryType: Blacklist QueryForm: Address Hostname: bl.spamcop.net Strictness: Normal Action: Reject Parameter: Spam blocked see: http://spamcop.net/bl.shtml? End
Begin Name: SpamHaus Zen PBL Enabled: Y QueryType: Blacklist QueryForm: Address Hostname: zen.spamhaus.org Strictness: Range 127.0.0.10 - 127.0.0.11 Action: Reject Parameter: X-Blocked: by SpamHaus.org PBL See http://spamhaus.org for removal instructions End
---------------------------------------------------- cut here ------------------------------------------------------------------------
[/quote]
Just out of curiosity why do you use normal strictness for the Spamcop and PSBL lists and ranges for spamhaus?
Another question : Where are the Emails, polled by MercuryD stored and
in which format ? While testing I remarked that my Emails were received
on the WHS but I couldn't find where they were stored in the meantime.
While the mail is being downloaded by MercuryD it goes to the scratch directory. It you are simply using the local username in the "Local user" field then it put into the local users account using that username. If you leave the local user field blank or use a user@domain.com address it is passed to core for processing. Mail is stored in RFC 2822 format in a *.CNM file in the users local mail directory.
FWIW, have you installed the MercuryP (POP3) or MercuryI (IMAP4) hosts so that Outlook has something to talk to?
OK.. but this would allow me to move messages to specific folder based on criteria I chose ??
Probably, I really do not know any more than what David has stated in this forum.
Any idea when we may see this ?
Absolutely none. I work around this in Pegasus Mail by filtering to directories and then having the user attach the directories via "Add mailbox to list". Same thing could be done by filtering to a username and having the IMAP4 user mount the other user via IMAP.
Acording to RFC 2049 appendix B, pt 7 and 8, it clearly states that to be MIME conformant, the BNF must be preceeded by CRLF, as part of the BNF itself.
That said, Mercury could possibly be made more "tolerant" in this respect.
Thanks to you all for the assistance. I got back on to the mail host this morning who told me I just needed to reboot the machine, when I explained that hadn't work, with a little reluctance he went away to check on the thing. In the end the file at his end had become corrupted with two funky characters in one of the headers. It is now fixed and I've got several thousand spam mails to compete with... I'm not so sure fixing it was that great now... lol