Drew Tomlinson wrote:
> > >The simplest thing to do is to encapsulate the original message
> > >as attachment to a new message.
> >
> > yes, this should work too.
>
> But wouldn't this make all my email appear to come from me and I'd
> have to go into each email to see the original email?
Yes. That is exactly correct. Because the mail *is* actually coming
from your forwarding server. And strict DMARC configurations
intentionally breaks forwarding. Therefore we can only re-send the
message from our forwarding servers.
[[Note that I am not a fan of a strict DMARC policy. I think that
should be reserved for banks.]]
> This doesn't seem very practical.
And yet it is the world of Gmail and Yahoo and others. If you want to
forward mail to Gmail then the mail will need to conform to the
*sending* site's DMARC policy. Google and Yahoo are simply following
the direction of the sending site.
> As it is, most forwarded email is making it to my gmail account.
Because most of your mail is not setting a strict DMARC policy. My
message here for example will have no trouble. Since I do not set a
strict DMARC policy.
But the status you quoted looked to me to be bounced due to content
filtering. Google decided that the content of the message was spam
and rejected it. Your forwarding server was the one connecting to
Gmail and therefore received the bounce as it was rejected at SMTP
time.
550-5.7.1 [40.78.46.245 12] Our system has detected that this message
is
550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to
Gmail,
550-5.7.1 this message has been blocked. Please visit
550-5.7.1 https://support.google.com/mail/?p=UnsolicitedMessageError
550 5.7.1 for more information. ch21si108253pjb.156 - gsmtp (in reply to
end of DATA command))
I think it is more likely that you received some spam to your first
address. This spam was forwarded along to Gmail. Gmail rejected it
at SMTP time due to content analysis filtering. Google does content
analysis on all free email accounts.
Although SPF and DMARC are problems for simple forwarding it is also a
problem to have spam forwarded due to content filtering too. And
there are many ways for things to go wrong.
The difference in anti-spam filters where an upstream receiver accepts
a message and then a later filter rejects the message is a fundamental
problem with a forwarding pipeline. Encapsulating a message is a way
to avoid the downstream filter rejection after an upstream has
accepted it.
> If changing the Mail From will help further, it seems that would be
> the best overall solution for me. I'm looking for a solution that
> keeps me from having to build my own IMAP server and web front end
> that works most of the time.
>
> I'm open for suggestions for this novice user... ;)
Frankly IMNHO if you want to read mail at Gmail then you should
arrange for Gmail to host the email for your domain directly. (Set MX
records for your domain pointing to Google.) Then there will be no
forwarding. Mail will go to Gmail directly. Configure Gmail to send
mail from your domain so you can reply. Google will be the gatekeeper
for your email left, right, and center. As I understand it this is
not a free service however and you would need to pay Google for it.
Bob
