On Sun, Dec 22, 2024 at 08:07:22PM -0500, Wietse Venema via Postfix-users wrote:
> The "full name" encoding for Postfix-generated From: headers is
> implemented. Code will be released after it has matured.
>
> Documentation:
> https://www.postfix.org/postconf.5.html#full_name_encoding_charset
Coo
The "full name" encoding for Postfix-generated From: headers is
implemented. Code will be released after it has matured.
Documentation:
https://www.postfix.org/postconf.5.html#full_name_encoding_charset
Wietse
___
Postfix-users mailing list -- p
On Mon, Dec 23, 2024 at 10:50:49AM +1100, Viktor Dukhovni via Postfix-users
wrote:
> On Sun, Dec 22, 2024 at 02:31:56PM +, Laura Smith via Postfix-users wrote:
>
> > > Note that after the above you're allowing TLS 1.0 by default, where you
> > > insisted on TLS 1.2 or higher before. Postfix p
On Sun, Dec 22, 2024 at 02:31:56PM +, Laura Smith via Postfix-users wrote:
> > Note that after the above you're allowing TLS 1.0 by default, where you
> > insisted on TLS 1.2 or higher before. Postfix parsing of the legacy
> > protocol negations has not changed. But you should be using the
> >
Alexander Leidinger via Postfix-users:
> Am 2024-12-22 01:39, schrieb Peter via Postfix-users:
> > On 22/12/24 02:54, Michael Tokarev via Postfix-users wrote:
> >>
> >> However, there are other mechanisms being developed, for example
> >> OAUTH2,
> >> which, in terms of Cyrus SASL, does not work
Am 2024-12-22 01:39, schrieb Peter via Postfix-users:
On 22/12/24 02:54, Michael Tokarev via Postfix-users wrote:
However, there are other mechanisms being developed, for example
OAUTH2,
which, in terms of Cyrus SASL, does not work with saslauthd at all,
I don't see why it wouldn't.
so
ne
> Note that after the above you're allowing TLS 1.0 by default, where you
> insisted on TLS 1.2 or higher before. Postfix parsing of the legacy
> protocol negations has not changed. But you should be using the
> preferred min/max forms.
I know you're saying nothing changed, but I'm telling yo
On Sun, Dec 22, 2024 at 02:04:46PM +, Laura Smith via Postfix-users wrote:
>
>
>
> > Perhaps Postfix does not "listen" on the IPv6 address? You can use nc or
> > lsof
> > to find out.
> >
>
> See above where I said "worked fine before the update". "Worked fine"
> includes external valid
> Perhaps Postfix does not "listen" on the IPv6 address? You can use nc or lsof
> to find out.
>
See above where I said "worked fine before the update". "Worked fine" includes
external validation, i.e. direct email delivery and ipv6 test websites such as
internet.nl
For the records, I *th
Laura Smith via Postfix-users:
> Following a Debian Bookworm update I am now seeing connectivity issues that
> were not present before (everything was working perfectly before)
>
> Postfix on the instance starts up fine, i.e. indicating no configuration
> errors.
>
> The error is:
> $ openssl s
Following a Debian Bookworm update I am now seeing connectivity issues that
were not present before (everything was working perfectly before)
Postfix on the instance starts up fine, i.e. indicating no configuration errors.
The error is:
$ openssl s_client -connect [IPV6_ADDRESS_REDACTED]:25 -sta
On 22/12/24 23:22, Michael Tokarev via Postfix-users wrote:
Cyrus SASL is a separate thing in people minds because it is a
separate, independent library/subsystem. You can install a separate
package named this way. But in Dovecot it is an integral part of a
larger system, it is not viewed like
Hi!
It seems that some my statements on this list are difficult to understand
somehow. While I usually mean one context, my statements are being interpreted
in another context.
Postfix documentation has always been an excellent example of clear brevity
to me, a high standard level which is almo
22.12.2024 13:13, Tomasz Pala via Postfix-users wrote:
Well, Cyrus is also not SASL-only...
https://doc.dovecot.org/2.3/admin_manual/sasl/ is what I mean.
Cyrus SASL is a separate thing in people minds because it is a
separate, independent library/subsystem. You can install a separate
packag
On 2024-12-22 07:53, Michael Tokarev via Postfix-users wrote:
>
> It is not true for you, but not for most others who treat dovecot like
> a mailbox storage/access solution (IMAP/POP/etc). Sure it is capable
> to provide just the auth part, it's just not what people think about it.
Well, Cyrus i
22.12.2024 11:53, Peter via Postfix-users wrote:
On 22/12/24 19:53, Michael Tokarev via Postfix-users wrote:
However, there are other mechanisms being developed, for example OAUTH2,
which, in terms of Cyrus SASL, does not work with saslauthd at all,
I don't see why it wouldn't.
saslauthd h
On 2024-12-22 01:42, Peter via Postfix-users wrote:
>>
>> What's worth mentioning is that PLAIN/LOGIN also requires cleartext
>> password storage - on the client side.
>
> This is not entirely true. It is possible for a client to store
> passwords in an encrypted db which is decrypted with its o
22.12.2024 11:53, Peter via Postfix-users wrote:
[people treat dovecot sasl as part of dovecot]
I realize that, but it's fairly easy to implement and easy to configure dovecot to only provide the SASL backend plus it does appear to be the most
comprehensive, easiest to implement solution for SA
On 22/12/24 19:53, Michael Tokarev via Postfix-users wrote:
22.12.2024 03:39, Peter via Postfix-users wrote:
On 22/12/24 02:54, Michael Tokarev via Postfix-users wrote:
However, there are other mechanisms being developed, for example OAUTH2,
which, in terms of Cyrus SASL, does not work with sa
19 matches
Mail list logo
