dovecot - Oct 2008 - Disabling global content_filter with an empty filter specified with an access table

On Wed, Oct 8, 2008 at 7:36 PM, mouss <mouss at netoyen.net>
wrote:
>
> an alternative is
>
> content_filter > smtpd_sender_restrictions >       
check_sender_access hash:/etc/postfix/sender_ok
>        check_sender_access pcre:/etc/postfix/filter
>
> == dsn_ok
> <>      OK
>
> == filter
> /./     FILTER filter:[1.2.3.4]:10024
>
> where "filter:[1.2.3...." is what you used to put in
content_filter.
Yes, that's what I was thinking when I wrote "workaround" in my
first mail:

On Wed, Oct 8, 2008 at 5:08 PM, Diego Liziero <diegoliz at gmail.com>
wrote:
>[..]
>I think that this solution is more readable than the only workaround I
>can imagine now (that is disabling global filtering and enabling it in
>a pcre table for everything except that particular case).
So it's a bit less readable, I've to remember to disable sender
restrictions in the content filter return transport to avoid filter
loops, there will be one more line for each mail in the log stating
that the filter is triggered, but apart from that it should work as I
need.

Thank you to everyone that helped me,
tomorrow I'm going to test both methods.

Regards,
Diego.