uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/02/87)
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/03/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP.UUCP (09/05/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/07/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP.UUCP (09/07/87)
Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP.UUCP (09/07/87)
Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP.UUCP (09/07/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP.UUCP (09/07/87)
Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP.UUCP (09/07/87)
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP.UUCP (09/08/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/09/87)
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducal)luucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/10/87)
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/10/87)
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sri-spam!sri-unix!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/11/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01959@tccc0.TFS> Date: 11 Sep 87 15:03:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111406.AA01147@tccc0.TFS> Date: 11 Sep 87 14:06:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 24 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111446.AA01790@tccc0.TFS> Date: 11 Sep 87 14:46:44 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01797@tccc0.TFS>
Date: 11 Sep 87 14:46:50 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01804@tccc0.TFS>
Date: 11 Sep 87 14:46:55 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01811@tccc0.TFS>
Date: 11 Sep 87 14:47:00 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01818@tccc0.TFS>
Date: 11 Sep 87 14:47:04 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111447.AA01825@tccc0.TFS> Date: 11 Sep 87 14:47:08 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01925@tccc0.TFS> Date: 11 Sep 87 15:03:21 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01932@tccc0.TFS>
Date: 11 Sep 87 15:03:28 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sconf uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111504.AA02018@tccc0.TFS>
Date: 11 Sep 87 15:04:45 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 28
Path: teknek!dual!ptsfa!ames!sri-spam!sri-unix!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01966@tccc0.TFS> Date: 11 Sep 87 15:03:56 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03061@tccc0.TFS>
Date: 11 Sep 87 17:00:02 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03082@tccc0.TFS> Date: 11 Sep 87 17:00:16 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03089@tccc0.TFS> Date: 11 Sep 87 17:00:22 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03096@tccc0.TFS>
Date: 11 Sep 87 17:00:26 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 61
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03103@tccc0.TFS>
Date: 11 Sep 87 17:00:32 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01912@tccc0.TFS>
Date: 11 Sep 87 15:03:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01946@tccc0.TFS>
Date: 11 Sep 87 15:03:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111659.AA03041@tccc0.TFS>
Date: 11 Sep 87 16:59:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03075@tccc0.TFS> Date: 11 Sep 87 17:00:12 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03068@tccc0.TFS>
Date: 11 Sep 87 17:00:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!aurora!labrea!jade!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111659.AA03048@tccc0.TFS> Date: 11 Sep 87 16:59:57 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111520.AA02141@tccc0.TFS> Date: 11 Sep 87 15:20:24 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 128 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taylor
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: news.groups,news.admin,comp.mail.elm Subject: `dual' and `uclachem': clean up your active file!! Summary: The mess in comp.mail.elm is THEIR fault! Message-ID: <775@hplabsz.HPL.HP.COM> Date: 11 Sep 87 23:40:35 GMT Followup-To: news.admin Distribution: world Organization: Hewlett-Packard Laboratories Lines: 19 The current havoc being wreaked in the Usenet group "comp.mail.elm" is actually the fault of two sites: dual and uclachem. It appears that they both still have the newsgroup listed as moderated, even though it changed status quite a while ago. As a consequence, all the postings that show up for the group are being MAILED to comp-mail-elm@hplabs which is automatically posting them, the posting of which is then being rejected and mailed to ... well ... it'll go on for a long time like this. At our end we've changed "comp-mail-elm@hplabs" to point to /dev/null to cut our half off, but dual and uclachem both need to clean up their active files to reflect the *UN*moderated status of the group! Please!!! Soon!!! --- Dave Taylor ex-moderator of comp.mail.elm Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/12/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120907.AA01492@tccc0.TFS>
Date: 12 Sep 87 09:07:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03103@tccc0.TFS>
Date: 11 Sep 87 17:00:32 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120929.AA01578@tccc0.TFS>
Date: 12 Sep 87 09:29:10 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 100
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01912@tccc0.TFS>
Date: 11 Sep 87 15:03:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120929.AA01585@tccc0.TFS>
Date: 12 Sep 87 09:29:17 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 100
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01946@tccc0.TFS>
Date: 11 Sep 87 15:03:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120929.AA01592@tccc0.TFS>
Date: 12 Sep 87 09:29:22 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 100
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111659.AA03041@tccc0.TFS>
Date: 11 Sep 87 16:59:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120906.AA01471@tccc0.TFS> Date: 12 Sep 87 09:06:56 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 66 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03082@tccc0.TFS> Date: 11 Sep 87 17:00:16 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120907.AA01478@tccc0.TFS> Date: 12 Sep 87 09:07:00 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 66 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03089@tccc0.TFS> Date: 11 Sep 87 17:00:22 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120929.AA01599@tccc0.TFS> Date: 12 Sep 87 09:29:26 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 76 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03075@tccc0.TFS> Date: 11 Sep 87 17:00:12 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120906.AA01457@tccc0.TFS> Date: 12 Sep 87 09:06:48 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 66 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01966@tccc0.TFS> Date: 11 Sep 87 15:03:56 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120906.AA01464@tccc0.TFS>
Date: 12 Sep 87 09:06:52 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 45
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03061@tccc0.TFS>
Date: 11 Sep 87 17:00:02 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120907.AA01485@tccc0.TFS>
Date: 12 Sep 87 09:07:04 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 70
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03096@tccc0.TFS>
Date: 11 Sep 87 17:00:26 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 61
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120905.AA01336@tccc0.TFS> Date: 12 Sep 87 09:05:11 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 76 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01959@tccc0.TFS> Date: 11 Sep 87 15:03:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120905.AA01343@tccc0.TFS> Date: 12 Sep 87 09:05:17 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 33 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111406.AA01147@tccc0.TFS> Date: 11 Sep 87 14:06:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 24 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120905.AA01360@tccc0.TFS>
Date: 12 Sep 87 09:05:30 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01797@tccc0.TFS>
Date: 11 Sep 87 14:46:50 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120905.AA01352@tccc0.TFS> Date: 12 Sep 87 09:05:24 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111446.AA01790@tccc0.TFS> Date: 11 Sep 87 14:46:44 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120905.AA01375@tccc0.TFS>
Date: 12 Sep 87 09:05:40 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01811@tccc0.TFS>
Date: 11 Sep 87 14:47:00 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120905.AA01367@tccc0.TFS>
Date: 12 Sep 87 09:05:35 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01804@tccc0.TFS>
Date: 11 Sep 87 14:46:55 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120905.AA01382@tccc0.TFS>
Date: 12 Sep 87 09:05:45 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01818@tccc0.TFS>
Date: 11 Sep 87 14:47:04 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120906.AA01429@tccc0.TFS> Date: 12 Sep 87 09:06:29 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 76 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111447.AA01825@tccc0.TFS> Date: 11 Sep 87 14:47:08 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120906.AA01436@tccc0.TFS> Date: 12 Sep 87 09:06:35 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 97 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01925@tccc0.TFS> Date: 11 Sep 87 15:03:21 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP.UUCP (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120906.AA01443@tccc0.TFS>
Date: 12 Sep 87 09:06:39 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 45
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01932@tccc0.TFS>
Date: 11 Sep 87 15:03:28 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120929.AA01606@tccc0.TFS>
Date: 12 Sep 87 09:29:30 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 100
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03068@tccc0.TFS>
Date: 11 Sep 87 17:00:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709120906.AA01450@tccc0.TFS>
Date: 12 Sep 87 09:06:45 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 37
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111504.AA02018@tccc0.TFS>
Date: 11 Sep 87 15:04:45 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 28
Path: teknek!dual!ptsfa!ames!sri-spam!sri-unix!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120929.AA01613@tccc0.TFS> Date: 12 Sep 87 09:29:35 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 97 Path: teknek!dual!ptsfa!ames!aurora!labrea!jade!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111659.AA03048@tccc0.TFS> Date: 11 Sep 87 16:59:57 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/12/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709120929.AA01620@tccc0.TFS> Date: 12 Sep 87 09:29:39 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 137 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111520.AA02141@tccc0.TFS> Date: 11 Sep 87 15:20:24 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 128 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709121520.AA22310@ucbvax.Berkeley.EDU> Date: 12 Sep 87 14:08:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!princeton!rutgers!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!cit-vax!ll-xn!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Lay o
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!rutgers!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01959@tccc0.TFS> Date: 11 Sep 87 15:03:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111406.AA01147@tccc0.TFS> Date: 11 Sep 87 14:06:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 24 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111446.AA01790@tccc0.TFS> Date: 11 Sep 87 14:46:44 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01797@tccc0.TFS>
Date: 11 Sep 87 14:46:50 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01804@tccc0.TFS>
Date: 11 Sep 87 14:46:55 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01811@tccc0.TFS>
Date: 11 Sep 87 14:47:00 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01818@tccc0.TFS>
Date: 11 Sep 87 14:47:04 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111447.AA01825@tccc0.TFS> Date: 11 Sep 87 14:47:08 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01925@tccc0.TFS> Date: 11 Sep 87 15:03:21 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01932@tccc0.TFS>
Date: 11 Sep 87 15:03:28 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111504.AA02018@tccc0.TFS>
Date: 11 Sep 87 15:04:45 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 28
Path: teknek!dual!ptsfa!ames!sri-spam!sri-unix!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01966@tccc0.TFS> Date: 11 Sep 87 15:03:56 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03061@tccc0.TFS>
Date: 11 Sep 87 17:00:02 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03082@tccc0.TFS> Date: 11 Sep 87 17:00:16 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03089@tccc0.TFS> Date: 11 Sep 87 17:00:22 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03096@tccc0.TFS>
Date: 11 Sep 87 17:00:26 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 61
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03103@tccc0.TFS>
Date: 11 Sep 87 17:00:32 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01912@tccc0.TFS>
Date: 11 Sep 87 15:03:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01946@tccc0.TFS>
Date: 11 Sep 87 15:03:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111659.AA03041@tccc0.TFS>
Date: 11 Sep 87 16:59:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03075@tccc0.TFS> Date: 11 Sep 87 17:00:12 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03068@tccc0.TFS>
Date: 11 Sep 87 17:00:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111659.AA03048@tccc0.TFS> Date: 11 Sep 87 16:59:57 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@uclachem.UUCP (Unix-to-Unix copy program) (09/13/87)
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111520.AA02141@tccc0.TFS> Date: 11 Sep 87 15:20:24 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 128 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!aurora!labrea!jade!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131031.AA05043@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:21:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!aurora!labrea!jade!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131032.AA05055@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:21:53 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131032.AA05080@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:22:09 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131032.AA05095@ucbvax.Berkeley.EDU> Date: 13 Sep 87 04:22:23 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131033.AA05110@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:23:01 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131034.AA05122@ucbvax.Berkeley.EDU> Date: 13 Sep 87 04:23:18 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131034.AA05132@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:23:36 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 36
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131035.AA05147@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:23:52 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131035.AA05162@ucbvax.Berkeley.EDU> Date: 13 Sep 87 04:25:29 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 128 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taneorm
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131036.AA05172@ucbvax.Berkeley.EDU> Date: 13 Sep 87 04:26:09 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131036.AA05187@ucbvax.Berkeley.EDU> Date: 13 Sep 87 04:26:26 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131036.AA05196@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:27:55 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 28
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!rutgers!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131037.AA05209@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:26:42 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131037.AA05224@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:26:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131038.AA05247@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:27:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 36
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131038.AA05260@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:27:17 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131039.AA05271@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:27:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131046.AA05362@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 01:17:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 51
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!princeton!rutgers!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131047.AA05377@ucbvax.Berkeley.EDU> Date: 13 Sep 87 03:23:27 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 24 Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!cit-vax!ll-xn!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131047.AA05386@ucbvax.Berkeley.EDU> Date: 13 Sep 87 04:21:03 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131048.AA05395@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 04:21:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131048.AA05405@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:28:16 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 61
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131048.AA05419@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:28:28 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131049.AA05428@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:35:15 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 76 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01959@tccc0.TFS> Date: 11 Sep 87 15:03:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11926@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:42 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131049.AA05443@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:35:26 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 33 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111406.AA01147@tccc0.TFS> Date: 11 Sep 87 14:06:51 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 24 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpfcdc!hpfcls!neutron From: neutron@hpfcls.HP.COM (Jack Applin) Newsgroups: comp.mail.elm Subject: backquote check in mkhdrs.c Message-ID: <7390001@hpfcls.HP.COM> Date: 8 Sep 87 23:21:45 GMT Organization: Hewlett-Packard SSO Lines: 15 In mkhdrs.c, there is code to recognize backquoting in .elmheaders. from mkhdrs.c (in add_mailheaders): > else if (occurances_of(BACKQUOTE, buffer) == 2) > expand_backquote(buffer, filedesc); I had a line in .elmheaders like: Number: `cd; n=0\`cat -s .num\`; n=\`expr $n + 1\`; echo $n >.num; echo $n` which wasn't recognized because it had more than two backquotes. It would be better to check for >=2 instead of for exactly two backquotes. -Jack Applin
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131049.AA05452@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:35:37 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111446.AA01790@tccc0.TFS> Date: 11 Sep 87 14:46:44 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102053.AA10398@ucbvax.Berkeley.EDU> Date: 10 Sep 87 03:18:55 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 70 Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131049.AA05461@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:36:01 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 36
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01804@tccc0.TFS>
Date: 11 Sep 87 14:46:55 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10470@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:17:24 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!cmcl2!rutgers!lll-lcc!well!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131050.AA05470@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:36:45 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 97 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01925@tccc0.TFS> Date: 11 Sep 87 15:03:21 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102130.AA11391@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 79 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131050.AA05479@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:36:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 45
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01932@tccc0.TFS>
Date: 11 Sep 87 15:03:28 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102130.AA11400@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131050.AA05488@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:37:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 37
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111504.AA02018@tccc0.TFS>
Date: 11 Sep 87 15:04:45 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 28
Path: teknek!dual!ptsfa!ames!sri-spam!sri-unix!husc6!uwvax!vanvleck!uwmcsd1!csd4.milw.wisc.edu!dave
From: dave@csd4.milw.wisc.edu (David A Rasmussen)
Newsgroups: comp.mail.elm
Subject: file corrupt bug
Message-ID: <2828@uwmcsd1.UUCP>
Date: 10 Sep 87 20:41:18 GMT
Sender: daemon@uwmcsd1.UUCP
Reply-To: dave@csd4.milw.wisc.edu (David A Rasmussen)
Distribution: na
Organization: Computing Services Division, UW Milwaukee
Lines: 16
My boss came in in a panic today saying "Elm says my mail file is corrupt
and can't read it" !<>?
Trouble is, last time he read his mail, he typed e, apparently hit a few
returns (and good old emacs is modeless and entered em right in, unlike vi
which would have beeped at him :-) and got out and saved it and went home.
So today elm sees blank lines and pukes.
I haven't looked at a fix for this yet, but thought I'd point it out before
1.7 hits the streets, so to speak.
Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee
Internet: dave@csd1.milw.wisc.edu Uucp: uwvax!uwmcsd1!dave {o,o}
Csnet: dave%uwmcsd1@uwm Bellnet: +1 (414) 229-5133 \u/
ICBM: 43 4 58 N/ 87 55 52 W Usnail: 3200 N Cramer #E380, Milw WI 53211uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131051.AA05504@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:37:17 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 66 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111503.AA01966@tccc0.TFS> Date: 11 Sep 87 15:03:56 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102147.AA11935@ucbvax.Berkeley.EDU> Date: 10 Sep 87 10:21:53 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 48 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131051.AA05515@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:37:29 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 45
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03061@tccc0.TFS>
Date: 11 Sep 87 17:00:02 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 36
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11311@tccc0.TFS>
Date: 10 Sep 87 06:26:11 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071938.AA18228@crocodile.TFS>
Date: 7 Sep 87 19:38:32 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!hoptoad!sunny
From: sunny@hoptoad.uucp (Sunny David Kirsten)
Newsgroups: comp.mail.elm
Subject: Re: Status of Elm 1.7
Message-ID: <2880@hoptoad.uucp>
Date: 5 Sep 87 06:03:37 GMT
References: <753@hplabsz.HPL.HP.COM>
Reply-To: sunny@hoptoad.UUCP (Sunny David Kirsten)
Distribution: world
Organization: Astral Consultants, Marin County, CA
Lines: 6
I'm interested in obtaining a copy,
even if I have to take over distribution of it.
--
Sunny David Kirsten, Astral Consultants (415)457-7555
POB 459, Forest Knolls, CA 94933
USENET: {sun,ptsfa,well,lll-crg,ihnp4,ucsfcgl,nsc,frog}!hoptoad!sunnyuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131051.AA05525@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:37:40 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 66 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03082@tccc0.TFS> Date: 11 Sep 87 17:00:16 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131052.AA05537@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:37:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 66 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03089@tccc0.TFS> Date: 11 Sep 87 17:00:22 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 57 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131052.AA05551@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:38:02 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 70
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03096@tccc0.TFS>
Date: 11 Sep 87 17:00:26 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 61
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709101142.AA14113@tccc0.TFS>
Date: 10 Sep 87 11:42:12 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 52
Path: teknek!dual!ptsfa!ames!husc6!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Mike Khaw)
Newsgroups: comp.mail.elm
Subject: summary of Elm 1.5b bugs
Keywords: the bugs I've run into
Message-ID: <16414@teknowledge-vaxc.ARPA>
Date: 8 Sep 87 16:50:04 GMT
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 41
Posted: Tue Sep 8 09:50:04 1987
I don't recall which of the following I've already reported previously,
so here they all are:
- standout bar has leading and trailing '2' on vt100 - buggy termcap(?)
or elm's curses fails to interpret curses padding.
- bounce option generates uucp bang sender address even when elm is
configured for Internet style addresses.
- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!)
I have an ugly fix for this.
- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the
builtin one)
- "from" doesn't understand metacharacters unless blank lines separate
nonblank lines in .elmrc
- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc)
- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode
on terminal (like Concepts) that have more than 1-page screen memory)
- use "ks", "ke" termcap for (vt100) application cursor/keypad keys
- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a
"Subject:", ^W should erase the word left of the cursor but doesn't).
Probably a case of "raw" mode when "cbreak" would've been better.
- needs a "copy" vs. "move" option instead of the current "save" (move) option
- patched version retains read mail in inbox unless deleted or saved elsewhere
- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox)
- options screen input doesn't interpret "~" notation
- mail-only mode needs to have nl mapping turned on for ~h header editing.
- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns
- builtin editor thinks "(" ")" are shell metachars!
- can't modify an alias in the alias database
- from gets sender wrong even when elm gets it right (saved rn news articles)
- changing folders and then changing back to a nonempty inbox kills elm
and a wishlist item:
- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to
do this using a global flag that the ^Z signal handler looks at).
Mike Khaw
--
internet: mkhaw@teknowledge-vaxc.arpa
usenet: {uunet|sun|ucbvax|decwrl|uw-beaver}!mkhaw%teknowledge-vaxc.arpa
USnail: Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131052.AA05561@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:38:14 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 36
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03103@tccc0.TFS>
Date: 11 Sep 87 17:00:32 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709091145.AA01696@tccc0.TFS>
Date: 9 Sep 87 11:45:07 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 18
Path: teknek!dual!ptsfa!ames!aurora!labrea!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131053.AA05577@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:46:31 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 100
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01912@tccc0.TFS>
Date: 11 Sep 87 15:03:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102128.AA11365@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:20:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131053.AA05588@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:46:44 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 100
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111503.AA01946@tccc0.TFS>
Date: 11 Sep 87 15:03:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102131.AA11420@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 10:21:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 82
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131053.AA05599@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:27:54 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709101030.AA13234@tccc0.TFS> Date: 10 Sep 87 10:30:26 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709091722.AA10956@ucbvax.Berkeley.EDU> Date: 7 Sep 87 00:31:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ll-xn!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131054.AA05610@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:28:05 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 57 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11332@tccc0.TFS> Date: 10 Sep 87 06:26:23 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 48 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071301.AA16491@crocodile.TFS> Date: 7 Sep 87 13:01:40 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 39 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm,comp.mail.misc Subject: Status of Elm 1.7 Message-ID: <753@hplabsz.HPL.HP.COM> Date: 4 Sep 87 06:56:15 GMT Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Followup-To: comp.mail.elm Distribution: world Organization: Hewlett-Packard Laboratories Lines: 27 A number of people have asked me recently about the status of the promised version 1.7 of the Elm Mail System...well...it's pretty much ready to ship out - I'm just waiting for some final authorization from management about it all and then I'll be able to send the 10 or so tapes that I currently have. If you are contemplating sending me a mag tape for it, however, DON'T. In fact, I'd like to hear from some people to find someone that would be willing to be the new 'owner' of the Elm sources - last time I posted a request of this nature no-one seemed that enthused about it, but this time it's a bit more imperative, y'all. Also, this newsgroup has been changed to be unmoderated, so you can directly post to it -- if you have any oustanding bug reports or whatever on version 1.5 please feel free to toss 'em here and I'll try my best to get them into the final 1.7 release. But, whatever happens, I *must* give up the code by the 15th of this month due to some other committments here at Hewlett-Packard, so at that point I shall simply toss the code onto tape, make a 'shar' of the sources available via FTP, and wash my hands of it all... Methinks we've been here before, though...Hmmmmm -- Dave Taylor Hewlett-Packard Labs
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131054.AA05621@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:35:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111446.AA01797@tccc0.TFS>
Date: 11 Sep 87 14:46:50 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102054.AA10422@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 03:19:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!burdvax!udel!gatech!rutgers!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131054.AA05630@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:36:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01811@tccc0.TFS>
Date: 11 Sep 87 14:47:00 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102055.AA10483@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 04:19:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 73
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!cit-vax!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131055.AA05639@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:36:23 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 36
Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111447.AA01818@tccc0.TFS>
Date: 11 Sep 87 14:47:04 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 27
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709102056.AA10497@ucbvax.Berkeley.EDU>
Date: 10 Sep 87 05:58:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 18
Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bloom-beacon!mit-eddie!rutgers!seismo!uunet!nbires!isis!udenva!slindahl
From: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Newsgroups: comp.mail.elm
Subject: original elm patches (request for code)
Message-ID: <4160@udenva.UUCP>
Date: 5 Sep 87 17:13:17 GMT
Reply-To: slindahl@udenva.UUCP (Steve "Mr. Decision Sciences" Lindahl)
Distribution: usa
Organization: Universe of Diversity, Ltd.
Lines: 7
I missed collecting the original elm patches. Could someone please let me
know if they have them. I do not want to overload the lines. I am looking
for the site that is closest to this one. Thanks!
--
Steve J. Lindahl |UUCP {hplabs,seismo}...!hao!udenva!duorion!slindahl
University of Denver |BITNET slindahl@ducairuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131055.AA05654@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:36:33 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 76 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111447.AA01825@tccc0.TFS> Date: 11 Sep 87 14:47:08 GMT Sender: uucp@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709102056.AA10513@ucbvax.Berkeley.EDU> Date: 10 Sep 87 06:06:01 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 58 Path: uclachem!cepu!trwrb!scgvaxd!wlbr!voder!pyramid!decwrl!decvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709060838.AA09126@ucbvax.Berkeley.EDU> Date: 5 Sep 87 09:18:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 49 Path: uclachem!cepu!trwrb!sdcrdcf!oberon!bbn!husc6!sri-unix!ctnews!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131056.AA05663@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:46:55 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 100
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111659.AA03041@tccc0.TFS>
Date: 11 Sep 87 16:59:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11297@tccc0.TFS>
Date: 10 Sep 87 06:26:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709071714.AA17591@crocodile.TFS>
Date: 7 Sep 87 17:14:52 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709041957.AA12217@ucbvax.Berkeley.EDU>
Date: 2 Sep 87 06:14:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 64
Path: uclachem!cepu!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131056.AA05672@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:47:07 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 76 Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111700.AA03075@tccc0.TFS> Date: 11 Sep 87 17:00:12 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 67 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11325@tccc0.TFS> Date: 10 Sep 87 06:26:19 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 58 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709070812.AA14724@crocodile.TFS> Date: 7 Sep 87 08:12:36 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 49 Path: teknek!dual!ptsfa!ames!aurora!labrea!decwrl!pyramid!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <746@hplabsz.HPL.HP.COM> Date: 3 Sep 87 07:28:42 GMT References: <2581@trwrb.UUCP> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Distribution: usa Organization: Hewlett-Packard Laboratories Lines: 37 Marc Ries refers to two interesting problems in the utility shell scripts supplied with the Elm system: 1. 'messages' doesn't like when you're not on a machine that has $MAIL defined. I never thougth of that (!) and shall change it as suggested. Thanks! 2. the reason that 'trim-headers' isn't doing much for you is because you're handing it something that isn't a valid mail message, so it, correctly, isn't touching it. Let's look at the example message: > Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher > From: gallagher@husc4.HARVARD.EDU (paul gallagher) > Newsgroups: rec.arts.movies > Subject: Re: Westerns > Message-ID: <2778@husc6.UUCP> > Date: 29 Aug 87 09:19:09 GMT > References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> > Sender: news@husc6.UUCP > Reply-To: gallagher@husc4.UUCP (paul gallagher) > Organization: Harvard Univ. Science Center > Lines: 19 > > <text of article or letter> The problem, of course, is that it isn't an RFC-822 conformant message text, so the program cannot actually distinguish between the message 'header' (aka the "envelope") and the message 'body'! If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" at the beginning you'd find it chopped down quite a bit. Alternatively, you *could* modify the trim-headers script to know that "Path:" is also an 'enter-message-header-state' prefix (just hope that it doesn't occur in the *body* of any of the messages you have saved...) -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp
From: uucp@uclachem.UUCP (Unix-to-Unix copy program)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709131056.AA05681@ucbvax.Berkeley.EDU>
Date: 13 Sep 87 08:47:19 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 100
Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709111700.AA03068@tccc0.TFS>
Date: 11 Sep 87 17:00:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 91
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709100626.AA11318@tccc0.TFS>
Date: 10 Sep 87 06:26:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 82
Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709072101.AA18535@crocodile.TFS>
Date: 7 Sep 87 21:01:09 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 73
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp
From: uucp@dual.UUCP (UNIX-to-UNIX Copy)
Newsgroups: comp.mail.elm
Subject: Submission for comp-mail-elm
Message-ID: <8709031708.AA24123@sccc0.TFS>
Date: 3 Sep 87 17:08:08 GMT
Sender: uucp@ucbvax.BERKELEY.EDU
Lines: 64
Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!ries
From: ries@trwrb.UUCP (Marc Ries)
Newsgroups: comp.mail.elm
Subject: Error handling in messages + trim-headers
Message-ID: <2581@trwrb.UUCP>
Date: 31 Aug 87 23:43:19 GMT
Reply-To: ries@trwrb.UUCP (Marc Ries)
Distribution: usa
Organization: TRW Operations and Support Group
Lines: 53
I recently tried the "messages" shell script (never used it
before), and got the error message:
z[13]: test: argument expected
Turns out that on our machine (Pyramid 98x OS 4.0), the MAIL
variable (at least in the ucb universe) isn't set to anything, so
that messages balks at "if [ -f <nothing> ]; then".
It would be nice to try and anticipate some of the possible error
conditions. Locally, something like this works:
#! /bin/sh
if [ "$MAIL" = "" ]; then
if [ "$LOGNAME" = "" ]; then
echo "$0: need MAIL or LOGNAME variables set"
exit 1
else
if [ -d /usr/mail ]; then
MAIL=/usr/mail/$LOGNAME
else
MAIL=/usr/spool/mail/$LOGNAME
fi
fi
fi
...
ALSO, does "trim-headers" work for anybody else? If I pass
something like:
Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher
From: gallagher@husc4.HARVARD.EDU (paul gallagher)
Newsgroups: rec.arts.movies
Subject: Re: Westerns
Message-ID: <2778@husc6.UUCP>
Date: 29 Aug 87 09:19:09 GMT
References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP>
Sender: news@husc6.UUCP
Reply-To: gallagher@husc4.UUCP (paul gallagher)
Organization: Harvard Univ. Science Center
Lines: 19
<text of article or letter>
That's exactly what I get back (ie, no "trimming" of the mail
headers).
--
Marc A. Ries
sdcrdcf!---\
ihnp4!------\----- trwrb! --- riesuucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131057.AA05690@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:47:31 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 97 Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111659.AA03048@tccc0.TFS> Date: 11 Sep 87 16:59:57 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 88 Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709100626.AA11304@tccc0.TFS> Date: 10 Sep 87 06:26:06 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 79 Path: teknek!dual!ptsfa!ihnp4!cbosgd!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709071833.AA17815@crocodile.TFS> Date: 7 Sep 87 18:33:57 GMT Sender: usenet@ucbvax.BERKELEY.EDU Lines: 70 Path: teknek!dual!ptsfa!ames!think!husc6!rutgers!ukma!david From: david@ms.uky.edu (David Herron -- Resident E-mail Hack) Newsgroups: comp.mail.elm Subject: Re: Error handling in messages + trim-headers Message-ID: <7218@e.ms.uky.edu> Date: 4 Sep 87 21:41:07 GMT References: <2581@trwrb.UUCP> <746@hplabsz.HPL.HP.COM> Distribution: usa Organization: U of Ky, Math. Sciences, Lexington KY Lines: 59 In article <746@hplabsz.HPL.HP.COM> taylor@hplabsz.UUCP (Dave Taylor) writes: >2. the reason that 'trim-headers' isn't doing much for you is > because you're handing it something that isn't a valid mail > message, so it, correctly, isn't touching it. Let's look at > the example message: >> Path: trwrb!sdcrdcf!oberon!cit-vax!ll-xn!husc6!husc4!gallagher >> From: gallagher@husc4.HARVARD.EDU (paul gallagher) >> Newsgroups: rec.arts.movies >> Subject: Re: Westerns >> Message-ID: <2778@husc6.UUCP> >> Date: 29 Aug 87 09:19:09 GMT >> References: <4VAiZCy00VsCgjo0dX@andrew.cmu.edu> <2551@trwrb.UUCP> >> Sender: news@husc6.UUCP >> Reply-To: gallagher@husc4.UUCP (paul gallagher) >> Organization: Harvard Univ. Science Center >> Lines: 19 > The problem, of course, is that it isn't an RFC-822 conformant > message text, so the program cannot actually distinguish between > the message 'header' (aka the "envelope") and the message 'body'! > > If you were to add a line "From gallagher Thu Sep 3 00:26:56 PDT 1987" > at the beginning you'd find it chopped down quite a bit. Alternatively, > you *could* modify the trim-headers script to know that "Path:" is also > an 'enter-message-header-state' prefix (just hope that it doesn't occur > in the *body* of any of the messages you have saved...) Dave, I expect better from you ... Take a look at RFC-822 please. Header lines *ALL* are of the same form: name: [ information ] Where "name" is a construct that includes letters, dashes, dots, and a couple of other things... A "From " line doesn't have the required ':', and such cannot be considered as part of the header. The "From " line is an artifact from the old /bin/mail program, and lives on today as part of RFC-976 as the UUCP worlds' minimum envelope. The "From " and ">From " lines together make up the return-path to the sender (in the same sort of way that you're supposed to make a Return-path: header in the SMTP world). In today's world I think you're better served by having a proper From: line and have the user-agent key off of that. It's a misfeature to support the "From " line longer than necessary. Further ... Path: is not valid under RFC-822, but RFC-850 (or whatever the news format rfc is, I think there's a new version of this too..). The point is, if you're going to start quoting RFC's at everybody, then you oughta know what you're talking about. -- ----- David Herron, Local E-Mail Hack, david@ms.uky.edu, david@ms.uky.csnet ----- {uunet,cbosgd}!ukma!david, david@UKMA.BITNET ----- ----- Je parle francais comme une vache espagnole.
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/13/87)
Path: teknek!dual!ptsfa!ames!sdcsvax!ucbvax!uclachem.UUCP!uucp From: uucp@uclachem.UUCP (Unix-to-Unix copy program) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709131057.AA05699@ucbvax.Berkeley.EDU> Date: 13 Sep 87 08:47:43 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 137 Path: uclachem!cepu!trwrb!sdcrdcf!ucla-cs!zen!ucbvax!dual.UUCP!uucp From: uucp@dual.UUCP (UNIX-to-UNIX Copy) Newsgroups: comp.mail.elm Subject: Submission for comp-mail-elm Message-ID: <8709111520.AA02141@tccc0.TFS> Date: 11 Sep 87 15:20:24 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 128 Path: teknek!dual!ptsfa!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hplabsz!taylor From: taylor@hplabsz.HPL.HP.COM (Dave Taylor) Newsgroups: comp.mail.elm Subject: Re: summary of Elm 1.5b bugs Message-ID: <767@hplabsz.HPL.HP.COM> Date: 10 Sep 87 21:05:49 GMT References: <16414@teknowledge-vaxc.ARPA> Reply-To: taylor@hplabsz.UUCP (Dave Taylor) Organization: Hewlett-Packard Laboratories Lines: 117 Mike Khaw posts a list of problems with Elm 1.5b...my thoughts on 'em follow: >- standout bar has leading and trailing '2' on vt100 - buggy termcap(?) > or elm's curses fails to interpret curses padding. That's fixed. >- bounce option generates uucp bang sender address even when elm is > configured for Internet style addresses. That's a new one and probably isn't fixed. >- in "batch" mode, ^C gives a prompt to hit ^C once more (forever!) That's fixed. >- 4bsd job control: hangs on a pager pipe (i.e., when pager is not the > builtin one) That's new, but I believe it's fixed because of some other work I did with the 4.XBSD signal handling... >- "from" doesn't understand metacharacters unless blank lines separate > nonblank lines in .elmrc This is a new one... >- "batch" mode doesn't save copy in sent folder (doesn't read .elmrc) Deliberate - this isn't a bug - but it can be trivially changed by a conditional in the routine "save_copy" I believe. >- needs to use termcap "ti"/"te" if applicable (to force 1 page screen mode > on terminal (like Concepts) that have more than 1-page screen memory) This is arguable though - when I'm on a system with multiple screens of memory I *don't* want to force it to one-screen mode since then I lose the ability to move around and possibly use the other screens (for example to page up and have the message I'm replying to in the upper screen, and my edit session in the lower screen). >- use "ks", "ke" termcap for (vt100) application cursor/keypad keys That's still not in there because of the pain of adding general purpose conditionals to the already killer case statement in "elm.c". >- doesn't always obey 4bsd "new" tty conventions (e.g., when in editing a > "Subject:", ^W should erase the word left of the cursor but doesn't). > Probably a case of "raw" mode when "cbreak" would've been better. That works now. >- needs a "copy" vs. "move" option instead of the current "save" (move) option That is configurable -- if you're not in "berkeley mail emulation mode" (e.g. "resolve=ON" in your .elmrc) then S)aving a message will not result in it being marked for deletion. >- patched version retains read mail in inbox unless deleted or saved elsewhere That's a local problem - I've never had this problem myself. Wait until 1.7 is released, please. >- need shorthand for (read) mailbox (i.e, shorthand for ~/mbox) That's a good idea but isn't there. Though it DOES have "%" and "!" as shorthand for your incoming mailbox (e.g. C)hange mailbox "!" will get you into your default incoming mailbox). >- options screen input doesn't interpret "~" notation True enough. >- mail-only mode needs to have nl mapping turned on for ~h header editing. That's fixed. >- builtin editor miscounts on ^U (kill line), backspacing 1 too many columns That's fixed. >- builtin editor thinks "(" ")" are shell metachars! I don't understand what you're talking about here...is this with regard to how it does ^W backspacing? Or...? >- can't modify an alias in the alias database That's really a whole can of worms you're opening here, Mike! I would like to see Elm have a general purpose database facility for the aliases, including searching, updating, adding, deleting, and so on, but it just isn't there... >- from gets sender wrong even when elm gets it right (saved rn news articles) Again, this is news. >- changing folders and then changing back to a nonempty inbox kills elm Not on my machine. Perhaps this is an artifact of your patches? >and a wishlist item: >- automagic ^L screen refresh on return from 4bsd ^Z (I have an ugly way to > do this using a global flag that the ^Z signal handler looks at). This is a bit friendlier on the new version, but since I'm not using curses for Elm (that's be a NICE thing to add) it's rather difficult to know at any given time A) where we are and B) what the screen looked like at that point. The program also hops out of screen mode into line mode and back, so that would just compicate things too (e.g. the builtin editor from the main screen). In summary, most of what Mike is talking about is fixed in the latest version, and those few things that aren't would either be fairly easy patches for someone to make or are sort of slung along as part of the fundamental paradigm. -- Dave Taylor
uucp@dual.UUCP (UNIX-to-UNIX Copy) (09/14/87)
Path: teknek!dual!ptsfa!ames!husc6!necntc!rayssd!dpw
From: dpw@rayssd.RAY.COM (Darryl P. Wagoner)
Newsgroups: comp.mail.elm
Subject: Help My mailbox is running over.
Message-ID: <1505@rayssd.RAY.COM>
Date: 14 Sep 87 00:01:19 GMT
Sender: dpw@rayssd.RAY.COM (Darryl P. Wagoner @ Raytheon Company, Portsmouth RI)
Distribution: usa
Organization: Raytheon Company, Portsmouth RI
Lines: 9
Today I had 175+ mail messages that had been bounced off of the elm
mailing list. This number has been growing for about 2 weeks.
Can someone stop this madness, PLEASE?
--
Darryl Wagoner Raytheon Co.; Portsmouth RI; (401)-847-8000 x4089
best path {allegra|gatech|mirror|raybed2} -----\
next best {linus|ihnp4|uiucdcs} ------------------>!rayssd!dpw