[CLOSED][APP][5.0+] FairEmail - Fully featured, open source, privacy oriented email app

[geodemarse]

Hello M66B,

I'm a FairEmail Pro user since 2019, downloaded from F-Droid.
I have been reading this thread carefully since last week. Everything has been said and well said, I just bring here for support Marcel.

I'm not a developer and I don't know if this is relevant here : I'm in France and I use the mail service of my operator @free.fr
I have 3 @free.fr emails configured on FairEmail.
At the end of April, beginning of May, I couldn't send any more mail, an error message telling me "The mail server said : 550 5.7.1 Spam Detected - Mail Rejected. Please see our policy at : http://postmaster.free.fr/#spam_detected." No fault with Thunderbird on my computer.
I followed the procedure to indicate a false positive.
Is there a causal link ? Since this week, it works Due to the latest FairEmail updates ?

In any case, take care of yourself and your loved ones.

N.B.: Marcel, you are incorrigible, no more 3 updates of the application since last week

 

[M66B]

Hello M66B,

I'm a FairEmail Pro user since 2019, downloaded from F-Droid.
I have been reading this thread carefully since last week. Everything has been said and well said, I just bring here for support Marcel.

I'm not a developer and I don't know if this is relevant here : I'm in France and I use the mail service of my operator @free.fr
I have 3 @free.fr emails configured on FairEmail.
At the end of April, beginning of May, I couldn't send any more mail, an error message telling me "The mail server said : 550 5.7.1 Spam Detected - Mail Rejected. Please see our policy at : http://postmaster.free.fr/#spam_detected." No fault with Thunderbird on my computer.
I followed the procedure to indicate a false positive.
Is there a causal link ? Since this week, it works Due to the latest FairEmail updates ?

In any case, take care of yourself and your loved ones.

N.B.: Marcel, you are incorrigible, no more 3 updates of the application since last week

An update can't explain why outbound messages aren't considered as spam anymore.
A common cause for this kind of problems is a network address the email server doesn't like.
So, using a different (mobile) network or a VPN can result in this problem too.

The latest GitHub update was May 18, almost a week ago.

 

[AG3S]

I don't mean this in a bad way, if money was the sole motivating factor, I might not even have started the project at all, but it sounds hypocritical that you hate subscriptions, you go even as far to say that you would leave the app behind for it, and that you on the other hand are depending on the app. Don't you want support if something doesn't work? Don't you want the app to be updated for new Android versions, which your next device might run? In other words, don't you want the app at least to be maintained and supported, and the room for improvement to be used?

Again, I don't mean this in a bad way. It just seems to me that you are mad because of bad behavior of others. That doesn't mean that everybody will behave in the same way.

This is exactly what I wanted to say... and is really sad to see...


Why not to pay a small fee a year for a software which we use on a daily basis!!!!!

Some people would like to see the project die than paying a ridiculous fee monthly!

However, I am sure many others here would love to contribute to this project.

 

[Tomoms]

Hello @M66B
I'd like to build FairEmail from source and have Gmail OAuth working. I currently build the Github variant via Gradle and sign it with my own Java Keystore. However, in order for Gmail OAuth to work, I've noticed that I have to update the fingerprint and the public key in app/src/main/res/values/strings.xml, and I am unsure how exactly to do it.
How do I get the fingerprint and the public key associated with my Java Keystore? It might be a stupid question, but it's the first time I deal with signing an Android APK and I'm a bit confused.
Thank you in advance!
EDIT: I guess the fingerprint can be read from the associated .x509.pem private key file (?)

 

[M66B]

Hello @M66B
I'd like to build FairEmail from source and have Gmail OAuth working. I currently build the Github variant via Gradle and sign it with my own Java Keystore. However, in order for Gmail OAuth to work, I've noticed that I have to update the fingerprint and the public key in app/src/main/res/values/strings.xml, and I am unsure how exactly to do it.
How do I get the fingerprint and the public key associated with my Java Keystore? It might be a stupid question, but it's the first time I deal with signing an Android APK and I'm a bit confused.
Thank you in advance!

You'll need to go through the Google audit process for this. This won't be easy.

Edit: if you want to do the same for Yahoo (Verizon), you'll need to sign a contract even.

 

[Tomoms]

You'll need to go through the Google audit process for this. This won't be easy.

Oh. I thought you just performed a local test to avoid breaking some Google regulation, and not that it actually required an active intervention by Google... Pity.

 

[M66B]

Oh. I thought you just performed a local test to avoid breaking some Google regulation, and not that it actually required an active intervention by Google... Pity.

Some background info:

Google's stunning plan to avoid apps slurping Gmail inboxes: Charge devs for security audits

Requirement threatens to break the bank

www.theregister.com

Solution: use an app password.

Edit: the alternative solution is to create an OAuth app in the Google developer console and to configure this in providers.xml. This will work without approval for a handful of users.

 

[Tomoms]

Solution: use an app password.

Thanks, it works!

 

[deechte]

How was the call with Google today, Marcel?

 

[chris122380]

How was the call with Google today, Marcel?

I think we are all waiting for the results from that.

 

[M66B]

How was the call with Google today, Marcel?

Google was pretty friendly and cooperative and told me the favicons are indeed the problem, and it can/should be fixed by updating in the privacy policy to "disclose how your app accesses, collects, uses, and shares user data":

Privacy Policy​

All apps must post a privacy policy in both the designated field in Play Console and within the app itself. The privacy policy must, together with any in-app disclosures, comprehensively disclose how your app accesses, collects, uses, and shares user data, not limited by the data disclosed in the Data Safety section. This must include:

• developer information and a privacy point of contact or a mechanism to submit inquiries
• disclosing the types of personal and sensitive user data your app accesses, collects, uses, and shares; and any parties with which any personal or sensitive user data is shared
• secure data handling procedures for personal and sensitive user data
• the developer’s data retention and deletion policy
• clear labeling as a privacy policy (e.g., listed as “privacy policy” in title)

The entity (e.g., developer, company) named in the app’s Google Play listing must appear in the privacy policy or the app must be named in the privacy policy. Apps that do not access any personal and sensitive user data must still submit a privacy policy.

Please make sure your privacy policy is available on an active URL (no PDFs) and is non-editable.

So, I have updated the privacy policy and added this new table:

https://github.com/M66B/FairEmail/blob/master/PRIVACY.md#summary-of-shared-data

I am not sure if it covers everything, so feedback is more than welcome. @mkasimd maybe you can take a look?

Note that I have also enabled BIMI, Gravatars, Libravatars and favicons for the Play store version again.

The short term goal is to release a Play store test version (and associated GitHub version) and to get the update approved. I will think about the next steps after this has been accomplished. Given the huge number of supportive messages I received (much appreciated!) the project will be continued in some form in any case.

 

[BalooRJ]

Sad to see that this project has been discontinued. I bought a pro license as well to use FairEmail from Github downloads since I use GrapheneOS with no Google logins. Thankfully in a few months I'll no longer have a need for any university Microsoft or Google email accounts, so I'll be switching to K-9 Mail full-time. This is just another reason why no one anywhere should be using any major-name email providers like Yahoo, Google, or Microsoft considering their draconian practices from keeping FOSS app developers from using their services. If it is free...YOU are the product!

 

[nadir husain]

Google was pretty friendly and cooperative and told me the favicons are indeed the problem, and it can/should be fixed by updating in the privacy policy to "disclose how your app accesses, collects, uses, and shares user data":



So, I have updated the privacy policy and added this new table:

https://github.com/M66B/FairEmail/blob/master/PRIVACY.md#summary-of-shared-data

I am not sure if it covers everything, so feedback is more than welcome. @mkasimd maybe you can take a look?

Note that I have also enabled BIMI, Gravatars, Libravatars and favicons for the Play store version again.

The short term goal is to release a Play store test version (and associated GitHub version) and to get the update approved. I will think about the next steps after this has been accomplished. Given the huge number of supportive messages I received (much appreciated!) the project will be continued in some form in any case.

Yayy!! I am surprised they didn't make you a job offer.
So relieved!!

 

[deechte]

That's all very positive and promising to hear Marcel! Fingers crossed...

 

[Brulsturm]

Marcel,

You asked for reasons to continue your work:

EXACTLY because of this! This shows (again) Google's true colors.
Only 1-2% of the users might get your app(s) from Github, but they are probably ones wich already freed themselves from Googles chains. And the ones that appreciate the true value of your work the most.

Your work, apps and attitude towards privacy is what keeps me believing I 'm on the right track, living Google-free (99%) for more than 7 years, or something now.
I could put it different: Thanks to apps like FairEmail it is possible for me in everyday life.
The more people discover what Google really is and that you can live whithout, the better.

Whatever you decide, thanks for your software! (and please don't quit)

 

[chris122380]

Google was pretty friendly and cooperative and told me the favicons are indeed the problem, and it can/should be fixed by updating in the privacy policy to "disclose how your app accesses, collects, uses, and shares user data":



So, I have updated the privacy policy and added this new table:

https://github.com/M66B/FairEmail/blob/master/PRIVACY.md#summary-of-shared-data

I am not sure if it covers everything, so feedback is more than welcome. @mkasimd maybe you can take a look?

Note that I have also enabled BIMI, Gravatars, Libravatars and favicons for the Play store version again.

The short term goal is to release a Play store test version (and associated GitHub version) and to get the update approved. I will think about the next steps after this has been accomplished. Given the huge number of supportive messages I received (much appreciated!) the project will be continued in some form in any case.

This is the best news I've heard all day.

I'm not a developer and know a little bit of code but I do have a few Google Play Store questions. How long does it take them to approve your software? I also noticed when other developers announce an update it can take almost a week before I see it. Is the app rollouts controlled by the developer or is that too also controlled by google? If I'm seeking an update I wish Google would let us update it even if it is set to a staggered rollout. This is why I started using the GitHub version for one they were more current and second is because Google takes forever to roll out updates.

 

[M66B]

This is the best news I've heard all day.

I'm not a developer and know a little bit of code but I do have a few Google Play Store questions. How long does it take them to approve your software? I also noticed when other developers announce an update it can take almost a week before I see it. Is the app rollouts controlled by the developer or is that too also controlled by google? If I'm seeking an update I wish Google would let us update it even if it is set to a staggered rollout. This is why I started using the GitHub version for one they were more current and second is because Google takes forever to roll out updates.

It works like this:

• Developer uploads an update via the Play store developer console
• Google scans the update and either approves or disapproves it
• Google makes the app available in the Play store

This can take an hour or a week.

 

[olifee]

I'm a bit late to this topic, but I also want to share my supportive words.

I'm a long-time pro user, and decided to support the project by going pro a few days after installation. I've never even once had any bad feeling about FairEmail. It's not only the most feature-rich client I know, it's also the most privacy oriented one, and it has the best support I have experienced.

I sometimes dream there would be a second Marcel on this planet developing an equally well-made mail client for desktops. FairEmail really goes to show that an application with high usability and a lot of features is not impossible on smartphones. This may be my personal ignorance of the plethora of apps our there, but I'm unaware of any other application which manages to pull that off — and is open source and privacy-oriented at the same time.
I'm just in love with FairEmail and the way it evolved and may still evolve, and I think I will always be. Thanks to Marcel for developing an app which handles the hundreds of mails thrown at me every day with ease, presents them to me in a way I can handle them, and makes my life easier to live.

 

[chris122380]

Google was pretty friendly and cooperative and told me the favicons are indeed the problem, and it can/should be fixed by updating in the privacy policy to "disclose how your app accesses, collects, uses, and shares user data":



So, I have updated the privacy policy and added this new table:

https://github.com/M66B/FairEmail/blob/master/PRIVACY.md#summary-of-shared-data

I am not sure if it covers everything, so feedback is more than welcome. @mkasimd maybe you can take a look?

Note that I have also enabled BIMI, Gravatars, Libravatars and favicons for the Play store version again.

The short term goal is to release a Play store test version (and associated GitHub version) and to get the update approved. I will think about the next steps after this has been accomplished. Given the huge number of supportive messages I received (much appreciated!) the project will be continued in some form in any case.

I have a suggestion for the privacy policy more as a help than for privacy and not necessarily needed in this version of the policy. For where it says that the feature is turned off by default can we have a link to the frequently asked questions on how to enable that feature? (Unless of course that violates Google policy and if so forget it then).

 

[selemine]

It feels a bit weird that a domain icon request has to be declared but it's their store and their rules .
Now we know for sure.