search for: 36e81cbe2892

Hi, I have an OpenSMTPD / Dovecot installation on an OpenBSD server. I recently came across an issue where Dovecot LMTP would reject a message sent to a local user from an address which contains a single apostrophe (e.g. firstname.o'lastname at example.com). Apparently apostrophe, as well as a number of other special characters, are valid characters in the local part of the email address

...xample.com> to=<me at example.org> rcpt=<me at example.org> user=me delay=0s result=PermFail stat=Error ("mail.lmtp: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in localpart") That's essentially the same bug as mentioned in <6386018f-22b2-9562-b5a2-36e81cbe2892 at debian.org> (bounces on invalid UTF-8 in localpart) that got assigned DOP-1045. Dovecot LDA and LMTP should just not care about remote address validity when delivering locally. It's not the LDA's business.

...m> to=<me at example.org> rcpt=<me at example.org> user=me delay=0s result=PermFail stat=Error ("mail.lmtp: LMTP server error: 501 5.5.4 Invalid FROM: Invalid character in localpart") > > That's essentially the same bug as mentioned in <6386018f-22b2-9562-b5a2-36e81cbe2892 at debian.org> (bounces on invalid UTF-8 in localpart) that got assigned DOP-1045. Dovecot LDA and LMTP should just not care about remote address validity when delivering locally. It's not the LDA's business. Ah, thanks a lot for that. I was trying to find any information about that, bu...

Hi list. I'm using dovecot as postfix's LDA. The version is 2.3.6. Last week some spammer set the envelope's FROM to "foo at bar@domain.com" (with two @). While trying to deliver (as this one didn't hit the spamassassin's score), dovecot said the following: Jun 21 02:35:58 mymailserver postfix/pipe[29736]: ADA268195E: to=<user at mydomain>, relay=dovecot,