From: ori@eigenstate.org
To: sl@stanleylieber.com, 9front@9front.org
Subject: Re: [9front] /mail/lib: cleanup proposal
Date: Sun, 20 Sep 2020 21:48:59 -0700 [thread overview]
Message-ID: <244F88C3BD79577CE92C0A3495FBC369@eigenstate.org> (raw)
In-Reply-To: <5B3C3AFC-BBCB-45E2-95C8-D0C40C5C3400@stanleylieber.com>
> > I think this would make it easier to figure out what's going
> > on with upas configuration, and get a working system.
> >
> > Thoughts? Complaints? "Don't touch the artwork!"?
>
> please keep in mind all our shit (read: this mailing list, and my
> personal mail) runs on upas before committing breaking changes.
Yep, definitely. That's why I'm trying to validate my assumptions
on what's actually considered configuration, and what's dumped
in there.
Note, /mail/lib isn't in hg, so sysupdate doesn't touch it.
The changes I'm proposing would be in the defaults for new
installs.
Any breakage would be from changes in /sys/src/cmd/upas, and
I don't see any problem with keeping things compatible. At
most it'd mean checking an extra path to decide what command
to run.
> strongly in favor of simplifying setup. whatever we're currently
> shipping is the remnants of what actually ran at the labs. all that
> configuration (anti-spam, etc.) was theirs. i got all my own stuff
> working by reading the man pages and trial and error.
Yeah. I'm doing that now as well for testing the smtpd changes
for date and time. I'm realizing that this stuff is simpler than
it looks, but the example config really overcomplicates things.
> i thought incoming messages were piped through qmail somewhere along
> the line.
Ah, I missed it in the rewrite file. Thanks for the cross check.
next prev parent reply other threads:[~2020-09-21 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 18:05 ori
2020-09-20 19:01 ` [9front] " Kurt H Maier
2020-09-20 20:19 ` hiro
2020-09-20 21:27 ` Stanley Lieber
2020-09-21 4:48 ` ori [this message]
2020-10-04 23:35 ` ori
2020-10-05 5:15 ` sirjofri+ml-9front
2020-09-21 17:53 ` Lyndon Nerenberg
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=244F88C3BD79577CE92C0A3495FBC369@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=sl@stanleylieber.com \
/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).