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
> Sorry for taking a long time to respond. > > > I think I understand now, but here is the file you requested Thomas. > I'll wait till you have a chance to look at it before changing > anything. Let me know what you think and what changes need to be > made to the postmaster account.
Here's some comments about your Mercury.ini file. I've removed the parts that I did not want to comment on.
[General] myname: bucataruserver # Canonical name for this server timezone: +0000 # Time Zone to add to date fields file_api: 1 # Use the file api instead of queues mailqueue: C:\MERCURY\QUEUE # Where mail should be put for delivery smtpqueue: C:\MERCURY\QUEUE # Where the SMTP client should look for mail newmail_path: C:\MERCURY\MAIL\~N # Where to find the users' WinPMail mailboxes.
The entry under myname: is the name of the server. This means the maiser and postmaster user the postmaster@bucataruserver and maiser@bucataruserver email addresses.
Really bad. The domain shaw.ca is considered local and you'll never be able to send to anyone at that domain. The at least should be changed to
[Domains] shaw: shaw shaw: local.shaw.ca
and alias all of the accounts you are receiving with the address user@shaw.net to user@local.shaw.net Personally if you do not have a domain I would use the same domains here as you did for the myname: entry. You must alias any address you receive though.
Might also want to go to and get one of the free domains and use that for the system.
> > As for what I'm trying to acheive Dilbert's, I want mercury to > download my e-mails, store them, and deliver them to my client > computers, which has already been achieved. Later on I might add > webmail, but for now I'm good to go. You have to understand that I > don't even know what real data there is to offer. I'm am so new at > this that I can barely navigate the menus. It's a miracle I got this > far and largely due to the great support here at the pmail > community. > > > Thank you to everybody who took the time to answer my questions. You > have all been of real help, even though some of you may have guessed > :) > >
You are THE MAN! I am up and running now! I knew I was making some noob mistake.
I was inspired to post here by this thread, http://community.pmail.com/forums/thread/7695.aspx, that I found by a google search when I first starting working on this problem. And it was you that had helped that thread's parent.
In order for MercuryB to work you need the file mercuryb.htm in the root folder of your installation. WIthout it the first page doesn't show, and comes up blank.
If the does show a blank page, your missing the directory MLSS directly under the root path, or you're missing the files therein. To mend your system, you can unzip the m32-462.exe file and extract the MLSS directory, and all should be fine.
[/quote]
Yes, only a blank page appears.
But there ist that MLSS directory (whith all the files in it) and the mercuryB.htm in the root directory.
I would setup a FORWARD file in one of the mailboxes forwarding to the other email addresses. You have to make sure you have turned on the file based forwarding in Configuration | Mercury Core | Advanced.
It would be interesting to hear if someone is running GrayWall 1.1.0 on Win98SE without having these problems. There are some differences in the Windows API between the Win95 and WinNT generation that can cause unexpected errors.