search for: lmtp_rcpt

....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 addresses that dovecot doesn't like. It can be corrected manually using: override_fields = destuser=&quot...

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 {

...> 501 5.5.4 Invalid parameters\r\n > > QUIT\r\n > > from director -> dovecot LMTP network dump: > > I could have a look at > starting to get a fix together tomorrow with an aim to providing a pull > request, if it turns out there are no side-effects to treating > lmtp_rcpt.address like this and you'd like an example of what I mean. My apologies for not adding your address on my initial response, Alexander - not sure if you noticed what I replied with or not. Nope, this isn't going to happen. I'm not familiar with the dovecot internals but lmtp uses just...

...r\n >>> >>> from director -> dovecot LMTP network dump: >>> >>> I could have a look at >>> starting to get a fix together tomorrow with an aim to providing a pull >>> request, if it turns out there are no side-effects to treating >>> lmtp_rcpt.address like this and you'd like an example of what I mean. >> My apologies for not adding your address on my initial response, Alexander - not >> sure if you noticed what I replied with or not. >> >> Nope, this isn't going to happen. I'm not familiar with the do...

...\r\n >> >> QUIT\r\n >> >> from director -> dovecot LMTP network dump: >> >> I could have a look at >> starting to get a fix together tomorrow with an aim to providing a pull >> request, if it turns out there are no side-effects to treating >> lmtp_rcpt.address like this and you'd like an example of what I mean. > > My apologies for not adding your address on my initial response, Alexander - not > sure if you noticed what I replied with or not. > > Nope, this isn't going to happen. I'm not familiar with the dovecot int...