Hello,
Thanks to all for the answers and suggestions.
I implemented the white list at the rspamd level with these two files :
/etc/rspamd/local.d/multimap.conf
/etc/rspamd/local.d/ip_whitelist.map
Content of "ip_whitelist.map" :
ip_address_1
...
ip_address_n
Content of "multimap.conf" :
IP_WHITELIST {
type = "ip";
map = "/etc/rspamd/local.d/ip_whitelist.map";
prefilter = true;
action = "accept";
}
Regards.
Le ven. 4 juin 2021 à 19:34, Archange <[email protected]> a écrit :
> Le 04/06/2021 à 13:58, Pete a écrit :
> > It seems that the reality is "Finally, a number of decisions must
> >> (mandatory) be taken:"
> > Well sure. A decison has to be made.
> >
> >
> >> filter whitelist \
> >> chain { test-rdns , test-fcrdns } \
> >> bypass
> > Is this even valid syntax? AFAIR the decision needs to be specified with
> the filter.
> >
> > I think it should be something along those lines:
> > filter "white-rdns" phase connect match rdns <whitelist> bypass
> > filter "white-fcrdns" phase connect match fcrdns bypass
>
> That’s not the same thing though. I did not reply earlier because I
> could not find a solution, but actually I don’t think there is one.
>
> Indeed, François wants bypass only if both rdns and fcrdns matches, not
> if either of them does. Hence why he tries to test both at once, but I
> don’t think there is a way to do this.
>
> Anyway, as shown in the last emails in this thread the issue is broken
> headers on the sender side, and rspamd tagging as spam. So whitelist
> should occur at rspamd level eventually, while the best thing would
> indeed be fixing broken headers.
>
> Regards.
>
>
>
