Extension: spam

[Gunnar Wrobel]

Does the spam configuration work for everyone? Any improvements needed?

[robert78]

Is there a HOWTO on how to set this up (other than enabling the USE flag)?

I suppose every user should have a spam folder in their account, that holds mails classified as spam, so that the user can check them, right?

Is anyone actually using such a setup?
If not, I'll try to get it done and report back :-)

[Gunnar Wrobel]

Hi Robert,

the "spam" use flag does not do anything in the direction of providing a per-user setup for spam handling. There is a short explanation here:

http://projects.gunnarwrobel.de/kolab/wiki/UseFlagSpam

What it does is activating the external spamassassin checks. These are not being activated by default in the standard kolab system. But theyse are the checks that actually make spamassassin useful in my opinion. In my case the external checks reduced the amount of unrecognized spam to about 1-2% while the level was at 50% without these checks. That's why added this flag.

What I do for global spam handling is to create a global shared folder that is writeable for all users. And I do have a cron job that empties this folder every night, running it through spamassassins learning procedures.

If you wish, you can take a look at http://projects.gunnarwrobel.de/scripts/browser/trunk/kolabscript which is the script that does the daily work. This is no more than a rather quick hack though. I'm definitely not going to support it at the moment or explain anything about it. So you need to know a little bit of python if you'd be interested in using it.

Cheers

Gunnar

[jayk]

Has anyone had any success in adding a shared folder and then setting it as the "$spam_quarantine_to =" in /etc/kolab/templates/amavisd.conf.template?

I am having trouble figuring out the proper syntax in the template file.

On the official kolab wiki they show it as:

Code:

$spam_quarantine_to = 'kolab+shared.spambox@example.com';

I saw a note on this forum that this does not currently work however, and I can vouch for that as it didn't work for me either.

I saw another note that said to use:

Code:

user+folder@mydomain.org

I am having trouble figuring out this syntax. It seems the way users are setup is that the uid is the email address. If I set it as: name@mydomain.org+shared.folder@mydomain.org I get syntax errors showing up in my log files. I have tried all sorts of variations and none of them are working. If anyone has had any success with this, maybe they could point me in the right direction.

Thanks,
Jason

[Gunnar Wrobel]

Code:

kolab+shared.spambox@example.com

is definitely the correct syntax for accessing shared folders from the outside. If you set the correct permissions for the shared folder (see admin frontend) it should be possible for anybody from the outside to send an e-mail to that address.

Last time I checked the syntax was working but I never tried that as a spam delivery target. I'll try myself this week and report back.

Cheers

Gunnar

[jayk]

This is what I'm seeing in my log files if it helps (I've edited the domain portion for security purposes):

Code:

Sep 25 17:25:19 mainsrv lmtp[19081]: verify_user(mydomain.org!shared^spam-quarantine) failed: Mailbox does not exist
Sep 25 17:25:19 mainsrv postfix/pipe[19073]: C0DB455AFC: to=<kolab+shared.spam-quarantine@mydomain.org>, relay=kolabmailboxfilter, delay=0, status=bounced (service unavailable. Command output: Failed to set recipient: Mailbox unknown.  Either there is no mailbox associated with this name or you do not have authorization to see it. 5.1.1 User unknown, code 550 )

Thanks,
Jason

[Gunnar Wrobel]

Hi Jason,

I finally found the time to look at the amavisd quarantine setting. But it all works as expected for me.

This is what I did:

Created a shared folder

testfolder@mydomain.de

The folder type (in the kolab webadmin) is "Unspecified" and you need to set the permission of the folder for UID "anyone" to "all".

Now I am able to set

$spam_quarantine_to = 'kolab+shared.testfolder@mydomain.de'

and spam get's redirected to the expected shared folder.

I opened a bug for this at

http://bug.pardus.de/view.php?id=9

Feel free to reopen it in case it still fails to work for you.

Cheers,

Gunnar

[jayk]

It's working fine for me now. I'm not sure why now and not before.

Thanks,
Jason