[quote] I asked the users to bounce a copy of incorrectly marked emails to the NoSpam address at each site. Unfortunately, the next email from the same source is marked as Spam again. After a few tries the users just stop sending the emails to the NoSpam address and moan at me instead.[/quote]

You have put your finger on one of the biggest dilemmas facing mail admins trying to implement Bayesian filtering in a network - managing user expectations.  I have found this a tricky problem and there are a few different strategies you can try.  Which one works for you may depend of the type of users as much as anything else.  At one site, I have to do all the classification myself because no one stays in post long enough to learn the details.

As Lex suggests, altering the whitelist expiry can help with infrequent mail lists.  Also, have a good read of the Spamhalter.pdf description - particularly the Whitelist/Blacklist section on page 17.

Agree with Thomas on protection measures.

Search this site regarding "web mail" or "webmail" and you'll find lots of pointers to programs:

You can also tell MercS to accept 'firstname.lastname' address variants.

It uses the  'personal name' part of the user definition.

I had the same problem when I recently upgraded to 4.52 and found that if I disabled the "Exit and restart each day after performing daily maintenance" option the problem went away.  I had originally used this setting because 4.01b seemed to have a memory leak on my XP installations which caused Mercury to freeze up after a couple of days.  I haven't yet had this problem with 4.52.  So, that might be something to check.

[quote user="Peter Strömblad"]

We have the same problem, so whenever there is a new version (as a tester there can be a few) I backup the server directory, not the queues, and the pmail.usr file - rest is left alone. Then I shut down the mercury server I'm about to upgrade, check that it is unloaded using both task manager, and file open check - then do any upgrades. It takes less than 2 minutes. Only very few users will see a pop3 connection error due to the upgrade. Normally I do it at 12:20 since most people then are at lunch, whether at home or at the office.

[/quote]

2 minutes sounds very good. Compared to the time, that the regular Windows updates needs, this is really a short time.

I think, the POP3 connection dropouts are not the problem. The only problem I had in the past concerned IMAP connections. Because we work in Netware mode, the users mailboxes are not located on the server where mercury is running. Sometimes we got destroyed folders or hierarchies, when an user is connected by IMAP and I shut down Mercury. It seems that this happens when the user is accessing to a folder in the same moment (moving or deleting mails)

That's why I will do the upgrade today in the evening - on Friday evenings most of the people are watching TV [:D] 

Best regards
Thomas
 

Today the Mercury GUI is tightly integrated with the operating core. When running services you need to unhook a GUI from direct screen calls (such as status windows etc). When David separates the GUI from the core process, there will be methods to create users, aliases, passwords, do restarts, etc by means of hooks into the core, through an API or similar means. Then it is easier to create whatever admin interface that interacts with the core through standardized calls.

The storage of domains etc, is to make it possible to have multiple installations of Mercury, and multiple domains. Today Mercury is based on a flat structure, but domains and users and aliases actually create a hierarchical structure. We have it organized this way today, but I never made a public software for it. A relational sql-database is perfect for this type of structure. Then it is very little effort to take the info to the flat file structure that Mercury is based on.

ok thanks for info.

 i'm using spamhalter and it define the most of them as spam.

[quote user="pbeddy"]

Thanks. I do appreciate the feedback, Thomas.

While I do not want to be lulled into a false security, it is reassuring to compare notes. I wonder how long it will take the virus authors to pick up on this measure and make their "products" "graywall-compliant"?

[/quote]

Not all that long I suspect, they are already delivering directly to the MX host in an attempt to bypass Graywall.   The problem for them is that the addition of the retry does make it more expensive in time to deliver the mail.  It might even make it easier for the operator of the "Zombied" machine to detect something is going on with their system.  The real point is that you still need something scanning the mail for viruses, the fact that Graywall blocks some is just an added extra.

Thanks,  That was the issue.  I've now set up (once I got NAT working over satellite connection... grrr) MercuryS to handle incoming mail and that (including forwarding) is working as it should.  Is it also true that local email won't be forwarded by this method either?

Thanks again.    -Guy 

[quote user="PlayWithFire"]

I am very new to the world of PHP development, but at work i was given a task to bring a PHP application online. The application was developed on the outside, and seems to work, but i can't configure the SMTP server to work.

I'll be honest, i am not even sure where to begin troubleshooting it, but when i am trying to send e-mails, i get an error saying that PHP cannot connect to the mail server.

 When i am in Mercury/32 application, and i try to send mail from there, the SMTP client is unable to resolve the name. So, i used OpenDNS in the SMTP client configuration, and it was able to resolve the name, but it just comes up with "Connection Error" and "Connection error on alternative"

 Can someone point me in the right direction? Thanks!

 

[/quote]

This is not really a PHP problem at all, yuo must first install the correct modules and verify that Mercury/32 is operational.  The very first step is to use Start | Run telnet 127.0.0.1 25 to verify that Mercury/32 MercuryS is up on your system and running on port 25 and can receive the mail.  Until this works all else is a waste of time.

Personally I would install v4.51 over the v4.01 that comes with XAMPP and setup the Mercury/32 server. 

I found it, I was searching only in the config file.

Thank you very much! 

Excellent, thank you David.

Are you on dialup?   If not why not just make Mercury check for mail rather more often I poll about once a minute at home where I have STACKS of bandwidth and a free always on connection.

Not saying that speculation is bad, but the decision is firm and the January turmoil is history.

Pegasus Mail lives on donations. Mercury will soon live on license fees.

With the above comment, I'm locking this thread since the content now is far away from the topic at hand.

Good evening

Thank you very much for your fast answer & your description of steps I can do! I'll go an test it…

Kind regards,
Thomas

[quote user="Rolf Lindby"]

If you block all incoming messages with <> as sender you may block more than you intend to. Delivery failure messages from SMTP servers can have that as well.

/Rolf 

[/quote]

Thanx for that heads-up.
At present I am moving the messages to a black-hole mailbox that I monitor.
I'll keep an eye open for that sort of message before I institute "killfile" :)

Yes, I did. The issue has been resolved. Thanks

Terry

Go to your mercury installation directory and delete the file 'm32pass.dat'.  (Probably best with Mercury not running.)

DNS MX records should contain a host name - that is a name you have set up with an 'A' record pointing to an IP address.