aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuilhem Moulin <guilhem@fripost.org>2019-01-20 20:59:08 +0100
committerGuilhem Moulin <guilhem@fripost.org>2019-01-22 12:15:01 +0100
commita0267074033e24a8e1bf70ac3d434fbc335e06a2 (patch)
treed68c99e75de78249b99e740a61834e30a26ef5ba
parentbd843c74a3fab134fd3d651782fbb729a80056ae (diff)
d/control: Improve description.
-rw-r--r--debian/control55
1 files changed, 32 insertions, 23 deletions
diff --git a/debian/control b/debian/control
index cc84ed8..26ed46b 100644
--- a/debian/control
+++ b/debian/control
@@ -14,38 +14,47 @@ Depends: ${misc:Depends}, ${perl:Depends},
Description: Fast bidirectional synchronization for QRESYNC-capable IMAP servers
InterIMAP performs stateful bi-directional synchronization between two
IMAP4rev1 servers. Compared to the so-called "full" synchronization
- solutions, InterIMAP is both much faster and parsimonious regarding network
+ solutions, InterIMAP is both much faster and parsimonious in network
traffic.
.
Stateful synchronization is made possible by the QRESYNC extension from
[RFC7162]; for convenience reasons servers must also support LIST-EXTENDED
[RFC5258], LIST-STATUS [RFC5819] and UIDPLUS [RFC4315].
.
- Furthermore, while InterIMAP can work with servers lacking support for LITERAL+
- [RFC2088] and MULTIAPPEND [RFC3502], these extensions greatly improve
- performance by reducing the number of required round trips hence are
- strongly recommended.
-
-Package: libinterimap
-Architecture: all
-Depends: ${misc:Depends}, ${perl:Depends},
- libconfig-tiny-perl, libnet-ssleay-perl (>=1.73-1)
-Description: Net::IMAP::InterIMAP library and utils
- Net::IMAP::InterIMAP is a minimal IMAP4 client for QRESYNC-capable servers,
- used by interimap. It can also be used for non QRESYNC-capable servers, but
- that can be unsafe as it does not keep a mapping between message sequence
- numbers and UIDs.
+ Furthermore, while InterIMAP can work with servers lacking support for
+ LITERAL+ [RFC2088] and MULTIAPPEND [RFC3502], these extensions greatly
+ improve performance by reducing the number of required round trips and it
+ thus strongly recommended to use a server supporting these.
+ .
+ InterIMAP supports the COMPRESS=DEFLATE extension from [RFC4978]. It is
+ enabled by default on remote servers advertising it, in order to reduce
+ network traffic, especially for long-lived connections.
Package: pullimap
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends},
libinterimap (>= ${source:Upstream-Version}~)
-Description: Pull mails from an IMAP mailbox and deliver them to a SMTP session
- PullIMAP retrieves messages from an IMAP mailbox and deliver them to a SMTP
- or LMTP transmission channel. It can also remove old messages after a
- configurable retention period.
+Description: Pull mails from an IMAP mailbox and deliver them via SMTP or LMTP
+ PullIMAP retrieves messages from an IMAP mailbox and deliver them to an
+ SMTP or LMTP transmission channel. It can also remove old messages after
+ a configurable retention period.
.
- A statefile is used to keep track of the mailbox’s UIDVALIDITY and UIDNEXT
- values. While PullIMAP is running, the statefile is also used to keep track
- of UIDs being delivered, which avoids duplicate deliveries if the process is
- interrupted.
+ A statefile is used to keep track of the mailbox's UIDVALIDITY and UIDNEXT
+ values. While PullIMAP is running, the statefile is also used to keep
+ track of UIDs being delivered, which avoids duplicate deliveries if the
+ process is interrupted.
+ .
+ PullIMAP supports the COMPRESS=DEFLATE extension from [RFC4978]. It is
+ enabled by default on servers advertising it, in order to reduce network
+ traffic, especially for long-lived connections (when IDLE commands are
+ enabled.)
+
+Package: libinterimap
+Architecture: all
+Depends: ${misc:Depends}, ${perl:Depends},
+ libconfig-tiny-perl, libnet-ssleay-perl (>=1.73-1)
+Description: Net::IMAP::InterIMAP library and utils
+ Net::IMAP::InterIMAP is a minimal IMAP4rev1 client for QRESYNC-capable
+ servers, used by interimap. It can also be used with non QRESYNC-capable
+ servers, but doing so can be unsafe as the client does not store any
+ in-session mapping between message sequence numbers and UIDs.