spam on this list

spam on this list

[Philip Edelbrock]

Sorry, I know the spam is a hassle.  It would be nice to have a 
moderator who can screen everything, but that takes too much time and 
delays emails.  Right now there is a procmail script which tags likely 
spam and puts in a X-SBClass: header.  If it is followed by 'Spam', then 
it is almost certainly spam, if it is followed by 'Blocked', then it 
scores high as being potential spam.  You should be able to set some 
rules in your mail client to throw those emails into a seperate folder.  
It's not bullet proof (some legit mails get tagged wrong, and vice 
versa), but it seems to be about 95% accurate in my experience.

BTW- If there are some recommendations on better alternatives, let me know.


Phil

Markus Schorer wrote:

>hi,
>
>being rather new here it seems to me that more spam is going 
>over this list than i2c related stuff.
>
>any chance of getting the spam excluded?
>
>regards,
>
>  
>

spam on this list

[Jean Delvare]

> Sorry, I know the spam is a hassle.  It would be nice to have a 
> moderator who can screen everything, but that takes too much time and 
> delays emails.  Right now there is a procmail script which tags likely
> 
> spam and puts in a X-SBClass: header.  If it is followed by 'Spam',
> then it is almost certainly spam, if it is followed by 'Blocked', then
> it scores high as being potential spam.  You should be able to set
> some rules in your mail client to throw those emails into a seperate
> folder.  It's not bullet proof (some legit mails get tagged wrong, and
> vice versa), but it seems to be about 95% accurate in my experience.
> 
> BTW- If there are some recommendations on better alternatives, let me
> know.

Actually, I tend to find that it works rather well. I have filtered on
X-SBClass = Blocked and, even if it rejects some legitimate posts, it
is generally efficient. I think that X-SBClass = Spam are already
rejected at higher level ? I don't remember seeing anything like this in
the mails I receive.

And, Markus, believe me, there is a lot less spam now that there used to
be ;) (but of course I'd like to see spam eradicated from Earth... what
times are we living now, seriously; looks to me like the middle-age of
Internet).

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

spam on this list

[Pierre Frenkiel]

I'm surprised to recieve  spams rather often from this list. I'm
subscribed to a big number of lists, and it's the only for which
this occurs. Would it be possible to refuse posts from non-members ?

best regards,
-- 
Pierre Frenkiel

Re: Spam on this list

[Dave Chinner]

On Wed, Aug 03, 2016 at 03:34:58PM +0200, Carlos E. R. wrote:
> On 2016-08-03 15:21, Martin Steigerwald wrote:
> 
> > Lista, Carlos, I recommend: If you are concerned about spam on the list 
> > contact the listmasters of it. They are the ones that can address it globally 
> > for the list.
> 
> Oh, I did, long ago. Still waiting.

Yes, that is the fundamental issue - spam filtering is essentially
controlled by SGI's internal infrastructure, which we have little
option on.

What it comes down to is whether we continue to use this list
(xfs@oss.sgi.com) or whether we move to linux-xfs@vger.kernel.org
so we get much more robust and up-to-date spam filtering. The issue
with doing this is forcing everyone to resubscribe, and then
capturing everything that is still sent to xfs@oss.sgi.com.

That said, I'm seriously tempted right now just to say "we're moving
to vger" and asking everyone to resubscribe to that list, and then
making xfs@oss.sgi.com respond with "list moved to vger, please
repost there". i.e. not even put a forwarding gateway in place.

If we do that, then I'll also shut down all the XFS git trees on
oss.sgi.com - I'll add commits to the them to say "go to
kernel.org". I'll need to work something out for the tarball
releases, but kernel.org does have functionality for that, too, so
that may just be a small change of process on my end (i.e. use kup).
Once that is done, we'll be running completely on community provided
infrastructure....

Thoughts?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Spam on this list

[Darrick J. Wong]

On Thu, Aug 04, 2016 at 09:15:29AM +1000, Dave Chinner wrote:
> On Wed, Aug 03, 2016 at 03:34:58PM +0200, Carlos E. R. wrote:
> > On 2016-08-03 15:21, Martin Steigerwald wrote:
> > 
> > > Lista, Carlos, I recommend: If you are concerned about spam on the list 
> > > contact the listmasters of it. They are the ones that can address it globally 
> > > for the list.
> > 
> > Oh, I did, long ago. Still waiting.
> 
> Yes, that is the fundamental issue - spam filtering is essentially
> controlled by SGI's internal infrastructure, which we have little
> option on.
> 
> What it comes down to is whether we continue to use this list
> (xfs@oss.sgi.com) or whether we move to linux-xfs@vger.kernel.org
> so we get much more robust and up-to-date spam filtering. The issue
> with doing this is forcing everyone to resubscribe, and then
> capturing everything that is still sent to xfs@oss.sgi.com.
> 
> That said, I'm seriously tempted right now just to say "we're moving
> to vger" and asking everyone to resubscribe to that list, and then
> making xfs@oss.sgi.com respond with "list moved to vger, please
> repost there". i.e. not even put a forwarding gateway in place.
> 
> If we do that, then I'll also shut down all the XFS git trees on
> oss.sgi.com - I'll add commits to the them to say "go to
> kernel.org". I'll need to work something out for the tarball
> releases, but kernel.org does have functionality for that, too, so
> that may just be a small change of process on my end (i.e. use kup).
> Once that is done, we'll be running completely on community provided
> infrastructure....
> 
> Thoughts?

YAY!

By the way, could we update the docs on
http://xfs.org/index.php/XFS_Papers_and_Documentation ?

The filesystem structure guide is a little out of date.

(The user guide probably is too, but as I've only been sending patches
for the disk format guide I'm keeping my mouth shut about the others.)

--D

> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Spam on this list

[Carlos E. R.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-08-04 01:15, Dave Chinner wrote:
> On Wed, Aug 03, 2016 at 03:34:58PM +0200, Carlos E. R. wrote:
>> On 2016-08-03 15:21, Martin Steigerwald wrote:

...

> Thoughts?

I have no objection to either staying or moving :-)

That is, I can live with the spam, and I can live with the move. You
do not need to care for people like me, we are just "users" ;-)

It is mostly the contributors you have to mind most.

I suppose that as log as you leave an autoresponder it will be Ok.

So go ahead when you wish :-)

- -- 
Cheers / Saludos,

		Carlos E. R.

  (from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAleikaMACgkQja8UbcUWM1x4AgD/b5NpxNS0O1LFuYAlBpdvMG7R
Ikr5YoxtNqLT9EcT8YQA/1O9P1p977AEOSlHxbxP3YMB4uEsea8p2PCaGINCUrKr
=OIsJ
-----END PGP SIGNATURE-----

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Spam on this list

[Lista Unx]

----- Original Message ----- 
From: "Dave Chinner" <david@fromorbit.com>
To: "Carlos E. R." <robin.listas@telefonica.net>
Cc: "XFS mail list" <xfs@oss.sgi.com>
Sent: Thursday, August 04, 2016 2:15 AM
Subject: Re: Spam on this list


> Yes, that is the fundamental issue - spam filtering is essentially
> controlled by SGI's internal infrastructure, which we have little
> option on.
>
> What it comes down to is whether we continue to use this list
> (xfs@oss.sgi.com) or whether we move to linux-xfs@vger.kernel.org
> so we get much more robust and up-to-date spam filtering. The issue
> with doing this is forcing everyone to resubscribe, and then
> capturing everything that is still sent to xfs@oss.sgi.com.
>
> That said, I'm seriously tempted right now just to say "we're moving
> to vger" and asking everyone to resubscribe to that list, and then
> making xfs@oss.sgi.com respond with "list moved to vger, please
> repost there". i.e. not even put a forwarding gateway in place.
>
> If we do that, then I'll also shut down all the XFS git trees on
> oss.sgi.com - I'll add commits to the them to say "go to
> kernel.org". I'll need to work something out for the tarball
> releases, but kernel.org does have functionality for that, too, so
> that may just be a small change of process on my end (i.e. use kup).
> Once that is done, we'll be running completely on community provided
> infrastructure....
>
> Thoughts?

I completely agree, is a good idea to move to a new place where more filters 
are already in place. It is a small change on user's side and benefits are 
for everyone. I cannot see any cons to not do it. It probably will be the 
best to keep also a message for newcommers and also for robots, that list 
has been moved to vger and new way to subscribe. 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

RE: Spam on this list

[Troy McCorkell]

On Wed, Aug 03,2016 at 6:15PM Dave Chinner wrote:
>On Wed, Aug 03, 2016 at 03:34:58PM +0200, Carlos E. R. wrote:
>> On 2016-08-03 15:21, Martin Steigerwald wrote:
>>
>> > Lista, Carlos, I recommend: If you are concerned about spam on the list
>> > contact the listmasters of it. They are the ones that can address it globally
>> > for the list.
>>
>> Oh, I did, long ago. Still waiting.
>
>Yes, that is the fundamental issue - spam filtering is essentially
>controlled by SGI's internal infrastructure, which we have little
>option on.
>
>What it comes down to is whether we continue to use this list
>(xfs@oss.sgi.com) or whether we move to linux-xfs@vger.kernel.org
>so we get much more robust and up-to-date spam filtering. The issue
>with doing this is forcing everyone to resubscribe, and then
>capturing everything that is still sent to xfs@oss.sgi.com.
>
>That said, I'm seriously tempted right now just to say "we're moving
>to vger" and asking everyone to resubscribe to that list, and then
>making xfs@oss.sgi.com respond with "list moved to vger, please
>repost there". i.e. not even put a forwarding gateway in place.
>
>If we do that, then I'll also shut down all the XFS git trees on
>oss.sgi.com - I'll add commits to the them to say "go to
>kernel.org". I'll need to work something out for the tarball
>releases, but kernel.org does have functionality for that, too, so
>that may just be a small change of process on my end (i.e. use kup).
>Once that is done, we'll be running completely on community provided
>infrastructure....
>
>Thoughts?
>
>Cheers,
>
>Dave.
>--
>Dave Chinner
>david@fromorbit.com

Dave,

It's probably the best option to move the mailing list to vger.
Let me know what we can do to facilitate the move.

Thanks,
Troy

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Spam on this list

[Martin Steigerwald]

Am Donnerstag, 4. August 2016, 09:15:29 CEST schrieb Dave Chinner:
> On Wed, Aug 03, 2016 at 03:34:58PM +0200, Carlos E. R. wrote:
> > On 2016-08-03 15:21, Martin Steigerwald wrote:
> > > Lista, Carlos, I recommend: If you are concerned about spam on the list
> > > contact the listmasters of it. They are the ones that can address it
> > > globally for the list.
> > 
> > Oh, I did, long ago. Still waiting.
> 
> Yes, that is the fundamental issue - spam filtering is essentially
> controlled by SGI's internal infrastructure, which we have little
> option on.
> 
> What it comes down to is whether we continue to use this list
> (xfs@oss.sgi.com) or whether we move to linux-xfs@vger.kernel.org
> so we get much more robust and up-to-date spam filtering. The issue
> with doing this is forcing everyone to resubscribe, and then
> capturing everything that is still sent to xfs@oss.sgi.com.
> 
> That said, I'm seriously tempted right now just to say "we're moving
> to vger" and asking everyone to resubscribe to that list, and then
> making xfs@oss.sgi.com respond with "list moved to vger, please
> repost there". i.e. not even put a forwarding gateway in place.
> 
> If we do that, then I'll also shut down all the XFS git trees on
> oss.sgi.com - I'll add commits to the them to say "go to
> kernel.org". I'll need to work something out for the tarball
> releases, but kernel.org does have functionality for that, too, so
> that may just be a small change of process on my end (i.e. use kup).
> Once that is done, we'll be running completely on community provided
> infrastructure....
> 
> Thoughts?

Nice, so this time discussing spam on the list on the list may have a nice 
effect in the end.

I completely agree and have no issues with resubscribung there.

Thank you,
-- 
Martin

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Spam on this list

[Carlos Eduardo Maiolino]

>> 
>> That said, I'm seriously tempted right now just to say "we're moving 
>> to vger" and asking everyone to resubscribe to that list, and then 
>> making xfs@oss.sgi.com respond with "list moved to vger, please 
>> repost there". i.e. not even put a forwarding gateway in place. 
>> 
>> If we do that, then I'll also shut down all the XFS git trees on 
>> oss.sgi.com - I'll add commits to the them to say "go to 
>> kernel.org". I'll need to work something out for the tarball 
>> releases, but kernel.org does have functionality for that, too, so 
>> that may just be a small change of process on my end (i.e. use kup). 
>> Once that is done, we'll be running completely on community provided 
>> infrastructure.... 
>> 
>> Thoughts? 

>Nice, so this time discussing spam on the list on the list may have a nice 
>effect in the end.
>
>I completely agree and have no issues with resubscribung there. 
>
>Thank you, 
>-- 
>Martin 

+1 here.

Honestly, I don't believe that moving to vger will be a big trouble for anyone other than the list maintainer who will need to set auto-respond messages.
And we have the advantage of moving it to a community provided infra as you said.

Let me know if you need any help with it, I'll be glad to help in this change



-- 
--Carlos

P.S. Martin, I apologize for the dup'ed e-mail, my MUA tricked me and I didn't copy xfs list on my previous reply..

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs