mirror
/
FairEmail
mirror of https://github.com/M66B/FairEmail.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated FAQ

This commit is contained in:
M66B 2024-02-03 13:56:52 +01:00
parent 00b68e0b63
commit 0b0a04933f
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
FAQ.md
View File

@ -3338,6 +3338,10 @@ If you receive a lot of spam messages in your inbox, the best you can do is to c
Also, FairEmail can show a small red warning flag
when DKIM, SPF or [DMARC](https://en.wikipedia.org/wiki/DMARC) authentication failed on the receiving server.
You can enable/disable [authentication verification](https://en.wikipedia.org/wiki/Email_authentication) in the display settings.
The feature depends on the header [Authentication-Results](https://datatracker.ietf.org/doc/html/rfc7601), which the receiving email server should add.
If the email server doesn't add an *Authentication-Results*, which is optional,
you can enable native DKIM in the debug panel, which appears when you enable debug mode in the miscellaneous settings tab page (last option).
Please be aware that this option will increase both data and battery usage.
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.
@ -5146,8 +5150,6 @@ Received: brown.elm.relay.mailchannels.net (brown.elm.relay.mailchannels.net. [2
for <test@example.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
```
The feature depends on the header *Authentication-Results*, which the receiving email server should add.
<br />
<a name="faq177"></a>

3
index.html
View File

@ -1734,7 +1734,7 @@ Y1 OK CAPABILITY completed</code></pre>
<p>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 <em>Automatically block the sender when reporting spam</em> in the behavior settings tab page.</p>
<p>Since version 1.2143, there is an “<em>Unblock all</em>” button in the receive-settings tab page, which will reset all above options.</p>
<p>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.</p>
<p>Also, FairEmail can show a small red warning flag when DKIM, SPF or <a href="https://en.wikipedia.org/wiki/DMARC">DMARC</a> authentication failed on the receiving server. You can enable/disable <a href="https://en.wikipedia.org/wiki/Email_authentication">authentication verification</a> in the display settings.</p>
<p>Also, FairEmail can show a small red warning flag when DKIM, SPF or <a href="https://en.wikipedia.org/wiki/DMARC">DMARC</a> authentication failed on the receiving server. You can enable/disable <a href="https://en.wikipedia.org/wiki/Email_authentication">authentication verification</a> in the display settings. The feature depends on the header <a href="https://datatracker.ietf.org/doc/html/rfc7601">Authentication-Results</a>, which the receiving email server should add. If the email server doesn’t add an <em>Authentication-Results</em>, which is optional, you can enable native DKIM in the debug panel, which appears when you enable debug mode in the miscellaneous settings tab page (last option). Please be aware that this option will increase both data and battery usage.</p>
<p>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.</p>
<p>If the domain name of the sender and the domain name of the reply address differ, the warning flag will be shown too because this is most often the case with phishing messages. If desired, this can be disabled in the receive settings (since version 1.1506).</p>
<p>If legitimate messages are failing authentication, you should notify the sender because this will result in a high risk of messages ending up in the spam folder. Moreover, without proper authentication there is a risk the sender will be impersonated. The sender might use <a href="https://www.mail-tester.com/">this tool</a> to check authentication and other things.</p>
@ -2547,7 +2547,6 @@ _submission._tcp SRV 0 1 587 smtp.example.com.</code></pre>
<pre><code>Received: brown.elm.relay.mailchannels.net (brown.elm.relay.mailchannels.net. [23.83.212.23])
by mx.google.com with ESMTPS id d10si6675855pgb.5.2021.12.24.13.20.38
for &lt;test@example.org&gt; (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);</code></pre>
<p>The feature depends on the header <em>Authentication-Results</em>, which the receiving email server should add.</p>
<p><br /></p>
<p><a name="faq177"></a> <strong>(177) What does ‘Sensitivity’ mean?</strong></p>
<p>🌎 <a href="https://translate.google.com/translate?sl=en&amp;u=https%3A%2F%2Fm66b.github.io%2FFairEmail%2F%23faq177">Google Translate</a></p>