View Revisions: Issue #5186

Summary 0005186: Spamfilter exceptions
Revision 2019-10-26 19:24 by syzop
Description The action of spamfilter is sometimes undesirable when the spam message is repeated by a relay bot (that is trusted). [..]
Allow adding exceptions for spamfilter. Users matching any of the provided masks should not be checked about spamfilters. Example config entry for that:
except spamfilter {
    action u;
    mask *@*.isp.com;
    mask *@*.anotherisp.com;
};
except spamfilter {
    action cpnN;
    mask *@relaybot.example.com;
};
except spamfilter {
    mask *@znc.example.com; // any action
};
Revision 2019-01-01 19:37 by k4be
Description The action of spamfilter is sometimes undesirable when the offender uses a shared account on a server, or when the spam message is repeated by a relay bot (that is trusted). Because of these reasons, two options should be helpful:
1. Allow adding exceptions for spamfilter. Users matching any of the provided masks should not be checked about spamfilters. Example config entry for that:
except spamfilter {
    action u;
    mask *@*.isp.com;
    mask *@*.anotherisp.com;
};
except spamfilter {
    action cpnN;
    mask *@relaybot.example.com;
};
except spamfilter {
    mask *@znc.example.com; // any action
};

2. Allow setting ident bans by spamfilter. This would cause "GLINE *@1.2.3.4" or "GZLINE *@1.2.3.4" to become "GLINE user@1.2.3.4" and "ZLINE *@1.2.3.4" to become "KLINE user@1.2.3.4", but won't do anything to users with ~username.
set {
    options {
       spamfilter-ban-ident;
    };
};