last dev HM (CVS)

I'm not sure if I'm missing something.... I got the CVS version of HM this (U.S. East Coast) morning, compiled + installed it, added these 2 options to my .hmrc file:

# 1 - Require non-null Message-IDs
# 0 - Allow null Message-IDs
hm_require_msgid = 0

# 1 - Discard duplicate Message-IDs
# 0 - Allow duplicate Message-IDs (modify them to be unique) hm_discard_dup_msgids = 0

... and then tested it (by sending a message to a mailing lsit that uses HM for archiving) and got the same error as before:

Message-ID is missing, ignoring message with subject 'Foo Bar'.

hypermail -V shows the same version/patch level info as the previous HM (2a22)...

I am invoking HM as follows:
... "|/usr/local/bin/hypermail -c /usr/home/majordomo/.hmrc -i"

File /usr/home/majordomo/.hmrc does exist, just checked.

Am I missing something, using HM incorrectly, or ... ?

Thanks!

Otis Gospodnetic

--
InfoJump - listing over 4,000 electronic periodicals
         - http://www.infojump.com/



> -----Original Message-----

> From: owner-hypermail_at_landfield.com

> [mailto:owner-hypermail_at_landfield.com]On Behalf Of Paul Haldane

> Sent: Friday, June 04, 1999 12:54 PM

> To: Daniel Stenberg

> Cc: Hypermail list

> Subject: RE: possible bug (was: options.h)

>
>


> I've just committed the following changes to the CVS server...

>


>   - Applied Tom van Alten's patch to correct improper formatting

>     of messages when hm_showhtml = 0 and showheaders = 1.

>


>   - New code to (optionally) accept messages wth no msgid.  Default

>     is to require msgids in all messages - use hm_require_msgid = 0

>     to avoid this check.

>


>   - Made handling of duplicate msgids optional.  By default duplicates

>     are discarded.  To accept them (replacing the msgid with a generated

>     msgid) use hm_discard_dup_msgids = 0.

>


>   - Check return value from addhash when reading old messages.  Messages

>     already archived should be valid but safer to check.

>


> Main thing to note here is that the default behaviour for handling

> messages with duplicate message-ids has changed.  a22 accepted them by

> default.  With this version you need to use

>    hm_discard_dup_msgids = 0

>


> Paul

>


> > > I've not committed the change to generate new msgids for

> messages with no

> > > msgid yet (in fact looking at the source, I've not even

> written it - not

> > > a problem - I've got most of it written already).

> >

> > Ah, I'm a little ahead of my time then! :-)

> >

> > > I'll probably make this optional behaviour.  In my situation

> I'd probably

> > > want to treat missing/duplicate msgids as an error but I

> understand that

> > > other people may not.

> >

> > Yes, I'd prefer it optional too. I want to block duplicates.

> >

> > > If I can get handling of missing msgids done and tested today then we

> > > could push out another release.

> >

> > Sure!

> >

> > > There's also Tom van Alten's formatting patch and the mutt

> mime separator

> > > patch to go in I think.

> >

> > That mutt fix is already included in the 1.19 version of

> parse.c. I see that

> > I didn't properly write that in the log, but I checked and the fix is in

> > there...

> >

> > --

> >              Daniel Stenberg - http://www.fts.frontec.se/~dast

> >    ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

> >

> >

>
>