1879 results found

1. 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,… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. (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… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Overnight events

   While traveling, it is important to know at what accommodation you sleep at night. These are events that span two days (or if staying a longer time, multiple nights). Is there a way to mark these kinds of events in the calendar? Especially useful if it can be clearly visible from the calendar overview that there is a lack of such a night-spanning event (i.e. one night one has not yet planned a place to stay).

   Currently, on the Android app, we see by the number of dots below a date how many events are there.

   To indicate the presence of an overnight event, one could put a small arrow or marker on these dots, so to know that it is a night-covering event. Then when a night is missing, it is immediately clear from the overview.

   Especially when traveling for business to many places, while the plan changes dynamically, having such a feature helps the user to reassure themselves that they got every night figured out.

   While traveling, it is important to know at what accommodation you sleep at night. These are events that span two days (or if staying a longer time, multiple nights). Is there a way to mark these kinds of events in the calendar? Especially useful if it can be clearly visible from the calendar overview that there is a lack of such a night-spanning event (i.e. one night one has not yet planned a place to stay).

   Currently, on the Android app, we see by the number of dots below a date how many events are there.

   To indicate the presence… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. 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.

   1. 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.

   2. 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.

   3. 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.

   1. The Impossibility of a… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. UX costumization in Calendar

   It would be great to be able to costumize the way we want to calendar app on Android.
   I'm thinkin of :
   - In monthly view, have a parameter that allows us to display the title of event on 2 or 3 lines, to be able to read it (Or to change the size of the title)
   - In weekly view, same thing : for a full day event only 2 letters of the event are displayed...
   - In weekly view : To have an option display the adress of the event : we have to check the event to find it.
   - In weekly/monthly view : To be able to change the color if the event is on several days (like a pastel-ish tone to the color of the event).

   I went from Samsung to Proton, the features on their calendars were much more efficient and nice to use, it's kind of difficult to adjust.

   It would be great to be able to costumize the way we want to calendar app on Android.
   I'm thinkin of :
   - In monthly view, have a parameter that allows us to display the title of event on 2 or 3 lines, to be able to read it (Or to change the size of the title)
   - In weekly view, same thing : for a full day event only 2 letters of the event are displayed...
   - In weekly view : To have an option display the adress of the event : we have to check the event to… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. “Read Receipt” as DEFAULT for Mac app users? Thanks.

   It would be very helpful, IMHO, to have a default setting option to request read receipts for outgoing messages. Thank you!

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. For Huawei devices

   Hi, I like the app and it would be nice if it is also available natively for Huawei devices in its app store, appgallery, for a better experience

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Show time zone names (or custom labels) in the calendar view, not just GMT offsets

   When two time zones are enabled, both columns are only labeled with their GMT offset. Example: Europe/Vienna and Africa/Johannesburg both display as "GMT+2" during European summer time — completely indistinguishable. In winter the offset differs by one hour, but "GMT+1 / GMT+2" still doesn't tell you which column belongs to which zone.

   Please show one of the following next to (or instead of) the offset:

   The IANA city name (e.g. Vienna, Johannesburg), or
   A user-defined label per zone, or
   The standard abbreviation (CET/CEST, SAST).

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Group Alias or Shared Account

   Current Limitation: Currently, Proton Mail does not allow a single custom email address (alias) to be assigned to multiple user accounts within a Family or Duo plan. When an administrator creates an alias (e.g., info@myfamily.com or support@mybusiness.com), it can only be assigned to one specific user.

   This forces users into inefficient workarounds:

   Manual Forwarding: One person owns the alias and must set up filters to forward mail to others. This breaks the "shared inbox" experience, as replies come from the individual's address, not the group address, and there is no central view of the conversation history.
   No Collaboration: Multiple team members cannot log in to the same mailbox to manage tickets, customer inquiries, or family correspondence simultaneously.
   The Request: I am requesting the addition of a Native Group Alias or Shared Inbox feature for Proton Family and Proton for Business plans.

   Desired Functionality:

   Multi-User Assignment: Allow an administrator to create an alias (e.g., team@domain.com) and assign it to multiple user accounts simultaneously.
   Shared Inbox View: When any assigned user logs in, they should see emails sent to this alias in a dedicated folder or shared view, alongside their personal mail.
   Unified Sending: Allow any assigned user to "Send As" the group alias, ensuring replies come from the group address (e.g., team@domain.com) rather than the individual's personal address.
   Conversation Sync: Ensure that if User A replies to a thread, User B sees that reply in the shared view, maintaining a single conversation history.
   Why This Matters: This is a critical feature for:

   Small Businesses: Teams need to manage support@, sales@, or info@ addresses without relying on a single "owner" account.
   Families: Families managing a shared household email (e.g., vacation@, school@) need all members to see and respond to messages without forwarding chains.
   Competitiveness: Competitors like Google Workspace and Microsoft 365 offer "Shared Mailboxes" and "Distribution Groups" as standard features. The lack of this capability is a significant barrier for small businesses considering migrating to Proton.
   Conclusion: While the current workaround of manual forwarding exists, it is clunky and lacks the collaborative features necessary for professional or shared household use. Adding native support for group aliases would significantly enhance Proton's utility for teams and families.

   Thank you for considering this request.

   Current Limitation: Currently, Proton Mail does not allow a single custom email address (alias) to be assigned to multiple user accounts within a Family or Duo plan. When an administrator creates an alias (e.g., info@myfamily.com or support@mybusiness.com), it can only be assigned to one specific user.

   This forces users into inefficient workarounds:

   Manual Forwarding: One person owns the alias and must set up filters to forward mail to others. This breaks the "shared inbox" experience, as replies come from the individual's address, not the group address, and there is no central view of the conversation history.
   No Collaboration: Multiple… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Set message expiry in the mobile

    Allow users to set messages to expire directly on the mobile app. It is currently only supported through the web interface.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Calender events prior to 1970

    It is currently only possible to enter calendar events prior to or going back no further than 1970. This makes it difficult to enter birthdates when you wish to track the actual age of the person as well as historical events.

    Implement option to enter dates prior to 1970 in Proton Calendar.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Birthday Entry is Very Difficult

    Presently, entering a birthday requires that I use the calendar pop-up to choose the birthday and it must require a year. My friends ar 70 years old. Scrolling the calendar back on moth at a time for something like 840 months is torture. Can you make it I can just type in the birthdate so I can get on with my life?

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Show matching filters when viewing an email

    When viewing an email that has had a sieve/filter applied it would be helpful to show & link to that filter. This would make it considerably easier to update a filter that is not behaving as expected.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Search function in Newsletters

    I use the Newsletters feature and have over 300 active newsletters that are listed. When looking to make a change it would be helpful to have a search function to easily find a particular newsletter.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Allow sending password-protected emails from alias

    Allow sending password-protected emails from alias. For now you cannot send password protected email from alias (Proton Pass or Simple Login) without revealing your email. This was described by me in 3757785 ticket.

    Allow to hide real email from recipient if sending password protected email through reverce alias

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Please enable file count for folders in Drive

    I would like to see the number of files in a given Drive folder.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Repeat calendar entry by selecting days

    Please add the possibility to repeat calendar entries by selecting certain dates in the monthly view, for instance, when creating the entry.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Mute a conversation/thread

    Like in other email providers, it should be possible to "mute" a thread.
    By doing so, other emails coming in the thread would not trigger a notification, nor put back the archived thread in the inbox.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Passwords for Password-protected emails selected by recipient

    Currently when sending Password-protected emails to non-proton recipients the sender has to select the password, notify the recipient of the password, and manually record the password for future correspondence. It is tedious and has two major issues.
    1. The first issue is if you want to send the message to multiple people they must both have the same password.
    2. If a recipient receives password-protected emails from more than one protonmail senders, they would need to track and keep a log of passwords for each and every sender.
    A solution would be to have the recipient select a password to decrypt the email link and store the password on a server in the same manner that passwords are handled for any other email (proton to proton, etc).
    Because the process of sending password-protect emails is tedious, it is rarely used (by me at least) and any email sent or cc'd to a recipient is on the gmail, yahoo, hotmail, etc. servers in plain text where companies like google can glean the content. Furthermore in the US, Section 702 of the FISA act allows the government to gather texts and emails from overseas without a warrant. Protonmail originates from overseas (Switzerland).
    An easy way to send and receive secure email from protonmail to non-proton recipients would go a long way to making protonmail secure.

    Currently when sending Password-protected emails to non-proton recipients the sender has to select the password, notify the recipient of the password, and manually record the password for future correspondence. It is tedious and has two major issues.
    1. The first issue is if you want to send the message to multiple people they must both have the same password.
    2. If a recipient receives password-protected emails from more than one protonmail senders, they would need to track and keep a log of passwords for each and every sender.
    A solution would be to have the recipient select a password to… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. search bar - ios search

    It would be great if the search icon/bar could be implemented at the bottom next to the write button and not at the top right corner, such as in the iOS system like in Mail, Settings, etc.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating