[Tickets #14710] Re: Headers encoded wrongly when replying to certain senders
noreply at bugs.horde.org
noreply at bugs.horde.org
Mon Dec 11 09:34:46 UTC 2017
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/14710
------------------------------------------------------------------------------
Ticket | 14710
Updated By | alexh at boxed.no
Summary | Headers encoded wrongly when replying to certain
| senders
Queue | Synchronization
Version | FRAMEWORK_5_2
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Rubinsky
------------------------------------------------------------------------------
alexh at boxed.no (2017-12-11 09:34) wrote:
>>
>>> If you look at line 9 and 10 from the tcpdump provided a few entries
>>> down, clearly Horde generates something that the MTA can't parse
>>> properly, though?
>>
>> Yes, and that is what I cannot reproduce.
>
> As a last ditch, can I make one of the recepients I have issues with
> send you a test email directly and see if that makes your server
> behave the same?
>
> -A
Also, I found this snipped in the postix documentation, that seems to
explain it, and explains why you cannot reproduce it (you seem to run
exim from some bounce messages I've got):
"When the Postfix SMTP server receives a message WITHOUT the SMTPUTF8
request, Postfix handles the message as it has always done (at least
that is the default, see autodetection below). Specifically, the
Postfix SMTP server does not accept UTF-8 in the envelope sender
domain name or envelope recipient domain name, and the Postfix SMTP
client does not issue the SMTPUTF8 request when delivering that
message to an SMTP or LMTP server that announces SMTPUTF8 support
(again, that is the default). Postfix will accept UTF-8 in message
header values and in the localpart of envelope sender and recipient
addresses, because it has always done that."
The two first sentences seem to be the problem.
-A
More information about the bugs
mailing list