<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket #826: Switching MX records from United to Google</title>
    <link>http://localhost:8080/trac/ticket/826</link>
    <description>&lt;p&gt;
TN are switching the MX records from United to Google on Friday 23/1/15.
&lt;/p&gt;
&lt;p&gt;
Will this affect the website/Web Architects in any way that we need to plan for in advance? Scripts, web forms etc? Anything you can think of?
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/ticket/826</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Mon, 19 Jan 2015 09:30:46 GMT</pubDate>
      <title>cc changed</title>
      <link>http://localhost:8080/trac/ticket/826#comment:1</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;cc&lt;/strong&gt;
              &lt;em&gt;chris&lt;/em&gt; added
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Adding Chris as CC - didn't add him originally - it's for him mostly...
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Mon, 19 Jan 2015 12:31:25 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/826#comment:2</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:2</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.25&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.25&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
As you know I think it is a big mistake to use &lt;a class="ext-link" href="http://wikileaks.org/Op-ed-The-Banality-of-Don-t-Be.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;a evil corporation&lt;/a&gt; for services such as this (I didn't start the clock on this ticket until I had completed this paragraph).
&lt;/p&gt;
&lt;p&gt;
These are the existing MX lines in the Gandi zone file:
&lt;/p&gt;
&lt;pre class="wiki"&gt;@ 	3600 	IN 	MX 	0 	mx1.spamfiltering.com.
@ 	3600 	IN 	MX 	5 	mx2.spamfiltering.com.
tech 	10800 	IN 	MX 	10 	mx.webarch.net.
&lt;/pre&gt;&lt;p&gt;
At a DNS level it'll simply be a matter of changing the above to match &lt;a class="ext-link" href="https://support.google.com/a/answer/174125"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;what Google wants&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;@ 	3600 	IN	MX 	1 	ASPMX.L.GOOGLE.COM.
@ 	3600 	IN	MX 	5 	ALT1.ASPMX.L.GOOGLE.COM.
@ 	3600 	IN 	MX 	5 	ALT2.ASPMX.L.GOOGLE.COM.
@ 	3600 	IN	MX 	10 	ALT3.ASPMX.L.GOOGLE.COM.
@ 	3600 	IN	MX 	10 	ALT4.ASPMX.L.GOOGLE.COM.
tech 	10800 	IN 	MX 	10 	mx.webarch.net.
&lt;/pre&gt;&lt;p&gt;
Note I wouldn't suggest changing the &lt;tt&gt;tech&lt;/tt&gt; line as that would break the incoming email interface for Trac.
&lt;/p&gt;
&lt;p&gt;
In terms of &lt;em&gt;"Scripts, web forms etc? Anything you can think of?"&lt;/em&gt; I can't think of anything apart from ensuring that the same accounts exist as exist at the moment with United and I'm sure you already realise this.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Tue, 20 Jan 2015 09:43:23 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:3</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:3</guid>
      <description>
        &lt;p&gt;
Thanks Chris,
&lt;/p&gt;
&lt;p&gt;
so if I leave the tech line, but turn off the existing mail servers at United, the tech TRAC emails won't be affected as they run off WA servers - please confirm.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Tue, 20 Jan 2015 09:59:05 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:4</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:4</guid>
      <description>
        &lt;p&gt;
Replying to &lt;a href="http://localhost:8080/trac/ticket/826#comment:3" title="Comment 3 for Ticket #826"&gt;ed&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
so if I leave the tech line, but turn off the existing mail servers at United, the tech TRAC emails won't be affected as they run off WA servers - please confirm.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Right, the &lt;tt&gt;tech&lt;/tt&gt; line is only for &lt;tt&gt;whatever@tech.transitionnetwork.org&lt;/tt&gt; emails and has nothing to do with &lt;tt&gt;whatever@transitionnetwork.org&lt;/tt&gt; emails.
&lt;/p&gt;
&lt;p&gt;
Two other things that are probably worth flagging up:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;I need to generate a new SSL cert in the next four days and this will result in a comodo CNAME being added to the zone file, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/820" title="maintenance: *.transitionnetwork.org 2015 security certificate (closed: fixed)"&gt;ticket:820&lt;/a&gt;.
&lt;/li&gt;&lt;li&gt;I seem to remember that if you edit the zone file then it is copied to another file and then if I edit it the same things happens, that is why there is several different zone file names.
&lt;/li&gt;&lt;/ol&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Tue, 20 Jan 2015 10:20:36 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:5</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:5</guid>
      <description>
        &lt;p&gt;
Replying to &lt;a href="http://localhost:8080/trac/ticket/826#comment:4" title="Comment 4 for Ticket #826"&gt;chris&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Replying to &lt;a href="http://localhost:8080/trac/ticket/826#comment:3" title="Comment 3 for Ticket #826"&gt;ed&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
so if I leave the tech line, but turn off the existing mail servers at United, the tech TRAC emails won't be affected as they run off WA servers - please confirm.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Right, the &lt;tt&gt;tech&lt;/tt&gt; line is only for &lt;tt&gt;whatever@tech.transitionnetwork.org&lt;/tt&gt; emails and has nothing to do with &lt;tt&gt;whatever@transitionnetwork.org&lt;/tt&gt; emails.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Confirmed I will leave the tech line in the Gandi DNS zone file while replacing the two UNITED ones with Google ones.
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Two other things that are probably worth flagging up:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;I need to generate a new SSL cert in the next four days and this will result in a comodo CNAME being added to the zone file, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/820" title="maintenance: *.transitionnetwork.org 2015 security certificate (closed: fixed)"&gt;ticket:820&lt;/a&gt;.
&lt;/li&gt;&lt;li&gt;I seem to remember that if you edit the zone file then it is copied to another file and then if I edit it the same things happens, that is why there is several different zone file names.
&lt;/li&gt;&lt;/ol&gt;&lt;/blockquote&gt;
&lt;p&gt;
Yes there is a list of zone files with the latest one being the one Gandi uses.
&lt;/p&gt;
&lt;p&gt;
Will you do this update before Friday? We should stay in touch about who's tinkering when. I will be editing on Friday after work in the evening.
&lt;/p&gt;
&lt;p&gt;
Question: SPF records: is this worth setting up?
&lt;a class="ext-link" href="https://support.google.com/a/answer/33786"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://support.google.com/a/answer/33786&lt;/a&gt;
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Tue, 20 Jan 2015 10:25:30 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:6</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:6</guid>
      <description>
        &lt;p&gt;
Ed note:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;it's DNS zone file ..../469819
&lt;/li&gt;&lt;li&gt;you create a new version with the changes, then tell Gandi to use the new version
&lt;/li&gt;&lt;/ol&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Tue, 20 Jan 2015 10:41:01 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:7</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:7</guid>
      <description>
        &lt;p&gt;
Replying to &lt;a href="http://localhost:8080/trac/ticket/826#comment:5" title="Comment 5 for Ticket #826"&gt;ed&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Will you do this update before Friday? We should stay in touch about who's tinkering when. I will be editing on Friday after work in the evening.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Yes, that would make sense, if I start the process on Thursday then I should be able to complete it during the day on Friday and then it'll be all yours to tinker with the zone files. The existing cert expires at midnight on Saturday so it'll mean there is a day or two overlap but I don't think that is worth worrying about (the issue being that the cert will have been issued for 365 days but only used for 363 or 364 days).
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Thu, 22 Jan 2015 11:27:29 GMT</pubDate>
      <title>hours deleted</title>
      <link>http://localhost:8080/trac/ticket/826#comment:8</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:8</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                &lt;em&gt;0&lt;/em&gt; deleted
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
One thought -- what is the plan with &lt;tt&gt;lists.transitionnetwork.org&lt;/tt&gt;?
&lt;/p&gt;
&lt;p&gt;
Currently, I assume, &lt;tt&gt;whatever@lists.transitionnetwork.org&lt;/tt&gt; goes to United servers via these entries:
&lt;/p&gt;
&lt;pre class="wiki"&gt;@ 	3600 	IN 	MX 	0 	mx1.spamfiltering.com.
@ 	3600 	IN 	MX 	5 	mx2.spamfiltering.com.
&lt;/pre&gt;&lt;p&gt;
If the TN wants to continue using the United Mailman server then I would guess that these entries would be needed (perhaps check with them?):
&lt;/p&gt;
&lt;pre class="wiki"&gt;lists 	3600 	IN 	MX 	0 	mx1.spamfiltering.com.
lists 	3600 	IN 	MX 	5 	mx2.spamfiltering.com.
&lt;/pre&gt;&lt;p&gt;
If the TN is also switching lists to Google then the archives are going to be lost? I'd strongly urge you to ask United for a copy of the HTML and mbox archives of all lists so we can host them somewhere (with password protection as needed) so they are not all lost.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Thu, 22 Jan 2015 14:30:39 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:9</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:9</guid>
      <description>
        &lt;p&gt;
Thanks Chris, good point - the plan is to move all the list activity to google using the groups tools - ending all our services with UNITED. We did not keep any list archives.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Thu, 22 Jan 2015 14:35:53 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:10</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:10</guid>
      <description>
        &lt;p&gt;
Replying to &lt;a href="http://localhost:8080/trac/ticket/826#comment:9" title="Comment 9 for Ticket #826"&gt;ed&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Thanks Chris, good point - the plan is to move all the list activity to google using the groups tools - ending all our services with UNITED. We did not keep any list archives.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Don't fully understand, the list archives will still exist, the list are still functioning, are you saying you don't want to keep any archives of the lists?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Thu, 22 Jan 2015 14:42:23 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:11</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:11</guid>
      <description>
        &lt;p&gt;
I am saying that Transition Network doesn't want to keep an archive of its mailing lists - the archiving was turned off some time ago...
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Thu, 22 Jan 2015 14:56:03 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:12</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:12</guid>
      <description>
        &lt;p&gt;
Replying to &lt;a href="http://localhost:8080/trac/ticket/826#comment:11" title="Comment 11 for Ticket #826"&gt;ed&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I am saying that Transition Network doesn't want to keep an archive of its mailing lists - the archiving was turned off some time ago...
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
The GZ'd mbox files are unavailable, I guess that is what you mean, but the HTML archives are still available, at least for the TTech list:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://lists.transitionnetwork.org/mailman/private/ttech_lists.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.transitionnetwork.org/mailman/private/ttech_lists.transitionnetwork.org/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
If I were you I'd ask United for a tar ball of these so they can be kept for posterity / referencing as needed (password protected).
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>chris</dc:creator>

      <pubDate>Thu, 22 Jan 2015 14:58:21 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:13</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:13</guid>
      <description>
        &lt;p&gt;
If you don't want to ask United for a copy of the archives we could use a script such as this one to scrape them:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://github.com/philgyford/mailman-archive-scraper"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/philgyford/mailman-archive-scraper&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Thu, 22 Jan 2015 15:01:03 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:14</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:14</guid>
      <description>
        &lt;p&gt;
Thanks - I'll add it to the list of things I can do if there's time. I used to work with Phil Gyford; brilliant man.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Fri, 23 Jan 2015 20:22:27 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:15</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:15</guid>
      <description>
        &lt;p&gt;
OK I'm doing the DNS zone update NOW.
&lt;/p&gt;
&lt;p&gt;
Negotiations with UNITED about archives are ongoing.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Fri, 23 Jan 2015 20:36:55 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:16</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:16</guid>
      <description>
        &lt;p&gt;
Now using &lt;strong&gt;version 17&lt;/strong&gt; of the Gandi DNS zone file with the UNITED MX files removed and the google MX files added
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Fri, 23 Jan 2015 22:15:26 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:17</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:17</guid>
      <description>
        &lt;p&gt;
Added SPF text to &lt;strong&gt;version 18&lt;/strong&gt; of the DNS zone file and updated Gandi
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Thu, 29 Jan 2015 11:04:20 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost:8080/trac/ticket/826#comment:18</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:18</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;fixed&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
The MX switch has gone fine so I am closing this ticket as fixed.
&lt;/p&gt;
&lt;p&gt;
I am failing at making myself understood with UNITED support about the back ups over various emails. I am copying Chris' explanations verbatim and going round in circles.
&lt;/p&gt;
&lt;p&gt;
UNITED say perhaps we can do this via the CPanel login - which we will have for a bit longer before I cancel the account.
&lt;/p&gt;
&lt;p&gt;
"I'm unsure as to your request but yes you can use cPanel &amp;gt; Files &amp;gt; File Manager to complete most file related tasks. "
&lt;/p&gt;
&lt;p&gt;
Therefore I have spent enough time on the back up idea for now and have pressing stuff to do, so am de-prioristing the back up question.
&lt;/p&gt;
&lt;p&gt;
If Ade or Chris want to pick it up I am happy for them to.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Mon, 16 Feb 2015 14:42:48 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/826#comment:19</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/826#comment:19</guid>
      <description>
        &lt;p&gt;
NB: The United service has been cancelled. It will end on 12/3/15.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>