Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xfer fails on unlimited quota (-1) #1452

Closed
brong opened this issue Sep 24, 2011 · 5 comments
Closed

xfer fails on unlimited quota (-1) #1452

brong opened this issue Sep 24, 2011 · 5 comments
Assignees

Comments

@brong
Copy link
Member

brong commented Sep 24, 2011

From: Wolfgang Breyha
Bugzilla-Id: 3559
Version: 2.4.11
Owner: Bron Gondwana

@brong
Copy link
Member Author

brong commented Sep 24, 2011

Attachment-Id: 1424
From: Wolfgang Breyha
Type: text/plain
File: cyrus-imapd-2.4.11-setquotafix.patch

fix for xfer_setquotaroot and cmd_setquota

@brong
Copy link
Member Author

brong commented Sep 25, 2011

From: Bron Gondwana

I swear there was another bug about this already... but I'll investigate and get a fix ready for 2.4.12

@brong
Copy link
Member Author

brong commented Sep 25, 2011

From: Bron Gondwana

(In reply to comment #1)
> I swear there was another bug about this already... but I'll investigate and
> get a fix ready for 2.4.12

In fact - your patch is great - accepted it as-is. I know it's going to be incompatible with 2.5 in lots of ways, so I don't know if we'll be taking it into mainline, but it will be in 2.4.12. Thanks.

@brong
Copy link
Member Author

brong commented Sep 25, 2011

From: Jeroen van Meeuwen (Kolab Systems)

(In reply to comment #2)
> (In reply to comment #1)
> > I swear there was another bug about this already... but I'll investigate and
> > get a fix ready for 2.4.12
>
> In fact - your patch is great - accepted it as-is. I know it's going to be
> incompatible with 2.5 in lots of ways, so I don't know if we'll be taking it
> into mainline, but it will be in 2.4.12. Thanks.

Note that with this patch we would accept:

. SETQUOTA user/john@example.org (STORAGE -1)

whereas previously we only accepted:

. SETQUOTA user/john@example.org ()

The former currently results in a bad argument list error in 2.4.11.

@brong
Copy link
Member Author

brong commented Sep 25, 2011

From: Bron Gondwana

(In reply to comment #3)
> Note that with this patch we would accept:
>
> . SETQUOTA user/john@example.org (STORAGE -1)
>
> whereas previously we only accepted:
>
> . SETQUOTA user/john@example.org ()
>
> The former currently results in a bad argument list error in 2.4.11.

Yeah, I'm not too disturbed about that - it's syntax that wouldn't have been accepted otherwise, and it doesn't add any capabilities that didn't exist before. AKA, I don't care that it leaks - and it fixes interoperability with old versions.

@brong brong closed this as completed Oct 4, 2011
@brong brong self-assigned this Dec 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant