otah...@gmx.ca writes:
>Could you please give a brief assesment of each, based on your experience?
It's been so many years since I last used xmh that I doubt I could give
an accurate assessment of it. But like you say, it's obsolete nowadays
anyway.
I use exmh as my main front end. It's buggy,
Ken Hornstein writes:
>if you get a message with a calendar invitation in it, what would
>you, as a user, _like_ to happen?
I would like repl to behave as normal. I would like repl with some
additional flags to instead invoke an external program to parse the
calendar data and construct a suitabl
valdis.kletni...@vt.edu writes:
>If you access your ~/Mail over NFS from a mixture of 32 and 64 bit boxes
>with a mix of old and new nmh's with different limits, Something Evil
>will happen to your .mh_sequences
Bad things already happen when you access your mail over NFS with MH. Not
all of
Ken Hornstein writes:
>>CentOS 5 is on Automake 1.7, but I upgraded to build
>>mhfixmsg once I figured out what the problem was...
>
>It's worth noting that Automake 1.7 was released in September ... of 2002.
>
>Also, versions of Automake older 1.11.6 and 1.12.2 have a security issue
>in their ge
Lyndon Nerenberg writes:
>The sad but inevitable facts of life say you have to implement fcntl()
>locking for POSIX portability, but should defer to anything else if you
>know the system supports it. This means flock() is the de facto on UNIX.
>Wrap it all up in mh_lock() or something similar and
Ken Hornstein writes:
>>What it doesn't mention is that the resulting train wreck can mangle other
>>sequences in the .mh_seq file as well. Also, should we change that text
>>to say "do not use rcvstore without an external locking mechanism'? It's
>>perfectly save to use it from procmail with u
Ralph Corderoy writes:
>>MIME messages are specified in RFC-2045 thru RFC-2049
>
>`through'! ;-)
If we're being picky about it, 'to'! :-)
Tet
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-w
berg...@merctech.com writes:
>I use a perl wrapper around "repl" which examines the headers to determine
>which of my accounts received the mail. Based on the account name, the
>wrapper sets environment variables to contain different valies for the
>From, Reply-To, and Fcc headers and the signatu
Robert Elz writes:
>So, if you have
>
>moreproc: less
>
>then when moreproc is needed, we'd look for
>
>less: -p
>
>(or whatever) in the profile, and get the args that way.
But that approach only lets you supply a single set of default
arguments per progam. How then do you invoke the same progra
Ken Hornstein writes:
>What is the deal with VISUAL and EDITOR? I always set EDITOR; I've never
>set VISUAL. I've never understood what the difference is.
EDITOR specifies a line editor (ed, ex, etc). VISUAL specifies a full
screen editor (vi, emacs etc). Virtually no one uses line editors any
Lyndon Nerenberg writes:
>On 2012-12-30, at 2:47 PM, Ken Hornstein wrote:
>
>> 2.69 was released in April of
>> 2012.
>
>Haven't seen anything younger than 2.69 for ages ... Do it.
There's plenty about. The 2.61 requirement already necessitates
compiling autoconf on RHEL5 (which only has up to
Lyndon Nerenberg writes:
>> So, the _right_ thing to do here is not clear, at least to me. The MIME
>> RFCs don't spell out what to do when you receive a message that is
>> malformed; are you supposed to error out?
>
>Yes.
In which case, how are you supposed to read the message? I know it's
nmh-workers-requ...@nongnu.org writes:
>Your membership in the mailing list Nmh-workers has been disabled due
>to excessive bounces The last bounce received from you was dated
>08-Nov-2012. You will not get any more messages from this list until
>you re-enable your membership. You will receive
nmh-workers-requ...@nongnu.org writes:
>Your membership in the mailing list Nmh-workers has been disabled due
>to excessive bounces The last bounce received from you was dated
>08-Nov-2012. You will not get any more messages from this list until
>you re-enable your membership. You will receive
Lyndon Nerenberg writes:
>I would like to change this so that ${PAGER} takes precedence over
>the compile time default, with moreproc in .mh_profile overriding
>${PAGER}. Objections?
Sounds good to me.
Tet
___
Nmh-workers mailing list
Nmh-workers@no
Ken Hornstein writes:
>Your draft file does not contain a From: header; this version of nmh
>requires that all draft messages contain one. See the default
>component templates for examples and insure that your draft contains
>a valid From: header.
s/insure/ensure/
Tet
Ken Hornstein writes:
>>A possible way to solve the access to MIME parts problem
>>might be to store the parts as messageNumber.partNumber*
>>Creation of these parts would be optional, and eat space,
>>but it would make indexing/grepping easy.
>
>You know ... given that & Norm's comments, that ac
Paul Fox writes:
> > $(libdir)/ap -format '%(decode(friendly{text}))' ''
>
>you're absolutely right that i've been tweaking the same forms for
>probably 20 years now, and totally missed this modernization.
Ha! You and me both. Having just updated my long untouched scanformat
file, scan now corr
valdis.kletni...@vt.edu writes:
>> No `#'? How about just always send to the user's shell from the
>> password entry with a -c, as distinct from /bin/sh.
>
>The problem is that some people (at least in the Elder TImes) would have
>their login shell set to /bin/csh but they'd want their scripty t
Ken Hornstein writes:
>>That's not strictly true, either. Both isspace() and iscntrl() return
>>zero for me for everything above 127. But although the subject line of
>>your message is correctly decoded by scan, it's broken when decoded by
>>show (and by exmh, which I'm guessing is just shelling
Ken Hornstein writes:
>Well, I guess it depends on your perspective. Is this a portability
>problem? Linux (the one I tested) returns 0 for isspace() &&
>iscntrl() > 127. If that's true for you, it works fine.
That's not strictly true, either. Both isspace() and iscntrl() return
zero for me f
Paul Vixie writes:
>did you know that if there's a corrupt .mh_sequences file,
>"rcvstore" won't run?
Sadly, yes I do :-( Given that all of my mail is stored in folders
on arrival using rcvstore, it's a pain in the arse when a broken
.mh_sequences prevents that from happening...
Tet
__
David Levine writes:
>> If people think it's a good idea I wouldn't mind shipping this with
>> nmh, but I'm not sure where is should go; right now nmh doesn't have
>> a dependency on perl. We could always put it in the "docs" directory.
>> Anyway, please let me know what you think!
>
>I'm fine w
David Levine writes:
>If it's not used by exmh (and mh-e and xmh?), how about if we
>disable it by default?
OK. I can assure you that exmh doesn't use it (at least not in any
critical way) because it's broken for multiple concurrent replies,
and I frequently reply to many messages concurrently w
Jerrad Pierce writes:
>An edge-case issue with @ be it in . ~/ or `mhpath +`
>is that it does not allow for multiple concurrent replies.
Hell, it's not even that much of an edge case. It's a reasonably
common situation, and it silently fails by simply relinking the
@ for each new reply. Unless a
Ken Hornstein writes:
>My thinking was that since bounces go to the SMTP envelope-from,
>bounces should go back to the person who wrote the message. In the
>example above, I'd want to know about a bounced email, rather than
>my secretary
If you're the sort of person that has a secretary send em
David Levine writes:
>The old docs, ps converted to pdf, are now in docs/historical/
I notice we've also got plain text and PDF versions of Rose/Romine's
"How to process 200 messages a day and still get some real work done"
paper in there too. It might be worth grabbing the TeX source while
it's
Ken Hornstein writes:
>Do people like the idea of:
>
>- A dedicated function %(localmbox)
>
>- A pseudo component %{localmbox}
>
>- Extra primitives to build the default local mailbox (%(myname), %(myhost)).
I'm not sure there's enough between them to make much of a difference.
You might as well
Robert Elz writes:
>If all you want from mh is "show/next/comp/repl/rmm" you might just as
>well use thunderbird, or sylpheed, or even outlook express - they all
>provide methods to read, delete, reply, ... to e-mail, and usually with
>a user interface that is easier to master.
Don't be so sure
paul vixie writes:
>On 2/6/2012 4:20 PM, Tethys wrote:
>> If we do so, it will of course have to allow arbitrarily deep nesting,
>> so we can address things like 53.6.4.1 (the 1st part of the 4th part of
>> the 6th part of message #53).
>
>ouch! my eyes!
Yes, but r
paul vixie writes:
>i think we're going to end up extending the "message number" to be a
>decimal not an integer, as in "53.6" to get MIME part 6 of message
>number 53. any place that accepts a "message number" will have to
>understand this
If we do so, it will of course have to allow arbitraril
Lyndon Nerenberg writes:
>As for internal locking, it's a toss-up between flock and lockf. To
>me the tie breaker is which of the two gets along best with network
>mounted filesystems these days (and think AFP and CIFS in addition
>to NFS).
In case anyone thinks this is hypothetical, it's not. B
ra...@hep.wisc.edu writes:
> > I don't have one of those. From the savannah tarball:
> >
> > local@riva:~/nmh-1.4% find . -name 'dtimep*' -print
> > ./sbr/dtimep.lex
>
>Really?
>
>$ wget http://download.savannah.nongnu.org/releases/nmh/nmh-1.4.tar.gz
>[...]
>$ tar -ztvf
Ken Hornstein writes:
>>That was fixed by installing ncurses-devel, but we should really be
>>checking for that at configure time. Also:
>
>I think we do, right? I mean, we check for tgetent in configure.
>What did configure say when you ran it without ncurses-devel installed?
checking
On CentOS 5, I get the following compile time errors:
gcc -s -o mhlist mhlist.o mhparse.o mhcachesbr.o mhlistsbr.o mhmisc.o
mhfree.o ftpsbr.o termsbr.o md5.o ../config/version.o ../config/config.o
../mts/libmts.a ../sbr/libmh.a
termsbr.o: In function `read_termcap':
te
Aleksander Matuszak writes:
>echo Enclosed | nail -a some.file some...@somewhere.net
Yep, that'd be nice. I've generally used metasend to achieve the same
end result, but I'd hardly say it was a pleasant experience...
Tet
___
Nmh-workers mailing lis
Ken Hornstein writes:
>People aren't so crazy about adding more text formatting smarts to mhl;
>that makes sense to me, I think whatever code I add wouldn't be as good
>as something like fmt or par, and that's keeping with the toolset idea
>of nmh.
I'm more of the opinion that mhl *should* do so
Joel Uckelman writes:
>Or, alternatively, I'd be happy for someone to package par for Fedora.
Heh. You have no idea how long that one's been on my TODO list. One
day I might actually have the spare time to get around to it...
Tet
___
Nmh-workers mail
Joel Uckelman writes:
>How are you guys using par calling it? From a script? manually?
>From within vi:
!}par
or
!Gpar
Tet
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Paul Fox writes:
>for instance, "par" purports to solve this pretty well
>already: http://www.nicemice.net/par . (i've never tried
>it, but i keep the link around in case i need to.)
I swear by par and use it every day. It's basically just fmt(1) that
understands quoting and handles it properl
Earl Hood writes:
>Apparently, CentOS 5.7 version of autoconf is older than
>what the nmh build process says is required. CentOS 5.7
>provides autoconfig 2.59 but nmh is configured to require
>2.61 and later.
Yep, I've just run into this (also on CentOS). No problem, I thought,
I'll just bite t
Ken Hornstein writes:
>So, I have some thoughts in this direction, but I'm wondering: what do
>you want out of repl in terms of better MIME handling?
#1 is for base64 and quoted-printable to be decoded into UTF-8 before
being included in the reply body. #2 would be for attachments to be
optional
ra...@hep.wisc.edu writes:
> > The problem with that approach is that sometimes the text part just says
> > ``There is no text part, use an HTML capable mail reader''. I'm seeing
> > more of them these days.
>
>Really? I've been reading text/plain over text/html with EXMH for years and
>recentl
o use with regexps to select
from a list would be good enough for most. Personally, I use over 500
addresses, so it wouldn't work well for me without a fair amount of
work :-)
>>On the other hand, Tethys' X-Envelope-From is just Return-Path and
>>should be there already.
>
>Y
Ken Hornstein writes:
>>That relies on some sendmail.mc config to add an X-Envelope-To header
>>to my mail on the way through:
>
>So all I have to do is get Google to change their entire server
>configuration to match the (lack of) capabilities in my mailer.
>Problem solved!
Errr... no. This has
27;s already fairly easy to do this with replcomps:
From: %<{X-Envelope-To}Tethys %{X-Envelope-To}%|Tethys
%>
That relies on some sendmail.mc config to add an X-Envelope-To header
to my mail on the way through:
LOCAL_CONFIG
HX-Envelope-From: $f
HX-Envelope-To
Jon Fairbairn writes:
>> The idea makes me wonder if git could be used as a mailstore.
>> With a blob for each message and tag-blobs for classifying
>> messages. Could be nice if you can push and pull mail between
>> machines.
>
>That does have a certain appeal.
It's something I've been thinking
valdis.kletni...@vt.edu writes:
>One of you probably has MM_CHARSET defined and the other doesn't. 'scan'
>(IIRC) doesn't even try to do 2047 quoting if that variable isn't set.
Nope:
leto:~% MM_CHARSET=1 scan +spam/unsure 652
652 2011.12.05 "=?UTF-8?Q?Priority= =?UTF-8?Q?
Ken Hornstein writes:
>You say that rpm says that the version is 1.3-3; is that some snapshot
>version? Or actually based on 1.3?
It's 1.3, and it's the third build that Fedora have made from that release.
It's usually rebuilt if an extra patch is added or if there's an update to
a static libra
Ken Hornstein writes:
> Specifically, scan can decode RFC 2047 headers, but it seems that show
> cannot (okay, mhshow seems to decode some headers, but not others).
I'd say you've got that the wrong way round:
leto:~% scan `pick -from PriorityClubeStatement`
461 2011.05.19
Does anyone have a pointer to a pretty printing program for email?
I mostly use exmh, and its print function just converts the raw text
of the message to postscript and prints it. The problem with that is
a) it's full of useless "Received:" headers that I simply don't care
about, and b) not MIME a
Peter Maydell writes:
>Just use rsync to copy the laptop's idea of the situation
>onto the desktop again? (And vice-versa in the morning.)
Bleurgh! It's a difficult problem to solve. Probably the best
way is to use a DVCS for your mail store. They're generally
explicitly designed for of
Joel Reicher writes:
>On a more practical note, inc is not a silver bullet for updating the
>index, since slocal/rcvstore, refile, and anno all change headers/folders.
Seconded. Indeed, I can't remember the last time I used inc. All of my
mail is stored with rcvstore.
Also, I'm not convinced th
Joel Uckelman writes:
>(E.g., acceptance tests would be easiest to do in something other
>than C. It would be good if those were done in whatever language
>people were most likely to contribute tests in. So what language?)
Bourne shell. It may not be the most expressive language out there,
or ev
Chad Walstrom writes:
>Would it be good enough to insert a header that refers to a path of
>the file containing the recorded BCC?
>
> X-MH-Bcc-Path: ~/Mail/.ahu7216hlkuq6.bcc
>
>If this were included while forwarding the message, it wouldn't really
>matter.
Arguably it might. The original
55 matches
Mail list logo
