Wietse Venema via Postfix-users wrote in
 <4bvwvk4lfszj...@spike.porcupine.org>:
 |H?kon Alstadheim via Postfix-users:
 |> Den 29.06.2025 15:40, skrev Dmytro Alieksieiev via Postfix-users:
 |>>
 |>> 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).

Only to make this clear: postfix simply does not deal with any
message nor header reencoding at all?
That is, if i would enable SMTPUTF8, and someone sends a true
message/global aka SMTPUTF8 email, then this will not be relayed
any further unless "the next hop" (usually the recipient today
thus) has support for SMTPUTF8 as such -- it will bounce
otherwise?
All that postfix will actually do is to IDNA encode the domain
name, likely for DNS lookups (i only grep()ped superficially) etc?

(I am still hoping AlpineLinux will turn off the ICU dependency
again.  ICU is really great, bla bla bla, the rest i removed.)

 |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.
 ...

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
|
|During summer's humble, here's David Leonard's grumble
|
|The black bear,          The black bear,
|blithely holds his own   holds himself at leisure
|beating it, up and down  tossing over his ups and downs with pleasure
|
|Farewell, dear collar bear
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to