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] The first round of kernel summit invites have gone out...
Date: Fri, 28 Aug 2015 10:48:10 -0700	[thread overview]
Message-ID: <1440784090.2202.40.camel@HansenPartnership.com> (raw)
In-Reply-To: <20150828173005.GA31345@thunk.org>

On Fri, 2015-08-28 at 13:30 -0400, Theodore Ts'o wrote:
> A number of program committee members have reported that their invites
> ended up in their SPAM folder.  My apologies; I've checked my DKIM and
> SPF settings, and they all look correct, but maybe some spam filter
> gone mad thinks invitations to technical conferences in Asia are
> automatically spam or something ridiculous like that.
> 
> So if you could, please check your spam folders.  We will be doing
> another round of invites next week, so if you haven't received an
> invite yet, please hold tight.  There were a large number of people to
> go through, and only a limited amount of time for the conference call.
> 
> If you have received an invite, and won't be able to attend, please
> let us know right away, so we can give someone else your spot.

Spamassassin is perfectly happy with the invitation email; this is what
I get:

X-spam-status:	No, score=-3.3 required=5.0
tests=AWL,BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD

So all the community filters work just fine and you get a low score.
The problem is that there seem to be a lot of snake oil commercial
companies out there that do really stupid things.  This is the worst
I've seen for my domain:

host fe-stp.mail.saunalahti.fi[62.142.5.93] said:
    554 5.7.1 <bedivere.hansenpartnership.com[66.63.167.143]>: Client host
    rejected: Too much foobar from 66.63.160.0/19 (in reply to RCPT TO command)

That basically means the entire service provider netblock is blacklisted
because someone bought a co-lo to send spam ... talk about group
punishments.  The problem is that companies trust services they pay for
(however unreliable the providers are) so as this creeps along we're
going to find large areas of the internet not accepting email from
people who don't send it from a large mail aggregator (like gmail)
because setting up a spam list based on extrapolation from a few reports
is a cheap thing to do.

James

  reply	other threads:[~2015-08-28 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 17:30 Theodore Ts'o
2015-08-28 17:48 ` James Bottomley [this message]
2015-08-28 18:17   ` Mark Brown

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=1440784090.2202.40.camel@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