Mailbox.org discovers unencrypted password transmission in myMail
mailbox.org
mailbox.org
To be fair microsoft's outlook ios and android clients does the same thing with external providers (like if you used it with fastmail). It is a common practice and something to be aware of when choosing an email app.
EDIT: I'm specifically answering this comment. As for the submission, that was incredibly stupid for them to do in 2023. At this point it should only be opt-in to turn encryption off, not a default.
And yes I still lament the loss of the blinking red LED, a victim of phone makers today treating devices as if they were a piece of jewelry as opposed to the utilitarian tools they really are.
That seems much more secure than having a third party collecting my passwords so they can connect to my mail server from their network using my password just to see if any new mail is there, read the messages, then send a notification to my phone to let me know about them.
I'm perfectly happy to trust Thunderbird enough to configure it to check my mailbox, but I wouldn't feel as comfortable handing my login information directly to Mozilla so that they can log into my mailbox whenever they feel like it. I guess Mozilla could push an update that collects my stored login credentials and do that anyway, but if they did I think there would be a lot of folks who'd protest.
Desktop mail clients do. Phone mail clients can’t, so you either check on a server, or don’t get notifications on time.
I've never used a mobile client that used a third party to monitor a mailbox, they all do polling as you suggest. I'm not sure the man in the middle approach it's as common as OP is implying here (for non-first party clients).
This reminded me of Pointcast Networks. Ah, the 90s. :) https://en.wikipedia.org/wiki/PointCast https://www.youtube.com/watch?v=qCqwB6sruIQ
I'm sure the third party you share your email just to get push notifications with isn't monitoring your mailbox to the second either...
They can but consider this: How would they know to send them?
If you are adding a provider only locally there's no way for the app to know to generate a notification if it doesn't have an IMAP idle connection open constantly or scheduled polling. If the app is shipped by the email provider (like gmail app for ios using a gmail account) they can send pushes without leaving connection open or polling.
The point of having your details with the app developer is that their servers will remain always connected to your email provierr and generate pushes that will go over Apple or Google's push network.
I guess otherwise I'd rather it be my phone regularly polling my mail server over my connection than a third party regularly polling it using theirs. I can see it being a popular option for folks on expensive/very limited data plans though. It doesn't take a ton of bandwidth to poll a mail server, but checking every 5-10 minutes it could add up.
Does it occur to you that there are so many different variants of Android and they all do their own thing regarding background processes? It is so complicated that you can find websites like this https://dontkillmyapp.com/
In some countries this is "unauthorised access to computing systems".
But Google and co. are above the law anyway.
Mixed in were many logins from an IP address owned by the Microsoft campus at times when I would have been asleep. The account is a backup, and I don't have that mailbox attached to any apps. I emailed their security team asking what was going on but never got a response. After changing the password all the access was stopped. Though I should go back and re-check.
Admittedly, this is a pet peeve of mine, as I've co-authored a paper about it. I wonder why mailbox.org does not recommend that users switch from STARTTLS to implicit TLS for SMTP/POP3/IMAP, as this would mitigate such issues more generally. This is also in line with current RFCs (RFC 8314).
And the mess I had unavoidably made around the sockets and starttls just made that worse. And there was no real way to unit test it.
Another nice one is that implicit TLS is SNI routable (and thus much easier to route) -- this is the main reason for me, and I wish the standard had been updated to encourage more people to try 465 (or have a way to specify port in DNS records for example). Huge missed opportunity.
https://www.fastmail.help/hc/en-us/articles/360060591153-Man... under "Client email auto-discovery"
Though support for these are...
It does look like they are actually for clients (i.e. MUAs doing IMAP & Submission), not for relay (i.e. MTAs doing SMTP/SMTPS).
I've used MTA-STS and XML to enable auto-config for my stuff:
https://vadosware.io/post/thunderbird-autoconfig-for-your-se...
Oh and it looks like MTA-STS might be the solution:
https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#...
Turns out there's an excellent guide by the UK government:
https://www.ncsc.gov.uk/collection/email-security-and-anti-s...
https://www.security.gov.uk/guidance/email-guidance/mta-sts/...
Relevant RFC: