How can I fix zmtrainsa?

[ms2k]

I have a new installation of Zimbra 4.5.4GA on Ubuntu 6.06. After 1 week of running with heavy activity, I can see no learning of incoming spam that gets moved into the Junk folder. Zmtrainsa is automatically configured in cron and runs each evening. However, upon examining the "spamtrain.log" output file, I find this output sequence repeatedly listed for every instance that zmtrainsa has run:

[] ERROR: can not find account spam.urusg7r83s@server.domain.com
[] ERROR: can not find account ham.zev0aqcd@server.domain.com
Learned from 0 message(s) (0 message(s) examined).
Learned from 0 message(s) (0 message(s) examined).
bayes: synced databases from journal in 0 seconds: 1485 unique entries (3405 total entries)

I have also run this manually and got the same results.

The two training accounts exist on this server and are active accounts. Why can't the commands in this script find them?

Also, the three dspam-related cron jobs are marked as inactive. Is that normal for Zimbra 4.5.4?

Thanks.

[phoenix]

DSPAM is disabled by default in the current version of Zimbra, search the forums for details on how to activate it.

[ms2k]

Does this mean that I cannot get zmtrainsa to function until I get DSPAM activated first?

[phoenix]

If it says it can't find those accounts then it can't find them. Use zmprov to print the details for those accounts and see if it can find them.

[EDIT] You should also search the forums (and the wiki) for details on how to list active the spam/ham accounts.

[ms2k]

Thanks for pointing me in the right direction. This installation was originally built under the domain "mail1.company.com". Since our MX mail domain is actually "company.com", after the Zimbra installation completed, I added a second domain "company.com". I then renamed the admin and spam-training accounts from "@mail1.company.com" to "@company.com", then I added user accounts to "@company.com", and finally deleted the "mail1.company.com" domain from the mail server. This is apparently where I screwed up the association to the spam training accounts.

The zmtrainsa script is still seeking the spam-training accounts at "xxx@mail1.company.com". I tried to edit the zmtrainsa file but cannot locate where the change should go.

How can I change the domain name for where the script looks for the training accounts without having to create a new domain to match their actual full account names?

[phoenix]

Check the spam account names with

zmprov gacf | grep Spam

you can then use zmprov to set the fields to the correct names.

[ms2k]

Okay, that was very helpful. I used "zmprov mcf" to change the training accounts to their proper domain. Then I did the following:

-Sent a test message with a phony email address to one of the Zimbra accounts
-Logged-in to that acoount, found the phony message, clicked on "Junk" to move it to the junk folder, and logged-out of the account
-Ran zmtrainsa
-The results no longer show that the 2 training accounts cannot be found
-However, I still see these lines:

[] INFO: Total messages processed: 0
[] INFO: Total messages processed: 0
Learned from 0 message(s)  (0 message(s) examined).

Shouldn't my new junk message have been included in this process?

Does it appear that the learning is still not functioning?

[phoenix]

That's not necessarily wrong, it shows that DSPAM may already know about that type of message and doesn't need to 'learn' from it. You'll find that spamassassin and DSPAM only learn from stuff that's new to them. Keep an eye on it for a couple of days and see what happens to your spam.

[ms2k]

Sounds good.

I've enhanced spamassassin with SPF, Razor, and Pyzor, per the wiki.

However, I never figured out how to activate DSPAM. And the three dspam-related cron jobs are marked as inactive, as it installed with version 4.5.4.

Do I need to activate DSPAM, and if so, how? I wasn't able to determine this by searching for the steps in the forums.

[phoenix]

It's in the first post of this thread - the initial thread on setting up DSPAM. The file you want is amavisd.conf.in, you'll see the bit you need to change. Don't forget that while dspam is disabled you'll need to make that modification on every upgrade.