[fwd: GNU mailutils 1.0 released ]

Does anybody know if the latest mailutils-mh works with exmh or not?

Chris

Hello,

The GNU mailutils team is pleased to announce release of GNU mailutils 1.0.
This is the first stable release since December, 2004, introducing lots
of new features and fixing bugs found so far (see the list at the end of
this message).

The release is available by anonymous FTP from

	ftp://ftp.gnu.org/gnu/mailutils/

and from mirrors worldwide -- see <http://www.gnu.org/order/ftp.html>.

The files and their MD5 checksums are:

06e6ea37b8cde4a41144c6c7fc16ff70  mailutils-1.0.tar.bz2
2d62ce76e7c5bd22c66370b3ed0dafee  mailutils-1.0.tar.bz2.sig

default sort of address db pop-up results

I'm very fond of using "^L" to do address completion, and the vast majority of 
results are coming from my exmh "Address Book" database. If the address isn't 
an exact match, I'd like to see the results in the database "pop-up" window 
sorted by date (ie., most recent first). I could see 
yet-another-preference-item, allowing users to specify the sort order 
(chronological or by closest match). For me, the most frequent use is that I'll 
want the address of someone with whom I've corresponded recently, even if it's 
not the best match.

So, any quick suggestions on how to sort the exmh Address Book database results 
by date?

Thanks,

Mark

Exmh FreeBSD port

Hi,

It's been some time since my last post :)

I've recently converted to using the FreeBSD port on our systems, and I've
noticed that because the exmh release file isn't updated concurrent to the
CVS, there isn't a simple way to update a ported version with revisions
from CVS. Today, I found a way that isn't _too_ awkward and thought it
might be useful to others.

    *  check out the revision that you want, usually just the head of the
    tree (run first command only if the first time) - do this in
    /var/db/origins so that it will be retained for later

cvs -d:pserver:anonymous <at> exmh.cvs.sourceforge.net:/cvsroot/exmh login
cvs -z3 -d:pserver:anonymous <at> exmh.cvs.sourceforge.net:/cvsroot/exmh co -P exmh

    * change into the /var/db/origins/exmh directory and run

make realsrctar

    * copy the resulting file exmh-2.7.2.tar.gz into /usr/ports/distfiles
    and run md5 against this file

    * edit /usr/ports/mail/exmh2/distinfo, substituting the MD5 checksum
    with the above

    * optionally, remove any *.tcl files from the
    /usr/ports/mail/exmh2/files directory - they are unlikely to be needed
    now.

mime decoding og folder scan listing

Hi,

I can't get exmh/nmh to convert MIME Quoted-Printable in
message headers in the scan listing.
Showing messages work fine - converting QP.

I have followed the advice in exmh FAQ 2C setting up the environment to
the wanted locale - see enclosed config.
Any stumblestones that comes to mind ?

exmh 2.7.2, nmh 1.2, ubuntu 6.06

cheers
  Olav

~>scan -file tmp/mime.mh -form scan.default
   1  07/26*=?UTF-8?Q?Kolbj=C  Re: tegndeklarasjon<<On Wed, 26 Jul 2006, Olav.K

~>env | grep 8859
MM_CHARSET=no_NO.iso88591
LANG=no_NO.iso88591
LANGUAGE=no_NO.iso88591:en

~>grep -v ^# .mh_profile 
MailDrop: /var/mail/oak
Path: Mail
repl: -nocc me
Alternate-mailboxes: Olav.Kvittem*
Aliasfile: alias
unseen-sequence: unseen

Re: Exmh FreeBSD port

> From: Joel Hatton <exmh-users <at> auscert.org.au>
> Date: Thu, 27 Jul 2006 00:12:38 +1000
> Sender: exmh-users-bounces <at> redhat.com
> 
> Hi,
> 
> It's been some time since my last post :)
> 
> I've recently converted to using the FreeBSD port on our systems, and I've
> noticed that because the exmh release file isn't updated concurrent to the
> CVS, there isn't a simple way to update a ported version with revisions
> from CVS. Today, I found a way that isn't _too_ awkward and thought it
> might be useful to others.
> 
>     *  check out the revision that you want, usually just the head of the
>     tree (run first command only if the first time) - do this in
>     /var/db/origins so that it will be retained for later
> 
> cvs -d:pserver:anonymous <at> exmh.cvs.sourceforge.net:/cvsroot/exmh login
> cvs -z3 -d:pserver:anonymous <at> exmh.cvs.sourceforge.net:/cvsroot/exmh co -P exmh
> 
>     * change into the /var/db/origins/exmh directory and run
> 
> make realsrctar
> 
>     * copy the resulting file exmh-2.7.2.tar.gz into /usr/ports/distfiles
>     and run md5 against this file
> 
>     * edit /usr/ports/mail/exmh2/distinfo, substituting the MD5 checksum
>     with the above

Re: Exmh FreeBSD port

(adding exmh-workers to the cc: list)

On Wed, 26 Jul 2006 08:54:29 PDT, Kevin Oberman said:
> At the moment the exmh port is lacking a maintainer. The long time
> maintainer, Bruce Mah, has dropped maintainership as he no longer used
> EXMH. (He requires IMAP.)

I'm not a BSD person, but I can contribute one somewhat useful piece of
info:

> 1. Monitor exmh CVS for changes on a regular basis

> other host of Brent's choosing is not available). It's the first item
> that I fear I would not have time to properly handle.

You'd only have to check once every few months - I recently did a CVS commit
and found it was the first one in literally a year or so.  It's probably been
2-3 years since a CVS commit happened that didn't get announced to the
exmh-workers list, I think.  That's pretty low-traffic.

Would it make sense to have CVS commits auto-announced to exmh-workers? I know
other sourceforge projects have a separate -commits list, but just dropping
them to -workers isn't going to flood that list.

Then whoever is maintaining an exmh-devel port for BSD could just watch
the list, and turn the crank at their end as needed...

Does that seem a workable plan?

Re: Exmh FreeBSD port

> From:  Valdis.Kletnieks <at> vt.edu
> Date:  Wed, 26 Jul 2006 14:05:08 -0400
>
> Would it make sense to have CVS commits auto-announced to exmh-workers? I know
> other sourceforge projects have a separate -commits list, but just dropping
> them to -workers isn't going to flood that list.
> 
> Then whoever is maintaining an exmh-devel port for BSD could just watch
> the list, and turn the crank at their end as needed...
> 
> Does that seem a workable plan?

Every now and then somebody gets a bug up their butt about some feature or 
other and does a flurry of commits as they work out the details of their code. 
I'm not sure you would have liked an email for every commit I did while 
working on the sequences window.  Maybe if i were a better tcl/tk coder, I 
would get things perfect the first time, but since exmh is the only tcl/tk 
project I work on, I'm not likely to get that good quickly.

Looking at the change log, it doesn't appear that I'm the user exmh-worker 
with this pattern.

Chris

--

-- 
Chris Garrigues                         Trinsic Solutions
President                               710-B West 14th Street
                                        Austin, TX  78701-1755

512-322-0180                            http://www.trinsics.com

Re: Exmh FreeBSD port

Hi,

First, thanks for all your replies - I didn't know if my message would
generate such response! Valdis, forgive me for picking on you to respond
to directly but yours was the last message, and I had to pick someone :)

On Wed, 26 Jul 2006 22:07:08 -0400, Valdis.Kletnieks <at> vt.edu wrote:
>
>1) I'd not be surprised if most of the big CVS committers are a bit rusty
>on working with CVS branches.
>
>2) I doubt we can only get notifications for commits to HEAD (which would
>mean work on a branch would be silent till the branch got merged again).
>
>Oh well...

I've reflected some more on this overnight, and I've thought of an approach
to the port that might work ok and reduce the workload on the exmh
committers. I'm definitely appreciative of the effort that people like
Chris (who I'm sure underrates his expertise in tcl/tk) have put into exmh,
and I don't want to make any more work for them than absolutely necessary.

My alternative method:

	o leave the current backend of exmh development the same ie major
	releases relatively long-term and static, with ongoing development
	in cvs

	o retain the current mail/exmh2 port and its relationship to major
	exmh version

Re: Exmh FreeBSD port

If it would help, I can add Joel to the source forge committer list.
I'll really need to make a new tarball release, call it 2.8.0, that
reflects the CVS head.  I'd like to get the "patch_exmh.sh" script
into that release, probably naming it "patch_exmh_freebsd.sh" or
something, and train the little sed script that knows about version
numbers to fix it up.

>>>Joel Hatton said:
 > 
 > Hi,
 > 
 > First, thanks for all your replies - I didn't know if my message would
 > generate such response! Valdis, forgive me for picking on you to respond
 > to directly but yours was the last message, and I had to pick someone :)
 > 
 > On Wed, 26 Jul 2006 22:07:08 -0400, Valdis.Kletnieks <at> vt.edu wrote:
 > >
 > >1) I'd not be surprised if most of the big CVS committers are a bit 
rusty
 > >on working with CVS branches.
 > >
 > >2) I doubt we can only get notifications for commits to HEAD (which 
would
 > >mean work on a branch would be silent till the branch got merged again).
 > >
 > >Oh well...
 > 
 > I've reflected some more on this overnight, and I've thought of an 
approach
 > to the port that might work ok and reduce the workload on the exmh

Paul Sala/Burlington/IBM is out of the office.

I will be out of the office starting  07/28/2006 and will not return until
08/14/2006.

If needed, I will respond to your message when I return. My backups are
Reese Ferry , May-hung Chan and Stacey King.