1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
Source: interimap
Section: mail
Priority: optional
Maintainer: Guilhem Moulin <guilhem@guilhem.org>
Build-Depends: debhelper (>= 9), jq, pandoc
Standards-Version: 3.9.6
Vcs-Git: https://git.guilhem.org/interimap
Vcs-Browser: https://git.guilhem.org/interimap
Package: interimap
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends},
libinterimap, libdbi-perl, libdbd-sqlite3-perl
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
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
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.
Package: pullimap
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends},
libinterimap
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.
.
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.
|
