From: Theodore Ts'o <tytso@mit.edu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] If you are using gmail, check your spam folders
Date: Wed, 4 Jun 2014 12:52:24 -0400 [thread overview]
Message-ID: <20140604165224.GA3127@thunk.org> (raw)
In-Reply-To: <538F46CA.70303@infradead.org>
On Wed, Jun 04, 2014 at 09:18:18AM -0700, Randy Dunlap wrote:
>
> 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.
Are you getting outright rejects, or is it ending up in Linus's spam
folder? (Which has happened to me with a PULL request, which is why I
set up DKIM....)
In any case, if you get outright rejects, if you can save the full
e-mail (including headers) in a file, and then put it somewhere I can
download it, I'd much appreciate it. (I've been having false
positives with MIT's Brightmail anti-spam service, so this problem is,
alas, not unique to Gmail. So if you want to send me samples which
Gmail has rejected as spam, it's better to put it up on a web or ftp
server, and send me the URL.)
If it ends up in a gmail spam folder, it's best if you can get the
recipient to send me the full e-mail, complete with headers.
The reason why the headers are useful is because we can use these to
hopefully send complaints to the anti-SPAM folks and ask them what's
up with their algorithms. For example, this was bounced by Gmail
despite the SPF and DKIM pass indications:
Received: from imap.thunk.org (imap.thunk.org. [2600:3c02::f03c:91ff:fe96:be03])
by mx.google.com with ESMTPS id m48si15663526yhl.39.2014.05.31.13.16.22
for <gregkh@linuxfoundation.org>
(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
Sat, 31 May 2014 13:16:22 -0700 (PDT)
Received-SPF: pass (google.com: domain of tytso@thunk.org designates 2600:3c02::f03c:91ff:fe96:be03 as permitted sender) client-ip=2600:3c02::f03c:91ff:fe96:be03;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of tytso@thunk.org designates 2600:3c02::f03c:91ff:fe96:be03 as permitted sender) smtp.mail=tytso@thunk.org;
dkim=pass header.i=@thunk.org
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb;
h=Date:Message-Id:To:Reply-To:Subject:From; bh=EYhTkkgyOXFA9DVUyhv3DV8emZh08SW9NRYmxy6b18s=;
b=XWykrAMWFJTkNFUb4AW2VrdrBu+45vDXNJQqcpADZcb8waUpl02GGfpFQ1qqJ7x6h4kHuB04ah3/7QcINWs1GEByE2Hy35ID/cTTlUtFg9pOEjqbIgoWnfeoKRbp6ZpdxZlK0o6McJcmIJOJN492fVk1UGXnKWR//r5X6RDbuNM=;
- Ted
next prev parent reply other threads:[~2014-06-04 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:06 Theodore Ts'o
2014-06-04 16:18 ` Randy Dunlap
2014-06-04 16:52 ` Theodore Ts'o [this message]
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=20140604165224.GA3127@thunk.org \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=rdunlap@infradead.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