IPv6 DNSRBLs

2022-05-29 Thread Peter
We're now starting to see some IPv6 DNSRBLs (eg: bl.ipv6.spameatingmonkey.net). It occurs to me that postscreen and postfix should only be sending IPv4 requests to IPv4-specific DNSRBLs and IPv6 requests to IPv6-specific lists. I would therefore hope for consideration of the following

Re: postscreen_dnsbl_sites questions about multiple matches.

2022-05-29 Thread Peter
On 30/05/22 3:49 pm, Bill Cole wrote: I have no idea, but assigning scores to DNSBL return values that are not currently in use is quite optimistic and dangerous. Also, 127.0.0.1 specifically is an indicator of likely DNSBL malfunction. Well, spamhaus documents that 127.0.0.0/24 are for

Re: Postfix+SASL chrooted - out of ideas (SASL_README tweak)

2022-05-29 Thread Viktor Dukhovni
On Mon, May 30, 2022 at 12:48:46PM +1000, raf wrote: > I don't think that's entirely correct. On Debian, for > example, the default value of cyrus_sasl_config_path is > empty, and /etc/postfix/sasl is the directory that is > used. Well, how exactly does that happen? I don't see any patches to

Re: postscreen_dnsbl_sites questions about multiple matches.

2022-05-29 Thread Bill Cole
On 2022-05-29 at 22:02:54 UTC-0400 (Mon, 30 May 2022 14:02:54 +1200) Peter is rumored to have said: First off my goal is that I want all zen.spamhaus.org entries to have a score of 3 except for CSS entries which should have a score of 2. zen returns 127.0.0.n for all entries and CSS

Re: Postfix+SASL chrooted - out of ideas (SASL_README tweak)

2022-05-29 Thread raf
On Sun, May 29, 2022 at 11:25:44AM -0400, Viktor Dukhovni wrote: > On Sat, May 28, 2022 at 10:32:56PM -0400, Viktor Dukhovni wrote: > > > > This might be irrelevant, but the SASL readme mentions > > > that on some systems Postfix is modified to look for > > > the Cyrus SASL config in

postscreen_dnsbl_sites questions about multiple matches.

2022-05-29 Thread Peter
First off my goal is that I want all zen.spamhaus.org entries to have a score of 3 except for CSS entries which should have a score of 2. zen returns 127.0.0.n for all entries and CSS specifically returns 127.0.0.3. What I think I can do is this: postscreen_dnsbl_sites =

Re: Postfix+SASL chrooted - out of ideas

2022-05-29 Thread Viktor Dukhovni
> On 29 May 2022, at 5:15 pm, Jim Garrison wrote: > > One possible suggestion for Postfix: Since it appears Postfix was > never able to even establish contact with Cyrus SASL, it might be nice > to detect that condition and provide a different error message than > just "authentication failed",

Re: Postfix+SASL chrooted - out of ideas

2022-05-29 Thread Jim Garrison
On 5/28/2022 7:07 PM, Viktor Dukhovni wrote: On Sat, May 28, 2022 at 05:11:22PM -0700, Jim Garrison wrote: Foreground saslauthd command, including debug output from successful testsaslauthd but no log entries corresponding to the immediately above extract from the Postfix log: $ sudo

Re: Postfix+SASL chrooted - out of ideas (SASL_README tweak)

2022-05-29 Thread Viktor Dukhovni
On Sat, May 28, 2022 at 10:32:56PM -0400, Viktor Dukhovni wrote: > > This might be irrelevant, but the SASL readme mentions > > that on some systems Postfix is modified to look for > > the Cyrus SASL config in /etc/postfix/sasl or > > /var/lib/sasl2. On Debian, it's in /etc/postfix/sasl. > >