Now peering at SFMIX in the San Francisco “Silicon Valley” region of California. Roller Network has an open peering policy and we are happy to peer with networks of any size. We’re also on the route servers.
Since the very beginning of our hosted mail service, SquirrelMail was there as a webmail option. It’s served thousands of users well, but the time has come where we need to declare SquirrelMail end of life (EOL) and no longer supported. SquirrelMail has not been actively developed for several years, and incompatibility with other upgrades we will be making across our system is very likely.
As an EOL service, we will no longer test changes for compatibility with SquirrelMail. Although the basic email functions of SquirrelMail will continue to function, any broken additional features in SquirrelMail will be removed or disabled.
We understand the desire for a simple webmail interface still exists in our customer base and we will be looking at replacement options. In the meantime, please plan to migrate your webmail needs to RoundCube at: https://webmail.rollernet.us/roundcube
SquirrelMail will be shut down on December 31, 2020.
Over the next several weeks are are going to try to get all of our systems updated to Debian 9 (oldstable) or ideally Debian 10 (stable) wherever possible. Many systems are still running Debian 8 LTS for which security support ends in June.
We will do our best to minimize disruptions. Any work that’s unavoidably disruptive will be performed during our weekly maintenance window every Saturday between 10:00 and 22:00. An example of a system that’s disruptive would be the account control center, webmail, or IMAP/POP3 hosted mail. To completely update a system there are required reboots, and in some cases (most notably IMAP/POP3 hosted mail), forced switches between active/standby pairs to verify functionality. Updates on our in-office system will cause interruptions to our phone and hotline number (which run on Asterisk) while we perform its upgrades. Email us if you don’t hear the voice prompts answer since someone will be watching for emails when we know voice is being worked on. Work to non-interactive systems like ns1/ns2 may be performed at any time since our supported configuration is that customers configure both on their domain, not just one. We may also decide to migrate older hardware based systems to a virtual machine on a case-by-case basis.
If you have any questions please contact support.
Almost 9 years ago we set up some publicly accessible IPv6 time servers. At the time there were few to no options for NTP over IPv6.
However, it’s time to retire those servers. They’ve run faithfully for almost 10 years and their watch is over. We don’t have a replacement for this service, but NIST has IPv6 NTP servers in their pool: https://tf.nist.gov/tf-cgi/servers.cgi
The IP addresses of our mail forwarding servers will be changing:
- Old IPv4 Address: 18.104.22.168
- Old IPv6 Address: 2607:fe70:0:16::a
- NEW IPv4 Address: 22.214.171.124
- NEW IPv6 Address: 2607:fe70:0:3::f
- NEW Name: mxfwd-a.rollernet.us
- Old IPv4 Address: 126.96.36.199
- Old IPv6 Address: 2607:fe70:0:16::b
- NEW IPv4 Address: 188.8.131.52
- NEW IPv6 Address: 2607:fe70:0:4::f
- NEW Name: mxfwd-b.rollernet.us
If you have created whitelists or used these servers in SPF records (we will update
include:m._spf.rollernet.us accordingly) please make sure to add the new addresses alongside the old addresses while this transition is in progress. Once completed, the old IP addresses will no longer be used for any mail-related functions.
CNAME records will be added pointing the legacy names to the new names, so it will be safe to continue referencing the old names.
If you are not using the Mail Forwarding functions in the account control center you will not be affected by this change. Log in to your account and see https://acc.rollernet.us/mail/mapping.php to check if you have mail forwarding configured.
The physical servers are being retired and their mail-related functions replaced with virtual machines. We’ll be repurposing the subnet for timing services since the forwarding servers were also used for NTP (ntp.rollernet.us) and installing Rubidium-based timing systems. This will ensure that functions that are more DNS friendly SMTP functions will transition smoothly, and NTP configurations which are normally configured by IP or only resolved in DNS once will continue with no impact.
UPDATE: All changes were completed successfully.