diff options
Diffstat (limited to 'pullimap.md')
-rw-r--r-- | pullimap.md | 25 |
1 files changed, 12 insertions, 13 deletions
diff --git a/pullimap.md b/pullimap.md index dd25571..1b2e509 100644 --- a/pullimap.md +++ b/pullimap.md @@ -5,7 +5,7 @@ Name ==== -PullIMAP - Pull mails from an IMAP mailbox and deliver them to a SMTP session +PullIMAP - Pull mails from an IMAP mailbox and deliver them to an SMTP session Synopsis ======== @@ -16,8 +16,8 @@ Synopsis Description =========== -`pullimap` retrieves messages from an IMAP mailbox and deliver them to a -SMTP or LMTP transmission channel. It can also remove old messages +`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 @@ -130,10 +130,10 @@ Valid options are: : One of `imap`, `imaps` or `tunnel`. `type=imap` and `type=imaps` are respectively used for IMAP and IMAP - over SSL/TLS connections over a INET socket. + over SSL/TLS connections over an INET socket. `type=tunnel` causes `pullimap` to create an unnamed pair of connected sockets for interprocess communication with a *command* - instead of a opening a network socket. + instead of opening a network socket. (Default: `imaps`.) *host* @@ -163,7 +163,7 @@ Valid options are: protocol][RFC 3501] on its standard output, and understand it on its standard input. The value is passed to `` `/bin/sh -c` `` if it contains shell metacharacters; otherwise it is split into words and - the list is passed to `execvp`(3). + the resulting list is passed to `execvp`(3). *STARTTLS* @@ -221,9 +221,8 @@ Valid options are: Attempting to connect to a server with a non-matching certificate SPKI fingerprint causes `pullimap` to abort the connection during the SSL/TLS handshake. - - You can use the following command to compute the SHA-256 digest of - certificate's Subject Public Key Info. + The following command can be used to compute the SHA-256 digest of a + certificate's Subject Public Key Info: openssl x509 -in /path/to/server/certificate.pem -pubkey \ | openssl pkey -pubin -outform DER \ @@ -266,7 +265,7 @@ Usually there are only two integers: the first is the *mailbox*'s smaller than this `UIDNEXT` value have already been retrieved and delivered). The [IMAP4rev1 specification][RFC 3501] does not guaranty that untagged -`FETCH` responses are sent ordered by UID in response to an `UID FETCH` +`FETCH` responses are sent ordered by UID in response to a `UID FETCH` command. Thus it would be unsafe for `pullimap` to update the `UIDNEXT` value in its *statefile* while the `UID FETCH` command is progress. Instead, for each untagged `FETCH` response received while the `UID @@ -281,7 +280,7 @@ FETCH` command is in progress. In more details, `pullimap` works as follows: - 1. Issue an `UID FETCH` command to retrieve message `ENVELOPE` and + 1. Issue a `UID FETCH` command to retrieve message `ENVELOPE` and `RFC822` (and `UID`) with UID bigger or equal than the `UIDNEXT` value found in the *statefile*. While the `UID FETCH` command is in progress, perform the following @@ -299,10 +298,10 @@ In more details, `pullimap` works as follows: i. append the message UID to the *statefile*. - 2. If a SMTP/LMTP transmission channel was opened, send a `QUIT` command + 2. If an SMTP/LMTP transmission channel was opened, send a `QUIT` command to terminate it gracefully. - 3. Issue an `UID STORE` command to mark all retrieved messages (and + 3. Issue a `UID STORE` command to mark all retrieved messages (and stalled UIDs found in the *statefile* after the eigth byte) as `\Seen`. |