Github messages for mblaze
 help / color / mirror / Atom feed
From: Anachron <>
Subject: Re: [ISSUE] [CLOSED] Question: How to auto sign emails?
Date: Fri, 16 Apr 2021 07:51:54 +0200	[thread overview]
Message-ID: <20210416055154.BUENnuz5szntTi6EEeF2o8-UZlcBGwdWIeFmJWscQwE@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Closed issue by Anachron on mblaze repository

So I was wondering how do you automatically sign emails (gpg)? I‘m new to email signing so that idea may be stupid... just let me know how you handle email signing. I am not sending emails with a lot of people so I guess there would be no problem sending my key to those I communicate to so all my emails can be signed by default.

Thanks and have a great day!

           reply	other threads:[~2021-04-16  5:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210416055154.BUENnuz5szntTi6EEeF2o8-UZlcBGwdWIeFmJWscQwE@z \ \ \

* 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).