PSA: Email App Passwords (IMAP-SMTP) Now Available on Beta
Note: Mailbox might intentionally be rolling this feature out in stages for people already on the Beta program to give adequate time for testing, so no promises if you sign up for Beta after reading this that the feature will be available for new sign ups.
Also, a word of caution. I found switching to Beta janky, unintuitive, and not very streamlined. It works, but getting there was bumpy. It might be better now. I advise making sure you have all your passwords saved securely, and going slowly and deliberately through the process. I do applaud the team though for making progress on improving features for users. Follow this official guide: https://kb.mailbox.org/en/private/mailbox-org-beta/
------------------------------
"Dear Beta Testers,
Effective immediately, email app passwords (IMAP/SMTP) are available -
exclusively for you as a beta member.
Email app passwords serve as individual credentials for your email
applications. They safeguard your main password by granting only limited
access and can be individually revoked.
*Action Required: Set Up Email App Passwords with 2FA Enabled*
If you have activated two-factor authentication (2FA), you must use email
app passwords. Your main password will then be reserved solely for
logging into the website. This measure is in place to prevent external
email clients from bypassing 2FA.
Please note that using the main password will only be allowed during a
transitional period until March 10, 2025.
*Setup and Management of Email App Passwords*
You can create a unique app password for each application, add a note,
and manage IMAP and SMTP usage separately.
Access the new feature via: Settings > mailbox.org > Email App Passwords
*Important Notice Regarding the Beta Program*
As expected, beta-stage features may still contain bugs that we are
continuously addressing. For this reason, we advise against relying on
beta features for critical processes.
*Your Feedback Is Important to Us*
We are delighted to have you as part of our beta community. So far, we
have received invaluable feedback from many beta testers - thank you for
your active support!
Best regards
The mailbox.org team
PS: You are receiving this email as part of your participation in the
mailbox.org beta programme. Thank you for your participation!"
--
mailbox.org
c/o Heinlein Hosting GmbH
Schwedter Str. 8/9b, 10119 Berlin, Germany
This is great news! As a result of this, I joined the Beta program. I setup 3 devices and all of them worked.
I did have some issues with Apple IOS when updating the IMAP password. The error was, "Invalid Email address". I did some searching and found out that all of the aliases have to be deleted prior to IMAP accepting the new App Password. Once I did this, my IOS device worked. I had to go back and add my aliases.
This is great news! As a result of this, I joined the Beta program. I setup 3 devices and all of them worked.
I did have some issues with Apple IOS when updating the IMAP password. The error was, "Invalid Email address". I did some searching and found out that all of the aliases have to be deleted prior to IMAP accepting the new App Password. Once I did this, my IOS device worked. I had to go back and add my aliases.
Really great news! Hopefully non beta users will get this soon as well. Thanks for sharing this.
Really great news! Hopefully non beta users will get this soon as well. Thanks for sharing this.
It took some time for me to find out this is only IMAP/SMTP. I use EAS since this syncs my contacts and calendar to my devices without having to rely on *DAV and having push email. When enabling MFA, I can no longer use EAS. Will and can App Passwords also be made available for EAS? I don't feel like removing MFA is the right answer here.
It took some time for me to find out this is only IMAP/SMTP. I use EAS since this syncs my contacts and calendar to my devices without having to rely on *DAV and having push email. When enabling MFA, I can no longer use EAS. Will and can App Passwords also be made available for EAS? I don't feel like removing MFA is the right answer here.
I currently use Mailbox.org for almost all my mails. Is it going to be too risky to join the Beta in order to get the app passwords? Seems quite risky given that they don't guarantee uptime.
I currently use Mailbox.org for almost all my mails. Is it going to be too risky to join the Beta in order to get the app passwords? Seems quite risky given that they don't guarantee uptime.
I opened a support case last week because I was stuck between beta and non-beta due to the login 2.0 experience and the inability to create app passwords for Exchange ActiveSync. The issue is not that I got stuck, but that getting support is taking ages. Fortunately I have a workaround, but if I hadn't, I would've been without email access for a while by now which would have been a serious issue.
I opened a support case last week because I was stuck between beta and non-beta due to the login 2.0 experience and the inability to create app passwords for Exchange ActiveSync. The issue is not that I got stuck, but that getting support is taking ages. Fortunately I have a workaround, but if I hadn't, I would've been without email access for a while by now which would have been a serious issue.
Anybody else see "Error: You have no authorization to use this command" when visiting the IMAP/SMTP section? Is this the "being stuck between beta and non-beta" described by Jeroen above?
Anybody else see "Error: You have no authorization to use this command" when visiting the IMAP/SMTP section? Is this the "being stuck between beta and non-beta" described by Jeroen above?
Does the beta also work for Exchange ActiveSync connections? That is my preferred way of syncing on mobile. Does it require an app password?
Does the beta also work for Exchange ActiveSync connections? That is my preferred way of syncing on mobile. Does it require an app password?
Replies have been locked on this page!