From: pshah.mumbai@gmail.com (Prashant Shah)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Gmail complaining about authenticity of emails sent/received via kernelnewbies
Date: Wed, 29 Jun 2011 19:58:52 +0530 [thread overview]
Message-ID: <BANLkTimgkfm5-LcS5EbKzxAjmsDX_=kF2g@mail.gmail.com> (raw)
In-Reply-To: <4E0B1E56.7090602@surriel.com>
On Wed, Jun 29, 2011 at 6:15 PM, Rik van Riel <riel@surriel.com> wrote:
>
> Did Gmail make changes perhaps?
>
just a wild guess. maybe something related to SPF
http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=185812
I know that the message was really sent by the sender. What can I do?
Many small senders don't follow good sending practices and do not
provide authentication information. This can lead to incoming emails
being misclassified as spam, and it can also attract spammers who use
the sender's name to send out spam.
We recommend contacting the sender of the email and encouraging them
to authenticate their messages by publishing a SPF record.
SPF records should also be published in DNS as type SPF records.
next prev parent reply other threads:[~2011-06-29 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 9:48 Gmail complaining about authenticity of emails sent/received via kernelnewbies Mandeep Sandhu
2011-06-29 9:56 ` Mulyadi Santosa
2011-06-29 11:00 ` Mandeep Sandhu
2011-06-29 11:04 ` Mandeep Sandhu
2011-06-29 11:07 ` Mulyadi Santosa
2011-06-29 12:45 ` Rik van Riel
2011-06-29 14:28 ` Prashant Shah [this message]
2011-06-29 14:37 ` Rik van Riel
2011-06-29 17:19 ` Mulyadi Santosa
2011-06-29 18:42 ` Rik van Riel
2011-06-29 21:19 ` julie Sullivan
2011-06-29 21:25 ` julie Sullivan
2011-06-30 5:07 ` Mandeep Sandhu
2011-06-29 10:00 ` Felix Varghese
2011-06-29 10:59 ` Mandeep Sandhu
[not found] ` <BANLkTin=ZJk_U4JZWrOTUrpxM6HxsbMseQ@mail.gmail.com>
2011-06-29 11:50 ` Mandeep Sandhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTimgkfm5-LcS5EbKzxAjmsDX_=kF2g@mail.gmail.com' \
--to=pshah.mumbai@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).