Repository navigation
Troubleshooting
The domain is not listed in goodmail.conf. Add a domainN= block, a domain*=* catch-all, or set autodiscover=true. See Configuration.
goodmail could not open the IMAP connection. Check host and port (993 TLS or 143 STARTTLS), firewall, and for a private CA the caN= or insecureN=true settings.
A passkey is tied to the exact host name. Behind a proxy keep ProxyPreserveHost On or set GOODMAIL_ORIGIN; do not set GOODMAIL_ORIGIN when serving several hosts. A passkey made on goodmail.example.org does not work on goodmail.example.com. See Two-Step Sign-In.
Sessions survive restarts as long as secret.key (or GOODMAIL_SECRET) is unchanged, because the login cookie is sealed with it. If the key changed or was deleted, or the cookie expired (12 hours, or a year with "Keep me signed in"), everyone has to sign in again.
Needs smime=true and a real OpenSSL ≥ 1.1.1 with cms. macOS's built-in LibreSSL is not enough: brew install openssl and set GOODMAIL_OPENSSL=/opt/homebrew/bin/openssl.
Add sieveN= for the domain and make sure ManageSieve (port 4190, STARTTLS) is reachable from goodmail.
They appear only when admincmdN=, passwordcmdN= (and for Forgot password also resetfrom= and resetsmtp=) are set, and Administration only for people the helper command recognises as administrators.
That is the optional error page, shown while the goodmail process is down or restarting. See Deployment. If it stays, check systemctl status goodmail and the journal.
goodmail shows Loading… while the first page is fetched; very large folders such as "All Mail" can take a moment on slow servers. Opened messages and folder lists are cached, so the next visit is fast.
That is a mail-server matter (SPF, DKIM, DMARC and IP reputation of the sending server), not goodmail's. The raw header view (the </> button) shows the authentication results of received mail.
⚙ has Date format, Time format and Language ("Automatic" follows the browser).
goodmail
Using it
Security
Running it