On Wed, Dec 4, 2019, at 1:14 PM, Stephan Bosch via dovecot wrote:
>
>
> On 17/08/2018 09:14, Stephan Bosch wrote:
> >
> >
> > Op 14/05/2018 om 23:03 schreef James Cassell:
> >>
> >> On Mon, May 14, 2018, at 4:52 PM, Stephan Bosch wrote:
> >&g
've not used the duplicate test anywhere in your example. See the RFC for
examples:
https://tools.ietf.org/html/rfc7352#section-5
Specifically, example 3 might help:
https://tools.ietf.org/html/rfc7352#section-5.3
but most simply, you can probably replace `if true` with `if not duplicate`
V/r,
James Cassell
ion RFC, it should
fallback to case-insensitive: https://tools.ietf.org/html/rfc5230
You could try working around the issue by adding to your `vacation` statement:
`:comparator "i;ascii-casemap"` -- but in any case, I'd file a bug about the
non-standard behavior.
V/r,
James Cassell
> Thanks
> Julian
>
>
Look at the currentdate test https://tools.ietf.org/html/rfc5260#section-5
V/r,
James Cassell
On Sat, Jan 5, 2019, at 11:26 AM, Jerry wrote:
> I am able to get sieve issuing an "out of office"message correctly.
> However, I want to configure it to send an "OOO" mes
On Mon, May 14, 2018, at 4:52 PM, Stephan Bosch wrote:
>
>
> Op 25/04/2018 om 22:49 schreef James Cassell:
> > On Wed, Apr 25, 2018, at 3:20 PM, Stephan Bosch wrote:
> >>
> >> Specify the ID used for duplicate checking explicitly using the
> >> :uniq
> My conclusion was the duplicate detection function is global to all
> > folders.
> >
> > If I could restrict the detection of duplicates in the current folder
> > only, this would let me run the import program again without error.
>
> Specify the ID used for duplicate checking explicitly using the
> :uniqueid argument (https://tools.ietf.org/html/rfc7352#section-3.1).
> Using the variables extenion, compose the uniqueid from the message-id
> and the mailbox name.
>
In my experience with dovecot's implementation, you can set the ID only once in
a script. If you try to filter duplicates based on multiple IDs, only the
first (or last, I don't remember) takes effect.
V/r,
James Cassell
> ssl = required
> > ssl_cert = > ssl_key = # hidden, use -P to show it
> > userdb {
> >args = /etc/dovecot/dovecot-sql.conf.ext
> >default_fields = uid=mail gid=mail home=/var/mail/%u master_user=%u
> >driver = sql
> > }
> > userdb {
> >args = /etc/dovecot/dovecot-ldap.conf.ext
> >default_fields = uid=mail gid=mail home=/var/mail/%u master_user=%u
> >driver = ldap
> > }
> > protocol lda {
> >mail_plugins = acl quota notify mail_log stats lazy_expunge sieve
> > }
> > protocol imap {
> >mail_max_userip_connections = 25
> >mail_plugins = acl quota notify mail_log stats lazy_expunge imap_quota
> > imap_stats
> > }
> >
> > I tested this with different users with the same result.
> > I tested and reproduced the error with Thunderbird and Roundcube.
> > The Apple Mail client uses IMAP COPY + DELETE, instead of IMAP MOVE, and no
> > errors are reported. So I think it's related to the IMAP MOVE
> > implementation on Dovecot server.
> >
> >
> > Has anyone seen the same error?
> > Any suggestions? Is this a Dovecot bug?
> >
> > ---
> > Daniele Barresi
> Hi!
>
> We'll open a bug on this. Thanks for reporting it.
>
> Aki
Hello,
I'm also seeing this error on Dovecot 2.2.27 from Debian jessie-backports. The
error seems to come up when trying to move FROM a folder for which the user
doesn't have the EXPUNGE ACL. It doesn't have to be a shared folder (and in my
case, it is not a shared folder.) My workaround is to not advertise the MOVE
capability, but long-term, it's better to fix the crash.
V/r,
James Cassell
t;name+foo" works. This is with dovecot-sieve 2.2.13, postfix here
> obviously does not alter the To header.
>
Since the header doesn't actually contain an e-mail address, I wouldn't expect
the subaddress extension, or even just the address test to do anything sane,
but that's just me.
V/r,
James Cassell
ermission:
4.2. RFC 4314, Access Control List (ACL)
The ACL rights [RFC4314] required for MOVE and UID MOVE are the union
of the ACL rights required for UID STORE, UID COPY, and UID EXPUNGE.
You should be able to get the old behavior back by overriding the CAPABILITY
response in the dovecot configuration to exclude "MOVE".
Hope that helps.
V/r,
James Cassell
=user@domain
> -write-seen
>
Thanks for sharing the solution you found.
V/r,
James Cassell
10 matches
Mail list logo
