DELIVER(8)
π DELIVER(8) β the Cyrus IMAP glow-up edition β¨
okay bestie, sit down, hydrate, because we're about to talk about deliver, one of the Cyrus IMAP girlies. This is the Cyrus IMAP docs page for it. She's an 8th-section command (so like, sysadmin territory, main character energy but for mail servers), and she is literally the one who takes a message and puts it in the right mailbox. No cap. π
β¨ NAME β¨
deliver β Cyrus IMAP documentation
intro π
πΈ SYNOPSIS πΈ
deliver [ -C config-file ] [ -d ] [ -r address ]
[ -f address ] [ -m mailbox ] [ -a auth-id ]
[ -q ] [ userid ]...
deliver [ -C config-file ] -l
π¦ DESCRIPTION π¦
So here's the vibe: deliver reads a message straight off standard input and delivers it to one or more IMAP mailboxes. That's it. That's her job. She eats from stdin and feeds mailboxes. π
And she pulls her configuration options out of the imapd.conf(5) file, unless you tell her otherwise with -C. iykyk.
π OPTIONS π
-Cconfig-file β Use the specified configuration file config-file rather than the defaultimapd.conf(5). Like, "not that config, this config". β¨-dβ Ignored. Yeah, she's just here for compatibility with/bin/mail, nothing more. Lowkey a legacy queen. π-raddress,--return-path=address β Insert aReturn-Path:header containing address.-faddress β Insert aReturn-Path:header containing address. (same energy as-r, no long-option twin, sorry bestie)-mmailbox,--mailbox=mailbox β Deliver to mailbox.
If any userids are specified, attempts to deliver to user.userid.mailbox for each userid. If the ACL on any such mailbox does not grant the sender the "p" right, or if -m is not specified, then delivers to the INBOX for the userid, regardless of the ACL on the INBOX. π
If no userids are specified, attempts to deliver to mailbox. If the ACL on mailbox does not grant the sender the "p" right, the delivery fails. π
-aauth-id,--auth-id=auth-id β Specify the authorization id of the sender. Defaults to"anonymous". π«Ά-q,--ignore-quotaβ Deliver message even when receiving mailbox is over quota. She does not care about the quota, she is on a mission. π₯-l,--lmtpβ Accept messages using the LMTP protocol.
β NOTES β
Okay so this part matters, pay attention:
Depending on the setting of reject8bit in imapd.conf(5), deliver either rejects/accepts messages with 8-bit-set characters in the headers. And if she does accept messages with 8-bit-set characters in the headers, then depending on the setting of munge8bit, those characters are either left un-touched or changed to "X".
Why is it like this, you ask? Because those characters can't be interpreted since the character set is not known. That said, some communities that aren't well-served by US-ASCII assume those characters can represent characters that aren't present in US-ASCII. π
A method for encoding 8-bit-set characters is provided by RFC 2047. slay.
π EXAMPLES π
[NB: Examples needed]
(not me putting a placeholder in a manpage, iconic)
π FILES π
/etc/imapd.conf
π₯ SEE ALSO π₯
π«Ά AUTHOR π«Ά
The Cyrus Team, Nic Bernstein (Onlight)
π COPYRIGHT π
1993β2026, The Cyrus Team
k that's the whole page bestie, go deliver some mail π
Version 3.12.3, dated Jul 15, 2026 β shoutout to the Cyrus IMAP girlies, catch you on the flip side πβ¨
π¦ where this page comes from
- ubuntu stonking: cyrus-common 3.12.3-3build1 Β· CMU
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms