1DELIVER(8)                        Cyrus IMAP                        DELIVER(8)
2
3
4

NAME

6       deliver - Cyrus IMAP documentation
7
8       intro
9

SYNOPSIS

11       deliver [ -C config-file ] [ -d ] [ -r address ]
12              [ -f address ] [ -m mailbox ] [ -a auth-id ]
13              [ -q ] [ userid ]...
14       deliver [ -C config-file ] -l
15

DESCRIPTION

17       deliver  reads a message from the standard input and delivers it to one
18       or more IMAP mailboxes.
19
20       deliver reads its configuration options out of the  imapd.conf(5)  file
21       unless specified otherwise by -C.
22

OPTIONS

24       -C config-file
25              Use the specified configuration file config-file rather than the
26              default imapd.conf(5).
27
28       -d     Ignored for compatibility with /bin/mail.
29
30       -r address
31              Insert a Return-Path: header containing address.
32
33       -f address
34              Insert a Return-Path: header containing address.
35
36       -m mailbox
37              Deliver to mailbox.  If any userids are specified,  attempts  to
38              deliver  to  user.userid.mailbox for each userid.  If the ACL on
39              any such mailbox does not grant the sender the “p” right  or  if
40              -m  is not specified, then delivers to the INBOX for the userid,
41              regardless of the ACL on the INBOX.
42
43              If no userids are specified, attempts to deliver to mailbox.  If
44              the  ACL on mailbox does not grant the sender the “p” right, the
45              delivery fails.
46
47       -a auth-id
48              Specify the authorization id of the sender.  Defaults to “anony‐
49              mous”.
50
51       -q user-id
52              Deliver message even when receiving mailbox is over quota.
53
54       -l     Accept messages using the LMTP protocol.
55

NOTES

57       Depending on the setting of reject8bit in imapd.conf(5), deliver either
58       rejects/accepts messages with 8-bit-set characters in the headers.   If
59       we  accept  messages with 8-bit-set characters in the headers, then de‐
60       pending on the setting of munge8bit, these characters are  either  left
61       un-touched or changed to “X”.
62
63       This  is because such characters can’t be interpreted since the charac‐
64       ter set is not known, although  some  communities  not  well-served  by
65       US-ASCII  assume that those characters can be used to represent charac‐
66       ters not present in US-ASCII.
67
68       A method for encoding 8-bit-set characters is provided by RFC 2047.
69

EXAMPLES

71       [NB: Examples needed]
72

FILES

74       /etc/imapd.conf
75

SEE ALSO

77       lmtpd(8)
78

AUTHOR

80       The Cyrus Team, Nic Bernstein (Onlight)
81

83       1993–2022, The Cyrus Team
84
85
86
87
883.6.0                          December 12, 2022                    DELIVER(8)
Impressum