Proton Mail & Calendar
- or
No existing idea results
- ~ No ideas found ~
1928 results found
-
newsletter view, option to disable for email domain/address
I regularly look in the newsletter view and have to choose under the dot-menu for the option to remove the message from the newsletter list.
But the next newsletter from that same domain will again end up in the newsletter view.A lot of the newsletters i see, i do not keep (delete) after i read it.
But i do want some/most newsletters to keep coming, so i do not want to Unsubscribe these letters.It would be nice to have an option in the menu (or as button) to acknowledge the newsletter in the newsletter view, but never see it in the newsletter view again, because i acknowledged it.
Others i can still unsubscribe and move to folder.
In fact a sort of blacklist/whitelist function, just to keep the newsletter view a little more clean.I regularly look in the newsletter view and have to choose under the dot-menu for the option to remove the message from the newsletter list.
But the next newsletter from that same domain will again end up in the newsletter view.A lot of the newsletters i see, i do not keep (delete) after i read it.
But i do want some/most newsletters to keep coming, so i do not want to Unsubscribe these letters.It would be nice to have an option in the menu (or as button) to acknowledge the newsletter in the newsletter view, but never see…
2 votes -
Buat yang nyari cara download Royal Dream APK versi terbaru, ini pengalaman aku. Versi terakhir sekarang v6 dengan ukuran sekitar 131,2 MB,
Buat yang nyari cara download Royal Dream APK versi terbaru, ini pengalaman aku. Versi terakhir sekarang v6 dengan ukuran sekitar 131,2 MB, ringan dan stabil di Android 5.0 ke atas. Aku selalu unduh langsung dari situs resminya biar file-nya aman dan nggak salah versi: https://royaldreamsapk.id/download.html
Langkahnya simpel: buka halaman download, klik "Download APK Android", aktifkan "izinkan instalasi dari sumber tidak dikenal" di pengaturan, lalu pasang seperti biasa. Royal Dream sendiri aplikasi game kartu & domino klasik untuk hiburan (Domino Gaple, Qiu Qiu, Rummy, sampai game arcade kasual). Buat iPhone juga ada versinya di App Store. Saran aku jangan download dari situs asal-asalan ya, mending dari sumber resmi biar aman.Buat yang nyari cara download Royal Dream APK versi terbaru, ini pengalaman aku. Versi terakhir sekarang v6 dengan ukuran sekitar 131,2 MB, ringan dan stabil di Android 5.0 ke atas. Aku selalu unduh langsung dari situs resminya biar file-nya aman dan nggak salah versi: https://royaldreamsapk.id/download.html
Langkahnya simpel: buka halaman download, klik "Download APK Android", aktifkan "izinkan instalasi dari sumber tidak dikenal" di pengaturan, lalu pasang seperti biasa. Royal Dream sendiri aplikasi game kartu & domino klasik untuk hiburan (Domino Gaple, Qiu Qiu, Rummy, sampai game arcade kasual). Buat iPhone juga ada versinya di App Store. Saran aku jangan download dari…2 votes -
Block email tracking via whitelist/blacklist to enable/disable per domain/email address
The option to block email tracking (settings -> All settings -> Email Privacy -> Block email tracking) sometimes screws up the layout of some emails.
These emails also get some layout from there own website and then this layout is blocked as if it is tracking info (and it might be).But if i disable this option, i disable it for all mails and not just for a few domains/addresses and that is not what i want. I want to keep for almost all emails the blocking active.
It would be nice if i read a mail that is screwed up, that there would be an option/button to blacklist or whitelist a domain or email-address for the Block Tracking option, just as i have a whitelist/blacklist for spam/Block/Authorised domains/addresses.
In this case i could determine if i trust the sender enough to unblock the email tracking for that sender/domain, but i keep it active for all others.
And with this option, i can read these screwed up emails much easier.
This would also show later messages as normal messages instead of screwed up messages.The option to block email tracking (settings -> All settings -> Email Privacy -> Block email tracking) sometimes screws up the layout of some emails.
These emails also get some layout from there own website and then this layout is blocked as if it is tracking info (and it might be).But if i disable this option, i disable it for all mails and not just for a few domains/addresses and that is not what i want. I want to keep for almost all emails the blocking active.
It would be nice if i read a mail that is screwed…
2 votes -
Having a button to archive an email while we are reading it without having to click on « Move to » or « … »
On iOS, when I read an email I most often want to archive it but I have to do it either through the « Move to » menu or through the « … » menu. It would be useful to have the archive button right there alongside the « Mark as unread », « Trash », « Move To », etc., buttons at the bottom of the screen when reading the email.
2 votes -
Conflict alerts
Calendar events may be tagged as "exclusive". The user can select in settings if new entries will default to exclusive or not.
Any time an exclusive event overlaps with another exclusive event, the user is given a warning about the conflict, so they can then decide how to resolve it.
If two exclusive events are booked close to each other and they both have addresses listed, an estimated travel time could be generated and a warning given if there isn't going to be enough time to travel from one location to the next.
This will be beneficial when importing events via ICS or Google calendar, using a shared family calendar alongside a shared work calendar etc.
Calendar events may be tagged as "exclusive". The user can select in settings if new entries will default to exclusive or not.
Any time an exclusive event overlaps with another exclusive event, the user is given a warning about the conflict, so they can then decide how to resolve it.
If two exclusive events are booked close to each other and they both have addresses listed, an estimated travel time could be generated and a warning given if there isn't going to be enough time to travel from one location to the next.
This will be beneficial when importing events…
2 votes -
Incorperate proton calendar with ubuntu top bar
Right now, there is no integration with ubuntu outside of the app. It would be extremely nice to not have to start the app every time I wish to check my calendar. An integration into ubuntu's top bar akin to the current calendar gui would be ideal. This would massively streamline my usage of proton calendar. Even a small extension in the top bar would be useful as well.
2 votes -
Send encrypted e-mails to non-Proton Mail users without password
Currently, Proton Mail users can send secure e-mails to non-Proton mail users user password protection. This feature adds complexity to the process. Can you provide an alternative method which doesn’t require a password but instead uses a 2FA method to verify the recipient’s e-mail address (similar to applictions such as Securemyemail),
2 votes -
Easy switch for registered emails from gmail to proton
Following the ability to connect my Proton Mail with my Gmail, I'd love suggestions in my inbox that offered me an easy way to change the email address associated with third parties.
For example, I have an account with Zalando. It would be awesome if, after an email from Zalando, there is an way for me to click-through to Zalando's account management screen where I can update my email. Providing this option for third parties who offer change of email addresses.
I'm not sure if this could be done in a way that doesn't intrude on privacy, but would be great if possible and really help me with migrating my life (not to be dramatic) over to Proton's ecosystem.
Following the ability to connect my Proton Mail with my Gmail, I'd love suggestions in my inbox that offered me an easy way to change the email address associated with third parties.
For example, I have an account with Zalando. It would be awesome if, after an email from Zalando, there is an way for me to click-through to Zalando's account management screen where I can update my email. Providing this option for third parties who offer change of email addresses.
I'm not sure if this could be done in a way that doesn't intrude on privacy, but would be…
2 votes -
Integration mit n8n für Proton Mail (Workflow-Automatisierung)
n8n (https://n8n.io) ist eine Open‑Source‑Workflow‑Automatisierungsplattform, die es erlaubt, verschiedenste Dienste miteinander zu verbinden. Eine offizielle Integration von Proton Mail, Proton Calendar und Proton Drive würde es ermöglichen, E‑Mails, Termine und Dateien in Workflows einzubinden, Anhänge automatisch in Drive zu speichern, Kalendereinträge aus E‑Mails zu erzeugen oder bestimmte Aktionen auszulösen. Dies würde die Produktivität steigern und Nutzern helfen, Proton‑Dienste flexibel in ihre bestehenden Arbeitsabläufe einzubinden.
15 votes -
Privacy-Preserving Notifications/Generic Notification Mode
Recently, reports involving Signal highlighted that operating system notification databases may retain sensitive information from message notifications, even after the original messages are deleted. While this example involved Signal and iOS, the same general risk may apply to other apps and operating systems where notification content is stored or indexed outside the app.
For privacy-focused users, Proton Mail and other Proton products should offer an option to use generic notification text instead of exposing message content in system notifications.
For example, instead of showing sender names, subject lines, or message previews, the notification could simply say:
“New Proton Mail message received”
This would reduce the chance that sensitive email metadata or content could later be recovered from operating system notification logs, backups, search indexes, forensic tools, or other third-party access.
Suggested feature: Generic Notification Mode
Proposed options:
Show full notification preview
Show sender only
Show generic notification only
Disable notifications entirelyThis would be a valuable privacy enhancement for Proton Mail, Proton Calendar, Proton Drive, Proton Pass, and other Proton apps where notifications may reveal sensitive content.
Recently, reports involving Signal highlighted that operating system notification databases may retain sensitive information from message notifications, even after the original messages are deleted. While this example involved Signal and iOS, the same general risk may apply to other apps and operating systems where notification content is stored or indexed outside the app.
For privacy-focused users, Proton Mail and other Proton products should offer an option to use generic notification text instead of exposing message content in system notifications.
For example, instead of showing sender names, subject lines, or message previews, the notification could simply say:
“New Proton Mail message…
3 votes -
Time-tracking Calendar Integration
One missing feature from the Proton Suite is a Time-tracking layer integrated in the Calendar app.
It would be a handy feature to toogle on/off alongside your planned schedule, in order to track the real time invested in your projects, get records and overviews, and be able to learn from them and improve your workflow. All with the same level of privacy and encryption of the other features.
Right now Proton users still depend on external apps to track their time, which don't integrate in the Proton ecosystem nor offer the same kind of data security. More on the contrary, multiplatform time-tracking sync apps are full of commercial trackers (pun very much intended) alongside security bugs.
Also, If the Calendar app is indeed planning to allow to run it locally and asynchronized as an option, the Time-tracking layer could work the same way for those who don't want/need online sync between devices.
I think there's a niche in the market for such (encrypted) feature, and it would be a point of attention for (small) businesses and independent entrepreneurs, while weighting on the idea of the Proton Suite above others.
One missing feature from the Proton Suite is a Time-tracking layer integrated in the Calendar app.
It would be a handy feature to toogle on/off alongside your planned schedule, in order to track the real time invested in your projects, get records and overviews, and be able to learn from them and improve your workflow. All with the same level of privacy and encryption of the other features.
Right now Proton users still depend on external apps to track their time, which don't integrate in the Proton ecosystem nor offer the same kind of data security. More on the contrary,…
3 votes -
Add multiple ways to sort emails.
I originally wanted to ask that we be able to sort our Inbox by tag/label. I did see that idea, but also saw requests to sort by star/no star and sender. So I wanted to combine these into a single improvement - to be able to sort the inbox by any column. Being able to do this, helps improve productivity. I would like to be able to see the emails I consider most important to follow up at the top, for example. It can also be valuable to see all the emails from a particular sender or under a specific label grouped together.
I originally wanted to ask that we be able to sort our Inbox by tag/label. I did see that idea, but also saw requests to sort by star/no star and sender. So I wanted to combine these into a single improvement - to be able to sort the inbox by any column. Being able to do this, helps improve productivity. I would like to be able to see the emails I consider most important to follow up at the top, for example. It can also be valuable to see all the emails from a particular sender or under a specific…
106 votes -
(Current) Critical Security Vulnerability: Missing Default-Deny Policy - Why Whitelists Fail Against Zero-Click Exploits (State Trojans)
(Current Text) April 26, 2026
Dear Proton Team,Currently, Proton Mail under (Filters) "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow"). The "Allow" function serves merely to move important emails back from the Spam folder to the Inbox; it does not prevent the receipt of emails from other domains. The "Block" function serves only to block known, malicious senders.
The fundamental security problem is that for users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model is fundamentally insufficient and dangerous. An attacker can register thousands of domains or use hacked servers to send malicious emails. A "Block" list can never cover all future, unknown attackers; as soon as a new, malicious domain is created, it is not on the list, and the email is accepted. Furthermore, as long as the Proton server accepts every connection from an unknown domain (even if it is later moved to Spam), there is a critical risk that a Zero-Click Exploit could be executed during the processing phase, such as rendering images, parsing metadata, or analyzing attachments. The malicious code does not even need the user to open it; it can compromise the email client or server infrastructure as soon as the data touches the server. Many users mistakenly believe that an "Allow" list automatically blocks everything else. Technically, this is not the case. The current list is merely a filter ensuring that certain emails do not land in Spam, not a firewall that cuts off access for everyone else.
I therefore demand the introduction of a separate, explicit setting "Allow Only Permitted Senders" that fulfills the following technical requirements. First, the whitelist must offer flexible granularity by supporting both individual email addresses and entire domains. This allows users to define permitted senders with two distinct levels of granularity to balance maximum security with practical usability. Individual email addresses are essential for high-security scenarios where only a specific person is trusted (e.g., john.doe@company.com); this prevents access even if other accounts within the same domain are compromised. Entire domains, on the other hand, serve for the efficient management of trusted organizations or partners (e.g., @trusted-partner.com) and allow all current and future senders from that domain without manual maintenance. The system must evaluate incoming mail against both lists, with a specific address rule taking precedence over a general domain rule if conflicts arise.
Second, server-side rejection at the TCP/SMTP level is required. The server must immediately reject the connection before any data transfer if the sender is not explicitly on the whitelist. This requires validation already during the SMTP handshake, ideally immediately after the EHLO/HELO command or at the latest before the MAIL FROM command. If the sender is not allowed, the server must immediately terminate the TCP connection or return an SMTP error code (e.g., 550 Access Denied or 554 Transaction Failed) before the actual email data transfer (DATA command) begins. No data packets containing potential exploits may be received; the server must not buffer or analyze the email content even temporarily if the sender is not on the list. The connection must be severed at the entrance so that no data packet containing a potential exploit is received by the server infrastructure.
Third, full user control must be guaranteed. Users must be given the opportunity to completely close their digital gate ("Air-Gap" principle for email) without relying on infinite and never-complete blocklists. The responsibility for maintaining the whitelist lies with the user; this is the principle of every high-security system.
Proton advertises worldwide with "maximum protection" and "end-to-end encryption." Yet, without a "Default-Deny" option that supports both address and domain whitelisting, the door remains physically open to unknown attackers. With this function, Proton would be the only commercial email provider enabling users to protect themselves against state surveillance and zero-day attacks through strict perimeter security. For journalists, whistleblowers, and activists, this is not an optional comfort feature, but a matter of survival. The ability to whitelist entire domains simplifies communication with teams, while the option to whitelist single addresses ensures precision against targeted attacks.
Please evaluate this request for technical feasibility and prioritize its integration into the roadmap for security updates. Proton should offer this choice to substantiate its position as the world's safest provider.
Thank you for your work on a safer internet.
(Current Text) April 26, 2026
Dear Proton Team,Currently, Proton Mail under (Filters) "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow"). The "Allow" function serves merely to move important emails back from the Spam folder to the Inbox; it does not prevent the receipt of emails from other domains. The "Block" function serves only to block known, malicious senders.
The fundamental security problem is that for users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model…
3 votes -
newsletter digest
Creating a daily or weekly digest message of newsletters. I can see the implementation being like an automatically generated email (opt in) that takes all the sender addresses and subject lines from every messages sorted into the newsletter view and delivered back into the inbox. This would condense messages quickly to make sure nothing important was missed and allow you to skip over everything else. This would be EXTRA useful if newsletters could be completely removed from the inbox view, or is a new -newsletter view was created. Really cut down on the clutter without the chance of missing something or something being misfiled
Creating a daily or weekly digest message of newsletters. I can see the implementation being like an automatically generated email (opt in) that takes all the sender addresses and subject lines from every messages sorted into the newsletter view and delivered back into the inbox. This would condense messages quickly to make sure nothing important was missed and allow you to skip over everything else. This would be EXTRA useful if newsletters could be completely removed from the inbox view, or is a new -newsletter view was created. Really cut down on the clutter without the chance of missing something…
2 votes -
Invert Newsletter View
I appreciate how the newsletter view concentrates the noise to one place but what would be way more helpful is a the view of all the messages that are not in the newsletter view. If either the messages in the newsletter view were excluded from the inbox or even just a new view that was the inbox sans -newsletter would be amazing. this would allow the important things wouldn't be buried in the newsletters.
2 votes -
Option to alphabetically sort labels
I would like the option to automatically sort labels alphabetically whenever I create a new label. This would make it easier to find a particular label in the side panel.
2 votes -
Critical Security Vulnerability: Missing Default-Deny Policy – Why Whitelist Fails Against Zero-Click Exploits (State Trojans)
Dear Proton Team,
Currently, Proton Mail under "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow").
The "Allowed" function serves merely to move important emails back from the Spam folder to the Inbox. It does not prevent the receipt of emails from other domains.
The "Blocked" function serves to block known, malicious senders.
The Fundamental Security Problem: For users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model is fundamentally insufficient and dangerous.
The Impossibility of a Complete Blocklist: An attacker can register thousands of domains or use hacked servers to send malicious emails. A "Blocked" list can never cover all future, unknown attackers. As soon as a new, malicious domain is created, it is not on the list, and the email is accepted.
The Risk of Server-Side Acceptance: As long as the Proton server accepts every connection from an unknown domain (even if it is later moved to Spam), there is a critical risk that a Zero-Click Exploit could be executed during the processing phase (rendering images, parsing metadata, analyzing attachments). The malicious code does not even need the user to open it; it can compromise the email client or server infrastructure as soon as the data touches the server.
Misunderstanding of the Current "Allowed" List: Many users mistakenly believe that an "Allowed" list automatically blocks everything else. This is technically not the case. The current list is only a filter ensuring that certain emails do not land in Spam. It is not a firewall that cuts off access for everyone else.
The Demand: A True "Strict Allow-Only Mode" (Default-Deny Policy) I demand the introduction of a separate, explicit setting "Allow Only Permitted Senders" that fulfills the following technical requirements:
Server-Side Rejection (TCP-Level Blockade): The server must immediately reject every connection from a domain/sender that is not explicitly on the whitelist (e.g., with 550 Access Denied) before the email data is even transmitted.
No Data Acceptance: The connection must be severed at the entrance. No data packets containing a potential exploit may be received.
Full User Control: Users must be given the opportunity to completely close their digital gate ("Air-Gap" principle for email) without relying on infinite and never-complete blocklists.
Why Proton Urgently Needs This: Proton advertises worldwide with "maximum protection" and "end-to-end encryption." Yet, without a "Default-Deny" option, the door remains physically open to unknown attackers.
Competitive Advantage: With this function, Proton would be the only commercial email provider enabling users to protect themselves against state surveillance and zero-day attacks through strict perimeter security.
Existential Necessity: For journalists, whistleblowers, and activists, this is not an optional comfort feature, but a matter of survival.
Next Steps: Please evaluate this request for technical feasibility and prioritize its integration into the roadmap for security updates. The responsibility for maintaining the whitelist lies with the user this is the principle of every high-security system. Proton should offer this choice to substantiate its position as the world's safest provider.
Thank you for your work on a safer internet.
Dear Proton Team,
Currently, Proton Mail under "Blocked and Allowed Senders Lists" offers only a whitelist as a positive exception in a system that standardly accepts everything ("Default-Allow").
The "Allowed" function serves merely to move important emails back from the Spam folder to the Inbox. It does not prevent the receipt of emails from other domains.
The "Blocked" function serves to block known, malicious senders.
The Fundamental Security Problem: For users who need to protect themselves against Zero-Click Exploits (e.g., advanced state trojans like Pegasus or similar spyware), this "Default-Allow" model is fundamentally insufficient and dangerous.
The Impossibility of a…
3 votes -
Support more than 4 Security Keys
Proton supports only 4 hardware security keys - this is not enough. Especially since using biometrics counts against the 4 key limit. I have three desktop computers which run my Proton accounts, and I have mobile devices which require 1 key. So I can't use the biometrics option without forcing a game of musical chairs with my security keys. I'm forced to continue using and subscribing to my 1Password account rather than Proton Pass until this limit is increased.
51 votes -
Saving calendar entry needs to be faster on iOS
Saving a calendar entry in iOS is very very slow, please make it faster.
5 votes -
Update Inactivity Policy
As a Proton user who infrequently logs into their Proton account
I want to ensure my account is not delete due to inactivity as per https://proton.me/support/inactive-accounts
So I want Proton to modify their inactive-acount rules to IF (account inactivity > 12 months AND space used > X*) THEN delete ELSE do nothing*where Proton decides an publishes what the amount of space used needs to be, e.g. > 1gb
2 votes
- Don't see your idea?