[pfx] Re: Cyrus SASL summary

2024-07-05 Thread Scott Kitterman via Postfix-users
On July 5, 2024 3:03:58 PM UTC, Viktor Dukhovni via Postfix-users wrote: >On Fri, Jul 05, 2024 at 08:45:49AM -0400, Scott Kitterman via Postfix-users >wrote: > >> > Note, "undo" isn't quite what I'm suggesting, rather I hope Debian will >> > replace the hardcoded preëmpt of the Cyrus SASL conf

[pfx] Re: Cyrus SASL summary

2024-07-05 Thread Viktor Dukhovni via Postfix-users
On Fri, Jul 05, 2024 at 08:45:49AM -0400, Scott Kitterman via Postfix-users wrote: > > Note, "undo" isn't quite what I'm suggesting, rather I hope Debian will > > replace the hardcoded preëmpt of the Cyrus SASL configuration directory, > > by a default value of $cyrus_sasl_config_path, that match

[pfx] Re: Cyrus SASL summary

2024-07-05 Thread Scott Kitterman via Postfix-users
On Friday, July 5, 2024 4:00:59 AM EDT Viktor Dukhovni via Postfix-users wrote: > On Thu, Jul 04, 2024 at 05:01:41PM -, John Levine via Postfix-users > wrote: > > > OK, I'll invent a user. Perhaps if we can get Scott to undo the control > > file move he can add a sasl user at the same time.

[pfx] Re: Question on DKIM process ordering

2024-07-05 Thread Gilgongo via Postfix-users
On Fri, 5 Jul 2024 at 09:10, Matus UHLAR - fantomas via Postfix-users < postfix-users@postfix.org> wrote: > I think in case of amavis it's just the order of logs being written. > IIUC amavis does not confirm receiving message from postfix until after > it's > scanned and passed further, which is w

[pfx] Re: Blocking by IP using check_helo_access

2024-07-05 Thread Linkcheck via Postfix-users
Thank you for your reply, Viktor. So I've been wrong for the past few years in thinking it was working. Surprising (to me!) but yet another warning to not pick up "working configurations" from web sites (and possibly mis-read them). :( I understand what you're saying. I may have mistaken chec

[pfx] Re: Question on DKIM process ordering

2024-07-05 Thread Matus UHLAR - fantomas via Postfix-users
On 05.07.24 08:42, Gilgongo via Postfix-users wrote: I'm setting up a server to handle outbound mail for sasl auth accounts and would like to scan that mail for spam and malware before DKIM signing because I assume scanning might potentially add headers that could break the sig. Right now I have

[pfx] Re: Question on DKIM process ordering

2024-07-05 Thread Viktor Dukhovni via Postfix-users
On Fri, Jul 05, 2024 at 08:42:31AM +0100, Gilgongo via Postfix-users wrote: > # For OpenDKIM signing > 127.0.0.1:10027inetn-n--smtpd > ... configs... > -o smtpd_milters=inet:127.0.0.1:8891 > > So I assume DKIM should come last. But the logs imply the spam/v

[pfx] Re: Cyrus SASL summary

2024-07-05 Thread Viktor Dukhovni via Postfix-users
On Thu, Jul 04, 2024 at 05:01:41PM -, John Levine via Postfix-users wrote: > OK, I'll invent a user. Perhaps if we can get Scott to undo the control file > move he can add a sasl user at the same time. Note, "undo" isn't quite what I'm suggesting, rather I hope Debian will replace the hardco

[pfx] Question on DKIM process ordering

2024-07-05 Thread Gilgongo via Postfix-users
I'm setting up a server to handle outbound mail for sasl auth accounts and would like to scan that mail for spam and malware before DKIM signing because I assume scanning might potentially add headers that could break the sig. Right now I have the following (extract) in my Amavis conf: $interface