From: kaigai@ak.jp.nec.com (KaiGai Kohei)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] NSA SELinux list unavailable?
Date: Tue, 24 Nov 2009 10:15:26 +0900 [thread overview]
Message-ID: <4B0B33AE.60203@ak.jp.nec.com> (raw)
Sorry for the unrelated topic.
Does anyone know whether the NSA SELinux list is available, or not?
I got this reply when I submit a message with an attachment.
------------------------------------------------
The original message was received at Tue, 24 Nov 2009 01:03:16 GMT
from localhost [127.0.0.1]
----- The following addresses had permanent fatal errors -----
<ewalsh@tycho.nsa.gov>
(reason: 550 #5.1.0 Address rejected.)
<selinux@tycho.nsa.gov>
(reason: 550 #5.1.0 Address rejected.)
----- Transcript of session follows -----
... while talking to goalie.tycho.ncsc.mil.:
>>> >>> RCPT To:<selinux@tycho.nsa.gov>
<<< 550 #5.1.0 Address rejected.
550 5.1.1 <selinux@tycho.nsa.gov>... User unknown
>>> >>> RCPT To:<ewalsh@tycho.nsa.gov>
<<< 550 #5.1.0 Address rejected.
550 5.1.1 <ewalsh@tycho.nsa.gov>... User unknown
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>
next reply other threads:[~2009-11-24 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 1:15 KaiGai Kohei [this message]
2009-11-24 16:25 ` [refpolicy] NSA SELinux list unavailable? Chad Sellers
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=4B0B33AE.60203@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--cc=refpolicy@oss.tresys.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.