forwardemail / status.forwardemail.net Goto Github PK

We are immediately scaling infrastructure for our IMAP servers to support increased demand.

Service should be restored within 5 minutes.

Our IP addresses are being intermittently blocked by Yahoo Postmaster.

We have escalated another support request to them (in addition to 3+ we've already filed) and are taking additional action to attempt to alleviate the issue as soon as possible.

Thank you.

We are aware that some users are experiencing issues logging in (super rare) - it appears due to a caching/build of client-side assets. This is being actively resolved now.

Since approximately 2 PM CT there have been intermittent delays with email forwarding. We are investigating and will follow up ASAP with resolution.

We are sustaining a consistent DDOS in our San Jose, CA region (for web/API servers).

Our Cloudflare load balancer is redirecting traffic to the failover servers successfully.

Please contact us if you experience any issues 🖖

We are aware of some senders/recipients having forwarding delays right now. Investigating now and will follow up shortly once resolved.

IMAP service has been restored after an outage this morning. We have resolved the underlying issues and mail should flow through shortly.

Hi folks 👋

We became alerted over the past 24 hours by our customers that use our service in combination with Gmail's send mail as feature. Specifically if you send an email from Gmail using the free send mail as feature (not with our SMTP server), then your emails to AOL/Yahoo/Verizon/Rocketmail will bounce with the following message:

550 5.7.9 This mail has been blocked because the sender is unauthenticated. Yahoo requires all senders to authenticate with either SPF or DKIM.

Discussion is at https://support.google.com/mail/thread/272163711/yahoo-and-aol-emails-are-blocked?hl=en.

To fix this issue, you will need to setup DKIM on your domain (on our unlimited $3/mo plan). This change was not from us, but by Yahoo Postmaster – and it may be a bug – but in the interim you could use our outbound SMTP server as a workaround.

We will leave this issue open for ~48 hours to give users notice.

Thank you,