From mboxrd@z Thu Jan  1 00:00:00 1970
From: pshah.mumbai@gmail.com (Prashant Shah)
Date: Wed, 29 Jun 2011 19:58:52 +0530
Subject: Gmail complaining about authenticity of emails sent/received via
	kernelnewbies
In-Reply-To: <4E0B1E56.7090602@surriel.com>
References: <BANLkTinSLR-h1FhVX8HGp6MPaTm+yGp5Mg@mail.gmail.com>
	<BANLkTi=D0wrpdDs1F3i=64SYuYkWMnyEdg@mail.gmail.com>
	<BANLkTinp6F9_AYwj0SpUgS_pXX4GRAz+Rw@mail.gmail.com>
	<4E0B1E56.7090602@surriel.com>
Message-ID: <BANLkTimgkfm5-LcS5EbKzxAjmsDX_=kF2g@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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.