Global sieve rule

Discussion:

Global sieve rule

Henry

2017-05-29 20:38:59 UTC

I wish to have a global sieve rule that moves spam mail to a user's
spam mail folder.

In Roundcube I can create this rule on a user by user basis:

# rule:[Spamassassin]
if header :contains "subject" "***SPAM***"
{
fileinto "Spam";
}

I would like to set the above as a default for all users.

Skale, Franz

2017-05-30 05:48:47 UTC

Permalink

Hi,
i think there's no easy way other than tweaking:
/usr/share/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve.php
(Line 137, Variable $script).
Try to submit a feature request to roundcube (github).
For me also, it doesn't make sense not to have default rules applied to
all roundcube users via config file.
Like: /usr/share/roundcubemail/plugins/managesieve/config.inc.php

Rgds.
Franz

Post by Henry
I wish to have a global sieve rule that moves spam mail to a user's
spam mail folder.
# rule:[Spamassassin]
if header :contains "subject" "***SPAM***"
{
fileinto "Spam";
}
I would like to set the above as a default for all users.
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users

Daniel Hoffend

2017-06-09 22:34:32 UTC

Permalink

Hi Franz

why don't you configure amavisd to deliver spam messages to +spam using
the parameter "addr_extension_spam". This was a spam gets delivered to
user+***@domain.tld and postfix/cyrus delivers the mail to the spam
folder using lmtp. This is possible without having a global sieve rule.

--
regards
Daniel

Post by Skale, Franz
Hi,
/usr/share/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve.php
(Line 137, Variable $script).
Try to submit a feature request to roundcube (github).
For me also, it doesn't make sense not to have default rules applied to all
roundcube users via config file.
Like: /usr/share/roundcubemail/plugins/managesieve/config.inc.php
Rgds.
Franz

_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users

Skale, Franz

2017-06-10 16:07:54 UTC

Permalink

Hi Daniel,
thanks for the hint.
But in a multidomain setup, i think, it would be sufficient, to route
all SPAM to user+***@domain.tld by configuring amavis via
/etc/amavis/conf.d/50-user:
$recipient_delimiter = '+';
$addr_extension_spam = 'Spam';

So, by reading the amavis perldoc, my interpretation:
All spam will be rewritten to user+***@domain.tld and i don't need one
rule for one user ?
Make sense to me, i give it a try.

Thanks.

Franz

Post by Daniel Hoffend
Hi Franz
why don't you configure amavisd to deliver spam messages to +spam using
the parameter "addr_extension_spam". This was a spam gets delivered to
folder using lmtp. This is possible without having a global sieve rule.
--
regards
Daniel

_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users

Franz Skale

2017-06-17 15:09:57 UTC

Permalink

Hi,
only want to report back, that the setting ( also for multidomain ) works.

Rgds.

Franz

Post by Skale, Franz
Hi Daniel,
thanks for the hint.
But in a multidomain setup, i think, it would be sufficient, to route
$recipient_delimiter = '+';
$addr_extension_spam = 'Spam';
one rule for one user ?
Make sense to me, i give it a try.
Thanks.
Franz

_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users