From: "Dave MacFarlane" <driusan@driusan.net>
To: 9front@9front.org
Subject: [9front] "Insecure" icon in gmail
Date: Wed, 15 May 2024 17:21:33 -0400 [thread overview]
Message-ID: <4C1B6B746BF77B2F88319BBFCBFEB08C@driusan.net> (raw)
I just spent more time than I care to admit trying
to get rid of the red "Insecure" icon on emails sent
to gmail from my 9front box.
In the end, the meat of my /mail/lib/remotemail ended up
being
exec /bin/upas/dkim -s 20180128 -d driusan.net >[2]/sys/log/dkim| /bin/upas/smtp -s -h driusan.net .driusan.net $addr $sender $*
But I had to modify upas/smtp to *not* validate the certificate
for startls by commenting out the okCertificate line in
/sys/src/cmd/upas/smtp/smtp.c
This doesn't seem like a great idea, but without -s remotemail
won't use startls, and with -s the list of thumbs needs to be
maintained for every email server on the internet in order to
send email as far as I can tell.
So I have 3 questions:
1. Am I missing something obvious?
2. Is there a better way to do this?
3. Would it make sense to add a flag to use startls but not validate certificates for upas/smtp?
- Dave
next reply other threads:[~2024-05-15 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 21:21 Dave MacFarlane [this message]
2024-05-15 21:28 ` Stanley Lieber
2024-05-16 1:23 ` [9front] " Anthony Martin
2024-05-16 1:39 ` Kurt H Maier
2024-05-16 2:06 ` Dave MacFarlane
2024-05-16 2:51 ` Anthony Martin
2024-05-16 10:27 ` [9front] " cinap_lenrek
2024-05-16 11:01 ` sirjofri
2024-05-18 18:45 ` ori
2024-05-18 20:12 ` hiro
2024-05-18 22:27 ` sirjofri
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=4C1B6B746BF77B2F88319BBFCBFEB08C@driusan.net \
--to=driusan@driusan.net \
--cc=9front@9front.org \
/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).