From: sl@9front.org
To: 9fans@9fans.net
Subject: Re: [9fans] upas : without acme : possible?
Date: Thu, 29 Nov 2018 22:32:20 -0500 [thread overview]
Message-ID: <D7A6F3F75974D64FAA1B7D806BCA0DC8@ewsd.inri.net> (raw)
In-Reply-To: 20181129155852.GA69882@wopr
> is that "mail" you mention similar to "mailx" under unix-like systems?
> the problem is one of not wanting a captive user-interface to the
> mailing sub-system.
On Plan 9, 'mail' is a shell script that invokes either nedmail(1) or
marshal(1), depending on the flags it consumes.
The nedmail program is nearly identical, from a user interface
standpoint, to the mail command that shipped with the 8th edition of
Research UNIX. It remains part of the same (though evolved) e-mail
processing system, upas.
Ned is a little different than mailx(1), but it's probably just about
what you're looking for.
Plan 9's mail system itself (upas) relies heavily upon upasfs(4),
filter(1), and simple rc scripts, which make even complex tasks
like custom spam filtering and automatic mailbox management
trivial.
sl
next reply other threads:[~2018-11-30 3:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 3:32 sl [this message]
2018-11-30 3:53 ` Mayuresh Kathe
2018-11-30 13:21 ` [9fans] non-captive user-interfaces: some ramblings; Plan 9 possibilities Ethan Gardener
2018-12-26 22:03 ` [9fans] MH port Lyndon Nerenberg
[not found] ` <f94ead0a574c9d37bbf037033c322814@kathe.in>
2018-12-29 2:28 ` Lyndon Nerenberg
-- strict thread matches above, loose matches on Subject: below --
2018-11-30 14:22 [9fans] upas : without acme : possible? sl
[not found] <3B648B1B56B7F372B8E8ADAE7AE3D0B3@ewsd.inri.net>
2018-11-30 4:52 ` Mayuresh Kathe
2018-11-30 4:40 sl
2018-11-29 13:44 Mayuresh Kathe
2018-11-29 14:13 ` Alexander Sychev
2018-11-29 14:34 ` Dan Cross
2018-11-29 14:57 ` Mayuresh Kathe
2018-11-29 15:58 ` Kurt H Maier
2018-11-29 16:50 ` erik quanstrom
2018-11-29 19:00 ` Steve Simon
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=D7A6F3F75974D64FAA1B7D806BCA0DC8@ewsd.inri.net \
--to=sl@9front.org \
--cc=9fans@9fans.net \
/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).