From: "Dave MacFarlane" <firstname.lastname@example.org>
Subject: [9front] smtpd -d documentation
Date: Thu, 17 Nov 2022 20:13:22 -0500 [thread overview]
Message-ID: <427AFBDD3E4388CBB2249F1542FAE09B@driusan.net> (raw)
I just realized my email yesterday never went through.. I think gmail probably silently added html even though I told it to send as plaintext.
Anyways, I think there's a bug in the documentation for upas/smtpd -d
-d turns on debugging output, with each connection's output
going to a uniquely-named file in /sys/log/smtpdb.
In fact, at /sys/src/cmd/upas/smtp/smtpd.c:163 is appends to the file
/sys/log/smtpd.db, not a new file in /sys/log/smtpdb.
reply other threads:[~2022-11-18 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
* 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).