From: Brent Bice <bbice@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Shyam Kaushik <shyam@zadarastorage.com>,
Alex Lyakas <alex@zadarastorage.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH 4/5] xfs: xfs_inode_free() isn't RCU safe
Date: Tue, 12 Apr 2016 15:55:07 -0600 [thread overview]
Message-ID: <570D6EBB.1010805@sgi.com> (raw)
In-Reply-To: <20160412211148.GJ567@dastard>
On 04/12/2016 03:11 PM, Dave Chinner wrote:
> It seems that sgi.com is rejecting quite a bit of legitimate mail
> lately. I've seen a couple of people in the past couple of weeks
> send stuff that has reached my private in boxes but not the list.
> Now this one, too.
Yeah, this one wasn't the anti-spam filters that I manage (the
barracudas, our private RBL, etc) but spamassassin on oss.sgi.com.
So... Dunno. I took a crack at whitelisting Alex's from address in
spamassassin (though I haven't looked at it's configs or man pages in
about 10 years).
> If someone is having to micro-manage the list to prevent rejections
> of valid email then that is bad...
So true. I only happened to notice because I had someone (I forget who
it was several years ago) tweak SA on oss so that rejections get
forwarded to me. The idea was I'd look at those (stuff that the cudas
missed but spamassassin caught) and use that info to update our filters
(the filters that benefit everyone at SGI, not just oss).
Anyway, I don't always have the bandwidth to look at every email SA
on oss rejects and update spam filters (if possible) and just happened
to notice this one and that it wasn't spam.
I am a lot more aggressive with the filters for oss because it's
such a sore-thumb-target for spammers. For instance, there are large
swaths of yahoo IP space being blocked now (for oss only) because over
the years I only found one legit sender to oss from a yahoo IP - the
rest was all spam/phish. But I've only dropped in yahoo IP ranges that
I was seeing spam from. I've gotten aggressive with some Chinese IP
space too for similar reasons. If any of the senders you know of having
trouble might be in yahoo or chinese IP space let me know and I can look
in the logs, but I'd bet a doughnut that if they didn't get a bounce
then they're running afoul of spamassassin 'n not the filters I manage. :-(
There was talk a while back of taking oss out of SGI and hosting it
somewhere in "Da cloud!" (tm) and having someone else in the xfs
community own it, wasn't there? Anyone still looking into that?
Brent
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-12 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 8:56 [PATCH 4/5] xfs: xfs_inode_free() isn't RCU safe Alex Lyakas
2016-04-12 11:29 ` Brent Bice
2016-04-12 21:11 ` Dave Chinner
2016-04-12 21:55 ` Brent Bice [this message]
2016-04-12 23:29 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2016-04-12 8:55 Alex Lyakas
2016-04-06 9:22 [PATCH 0/5] xfs; xfs_iflush_cluster vs xfs_reclaim_inode Dave Chinner
2016-04-06 9:22 ` [PATCH 4/5] xfs: xfs_inode_free() isn't RCU safe Dave Chinner
2016-04-07 15:50 ` Christoph Hellwig
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=570D6EBB.1010805@sgi.com \
--to=bbice@sgi.com \
--cc=alex@zadarastorage.com \
--cc=david@fromorbit.com \
--cc=shyam@zadarastorage.com \
--cc=xfs@oss.sgi.com \
/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