[inigoml]

Originally Posted by Ericx

INIGOML, Thank you for the post on SQLGrey. I'll make that my priority project for Monday. I want to personally thank you or whoever made the wiki for improving spam. It is very well done. I'm sorry if I left the wrong impression.

I uploaded first version, but it has been enriched, corrected and improved by several forum members. This is a colaborative working, so if you can share your experiences, they will be welcomed.

And SQLGrey (or greylisting in general)... ufff... at this moment the holy grial.
Anyway, you have to understand perfectly how greylisting works and some related minor problems. There is only to minor (for me) problems:

1- First mail from a user to a local user takes longer than before. Depending your greylisting configuration and remote MTA retry time, from 5 minutes to several hours. Tipically, no more than 30 minutes. But ONLY first time.

2- Some old MTAs do not work well with "temporaly unavailable" response from your server and treat it like an "unavailable" and mail is bounced to sender. But this is very unsual.

However benefits are evident, and avoiding most of spam is wonderful.

Since the wiki and forums are community supported, I was nervous about making those changes to my production server. I'm using the commercial version of Zimbra on a Commercial Version of Redhat; which Zimbra recommends. I even received a discount from Zimbra for using RHEL4 instead of Suse, which I normally use. My comments are more for the Zimbra team to officially put something out there for spam management.

Zimbra employees read everyday this forum, and they review documents created by members. But I understand perfectly you. When working with commercial software you are expecting some "formal" support for these kind of modifications. But Zimbra is commercial... and an opensource development, so there is a shared way to make things better you will not find in commercial software. For example, Microsoft wouldn't let you customize exchange the way Zimbra let's you customize its product.

Spam is killing me and my users. I've spent more time trying to tame spam than I have all the other tasks combined - including testing and migrating from Exchange (which went extremely well!)

Yes, it's probably one area where zimbra development team should improve the product. However is quite easy to do it. I'm sure for next release (5.0) we will see some changes in spam administration and functionality.

I have never used spamassassian before, but I felt confident that I could figure it out. Wrong! If it weren't for the posts made by the Zimbra community, I would have never figured it out.

Do you remember McAfee antispam? It's spamassasin based.

Even a simple admin zimlet that will allow System Admins to manually edit some of the config files would be great! That should not be too hard to do. I'll even try to stub one out and test it and post it on the forums if someone can give me a list of files.

Ask for it! I assure you that bugzilla works! I have requested some new functionality for Zimbra and, sometimes before, sometimes later, it's finally added. For example, http proxy support for Outlook Connector will be included in next minor release (4.5.1), and I asked for it one month and a half ago.