Based on information from the mailing list and my own experience, I can
confirm that these example settings work.
---
 providers/protonmail.md | 34 ++++++++++++++++++++--------------
 1 file changed, 20 insertions(+), 14 deletions(-)

diff --git a/providers/protonmail.md b/providers/protonmail.md
index cd32095..9cf66bb 100644
--- a/providers/protonmail.md
+++ b/providers/protonmail.md
@@ -5,29 +5,35 @@ 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:
+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`:
+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 # if using aerc <= 0.14
 ```
 
 The first time you run aerc with this configuration you can expect a
-- 
2.40.1

aerc/patches: FAILED in 1m39s

[Update the Proton Mail docs][0] from [Tristan Partin][1]

[0]: https://lists.sr.ht/~rjarry/aerc-devel/patches/41385
[1]: tristan@partin.io

✗ #995512 FAILED aerc/patches/alpine-edge.yml https://builds.sr.ht/~rjarry/job/995512
✗ #995513 FAILED aerc/patches/openbsd.yml     https://builds.sr.ht/~rjarry/job/995513

Build failure seems unrelated.

-- 
Tristan Partin
https://tristan.partin.io

Tristan Partin, May 25, 2023 at 04:41:
> Build failure seems unrelated.

This is because you sent a patch against the wiki branch but prefixed
your patch with "aerc". This makes the CI to trigger a build which tries
to apply the patch against the wrong branch.

I need to update the contributing guide to explain how to send patches
for the wiki.

TL;DR, for patches against the wiki branch:

    git send-email -1 --subject-prefix="PATCH aerc/wiki"

Tristan Partin, May 25, 2023 at 04:36:
> Based on information from the mailing list and my own experience, I can
> confirm that these example settings work.

Applied. Thanks!