From: Randy Dunlap <rdunlap@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] If you are using gmail, check your spam folders
Date: Wed, 04 Jun 2014 09:18:18 -0700 [thread overview]
Message-ID: <538F46CA.70303@infradead.org> (raw)
In-Reply-To: <20140604130646.GA25092@thunk.org>
On 06/04/2014 06:06 AM, Theodore Ts'o wrote:
> Hi,
>
> Unfortunately, it's come to my attention that at least two people who
> are using GMail had their invites trapped as spam. This is despite
> the fact that I went to careful lengths to make sure that the
> invitation passed both SPF and DKIM checks. A forwarded message from
> Greg K-H from his Gmail spam folder confirmed that whatever got
> GMail's anti-spam filters upset, it wasn't SPF or DKIM. (The From
> address was tytso@thunk.org, specifically so the SPF would pass, and
> so the SPF identity would == the DKIM identity.)
I often get rejects from gmail when I reply to email and one of the
Cc:s is torvalds@, akpm@, or gregkh@ linux-foundation.org (which is
using gmail). It's all bogus AFAIK. It's just Linux patch-related stuff.
> I'm trying to investigate this internally inside Google, but in the
> meantime, if you are using Gmail as your mail reader, plesae check
> your spam filters. I apologize in advance for the inconvenience.
Good. Hope that works for you.
--
~Randy
next prev parent reply other threads:[~2014-06-04 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:06 [Ksummit-discuss] If you are using gmail, check your spam folders Theodore Ts'o
2014-06-04 16:18 ` Randy Dunlap [this message]
2014-06-04 16:52 ` Theodore Ts'o
2014-06-05 4:11 ` Randy Dunlap
2014-06-05 4:40 ` Greg KH
2014-06-05 12:33 ` Theodore Ts'o
2014-06-05 13:26 ` David Woodhouse
2014-06-05 17:12 ` Randy Dunlap
2014-06-07 20:42 ` David Woodhouse
2014-06-05 14:21 ` James Bottomley
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=538F46CA.70303@infradead.org \
--to=rdunlap@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.