44 lines
1.8 KiB
Plaintext
44 lines
1.8 KiB
Plaintext
MBOX-Line: From tss at iki.fi Fri Jun 11 07:27:30 2010
|
|
To: imap-protocol@u.washington.edu
|
|
From: Timo Sirainen <tss@iki.fi>
|
|
Date: Fri Jun 8 12:34:43 2018
|
|
Subject: [Imap-protocol] IMAP MOVE extension
|
|
In-Reply-To: <201006111547.09949.witold.krecicki@firma.o2.pl>
|
|
References: <201006110854.37969.witold.krecicki@firma.o2.pl>
|
|
<201006111454.51874.witold.krecicki@firma.o2.pl>
|
|
<1276262838.22134.61.camel@kurkku.sapo.corppt.com>
|
|
<201006111547.09949.witold.krecicki@firma.o2.pl>
|
|
Message-ID: <1276266450.22134.92.camel@kurkku.sapo.corppt.com>
|
|
|
|
On pe, 2010-06-11 at 15:47 +0200, Witold Kr?cicki wrote:
|
|
> > > > > And how hard it would be to really implement it in Dovecot?
|
|
> > > >
|
|
> > > > Much more difficult than I originally thought.
|
|
> > >
|
|
> > > Well, 'brutal' (and nonsense in a way) implementation would be to
|
|
> > > 'internally' do copy messages listed and then expunge messages that were
|
|
> > > copied (at least there is no setting flags).
|
|
> >
|
|
> > The problem is that I'd have to add a new internal "move" operation, and
|
|
> > then quota code would also have to handle it, and there are probably
|
|
> > many other places that would need to handle it. Also the whole move
|
|
> > operation doesn't really even fit into Dovecot's internal design. It
|
|
> > would be difficult to implement in any other way than copy+expunge (but
|
|
> > with all the extra complexity in quota/etc code).
|
|
> Still - is it worth the effort?
|
|
|
|
I don't currently see it being worth the trouble. Maybe I'll implement
|
|
it some day, but only if my employer wants it.
|
|
|
|
Actually, I just thought of another simple way to implement it:
|
|
|
|
1) Temporarily disable quota enforcing
|
|
2) copy
|
|
3) expunge
|
|
4) Enable quota enforcing
|
|
|
|
The only benefit with that would then be able to move messages without
|
|
running out of quota. I guess I could implement that..
|
|
|
|
|