Hi Ellie
I think you got most of it.
The object storage implementation was built on top of the "archive_enabled"
feature. Both must be enable for the object storage to kick in. Or in
other words it is only when a file (email) must be archive that it will go
into object storage.
You can enable
Hi Bron
Sorry for the delay and thank you for pushing this work to master.
A) While doing this, some of the logic was broken. (This is now fix.)
B) The new solution works very well with a mix of archive (in object
storage) and non archive (on regular spool) emails.
C) Unarchive have been fix. (
AEDT Monday Feb 29th. (In other
> words: in a few hours from now)
>
> https://plus.google.com/hangouts/_/g4xnqjjb5zvomzeb4kqvja3fz4a
>
> Looking forward to hearing your news.
>
>Nicola
>
> On Wed, Feb 24, 2016, at 01:39 AM, Raymond Poitras via Cyrus-devel wrote:
>
Hi Bron,
Really sorry for the delay. It took me a while to get back to this.
It is harmless (other than a waste of CPU cycle) to call delete "if the
record isn't there".
It must be found in that specific mailbox for something to happen.
Nevertheless, I made some small logic adjustment.
Also clean
