Instead, the problem is a combination of issues at the original sending end and the Gmail end. If you’ve added a mailbox for on our servers, you’ll find the message was properly delivered there (you can use Webmail to check that if you’re not already reading it another way). If this happens, it’s important to keep in mind that the problem is not with the address. Our system returns the forwarded message back to because it can’t be delivered to Gmail.Our system sends a second forwarded copy to Gmail rejects the forwarded message because they think it might be spam and it doesn’t have a DKIM signature and.

Our system accepts the message from to anyway, because our filters don’t think it’s spam.sends a message to The message from does not have a DKIM signature.

Why does this happen when forwarding messages to Gmail?Īs an example, let’s say you set up to forward incoming mail to see this problem if: But it can still happen if you forward messages from other addresses to Gmail. Our servers always add DKIM signatures for messages you send, so you probably won’t experience this when you send messages to Gmail from your address with us. (DKIM signatures make messages less likely to be wrongly treated as spam.) If this happens to you, it means Gmail thinks the message might be spam for some reason, and they won’t accept it unless the original sending server uses what’s called a DKIM signature to send it.

To best protect our users from spam, the message has been blocked. This message does not pass authentication checks (SPF and DKIM both do not pass).

Server email bounce back message gmail