[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Request Deprecation of mts.conf's mmdelim1 and mmdelim

From: Ralph Corderoy
Subject: Re: [Nmh-workers] Request Deprecation of mts.conf's mmdelim1 and mmdelim2.
Date: Wed, 24 May 2017 18:36:11 +0100

Hi again,

More woes.

> I take this to be an MH-only file, unused by other parties.  Thus if
> nothing in nmh reads them then it doesn't have to bother to create and
> maintain them any more?  And so all the supporting code can also go
> pre-1.7?

The main user in creating map files is inc(1), but only when POP3 is
being used, and only then if -pack has been given.  Before Larry Hynes
deleted the interesting bit, inc(1) used to say

    If inc uses POP, then the -pack file switch is considered.  If
    given, then inc simply uses the POP to packf the user's maildrop
    from the POP service host to the named file.  This switch is
    provided for those users who prefer to use msh to read their

The code duplicates the packf code that's elsewhere, always assumes
packf's -mmdf, so no mbox option, and has the ^A^A^A^A munging but
without the buffer-boundary bug because it stdios by line.

Untwining inc's map code whilst leaving -pack seems awkward, e.g. it may
be appending to an existing pack file and so looks up, using the map
file, how many messages are in it first so scan() can give the following
message numbers.

inc(1) implies above that `inc -host pop3.example.com -pack spool.mmdf'
is for msh(1) users.  msh has gone post 1.6.  Can inc's -pack die too
before 1.7?  It seems there's quite a bit of lingering msh rotting away.

Cheers, Ralph.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]