All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: bp@suse.de, bp@alien8.de,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	mingo@redhat.com, LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, hpa@zytor.com, jdike@addtoit.com,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/build] x86/um/vdso: Drop implicit common-page-size linker flag
Date: Tue, 11 Dec 2018 21:14:28 +0100	[thread overview]
Message-ID: <26201549.d0hG7Wm4ip@blindfold> (raw)
In-Reply-To: <CAKwvOd=OY-qWqxK9gcacKChAEAPqFWyyBbgsQK6-h0zTYTcOgg@mail.gmail.com>

Am Dienstag, 11. Dezember 2018, 20:08:30 CET schrieb Nick Desaulniers:
> > But in this particular case, DKIM is pretty good spam protection
> > mechanism so enabling it is a good idea.
> 
> Internal Gmail developers were able to help me verify that SPF was
> setup correctly, but indeed there's no DKIM.  This article has more
> info: https://support.google.com/mail/answer/81126?hl=en.  Richard, I
> don't know if that's a lot of work on your end, but other folks using
> gmail might have the same issue repeatedly with receiving emails from
> your domain otherwise.

Running your own mailserver is already a PITA, so adding a little more
pain does not count in much more.
Thanks for talking to Gmail guys, I'll look into adding DKIM.

Thanks,
//richard



  reply	other threads:[~2018-12-11 20:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 19:12 [PATCH] x86/vdso: drop implicit common-page-size linker flag ndesaulniers
2018-12-06 20:29 ` Andy Lutomirski
2018-12-07 10:18 ` Borislav Petkov
2018-12-07 17:45   ` Nick Desaulniers
2018-12-07 17:52     ` Borislav Petkov
2018-12-07 18:00       ` Nick Desaulniers
2018-12-07 18:33 ` [tip:x86/urgent] x86/vdso: Drop " tip-bot for Nick Desaulniers
2018-12-11 13:12 ` [tip:x86/build] x86/um/vdso: " tip-bot for ndesaulniers@google.com
2018-12-11 17:39   ` Nick Desaulniers
2018-12-11 17:43     ` Richard Weinberger
2018-12-11 17:46       ` Borislav Petkov
2018-12-11 17:53         ` Nick Desaulniers
2018-12-11 18:05           ` Borislav Petkov
2018-12-11 19:08             ` Nick Desaulniers
2018-12-11 20:14               ` Richard Weinberger [this message]
2018-12-11 20:53               ` Borislav Petkov
2018-12-11 13:25 ` tip-bot for Nick Desaulniers

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=26201549.d0hG7Wm4ip@blindfold \
    --to=richard@nod.at \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=ndesaulniers@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yamada.masahiro@socionext.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.