Hi Ken,
> Yes ... but I would personally prefer if it was more generic. Like if
> the -endofdigest switch took a regular expression
That's an improvement. An alternative is a -preproc that took a command
that preprocessed each MIME-decoded part before being read for bursting;
only used in
ralph wrote:
> Hi Paul,
>
> > An obvious fix (for me) is to pre-process the digest, and
> > hyphen-escape all lines which follow the "END OF DIGEST" line and
> > which begin with a '-', by adding an extra '- ' at the start of line.
> > If I do that, then burst will do the right thing, and
>If I were to become extra-ambitious, and create a patch which added a
>"-endofdigest" switch which did something similar, would there be
>interest?
Yes ... but I would personally prefer if it was more generic. Like
if the -endofdigest switch took a regular expression, because as far
as I can
Hi Paul,
> An obvious fix (for me) is to pre-process the digest, and
> hyphen-escape all lines which follow the "END OF DIGEST" line and
> which begin with a '-', by adding an extra '- ' at the start of line.
> If I do that, then burst will do the right thing, and ignore all of
> the trailer
I'm on a list which, for historical reasons, is available only
in digest form. (Sigh.)
Like many digests, it includes hyphen-rich separator lines in the
trailing text of the digest, causing burst to create a flurry of
malformed messages when it parses according to RFC 934. Hoping for
the
