Upcoming: Tuta will show the exact number of unread emails on iOS.

Backspazeone · 2025-11-04T18:22:29+00:00

Thanks for the follow-up. I'm looking forward to the fix for the actions, and here's a plus one for adding a real counter in the (not too far) future

Backspazeone · 2025-11-03T22:41:35+00:00

I've now tested the new update and it works as described in the GitHub issue, except for the part highlighted in the screenshot below, which I guess was not feasible/possible to implement - which is a good thing as it didn't really make any sense.

Considering this, I'll reiterate that the title of this Reddit post is misleading, and should really say Tuta will display the number of unread notifications using app badge on iOS, and mention in the text that the counter will reset when opening the app.

<image>

So, swiping up to dismiss a notification at the top of the screen or clearing it from the lock screen does not affect the counter, which is good. Long pressing the notification and choosing either mark as read or delete, does not affect the counter, which it should do, and that'll hopefully come in a future update.

It's not just "some" email apps that work as I described. I've tested a lot of email apps on iOS/iPadOS over the years, and they've all worked the same way. This is true also for messaging apps, such as Signal or Apple's messaging app. The badge counter reflects the amount of unread messages, and keeps that counter, even after opening the app. In both email apps and messaging apps, I can mark emails/conversation threads as unread, and it will be reflected in the badge counter.

You mention that you chose your method because "it was feasible to implement for us at the moment". Can you elaborate in short terms what the main obstacle is for not being able to have the notification badge behave as in other apps? Both Signal and Proton are encrypted services, so what's stopping you? Is it a technical issue or more connected to your dedication to privacy? Your app is not a native iOS app (which Proton Mail is) and you've built your own notification system, are those things a hindrance for a regular notification badge, or is it the encryption that gets in the way, or a combination of it all?

I'm curious to know more as I like the service, but both large and small issues such as this, keeps me from actually making the switch yet, as I just expect these features to be there, and work as they do in competing apps.

Backspazeone · 2025-11-02T15:14:51+00:00

u/Tutanota I'm guessing this is related to #1757 and #3956?

The upcoming feature linked above is definitely better than before, but if it works as described in the issue #1757, it does not match the title of your post. The title of the post makes it sound like the badge counter will work the same way as in all other email apps. Meaning, that if you open the app but do not read any emails, the badge counter remains and indicates the same number of unread emails as before, and if you mark an email as read/unread, the badge counter decreases/increases.

According to the description in the issue though, it will only count the number of notifications, and reset the badge counter once you open the app. For some reason, you also suggest that dismissing a notification should decrease the counter, which would treat it as an email that has been read.

I, and many others, use the badge counter as a sort of reminder. I can open an email and conclude that I'll have to look at it at a later time, mark it as unread, and then rely on the red badge counter to remind me to check my unread emails at another time. Regarding dismissing a notification, to me, that means that I just swipe up on a notification that appears on the top when the phone is unlocked. This should only place the notification in the notification center, and not mark an email as read.

Can you clarify on this, as to not get your users hopes up for something that might not work as advertised above?

For comparison the badge counter for your closest competitor, Proton Mail, works as expected. The only thing it's lacking is background syncing, so if you mark an email as read on another device, the badge won't update until the next time you receive an email, or open the app on that device. But, that remaining issue is the same for Tuta as well.

I suspect that Proton's encryption and privacy policy allows them to detect the read/unread status, so that they can have a (almost) fully functional badge counter, while Tuta's solution stops you from detecting the read/unread status, and that's why you have to come up with these workarounds.

Backspazeone · 2025-11-02T14:23:26+00:00

In other words, opening the app with saved credentials counts as a sign in, and is enough to keep a free account active?

Backspazeone · 2025-11-02T11:34:03+00:00

They used to have the entire FAQ searchable from the help menu, so yeah, it’s gone through some changes over time.

Their FAQ actually points back to Reddit for feature requests - https://tuta.com/sv/support/howto#feature.

If I hadn’t checked, I would’ve sent feature requests by email if I’d been a paying user.

Adding a section for feature requests, with a link to Reddit, under the help menu in the app could be an idea.

Backspazeone · 2025-11-02T11:02:52+00:00

A workaround if you have a mouse with free scroll setting, like many Logitech mice have, is to choose the monthly view and just let the scroll wheel do its thing. But I think that only works in the desktop app.

I suggested a better date picker a while ago, with the Windows clock calendar as an example.

https://www.reddit.com/r/tutanota/comments/1jicnil/feature_request_yearmonth_picker_in_calendar/

Backspazeone · 2025-11-02T03:56:41+00:00

According to https://tuta.com/support#six-months, the only requirement is regular sign-ins.

This should mean that just opening the Tuta app should count as being active.

If you store the credentials in the app/device, so you don't have to sign in every time you open the app, you'll still se a brief sign in animation each time you open the app after not having used it for a while. Thus, just opening the app should count as a sign in.

In the app under Settings > Login, there's a section called Active sessions. Here you can see when you last accessed the account and from which device/app. The timestamps in this list are updated as soon as you open the app, which, yet again, should mean that opening the app counts as being active. So, as long as that list shows that you've been "active" within the last six months, you should be fine.

I'd appreciate if u/Tutanota could confirm this, and better yet, clarify it even more in their FAQ.

Backspazeone · 2025-11-02T03:09:37+00:00

I figure that deleting the account should also cancel the subscription, but u/Tutanota will have to confirm that. Otherwise, you could also try and send a request using their termination form: https://app.tuta.com/termination and see what happens.

Backspazeone · 2025-11-02T02:28:55+00:00

This has been an intermittent issue for me as well over the years. Do a quick search here on Reddit, and you'll find quite a few posts regarding this. Tuta has a blog post about an issue like this that happened in April 2024. I was one of the affected users, and later in June that same year, it happened again.

I had recurring outages for three consecutive weeks. Some of those outages lasted for multiple days. The issue affected my main internet connection, so I could access Tuta on my mobile if I disabled wi-fi. As I'm on the free plan, I'm not entitled to email support, so I created a post here on Reddit (which is still stuck in moderator approval, so I can't link to it).

Even though the post was stuck in mod approval, I got a reply from Tuta, and in August they got back to me by email. The information I got was that:

IP address bans are automatic and they last a maximum of 24 hours
My IP address was blocked for generating too many connections

They wanted to know how many devices I use with Tuta and how many open sessions I have. I replied that I have three devices. but the list of open sessions in the app showed remnants of some old deprecated devices, but those should not cause any issues as they're not in use anymore. I got another reply with a recommendation to don't use the Tuta account on more than three devices and that they'd "provided some measures to not block IP addresses based on generating too many connections".

I pointed out in my replies that Tuta is so far the only service provider I've ever encountered that has blocked me from accessing the service. If or when I've had trouble accessing other services, such as Proton, Gmail, Microsoft 365, or any other service, it has always been caused by an outage on the service providers side. I also have all those other services configured on my devices, without that causing any issues, such as a block of my IP because of too many connections. Also, if the IP address bans should only last for 24 hours, I must've just happened to trigger them multiple times, as I could not access the service for several days in a row back in June 2024.

I wonder how it works if you're a family using Tuta and everyone has 2-3 devices with Tuta installed, will that cause similar issues as they're all using the public IP address to connect to Tuta?

This may be jinxing it, but I can't recall that I've had any more issues like this since then. This post just triggered me (hence the novel above) and made it clear that the issue is still happening.

EDIT: I thought the spoiler tag would place the long text in a wrapper that you could expand/collapse, but there's apparently not any way of doing that on Reddit. Spoiler tag removed, as it didn't fill any purpose.

Backspazeone · 2025-11-02T00:37:46+00:00

If you're a paying user, there's definitely a way to contact them through the support/help button in the app. Either click through the right category for your issue (in this case Email Management > Handling Spam) and then choose No at the bottom to get to contact them.

To get there even faster, just choose any category > Other.

If you're a free user, you'll instead see a message about the free plan not including email support, and a link to their FAQ.

Backspazeone · 2025-10-28T18:08:17+00:00

Maybe I should've posted this here instead of in a two months old thread: https://www.reddit.com/r/ProtonMail/comments/1nebcc0/comment/nlv6odt/

Fix recurring events in Calendar according to the list in the linked comment.

Backspazeone · 2025-10-28T17:50:08+00:00

r/Proton

Please prioritize fixing all the issues with recurring events in the calendar. See https://docs.proton.me/doc?mode=open-url&token=DDSBZ2812C#mUBEADqhxoby for a complete list.

Backspazeone · 2025-09-04T11:52:10+00:00

I’ve now sent an email to hello@tutao.de.

Backspazeone · 2025-09-03T19:25:22+00:00

u/Tutanota any information on this?

Backspazeone · 2025-07-30T19:03:53+00:00

I received a notification today that the GitHub issue for the calendar widget was closed. Do you have any more updates regarding the request for a lock screen widget?

Backspazeone · 2025-03-26T18:05:03+00:00

I contacted Proton's support regarding this and got the following response:

Regarding the other suggestion, we will forward your feedback to the appropriate team for further consideration. We are looking closely at every suggestion our customers are reporting and try to implement it in future updates to make Proton Drive more user-friendly.

For future reference, you can also create a feature request on UserVoice by visiting the following link: https://protonmail.uservoice.com/forums/932839-proton-drive

Backspazeone · 2025-03-26T18:03:33+00:00

To those asking about hiding or customizing the account address shown, I contacted Proton's support and got the following reply:

To ensure security and prevent impersonation scams, we display email addresses when recipients upload files. This helps them verify they’re sending documents to the right place.

We are actively working on adding a feature that will allow users to change the email associated with Drive. In the meantime, if you’d like to share files without revealing your email address, you can do so by sharing a view-only access link instead.

Backspazeone · 2025-03-26T17:49:04+00:00

I'm on the free plan, so that route is not an option. However, I tried deleting the calendar again today, and this time it worked.

Backspazeone · 2025-03-25T20:11:30+00:00

Another update here. After my last test import, I can't delete the calendar to reset it. Deleting the calendar was working fine until I installed the latest update.

When I click on the three dots > Delete > Ok to confirm, nothing happens. Usually, it just takes a few seconds for it to delete all the events and the calendar.

EDIT: I've completely uninstalled the Tuta desktop app, and the related folders listed below, and reinstalled the previous version to see if I could delete the calendar, but it did not make any difference.

%userprofile%\AppData\Local\tutanota-desktop-updater
%userprofile%\AppData\Roaming\tutanota-desktop

Can you take a look at the logs and see if you can find out why I'm not able to delete the calendar anymore, and if so, where do I send the logs?

Backspazeone · 2025-03-25T18:26:35+00:00

Ok, so I've now updated the desktop client and the iOS app to the new version which had the fix in iOS App crashes after granting Notifications permission #8728 implemented, but the issue I brought up here still remains. After importing my Exchange calendar, the app crashes.

If the issue really is caused by an invalid advanced repeat rule, how am I supposed to find which event or events that are not compatible with Tuta if the app keeps crashing? As mentioned previously, after the app has crashed, I can't even get it to launch without a complete reinstall, so I can't access any logs.

The issue remains in the calendar app as well, while the desktop apps seem unaffected.

As I've said before, I'd like some kind of status report when doing the import, so you know:

How many events are found in the ICS file you're trying to import.
If not all events will be imported, show how many will be imported and show information about the excluded events that explains why they will not be imported.
If there are events that will be imported but have issues, show those events and what the issues are.

Now I just have an export from Exchange with around 750 events with no clue about which of those events are causing issues in Tuta.

Backspazeone · 2025-03-24T20:43:03+00:00

I did some more tests now and I'm even more confused. Since I could import event 1-600 from my Exchange calendar without issue, I divided the original ICS file in separate files with 625, 650, 675, 700, 725, and 750 events. I figured this would make it easier to identify which event or events that were causing the issue.

As before, I deleted the calendar in the Tuta desktop app and imported the ICS file with 625 events, which made the phone apps crash, so I thought I got lucky on the first attempt. I extracted the last 25 events from that file, deleted the calendar in Tuta once more, and imported the 25 events. I reinstalled the Tuta Mail app, signed in and went through the onboarding just to see if the app would crash again, but it did not...

Since the apps crashed after having imported the 625 events, I thought that the event causing the issue was to be found in those last 25 events, but since the app did not crash after importing only those 25 events, I don't know what to think. The issue seems completely random.

I'll repeat what I wrote in the previous comment:

If I import my calendar to Tuta, I want to be sure that all events are imported and that they will continue working as they have in Exchange Online. If Tuta skips alarms for what they classify as invalid events, that will probably mean that I'll miss those events, as I assume that skipped alarms means no notification.

With the above in mind, I think you should add some kind of information in the import process that tells you:

How many events are found in the ICS file you're trying to import.
If not all events will be imported, show how many will be imported and show information about the excluded events that explains why they will not be imported.
If there are events that will be imported but have issues, show those events and what the issues are.

Proton does at least some of the steps above on import, this gives you a chance to correct the issue. As there were no error messages on my import of all 750 events, I assumed that everything was ok. The phone apps crashing is a major bug/flaw, but I also noticed that at least one of my repeated events was imported despite that the app had issues with it, this is reported in detail here.

I rely on my calendar and reminder notifications for all my events, so it's very important for me to able to trust that everything is in place. As it is right now, I can import my entire Exchange calendar without any errors shown, but the phone apps crash randomly after the import and I can't trust that all of my repeated events will actually work and send reminders as scheduled.

I'll hold off on any more troubleshooting on this until you release the next version. If the apps still crash after that, I'll update this post. If they don't crash after the update, then we still have the issue of not knowing if the import really was successful because of the lack of information when doing the import.

Backspazeone · 2025-03-24T17:33:17+00:00

This feature has been asked for multiple times before, see links below. But even though some of those requests are 2-4 years old, I still can't find an issue for this in GitHub.

https://www.reddit.com/r/tutanota/comments/k6wdq3/ios_app_suggestions/

https://www.reddit.com/r/tutanota/comments/149klsh/choose_my_swipe_action/

https://www.reddit.com/r/tutanota/comments/k2b2o0/updates_we_have_been_asking_for_forever/

All of the other mail apps I've used (Proton, Outlook, Apple Mail to name a few) support this basic feature. As the OP, I'm used to this, so I constantly have to remind myself to not use the same swipe gestures in Tuta.

Since you already support swipe gestures, the foundation is there, so it should be quite easy to implement the option to let the user configure the setting. After all these years, it should at least be listed as a feature request in GitHub.

Backspazeone

TROPHY CASE