search for: faeustlin

The recipients in the vacation :addresses String list are matched case-sensitive. If the recipient gets a mail with wrong case, the message is discarded with: "discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers" I think the matching should be case-insensitive. Is this a bug or do I miss some option? I'm

On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot < dovecot at dovecot.org> > Further investigation showed me that it has to be a bug. > > I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24 > (5a7e9e62): > > In this version the additional addresses in vacation :addresses > ["test at e...

> On 9 Sep 2019, at 16.17, Philipp Faeustlin via dovecot <dovecot at dovecot.org> wrote: > >> It is not recommended to rely on local-part case, but it is indeed >> case-sensitive. >> And this is to avoid such issues that postfix supports address >> cleanup/canonicalisation before forwarding mails...

Am 02.09.19 um 15:05 schrieb Philipp Faeustlin via dovecot: > The recipients in the vacation :addresses String list are matched > case-sensitive. > > If the recipient gets a mail with wrong case, the message is discarded > with: > "discarding vacation response for implicitly delivered message; no known > (envelope)...

> Le 4 sept. 2019 ? 19:37, Roger Klorese via dovecot <dovecot at dovecot.org> a ?crit : > > > > On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> > Further investigation showed me that it has to be a bug. > > I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24 > (5a7e9e62): > > In this version the additional addresses in va...

On 02/09/2019 15:05, Philipp Faeustlin via dovecot wrote: > The recipients in the vacation :addresses String list are matched > case-sensitive. > > If the recipient gets a mail with wrong case, the message is discarded > with: > "discarding vacation response for implicitly delivered message; no > known (enve...

> > It is not recommended to rely on local-part case, but it is indeed > case-sensitive. > > And this is to avoid such issues that postfix supports address > cleanup/canonicalisation before forwarding mails to dovecot. > > ---------- > RFC 5321: > > "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive > [?] > While the above definition

Hello List, with dovecot version 2.2.13.9, I actually have a problem using lazy_expunge and acl together. Shared/Public Folders work fine with lazy_expunge disabled. If lazy_expunge is enabled and userA got a shared folder form userB, then there is the error shown in subject. My test case to reproduce the error. doveadm mailbox list -u userA at domain --> Output Fine. doveadm acl set -u

> It is not recommended to rely on local-part case, but it is indeed > case-sensitive. > > And this is to avoid such issues that postfix supports address > cleanup/canonicalisation before forwarding mails to dovecot. > > ---------- > RFC 5321: > > "Local-part ? ? = Dot-string / Quoted-string ; MAY be case-sensitive > [?] >

Hello Timo, Hello Dovecot Developers, Hello everyone on the list, I think I have some bug, because I haven't found a working configuration till now. I use latest dovecot 2.2.13 from the dovecot-ee repository, with acl and the lazy_expunge plugin. My configuration for shared folders work fine with lazy_expunge disabled. If I enable lazy_expunge and the user (named userA), which I'm

Am 27.07.2015 um 11:41 schrieb Ralf Hildebrandt: > * Daniel Tr?der <troeder at univention.de>: > >> Just guessing? >> >> The signature of the command is: >> doveadm [-Dv] import [-S socket_path] [-s] -u user source_location >> dest_parent search_query >> >> You supply "" as dest_parent which I guess could mean ".", and that