[api-web] autoconfig: Rename README to README.evolution
- From: Matthew Barnes <mbarnes src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [api-web] autoconfig: Rename README to README.evolution
- Date: Wed, 5 Nov 2014 15:48:52 +0000 (UTC)
commit 5037093b02cf70c32f4e22ce426c7d0fcf63321a
Author: Matthew Barnes <mbarnes redhat com>
Date: Wed Nov 5 10:45:39 2014 -0500
autoconfig: Rename README to README.evolution
Mozilla's autoconfig source repository also has a README file.
Rename ours so they don't keep conflicting everytime I do an update.
evolution/autoconfig/1.1/README | 64 ++++++++---------------------
evolution/autoconfig/1.1/README.evolution | 53 ++++++++++++++++++++++++
2 files changed, 71 insertions(+), 46 deletions(-)
---
diff --git a/evolution/autoconfig/1.1/README b/evolution/autoconfig/1.1/README
index 2cc2a53..107e5fb 100644
--- a/evolution/autoconfig/1.1/README
+++ b/evolution/autoconfig/1.1/README
@@ -1,53 +1,25 @@
-The files in this directory are used by Evolution 3.6 and later to
-automatically configure email accounts. This so that you can tell it,
-"My mail is example gmail com" and it will automatically figure out that
-it must use imap.googlemail.com and smtp.googlemail.com.
+https://wiki.mozilla.org/MailServerList
+https://developer.mozilla.org/en/Thunderbird/Autoconfiguration
+https://wiki.mozilla.org/Thunderbird:Autoconfiguration
+http://spreadsheets.google.com/ccc?key=p49SW32nNYX0otkRc3UZUJA
-The files in this directory use the <clientConfig version="1.1"> format,
-whereas files in the parent directory use the initial <clientConfig> format.
-As far as I can tell, there's merely some naming differences between the two.
+Any changes where will go live and affect the new account settings of all
+TB3 users, so be careful. Be sure to read the docs above.
-The files themselves need to be named after an authoritative name server
-for the domains listed in the file, based on the domain's NS record in DNS.
-For example:
+Alternative configurations
- $ dig ns rocketmail.com
+Some ISPs / providers have different kinds of users underneath the
+same domain, e.g. allows IMAP only for users who pay more.
+Another case is when a provider requires different configurations
+depending on situation: E.g. one only works within their ISP network,
+others only work in their hotspots etc.pp..
- ; <<>> DiG 9.8.1-P1 <<>> mx rocketmail.com
- ;; global options: +cmd
- ;; Got answer:
- ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4974
- ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 5, ADDITIONAL: 16
+In these cases, we'll create one file for each config alternative, with
+filename domain, space, reason, e.g. "gmx.de" and "gmx.de pay". Because
+TB3 does not requests domains with a space, these alternative configs are
+effectively inactive.
- ... <snipped> ...
+This problem would of course be much easier with a database.
- ;; ANSWER SECTION:
- rocketmail.com. 29284 IN NS ns1.yahoo.com.
- rocketmail.com. 29284 IN NS ns5.yahoo.com.
- rocketmail.com. 29284 IN NS ns3.yahoo.com.
- rocketmail.com. 29284 IN NS ns4.yahoo.com.
- rocketmail.com. 29284 IN NS ns2.yahoo.com.
-
- ... <snipped> ...
-
- ;; Query time: 101 msec
- ;; SERVER: 10.5.26.21#53(10.5.26.21)
- ;; WHEN: Fri Mar 23 08:25:42 2012
- ;; MSG SIZE rcvd: 505
-
-Evolution will perform its own NS record lookup, extract the highest
-priority record, and pare down the name server domain until it gets a
-match like so:
-
- http://api.gnome.org/evolution/autoconfig/1.1/ns1.yahoo.com : NOT FOUND
- http://api.gnome.org/evolution/autoconfig/1.1/yahoo.com : FOUND!
-
-Run the test-nameservers.py script periodically to verify symbolic links
-for authoritative name server domains.
-
-These files are copied from
-http://svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk
-
- Matthew Barnes
- November 2012
+Ben Bucksch
diff --git a/evolution/autoconfig/1.1/README.evolution b/evolution/autoconfig/1.1/README.evolution
new file mode 100644
index 0000000..2cc2a53
--- /dev/null
+++ b/evolution/autoconfig/1.1/README.evolution
@@ -0,0 +1,53 @@
+The files in this directory are used by Evolution 3.6 and later to
+automatically configure email accounts. This so that you can tell it,
+"My mail is example gmail com" and it will automatically figure out that
+it must use imap.googlemail.com and smtp.googlemail.com.
+
+The files in this directory use the <clientConfig version="1.1"> format,
+whereas files in the parent directory use the initial <clientConfig> format.
+As far as I can tell, there's merely some naming differences between the two.
+
+The files themselves need to be named after an authoritative name server
+for the domains listed in the file, based on the domain's NS record in DNS.
+
+For example:
+
+ $ dig ns rocketmail.com
+
+ ; <<>> DiG 9.8.1-P1 <<>> mx rocketmail.com
+ ;; global options: +cmd
+ ;; Got answer:
+ ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4974
+ ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 5, ADDITIONAL: 16
+
+ ... <snipped> ...
+
+ ;; ANSWER SECTION:
+ rocketmail.com. 29284 IN NS ns1.yahoo.com.
+ rocketmail.com. 29284 IN NS ns5.yahoo.com.
+ rocketmail.com. 29284 IN NS ns3.yahoo.com.
+ rocketmail.com. 29284 IN NS ns4.yahoo.com.
+ rocketmail.com. 29284 IN NS ns2.yahoo.com.
+
+ ... <snipped> ...
+
+ ;; Query time: 101 msec
+ ;; SERVER: 10.5.26.21#53(10.5.26.21)
+ ;; WHEN: Fri Mar 23 08:25:42 2012
+ ;; MSG SIZE rcvd: 505
+
+Evolution will perform its own NS record lookup, extract the highest
+priority record, and pare down the name server domain until it gets a
+match like so:
+
+ http://api.gnome.org/evolution/autoconfig/1.1/ns1.yahoo.com : NOT FOUND
+ http://api.gnome.org/evolution/autoconfig/1.1/yahoo.com : FOUND!
+
+Run the test-nameservers.py script periodically to verify symbolic links
+for authoritative name server domains.
+
+These files are copied from
+http://svn.mozilla.org/mozillamessaging.com/sites/autoconfig.mozillamessaging.com/trunk
+
+ Matthew Barnes
+ November 2012
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]