Displaying 2 results from an estimated 2 matches for "client_proxy_rcpt".
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
There seems to be a bug with RFC822 processing in ltmp proxying that doesn't
quote local parts that, for example, contain spaces.
director config:
director_username_hash = %Ln
lmtp_proxy = yes
recipient_delimiter = +
protocol lmtp {
auth_socket_path = director-userdb
auth_username_chars =
auth_username_format = %Ln
passdb {
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
...LMTP network dump:
MAIL FROM:<test at testdomain.com>\r\n
RCPT TO:<deemzed.uk+Junk E-mail at mailbox.localhost>\r\n
501 5.5.4 Invalid.parameters\r\n
The problem is that dovecot is interpreting/unquoting the local part of
the address to insert into the username, but the client code in
client_proxy_rcpt()/address_add_detail() [lmtp/commands.c] then inserts
the username and detail directly into lmtp_rcpt.address with no attempt
whatsoever to requote that string regardless of what characters it
contains, leading to the situation where a straight-through proxy fails
as director is generating addresse...