Troubleshooting

The server cannot be reached

• Check host and port (usually 4190). Discover finds them if your domain publishes a _sieve._tcp record.
• The server must offer STARTTLS with a valid certificate. Sievesmith does not accept self-signed or expired certificates; there is no way to override this.
• Some networks block port 4190. Try another network.

Sign-in fails

• Many providers need an app-specific password instead of your normal one.
• Test Connection lists the sign-in methods the server offers. Sievesmith supports SCRAM-SHA-256, SCRAM-SHA-1, PLAIN, LOGIN, OAUTHBEARER and XOAUTH2 and chooses the strongest one offered.

The protocol log

Settings › Data › Protocol Log records the conversation with your servers on this device when you turn it on. Passwords, tokens and sign-in data are never recorded. Export it and attach it when you contact support; turn it off again afterwards.

Server notes

• Dovecot (Pigeonhole): the ManageSieve service must be enabled by the server’s administrator.
• Cyrus IMAP and Stalwart: ManageSieve usually listens on port 4190; Stalwart’s own Sieve extensions are recognized.