Dear Eugene

thank you for your valuable response

I have changed the configuration as per your suggestion.

plugin {

  antispam_backend = dspam antispam_crm_args = --config=/home/vmail antispam_dspam_args = --client;--user=vmail; --source=error;--signature=%%s antispam_dspam_binary = /usr/bin/dspamc antispam_signature = X-DSPAM-Signature

}

but in mail debug ouput it is displaying the following error and mail receive in inbox:

Apr 30 18:29:18 sogo dovecot: imap(kanchan): Error: antispam plugin folders are not configured for this user

 can you give me hints whats I do in next step.

Regard's

Ravi Kanchan Sharma Sr. System Administrator Infinite Computer Solutions (I) Ltd. Bglr. Mo. 9997154666

From: Eugene Paskevich eugene@raptor.kiev.ua To: "dovecot@dovecot.org" dovecot@dovecot.org; Ravi Kanchan ravi_kanchan2004@yahoo.com Sent: Tuesday, 30 April 2013 5:17 PM Subject: Re: [Dovecot] dovecot antispam plugin is not woking

On Tue, 30 Apr 2013 12:36:44 +0300, Ravi Kanchan  ravi_kanchan2004@yahoo.com wrote:

I am using dovecot  version 2.0.9 DSPAM Anti-Spam Suite 3.10.2 (agent/library) ClamAV 0.97.7/17102

and dspam antispam plugin dovecot-antispam-plugin-43880985e3dd

That is quite an old revision. However, there were no significant changes since then. If you update to the latest revision you might need to revert 5e8351bcfb29, given your dovecot version.

and plugin configuration is given below:

protocol imap { mail_plugins = " antispam autocreate" } protocol pop3 { mail_plugins = antispam autocreate }

I'm not sure this plugin could be used with POP3.

plugin { antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_crm_args = --config=/home/vmail

This line isn't used for dspam backend.

  antispam_dspam_args = --client;--user vmail

"--user vmail" is treated like a single argument due to missing semicolon. That is definitely not what you want. Put it like "--client;--user;vmail".

Also, you might consider adding these two:  "--source=error;--signature=%%s". But I've never used dspam, so can't know for sure.

  antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent

These are default, could be removed.

  antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam

This last line could also be removed because it's default.

  antispam_mail_tmpdir = /tmp

No such setting at all for this plugin.

  antispam_signature = X-DSPAM-Signature antispam_signature_missing = error

Again, default.

  antispam_spam = Spam }

dspam bin path:

[root@sogo ~]# which dspam /usr/bin/dspam

but my dspam plugin configuration is not working. and I am not getting any log from dspam. My dspam server is working prefect.

cna anyone help me

Please fix antispam_dspam_args and let me know whether it works.

-- Eugene Paskevich            |  *==)-----------  |    Plug me into eugene@raptor.kiev.ua        |  -----------(==*  |      The Matrix

On 30-04-13 17:14, Eugene Paskevich wrote:

On Tue, 30 Apr 2013 15:56:19 +0300, Ravi Kanchan ravi_kanchan2004@yahoo.com wrote:

...

thank you for your valuable response

I have changed the configuration as per your suggestion.

Try putting it this way:

plugin { antispam_spam = Spam antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_dspam_args = --client;--user;vmail;--source=error;--signature=%%s antispam_dspam_result_header = X-DSPAM-Result antispam_signature = X-DSPAM-Signature }

I run dovecot, dspam and antispam plugin on dovecot 2.1.16 with:

plugin { antispam_backend = dspam antispam_dspam_args = --user;mail;--deliver=;--source=error;--signature=%%s antispam_dspam_binary = /usr/bin/dspamc antispam_dspam_notspam = --class=innocent antispam_dspam_spam = --class=spam antispam_signature = X-DSPAM-Signature antispam_signature_missing = move antispam_spam_pattern_ignorecase = Junk;Junk.* antispam_trash_pattern_ignorecase = Trash;Deleted Items;Deleted Messages }

And it works great :)

-- Tom

On 04/30/2013 05:47 AM, Eugene Paskevich wrote:

On Tue, 30 Apr 2013 12:36:44 +0300, Ravi Kanchan ravi_kanchan2004@yahoo.com wrote:

...

and plugin configuration is given below:

protocol imap { mail_plugins = " antispam autocreate" } protocol pop3 { mail_plugins = antispam autocreate }

I'm not sure this plugin could be used with POP3. I am pretty sure that it cannot be used with POP3. It requires IMAP.

Trever

On Sat, 04 May 2013 08:13:44 +0300, Ravi Kanchan
ravi_kanchan2004@yahoo.com wrote:

But it is not woking in our setup its not block or marking SPAM mail
which is receiving through IMAP or POP3 services.

Antispam plugin isn't supposed to block nor mark mails. It's only used to teach your spam system should it make an error.

-- Eugene Paskevich | *==)----------- | Plug me into eugene@raptor.kiev.ua | -----------(==* | The Matrix