On 11 June 2012 at 0:42, Ken Hornstein k...@pobox.com wrote:
I am pleased to announce the release of nmh 1.5. It is available for
download here:
http://download.savannah.gnu.org/releases/nmh/nmh-1.5.tar.gz
1.5 works great on my systems. That's no surprise as RC2 and RC3
worked
David Levine levin...@acm.org writes:
Norm wrote:
Maybe mhmail needs a '-server servername' option and perhaps
some other send options as well.
Perhaps, though is that necessary? It seems that mhmail was
intended to be lean. The man page recommends using comp and
send for interactive use.
mts=/usr/local/nmh/etc/mts.conf#depends on installation
sed $mts | /tmp/mts.conf -e '/^servers:/s/:.*/: localhost/'
MHMTSCONF=/tmp/mts.conf mhmail norm -from norm -subject $1
I'm wondering ... do you really think these gyrations are appropriate
for mhmail?
Back in the day, needing to
Ken wrote:
I'm wondering ... do you really think these gyrations are appropriate
for mhmail?
Back in the day, needing to change the server used by post and
friends was very rare, so putting it all in mts.conf was reasonable.
But now we have alternate ports and changing servers is more
n...@dad.org wrote:
David Levine levin...@acm.org writes:
Norm wrote:
Suppose I want to do something like:
mts=/usr/local/nmh/etc/mts.conf#depends on installation
sed $mts | /tmp/mts.conf -e '/^servers:/s/:.*/: localhost/'
MHMTSCONF=/tmp/mts.conf mhmail norm -from norm
Can we make send look like mhmail (mhmail with arguments, when
sending)? Then mhmail could be a simple wrapper around it.
The only thing we'd lose is that it would read the profile and
aliases, but I don't see those as a drawback these days. If
it is important, we could add an option to send to
David Levine levin...@acm.org writes:
Ken wrote:
I'm wondering ... do you really think these gyrations are appropriate
for mhmail?
Back in the day, needing to change the server used by post and
friends was very rare, so putting it all in mts.conf was reasonable.
But now we have alternate
Ken wrote:
Okay, here's my thinking, for what it's worth:
- send in my mind is mostly a front-end to post (or whatever you
have your postproc set to). You need to give it a already-formed
draft.
- mhmail is more of a replacement for mailx; it does the draft
composition for you.
So
mhmail has traditionally been a front end to post, too.
But it's now inadequate and it's a maintenance headache.
I think that replacing it with a script that relies
on send or post could solve both problems.
I don't really care about the implementation details (although it occurs to
me that one
I just committed uip/mhmail.in. It's a .in file because
autoconf will eventually digest it, but it can be run as-is
for now.
By default, it uses post. It emulates mhmail plus passes
along any post options. So this works, and ignores the
server in my mts.conf:
uip/mhmail.in levine -subject
10 matches
Mail list logo
