All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy McCorkell <tdm@sgi.com>
To: Lista Unx <lista.unx@gmail.com>,
	Chris Murphy <lists@colorremedies.com>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: RE: partition 100% full No space left on device. looks like xfsiscorrupted or a bug
Date: Tue, 2 Aug 2016 19:11:01 +0000	[thread overview]
Message-ID: <DF733A1EC32F124D86BC1188068FECB101A72DB79E@P-EXMB4-DC21.corp.sgi.com> (raw)
In-Reply-To: <5B47A77EB08F49A9B0843A6215A24C64@dinulap>

>On Mon, Aug 1, 2016 at 7:51 AM, Lista Unx <lista.unx@gmail.com> wrote:
>
>> On Mon, Aug 1, 2016 at 6:00 AM, Lista Unx <lista.unx@gmail.com> wrote:
>>
>>> Yes, I've created a new gmail account especially to be able to post to
>>> this
>>> mailing list which is filtering very seriously legit messages comming
>>> from
>>> legit users, just because they are comming from yahoo accounts (servers)
>>> ...
>>
>> It's a Yahoo policy. It's completely reasonable for lists to reject
>> yahoo.com emails, but ideally it'd reject them at signup time.
>>
>> https://help.yahoo.com/kb/SLN24050.html
>> https://help.yahoo.com/kb/mail/SLN24016.html?impressions=true
>> http://www.pcworld.com/article/2141120/yahoo-email-antispoofing-policy-breaks-mailing-lists.html
>>
>>
>
>Ok, I understand. In this case:
>1. Is a good idea to not allow those using yahoo accounts to subscribe to
>this list (with a clear message regarding why you are doing it)
>and
>2. Reject all messages comming from users which does not have valid
>membership on this list (for sure, you will reduce spam)

The policy for the xfs@oss.sgi.com mailing list is it is open and unmoderated to allow any user
of XFS to communicate with the XFS community.    Yes, the policy does result in spam on the mailing list.

If you have problems with the mailing list please CC me on the email.

Thanks,
Troy McCorkell
SGI



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

  reply	other threads:[~2016-08-02 19:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  9:01 partition 100% full No space left on device. looks like xfs is corrupted or a bug Lista Unx
2016-07-29 10:48 ` Carlos E. R.
2016-07-29 14:27   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 14:03 ` partition 100% full No space left on device. looks like xfs is corrupted " Brian Foster
2016-07-29 14:37   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 15:20     ` Brian Foster
2016-07-29 21:49 ` partition 100% full No space left on device. looks like xfs is corrupted " Eric Sandeen
2016-08-01 11:24   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 23:35 ` partition 100% full No space left on device. looks like xfs is corrupted " Dave Chinner
2016-08-01 12:00   ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-08-01 12:23     ` Carlos E. R.
2016-08-02 17:34       ` partition 100% full No space left on device. looks like xfsiscorrupted " Lista Unx
2016-08-02 17:34       ` Lista Unx
2016-08-01 16:51     ` partition 100% full No space left on device. looks like xfs iscorrupted " Chris Murphy
2016-08-02 17:58       ` partition 100% full No space left on device. looks like xfsiscorrupted " Lista Unx
2016-08-02 19:11         ` Troy McCorkell [this message]
2016-08-03 12:59     ` Spam on this list [Was: Re: partition 100% full No space left on device. looks like xfs iscorrupted or a bug] Carlos E. R.
2016-08-03 13:21       ` Martin Steigerwald
2016-08-03 13:34         ` Carlos E. R.
2016-08-03 23:15           ` Spam on this list Dave Chinner
2016-08-03 23:29             ` Darrick J. Wong
2016-08-04  0:51             ` Carlos E. R.
2016-08-04 11:34             ` Lista Unx
2016-08-04 13:40             ` Troy McCorkell
2016-08-04 15:49             ` Martin Steigerwald
2016-08-05  8:25               ` Carlos Eduardo Maiolino

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=DF733A1EC32F124D86BC1188068FECB101A72DB79E@P-EXMB4-DC21.corp.sgi.com \
    --to=tdm@sgi.com \
    --cc=lista.unx@gmail.com \
    --cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.