Effective on 1 September 2017, our SMTP server will reject any outgoing message that uses a sender address in the form of “firstname.lastname@example.org” (for example, “email@example.com”).
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 “firstname.lastname@example.org”, 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-07-27 21:16 UTC: Microsoft is currently blocking and/or throttling mail sent via our SMTP to hotmail.com, outlook.com, msn.com, and other email domains hosted by Microsoft. We’re working with Microsoft to resolve this issue and will update this post when more information is available.
2017-08-02 18:02 UTC: We’ve set up some downstream SMTP relays to help with delivery while we continue to work to get the main SMTP IP address unblocked.
2017-08-03 16:54 UTC: Mail sent via our SMTP to hotmail.com, outlook.com, msn.com, and other email domains hosted by Microsoft is no longer being blocked or throttled. We’ll continue to monitor.
2017-07-25 22:21 UTC: a filesystem issue on one of our POP/IMAP proxies is disrupting mail service for some customers. We’re working to restore service and will update this post when more info is available.
2017-07-25 23:09 UTC: The faulty mail proxy is back online. We’ll continue to monitor.
2017-07-27 21:15 UTC: We’ve seen no further issues with the POP/IMAP proxies.
2017-06-20 20:44 UTC: A networking issue in one of our US data centers is affecting incoming mail service and webmail logins for some customers. We’re working to restore service and will update this post when more information is available.
2017-06-20 20:59 UTC: Service has been restored – we’ll continue to monitor.
2017-06-21 14:36 UTC: There have been no further disruptions, and the data center confirms that the networking issue is resolved.
2017-06-20 01:41 UTC: Web576 is currently offline due to a DDoS attack. We’re working to restore service and will update this post when more information is available.
2017-06-20 02:09 UTC: We’ve mitigated the attack upstream. The server appears to be stable, but the mitigation may affect UDP traffic. Please contact WebFaction support if you’re not able to access the server. We’ll continue to monitor.
2017-06-20 14:33 UTC: At the present time, Web576 is showing very high packet loss. We’re investigating at this time.
2017-06-20 17:48 UTC: Web576 is stable at this time. We’ll continue to monitor.
2017-06-21 14:37 UTC: The attack has resumed, and we’re working to mitigate it.
2017-06-21 18:21 UTC: We’ve possibly identified the intended target of the attack and have isolated them from other customers. The server is stable at this time and we’ll continue to monitor.
2017-06-22 18:23 UTC: The server has been stable for the past 24 hours. We’ll continue to monitor.
2017-06-25 15:23 UTC: The server has been stable for over 72 hours, and there has been no further sign of any attack.
2017-06-05 19:36 UTC: our control panel server is currently not responding. This also affects the control panel API and www.webfaction.com. We’re working to restore service and will update this post when more info is available.
2017-06-05 19:47 UTC: the panel, API, and www.webfaction.com are back online. We’re monitoring for further issues.