From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: prsriva <prsriva@linux.microsoft.com>,
Nayna <nayna@linux.vnet.ibm.com>,
Prakhar Srivastava <prsriva02@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-integrity@vger.kernel.org,
inux-security-module@vger.kernel.org, zohar@linux.ibm.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
vgoyal@redhat.com, Prakhar Srivastava <prsriva@microsoft.com>
Subject: Re: [PATCH v2 2/5 RFC] use event name instead of enum to make the call generic
Date: Fri, 26 Apr 2019 08:34:29 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1904260833140.7315@namei.org> (raw)
In-Reply-To: <CAADWXX8NC-PFJmuvQbNXn49CYjvyn-e0rtH_EoUfCvuJHTwHAQ@mail.gmail.com>
On Thu, 25 Apr 2019, Linus Torvalds wrote:
> On Thu, Apr 25, 2019 at 10:19 AM prsriva <prsriva@linux.microsoft.com> wrote:
> >
> > I will fix the comments and send out the patchset with a cover letter.
> > Thankyou for pointing this out.
>
> Please trim the emails you reply to rather than quoting everything.
>
> But the real reason I'm reacting to this email is because it was
> marked as spam, because your SMTP setup is incorrect, and you don't go
> through the proper MS SMTP server. As a result, you don't get the
> proper DKIM signature for verification of the microsoft.com email
> address, and sane email clients will mark your emails as spam.
>
> Please fix.
It's the correct SMTP server for linux.microsoft.com.
linux.microsoft.com. 3600 IN TXT "v=spf1 ip4:13.77.154.182 -all"
linux.microsoft.com. 3600 IN TXT "v=DMARC1;p=none;pct=100;rua=mailto:jamorris@microsoft.com"
We don't have DKIM set up yet.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-04-25 22:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 0:15 [PATCH v2 1/5 RFC] added ima hook for buffer, being enabled as a policy Prakhar Srivastava
2019-04-24 0:15 ` [PATCH v2 2/5 RFC] use event name instead of enum to make the call generic Prakhar Srivastava
2019-04-25 11:48 ` Nayna
2019-04-25 17:19 ` prsriva
2019-04-25 18:31 ` Linus Torvalds
2019-04-25 22:34 ` James Morris [this message]
2019-04-25 23:18 ` James Bottomley
2019-04-26 0:03 ` James Morris
2019-04-25 23:19 ` Linus Torvalds
2019-04-25 18:41 ` Nayna
2019-04-24 0:15 ` [PATCH v2 3/5 RFC] since cmdline args can be same for multiple kexec, log entry hash will collide. Prepend the kernel file name to the cmdline args to distinguish between cmdline args passed to subsequent kexec calls Prakhar Srivastava
2019-04-24 0:15 ` [PATCH v2 4/5 RFC] added a buffer_check LSM hook Prakhar Srivastava
2019-04-24 0:15 ` [PATCH v2 5/5 RFC] add the buffer to the event data in ima free entry data if store_template failed added check in templates for buffer Prakhar Srivastava
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=alpine.LRH.2.21.1904260833140.7315@namei.org \
--to=jmorris@namei.org \
--cc=ebiederm@xmission.com \
--cc=inux-security-module@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nayna@linux.vnet.ibm.com \
--cc=prsriva02@gmail.com \
--cc=prsriva@linux.microsoft.com \
--cc=prsriva@microsoft.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).