1 Mar
2011
1 Mar
'11
11:20 p.m.
On Tue, Mar 01, 2011 at 09:21:06PM +0100, Sven Hartge wrote:
Hi!
I am in the planning stage for an upgrade of my employers mail system.
In the backend I will be using dovecot which supports IMAP COMPRESS
<http://www.ietf.org/rfc/rfc4978.txt>,
<http://wiki2.dovecot.org/Plugins/Compress>.
In the frontend I would like to continue using perdition.
Hi Sven,
I think that you are correct and the only thing that you will need to teach
perdition is the correct capabilities to advertise. That can be done
through the configuration file.
From the RfC I assume, perdition should cope with
IMAP COMPRESS, since
everything after a successful authentication is just passed
through.
From the RfC:
,----
| The following example illustrates how commands and responses are
| compressed during a simple login sequence:
|
| S: * OK [CAPABILITY IMAP4REV1 STARTTLS COMPRESS=DEFLATE]
| C: a starttls
| S: a OK TLS active
|
| From this point on, everything is encrypted.
|
| C: b login arnt tnra
| S: b OK Logged in as arnt
| C: c compress deflate
| S: d OK DEFLATE active
|
| From this point on, everything is compressed before being
| encrypted.
`----
Is my assumption correct that it is safe to use perdition in such a
setup? Or am I threading on thin ice here, bound for disaster?