From: Julien Lepiller <julien@lepiller.eu>
To: Joshua Branson <jbranso@dismail.de>
Cc: Joshua Branson via <help-guix@gnu.org>
Subject: Re: Troubles with opensmtpd-filter-dkimsign
Date: Tue, 03 Nov 2020 16:22:21 -0500 [thread overview]
Message-ID: <FC60BF7B-34FD-49A2-A7CB-80B24A884DC4@lepiller.eu> (raw)
In-Reply-To: <87lffixjit.fsf_-_@dismail.de>
I don't use opensmtpd-filter-dkimsign. However, you could try to stop smtpd, and use smtpd manually on a configuration file you can write on without having to reconfigure all the time. That will give you shorter cycles and more debugging output.
Le 3 novembre 2020 15:39:06 GMT-05:00, Joshua Branson <jbranso@dismail.de> a écrit :
>
>I am having an issue with getting opensmtpd-filter-dkimsign to work.
>Is
>anyone using opensmtpd-filter-dkimsign? I can't seem to find the
>correct syntax.
>
>https://notabug.org/jbranso/linode-guix-system-configuration/src/master/mail.scm
>
>I've tried a couple of different ways. Here's the relevant bits from
>my
>configuration.
>
>#+BEGIN_SRC sh
># an initial attempt at getting dkim-signing to work
>#this doesn't work
># filter \"dkimsign\" proc-exec \"filter-dkimsign -d gnucode.me -s
>20201004 -k \
>#
>/home/joshua/linode-guix-system-configuration/email-ssh-keys/gnucode.me.key\"
>\
># user joshua group joshua
>
>#this doesn't work
># filter \"dkimsign\" proc-exec \"filter-dkimsign -d gnucode.me -s
>20201004 -k
>/home/joshua/linode-guix-system-configuration/email-ssh-keys/gnucode.me.key\"
>user joshua group joshua
>
># this doesn't work
>filter \"dkimsign\" proc-exec
>\"/gnu/store/z3iz3xp59ql4zbp4w06l0sqxciapg8q3-profile/libexec/opensmtpd/filter-dkimsign
>-d gnucode.me -s 20201004 -k
>/home/joshua/linode-guix-system-configuration/email-ssh-keys/gnucode.me.key\"
>user joshua group joshua
>
># listen on eth0, fairly explainatory
>listen on socket # filter \"dkimsign\"
>listen on eth0 tls pki mail.gnucode.me # filter \"dkimsign\"
>listen on eth0 port 465 smtps pki mail.gnucode.me auth <creds>
>listen on eth0 port 587 tls-require pki mail.gnucode.me auth <creds>
>#+END_SRC
>
>I'm currently not even using the opensmtpd-filter-dkimsign. I'm just
>trying to get the "filter" line to work. Currently "sudo herd restart
>opensmtpd" fails to restart the service, and I'm not certain why.
>
>Thanks,
>
>Joshua
>
>--
>Joshua Branson
>Sent from Emacs and Gnus
>https://gnucode.me
>https://video.hardlimit.com/accounts/joshua_branson/video-channels
>"You can have whatever you want, as long as you help enough other
>people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2020-11-03 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 6:46 Troubles with opensmtpd Joshua Branson via
2020-10-27 11:19 ` Tobias Geerinckx-Rice
2020-10-28 23:13 ` Joshua Branson
2020-10-27 11:19 ` Julien Lepiller
2020-10-28 23:10 ` Joshua Branson
2020-11-03 20:39 ` Troubles with opensmtpd-filter-dkimsign Joshua Branson
2020-11-03 21:15 ` Tobias Geerinckx-Rice
2020-11-04 0:39 ` Joshua Branson
2020-11-04 0:54 ` Joshua Branson
2020-11-04 1:20 ` Tobias Geerinckx-Rice
2020-11-03 21:22 ` Julien Lepiller [this message]
2020-11-04 0:37 ` Joshua Branson
2020-10-27 11:21 ` Troubles with opensmtpd Julien Lepiller
2020-10-27 12:21 ` Tobias Geerinckx-Rice
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FC60BF7B-34FD-49A2-A7CB-80B24A884DC4@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).