Note: Our documentation pages are a work in progress! If you can't find the answers you need, please email us to let us know. We'll be happy to answer your questions.
For shared domains (e.g. purelymail.com), Purelymail should work out of the box on modern mail apps, using default settings. Just enter your email address and your password, and make sure to use SSL or STARTTLS for security.
In case it doesn't or if you're using a custom domain, here you can find explicit configurations. Remember that if you are using Two Factor Authentication, you will need to use an App Password in place of your real password to connect to these protocols.
Incoming Mail / IMAP #
IMAP is a widely-supported protocol for viewing mail.
Our imap servers can be found at imap.purelymail.com with port 993. Make sure your app connects with SSL/TLS.
Outgoing Mail / SMTP #
SMTP takes care of delivering your messages. Use smtp.purelymail.com with port 465. This should be SSL/TLS.
If your client only supports STARTTLS, use port 587 with STARTTLS enabled.
Incoming Mail / POP3 #
Make sure you really need POP3 before using it! POP3 usually deletes messages from our servers after you download them. It can be found at: pop3.purelymail.com with port 995. Make sure your app connects with SSL/TLS.
If you'd like to configure filters via Sieve, a ManageSieve implementation is available at mailserver.purelymail.com with port 4190. Use STARTTLS.
Note that you can also configure Sieve filters in webmail.
I get an authentication failure! #
Remember that if you're using Two Factor Authentication, you need to use an App Password instead of your regular password. Also, make sure you're using your full email address as a username (email@example.com, not just foo).
I can't connect from my VPS or VPN! #
Some VPSes or VPNs may block the ports that you need to connect with. In general, you will need to look to your specific VPS or VPN for a solution.
Thunderbird failed to find the settings for my email account #
Assuming you've entered all the server settings correctly, this might be a weird Thunderbird bug. We're not sure how to solve it. This may be related?
In any event, we'd be happy to try to figure it out with you, or if you do figure it out, let us know.