Kevin Cosgrove | 16 Apr 06:25 2012
X-Face
Picon

Aging Dependencies?

Hiya,

Anyone heard of plans regarding what to do about aging
dependencies for exmh?  I'm trying to bring a Fedora 16 machine
up to capable, which includes installing exmh.  I can live
without faces, especially now that Outlook 2010 finally has
faces -- how many decades has it taken them to catch up, er, uh
innovate?

I found metamail for Fedora 16 on-line, maybe it was at pkgs.net?

expectk has been dropped by the author(s) of expect, as of
version 5.45, in lieu of tclsh run in the right way ("Please use
tclsh with package require Tk and Expect instead of expectk").
But, Fedora 14 has expectk and I'm going to package it in a way
so I can get a functional expectk executable and support for
that, but without conflicting with the Fedora 16 expectk package,
which oddly no longer contains expectk.

FWIW, I'm doing all this with an exmh CVS download with the
newest component dated 2012-01-23, if that's important.

Cheerio....

--
Kevin
Ken Hornstein | 16 Apr 15:14 2012
X-Face
Picon
Picon

Re: Aging Dependencies?

>Anyone heard of plans regarding what to do about aging
>dependencies for exmh?  I'm trying to bring a Fedora 16 machine
>up to capable, which includes installing exmh.  I can live
>without faces, especially now that Outlook 2010 finally has
>faces -- how many decades has it taken them to catch up, er, uh
>innovate?

I _think_ for that all you need is compface/uncompface, which exmh
includes.

>I found metamail for Fedora 16 on-line, maybe it was at pkgs.net?

MacPorts includes a "mmencode" package which has the piece you
really need (you don't really need all of metamail).  There's a
built-in base64 encoder/decoder in exmh, but there is a file
descriptor leak in there somewhere; I never was able to track it
down and installing mmencode was just easier.  Perhaps one of us
should consider creating an RPM for that?

>expectk has been dropped by the author(s) of expect, as of
>version 5.45, in lieu of tclsh run in the right way ("Please use
>tclsh with package require Tk and Expect instead of expectk").
>But, Fedora 14 has expectk and I'm going to package it in a way
>so I can get a functional expectk executable and support for
>that, but without conflicting with the Fedora 16 expectk package,
>which oddly no longer contains expectk.

>From what I remember .... the only use of expect/expectk is for handling
MIME external-body messages.  I haven't gotten one of those in forever,
and I think the last time I _did_ the support didn't work.  Do you get
(Continue reading)

Andreas Wittkemper | 17 Apr 10:33 2012

Re: Aging Dependencies?


Am 16.04.2012 um 15:14 schrieb Ken Hornstein:

FWIW, I'm doing all this with an exmh CVS download with the
newest component dated 2012-01-23, if that's important.

That is itself part of the problem ... exmh hasn't gotten a lot of
love lately.  A new release is overdue.



Is there anyone still around who could do it ? Since nmh speeds up again it would be a good starting point for exmh too.
For example our it depar tment refuses to install development versions.

regards

  Andreas




Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Detlef Eppig - Vorsitzender des Aufsichtsrats: Dominique Gaillard


_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 17 Apr 15:12 2012
X-Face
Picon

Re: Aging Dependencies?

>Is there anyone still around who could do it ? Since nmh speeds up again
>it would be a good starting point for exmh too.  For example our it
>department refuses to install development versions.

There are a couple people who still makes changes to exmh.  (The
last change to the exmh repository was two months ago).  I kinda
pestered one of those people to crank out a new exmh release on the
nmh-workers list, but I'm not sure that's going to happen.  So yes,
there are people who have the ability and access, but lack the time
or desire to do so.

I can say from my experience with nmh you kinda need someone who's
willing to do the grunt work of cranking out a release (and it's more
work than you think).

--Ken
Valdis.Kletnieks | 18 Apr 11:19 2012
Picon

Re: Aging Dependencies?

On Tue, 17 Apr 2012 09:12:57 -0400, Ken Hornstein said:

(adding exmh-workers to the list)

> There are a couple people who still makes changes to exmh.  (The
> last change to the exmh repository was two months ago).

I'm one of those people - unfortunately, though I can make a release
show up in the CVS tree, I have no clue how to make one pop *out* of
the CVS tree...

Anybody know of anything that should be iadded to the exmh CVS tree
before we cut a release? Or is it ready to cut a 2.7.3/2.8/3.0?

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 18 Apr 15:26 2012
X-Face
Picon

Re: Aging Dependencies?

>I'm one of those people - unfortunately, though I can make a release
>show up in the CVS tree, I have no clue how to make one pop *out* of
>the CVS tree...

Is the issue changing the web page?  I guess we need to bug Brent Welch
about that.  Or is there something else?

>Anybody know of anything that should be iadded to the exmh CVS tree
>before we cut a release? Or is it ready to cut a 2.7.3/2.8/3.0?

Actually ... one issue comes to mind.

When testing out replyfilter, I occasionally run across messages
that make it output warnings (see my email about Andreas's message).
That makes Exmh refuse to pull up an editor ... repl completes
successfully with an exit code of 0 and the draft is okay, but I
guess it's unhappy about the stuff on standard error.  Is my
understanding correct?  If so ... does that make sense?  Should my
replyfilter (or repl) do something else with warnings?

--Ken
Valdis.Kletnieks | 18 Apr 18:34 2012
Picon

Re: Aging Dependencies?

On Wed, 18 Apr 2012 09:26:44 -0400, Ken Hornstein said:
> >I'm one of those people - unfortunately, though I can make a release
> >show up in the CVS tree, I have no clue how to make one pop *out* of
> >the CVS tree...
>
> Is the issue changing the web page?  I guess we need to bug Brent Welch
> about that.  Or is there something else?

Well, if I knew what else was involved, I could answer that question.  I may actually
have the needed permissions to do all of it - but I've never pushed out an exmh
release so I don't know.

Arthur Dent: You know, it's at times like this, when I'm stuck in a Vogon
    airlock with a man from Betelgeuse, about to die of asphyxiation in deep space,
    that I really wish I'd listened to what my mother told me when I was young.
Ford Prefect: Why? What did she tell you?
Arthur Dent: I don't know! I didn't listen!

_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Ken Hornstein | 18 Apr 18:47 2012
X-Face
Picon

Re: Aging Dependencies?

>Well, if I knew what else was involved, I could answer that question.
>I may actually have the needed permissions to do all of it - but I've
>never pushed out an exmh release so I don't know.

Heh, understood.  I guess Brent was the only one who ever did it?  You
(or I could do it) could email him to ask him about it.

I get the impression that there's no real release process in exmh, unlike
other packages.  I say: tar up the tree and see if that's makes something
close to the release tarball out there today.

--Ken
Welch, Brent | 19 Apr 00:44 2012

RE: Aging Dependencies?

The release tarball is created via the Makefile in the CVS tree.  There is a version.csh script that explains
what to do.  I'm happy to help/advise, but I think it would be better for someone else to take it for a test
drive.  As I said earlier, I'll update the html files on www.beedub.com/exmh when you guys are ready.

--
Brent

-----Original Message-----
From: exmh-workers-bounces <at> redhat.com [mailto:exmh-workers-bounces <at> redhat.com] On Behalf Of Ken Hornstein
Sent: Wednesday, April 18, 2012 9:47 AM
To: Discussion list for EXMH users; exmh-workers <at> redhat.com
Subject: Re: Aging Dependencies?

>Well, if I knew what else was involved, I could answer that question.
>I may actually have the needed permissions to do all of it - but I've
>never pushed out an exmh release so I don't know.

Heh, understood.  I guess Brent was the only one who ever did it?  You
(or I could do it) could email him to ask him about it.

I get the impression that there's no real release process in exmh, unlike
other packages.  I say: tar up the tree and see if that's makes something
close to the release tarball out there today.

--Ken

_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Welch, Brent | 18 Apr 18:42 2012

RE: Aging Dependencies?

Let me know what I can do to help.  In theory the Makefile captures most of the mechanics to generate a tarball,
and I can update www.beedub.com/exmh.  Look at version.csh for hints.  You'll want to update some of the
files like html/index.html and html/software.html by hand.

I'm looking at my CVS repository and I have a small number of changes I've accumulated.  You'd want to vet
those changes to see if they work OK for you.  It appears I added a number of timing things to the log, and I
removed the Fcache_RedisplayUnseen variable trace and do a more direct update in sequences.tcl. 
Frankly, I'm not sure that's perfect so you'd need to validate that.  I'm attaching the output of "cvs diff"
to this email.

I suggest that someone do the CVS commits to change the version to 2.8.0 (e.g.) and build the tar file - and
test it.  I will pull that and use the html files to update www.beedub.com/exmh.  I'll have to see about
updating sourceforge with the new tarball.

But, sadly I have to admit that I stopped using exmh about a year ago.  A mobile work pattern puts me in a Windows
laptop environment for a big chunk of time, and all my Linux/BSD machines are in a server room.  When the
Panasas IT guys upgraded our exchange server to require encrypted channels, and my desktop (which I now
don't use) got a new Ubuntu distribution, I failed to put my elaborate email tool chain back together.  So
I've punted to the dark side.  I even read email on my iphone sometimes.

--
Brent

-----Original Message-----
From: exmh-users-bounces <at> redhat.com [mailto:exmh-users-bounces <at> redhat.com] On Behalf Of Ken Hornstein
Sent: Wednesday, April 18, 2012 6:27 AM
To: Discussion list for EXMH users
Cc: exmh-workers <at> redhat.com
Subject: Re: Aging Dependencies?

>I'm one of those people - unfortunately, though I can make a release
>show up in the CVS tree, I have no clue how to make one pop *out* of
>the CVS tree...

Is the issue changing the web page?  I guess we need to bug Brent Welch
about that.  Or is there something else?

>Anybody know of anything that should be iadded to the exmh CVS tree
>before we cut a release? Or is it ready to cut a 2.7.3/2.8/3.0?

Actually ... one issue comes to mind.

When testing out replyfilter, I occasionally run across messages
that make it output warnings (see my email about Andreas's message).
That makes Exmh refuse to pull up an editor ... repl completes
successfully with an exit code of 0 and the draft is okay, but I
guess it's unhappy about the stuff on standard error.  Is my
understanding correct?  If so ... does that make sense?  Should my
replyfilter (or repl) do something else with warnings?

--Ken

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
? .exmhinstall
? DIFF.apr.2012
? Tar.exclude
? exmh
? exmh-2.4.tar.gz
? exmh-2.5.tar.gz
? exmh-2.6.1.tar.gz
? exmh-2.6.2.tar.gz
? exmh-2.6.3.tar.gz
? exmh-2.6.tar.gz
? exmh-2.7.0.tar.gz
? exmh-2.7.2.tar.gz
? exmh-async
? exmh-bg
? exmh-strip
? ftp.expect
? html-2.4.tar.gz
? html-2.5.tar.gz
? html-2.6.1.tar.gz
? html-2.6.2.tar.gz
? html-2.6.3.tar.gz
? html-2.6.tar.gz
? html-2.7.0.tar.gz
? html-2.7.2.tar.gz
? inc.expect
? lib/flist.tcl.new
? lib/html_content.tcl.good
? lib/html_content.tcl.new
? lib/main.tcl.good
? lib/main.tcl.new
? lib/mime.tcl.good
? lib/mime.tcl.new
? lib/msg.tcl.good
? lib/msg.tcl.new
? lib/seditExtras.tcl.good
? lib/seditExtras.tcl.new
? lib/html/Tar.exclude
? lib/html/exmh.CHANGES.txt
? misc/jpilot-lookup.tcl
? misc/query_jpilot.sh
Index: lib/fcache.tcl
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/fcache.tcl,v
retrieving revision 1.13
diff -r1.13 fcache.tcl
71c71,72
<     trace variable flist wu Fcache_RedisplayUnseen
---
>     # This is an expensive trace.  See SeqSetCount
>     # trace variable flist wu Fcache_RedisplayUnseen
99c100
< proc Fcache_RedisplayUnseen { array elem op } {
---
> proc Fcache_RedisplayUnseen { seq } {
102,103c103
<         set force [scan $elem "seqcount,%s,$mhProfile(unseen-sequence)" folder]
< 	Fcache_Display $force
---
> 	Fcache_Display [expr {"$seq" == "$mhProfile(unseen-sequence)"}]
Index: lib/mh.tcl
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/mh.tcl,v
retrieving revision 1.60
diff -r1.60 mh.tcl
580a581,586
>   Exmh_Debug Mh_SequenceUpdate $folder $how $seq $msgids $which
>   Mh_SequenceUpdateTimed $folder $how $seq $msgids $which
>   Exmh_Debug Mh_Sequence Update complete
> }
> 
> proc Mh_SequenceUpdateTimed { folder how seq {msgids {}} {which public}} {
Index: lib/msg.tcl
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/msg.tcl,v
retrieving revision 1.36
diff -r1.36 msg.tcl
118,121c118,125
<     Ftoc_ClearCurrent
<     set oldcur [Seq_Msgs $exmh(folder) cur]
<     Mh_SetCur $exmh(folder) $msgid
<     set lineno [Ftoc_FindMsg $msgid]
---
> Exmh_Debug Ftoc_ClearCurrent [time Ftoc_ClearCurrent]
> #    Ftoc_ClearCurrent
> Exmh_Debug Seq_Msgs [time {set oldcur [Seq_Msgs $exmh(folder) cur]}]
> #    set oldcur [Seq_Msgs $exmh(folder) cur]
> Exmh_Debug Mh_SetCur [time {Mh_SetCur $exmh(folder) $msgid}]
> #    Mh_SetCur $exmh(folder) $msgid
> Exmh_Debug Ftoc_FindMsg [time {set lineno [Ftoc_FindMsg $msgid]}]
> #    set lineno [Ftoc_FindMsg $msgid]
Index: lib/ps.tcl
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/ps.tcl,v
retrieving revision 1.1
diff -r1.1 ps.tcl
66a67
>     darwin	-
Index: lib/sequences.tcl
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/sequences.tcl,v
retrieving revision 1.24
diff -r1.24 sequences.tcl
177c177
<     # This trace is crude, and now we do all the updating in
---
>     # This trace is expensive, and now we do all the updating in
189c189
<     ldelete flist($seq) $folder
---
>     set ix [lsearch $flist($seq) $folder]
191c191,193
<         lappend flist($seq) $folder
---
>         if {$ix < 0} {
>           lappend flist($seq) $folder
>         }
193a196,197
>     } elseif {$ix >= 0} {
>         ldelete flist($seq) $folder
219a224,230
> # This procedure replaces an expensive trace on the flist var from fcache.tcl
> 
> proc SeqSetCount {folder seq count} {
>   global flist mhProfile
>   set flist(seqcount,$folder,$seq) $count
>   Fcache_RedisplayUnseen $seq
> }
231c242
<     set flist(seqcount,$folder,$seq) 0
---
>     SeqSetCount $folder $seq 0
279c290
<     set flist(seqcount,$folder,$seq) [expr $new + $num]
---
>     SeqSetCount $folder $seq [expr {$new + $num}]
304c315
< 	set flist(seqcount,$folder,$seq) 0
---
>         SeqSetCount $folder $seq 0
309c320,321
<     set flist(seqcount,$folder,$seq) $newnum
---
> Exmh_Debug flist(seqcount) [time {
>     SeqSetCount $folder $seq $newnum
311,312c323,325
<     if {![info exist flist($seq)] || ([lsearch $flist($seq) $folder] < 0)} {
< 	lappend flist($seq) $folder
---
>     if {![info exist flist($seq)]} {
>         # SeqCount will append $folder to flist($seq) if necessary
> 	set flist($seq) {}
314c327,328
<     SeqCount $folder $seq
---
> }]
>     Exmh_Debug SeqCount $folder $seq [time {SeqCount $folder $seq}]
320c334
< 	Fdisp_HighlightUnseen $folder
---
> 	Exmh_Debug Fdisp_HighlightUnseen [time {Fdisp_HighlightUnseen $folder}]
352c366,368
<     Seq_Set $folder $seq [Mh_Sequence $folder $seq]
---
> Exmh_Debug Mh_Sequence $folder $seq [time {set s [Mh_Sequence $folder $seq]}]
> #    Seq_Set $folder $seq [Mh_Sequence $folder $seq]
> Exmh_Debug Seq_Set $folder $seq [time {Seq_Set $folder $seq $s}]
Index: lib/html/index.html
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/html/index.html,v
retrieving revision 1.30
diff -r1.30 index.html
66,69c66,67
<   <li><a HREF="http://www.ics.uci.edu/~mh/book/">Jerry Peek's MH &amp;
<       xmh book</a>, which includes 
<       <a HREF="http://www.ics.uci.edu/~mh/book/exmh/">chapters about
<       exmh</a>. 
---
>   <li><a HREF="http://rand-mh.sourceforge.net/book/">Bill Wohler and Jerry Peek's MH &amp;
>       nmh book</a>, which includes chapters about exmh.
123c121
<         <li><a HREF="http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/mime-faq/top.html">MIME
---
>         <li><a HREF="http://www.newt.com/faq/mh.html">MH
125,131d122
< 
<         <li><a HREF="http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/mh-faq/top.html">MH
< 	    Frequently Asked Questions</a> 
< 
<         <li><a HREF="http://www.cis.ohio-state.edu/hypertext/faq/usenet/tcl-faq/top.html">TCL
< 	    Frequently Asked Questions</a> 
< 
Index: lib/html/software.html
===================================================================
RCS file: /cvsroot/exmh/exmh/lib/html/software.html,v
retrieving revision 1.31
diff -r1.31 software.html
43,46c43,45
<       HREF="ftp://ftp.ics.uci.edu/pub/mh">mh-6.8.tar.Z</a> 
<   <dd>The current version of MH (standard with some UNIX systems).  Due to security
<     issues with the handling of attachments, it is <em>strongly</em> recommended
<     that you <b>use the latest nmh</b>.
---
>       HREF="http://sourceforge.net/projects/rand-mh/">rand-mh</a> 
>   <dd>The original MH mail package.  This is also the web site for the
>       <a href="http://rand-mh.sourceforge.net/book/">MH and nmh book</a>
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Andy Bradford | 19 Apr 04:27 2012

Re: Aging Dependencies?

Thus said "Welch, Brent" on Wed, 18 Apr 2012 16:42:35 -0000:

> When  the Panasas  IT guys  upgraded  our exchange  server to  require
> encrypted channels, and  my desktop (which I now don't  use) got a new
> Ubuntu distribution,  I failed  to put my  elaborate email  tool chain
> back together. So I've  punted to the dark side. I  even read email on
> my iphone sometimes.

I had  a stint with the  dark side for a  bit, but I couldn't  stand it.
Eventually  I  discovered  Davmail,  and  while  it's  not  the  perfect
solution,  it  does  allow   integration  with  Exchange  and  encrypted
channels.

Andy
Klaus Elsbernd | 20 Apr 11:28 2012
X-Face
Picon
Picon

Re: Aging Dependencies?

exmh-users-request <at> redhat.com said:
> That is itself part of the problem ... exmh hasn't gotten a lot of love
> lately.  A new release is overdue.
I have to defend my use of exmh against the majority of thunderbird and
outlook users, using it since Nov 1993 and I'm quite happy with it.

Releasing a new version with faster decoding support of encoded attachments
would help a lot.
Since thunderbird, outlook and apple mail users don't care about the size of
their mail, decoding of 5MB "messages ... bloated" with
"MIME/multipart/HTML/RichText/PDF multimedia monstrosities"
(Michael O'Donnell) lasts long on my aged sparc/solaris environment.

And if I may add a second wish, solving the mangeling of utf-8/iso8859-1
character problem mentioned by Ken Hornstein (18 Apr 2012) would be great too.
I encounter such difficulties more and more with E-Mails I got
from my dear colleagues.
And the problem is older than the introduction of nmh1.4.

Bis dann
Klaus

--

-- 
-- _____________________________________________________________________________
Klaus Elsbernd; System Administrator, BOFH; elsbernd <at> dfki.uni-kl.de

"Once we know the number one, we believe that we know the number two, because
one plus one equals two. We forget that first we must know the meaning of plus."
                                                            Alpha 60
"Everything has been said, provided words do not change their meanings,
and meanings their words."                                  Alpha 60

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 20 Apr 15:13 2012
X-Face
Picon

Re: Aging Dependencies?

>Releasing a new version with faster decoding support of encoded attachments
>would help a lot.
>Since thunderbird, outlook and apple mail users don't care about the size of
>their mail, decoding of 5MB "messages ... bloated" with
>"MIME/multipart/HTML/RichText/PDF multimedia monstrosities"
>(Michael O'Donnell) lasts long on my aged sparc/solaris environment.

If you install the metamail package (specifically mmencode) that should
speed up base64 decoding a lot.  Although it occurs to me that if you're
using a Sparc system there is probably very little you can do to speed
up your system :-/.  I feel your pain ... until a few months ago I was
using a Sparc system as my desktop ... which was end-of-lifed by Sun
back in May of 1999.

>And if I may add a second wish, solving the mangeling of utf-8/iso8859-1
>character problem mentioned by Ken Hornstein (18 Apr 2012) would be great too.
>I encounter such difficulties more and more with E-Mails I got
>from my dear colleagues.

There are two issues that came up.  The first is the font issues
that Valdis mentioned.  That is correctable if you run in a UTF-8
locale and you use UTF-8 fonts everywhere.

The second is how nmh/exmh should handle messages with incorrectly coded
character sets.  The core problem _there_ was that Andreas's message was
marked as us-ascii, but contained iso-8859.  In my experience the problems
there crop up mostly from us fossils; the messages I get from more modern
mailers generally get the character set correct.

--Ken
Wolfgang Denk | 20 Apr 15:26 2012
Picon
Picon

Re: Aging Dependencies?

Dear Ken,

In message <201204201313.q3KDDFVQ001176 <at> hedwig.cmf.nrl.navy.mil> you wrote:
>
> If you install the metamail package (specifically mmencode) that should
> speed up base64 decoding a lot.  Although it occurs to me that if you're

Is there source code for this package that actully builds in any
semi-recent Linux distribution?  Fedora dropped it long ago (I think
in early 2006 or so); I'm currently using a sheel script instead that
is based on GNU recode...

Best regards,

Wolfgang Denk

--

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
Our business is run on trust.  We trust you will pay in advance.
Ken Hornstein | 20 Apr 16:21 2012
X-Face
Picon

Re: Aging Dependencies?

>Is there source code for this package that actully builds in any
>semi-recent Linux distribution?  Fedora dropped it long ago (I think
>in early 2006 or so); I'm currently using a sheel script instead that
>is based on GNU recode...

So I took a look at that ... the whole PACKAGE doesn't build right, but
if you untar it, change into src/metamail, and do "make mmencode", it
builds fine.

It looks like the issues are: either mmencode needs a home, or we need to
switch exmh to a package that is more recent than the first Clinton
administration.

It occurs to me that mmencode could have a home in nmh (well, I guess exmh
uses "mimencode", but same thing really).  Although I see exmh can use
recode if available.  Maybe this is a non-problem?

--Ken
Alexander Zangerl | 20 Apr 17:14 2012
Picon

Re: Aging Dependencies?

On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
>It looks like the issues are: either mmencode needs a home, or we need to
>switch exmh to a package that is more recent than the first Clinton
>administration.

the debian variant of exmh (which i maintain) goes for mimencode
or recode and falls back to the tcl decoder. the changes are small and 
trivial (see attached patch).

regards
az

Attachment (10_nometamail.dpatch): text/x-shellscript, 5532 bytes
--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
The programmer's national anthem is 'AAAAAAAAHHHHHHHH'. -- Weinberg, p.152
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 20 Apr 17:21 2012
X-Face
Picon

Re: Aging Dependencies?

>On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
>>It looks like the issues are: either mmencode needs a home, or we need to
>>switch exmh to a package that is more recent than the first Clinton
>>administration.
>
>the debian variant of exmh (which i maintain) goes for mimencode
>or recode and falls back to the tcl decoder. the changes are small and 
>trivial (see attached patch).

Yup, I see those changes are in the CVS tree.  All we need now is a
release that contains them :-)

--Ken
Welch, Brent | 20 Apr 18:52 2012

RE: Aging Dependencies?

Any opinion on the patch I added to my exmh-workers email most recently?  I'm inclined *not* to submit that
stuff because I think it is less than perfect and whatever performance issue I was worried about may not be
important to users.

I could turn the crank on a release, but I would need a helper to actually verify it works.

--
Brent

-----Original Message-----
From: exmh-workers-bounces <at> redhat.com [mailto:exmh-workers-bounces <at> redhat.com] On Behalf Of Ken Hornstein
Sent: Friday, April 20, 2012 8:22 AM
To: Discussion list for EXMH users
Cc: exmh-workers <at> redhat.com
Subject: Re: Aging Dependencies?

>On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
>>It looks like the issues are: either mmencode needs a home, or we need to
>>switch exmh to a package that is more recent than the first Clinton
>>administration.
>
>the debian variant of exmh (which i maintain) goes for mimencode
>or recode and falls back to the tcl decoder. the changes are small and 
>trivial (see attached patch).

Yup, I see those changes are in the CVS tree.  All we need now is a
release that contains them :-)

--Ken

_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Ken Hornstein | 22 Apr 04:45 2012
X-Face
Picon

Re: Aging Dependencies?

>Any opinion on the patch I added to my exmh-workers email most recently?
>I'm inclined *not* to submit that stuff because I think it is less than
>perfect and whatever performance issue I was worried about may not be
>important to users.

It's been a while since I did any Tcl/Tk work and exmh was always a
big pile of code to digest, so I'm not sure I'm qualified to give it a
thorough review.  But my gut is saying that it should be held off; I
made the mistake of trying to sneak in a feature into the last nmh
release and it turned out that a patch from someone which "had worked
great for us for years" broke some pretty important stuff.  I see you've
already started a release candidate for exmh 2.8.0; awesome!  Hopefully
I'll be able to crank out a release candidate for nmh tomorrow.

--Ken
Alexander Zangerl | 22 Apr 07:14 2012
Picon

Re: patches for 2.8.0 (was: Aging Dependencies?)

On Fri, 20 Apr 2012 16:52:24 GMT, "Welch, Brent" writes:
>Any opinion on the patch I added to my exmh-workers email most recently? 
>I'm inclined *not* to submit that stuff because I think it is less than 
>perfect and whatever performance issue I was worried about may not be 
>important to users.

i haven't had any issues with sequences myself, but i think it won't hurt
to include the patch.

apropos patches: i've just packaged 2.8.0 for debian (yay, loads of 
patches gone!) and found two improvements that i hadn't committed to cvs. 
the commit is done now, and i think these are useful enough to get into
the next release-candidate.

* posix doesn't require $HOSTNAME, but misc/exmhwrapper uses /bin/sh
  and still assumes $HOSTNAME is present. the fix is to export the variable
  if necessary, e.g. if your /bin/sh is dash or some other stricter shell.

* i've also made audit logging a configurable option.

apart from those minor bits 2.8.0 works fine here.

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
I came, I saw, I deleted all your files.
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Kevin Cosgrove | 6 May 22:05 2012
Picon

Re: Aging Dependencies?


On 21 April 2012 at 1:14, Alexander Zangerl <exmh <at> bin.snafu.priv.at> wrote:

> On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
> >It looks like the issues are: either mmencode needs a home, or we need to
> >switch exmh to a package that is more recent than the first Clinton
> >administration.
> 
> the debian variant of exmh (which i maintain) goes for mimencode
> or recode and falls back to the tcl decoder. the changes are small and 
> trivial (see attached patch).
> 
> --=-=-=
> Content-Type: text/x-shellscript
> Content-Disposition: inline; filename=10_nometamail.dpatch
> 
> #! /bin/sh /usr/share/dpatch/dpatch-run
> ## 10_nometamail.dpatch by  <az <at> debian.org>
> ##
> ## All lines beginning with `## DP:' are a description of the patch.
> ## DP: fix fd leakage, add support for recode as alternative to mimencode
> 
>  <at> DPATCH <at> 
> diff -urNad exmh-2.7.2~/lib/mime.tcl exmh-2.7.2/lib/mime.tcl
> --- exmh-2.7.2~/lib/mime.tcl	2008-06-18 21:50:33.863033779 +1000
> +++ exmh-2.7.2/lib/mime.tcl	2008-06-18 21:54:39.608893927 +1000
[snip]

Hiya,

Does it make sense to inclue Alexander's patch in CVS for testing
prior to 2.8.1?  Maybe it's a good fallback patch for systems
which won't have metamail?  Would it give exmh more portability
across various systems?

Thanks....

--
Kevin
Ken Hornstein | 6 May 22:13 2012
X-Face
Picon

Re: [exmh-workers] Aging Dependencies?

>Does it make sense to inclue Alexander's patch in CVS for testing
>prior to 2.8.1?  Maybe it's a good fallback patch for systems
>which won't have metamail?  Would it give exmh more portability
>across various systems?

That code (or something similar to it) is already in there.

--Ken
Kevin Cosgrove | 6 May 22:55 2012
Picon

Re: [exmh-workers] Aging Dependencies?


On 6 May 2012 at 16:13, Ken Hornstein <kenh <at> pobox.com> wrote:

> >Does it make sense to inclue Alexander's patch in CVS for testing
> >prior to 2.8.1?  Maybe it's a good fallback patch for systems
> >which won't have metamail?  Would it give exmh more portability
> >across various systems?
> 
> That code (or something similar to it) is already in there.

I thought that's what a semi-recent message of yours was saying.
Thanks for the confirmation.

Cheerio....

--
Kevin
Kevin Cosgrove | 6 May 10:11 2012
Picon

Re: Aging Dependencies?


I've built a CVS version of exmh.  I pulled down the source on
May 2, 2012.  The most recent tarball is 2.8.0, and I think the
CVS is slightly newer.  This built fine on Fedora 16.  I'm using
the Fedora supplied nmh, version 1.4.

So far everything seems to work.  But, I haven't tested much.
Here are some observations:

- I haven't been able to get a fixed width font to work.
- My custom buttons seem to be intact just fine.
- Sending & receiving messages works.
- Moving messages between folders works.
- Changing folders works.
- Pick works.
- Attaching files works.
- MIME preview works.

I included two patches, which I've been dragging around since maybe 
2.7.[0|2].  I'm not sure if they're needed anymore.  But, they're not 
applied.  Maybe I got them from this list?  See the attachments for 
those.  Any ideas as to whether I should keep dragging them around?

Thanks....

--
Kevin

Attachment (exmh-2.8.0-textpgp.patch): application/x-patch, 2826 bytes
Attachment (exmh-2.8.0-mangle.patch): application/x-patch, 1610 bytes
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Welch, Brent | 6 May 17:10 2012

RE: Aging Dependencies?

The mangle patch changes a . to a [^\n] in regexp, which seems pretty good.  I gather you don't want to gobble up
the whole message when we're matching "BEGIN PGP MESSAGE" and that line is messed up.

The other patch drops a ";" from the mail headers, and I'm not sure that's ok ?  It also changes the mime type to
text/x-pgp from text/pgp - not sure that is what you want either ?

I do plan to make a 2.8.1 after we flush out more patches like this that folks have been carrying around.

--
Brent

-----Original Message-----
From: exmh-users-bounces <at> redhat.com [mailto:exmh-users-bounces <at> redhat.com] On Behalf Of Kevin Cosgrove
Sent: Sunday, May 06, 2012 1:11 AM
To: exmh-users <at> redhat.com; exmh-workers <at> redhat.com
Subject: Re: [exmh-workers] Aging Dependencies?

I've built a CVS version of exmh.  I pulled down the source on
May 2, 2012.  The most recent tarball is 2.8.0, and I think the
CVS is slightly newer.  This built fine on Fedora 16.  I'm using
the Fedora supplied nmh, version 1.4.

So far everything seems to work.  But, I haven't tested much.
Here are some observations:

- I haven't been able to get a fixed width font to work.
- My custom buttons seem to be intact just fine.
- Sending & receiving messages works.
- Moving messages between folders works.
- Changing folders works.
- Pick works.
- Attaching files works.
- MIME preview works.

I included two patches, which I've been dragging around since maybe 
2.7.[0|2].  I'm not sure if they're needed anymore.  But, they're not 
applied.  Maybe I got them from this list?  See the attachments for 
those.  Any ideas as to whether I should keep dragging them around?

Thanks....

--
Kevin
Kevin Cosgrove | 6 May 20:55 2012
Picon

Re: [exmh-workers] Aging Dependencies?


On 6 May 2012 at 15:10, "Welch, Brent" <welch <at> panasas.com> wrote:

> The mangle patch changes a . to a [^\n] in regexp, which seems
> pretty good.  I gather you don't want to gobble up the whole
> message when we're matching "BEGIN PGP MESSAGE" and that line
> is messed up.

Maybe that one will make it into 2.8.1.

There's another simple patch attached.  This one makes gvim's
syntax highlighting happy, just by removing a space in the code.

> The other patch drops a ";" from the mail headers, and I'm not
> sure that's ok ? It also changes the mime type to text/x-pgp
> from text/pgp - not sure that is what you want either ?

Your comment nudged me into refactoring my patches.  Now all of
my PGP related stuff is in the attached pgptext.patch file.  It's
been 10 years since I adopted that mess, and I can't recall what
I wanted to change, nor even whether those patches are authored
by me.  But, I can say that my GPG interactions with exmh are
pleasant.

> I do plan to make a 2.8.1 after we flush out more patches like
> this that folks have been carrying around.

I was thinking I read that intent in this thread.

Thanks!

--
Kevin

Attachment (exmh-2.8.0-vimsyntax.patch): application/x-patch, 563 bytes
Attachment (exmh-2.8.0-pgptext.patch): application/x-patch, 4063 bytes
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Tom Lane | 6 May 21:21 2012
Picon

Re: [exmh-workers] Aging Dependencies?

"Welch, Brent" <welch <at> panasas.com> writes:
> I do plan to make a 2.8.1 after we flush out more patches like this that folks have been carrying around.

I have a couple of ancient patches that I've been carrying, which maybe
you'd consider:

(1) Allow stuff in front of "X server insecure" in send.tcl;
this seems to be necessary in my operating environment:

*** /usr/local/lib/exmh-2.7.2/send.tcl~	Tue Oct 27 22:33:17 2009
--- /usr/local/lib/exmh-2.7.2/send.tcl	Tue Oct 27 22:36:20 2009
***************
*** 14,20 ****
   proc send { args } {
      global errorInfo errorCode
      if [catch {eval tk-send $args} x] {
! 	if [string match "X server insecure*" $x] {
  	    catch {exec xhost} out
  	    set retry 0
  	    if [regexp disabled $out] {
--- 14,20 ----
   proc send { args } {
      global errorInfo errorCode
      if [catch {eval tk-send $args} x] {
! 	if [string match "*X server insecure*" $x] {
  	    catch {exec xhost} out
  	    set retry 0
  	    if [regexp disabled $out] {

(2) Use the modified send proc in exmh-async (probably there are better
ways to do this, and I'm not sure if it needs to be configurable).
I find this to be necessary too, as sometimes things reset the xhost
list while I'm editing a message:

*** /usr/local/bin/exmh-async~	Tue Oct 27 22:33:10 2009
--- /usr/local/bin/exmh-async	Tue Oct 27 22:37:02 2009
***************
*** 9,14 ****
--- 9,19 ----
  package require Tk
  wm withdraw .

+ # CRUDE HACK: force sendHack behavior
+ source /usr/local/lib/exmh-2.7.2/send.tcl
+ # needed by send.tcl
+ proc Exmh_Status { args } { }
+ 
  # simple argv cracking
  set exmh [lindex $argv 0]
  set editorCmd [lrange $argv 1 end]

			regards, tom lane
Alexander Zangerl | 8 May 02:39 2012
Picon

Re: xhost-related patches

note: recipients adjusted to -workers only

On Sun, 06 May 2012 15:21:07 -0400, Tom Lane writes:
>I have a couple of ancient patches that I've been carrying, which maybe
>you'd consider:
>
>(1) Allow stuff in front of "X server insecure" in send.tcl;
>this seems to be necessary in my operating environment:

just committed.

>(2) Use the modified send proc in exmh-async (probably there are better
>ways to do this, and I'm not sure if it needs to be configurable).
>I find this to be necessary too, as sometimes things reset the xhost
>list while I'm editing a message:

do you have the preference 'Keep xhost list clear' on (in background
processing)?

but more to the point: are you still using xhost instead of xauthority?
i haven't seen any xhost-related issues in a decade, so your report here
is somewhat surprising...

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
"Qrovna: I still think that this sounds like a dodgy Slovenian liqueur 
derived from mouldy potatoes and tractor-fuel, and best drunk by other 
people whom you don't like very much." -- Roger Burton West on ROT13(Debian)
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Alexander Zangerl | 7 May 15:50 2012
Picon

Re: Aging Dependencies?

On Sun, 06 May 2012 15:10:48 GMT, "Welch, Brent" writes:
>The mangle patch changes a . to a [^\n] in regexp, which seems pretty good.  I 
>gather you don't want to gobble up the whole message when we're matching "BEGIN
> PGP MESSAGE" and that line is messed up.

indeed, looks good and i'll be committing it RSN.
>
>The other patch drops a ";" from the mail headers, and I'm not sure that's ok ?

that patch only applies to application/pgp (i.e. the non-mime, non-multipart, 
ancient pgp format) which hopefully nobody uses anymore on this side of y2k...

as far as i can tell that patch should NOT go in: the mods damage the
already non-standard x-action/x-recipients headers beyond mime compliance
(that ; is required), and the old cruft should contine using mime type
 application/pgp  instead of the application/x-pgp from the patch.

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
Fachbegriffe der Informatik, Hot plugable: 
 Glüht beim Einstecken auf -- Martin Neumann
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Welch, Brent | 7 May 17:39 2012

RE: Aging Dependencies?

Thanks - I agree.

--
Brent

-----Original Message-----
From: exmh-workers-bounces <at> redhat.com [mailto:exmh-workers-bounces <at> redhat.com] On Behalf Of
Alexander Zangerl
Sent: Monday, May 07, 2012 6:50 AM
To: exmh-workers <at> redhat.com
Subject: Re: [exmh-workers] Aging Dependencies?

On Sun, 06 May 2012 15:10:48 GMT, "Welch, Brent" writes:
>The mangle patch changes a . to a [^\n] in regexp, which seems pretty good.  I 
>gather you don't want to gobble up the whole message when we're matching "BEGIN
> PGP MESSAGE" and that line is messed up.

indeed, looks good and i'll be committing it RSN.
>
>The other patch drops a ";" from the mail headers, and I'm not sure that's ok ?

that patch only applies to application/pgp (i.e. the non-mime, non-multipart, 
ancient pgp format) which hopefully nobody uses anymore on this side of y2k...

as far as i can tell that patch should NOT go in: the mods damage the
already non-standard x-action/x-recipients headers beyond mime compliance
(that ; is required), and the old cruft should contine using mime type
 application/pgp  instead of the application/x-pgp from the patch.

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
Fachbegriffe der Informatik, Hot plugable: 
 Glüht beim Einstecken auf -- Martin Neumann
Kevin Cosgrove | 7 May 21:42 2012
Picon

Re: Aging Dependencies?


On 7 May 2012 at 23:50, Alexander Zangerl <exmh <at> bin.snafu.priv.at>wrote: 
> On Sun, 06 May 2012 15:10:48 GMT, "Welch, Brent" writes:
> 
> > The mangle patch changes a . to a [^\n] in regexp, which seems
> > pretty good.  I gather you don't want to gobble up the whole
> > message when we're matching "BEGIN PGP MESSAGE" and that line is
> > messed up.
> 
> indeed, looks good and i'll be committing it RSN.

Nice.

> > The other patch drops a ";" from the mail headers, and I'm not
> > sure that's ok ?
> 
> that patch only applies to application/pgp (i.e. the non-mime,
> non-multipart, ancient pgp format) which hopefully nobody uses
> anymore on this side of y2k...
> 
> as far as i can tell that patch should NOT go in: the mods
> damage the already non-standard x-action/x-recipients headers
> beyond mime compliance (that ; is required), and the old cruft
> should contine using mime type application/pgp instead of the
> application/x-pgp from the patch.

I'll bet I adopted (created?) that patch back when I was using PGP, 
as you say pre y2k.  I'll pick through my email to see if I still 
have anything stored that conforms to the old way, with an eye to 
backing out the patch from my own build.

Thanks for the education....

--
Kevin
Kevin Cosgrove | 6 May 21:58 2012
Picon

Re: [exmh-workers] Aging Dependencies?


I'm happy to report that the May 2nd, 2012 CVS seems to run fine on:

 - Mandriva 2007.0, tcl/tk 8.4.13
 - Mandriva 2010.2, tcl/tk 8.6
 - Fedora 16, tcl/tk 8.5.11

My patching is minimal, the same on all systems, and already in 
discussion on this list.  I hope that helps.

Cheerio....

--
Kevin
Wolfgang Denk | 20 Apr 16:31 2012
Picon
Picon

Re: Aging Dependencies?

Dear Ken Hornstein,

In message <201204201421.q3KELVOu001849 <at> hedwig.cmf.nrl.navy.mil> you wrote:
>
> It looks like the issues are: either mmencode needs a home, or we need to
> switch exmh to a package that is more recent than the first Clinton
> administration.
> 
> It occurs to me that mmencode could have a home in nmh (well, I guess exmh
> uses "mimencode", but same thing really).  Although I see exmh can use
> recode if available.  Maybe this is a non-problem?

Eventually the attached script is sufficient?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
All this doesn't alter anything, you know. The world is still full of
stupid people. They don't use their brains. They don't seem  to  want
to think straight.                    - Terry Pratchett, _Soul Music_

#!/bin/sh

# Synopsis:
#	mimencode [-u] [-b] [-q] [file name]
#
# -u : decode rather than encode
# -b : use "base64" encoding (default)
# -q : use "quoted-printable" encoding

# Default: encode to base64
ENCODE="../base64"
DECODE="/base64.."

ACTION="encode"

while [ $# -gt 0 ]
do
	case "$1" in
	-u)	ACTION="decode"
		shift
		;;
	-b)	ENCODE="../base64"
		DECODE="/base64.."
		shift
		;;
	-q)	ENCODE="../qp"
		DECODE="/qp.."
		shift
		;;
	--)	shift
		break
		;;
	*)	break
		;;
	esac
done

if [ ${ACTION} = "encode" ]
then
	CONVERT="${ENCODE}"
else
	CONVERT="${DECODE}"
fi

cat "$ <at> " | recode -f -q "${CONVERT}"
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 20 Apr 16:36 2012
X-Face
Picon

Re: Aging Dependencies?

>> It occurs to me that mmencode could have a home in nmh (well, I guess exmh
>> uses "mimencode", but same thing really).  Although I see exmh can use
>> recode if available.  Maybe this is a non-problem?
>
>Eventually the attached script is sufficient?

My reading of the exmh source code shows me that this isn't necessary;
it will call recode with the right arguments directly.  But maybe that
support is newer than 2.7.2?  (I will confess to running a CVS snapshot
because I needed stuff that wasn't fixed in a release).

--Ken
Valdis.Kletnieks | 20 Apr 17:04 2012
Picon

Re: Aging Dependencies?

On Fri, 20 Apr 2012 10:36:16 -0400, Ken Hornstein said:
> >> It occurs to me that mmencode could have a home in nmh (well, I guess exmh
> >> uses "mimencode", but same thing really).  Although I see exmh can use
> >> recode if available.  Maybe this is a non-problem?
> >
> >Eventually the attached script is sufficient?
>
> My reading of the exmh source code shows me that this isn't necessary;
> it will call recode with the right arguments directly.  But maybe that
> support is newer than 2.7.2?  (I will confess to running a CVS snapshot
> because I needed stuff that wasn't fixed in a release).

Yes, it is newer:

cvs repository 06/20/2008 az <at> debian.org
  incorporated a number of patches from debian
  exmh.l: silence some man warnings
  lib/mh.tcl: mention install-mh by full path in initial greeting
  lib/bogo.tcl: add learning-from-stdin for learning ham, too
   (not just spam)
  lib/glimpse.tcl: add the -W glimpse option (and scope for
   whole file) to permanent preferences
  lib/scan.tcl, lib/folder.tcl: fix the stale scan cache problem
  lib/uri.tcl, html_links.tcl: make html links clickable in
   inline-displayed html, and consolidate status line handling for links
  lib/seditExtras.tcl, lib/mime.tcl: patch from Marion Hakanson to
   fix fd leakage in internal mime qp/base64 decoder
   patch from debian: add support for recode as alternative to mimencode

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Andy Bradford | 19 Apr 04:27 2012

Re: Aging Dependencies?

Thus said "Welch, Brent" on Wed, 18 Apr 2012 16:42:35 -0000:

> When  the Panasas  IT guys  upgraded  our exchange  server to  require
> encrypted channels, and  my desktop (which I now don't  use) got a new
> Ubuntu distribution,  I failed  to put my  elaborate email  tool chain
> back together. So I've  punted to the dark side. I  even read email on
> my iphone sometimes.

I had  a stint with the  dark side for a  bit, but I couldn't  stand it.
Eventually  I  discovered  Davmail,  and  while  it's  not  the  perfect
solution,  it  does  allow   integration  with  Exchange  and  encrypted
channels.

Andy
Julian H. Stacey | 18 Apr 16:22 2012

Add URLS to list descriptions.

Hi
Footer of exmh-users <at> redhat.com has 
	https://www.redhat.com/mailman/listinfo/exmh-users
I suggest in that page, in "About Exmh-users" list list owner please add:
  See Also: 
	- https://www.redhat.com/mailman/listinfo/exmh-workers
	- http://www.beedub.com/exmh/

& to https://www.redhat.com/mailman/listinfo/exmh-workers that list owner add:
	- http://www.beedub.com/exmh/
	- URL of cvs repository, if has a web interface to allow viewing

Cheers,
Julian
--

-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below not above, cumulative like a play script, & indent with "> ".
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
	Mail from  <at> yahoo dumped  <at> berklix.  http://berklix.org/yahoo/
Ken Hornstein | 18 Apr 16:54 2012
X-Face
Picon

Re: Add URLS to list descriptions.

Unrelated to that ....

>Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
> Reply below not above, cumulative like a play script, & indent with "> ".
> Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.

I understand your feelings about message formats and I'm not even
sure I disagree with them, but if I want to send text using UTF-8,
exactly what should I be using as a Content-Transfer-Encoding?
8bit?  The last message I sent to the list left my mailbox as
quoted-printable which I think is probably the best choice available,
but the list software re-encoded it as base64.

--Ken
Julian H. Stacey | 20 Apr 02:33 2012

Re: Add URLS to list descriptions.

Hi,
Ken Hornstein wrote:
> Unrelated to that ....
> 
> >Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
> > Reply below not above, cumulative like a play script, & indent with "> ".
> > Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
> 
> I understand your feelings about message formats and I'm not even
> sure I disagree with them, but if I want to send text using UTF-8,
> exactly what should I be using as a Content-Transfer-Encoding?
> 8bit?  The last message I sent to the list left my mailbox as
> quoted-printable which I think is probably the best choice available,
> but the list software re-encoded it as base64.
> 
> --Ken

My generic automatic ~/.signature was not written for this list,
which has competent people :-)  It's to deter locals I run
free lists for (mostly clueless MS non tech. users), from sending
me broken umlauts, HTML, Doc & other rubbish.

> I'm digging the exmh love fest, I really am ... but I don't suppose any of
> that love would translate to the development cycles for exmh or nmh, would
> it? :-)  Because in all seriousness that's what we really need.

I'm using exmh-2.7.2 with tiny personal tweaks
	http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/mail/exmh2/
	http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/jhs/mail/exmh2/
& nmh-1.2_3
	(version normal to FreeBSD, not OS generic)
on FreeBSD (8.2-RELEASE, but 9.0 & 8.3 too soon) :

http://www.freebsd.org/cgi/cvsweb.cgi/ports/mail/nmh/Makefile
	MAINTAINER=     scott+ports <at> sabami.seaslug.org
	PORTVERSION=    1.3
	
http://savannah.nongnu.org/projects/nmh/
	nmh 1.4 has been released! posted by kenh, Mon 02 Jan 2012 
	nmh 1.3 has been released posted by pm215, Sun 01 Jun 2008

so I cc'd scott+ports <at> sabami.seaslug.org for info : new generic available.

http://www.freebsd.org/cgi/cvsweb.cgi/ports/mail/exmh2/Makefile
	MAINTAINER?=    ports <at> FreeBSD.org
	PORTVERSION=    2.7.2

As earlier, exmh-users <at>  list owner should put some text on
	https://www.redhat.com/mailman/listinfo/exmh-users
like eg:
	See http://www.beedub.com/exmh/		+,
	if you can help test new exmh code, or contribute patches, see  also
	https://www.redhat.com/mailman/listinfo/exmh-workers

& put some text on
	https://www.redhat.com/mailman/listinfo/exmh-workers
pointing to CVS archive.

I just subscribed workers <at>  so you could later lean on me to help
test/ update port for new exmh tar.gz on FreeBSD.

Hopefuly a few other happy users may also subscribe
	https://www.redhat.com/mailman/listinfo/exmh-workers

Cheers,
Julian
--

-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below not above, cumulative like a play script, & indent with "> ".
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
	Mail from  <at> yahoo dumped  <at> berklix.  http://berklix.org/yahoo/
Ken Hornstein | 20 Apr 02:59 2012
X-Face
Picon

Re: Add URLS to list descriptions.

>http://www.freebsd.org/cgi/cvsweb.cgi/ports/mail/nmh/Makefile
>	MAINTAINER=     scott+ports <at> sabami.seaslug.org
>	PORTVERSION=    1.3
>	
>http://savannah.nongnu.org/projects/nmh/
>	nmh 1.4 has been released! posted by kenh, Mon 02 Jan 2012 
>	nmh 1.3 has been released posted by pm215, Sun 01 Jun 2008

As long as you're updating the nmh port ... if things go well I
_should_ start the release cycle for nmh 1.5 this weekend, which
will actually have a couple new things that exmh users might care
about.

--Ken
Wolfgang Denk | 20 Apr 09:39 2012
Picon
Picon

Re: Add URLS to list descriptions.

Dear Ken,

In message <201204200100.q3K0xxHD029025 <at> hedwig.cmf.nrl.navy.mil> you wrote:
> >http://www.freebsd.org/cgi/cvsweb.cgi/ports/mail/nmh/Makefile
> >	MAINTAINER=     scott+ports <at> sabami.seaslug.org
> >	PORTVERSION=    1.3
> >	
> >http://savannah.nongnu.org/projects/nmh/
> >	nmh 1.4 has been released! posted by kenh, Mon 02 Jan 2012 
> >	nmh 1.3 has been released posted by pm215, Sun 01 Jun 2008
> 
> As long as you're updating the nmh port ... if things go well I
> _should_ start the release cycle for nmh 1.5 this weekend, which
> will actually have a couple new things that exmh users might care
> about.

With nmh 1.4, bouncing of messages stopped working for me: dist fails
with an "unable to link ... File exists" error. I didn't build this
from sources, so I only reported a bug against the Fedora
distribution, see https://bugzilla.redhat.com/show_bug.cgi?id=804333

For the new release it would be nice if you could make sure this gets
tested, too.

Thanks a lot in advance.

BTW: I'm using exmh since version 1.6.4 10/10/1995...

Best regards,

Wolfgang Denk

--

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
A witty saying proves nothing, but saying  something  pointless  gets
people's attention.
Ken Hornstein | 20 Apr 14:50 2012
X-Face
Picon

Re: Add URLS to list descriptions.

>With nmh 1.4, bouncing of messages stopped working for me: dist fails
>with an "unable to link ... File exists" error. I didn't build this
>from sources, so I only reported a bug against the Fedora
>distribution, see https://bugzilla.redhat.com/show_bug.cgi?id=804333

Yeah, sorry about that.  I discovered that after 1.4 was released.
It's fixed in the current version and will be fixed in 1.5.  It
turned out that was broken for a while, but since not that many
people use the current source code from the revision control tree
it wasn't noticed (I don't use dist very much myself ... I only
noticed when I upgraded my wife's copy of nmh and she started
complaining about it).  If you're up for patching it yourself the
revision where it was fixed is here:

http://git.savannah.gnu.org/cgit/nmh.git/commit/?id=01943d78230ead5bcc568e8a87d3cdbaac1f5584

We actually resurrected the old nmh test suite and integrated it
into Automake, so now a lot of things automatically get checked.
Although it occurs to me that dist is NOT currently in the test
suite; I should put it in there.

--Ken
Tom Lane | 10 Aug 04:14 2013
Picon

Re: Aging Dependencies?

Awhile back, Ken Hornstein <kenh <at> cmf.nrl.navy.mil> wrote:
>> Anyone heard of plans regarding what to do about aging
>> dependencies for exmh?  I'm trying to bring a Fedora 16 machine
>> up to capable, which includes installing exmh.
>> I found metamail for Fedora 16 on-line, maybe it was at pkgs.net?

> MacPorts includes a "mmencode" package which has the piece you
> really need (you don't really need all of metamail).  There's a
> built-in base64 encoder/decoder in exmh, but there is a file
> descriptor leak in there somewhere; I never was able to track it
> down and installing mmencode was just easier.  Perhaps one of us
> should consider creating an RPM for that?

FWIW, I ran into this while moving onto a new machine running RHEL6.
I didn't really want to install metamail, but pulling up any large
base64-encoded or qp-encoded message was just horribly slow.  I went
looking in the exmh source code and almost immediately stumbled
across this changelog entry:

cvs repository 06/20/2008 az <at> debian.org
  lib/seditExtras.tcl, lib/mime.tcl: patch from Marion Hakanson to
   fix fd leakage in internal mime qp/base64 decoder
   patch from debian: add support for recode as alternative to mimencode

Sure enough, installing recode (which *is* available as a RHEL or Fedora
package) and restarting exmh fixed the speed problem.  So that seems
like an alternative worth keeping in mind.  A bit of looking says that
recode hasn't seen an upstream release in a long while either, but
maybe it's just one of those pieces of software that doesn't need
many changes.

			regards, tom lane
Emile CARCAMO | 20 Apr 08:35 2012
X-Face
Picon

Re: Aging Dependencies?


Dear List
Members,

	I'm also using exmh since March 1995, and I was
	always able to keep it working when switching
	from one company to another :

	- slocal and ~/.maildelivery usage ( at HP )

	- fetchmail with IMAP support and procmail to
	dispatch messages in appropriate folders ( at NEC )

	Still using method #2 now at BULL ;-) I'll be glad to
	give it a try if someone posts another release soon !
	This will remind me the "good old days" ;-)

	And btw I'll also update my nmh 1.3 version ... All
	this stuff keeps running fine under Fedora releases
	for years, now !!

	I can't imagine switching to another MUA. Exmh is
	not perfect by I can "live" with its few limitations ;-)

	With best regards,

-Émile
Klaus Elsbernd | 20 Apr 11:28 2012
X-Face
Picon
Picon

Re: Aging Dependencies?

exmh-users-request <at> redhat.com said:
> That is itself part of the problem ... exmh hasn't gotten a lot of love
> lately.  A new release is overdue.
I have to defend my use of exmh against the majority of thunderbird and
outlook users, using it since Nov 1993 and I'm quite happy with it.

Releasing a new version with faster decoding support of encoded attachments
would help a lot.
Since thunderbird, outlook and apple mail users don't care about the size of
their mail, decoding of 5MB "messages ... bloated" with
"MIME/multipart/HTML/RichText/PDF multimedia monstrosities"
(Michael O'Donnell) lasts long on my aged sparc/solaris environment.

And if I may add a second wish, solving the mangeling of utf-8/iso8859-1
character problem mentioned by Ken Hornstein (18 Apr 2012) would be great too.
I encounter such difficulties more and more with E-Mails I got
from my dear colleagues.
And the problem is older than the introduction of nmh1.4.

Bis dann
Klaus

--

-- 
-- _____________________________________________________________________________
Klaus Elsbernd; System Administrator, BOFH; elsbernd <at> dfki.uni-kl.de

"Once we know the number one, we believe that we know the number two, because
one plus one equals two. We forget that first we must know the meaning of plus."
                                                            Alpha 60
"Everything has been said, provided words do not change their meanings,
and meanings their words."                                  Alpha 60

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 20 Apr 15:13 2012
X-Face
Picon

Re: Aging Dependencies?

>Releasing a new version with faster decoding support of encoded attachments
>would help a lot.
>Since thunderbird, outlook and apple mail users don't care about the size of
>their mail, decoding of 5MB "messages ... bloated" with
>"MIME/multipart/HTML/RichText/PDF multimedia monstrosities"
>(Michael O'Donnell) lasts long on my aged sparc/solaris environment.

If you install the metamail package (specifically mmencode) that should
speed up base64 decoding a lot.  Although it occurs to me that if you're
using a Sparc system there is probably very little you can do to speed
up your system :-/.  I feel your pain ... until a few months ago I was
using a Sparc system as my desktop ... which was end-of-lifed by Sun
back in May of 1999.

>And if I may add a second wish, solving the mangeling of utf-8/iso8859-1
>character problem mentioned by Ken Hornstein (18 Apr 2012) would be great too.
>I encounter such difficulties more and more with E-Mails I got
>from my dear colleagues.

There are two issues that came up.  The first is the font issues
that Valdis mentioned.  That is correctable if you run in a UTF-8
locale and you use UTF-8 fonts everywhere.

The second is how nmh/exmh should handle messages with incorrectly coded
character sets.  The core problem _there_ was that Andreas's message was
marked as us-ascii, but contained iso-8859.  In my experience the problems
there crop up mostly from us fossils; the messages I get from more modern
mailers generally get the character set correct.

--Ken
Wolfgang Denk | 20 Apr 15:26 2012
Picon
Picon

Re: Aging Dependencies?

Dear Ken,

In message <201204201313.q3KDDFVQ001176 <at> hedwig.cmf.nrl.navy.mil> you wrote:
>
> If you install the metamail package (specifically mmencode) that should
> speed up base64 decoding a lot.  Although it occurs to me that if you're

Is there source code for this package that actully builds in any
semi-recent Linux distribution?  Fedora dropped it long ago (I think
in early 2006 or so); I'm currently using a sheel script instead that
is based on GNU recode...

Best regards,

Wolfgang Denk

--

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
Our business is run on trust.  We trust you will pay in advance.
Ken Hornstein | 20 Apr 16:21 2012
X-Face
Picon

Re: Aging Dependencies?

>Is there source code for this package that actully builds in any
>semi-recent Linux distribution?  Fedora dropped it long ago (I think
>in early 2006 or so); I'm currently using a sheel script instead that
>is based on GNU recode...

So I took a look at that ... the whole PACKAGE doesn't build right, but
if you untar it, change into src/metamail, and do "make mmencode", it
builds fine.

It looks like the issues are: either mmencode needs a home, or we need to
switch exmh to a package that is more recent than the first Clinton
administration.

It occurs to me that mmencode could have a home in nmh (well, I guess exmh
uses "mimencode", but same thing really).  Although I see exmh can use
recode if available.  Maybe this is a non-problem?

--Ken
Alexander Zangerl | 20 Apr 17:14 2012
Picon

Re: Aging Dependencies?

On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
>It looks like the issues are: either mmencode needs a home, or we need to
>switch exmh to a package that is more recent than the first Clinton
>administration.

the debian variant of exmh (which i maintain) goes for mimencode
or recode and falls back to the tcl decoder. the changes are small and 
trivial (see attached patch).

regards
az

Attachment (10_nometamail.dpatch): text/x-shellscript, 5532 bytes
--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
The programmer's national anthem is 'AAAAAAAAHHHHHHHH'. -- Weinberg, p.152
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 20 Apr 17:21 2012
X-Face
Picon

Re: Aging Dependencies?

>On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
>>It looks like the issues are: either mmencode needs a home, or we need to
>>switch exmh to a package that is more recent than the first Clinton
>>administration.
>
>the debian variant of exmh (which i maintain) goes for mimencode
>or recode and falls back to the tcl decoder. the changes are small and 
>trivial (see attached patch).

Yup, I see those changes are in the CVS tree.  All we need now is a
release that contains them :-)

--Ken
Welch, Brent | 20 Apr 18:52 2012

RE: Aging Dependencies?

Any opinion on the patch I added to my exmh-workers email most recently?  I'm inclined *not* to submit that
stuff because I think it is less than perfect and whatever performance issue I was worried about may not be
important to users.

I could turn the crank on a release, but I would need a helper to actually verify it works.

--
Brent

-----Original Message-----
From: exmh-workers-bounces <at> redhat.com [mailto:exmh-workers-bounces <at> redhat.com] On Behalf Of Ken Hornstein
Sent: Friday, April 20, 2012 8:22 AM
To: Discussion list for EXMH users
Cc: exmh-workers <at> redhat.com
Subject: Re: Aging Dependencies?

>On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
>>It looks like the issues are: either mmencode needs a home, or we need to
>>switch exmh to a package that is more recent than the first Clinton
>>administration.
>
>the debian variant of exmh (which i maintain) goes for mimencode
>or recode and falls back to the tcl decoder. the changes are small and 
>trivial (see attached patch).

Yup, I see those changes are in the CVS tree.  All we need now is a
release that contains them :-)

--Ken

_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Ken Hornstein | 22 Apr 04:45 2012
X-Face
Picon

Re: Aging Dependencies?

>Any opinion on the patch I added to my exmh-workers email most recently?
>I'm inclined *not* to submit that stuff because I think it is less than
>perfect and whatever performance issue I was worried about may not be
>important to users.

It's been a while since I did any Tcl/Tk work and exmh was always a
big pile of code to digest, so I'm not sure I'm qualified to give it a
thorough review.  But my gut is saying that it should be held off; I
made the mistake of trying to sneak in a feature into the last nmh
release and it turned out that a patch from someone which "had worked
great for us for years" broke some pretty important stuff.  I see you've
already started a release candidate for exmh 2.8.0; awesome!  Hopefully
I'll be able to crank out a release candidate for nmh tomorrow.

--Ken
Alexander Zangerl | 22 Apr 07:14 2012
Picon

Re: patches for 2.8.0 (was: Aging Dependencies?)

On Fri, 20 Apr 2012 16:52:24 GMT, "Welch, Brent" writes:
>Any opinion on the patch I added to my exmh-workers email most recently? 
>I'm inclined *not* to submit that stuff because I think it is less than 
>perfect and whatever performance issue I was worried about may not be 
>important to users.

i haven't had any issues with sequences myself, but i think it won't hurt
to include the patch.

apropos patches: i've just packaged 2.8.0 for debian (yay, loads of 
patches gone!) and found two improvements that i hadn't committed to cvs. 
the commit is done now, and i think these are useful enough to get into
the next release-candidate.

* posix doesn't require $HOSTNAME, but misc/exmhwrapper uses /bin/sh
  and still assumes $HOSTNAME is present. the fix is to export the variable
  if necessary, e.g. if your /bin/sh is dash or some other stricter shell.

* i've also made audit logging a configurable option.

apart from those minor bits 2.8.0 works fine here.

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
I came, I saw, I deleted all your files.
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Kevin Cosgrove | 6 May 22:05 2012
Picon

Re: Aging Dependencies?


On 21 April 2012 at 1:14, Alexander Zangerl <exmh <at> bin.snafu.priv.at> wrote:

> On Fri, 20 Apr 2012 10:21:31 -0400, Ken Hornstein writes:
> >It looks like the issues are: either mmencode needs a home, or we need to
> >switch exmh to a package that is more recent than the first Clinton
> >administration.
> 
> the debian variant of exmh (which i maintain) goes for mimencode
> or recode and falls back to the tcl decoder. the changes are small and 
> trivial (see attached patch).
> 
> --=-=-=
> Content-Type: text/x-shellscript
> Content-Disposition: inline; filename=10_nometamail.dpatch
> 
> #! /bin/sh /usr/share/dpatch/dpatch-run
> ## 10_nometamail.dpatch by  <az <at> debian.org>
> ##
> ## All lines beginning with `## DP:' are a description of the patch.
> ## DP: fix fd leakage, add support for recode as alternative to mimencode
> 
>  <at> DPATCH <at> 
> diff -urNad exmh-2.7.2~/lib/mime.tcl exmh-2.7.2/lib/mime.tcl
> --- exmh-2.7.2~/lib/mime.tcl	2008-06-18 21:50:33.863033779 +1000
> +++ exmh-2.7.2/lib/mime.tcl	2008-06-18 21:54:39.608893927 +1000
[snip]

Hiya,

Does it make sense to inclue Alexander's patch in CVS for testing
prior to 2.8.1?  Maybe it's a good fallback patch for systems
which won't have metamail?  Would it give exmh more portability
across various systems?

Thanks....

--
Kevin
Ken Hornstein | 6 May 22:13 2012
X-Face
Picon

Re: [exmh-workers] Aging Dependencies?

>Does it make sense to inclue Alexander's patch in CVS for testing
>prior to 2.8.1?  Maybe it's a good fallback patch for systems
>which won't have metamail?  Would it give exmh more portability
>across various systems?

That code (or something similar to it) is already in there.

--Ken
Kevin Cosgrove | 6 May 22:55 2012
Picon

Re: [exmh-workers] Aging Dependencies?


On 6 May 2012 at 16:13, Ken Hornstein <kenh <at> pobox.com> wrote:

> >Does it make sense to inclue Alexander's patch in CVS for testing
> >prior to 2.8.1?  Maybe it's a good fallback patch for systems
> >which won't have metamail?  Would it give exmh more portability
> >across various systems?
> 
> That code (or something similar to it) is already in there.

I thought that's what a semi-recent message of yours was saying.
Thanks for the confirmation.

Cheerio....

--
Kevin
Kevin Cosgrove | 6 May 10:11 2012
Picon

Re: Aging Dependencies?


I've built a CVS version of exmh.  I pulled down the source on
May 2, 2012.  The most recent tarball is 2.8.0, and I think the
CVS is slightly newer.  This built fine on Fedora 16.  I'm using
the Fedora supplied nmh, version 1.4.

So far everything seems to work.  But, I haven't tested much.
Here are some observations:

- I haven't been able to get a fixed width font to work.
- My custom buttons seem to be intact just fine.
- Sending & receiving messages works.
- Moving messages between folders works.
- Changing folders works.
- Pick works.
- Attaching files works.
- MIME preview works.

I included two patches, which I've been dragging around since maybe 
2.7.[0|2].  I'm not sure if they're needed anymore.  But, they're not 
applied.  Maybe I got them from this list?  See the attachments for 
those.  Any ideas as to whether I should keep dragging them around?

Thanks....

--
Kevin

Attachment (exmh-2.8.0-textpgp.patch): application/x-patch, 2826 bytes
Attachment (exmh-2.8.0-mangle.patch): application/x-patch, 1610 bytes
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Welch, Brent | 6 May 17:10 2012

RE: Aging Dependencies?

The mangle patch changes a . to a [^\n] in regexp, which seems pretty good.  I gather you don't want to gobble up
the whole message when we're matching "BEGIN PGP MESSAGE" and that line is messed up.

The other patch drops a ";" from the mail headers, and I'm not sure that's ok ?  It also changes the mime type to
text/x-pgp from text/pgp - not sure that is what you want either ?

I do plan to make a 2.8.1 after we flush out more patches like this that folks have been carrying around.

--
Brent

-----Original Message-----
From: exmh-users-bounces <at> redhat.com [mailto:exmh-users-bounces <at> redhat.com] On Behalf Of Kevin Cosgrove
Sent: Sunday, May 06, 2012 1:11 AM
To: exmh-users <at> redhat.com; exmh-workers <at> redhat.com
Subject: Re: [exmh-workers] Aging Dependencies?

I've built a CVS version of exmh.  I pulled down the source on
May 2, 2012.  The most recent tarball is 2.8.0, and I think the
CVS is slightly newer.  This built fine on Fedora 16.  I'm using
the Fedora supplied nmh, version 1.4.

So far everything seems to work.  But, I haven't tested much.
Here are some observations:

- I haven't been able to get a fixed width font to work.
- My custom buttons seem to be intact just fine.
- Sending & receiving messages works.
- Moving messages between folders works.
- Changing folders works.
- Pick works.
- Attaching files works.
- MIME preview works.

I included two patches, which I've been dragging around since maybe 
2.7.[0|2].  I'm not sure if they're needed anymore.  But, they're not 
applied.  Maybe I got them from this list?  See the attachments for 
those.  Any ideas as to whether I should keep dragging them around?

Thanks....

--
Kevin
Kevin Cosgrove | 6 May 20:55 2012
Picon

Re: [exmh-workers] Aging Dependencies?


On 6 May 2012 at 15:10, "Welch, Brent" <welch <at> panasas.com> wrote:

> The mangle patch changes a . to a [^\n] in regexp, which seems
> pretty good.  I gather you don't want to gobble up the whole
> message when we're matching "BEGIN PGP MESSAGE" and that line
> is messed up.

Maybe that one will make it into 2.8.1.

There's another simple patch attached.  This one makes gvim's
syntax highlighting happy, just by removing a space in the code.

> The other patch drops a ";" from the mail headers, and I'm not
> sure that's ok ? It also changes the mime type to text/x-pgp
> from text/pgp - not sure that is what you want either ?

Your comment nudged me into refactoring my patches.  Now all of
my PGP related stuff is in the attached pgptext.patch file.  It's
been 10 years since I adopted that mess, and I can't recall what
I wanted to change, nor even whether those patches are authored
by me.  But, I can say that my GPG interactions with exmh are
pleasant.

> I do plan to make a 2.8.1 after we flush out more patches like
> this that folks have been carrying around.

I was thinking I read that intent in this thread.

Thanks!

--
Kevin

Attachment (exmh-2.8.0-vimsyntax.patch): application/x-patch, 563 bytes
Attachment (exmh-2.8.0-pgptext.patch): application/x-patch, 4063 bytes
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Tom Lane | 6 May 21:21 2012
Picon

Re: [exmh-workers] Aging Dependencies?

"Welch, Brent" <welch <at> panasas.com> writes:
> I do plan to make a 2.8.1 after we flush out more patches like this that folks have been carrying around.

I have a couple of ancient patches that I've been carrying, which maybe
you'd consider:

(1) Allow stuff in front of "X server insecure" in send.tcl;
this seems to be necessary in my operating environment:

*** /usr/local/lib/exmh-2.7.2/send.tcl~	Tue Oct 27 22:33:17 2009
--- /usr/local/lib/exmh-2.7.2/send.tcl	Tue Oct 27 22:36:20 2009
***************
*** 14,20 ****
   proc send { args } {
      global errorInfo errorCode
      if [catch {eval tk-send $args} x] {
! 	if [string match "X server insecure*" $x] {
  	    catch {exec xhost} out
  	    set retry 0
  	    if [regexp disabled $out] {
--- 14,20 ----
   proc send { args } {
      global errorInfo errorCode
      if [catch {eval tk-send $args} x] {
! 	if [string match "*X server insecure*" $x] {
  	    catch {exec xhost} out
  	    set retry 0
  	    if [regexp disabled $out] {

(2) Use the modified send proc in exmh-async (probably there are better
ways to do this, and I'm not sure if it needs to be configurable).
I find this to be necessary too, as sometimes things reset the xhost
list while I'm editing a message:

*** /usr/local/bin/exmh-async~	Tue Oct 27 22:33:10 2009
--- /usr/local/bin/exmh-async	Tue Oct 27 22:37:02 2009
***************
*** 9,14 ****
--- 9,19 ----
  package require Tk
  wm withdraw .

+ # CRUDE HACK: force sendHack behavior
+ source /usr/local/lib/exmh-2.7.2/send.tcl
+ # needed by send.tcl
+ proc Exmh_Status { args } { }
+ 
  # simple argv cracking
  set exmh [lindex $argv 0]
  set editorCmd [lrange $argv 1 end]

			regards, tom lane
Alexander Zangerl | 8 May 02:39 2012
Picon

Re: xhost-related patches

note: recipients adjusted to -workers only

On Sun, 06 May 2012 15:21:07 -0400, Tom Lane writes:
>I have a couple of ancient patches that I've been carrying, which maybe
>you'd consider:
>
>(1) Allow stuff in front of "X server insecure" in send.tcl;
>this seems to be necessary in my operating environment:

just committed.

>(2) Use the modified send proc in exmh-async (probably there are better
>ways to do this, and I'm not sure if it needs to be configurable).
>I find this to be necessary too, as sometimes things reset the xhost
>list while I'm editing a message:

do you have the preference 'Keep xhost list clear' on (in background
processing)?

but more to the point: are you still using xhost instead of xauthority?
i haven't seen any xhost-related issues in a decade, so your report here
is somewhat surprising...

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
"Qrovna: I still think that this sounds like a dodgy Slovenian liqueur 
derived from mouldy potatoes and tractor-fuel, and best drunk by other 
people whom you don't like very much." -- Roger Burton West on ROT13(Debian)
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Alexander Zangerl | 7 May 15:50 2012
Picon

Re: Aging Dependencies?

On Sun, 06 May 2012 15:10:48 GMT, "Welch, Brent" writes:
>The mangle patch changes a . to a [^\n] in regexp, which seems pretty good.  I 
>gather you don't want to gobble up the whole message when we're matching "BEGIN
> PGP MESSAGE" and that line is messed up.

indeed, looks good and i'll be committing it RSN.
>
>The other patch drops a ";" from the mail headers, and I'm not sure that's ok ?

that patch only applies to application/pgp (i.e. the non-mime, non-multipart, 
ancient pgp format) which hopefully nobody uses anymore on this side of y2k...

as far as i can tell that patch should NOT go in: the mods damage the
already non-standard x-action/x-recipients headers beyond mime compliance
(that ; is required), and the old cruft should contine using mime type
 application/pgp  instead of the application/x-pgp from the patch.

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
Fachbegriffe der Informatik, Hot plugable: 
 Glüht beim Einstecken auf -- Martin Neumann
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Welch, Brent | 7 May 17:39 2012

RE: Aging Dependencies?

Thanks - I agree.

--
Brent

-----Original Message-----
From: exmh-workers-bounces <at> redhat.com [mailto:exmh-workers-bounces <at> redhat.com] On Behalf Of
Alexander Zangerl
Sent: Monday, May 07, 2012 6:50 AM
To: exmh-workers <at> redhat.com
Subject: Re: [exmh-workers] Aging Dependencies?

On Sun, 06 May 2012 15:10:48 GMT, "Welch, Brent" writes:
>The mangle patch changes a . to a [^\n] in regexp, which seems pretty good.  I 
>gather you don't want to gobble up the whole message when we're matching "BEGIN
> PGP MESSAGE" and that line is messed up.

indeed, looks good and i'll be committing it RSN.
>
>The other patch drops a ";" from the mail headers, and I'm not sure that's ok ?

that patch only applies to application/pgp (i.e. the non-mime, non-multipart, 
ancient pgp format) which hopefully nobody uses anymore on this side of y2k...

as far as i can tell that patch should NOT go in: the mods damage the
already non-standard x-action/x-recipients headers beyond mime compliance
(that ; is required), and the old cruft should contine using mime type
 application/pgp  instead of the application/x-pgp from the patch.

regards
az

--

-- 
Alexander Zangerl + GnuPG Keys 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
Fachbegriffe der Informatik, Hot plugable: 
 Glüht beim Einstecken auf -- Martin Neumann
Kevin Cosgrove | 7 May 21:42 2012
Picon

Re: Aging Dependencies?


On 7 May 2012 at 23:50, Alexander Zangerl <exmh <at> bin.snafu.priv.at>wrote: 
> On Sun, 06 May 2012 15:10:48 GMT, "Welch, Brent" writes:
> 
> > The mangle patch changes a . to a [^\n] in regexp, which seems
> > pretty good.  I gather you don't want to gobble up the whole
> > message when we're matching "BEGIN PGP MESSAGE" and that line is
> > messed up.
> 
> indeed, looks good and i'll be committing it RSN.

Nice.

> > The other patch drops a ";" from the mail headers, and I'm not
> > sure that's ok ?
> 
> that patch only applies to application/pgp (i.e. the non-mime,
> non-multipart, ancient pgp format) which hopefully nobody uses
> anymore on this side of y2k...
> 
> as far as i can tell that patch should NOT go in: the mods
> damage the already non-standard x-action/x-recipients headers
> beyond mime compliance (that ; is required), and the old cruft
> should contine using mime type application/pgp instead of the
> application/x-pgp from the patch.

I'll bet I adopted (created?) that patch back when I was using PGP, 
as you say pre y2k.  I'll pick through my email to see if I still 
have anything stored that conforms to the old way, with an eye to 
backing out the patch from my own build.

Thanks for the education....

--
Kevin
Kevin Cosgrove | 6 May 21:58 2012
Picon

Re: [exmh-workers] Aging Dependencies?


I'm happy to report that the May 2nd, 2012 CVS seems to run fine on:

 - Mandriva 2007.0, tcl/tk 8.4.13
 - Mandriva 2010.2, tcl/tk 8.6
 - Fedora 16, tcl/tk 8.5.11

My patching is minimal, the same on all systems, and already in 
discussion on this list.  I hope that helps.

Cheerio....

--
Kevin
Wolfgang Denk | 20 Apr 16:31 2012
Picon
Picon

Re: Aging Dependencies?

Dear Ken Hornstein,

In message <201204201421.q3KELVOu001849 <at> hedwig.cmf.nrl.navy.mil> you wrote:
>
> It looks like the issues are: either mmencode needs a home, or we need to
> switch exmh to a package that is more recent than the first Clinton
> administration.
> 
> It occurs to me that mmencode could have a home in nmh (well, I guess exmh
> uses "mimencode", but same thing really).  Although I see exmh can use
> recode if available.  Maybe this is a non-problem?

Eventually the attached script is sufficient?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
All this doesn't alter anything, you know. The world is still full of
stupid people. They don't use their brains. They don't seem  to  want
to think straight.                    - Terry Pratchett, _Soul Music_

#!/bin/sh

# Synopsis:
#	mimencode [-u] [-b] [-q] [file name]
#
# -u : decode rather than encode
# -b : use "base64" encoding (default)
# -q : use "quoted-printable" encoding

# Default: encode to base64
ENCODE="../base64"
DECODE="/base64.."

ACTION="encode"

while [ $# -gt 0 ]
do
	case "$1" in
	-u)	ACTION="decode"
		shift
		;;
	-b)	ENCODE="../base64"
		DECODE="/base64.."
		shift
		;;
	-q)	ENCODE="../qp"
		DECODE="/qp.."
		shift
		;;
	--)	shift
		break
		;;
	*)	break
		;;
	esac
done

if [ ${ACTION} = "encode" ]
then
	CONVERT="${ENCODE}"
else
	CONVERT="${DECODE}"
fi

cat "$ <at> " | recode -f -q "${CONVERT}"
_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Ken Hornstein | 20 Apr 16:36 2012
X-Face
Picon

Re: Aging Dependencies?

>> It occurs to me that mmencode could have a home in nmh (well, I guess exmh
>> uses "mimencode", but same thing really).  Although I see exmh can use
>> recode if available.  Maybe this is a non-problem?
>
>Eventually the attached script is sufficient?

My reading of the exmh source code shows me that this isn't necessary;
it will call recode with the right arguments directly.  But maybe that
support is newer than 2.7.2?  (I will confess to running a CVS snapshot
because I needed stuff that wasn't fixed in a release).

--Ken
Valdis.Kletnieks | 20 Apr 17:04 2012
Picon

Re: Aging Dependencies?

On Fri, 20 Apr 2012 10:36:16 -0400, Ken Hornstein said:
> >> It occurs to me that mmencode could have a home in nmh (well, I guess exmh
> >> uses "mimencode", but same thing really).  Although I see exmh can use
> >> recode if available.  Maybe this is a non-problem?
> >
> >Eventually the attached script is sufficient?
>
> My reading of the exmh source code shows me that this isn't necessary;
> it will call recode with the right arguments directly.  But maybe that
> support is newer than 2.7.2?  (I will confess to running a CVS snapshot
> because I needed stuff that wasn't fixed in a release).

Yes, it is newer:

cvs repository 06/20/2008 az <at> debian.org
  incorporated a number of patches from debian
  exmh.l: silence some man warnings
  lib/mh.tcl: mention install-mh by full path in initial greeting
  lib/bogo.tcl: add learning-from-stdin for learning ham, too
   (not just spam)
  lib/glimpse.tcl: add the -W glimpse option (and scope for
   whole file) to permanent preferences
  lib/scan.tcl, lib/folder.tcl: fix the stale scan cache problem
  lib/uri.tcl, html_links.tcl: make html links clickable in
   inline-displayed html, and consolidate status line handling for links
  lib/seditExtras.tcl, lib/mime.tcl: patch from Marion Hakanson to
   fix fd leakage in internal mime qp/base64 decoder
   patch from debian: add support for recode as alternative to mimencode

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users

Gmane