ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] If you are using gmail, check your spam folders
Date: Thu, 05 Jun 2014 07:21:29 -0700	[thread overview]
Message-ID: <1401978089.2207.14.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20140604130646.GA25092@thunk.org>

On Wed, 2014-06-04 at 09:06 -0400, Theodore Ts'o wrote:
> Hi,
> 
> The first round of invites for the kernel summit was sent out over the
> weekend.
> 
> 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.)
> 
> Sigh.  Maybe there's some Nigerian scam involving inviting people to
> Kernel Summits, or some such.  :-(
> 
> 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.

I don't know if it helps, but my pull requests used to end up in Linus
spam folder on gmail before he added a specific whitelist for me.  I've
not really had trouble with other peoples' gmail addresses (that I know
of).

There are a lot of stupid spam filters out there.  The parallels one is
exchange based and it seems to classify a lot of open source related
stuff as spam (mostly patches), which is why I mostly miss things if
they don't go to the right mailing lists (I keep all my mailing list
subscriptions on hansenpartnership.com which uses spamassassin and
greylisting).

I did discover a while ago that lots of companies selling "spam"
services are completely unreliable.  Novell used to use one (forget
which) for groupwise.  It had a "this is spam" tag on the netblock of
the colo the hansenpartnership.com server was located in, however, none
of their removal procedures actually worked ... not even contacting the
company directly from a novell.com email worked ... they were only
interested in collecting money for providing a dubious service, not
actually in improving their service ...

The problem with these private services is that it's very hard to tell
if you're listed (I had to get the novell admin to diagnose) and it's
impossible to get removed if you do.  Ted you might like to check if
google has any inputs other than the ones
http://mxtoolbox.com/blacklists.aspx knows about.

James

      parent reply	other threads:[~2014-06-05 14:21 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
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 [this message]

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=1401978089.2207.14.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox