move the spam options for the mail user tab to a spamassasin user tab

hello,

in fact we should remove it from user and rewritte it correctly wit support for correct spamassassin attribute and configuration

https://svn.apache.org/repos/asf/spamassassin/branches/3.0/ldap/README

Cheers

(from redmine: written on 2016-04-14)

hello,

remove the spam options from the mail tabs were not useful or right

Cheers

(from redmine: written on 2016-04-15)

Also applied this to 1.1

(from redmine: written on 2016-04-19)

hello,

we need to remove the spam options title and leftover function from the mail user tab

Cheers

  'options2' => array(
    'name' => _('Spam options'),
    'attrs' => array(
      new FlagsAttribute ('gosaMailDeliveryMode', array(
        'flag_ownmailbox',
        'flag_vacation',
        'flag_localonly',
        'flag_sieveownscript'
      ))
    )
  ),

(from redmine: written on 2016-04-20)

hello,

there is an exemple ldif here

https://svn.apache.org/repos/asf/spamassassin/branches/3.0/ldap/sa_test.ldif

i seems its multivaluated and looks like that

spamassassin: add_header all Foo LDAP read

but there is not much doc about it :/

(from redmine: written on 2016-04-26)

There is a bit of documentation here: http://commons.oreilly.com/wiki/index.php/SpamAssassin/SpamAssassin_Rules#Storing_Scores_in_an_LDAP_Database

But they don’t seem to provide a schema, there is even no objectClass provided, they say «To add SpamAssassin preferences to your users, extend the objectClass that represents a user to allow an additional, optional spamassassin attribute», which does not seem very clean. We need to check the OID they provide to see if we can reuse it and decide if we use our own OID prefix for the objectClass.

About the content of the attribute it seems to be spamassassin rules syntax, so we also need to see if we provide direct rule edition or something higher level.

(from redmine: written on 2016-04-26)

Added basic support for this attribute but I don’t fully understand what it’s for, documentation is far from clear.

(from redmine: written on 2016-04-27)

The readme say that only the next options will work with the LDAP backend.

score: add a value to define if the mail is a spam or not (5 = spam)
whitelist_from: define if the sender is whitelisted or not (work with regex => https://wiki.apache.org/spamassassin/ManualWhitelist)
required_score: minimum value to define the mail as spam (default 5)
auto_report_threshold: not found in the documentation

I think it would be better to create a list of directives that the user can select and use a field to write the rest of the rule.

In FD:

score: dropdown with numbers and a field to complete the rule (score MYRULE 2)
whitelist_from: a simple field (whitelist_from toto@mail.com)
required_score: a dropdown with a field to complete the rule (required_score MYRULE 20)

(from redmine: written on 2016-04-28)

Ok, I changed the first field for a dropdown with the possible values: score, whitelist_from, required_score

(from redmine: written on 2016-04-29)

Close issue

(from redmine: written on 2016-04-29)

closed

added Changed label

move the spam options for the mail user tab to a spamassasin user tab

Tasks

Activity

Menu

move the spam options for the mail user tab to a spamassasin user tab

Tasks

Linked items 0

Activity

Linked items
0