Modify ↓
Opened 3 years ago Closed 10 months ago #128 closed task (fixed)Enhance the SPAM filter engine to recognize external SPAM checker
Description (last modified by damato)
In Thunderbird, a user can very easily select that the SPAM checker engine should recognize the SPAM status of incoming mails based on commonly known header insertion lines like "X-Spam-Status:" for "SpamAssassin".
YAM should adopt that behaviour in a future version and automatically flag a mail as SPAM or HAM according to that external "trusted" checkers. However, the users should be able to manually select which of the external SPAM engines to trust... Attachments (0)Change History (5)comment:1 Changed 3 years ago by damato
comment:2 Changed 18 months ago by damato
comment:3 Changed 11 months ago by thboeckel
comment:4 Changed 11 months ago by damato
Sorry, but IMHO this ticket is not fully fulfilled. We need to have the Spamassassin&SpamCop rules from Thunderbird hardcoded in YAM rather than relying on having the user to import them manually. Thus, I will reopen this ticket as still unresolved. Neverthelesse, the possibility to import a filter form thunderbird is a very good point now. comment:5 Changed 10 months ago by thboeckel
(In [6095]) * YAM_CO.c, YAM_COg.c, YAM_COs.c, YAM_FI.c: implemented the "trust header lines of external filter" feature as known from Thunderbird. This lets the user choose an external filter from an number of installed .sfd files in the resources directory. These files usually define two filters for specific header lines to tell spam and non-spam mails apart. The filters will *not* occur in YAM's own list of filters. This finally closes #128 again. Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber
| ||||||||||||||||||||||||||||
(In [6087]) * YAM_COg.c, YAM_FI.c: implemented a filter import from Thunderbird's .sfd files. This import will try to replicate the given filters as close as possible using YAM's filtering facilities. Please note that not all features of Thunderbird's filters can be replicated by YAM due to fundamental differences in operation. This closes #128.