Displaying 3 results from an estimated 3 matches for "lmtp_client_send_rcpts".
2017 Nov 03
0
Bug: lmtp proxy does not quote local parts with spaces
...;
> 3. The third problem is then re-encoding the username in the envelope recipient
> when proxying, which was not done at all. I've added a function
> lmtp_client_rfc822_escape_address(), which is similar to
> str_append_maybe_escape() to escape the address at protocol time in
> lmtp_client_send_rcpts() [src/lib-smtp/lmtp-client.c], although I suspect it
> should be done earlier, this is just a working proof.
>
> The other reason I don't believe this patch is production quality is that I have
> not examined any interaction between these changes and sieve's use of the
> env...
2017 Nov 01
2
Bug: lmtp proxy does not quote local parts with spaces
...is
change should be made.
3. The third problem is then re-encoding the username in the envelope recipient
when proxying, which was not done at all. I've added a function
lmtp_client_rfc822_escape_address(), which is similar to
str_append_maybe_escape() to escape the address at protocol time in
lmtp_client_send_rcpts() [src/lib-smtp/lmtp-client.c], although I suspect it
should be done earlier, this is just a working proof.
The other reason I don't believe this patch is production quality is that I have
not examined any interaction between these changes and sieve's use of the
envelope recipient. I'm...
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
On 26/10/2017 18:38, Alexander Dalloz wrote:
> Am 26.10.2017 um 12:20 schrieb David Zambonini:
>>
>> There seems to be a bug with RFC822 processing in ltmp proxying that
>> doesn't
>> quote local parts that, for example, contain spaces.
>
> Newer related RFCs are RFC 5321 and 5322.
Typo, meant to say RFC2822, which they still supercede, not that the