Input Warden Antispam & Virus Protection Extension for Plesk

[papahausa]

@papahausa usually that means that your database credentials are corrupted. You can try resetting them with the command:

// reset the Amavis database credentials
warden --task=contentfilter:contentfilter --default=yes --reload=yes

// reset the SpamAssassin learning database credentials
warden --task=antispam:learning --default=yes --reload

After you reset the credentials you can to some manual training from the command line to see if its working correctly:

How can I perform Bayes training from the Warden command line interface? - Knowledgebase - Danami

done.
i hope this solution can help for other.
@danami Thanks.

 

[papahausa]

[root@salmon ~]# warden --task=contentfilter:contentfilter --default=yes --reload=yes
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /usr/local/psa/admin/plib/modules/warden/library/modules/database/classes/Kohana/Database/MySQLi.php on line 171
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/psa/admin/plib/modules/warden/library/modules/log/classes/Model/Log/Application.php on line 1
[root@salmon ~]# warden --task=antispam:learning --default=yes --reload
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /usr/local/psa/admin/plib/modules/warden/library/modules/database/classes/Kohana/Database/MySQLi.php on line 171
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /usr/local/psa/admin/plib/modules/warden/library/system/classes/Kohana/Core.php on line 980

 

[danami]

@papahausa open a support ticket in our client area and a tech can help you.

 

[papahausa]

@papahausa open a support ticket in our client area and a tech can help you.

Solved. after reboot.

 

[papahausa]

Hello.
after plesk update Dovecot cant start.
dovecot[83256]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 9: Unknown section name: plugin
systemd[1]: dovecot.service: Main process exited, code=exited, status=89/n/a

systemd[1]: dovecot.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu

systemd[1]: Failed to start dovecot.service - Dovecot IMAP/POP3 email server.
░░ Subject: A start job for unit dovecot.service has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu

Product name
Warden Anti-spam and Virus Protection
Product version
5.02

 

[papahausa]

Seems Dovecot 2.4.1 not support section plugin and imapsieve_mailbox* parametrs in /etc/dovecot/conf.d/99-warden.conf

 

[papahausa]

i changed config /etc/dovecot/conf.d/99-warden.conf with minimum changes.
service imap {
vsz_limit = 512MB
}

protocol imap {
mail_plugins = $mail_plugins
}

now service work, but without danami.

 

[papahausa]

i changed config /etc/dovecot/conf.d/99-warden.conf with minimum changes.
service imap {
vsz_limit = 512MB
}

protocol imap {
mail_plugins = $mail_plugins
}

now service work, but without danami.

sorry. wrong config.
this correct.

service imap {
vsz_limit = 512MB
}

protocol imap {
mail_plugins = notify mail_log quota
}

 

[danami]

@papahausa Yes this is because Plesk upgraded dovecot to version 2.4.1-4 which uses a completely different configuration syntax to all previous versions of dovecot. We have a KB article with a temp fix:

How can I fix the error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 9: Unknown section name: plugin after upgrading to Plesk 18.0.73? - Knowledgebase - Danami

We will be releasing Warden 5.03 shortly with a permanent fix.

 

[papahausa]

@papahausa Yes this is because Plesk upgraded dovecot to version 2.4.1-4 which uses a completely different configuration syntax to all previous versions of dovecot. We have a KB article with a temp fix:

How can I fix the error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 9: Unknown section name: plugin after upgrading to Plesk 18.0.73? - Knowledgebase - Danami

We will be releasing Warden 5.03 shortly with a permanent fix.

Thanks for replay.
Still waiting update. Have a nice day.

 

[danami]

@papahausa We've updated that KB article with additional changes.

How can I fix the error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 9: Unknown section name: plugin after upgrading to Plesk 18.0.73? - Knowledgebase - Danami

This dovecot update has a lot of changes that we have to go though:

https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html

Hopefully we are should have an update ready for Monday.

 

[papahausa]

How can I fix the error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/99-warden.conf line 9: Unknown section name: plugin after upgrading to Plesk 18.0.73? - Knowledgebase - Danami

I use this config. All is good at this moment.

Still waiting updates.

 

[lightingman2003]

@danami - I posted this in another thread, but here's hoping this is the right thread

There is an issue with the AntiSpam Learning Statistics provided on the Dashboard tab of Warden.

Ever since the automatic update to Warden AntiSpam 5.02, whenever the Server is rebooted (for Kernel updates etc), the AntiSpam Learning Statisics are reset back to 0, and it starts counting up from 0 again for any Spam/Ham learnt. For example, our server was rebooted last night, but the number of spam & Ham learned is now showing as the below:

Prior to this, it had learnt over 2.5k Spam, and a similar amount of Ham. We think the issue started when Warden auto-updated to 5.02 on 15th September. From memory, at this point it never cleared the stats, and it counted well over 20-30k spam emails learnt.

Whilst this is in itself is not a massive issue, its odd how it only started happening since Warden 5.02.

 

[danami]

@lightingman2003 Are you maybe using Redis as the Bayes back end? Remember that Redis is an in memory engine and would get cleared when Redis is rebooted (if you don't have Redis set to save to storage). If you aren't using Redis then I recommend opening a support ticket in our client area then we can look at this issue for you.

 

[danami]

@lightingman2003 Looking at your screenshot it looks like you are using Redis as your Bayes back end (because it doesn't have token counts like the default MySQL back end). So when you reboot it clears anything stored in Redis because redis isn't set to persist.

Redis persistence

How Redis writes data to disk

redis.io