DELIVER(8)
π DELIVER(8) β Cyrus IMAP π
okay bestie, welcome to deliver, part of the Cyrus IMAP documentation fam. this one's a lil intro to the whole deliver situation, so grab a boba and let's get into it π§β¨
πΈ SYNOPSIS πΈ
deliver [ -C config-file ] [ -d ] [ -r address ]
[ -f address ] [ -m mailbox ] [ -a auth-id ]
[ -q ] [ userid ]...
deliver [ -C config-file ] -l
two whole modes, pick your fighter π
β¨ DESCRIPTION β¨
so deliver does the thing: it reads a message off standard input and drops it into one or more IMAP mailboxes. that's the whole vibe. mail goes in, mail comes out, nobody gets hurt π¦
and it's a good listener, fr fr β it pulls its configuration options out of the imapd.conf(5) file, unless you tell it otherwise with -C. no cap.
π OPTIONS π
-C config-fileβ bestie, use thisconfig-fileinstead of the defaultimapd.conf(5). your config, your rules β¨-dβ literally ignored. it's just here for compatibility with/bin/mail. it's giving "i'm just here so i don't get fined" π-r address,--return-path=addressβ pops aReturn-Path:header in there containing address π-f addressβ same energy, same slay: inserts aReturn-Path:header containing address.-m mailbox,--mailbox=mailboxβ deliver to mailbox. here's the tea tho:- if any userids are specified, it tries to deliver to
user.userid.mailboxfor each userid. but if the ACL on any such mailbox does not grant the sender the"p"right, or if-mwasn't specified at all, then it delivers to theINBOXfor the userid β regardless of the ACL on the INBOX. yeah, the INBOX has no gatekeeper, iconic behavior tbh π - if no userids are specified, it tries to deliver to mailbox. and if the ACL on mailbox doesn't grant the sender the
"p"right? the delivery fails. periodt. π
- if any userids are specified, it tries to deliver to
-a auth-id,--auth-id=auth-idβ specify the authorization id of the sender. defaults to"anonymous"because mystery is a lifestyle π΅οΈββοΈ-q,--ignore-quotaβ deliver the message even when the receiving mailbox is over quota. rules are fake, quotas are fake, mail must flow π₯-l,--lmtpβ accept messages using the LMTP protocol. fancy protocol moment β¨
π NOTES π
this part is important so listen up, bestie π«Ά
depending on the setting of reject8bit in imapd.conf(5), deliver either rejects or accepts messages with 8-bit-set characters in the headers. and if we do 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". yeah. just an X. mysterious. π
why tho? because such characters can't be interpreted since the character set is not known β even though some communities that aren't well-served by US-ASCII assume those characters can be used to represent characters that aren't present in US-ASCII. it's giving wishful thinking, ngl π
good news tho: a method for encoding 8-bit-set characters is provided by RFC 2047. so there's a whole correct way to do this, bestie π
π EXAMPLES π
[NB: Examples needed]
yeah. the examples section is empty. not me pointing at the void π (that's literally what the page says, i don't make the rules)
π FILES π
/etc/imapd.conf
π SEE ALSO π
lmtpd(8)β go say hi to the LMTP daemon, it's the sibling π
βοΈ AUTHOR βοΈ
the legends themselves: The Cyrus Team, and Nic Bernstein (Onlight) π«Ά
Β©οΈ COPYRIGHT Β©οΈ
1993β2026, The Cyrus Team β a whole legacy, fr fr π
and that's the whole page, bestie!! π this was DELIVER(8) from Cyrus IMAP, version 3.12.4, dated Sep 09, 2026. go forth and deliver your mail with main character energy πβ¨ mwah π
π¦ where this page comes from
- fedora 44: cyrus-imapd 3.12.4-1.fc44 Β· BSD-Attribution-HPND-disclaimer
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms