similar to: Pigeonhole vacation and envelope extension recipient addresses

Op 23-10-2017 om 14:51 schreef David Zambonini: > I have a situation where my LMTP RCPT TO: goes to a mailbox user account that > does not reflect either the final (through aliasing) or envelope email address. > > SMTP RCPT TO: (envelope-local-part at envelope-domain) > Final Recipient: (final-local-part at final-domain) > LMTP RCPT TO: (mailbox-local-part at

Hi again, I've not heard anything further regarding this bug, so I've had a look at the code. To restate the bug in a more precise way: LMTP in dovecot treats external RFC822 email addresses in the envelope recipient and internal usernames as almost identical/interchangeable. This is incorrect and leads to issues when attempting to use director as an LMTP proxy to proxy to recipients

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

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 {

On 26/10/2017 19:33, David Zambonini wrote: > 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.

Hi, Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be replaced in v2.3, but I'll give the? older code a look as well. This can take a while though. Regards, Stephan. Op 1-11-2017 om 18:34 schreef David Zambonini: > Hi again, > > I've not heard anything further regarding this bug, so I've had a look at the code. > > To restate the bug

I am getting these errors[1]. With fairly default setup where sendmail is delivering mail via lmtp. Adding these, do not seem to make a difference. Should I add something to the sendmail configuration? sieve_vacation_dont_check_recipient = no sieve_vacation_use_original_recipient = no [1] discarding vacation response for implicitly delivered message; no known (envelope) recipient address

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. [ ... ] > MAIL FROM:<test at testdomain.com>\r\n > RCPT TO:<deemzed.uk+Junk E-mail>\r\n > > 501 5.5.4 Invalid.parameters\r\n That

I found this[1] thread that describes the same problem with dovecot-LDA, but the solution (add X-Original-To: header) has no effect with LMTP. My sendmail LMTP configuration: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp') Sendmail's address test indicates that sendmail is providing user+detail to LMTP (see below). Except for this problem, dovecot, LMTP, and sieve

On 03/11/2017 11:48, Stephan Bosch wrote: > Hi, > > Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be > replaced in v2.3, but I'll give the? older code a look as well. > > This can take a while though. Thank you very much for getting back to me, I can appreciate it can get hectic, and I don't wish to appear ungrateful, I wholeheartedly

On 07/11/2017 14:18, Mathieu R. wrote: > Maybe i got no answer because there is an error which seem obvious in my > logs : > > Nov 4 20:57:55 vps81550 dovecot: auth: Fatal: sql: driver not set in > configuration file /etc/dovecot/dovecot-sql.conf.ext This might sound silly, but in your doveconf you have: passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } Yet

Hello list, Dovecot Version: 2.2.34 (874deae) on FreeBSD MTA: Postfix 3.3.0 I've got an issue with the quota-status service: Something breaks when receiving mail with a recipient address that includes non-lowercase characters, for example foo at Example.com instead of foo at example.com: postfix log: postfix/smtp/smtpd[83387]: NOQUEUE: reject_warning: RCPT from

On 2018-03-03 21:47, Karol Augustin wrote: > On 2018-03-03 21:28, Stephan Bosch wrote: >> Op 3/2/2018 om 3:35 PM schreef Karol Augustin: >>> Hi, >>> >>> I am using Dovecot LDA as LMTP renders envelope extension unusable. >>> >>> The problem I have noticed is that when user has multiple aliases sieve >>> responds to all of them, not

Op 3/2/2018 om 3:35 PM schreef Karol Augustin: > Hi, > > I am using Dovecot LDA as LMTP renders envelope extension unusable. > > The problem I have noticed is that when user has multiple aliases sieve > responds to all of them, not only to :addresses specified. > > From testing it seems that :addresses only adds addresses to the list of > "known" emails to

Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? Using the same config that I've had for the past 10 or so point releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, but with 2.2.33 (and .1 and .2) no new logfiles are created, file descriptors still have the original files open and keep writings to those logs. On an idling test instance, I get: master:

On 07.11.2017 08:54, Aki Tuomi wrote: > > On 06.11.2017 23:31, David Zambonini wrote: >> Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? >> >> Using the same config that I've had for the past 10 or so point >> releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, >> but with 2.2.33 (and .1 and .2) no new logfiles are

Hallo Liste, hallo Ralf, danke schon mal. Ja die Whitespaces sind beim Rausl?schen entstanden. Ich verstand das so, dass das nun durch die address_verify_map erledigt w?rde. Muss ich dann entsprechend einfach auf die verweisen? Ich versuchte gerade die address_verify_map = btree:$data_directory/verify_cache auf local_recipient_maps = btree:$data_directory/verify_cache verweisen zu lassen.

On 2018-03-03 21:28, Stephan Bosch wrote: > Op 3/2/2018 om 3:35 PM schreef Karol Augustin: >> Hi, >> >> I am using Dovecot LDA as LMTP renders envelope extension unusable. >> >> The problem I have noticed is that when user has multiple aliases sieve >> responds to all of them, not only to :addresses specified. >> >> From testing it seems that

Hi list, many moons ago I asked about preserving hardlink between identical messages when pigeonhole (for sieve filtering) was used. The reply was that, while hardlink worked well for non-filtered messages, using pigeonhole broke the hardlink (ie: some message-specific data was appended to the actual mail file). Here you can find the original thread:

Hi, I am using Dovecot LDA as LMTP renders envelope extension unusable. The problem I have noticed is that when user has multiple aliases sieve responds to all of them, not only to :addresses specified. >From testing it seems that :addresses only adds addresses to the list of "known" emails to check against. It is not limiting it. As I understand, sieve should check if To: header