We’re currently doing a major upgrade of the support system we use to manage support tickets on https://support.runbox.com.
We appreciate your patience while we get everything working properly.
The Runbox website is now protected by an Extended Validation Certificate when in secure mode at https://secure.runbox.com. This is usually indicated by a green address bar in your browser.
This certificate independently verifies the identity of our company as the owner of the domain runbox.com, meaning that visitors can be certain the web pages they see are legitimate.
We recommend you always be aware of the domain name shown in your browser, especially after clicking links in email messages, to prevent so-called phishing.
We also recommend using secure mode (SSL) when logging on to Runbox. You can enable this in your browser by clicking the “Secure” link next to the login fields on the front page.
We just donated to Wikipedia and encourage other companies to do the same.
Wikipedia is ad-free and relies on donations for their servers and staff, and it’s a fantastic resource for anyone interested in independent and objective information about virtually any topic imaginable.
We have now completed the update of port 465 for SMTP (Sending Email). If you have issues sending emails after the update, you can change to port 587.
If things still does not work for you, then open a ticket with Support: https://support.runbox.com/
On Thursday, October 27, we will perform a configuration change on the Runbox email servers that affects a few of our users.
If your email program (such as Outlook and Thunderbird) is using port 465 for sending email (SMTP), please read on.
If you don’t know whether your email program is using port 465, please check the settings for your Runbox account in your email program.
What is being changed?
In order to conform to email protocol standards and to correct a problem affecting Android-powered smart phones, the outgoing (SMTP) port 465 will now require that SSL (secure connections) is enabled.
This change will also affect other email programs that use port 465.
What you can do
Different email programs react differently to this change, and you might not have to do anything at all.
If you have trouble sending email after the change is completed on Thursday, please update your email program’s outgoing (SMTP) settings to use SSL.
Alternatively, change your program’s outgoing (SMTP) port number from 465 to 587, which will work both with SSL and without.
If none of this works, you can remove the settings for outgoing email and set them up again according to these instructions:
http://doc.runbox.com/twiki/bin/view/RunboxHelp/SMTP
If you have any questions regarding this change, please open a support ticket at https://support.runbox.com.
17:00 CET (11 AM EST)
We need to replace a disk in the server responsible for delivering outgoing email, which means that email sent by our users will be delayed a few minutes while the server is down.
Everything should work normally in Webmail and in your email client, but email you send will be queued on other servers until the server is brought back online.
No email will be lost or rejected during this routine operation, which should only last a few minutes.
Earlier this year you will remember that we moved the servers that handle your email to a new data center. At the same time we partnered with a new systems management partner (Copyleft Solutions) and have spent some time since then getting used to working together and getting all the documentation and routines in order.
We have now started a maintenance phase where we will perform various behind the scenes configuration improvements and minor upgrades. This will make the systems easier to maintain, improve service snappiness and lay the foundation for future development of our services.
The maintenance phase will last approximately 2 months, and to allow for the flexibility needed during this phase we are likely to schedule minor downtimes with relatively short notice.
We will try to give at least 2 days notice on our website, and on each occasion the downtime is expected to be less than 15 minutes.
We understand that service disruption can be a problem, but will be grateful for your patience while we work to make Runbox a better and more responsive service.
Today we added a sent messages meter in the Webmail. If you see any issues, then please let us know either by adding a comment or opening a Support Ticket.
Here are some pictures from the move showing our old and new Data Center, our servers, and some of our sysadmins.
All in all the process involved around 2 weeks of planning, 10 people, 3 cars, a few hundred feet of cable, 10 hours of deracking, driving, and installing, and a week cleaning up afterwards.
It’s good to know that Perdita, Pongo, Patch, Penny, Pepper, Taishi, Rambo, Takara, Tinkerbell, Chernushka, Strelka, Bars, Pink, Oscar, Fenris, Greyhound, Odie, Marmaduke, and Sirius are all running smoothly in their new pound!
We have been busy cleaning up after yesterday’s big (and long) move and want to thank everyone for your patience while we got everything running the way it should.
Currently the status is:
- Webmail, POP, IMAP, and SMTP should be working normally for all users since we located and corrected a proxy problem this afternoon (which was actually introduced before we moved and had to do with the format of distributed authentication files).
- All email that was queued during the transition has been delivered to their respective accounts.
- We have some issues with messages sent from the Webmail that we’re investigating.
- We still have some timeouts on FTP that we’re working on.
Our new sysadmin team is already hard at work making the service more reliable, and once we have all the support systems and routines in place across our organizations we will work more efficiently together.