Gmail will think itâs all coming from your mail server. And theyâre likely to mark that server as a source of spam.
They are, and that exacerbates the problem I noted above.
I see this too in my hosting setups, and itâs related to the spam issue above.
Think about this from Googleâs point of view.
Say you have a hosting server with an account that gets 50 emails per day. Letâs say 30 of them are spam. Your hosting server sees that it got 50 different emails from 50 different sources, and it can theoretically look for a pattern across all the accounts on the server to block senders and manage spam.
But now you set up a forward and send those emails to Google. Since your hosting server is now the âsourceâ of the email, Google sees a server sending 50 messages per day, over half of which are spam. So it just blocks the server entirely, because your server is sending 60% spam.
Iâve had this happen to me and my customers. Google doesnât care that youâre forwarding the email at the request of the customer. They care that your server is the source of spam. If youâre really, really lucky, theyâll tell you so that you can address the issue. If youâre not lucky, theyâll accept the email as if nothing is wrong, and just silently throw it away behind the scenes.
Incidentally, this service isnât subject to the problems above because itâs not forwarding. At least not in the conventional sense. It looks to be pulling your email in POP, and then using the Gmail API to manually add the message to your inbox. Kind of (but not exactly) like if you set up your POP account and your Gmail account in Apple Mail, and dragged messages from one account to the other.
Which, incidentally, is a solution if you have mail software that supports it. For me, I have MailMate. It takes the emails that come into one account and moves all of them to my âmainâ account. No âforwardingâ necessary.