Roller NetworkIt’s been a while since we posted a Verizon update. The last time we had contact with them was at the end of December, and we recently learned that as of Friday (02-12-2010) that no progress has been made in re-provisioning the circuit to match what was ordered. The latest roadblock is that there isn’t any capacity at the San Jose hub for us. This has become the longest attempt at a new circuit turn-up that we have ever had the displeasure to experience.
The logs for Outbound Accounts have returned!
We have added preliminary IPv6 support (display only, no CIDR searching yet) and our queue ID will now be logged if the message was accepted into the mail queue. Viewing is now by outbound account name instead of domain name, which means that submissions from “mail server” account types are now viewable in the logs.
Due to these changes there’s a new URL for the outbound account logs:
If you’re feeling brave and have IPv6 connectivity, you can now submit mail to our Outbound Mail service (SMTP AUTH) over IPv6 by connecting to “smtpauth6.rollernet.us”. All of the same ports and TLS available under IPv4 also apply as we have simply dual-stacked the service. Please see “Submitting Outbound Mail via IPv6” on the forums for current limitations.
As far as we’re aware, Roller Network one of the very few – maybe even the first – provider in our arena to enable IPv6 for transport-level SMTP. This is quite a bit more substantial than simply making a website IPv6 available, so please send us feedback if you try it.
If you’ve been keeping up on our newspipe you’ll know that the long story of delays with Verizon continues. We were informed yesterday (Dec 22.) that the circuit was ready, however it still does not need our basic requirements (IPv4/IPv6 dual stack). This is continuing to impact our ability to expand our colocation, dedicated servers, and hosting options.
As such, we have decided to enact a backup plan and bring in an additional circuit from Sprint so we can get back to business with a predictable timeline. The installation interval should be about 60 days plus we have requested an expedite on the order. As we’ve been a Sprint customer for 5 years and already have existing service with them, we do not expect the same problems that have plagued our attempt at obtaining service with Verizon. Furthermore, we are pleased to report that Sprint’s IPv6 offering is moving to their native network after we’ve been on their test network for the last 4 years. As soon as we have more information from Sprint we will share it here.
Again, we apologize for the delays and problems we’ve faced beyond our control in not meeting our original October/November 2009 opening of the new facility.
As today is December 24 this will be our last post on the newspipe for 2009. We’re going to take it easy for the next week so we can recharge and regroup for what lies ahead. As many of you (and us) are on vacation, holiday, or spending the new year with family and friends, we will be operating on a reduced schedule. Technical support will still be available. See you in 2010!
We were notified on December 10 that the circuit was finally ready to be turned up. However, during the process of assigning point-to-point addresses to the link, we discovered that it was out of Sacramento, CA. That means it was provisioned incorrectly yet again, just like back in September.