Gmail complaining about authenticity of emails sent/received via kernelnewbies
Hi All, I'm using gmail.com for corresponding to this mailing list. Recently I have observed that gmail has started complaining about the authenticity of the sender. Eg: I see this message quite often when someone replies to a kernewbies post: This message may not have been sent by: xyz@gmail.com Is anyone else seeing this too? I think mailing lists set a "via" (or some such) header in the mail to indicate that the mail is being sent on behalf of the original sender. Could that be missing? -mandeep
On Wed, Jun 29, 2011 at 16:48, Mandeep Sandhu <mandeepsandhu.chd@gmail.com> wrote:
Hi All,
I'm using gmail.com for corresponding to this mailing list.
Recently I have observed that gmail has started complaining about the authenticity of the sender.
same thing here....I guess, there is a header mangling somewhere done by the mailing list program? -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
On Wed, Jun 29, 2011 at 4:30 PM, Mandeep Sandhu <mandeepsandhu.chd@gmail.com> wrote:
same thing here....I guess, there is a header mangling somewhere done by the mailing list program?
Here's a google link explaining 'via' header: http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=1311182 This also seems to be a recent addition to gmail. So I'm not sure if anything has changed on the kernelnewbiews mail server end. This warning might be a result og gmail rolling out this new header check. HTH, -mandeep
Hi all On Wed, Jun 29, 2011 at 18:04, Mandeep Sandhu <mandeepsandhu.chd@gmail.com> wrote:
This also seems to be a recent addition to gmail. So I'm not sure if anything has changed on the kernelnewbiews mail server end. This warning might be a result og gmail rolling out this new header check.
yeah, looks like gmail puts few new stuffs quite recently, like a new "people involved in discussion" we see right of message pan. OK, we need to tell Rik van Riel ... RIk, hope you notice this man.... -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
On 06/29/2011 07:00 AM, Mandeep Sandhu wrote:
same thing here....I guess, there is a header mangling somewhere done by the mailing list program?
Yup. Looks like some settings changed on the kernelnewbies mail server.
I did not make any configuration changes on this side in the past few months. The last update to the mailman package is from February, so a software update isn't the problem, either. Did Gmail make changes perhaps? -- All rights reversed.
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.
On 06/29/2011 10:28 AM, Prashant Shah wrote:
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.
You've got to be kidding me. SPF is fundamentally flawed in so many ways, noone should be recommending it in this day and age. -- All rights reversed.
Hi Rik... Long time no chat :) On Wed, Jun 29, 2011 at 21:37, Rik van Riel <riel@surriel.com> wrote:
You've got to be kidding me.
SPF is fundamentally flawed in so many ways, noone should be recommending it in this day and age.
So, what do you recommend about this issue? Should we just bear with it? -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
On 06/29/2011 01:19 PM, Mulyadi Santosa wrote:
Hi Rik...
Long time no chat :)
On Wed, Jun 29, 2011 at 21:37, Rik van Riel<riel@surriel.com> wrote:
You've got to be kidding me.
SPF is fundamentally flawed in so many ways, noone should be recommending it in this day and age.
So, what do you recommend about this issue? Should we just bear with it?
At some point I will upgrade kernelnewbies.org to a RHEL 6 virtual machine, with newer versions of everything. Right now I am very busy with other things though, so it'll be a few months before I get around to it... -- All rights reversed.
Hi list, I've looked on a couple of the other kernel mailing lists I'm following too and 'This message may not have been sent by:' is not appearing there, just the 'blah.com via mailinglist.org' thingie (even for .gmail.com addresses). Btw just to make sure .gmail.com mails on kernelnewbies haven't been peculiarly marked with strange metadata somewhere, I checked my kernelnewbies messages via Kmail and they're not, the 'warning' only appears when reading them using Gmail. I'm sure we can put up with it for a few months until Rik has time to upgrade, I for one am getting a bit inured to Gmail's ever-expanding collection of idiosyncrasies... :-/ Cheers Julie
Oh, and I just noticed that I can't see the 'This message may not have been sent by:' on the mail I just sent before - presumably because my Gmail account knows I'm me. Hooray. :-) Cheers Julie
On Thu, Jun 30, 2011 at 2:49 AM, julie Sullivan <kernelmail.jms@gmail.com> wrote:
Hi list,
I've looked on a couple of the other kernel mailing lists I'm following too and 'This message may not have been sent by:' is not appearing there, just the 'blah.com via mailinglist.org' thingie (even for .gmail.com addresses).
Btw just to make sure .gmail.com mails on kernelnewbies haven't been peculiarly marked with strange metadata somewhere, I checked my kernelnewbies messages via Kmail and they're not, the 'warning' only appears when reading them using Gmail.
I'm sure we can put up with it for a few months until Rik has time to upgrade, I for one am getting a bit inured to Gmail's ever-expanding collection of idiosyncrasies... :-/
Agreed. This is no biggie, as it's nothing more than a warning. -mandeep
On 29 June 2011 15:18, Mandeep Sandhu <mandeepsandhu.chd@gmail.com> wrote:
Hi All,
I'm using gmail.com for corresponding to this mailing list.
Recently I have observed that gmail has started complaining about the authenticity of the sender.
Eg: I see this message quite often when someone replies to a kernewbies post:
This message may not have been sent by: xyz@gmail.com
Is anyone else seeing this too?
I think mailing lists set a "via" (or some such) header in the mail to indicate that the mail is being sent on behalf of the original sender. Could that be missing?
Yes, I'm seeing this too. Seems like gmail introduced this particular feature(?) recently. The warning is technically correct, isn't it? You did not send this message to me - kernelnewbies did! Maybe they overlooked (or don't care about) the fact that mailing lists broadcast messages on behalf of the original sender. Or maybe something will have to change in the way the kernelnewbies mailing list sends out its messages. Regards, Felix.
Yes, I'm seeing this too. Seems like gmail introduced this particular feature(?) recently. The warning is technically correct, isn't it? You
Yes. Gmail seems to be doing the right thing.
overlooked (or don't care about) the fact that mailing lists broadcast messages on behalf of the original sender. Or maybe something will
I think Gmail is pretty 'mailing list' aware. I have filters specifically for mailing list (like this). Looks like the kernelnewbies list is not adding the 'via' header to the mails (I don't know the correct 'technical name for it :)) Maybe the list admin can throw some light on this issue? -mandeep
participants (6)
-
Felix Varghese -
julie Sullivan -
Mandeep Sandhu -
Mulyadi Santosa -
Prashant Shah -
Rik van Riel