NOTIFYD(8)

πŸ’Œ NOTIFYD(8) β€” the Cyrus IMAP notification server, bestie edition πŸ’Œ

okay so this is the manual page for notifyd, part of the Cyrus IMAP docs, and honestly? she's a whole vibe. she's the little daemon in the group chat who actually delivers the messages. let's get into it 🫢


✨ NAME ✨

notifyd β€” that's the Cyrus notification server, fr fr. she handles the notifs so other daemons don't have to. iconic behaviour honestly πŸ’…


🌸 SYNOPSIS 🌸

notifyd [ -C config-file ] [ -U uses ] [ -T timeout ] [ -D ]

that's it. that's the whole summon-her incantation. ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so notifyd is a daemon, meaning she's out here living her life in the background, started up from master(8). her whole job? handling notification requests on behalf of lmtpd(8). like, lmtpd slides into her DMs with a request, and notifyd takes it and actually performs the notification using whatever method the request specified. she's the one who sends the message. the main character energy is real. πŸ‘‘

bestie, listen, this part is important: for notifyd to run properly you must set proto=udp in her cyrus.conf(5) services entry. the docs also recommend prefork=1. no cap, do both. πŸ’€

notifyd reads her config options out of the imapd.conf(5) file β€” unless you tell her otherwise with -C.

and the notifysocket option? that's the one that specifies the Unix domain socket she listens on for notifications. that's her lil doorstep where the notifs get delivered. πŸŽ€


πŸ’– OPTIONS πŸ’–

  • -C config-file β€” use the config file config-file instead of the default imapd.conf(5). like, "no thanks default, I brought my own." πŸ’…
  • -U uses β€” the maximum number of times the process should be used for new connections before shutting down. default is 250. she's got stamina but even she has limits. 🫢
  • -T timeout β€” the number of seconds the process will wait for a new connection before shutting down. note that a value of 0 (zero) will disable the timeout entirely. default is 60. ⏳
  • -D β€” run the external debugger specified in debug_command. yes she's getting debugged. it's giving "under observation." πŸ”

🌈 NOTIFICATION METHODS 🌈

these are the flavours of notif delivery. pick your fighter:

  • null β€” ignore the notification request entirely. ghosted. πŸ’€
  • log β€” log the notification to syslog. (this one's for testing, bestie, not for the real thing.) πŸ“
  • mailto β€” email the notification. heads up: this method can ONLY be used in a Sieve 'notify' action, because it requires a mailto: URL to be specified as an :option. no mailto URL? no service. periodt. πŸ“§
  • zephyr β€” send the notification as a zephyrgram. and if you're using it in a Sieve 'notify' action, you can specify additional recipients as :options. extra credits, extra recipients. ✨
  • external β€” send the notification via an external program. the path to that program is specified using the notify_external option in the configuration file. outsourcing, but make it classy. 🧚

πŸŽ€ FILES πŸŽ€

  • /etc/imapd.conf
  • /etc/cyrus.conf

the two sacred texts. πŸ’œ


πŸ’œ SEE ALSO πŸ’œ

go read those too, bestie, iykyk. πŸ“š


πŸ‘‘ AUTHOR πŸ‘‘

The Cyrus Team, Nic Bernstein (Onlight). legends only, honestly. 🫢


1993–2026, The Cyrus Team


and that's the whole page!! tysm for reading, she ate and left no crumbs πŸ“

sign-off: this darling little manual is Cyrus IMAP version 3.12.3, dated Jul 15, 2026. mwah. πŸ’– 🌈 ✨

πŸ“¦ where this page comes from