On Wed, Jul 06, 2022 at 12:07:51AM -0400, Viktor Dukhovni wrote:
> On Mon, Jul 04, 2022 at 04:32:42PM +0200, Spil Oss wrote:
>
> > Since migrating to OpenSSL 3.0 we are experiencing intermittent issues
> > in TLS handshakes.
> > [...]
> > the client returns a a Fatal alert, unexpected_message.
>
On Mon, Jul 04, 2022 at 04:32:42PM +0200, Spil Oss wrote:
> Since migrating to OpenSSL 3.0 we are experiencing intermittent issues
> in TLS handshakes.
> [...]
> the client returns a a Fatal alert, unexpected_message.
>
> See also
> * https://github.com/openssl/openssl/issues/18690
This is due
Reporting back with successful results and a few notes:
https://www.postfix.org/header_checks.5.html says I can use pcre or regexp.
It took me seversl iterations to discover I do not have pcre available with
“postconf -m”
So, I added
header_checks = regexp:/etc/postfix/header_checks
to
Hi,
If helps, and your problem is than alias can be completly different than
sasl, I'm just implementing several approach, and I configure 2 diferent
maps
hash:aliases.map
em...@domain.tld alias,em...@domain.tld
Another one with authorized domains:
regexp:authdomains.map
> On 5 Jul 2022, at 7:31 am, Wietse Venema wrote:
>
>> This lookup table looks for the sender address and returns the SASL
>> username that is allowed to send mail with that address. I could (with
>> much additional complexity) generate all the app-specific uids and
>> return these, but I
Tobias Florek:
> Hi!
>
> I deployed postfix with dovecot SASL using XOAuth2 successfully but need
> application specific passwords for legacy clients (like any IMAP-Client
> that is not roundcube).
>
> I implemented them within dovecot with a separate password database that
> uses extra-users
Hi!
I deployed postfix with dovecot SASL using XOAuth2 successfully but need
application specific passwords for legacy clients (like any IMAP-Client
that is not roundcube).
I implemented them within dovecot with a separate password database that
uses extra-users like +@example.com. This
