Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

50%
+0 −0
Q&A PGP sign emails sent with git-send-email(1)

git-send-email(1) uses sendmail(8) as the MTA by default. However, this can be changed by passing the --sendmail-cmd option. $ man git-send-email | sed -n '/--sendmail-cmd=/,/^$/p' --sendma...

posted 8mo ago by alx‭  ·  edited 8mo ago by alx‭

Answer
#2: Post edited by user avatar alx‭ · 2024-04-22T10:08:43Z (8 months ago)
  • *git-send-email*(1) uses sendmail(8) as the MTA by default. However, this can be changed by passing the `--sendmail-cmd` option.
  • ```
  • $ man git-send-email | sed -n '/--sendmail-cmd=/,/^$/p'
  • --sendmail-cmd=<command>
  • Specify a command to run to send the email. The command should
  • be sendmail-like; specifically, it must support the -i option.
  • The command will be executed in the shell if necessary.
  • Default is the value of sendemail.sendmailcmd. If unspecified,
  • and if --smtp-server is also unspecified, git-send-email will
  • search for sendmail in /usr/sbin, /usr/lib and $PATH.
  • ```
  • or the equivalent, `sendemail.sendmailcmd`, in git-config(1).
  • A MUA program like neomutt(1) can be used for this purpose:
  • ```
  • [sendemail]
  • sendmailcmd = neomutt -C -H - && true
  • ```
  • The `&& true` trick is to ignore the arguments that git-send-mail(1) passes to the MTA, which neomutt(1) doesn't need. The -C flag was added (disclaimer: I did that) to neomutt(1) recently to allow using crypto when running in batch mode (reading from stdin), which is disabled otherwise.
  • This has other benefits, like not having to configure `[sendemail]` for git-send-email(1) if you already have neomutt(1) configured.
  • See also: <https://neomutt.org/feature/cli-crypto>
  • *git-send-email*(1) uses sendmail(8) as the MTA by default. However, this can be changed by passing the `--sendmail-cmd` option.
  • ```
  • $ man git-send-email | sed -n '/--sendmail-cmd=/,/^$/p'
  • --sendmail-cmd=<command>
  • Specify a command to run to send the email. The command should
  • be sendmail-like; specifically, it must support the -i option.
  • The command will be executed in the shell if necessary.
  • Default is the value of sendemail.sendmailcmd. If unspecified,
  • and if --smtp-server is also unspecified, git-send-email will
  • search for sendmail in /usr/sbin, /usr/lib and $PATH.
  • ```
  • or the equivalent, `sendemail.sendmailcmd`, in git-config(1).
  • A MUA program like neomutt(1) can be used for this purpose:
  • ```
  • [sendemail]
  • sendmailcmd = neomutt -C -H - && true
  • ```
  • The `&& true` trick is to ignore the arguments that git-send-mail(1) passes to the MTA, which neomutt(1) doesn't need. The -C flag was added (disclaimer: I did that) to neomutt(1) recently to allow using crypto when running in batch mode (reading from stdin), which is disabled by default.
  • This has other benefits, like not having to configure `[sendemail]` for git-send-email(1) if you already have neomutt(1) configured.
  • See also: <https://neomutt.org/feature/cli-crypto>
#1: Initial revision by user avatar alx‭ · 2024-04-22T10:07:47Z (8 months ago)
*git-send-email*(1) uses sendmail(8) as the MTA by default.  However, this can be changed by passing the `--sendmail-cmd` option.

```
$ man git-send-email | sed -n '/--sendmail-cmd=/,/^$/p'
     --sendmail-cmd=<command>
         Specify a command to run to send the email. The command should
         be sendmail-like; specifically, it must support the -i option.
         The command will be executed in the shell if necessary.
         Default is the value of sendemail.sendmailcmd. If unspecified,
         and if --smtp-server is also unspecified, git-send-email will
         search for sendmail in /usr/sbin, /usr/lib and $PATH.

```

or the equivalent, `sendemail.sendmailcmd`, in git-config(1).

A MUA program like neomutt(1) can be used for this purpose:

```
[sendemail]
	sendmailcmd = neomutt -C -H - && true
```

The `&& true` trick is to ignore the arguments that git-send-mail(1) passes to the MTA, which neomutt(1) doesn't need.  The -C flag was added (disclaimer: I did that) to neomutt(1) recently to allow using crypto when running in batch mode (reading from stdin), which is disabled otherwise.

This has other benefits, like not having to configure `[sendemail]` for git-send-email(1) if you already have neomutt(1) configured.

See also: <https://neomutt.org/feature/cli-crypto>