There should not be any limitations for anyone using ProtonMail on who outside of the bounds of Proton Technologies can receive their email--and no please don't go the route of creating a separate app for this; instead tweak the web interface for the accommodation. An understandable configuration would be IMAP and POP3 being reserved for paid accounts.The current configuration is a way to rip people off. If ProtonMail is to succeed it must be user-friendly (at-least to the point where any ProtonMail user (including an unpaid user) can send emails to anyone (including those outside the Proton Technologies Network)). I personally tried to send an email to some people (for personal reasons) using a domain hosted by outlook but it bounced back and I suspect that SMTP not being available on the web interface along with my account being an unpaid one (I cannot use ProtonMail Bridge) is to blame but interestingly I can send email to Gmail. I did not like that. I appreciate the extensive security and the dedication of the Proton Technologies team but the problem I stated above I am sorry to say would turn the general public away from ProtonMail. Please Fix! PS: Unless if you guys are able to support POP3 I don't think you guys should reserve IMAP on its own without POP3 support for paid accounts and absolutely not all costs reserve SMTP for paid accounts whether SMTP be reserved for paid accounts on its own or with anything else for example with IMAP or POP3 or even all three of them together.

Please have someone do a true usability test on the beta version. If you are trying to frustrate and turn-off your users, it's going to do a good job. A couple of things I noticed immediately.

WHY is the Dashboard the first thing displayed??? This is NOT what people are coming to see. They want to go directly to their Inbox, not be up-selled with your latest products. And then when you do figure out you need to get to the Inbox - WHY is sitting in the upper-right hand corner of the screen? Literally, the last place that anyone will look. (I stumbled across it accidentally.) Seriously, have someone who has used the older version of Protonmail do a usability test on the new version. (NOT a developer or someone who already works at Protonmail...they are pre-biased to start with.) It can only help your product.

At the moment, ProtonMail's filters are, unfortunately, fairly weak compared to GMails — the transition is hitting me fairly hard.

As an example, a filter like this is almost impossibly laborious to represent in ProtonMail's manual system:

> from:(auto-confirm@amazon.com OR digital-no-reply@amazon.com) AND subject:("Amazon.com order of" OR "Your Amazon.com order")

Given that I can't have both an AND and an OR in a single filter, for the above simple example, I'd have to create four filters:

• from:<a rel="nofollow noreferrer" href="mailto:auto-confirm@amazon.com">auto-confirm@amazon.com</a> AND subject:&quot;Amazon.com order of&quot;


• from:<a rel="nofollow noreferrer" href="mailto:digital-no-reply@amazon.com">digital-no-reply@amazon.com</a> AND subject:&quot;Amazon.com order of&quot;


• from:<a rel="nofollow noreferrer" href="mailto:auto-confirm@amazon.com">auto-confirm@amazon.com</a> AND subject:&quot;Your Amazon.com order&quot;


• from:<a rel="nofollow noreferrer" href="mailto:digital-no-reply@amazon.com">digital-no-reply@amazon.com</a> AND subject:&quot;Your Amazon.com order&quot;

This manual permutation over the possibilities becomes a much bigger problem in my real-world filters with more than 2x2 nesting boolean operations — for instance, the above is an abbreviated version of an Amazon-receipts filter with three sender-addresses and eight subject-lines; that'd require 24 manual filters on ProtonMail! 😫