Re: nmh 1.1 release canidate uploaded

Scott Lipcon <[EMAIL PROTECTED]> wrote: > I don't think release candidates belong in the ports collection. 1.1rc1 > should be relatively stable, but it hasn't been tested much at this point. > Development has gone very slowly.If there is enough demand, I'd consider > making a second port,

Re: nmh 1.1 release canidate uploaded

Ken Hornstein <[EMAIL PROTECTED]> wrote: > Everyone, > > I've created a nmh 1.1 release canidate. You can get it from: > > http://savannah.gnu.org/download/nmh/nmh-1.1-RC1.tar.gz Well...yesterday I sent a message from a different email address that I imagine the list owner might be reading abo

Re: folder-specific defaults? [long]

[EMAIL PROTECTED] wrote: > => Allow folder specific component files to be located in a centralized > => location. For example, if I wanted a custom "scan.monthly" format > => file for my inbox, I would create a file with a pathname of > => `mhpath`/scan.monthly.inbox. It does get ambiguous with

Re: folder-specific defaults? [long]

Jerry Peek <[EMAIL PROTECTED]> wrote: > Tobias Nijweide wrote: > > 2 Where do we look for component files: > > > > a - If fixed path (Starting with '/', '~', './' or '../'), only one choice. > > b - Current, or selected folder > > c - Recursive search upwards from current folder, up to: > > d -

Re: folder-specific defaults?

Earl Hood <[EMAIL PROTECTED]> wrote: > ... > All we care about is any argument starting with a '+', so nothing > complex is required. Actually...that's not quite complete...what we care about is any argument starting with a '+' that's not an argument to some other argument. Usage: scan [+fo

Re: folder-specific defaults?

Earl Hood <[EMAIL PROTECTED]> wrote: > On June 27, 2002 at 21:54, Tobias Nijweide wrote: > > > [EMAIL PROTECTED] said: > > > * I have a folder where I always want to use a different '-form' > > > option for scan. > > > > Don't have a solution for this. You could code a variant of the patches >

folder-specific defaults?

I was just wondering...I keep running into cases like these: * I have a folder where I always want to use a different '-form' option for scan. It's my +trash folder where my mailagent mail filtering files suspected spam and other stuff after adding a "X-Trashed-By" header explaining why...so

FW: ports/36307: nmh port cuts off last part of sender domain

Hi- This is a bug report from the FreeBSD ports mailing list. I'm the maintainer of this port, so I figured I'd look into it a bit. Does this behavior sound familiar to anyone? Thanx, Scott - Forwarded message from Matthias Buelow <[EMAIL PROTECTED]> - Date: Mon, 25 Mar 2002 17:23:4

Re: APOP

Doug Porter <[EMAIL PROTECTED]> wrote: > Christophe =?ISO-8859-1?B?UHLpdm90YXV4?= <[EMAIL PROTECTED]> wrote: > > > > I am trying to use APOP with NMH-1.0.4 port under FreeBSD (in > > the port tree) however this function seems not to be available. > > You need to give the `--enable-apop' argumen

Re: seconds > 1e9 bug in nmh-1.0.4

Bill Sommerfeld <[EMAIL PROTECTED]> wrote: > ... > The problem lies in the guts of the PUTD() macro, which > contain the following code fragment: > > c = 10; > while (c <= i) > c *= 10; > > The repeated "c *= 10" done here will overflow a 32-b

Re: Re-sorting folders, exmh or nmh question ?

Marc BAADEN <[EMAIL PROTECTED]> wrote: > ... > whether this is something only implemented in this form > by exmh, which also raises the question whether you can > easily perform this function on all or a number of folders ? Sounds like a job for a shell script...if you're using nmh with its 'fli

Re: [Fwd: Re: Questions about IMAP and sequences]

t it's been a while, so I'm not positive. And I don't have an easy way to test it out at the moment. -- Scott Blachowicz

Re: [Fwd: Re: Questions about IMAP and sequences]

> > (2) When away from your main system, you might want to be able to > > use IMAP to access your nmh folders from a remote site. > > _This_ would require a special IMAP server; I'm not sure one like > this exists, and would be a lot of work. The IMAP model, for good > or bad, is you alwa

Re: [Fwd: Re: Questions about IMAP and sequences]

t; script: #!/bin/sh pick -seq picked ${1+"$@"} && scan picked that I use a lot to do things like: picks -subj IMAP then if I'm not interested in them, I can 'rmm' them all at once or 'refile' them or whatever by sequence name. -- Scott Blachowicz

Keeping last message number?

Hi- >From what I can think of, I don't think there's a way to do this, but... I would like to (sometimes, at least) read my nmh folders with gnus in emacs. If I understand things correctly, it would be a lot easier to do that if message numbers didn't get reused. Operating totally within gnus,

Re: Outgoing mail not saved

Neil W Rickert <[EMAIL PROTECTED]> wrote: > Copy the 'components' file to your $HOME/Mail directory. Edit it, > and add an "Fcc:" line. The components file is in the 'etc' > directory of 'nmh'. That doesn't give you dynamically named folders (he was using 'date' commands to generate the folder

Re: $USERPLUS / $USER_EXTENSION (was Re: boolean type, DIFFERENCES...)

> > FYI...Postfix calls that variable "recipient_delimiter" in its > > configuration file and it defaults to '+'. So, what happens if > > USERNAME_EXTENSION isn't set, but "masquerade:" includes > > "username_extension"? > > I think you misunderstood my comments above. $USERNAME_EXTENSION is th

Re: $USERPLUS / $USER_EXTENSION (was Re: boolean type, DIFFERENCES...)

Dan Harkless <[EMAIL PROTECTED]> wrote: > Here's my ChangeLog entry: > > * Changed the new "plussed_user" option to mts.conf's > "masquerade:" to "username_extension" after getting feedback from > qmail users, who use '-' as a separator rather than '+'. Removed > checkin

Re: nmh security update

"Dan Harkless" <[EMAIL PROTECTED]> wrote: > D'oh! Sorry about that, Scott (and anyone else affected). Stupid of me to > think my prototype would be free of conflicts on all UNIXen. That's what I > get for coding in the middle of the night. I've fixed it so now configure > looks in and for t

Re: nmh security update

[EMAIL PROTECTED] (Ruud de Rooij) wrote: > This bug has been fixed in nmh 1.0.3 and we encourage you to upgrade > immediately. The fixed package is available at > > ftp://ftp.mhost.com/pub/nmh/nmh-1.0.3.tar.gz Just updating the FreeBSD port to nmh-1.0.3 and ran across this problem...

Re: Problem with Fcc

> > Fcc +mail_log: errored (0177400) > I searched through the nmh source and there is no mention of "177400", so > you should ask the exmh people about that cryptic error. I'd bet that the "177400" isn't a literal string, but an integer printed out with a "%d" printf format, so a string search f

Minor tweak to man/Makefile

Hi- In that Makefile, it links mh-profile.5 and mh_profile.5 in the install step, but fails if mh_profile.5 is already there for some reason. I use the appended patch to just force removal before creating the link. Not sure if it should really use some $(RM) make variable or some such, though. [

Re: Upped the development source version number to 1.0.3

"Dan Harkless" <[EMAIL PROTECTED]> wrote: > > so bouncing between even & odd release numbers over time seems weird. > > There's no bouncing between them. People with FTP access get the > even-numbered releases. People with CVS access can get the odd-numbered > developer versions in between as

Re: Upped the development source version number to 1.0.3

Simon Burge <[EMAIL PROTECTED]> wrote: > I've never been a fan of the internal vs. external release number idea. > If we have 1.0.2 being released then 1.0.4, people may wonder whatever > happened if 1.0.3 and so on... Same here...I may be old-fashioned, but I think the version number should be

Re: nmh snapshot

Doug Morris <[EMAIL PROTECTED]> wrote: > Scott Blachowicz wrote: > >and to make sure HAVE_MKSTEMP doesn't get defined (since it's usage is > >wrong)). And, I also need to get some "real" work done, too :-)). > > Check the usage. That's one

Re: nmh snapshot

Doug Morris <[EMAIL PROTECTED]> wrote: > I've fixed the tests and put up a new shapshot at > > For what it's worth - that snapshot builds out-of-the-box on FreeBSD 3.2. I need to go cobble up a new set of patch files to

Re: Problem compiling nmh-1.0.1 on Linux SuSE

Doug Morris <[EMAIL PROTECTED]> wrote: > Ruud de Rooij wrote: > >Daniel FLIPO <[EMAIL PROTECTED]> writes: > >[ This has been fixed in the CVS version. Doug, should we release a > >1.0.2 soon, if only to eliminate these recurring compilation > >problems? ] > > Yes, for that and to get your -grou

use of mkstemp() in nmh

Hi- I was just fiddling with updating the FreeBSD "port" of nmh from 1.0 to 1.0.1 when I noticed that I get this warning compiling: cc -c -DHAVE_CONFIG_H -I.. -I. -I.. -O -pipe m_tmpfil.c m_tmpfil.c: In function `m_tmpfil': m_tmpfil.c:18: warning: passing arg 1 of `unlink' makes poin