From: Benjamin LaHaise <bcrl@kvack.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christopher Lameter <cl@linux.com>,
Randy Dunlap <rdunlap@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>,
akpm@linux-foundation.org, Mel Gorman <mel@skynet.ie>,
andi@firstfloor.org, Rik van Riel <riel@redhat.com>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC 0/8] Xarray object migration V1
Date: Thu, 28 Dec 2017 15:33:52 -0500 [thread overview]
Message-ID: <20171228203352.GP24310@kvack.org> (raw)
In-Reply-To: <1514491258.3040.28.camel@HansenPartnership.com>
On Thu, Dec 28, 2017 at 12:00:58PM -0800, James Bottomley wrote:
...
> > The list is not hosted on Google - Google's anti-spam service is only
> > used for ingress filtering.
>
> OK, but that is the problem: you're relying on google infrastructure
> for a service it does incredibly poorly.
I did say that I am open to changing how spam filtering is done.
> > Spamassassin is not a "Good Enough" option these days given the
> > volume and nature of spam that comes into kvack.org. If you can
> > point me at a better anti-spam solution that actually works (and is
> > not RBL based), I'd be happy to try it since the Google service is
> > absolutely awful with pretty much no way to get a human to fix
> > obviously broken things.
>
> Well, to be honest, I find spamassassin to be incredibly useful (it's
> what I use), especially being rules and points based instead of
> absolute (meaning I can use the RBL but not rely on it). It hasn't
> given me a false positive on anything for over a year and its false
> negative rate is about 2% with my current configuration.
False negative rate last time I used spam assassin was way more than
10-15%, and it mostly failed to filter out the phishing scams which tend
to be the bigger problem of late. That isn't so much of a mailing list
concern, but it is a significant issue for user accounts.
> However, I think the best solution is to use vger ... it already has an
> efficient ingress filter and it doesn't rely on google, so it doesn't
> suffer the arbitrary mail loss problem of google.
This is the first time anyone has complained to me about messages being
filtered in a number of years, and I have added whitelists for people over
the years that had problems ending up on various blacklists. I don't have
time these days to actively scan mailing lists for issues, so reporting
them on-list without directly Cc'ing me will not get my attention. I'll
look into options over the next few days and see if there are any better
solutions available now than the last time I looked at the spam problem.
Please give me at least a little a bit of time to look into possible fixes
before going nuclear.
-ben
> James
>
>
--
"Thought is the essence of where you are now."
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-28 20:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 22:06 Christoph Lameter
2017-12-27 22:06 ` [RFC 2/8] slub: Add defrag_ratio field and sysfs support Christoph Lameter
2017-12-30 6:20 ` Matthew Wilcox
2018-01-02 14:53 ` Christopher Lameter
2017-12-27 22:06 ` [RFC 3/8] slub: Add isolate() and migrate() methods Christoph Lameter
2017-12-30 6:42 ` Matthew Wilcox
2018-01-01 21:20 ` Matthew Wilcox
2018-01-02 14:56 ` Christopher Lameter
2018-01-02 14:55 ` Christopher Lameter
2017-12-27 22:06 ` [RFC 4/8] slub: Sort slab cache list and establish maximum objects for defrag slabs Christoph Lameter
2017-12-27 22:06 ` [RFC 5/8] slub: Slab defrag core Christoph Lameter
2017-12-27 22:06 ` [RFC 6/8] slub: Extend slabinfo to support -D and -F options Christoph Lameter
2017-12-27 22:06 ` [RFC 7/8] xarray: Implement migration function for objects Christoph Lameter
2017-12-27 22:06 ` [RFC 8/8] Add debugging output Christoph Lameter
2017-12-28 5:19 ` [RFC 0/8] Xarray object migration V1 Randy Dunlap
2017-12-28 14:57 ` Christopher Lameter
2017-12-28 17:18 ` James Bottomley
2017-12-28 17:33 ` Benjamin LaHaise
2017-12-28 17:40 ` James Bottomley
2017-12-28 19:17 ` Benjamin LaHaise
2017-12-28 20:00 ` James Bottomley
2017-12-28 20:33 ` Benjamin LaHaise [this message]
2017-12-28 22:24 ` Dave Chinner
2017-12-29 0:19 ` Christopher Lameter
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=20171228203352.GP24310@kvack.org \
--to=bcrl@kvack.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@infradead.org \
--cc=riel@redhat.com \
--cc=willy@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