DBMAIL-IMAPD(8)
πΈ dbmail-imapd(8) β the IMAP girlie π
okay so bestie, welcome to dbmail-imapd, a page from the DBMAIL-IMAPD(8) manual β¨ (yes that's the manual section, no we're not gonna be normal about it).
β¨ NAME β¨
dbmail-imapd β the whole entire vibe is that it gives clients access to the DBMail system, but only for clients that support Internet Message Access Protocol, IMAP4r1, exactly as specified in RFC 3501 π
β¨ SYNOPSIS β¨
dbmail-imapd [--config configfile] [--pidfile pidfile]
dbmail-imapd [--config configfile] [--pidfile pidfile] --no-daemon
dbmail-imapd [--config configfile] [--pidfile pidfile] --inetd
like, three whole ways to launch her. pick your fighter π
β¨ DESCRIPTION β¨
so the dbmail-imapd daemon is a fully featured IMAP4r1 server. that's it, that's the whole description, and honestly? she ate. π
β¨ OPTIONS β¨
-p,--pidfilepidfile β specify an alternate pid file, bestie π«Ά by default the daemons usedbmail-<daemon>.pidfor their pid files, and they save them in the directory specified by thepid_directoryentry indbmail.conf, or if that does not exist, the value set by the configuration option--localstatedir. and she will halt if the pid file cannot be written π so like, be normal about this. use the-ppidfile option to place the pid file in your system's preferred location.-n,--no-daemonβ No daemonize: inetd mode π the program remains attached to the console from which it was started and will read and write on stdin/stdout. this is useful for debugging when combined with the-voption. it's also used for running from (x)inetd. it's giving "I'm right here in the terminal with you" πΈ-D,--inetdβ No daemonize: the program remains attached to the console and will listen on the network sockets defined indbmail.confπ₯ this is mostly used for xinetd (Extended Internet Service Daemon).
β¨ COMMON OPTIONS β¨
-f,--configconfigfile β specify an alternate config file β¨
use dbmail-<utility> --help to show the default location. iykyk π
-q,--quietβ quietly skip interactive prompts and helpful status messages which would otherwise be printed to stdout π use two-q's to silence errors which would otherwise be printed to stderr. double quiet is lowkey the icon behavior.-v,--verboseβ operate verbosely π£οΈ some of the utilities in the DBMail suite can take two-v's for extra verbosity. those which don't understand this convention won't complain about having the extra-vand will simply operate at their normal verbosity. no drama, no cap π-V,--versionβ show the version and copyright, then exit β-h,--helpβ show a brief summary of options, then exit π¦
β¨ EXAMPLE β¨
for xinetd π§
# /etc/xinet.d/dbmail-imap
#
service imap
{
socket_type = stream
wait = no
user = root
server = /usr/local/sbin/dbmail-imapd
protocol = tcp
server_args = -n
log_on_failure += USERID
disable = no
}
for stunnel π
pid = /var/run/stunnel.pid
cert = /etc/stunnel/yourkeys.pem
# The next two sections will turn stunnel
# into a 'secure inetd'. This is mutually
# exclusive with the proxy sections below.
[dbmail-pop3d]
accept = 995
exec = /usr/local/sbin/dbmail-pop3d
execargs = dbmail-pop3d -n
[dbmail-imapd]
accept = 993
exec = /usr/local/sbin/dbmail-imapd
execargs = dbmail-imapd -n
# The next two sections will proxy
# from the secure protocol over to
# the insecure protocol. In this case,
# use BINDIP=localhost in dbmail.conf!
[pop3s]
accept = 995
connect = 110
[imaps]
accept = 993
connect = 143
# Useful if your preferred SMTP server doesn't do SSL/TLS.
# This is with your MTA configuration, not DBMail, per se.
[ssmtp]
accept = 465
connect = 25
bestie please read that comment block up there β the secure-inetd sections are mutually exclusive with the proxy sections below them. that's literally stated. don't mix them π
β¨ SEE ALSO β¨
dbmail(1), dbmail.conf(5), dbmail-deliver(1), dbmail-export(8), dbmail-httpd(8), dbmail-imapd(8), dbmail-lmtpd(8), dbmail-pop3d(8), dbmail-sieved(8), dbmail-sievecmd(8), dbmail-users(8), dbmail-util(8) β yeah she's in the group chat with all her sisters π«Ά
β¨ BUGS β¨
- for the latest announcements, please subscribe to the DBMail announce mailing list<sup>1</sup> π£
- for general discussion, please subscribe to the DBMail general mailing list<sup>2</sup> π¬
- if you experience an issue with DBMail, please report it on the DBMail Bug Tracker<sup>3</sup>. it may be helpful to have a debug log available π (ngl a debug log is the moment)
β¨ LICENSE β¨
DBMail and its components are distributed under the terms of the GNU General Public License Version 2. copyrights are held variously by the authors listed below βοΈ
β¨ AUTHOR(S) β¨
DBMail is a collaborative effort among the core developers listed below and the tremendous help of the testers, patchers and bug hunters listed in the AUTHORS and THANKS files found in the DBMail source distribution π«Ά
Alan Hicks Persistent Objects Ltd https://p-o.co.uk
Eelco van Beek Aaron Stone Paul J Stevens
Roel Rozendaal Open Source Engineer NFG Net Facilities Group BV
Ilja Booij Palo Alto, CA USA http://www.nfg.nl
IC&S http://www.ic-s.nl
β¨ AUTHOR β¨
Alan Hicks <ahicks@p-o.co.uk> β Author. π
β¨ NOTES β¨
- DBMail announce mailing list
https://dbmail.org/wws/info/dbmail-announce/ - DBMail general mailing list
https://dbmail.org/wws/info/dbmail-general/ - DBMail Bug Tracker
https://github.com/dbmail/dbmail/issues
okay that's the whole page, you're so welcome π this little DBMAIL-IMAPD(8) beauty has been out here since the 08/28/2026 build, so go forth, run your daemon, and slay β¨π¦π
π¦ where this page comes from
- arch rolling: dbmail 3.5.6-2 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms