summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTristan Partin <tristan@partin.io>2023-05-25 02:36:15 +0000
committerRobin Jarry <robin@jarry.cc>2023-05-28 18:10:08 +0200
commitb90bc6a7581f020ed36d6c8b6389960d8428df3d (patch)
treeea9c16dbff3ed439911b165bae817b90f7246e26
parent998f052682d845795303b8d0cc0b05252af65928 (diff)
downloadaerc-b90bc6a7581f020ed36d6c8b6389960d8428df3d.tar.gz
aerc-b90bc6a7581f020ed36d6c8b6389960d8428df3d.zip
Update the Proton Mail docs
Based on information from the mailing list and my own experience, I can confirm that these example settings work. Signed-off-by: Tristan Partin <tristan@partin.io>
-rw-r--r--providers/protonmail.md33
1 files changed, 20 insertions, 13 deletions
diff --git a/providers/protonmail.md b/providers/protonmail.md
index cd32095a..c10a894a 100644
--- a/providers/protonmail.md
+++ b/providers/protonmail.md
@@ -4,30 +4,37 @@ title: "aerc-wiki: Providers/ProtonMail"
# ProtonMail
-Using ProtonMail with aerc is not trivial, as you will likely
-experience issues with the `protonmail-bridge` certificate, stored
-in `$HOME/.config/protonmail/bridge/`. The workaround is to add this
-certificate to the root trust database. Please note that this is tested
-on Arch Linux, and might not be valid on other distros. Run this command:
+Using ProtonMail with aerc is not trivial, as you will likely experience
+issues with the `protonmail-bridge` certificate. The workaround is to
+add this certificate to the root trust database. The certificate must be
+exported from the bridge.
+
+```text
+Settings -> Advanced settings -> Export TLS certificates
+```
+
+Once you have saved the certificate on the system, run the following
+command. Please note that this is tested on Arch Linux and Fedora, and
+might not be valid on other distros.
```bash
sudo trust anchor --store ~/.config/protonmail/bridge/cert.pem
```
-For outgoing mail to work, you might have to change the SMTP
-configuration in `protonmail-bridge` and set security to SSL instead of
-STARTTLS.
+The bridge's default configuration of STARTTLS instead of SSL should
+work with the following configuration
Example account configuration, using the default ports of
`protonmail-bridge`:
```ini
[Protonmail]
-source = imap+insecure://youraccount%40protonmail.com:yourprotonmailbridgepassword@127.0.0.1:1143
-outgoing = smtps+plain://youraccount%40protonmail.com:yourprotonmailbridgepassword@127.0.0.1:1025
-default = INBOX
-from = Your Name <youraccount@protonmail.com>
-copy-to = Sent
+source = imap://youraccount%40protonmail.com:yourprotonmailbridgepassword@127.0.0.1:1143
+outgoing = smtp://youraccount%40protonmail.com:yourprotonmailbridgepassword@127.0.0.1:1025
+default = INBOX
+from = Your Name <youraccount@protonmail.com>
+copy-to = Sent
+#smtp-starttls = yes # uncomment if using aerc <= 0.14
```
The first time you run aerc with this configuration you can expect a