cyrus 2.3.3 change + solved: permission denied setting flags
Bron Gondwana
brong at fastmail.fm
Thu May 18 13:02:41 EDT 2006
On Fri, May 19, 2006 at 02:40:11AM +1000, Robert Mueller wrote:
> [...] saying that it's in [READ-WRITE] mode on an "examine"
> while previously it used to say [READ-ONLY]. Is that an expected behaviour
> change, or a bug?
And if it's expected, then why was it saying "Permission denied" when our
code took it at its word and tried to set flags on a message!
Our solution is to be conservative in what we believe, and storing
'read-only' in our internal "connection state" data if we asked
for an examine rather than a select - regardless of the server's
response. This feels like a good idea that will keep working just
fine when the bug is fixed, and protect us against any future
regressions!
Bron.
More information about the Info-cyrus
mailing list