H?kon Alstadheim via Postfix-users:
>
> Den 29.06.2025 15:40, skrev Dmytro Alieksieiev via Postfix-users:
> >
> > Hi Jorge,
> >
> > To have SMTPUTF8 enabled in system it should be supported by all
> > components of mail system.
> >
> > If you have LMTP as f.e. Dovecot which not yet production ready for
> > SMTPUTF8 (at least from my view, as it only got support of it couple
> > of months ago and I would not rush deploying it on Prod)
> >
> About that, do you know how the dovecot-lda binary behaves with UTF8
> emails?
Postfix would forward SMTPUTF8 mail to an LMTP server only if the
server announces SMTPUTF8 (in LHLO).
I suppose one could fake that with the smtp_reply_filter feature:
smtp_reply_filter = inline:{{250-ENHANCEDSTATUSCODES = 250-SMTPUTF8}}
This replaces an uninportant part of Dovecot's response. so that
> LHLO mail.example.com
< 250-mail.example.com
< 250-8BITMIME
< 250-ENHANCEDSTATUSCODES
< 250 PIPELINING
becomes
> LHLO mail.example.com
< 250-mail.example.com
< 250-8BITMIME
< 250-SMTPUTF8
< 250 PIPELINING
I will not speculate how Dovecot deals with non-ASCII headers,
non-ASCII envelopes, and how all this interacts with Sieve.
Wietse
> It *should* only bother about the envelope headers I'd think? So, as
> long as recipient localpart is 7bit, I should be OK with allowing utf8
> on incoming? I've had separate outgoing/incoming paths like you suggest,
> with smtputf8_enable=no on local deliver, sendmail submit and smtp
> submit, but it feels *wrong*. I'm not using lmtp for local delivery for
> some reason I can't remember. I've got concurrency_limit and
> recipient_limit = 1 for local delivery, so? access and locking should be
> OK. Filtering and filing works well with dovecots imapsieve.
>
> _______________________________________________
> Postfix-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
