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:
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.
Server Relocation and Email Downtime – Tuesday June 14 10-14 CET (08-12 GMT / 05-09 AM EDT / 02-06 AM PDT)
We’re excited to announce that Runbox is partnering with a new server hosting and management company, Copyleft Solutions. As part of this change we will move our email server park to a new Data Center on Tuesday June 14 between approximately 10 and 14 CET.
How will this affect me?
Our email services, including Webmail, POP, IMAP, and SMTP, will be inaccessible for about 4 hours while the servers are being moved. Incoming email will normally be queued on the sending servers, but users of mailing list services such as Yahoo Groups might want to suspend those to avoid bouncing of incoming email.
The Runbox Web Hosting services will *not* be affected as they are hosted in a different location. All web sites and domains hosted with Runbox will continue to work normally.
We apologize for any inconvenience caused by the relocation.
What can I do?
We recommend that you check your email before the scheduled downtime. While we are migrating it will not be possible for you to access your email.
You will not need to change any settings in your email client. It will work normally once our servers are online again.
(For those who have been using our IP address (126.96.36.199) instead of a regular server name, please change this to 188.8.131.52.)
If you have any questions, please use the Support Center at http://support.runbox.com
Why are you relocating?
Runbox is partnering with Copyleft Solutions, a Norwegian company focusing on secure hosting and open source software. Copyleft Solutions shares Runbox’ values and core principles, and we will be their preferred email provider going forward.
The partnership will strengthen both companies in the long-term as we also share many goals and interests — first and foremost to provide the best possible email services for our users.
The new Data Center
The Runbox email server park will be moved to Copyleft Solution’s data center at Digiplex. Digiplex offers state of the art facilities with secure, climate controlled environments and full power and telecom redundancy.
In the future, this move will improve the quality and responsiveness of our services, as the servers will be hosted on a higher capacity network by a company committed to further developing the platform.
We will do some scheduled downtime today at 12:00 CET. We estimate that we will be back up again 30 minutes later.
We’ve had reports about falsified messages purporting to be official, requesting that the recipient reply with their username and password.
The subject of the message is reported to be “E-Mail Account Maintenance Runbox Webmail” and the sender might be a Gmail address.
If you see such a message, please delete it.
Note that Runbox will never ask you for your username or password in an email, and we will address you with your full name (which a phisher/scammer would not be able to).
We’ve received reports about a phishing email impersonating Runbox Support and trying to trick people into logging into their account from a fake mockup of the Runbox login page. The purpose of this is to steal user logins in order to send Nigerian-type scammer mails from the hijacked accounts.
The fake sender address of the message is email@example.com and the subject is You have 1 new Alert Message !. We have put in place a global filter to reject further messages of this sort, and are currently deleting all instances of it from the Runbox servers. If you still should have received the message, please just delete it.
The phishing site linked to in the message is now blocked in most browsers, but if you tried to log in from it earlier, please change your password immediately using the Account screen after logging in at www.runbox.com, and contact us afterwards.
As a general rule, always make sure you’re logging in at a official Runbox website (www.runbox.com). Please see the Phishing section of this article for more information.
For unclear reasons, Runbox’ outgoing IP address has been listed by Symantec, and some mail servers which use their blacklist are therefore bouncing mails from Runbox. We are awaiting delisting at the moment.
After tuning the memory configuration of the main database server we have seen a significant improvement in performance that will hopefully be noticeable especially in Webmail.
For the technically inclined, decreasing the limit MySQL may use for memory swapping can have a positive effect on large databases.