Daniele Nicolodi:
> >>> Maybe this helps:
> >>>
> >>> Go to your Mail settings and Accounts tab and add the address
> >>> you are forwarding from to 'Send mail as'. This is a new feature
> >>> from user requests, where Gmail will detect that you forwarded
> >>> from that account and help prevent displaying a phishing warning.
> >>>
> >>> https://support.google.com/a/answer/175365?hl=en
> >>
> >> Hello Wietse,
> >>
> >> thanks for your reply. However, this is not the problem.
> >>
> >> Maybe I was not clear in my explanation: I'm nor trying to forward
> >
> > You did not try it. Good for you.
>
> Hello Wietse,
>
> I may have dismissed what you proposed a bit too quickly but I don't
> really understand how setting this option for a test account will affect
> my ability to send email to other Gmail accounts.
Based on this:
"Currently I'm able to send emails to my address @gmail.com
from the email address I'm currently using without having them
classified as spam, but not from any email address having a
different local part."
The problem is that different accounts in your domain receive
different treatments, when they send mail to one Gmail account.
I didn't read that as a problem sending mail to different Gmail
accounts.
> Do you have empirical evidence of this setting somehow influencing the
> reputation of a domain as seen by the Google infrastructure?
No, but I have empirical evidence that Google documentation should
sometimes not be taken too literally (disclosure: I work there).
That said, perhaps I should not have taken your question too
literally, either. What started as a problem with different senders
in your domain sending mail to one Gmail recipient, has become a
problem with sending mail to different Gmail recipients.
With the Google pointer one can tell Gmail to treat some addresses
as "equivalent". I don't know if it works only when those different
addresses are used as a recipient (as when mail is forwarded), or
if it also applies when those different addresses are used as a
sender (as in your original question). That's the part about taking
documentation not too literally.
In any case, I agree that you need to clean up your DNS, so that
the Received: header shows zed.grinta.net as the sending host, not
grinta.net.
Definitely:
grinta.net. IN MX pref zed.grinta.net.
zed.grinta.net. IN A 109.74.203.128
128.203.74.109.in-addr.arpa. IN PTR zed.grinta.net.
Maybe:
grinta.net. IN A 109.74.203.128
Not:
128.203.74.109.in-addr.arpa. IN PTR grinta.net.
Wietse
