I don't see a downside to have one monolithic package. I think its
easier for an admin to have everything available to them in one package
rather than having to go find the correct package for the optional piece
they are looking for. But that's just me.
On 3/12/19 12:39 PM, Patrick Goetz w
I'm finally getting around to updating the Arch linux cyrus-imapd
package, and have a question.
Looking through the configuration options, it looks like there are a
number of functionality critical decisions to be made:
CalDAV and CardDAV
./configure --enable-http --enable-calalarmd
Mu
On 3/12/19 9:27 AM, Marco wrote:
Hello,
could you help me to understand how Cyrus IMAP works with rename at
INBOX level?
RFC3501 says that "Renaming INBOX is permitted, and has special
behavior. It moves all messages in INBOX to a new mailbox with the
given name, leaving INBOX empty."
If I remember correctly, Cyrus only permits the owner of the INBOX to
rename it. Proxy authenticate as n...@example.com and try again.
On 3/12/19 8:27 AM, Marco wrote:
Hello,
could you help me to understand how Cyrus IMAP works with rename at
INBOX level?
RFC3501 says that "Renaming INBO
Hello,
could you help me to understand how Cyrus IMAP works with rename at
INBOX level?
RFC3501 says that "Renaming INBOX is permitted, and has special
behavior. It moves all messages in INBOX to a new mailbox with the
given name, leaving INBOX empty."
If I try with Cyrus IMAP I see:
*
