A desktop mail app rejects a password that still works on the Proton website. Before resetting the account, identify the connection you are configuring. If that app connects through Proton Mail Bridge, the password expected by the mail app is not the same credential you use to sign in to your Proton Account.
This guide is for an existing Bridge setup. It is not a recommendation to buy a plan, install software or change an account’s security settings. The immediate task is to identify the mailbox, application and password prompt without sharing any secret with another person.
Keep the two sign-in steps separate
Proton’s official password-error guidance says mail clients using Bridge need the password generated by Bridge. Check that Bridge is running and signed in, select the correct mailbox and use the current credential in its Mailbox details. If the client stores incoming and outgoing passwords separately, Proton says both need the appropriate Bridge credential. A mailbox removed and added again may require updating the client with the current details.
Those checks address a particular connection path. A failure to sign in to the Proton website itself is a different problem. Do not assume that a message containing the word “password” always asks for the account’s main password.
An example with two mailboxes
Imagine a computer configured for a personal mailbox and a small volunteer group’s mailbox. The personal address works in the desktop app. The group address repeatedly prompts for a password. A helper might be tempted to copy whatever was used for the working account, but that skips the most important comparison: which mailbox the prompt names.
Write down a masked address label for each, such as “personal mailbox” and “group mailbox.” Compare the address shown in the failing prompt with the mailbox selected in Bridge. You do not need to write either password in the worksheet. The point is to match the identities, not to build a document full of credentials.
A short check before another login attempt
- Name the application. State whether the prompt appears in Bridge, Thunderbird, Outlook, Apple Mail or a browser. Include the version if you can find it easily.
- Name the mailbox. Confirm the intended account without sending a full private address to a public discussion.
- Identify the prompt. Record the exact non-sensitive error wording and whether it appears while receiving, sending or both.
- Compare the current setup. Review the mailbox details locally using the provider’s instructions. Do not copy a credential from another mailbox because it happens to work.
- Record the result. Note whether the next attempt changed the error, succeeded or failed at the same stage. Avoid several unrelated changes between tests.
Receiving and sending deserve separate notes
A report that says “mail does not work” can hide an important distinction. Perhaps new messages arrive, but an outgoing test remains unsent. Or perhaps the app cannot authenticate before either operation begins. Describe those outcomes separately.
Use one harmless test only if you choose to test delivery, and use an address you control. Before retrying an outgoing message, check its current state so you do not accidentally send several copies. An unsuccessful test does not justify turning off encryption or copying server settings from another provider.
Help without exposing the password
A useful support note might say: “The group mailbox works in the browser. The desktop app prompts during sending. Bridge is open, and I checked that the selected mailbox matches the prompt.” Add the app version and error text, but leave passwords, recovery codes and private message contents out.
If someone asks you to paste a credential into chat or show it in a screen recording, pause. You can carry out the local comparison yourself while a helper explains the documented steps. Also hide credentials before taking a screenshot of a settings window; a configuration page can reveal more than the error you intended to capture.
Choose the next support route from the failing stage
If the problem persists after the documented local checks, preserve your observations and consult Proton’s current Bridge support. Account recovery belongs with Proton. Rebuilding the entire mail profile without preserving local-only information is a much larger step than identifying a mismatched credential.
The independent EmailSupport Proton Mail guide provides general triage and points readers toward official resources. EmailSupport is operated by Scott Jeppesen and is not affiliated with or endorsed by Proton or other email providers. A clear description of the failing stage supports a better next step; it does not guarantee a repair or account-recovery outcome.
Comments (0)
Want to join the discussion?
Log In to Comment