IMAPGOOSE.CONF(5)
π imapgoose.conf β the vibe guide π
okay so this is the configuration file for imapgoose, from the File Formats Manual girlies π
literally the file that tells imapgoose(1) which IMAP accounts to sync and where to put your mail. bestie, it's the whole map πΊοΈβ¨
πΈ DESCRIPTION πΈ
imapgoose(1) uses scfg format for its configuration file, no cap. The file is just one or more account blocks, and each block defines one IMAP account to synchronize plus its matching local directory. that's it, that's the whole thing π«Ά
every mailbox for each account is automatically discovered and synchronized β like, it handles it, you don't have to. there's no mailbox selectivity, periodt. you get all of them or, well, all of them π
π FILE FORMAT π
the config uses a simple structured configuration format. each account lives inside an account block, like this iconic little number:
account example {
server imap.example.com:993
username user@example.com
password-cmd pass show email/example
local-path ~/mail/example
max-connections 3
post-sync-cmd notmuch new
}
that's the template, bestie β copy the vibe π¦
β¨ ACCOUNT DIRECTIVES β¨
each account block supports these directives, and yes we're going through all of them π
server host:portβ (optional) the IMAP server address and port. TLS/SSL is always used (port993is the standard one, iykyk). STARTTLS is deprecated and is not supported β like, not even a little bit, don't ask π. defaults to using service discovery, as defined in RFC 6186.username stringβ (required) your IMAP username for authentication. gotta have it πpassword-cmd commandβ (required) the command that retrieves the account password. the command gets executed and its stdout (trimmed of whitespace/newlines) is used as the password. this is the whole point: it prevents storing passwords in plaintext config files. we love security π
common examples, since you'll ask:
password-cmd pass show email/examplepassword-cmd hiq -dF password proto=imaps host=imap.example.com
local-path pathβ (required) the local directory for Maildir storage. tilde and environment variables are automatically expanded, slay. each mailbox gets stored as a separate subdirectory using a flat structure β e.g.,~/mail/example/INBOX/,~/mail/example/Sent/.max-connections numberβ (optional, default: 3) maximum concurrent IMAP connections per account. minimum is 2 (that's1for the NOTIFY listener +1worker β the math checks out β¨).post-sync-cmd commandβ (optional) command to run after each successful mailbox sync. so useful for integrating with indexing tools likenotmuch(1) π§
the command is executed with the account's local-path as the working directory. use -v to print command output π
example: post-sync-cmd notmuch new
ignore regexβ ignore mailboxes matching regex. bye felicia πdisable-tlsβ disables TLS. use with extreme care, and never over a public network π this one is intended to be used with local proxies or similar setups. like, it's giving "I know what I'm doing" energy, so please actually know what you're doing π
π¦ SEE ALSO π¦
imapgoose(1)notmuch(1)hiq(1)pass(1)
the scfg(5) format specification lives here, go be educated bestie: https://git.sr.ht/~emersion/scfg/tree/master/item/scfg.5.scd
π AUTHORS π
Hugo Osvaldo Barrera <hugo@whynothugo.nl> β thank you for your service π«‘π
mwah π this page came from the Debian girlies and it's dated 2025-10-25 β that's the source, the version, and the date, all wrapped up with a bow π see you in the group chat, bestie π¦β¨
π¦ where this page comes from
- alpine 3.24: imapgoose-doc 0.5.5-r2 Β· ISC
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms