You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each domain, look up the DNS MX record. Look at the MX hostname. Find who is the hoster. Also find out which clusters they have. E.g. Yahoo and Outlook.com have US and European clusters, and we need to differentiate them. But we want to merge live.de, live.fr, live.it, outlook.de, hotmail.de etc. into the same config, if possible. What matters is the mail storage cluster, but you can typically see that from the MX hostnames.
Find the correct IMAP, POP3 and SMTP configuration, using the customer help or support documents that they publish. You can typically search for " thunderbird IMAP hostname" or a similar search. But important make sure that your are the official website of the provider. Or that the config hostnames match the provider's main domain (e.g. imap.sekan.net for [email protected]).
We need: hostname, port number, TLS or STARTTLS (which one of the two) - each for IMAP, POP3 and SMTP. Also username form ("[email protected]" (preferred) or "foo" or something else?), and whether an app-specific password is required.
Write these into an Excel or LibreOffice Calc sheet or a text file.
But IMPORTANT: You are NOT ALLOWED to look at either the Mozilla ISP DB (which I, Ben Bucksch, originally created), nor at copycat websites. The entire purpose of the excersize is to re-create the information from scratch, from original sources, not from the existing ISPDB. This is important for legal reasons. This is a "clean room" re-creation of the DB.
The text was updated successfully, but these errors were encountered:
But IMPORTANT: You are NOT ALLOWED to look at either the Mozilla ISP DB (which I, Ben Bucksch, originally created), nor at copycat websites. The entire purpose of the excersize is to re-create the information from scratch, from original sources, not from the existing ISPDB. This is important for legal reasons. This is a "clean room" re-creation of the DB.
The text was updated successfully, but these errors were encountered: