3 ms·
Well if you receive an email from any of those, your email client requests something from those domain names (which a lot of email clients will do by default).
by gommm 4y ago
Well if you receive an email from any of those, your email client requests something from those domain names (which a lot of email clients will do by default). So it'd also show in the firewall logs etc..
So that favicon feature should be an optional feature but calling it sharing contact details is really exaggerating it.
EDIT: It is even optional, so yes really it's a non-issue.
- g_p 4y agoMy understanding is that this was an optional feature, and turned off by default - a user wanting to use this would need to enable it manually. If a user turns on a feature to request favicons for received mail, it therefore seems logical that the app has to retrieve favicons. Doing direct retrieval is likely less damaging to privacy than using a central favicon retrieval server.
- corney91 4y agoI use FairEmail so I just checked: Display Favicons is disabled by default and there's a note below the setting that says "there might be a privacy risk" and links to https://en.wikipedia.org/wiki/Favicon https://en.wikipedia.org/wiki/Favicon
- teawrecks 4y agoAgreed, 1) it's not sharing contacts, 2) it only pings those domains if you enable the optional feature. This is exactly how I'd want the app to behave, and I honestly can't think of a better way to handle it. Maybe caching the favicons on a server hosted by the app creator so that no matter what domain the app looks up, it looks like it's contacting FairEmail.