On Monday, 4 September 2017 between 11:00 and 12:00 UTC, we will perform maintenance on our Control Panel.
During this time, the Control Panel and API will be temporarily unavailable. We apologize in advance for the inconvenience. Should you have any questions about this maintenance, feel free to open a support ticket and our support team will be happy to help.
2017-09-04 12:01 UTC: We are starting the maintenance.
2017-09-04 13:49 UTC: The maintenance is now over. Thank you for your patience, and if there are any issues please feel free to contact support by opening a ticket.
2017-08-12 04:27 UTC: Users with email mailboxes on Mailbox8 and Mailbox9 servers may encounter intermittent authentication failures. Please stand by for further updates.
2017-08-16 22:54 UTC: We’ve determined that this issue is related to an ongoing migration of mailboxes to new hardware. We’re continuing to troubleshoot.
2017-08-28 22:55 UTC: A permission problem related to the ongoing mailbox migrations is currently causing IMAP/POP login failure. We’re fixing the permissions at this time and will update this post when complete.
2017-08-28 23:42 UTC: The permission problem has been resolved, and IMAP/POP authentication should be working normally at this time. We’ll continue to monitor.
2017-08-30 21:53 UTC: We’re still seeing intermittent IMAP/POP authentication failures related to the ongoing mailbox migrations. This also affects webmail logins. Any failures should be temporary – if they don’t seem resolved within a few minutes, then please contact WebFaction support for further assistance.
2017-09-07 18:45 UTC: We’ve updated our migration process to minimize its impact on the IMAP/POP service, and are no longer seeing intermittent IMAP/POP authentication issues.
Effective on 1 September 2017, our SMTP server will reject any outgoing message that uses a sender address in the form of “email@example.com” (for example, “firstname.lastname@example.org”).
This change primarily affects customers who are using sendmail (including the PHP mail() function) to send messages without explicitly setting a sender address.
If you’re not sure if you will be affected by this change, then send yourself a message from the potentially-affected website, script, or other application, and then inspect the headers of the received message to ensure that the “From” header is a valid address not in the form of “email@example.com”, and does not use any of the domains listed in our email limitations and restrictions.
If you have any questions or concerns regarring this change, please open a support ticket and our team will be happy to assist.
2017-09-01 17:09 UTC: The new restrictions are now in effect.
2017-09-17 18:24 UTC: This change was disrupting outgoing email for several customers’ WordPress sites, so we’ve rolled it back and will re-deploy when that issue has been resolved.