Note that a sender will automatically be blocked when a message is moved into the spam folder. You can disable this behavior by disabling the option Automatically block the sender when reporting spam in the behavior settings tab page.
+Since version 1.2143, there is an “Unblock all” button in the receive-settings tab page, which will reset all above options.
If you receive a lot of spam messages in your inbox, the best you can do is to contact the email provider to ask if spam filtering can be improved.
Also, FairEmail can show a small red warning flag when DKIM, SPF or DMARC authentication failed on the receiving server. You can enable/disable authentication verification in the display settings.
FairEmail can show a warning flag too if the domain name of the (reply) email address of the sender does not define an MX record pointing to an email server. This can be enabled in the receive settings. Be aware that this will slow down synchronization of messages significantly.
@@ -1754,9 +1755,9 @@ Y1 OK CAPABILITY completedFairEmail uses services and alarms, provides widgets and listens for the boot completed event to be started on device start, so it is not possible to store the app on external storage media, like an sdcard. See also here.
Since the app is small anyway and the data files will be stored in the same place, the benefit would be limited anyway.
Messages, attachments, etc stored on external storage media, like an sdcard, can be accessed by other apps and is therefore not safe. See here for the details. Instead, consider to use adoptable storage.
-Since version 1.1829 is it possible to store attachments to external storage space private to the app (except for file managers) via an option in the debug panel. You can enable the debug panel by enabling debug mode in the miscellaneous settings (last option). To prevent ongoing operations from storing attachments at the old location you should disable receiving messages in the receive settings and wait until all operations have been completed before changing this option. Please be aware that removing the storage space will inevitably result in problems, which is one of the reasons why this option is hidden.
Moving messages to an sdcard is not an option because this would significantly reduce the response times of the app.
The option to move attachments to external storage space was removed in version 1.2137 because Play Store policies considers it unsafe.
+Since version 1.1829 is it possible to store attachments to external storage space private to the app (except for file managers) via an option in the debug panel. You can enable the debug panel by enabling debug mode in the miscellaneous settings (last option). To prevent ongoing operations from storing attachments at the old location you should disable receiving messages in the receive settings and wait until all operations have been completed before changing this option. Please be aware that removing the storage space will inevitably result in problems, which is one of the reasons why this option is hidden.
+Please note that more often than not the external storage space is emulated on recent Android versions and recent devices. and that there is no longer a viable way to get permission to write to other locations.
+Moving messages to an sdcard is not an option because this would significantly reduce the response times of the app.
When needed you can save (raw) messages via the three-dots menu just above the message text and save attachments by tapping on the floppy icon.
If you need to save on storage space, you can limit the number of days messages are being synchronized and kept on your device and disable downloading and storing of message texts and attachments (which means only message headers will be stored). You can change these settings by long pressing a folder in the folder list and selecting Edit properties.