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

Search This thread

fraschi51

Senior Member
Mar 17, 2016
1,105
385
You can also reply with a template.

Note that you can make one or more templates favorite, which will show them directly in the answer popup menu.
Yes, I know, but that doesn't use so much here in my case, because I usually use templates here not for replying, but for composing, e.g. for my numerous birthday greeting emails.
 

M66B

Recognized Developer
Aug 1, 2010
25,754
54,978

heinhuiz

Senior Member
Nov 26, 2011
1,114
867
Xiaomi Mi A1
Redmi K20 / Xiaomi Mi 9T
  • Like
Reactions: M66B
I like to hear suggestions for a new release name:


Hi,

I like those 2, but can't picked one between :

*Euskelosaurus*
Euskelosaurus ("good leg lizard") (...). Fossils have only been recovered from the lower Elliot Formation in South Africa and Lesotho,[1] and in one locality in Zimbabwe.
Its bones are robust and it had a graviportal limb arrangement, a key character trait of basal sauropodomorphs.

*Elopteryx*
(...) found near Sînpetru, in what is now the Romanian region of Transylvania, some bone fragments of a small theropod.
The genus name Elopteryx is from Ancient Greek helos (ἕλος), "marsh" + pteryx (πτέρυξ), "wing".

Edit
This one is really interesting,
Name 'catching' 😇
Description with many level underlying...
but not sure everyone will be cool with the 'pun' and 'seriousness' of the description 🙃
*Epidexipteryx*
 
Last edited:
  • Like
Reactions: WiraHy and M66B

M66B

Recognized Developer
Aug 1, 2010
25,754
54,978
Since downloading attachments on demand doesn't appear to work anymore due to a recent change, version 1.1812 isn't available for downloading anymore. I will fix this soon.
 
  • Like
Reactions: husky61 and ROO3VER

M66B

Recognized Developer
Aug 1, 2010
25,754
54,978
Version 1.1814 is available on Bitbucket now. which means that there won't be an 'update' notification.

Since the protocol to set messages as seen (read), flagged (starred) and deleted (permanent deletion) has been changed, this is a somewhat EXPERIMENTAL RELEASE. If email is very important to you, please skip this version. Of course everything was tested, but there might be unforeseen side effects.

Download:
https://bitbucket.org/M66B/fairemail-test/downloads/FairEmail-v1.1814a-github-release.apk

Changelog:
https://github.com/M66B/FairEmail/blob/master/CHANGELOG.md

All changes:
https://github.com/M66B/FairEmail/compare/1.1813...1.1814?w=1

Support for the Sensitivity header was added, and the value (personal, private, confidential) will be displayed in the message header (see the legend) and can be set via the send dialog (long press the send button if needed).
 
Support for the Sensitivity header was added, and the value (personal, private, confidential) will be displayed in the message header (see the legend) and can be set via the send dialog (long press the send button if needed).


Hi everyone,

Maybe off topic, but about the sensitivity header and the RFC.
I tried to read the document but not sure about the outcome :
- is there a hierarchical relationship between the 3 values ?
or it's ''just'' a tag ?
- how do the server handle (if it supported) any message with that header set ? From a user perspective.
Do the a user could or not be able to do an action according to it ?

Thanks
 

M66B

Recognized Developer
Aug 1, 2010
25,754
54,978
Hi everyone,

Maybe off topic, but about the sensitivity header and the RFC.
I tried to read the document but not sure about the outcome :
- is there a hierarchical relationship between the 3 values ?
or it's ''just'' a tag ?
- how do the server handle (if it supported) any message with that header set ? From a user perspective.
Do the a user could or not be able to do an action according to it ?

Thanks
It are 'tags', used by some companies.

For now, FairEmail does nothing with the headers, except add them when sending a message and show them for received messages.

As I see it (I might be wrong):
  • personal: only for you
  • private: for you and close persons
  • confidential: within an company/organization/department

Sensitive messages *should* not be (automatically) forwarded, but I don't think it is a good idea to enforce this in the app.

This is the best article I could find about this subject:

 

Top Liked Posts

  • 24
    Version 1.1900 has been approved by Google and is available in the test program now.
    I didn't receive feedback from Google's privacy and policy team yet though.
    18
    I didn't receive feedback from Google's privacy and policy team yet. I don't expect feedback today, on Ascension Day, in any case.

    Also, I asked better to be thorough than to be fast to prevent trouble later on again.

    I'll keep you informed.
    4
    Marcel, just to add my voice to all those who have so much appreciated FE.
    Your work has been really appreciated. Good luck, thanks for reconsidering and I wish you and yours all the best.
    4
    Really happy you managed to talk with a real person at Google. That's not something many smaller devs ever manage to do.

    I didn't know FairEmail before, but I've been using (and recommending) Netguard for years.

    I'll definitly check out FairEmail, though.

    Btw, I think it's kinda funny to see how many people seem to think, that a one-time payment of $6 would give them a right to unlimited life-time updates.

    Any app can be discontinued at any time (and most will at some time). Unless you have a contract specifying otherwise, that's just how that works.

    There is a term for what those guys expect. It's (incredibly cheap) indentured servitude. And luckily, that's illegal.
    2
    Version 1.1900 has been approved by Google and is available in the test program now.
    I didn't receive feedback from Google's privacy and policy team yet though.
    Congratulations Marcel 👏
    It's the begining if a new life for you and FE !
  • 62
    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.
    42
    Version 1.1900 is available on GitHub now and in the Play store test program after Google's approval (which is the main goal of this release).

    Changelog/download:
    https://github.com/M66B/FairEmail/releases

    My girlfriend is slowly recovering too :)
    30
    The balance

    The few euros I receive in return for what's being offered and the fun of developing things are no compensation for the thousands of questions I answer every month, for unfair Play store reviews and for stress about unclear Google requirements.


    The verdict

    I have not reached a conclusion yet, but the question I am asking myself is why I would continue with the project. Maybe it is the moment, with a sick girlfriend, but I currently don't see it.


    Alternatives

    GitHub only version: 98% of the audience will be lost.

    Strip down the app: more bad reviews

    Paid support: more bad reviews

    Stop answering questions: more bad reviews

    Bad reviews will shift the balance only in the wrong direction.


    Core problem

    Google. There is no sensible way to appeal in case of bad reviews or alleged violations of Play store policies.

    People. They are generally pretty demanding and on the other hand everything should be free.

    Myself. An old and grumpy developer, who maybe should retired.


    Input is welcome.
    27
    I paid for this software and donated several times, so what would I gain by trolling? I share my opinion with you and get trolled by you because you don't like it? It is much sadder how grateful my money is accepted although I would troll. Would you rather be lied to and cheated instead or how do I have to imagine this? Honestly, I do not care if you like my opinion or not. I stand by it and think my part.
    I feel responsible, but what is your problem exactly? The app as-is works fine and it will keep working fine for the foreseeable future. I even published an update in this thread yesterday for an ugly problem introduced in recent versions. Please tell me what is wrong and I will see what I can do. Please be nice and you'll be responded to in the same way. There is already enough hate on this planet.

    Please understand that mainly Google caused this "event". There is some good news though because a real human contacted me outside the usual Google "flow". There will be a phone call Tuesday.
    24
    On special request by PM of OP, Marcel aka @M66B, I have to inform you as follows:
    Can you please write in each XDA thread that the GitHub repos have been restored?
    Marcel, I know you can't respond here but personally I hope that this isn't your final decision.
  • 230
    ic_launcher.png

    FairEmail
    Open source, privacy friendly email app for Android

    banner7_long.png


    See here for a description:
    https://github.com/M66B/open-source-email/

    Downloads:
    https://github.com/M66B/open-source-email#user-content-downloads

    See this XDA article for some screenshots:
    https://www.xda-developers.com/fairemail-open-source-privacy-friendly-email/

    See here for more screenshots:
    https://email.faircode.eu/#screenshots

    Frequently asked questions:
    https://github.com/M66B/open-source-email/blob/master/FAQ.md

    This XDA thread is about using the latest version of FairEmail.

    For support on authorizing an account you should consult the documentation of your provider, see also here.

    Off topic comments are allowed as long they are related to FairEmail and are in the general interest of the followers of this thread.

    Discussion of purchases is not allowed here, please contact me via here instead.


    XDA:DevDB Information
    FairEmail, App for all devices (see above for details)

    Contributors
    M66B
    Source Code: https://github.com/M66B/open-source-email/


    Version Information
    Status:
    Stable

    Created 2018-08-02
    Last Updated 2020-11-18
    62
    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.
    45
    It is time for a new, modern, open source, privacy friendly email client for Android.

    I have just released a first alpha version for feedback on the design and features.

    Not for production use yet!

    Most of the stuff basically works, but be prepared for crashes and error notifications.


    Safe email is a working name, but it is for several reasons not a convenient name, so suggestions for a name are welcome.
    42
    Version 1.1900 is available on GitHub now and in the Play store test program after Google's approval (which is the main goal of this release).

    Changelog/download:
    https://github.com/M66B/FairEmail/releases

    My girlfriend is slowly recovering too :)
    37
    I have just released alpha version 0.15

    Changelog/download:
    https://github.com/M66B/open-source-email/releases

    With a bit of luck the next version can be a beta version.

    I am putting a lot of effort into this project, so thanks are appreciated.