Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Ugh!  Ack!  Argh!  Nggh!
Date: 17 Jul 1999 05:21:03 -0700	[thread overview]
Message-ID: <m3vhbj79hs.fsf@satellite.local.lan> (raw)
In-Reply-To: Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "17 Jul 1999 13:02:25 +0200"

Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

> Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> 
> > Ken McGlothlen <mcglk@itchy.serv.net> writes:
> > 
> > [...]
> > 
> > > Also, one question: What's a quick way to take an nnml folder and
> > > convert it to an mbox-compliant file so that I can reprocess it with
> > > procmail?  Or even a slow way?
> > 
> > % cat nnml-folder-dir/* > mboxfile
> > 
> > Or have I missed something vital?
> 
> I think you missed two things: the From_ lines and the file order.
> The From_ lines thing is probably vital...
> 
> Another possibility would be to use Gnus: create an nnfolder group and
> move all nnml messages there.  Take care that the nnml backend
> (server) and the nnfolder backend (server) are not using the same
> active file, though.


I think he just wants a spool file to run through procmail again.
In that case:  cd to Mail/nnmlgroup  then run:

sed 's/X-From-Line:/From/' `ls [0-9]*` >MBOX_OUT
NOTE: The second set of single quotes are back ticks.. not single
quotes : )

Gnus removes the "From " from the original "From line" and replaces it
with "X-From-Line:".  So let sed remove it and reinsert "From"

Test the new file with `mutt -f MBOX_OUT'. Or in gnus group buffer do `G
m f' (make nndoc group),to see if the new file is properly formatted,
if so ...  Run it back through procmail.





  reply	other threads:[~1999-07-17 12:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-15 17:59 Gnus and NoCeM Ken McGlothlen
1999-07-15 19:05 ` Colin Rafferty
1999-07-15 19:32   ` Ken McGlothlen
1999-07-15 20:27     ` Colin Rafferty
1999-07-15 21:51       ` Ken McGlothlen
1999-07-15 22:58         ` David Hedbor
1999-07-16  0:15       ` Dan Christensen
1999-07-17  3:54         ` Justin Sheehy
1999-07-17  7:02           ` Ugh! Ack! Argh! Nggh! Ken McGlothlen
     [not found]             ` <wtnu2r3bslp.fsf@licia.dtek.chalmers.se>
1999-07-17 10:15               ` Hans de Graaff
1999-07-17 16:05                 ` Michael Cook
1999-07-17 10:17               ` Kjetil Ødegaard
1999-07-17 11:02               ` Kai Großjohann
1999-07-17 12:21                 ` Harry Putnam [this message]
1999-07-17 11:14             ` Kai Großjohann
1999-07-18  7:10               ` Ken McGlothlen
1999-07-19 10:50                 ` Kai Großjohann
1999-07-27 15:37                   ` Jack Vinson
1999-07-26 17:14                     ` Hrvoje Niksic
1999-07-26 17:45                       ` Paul Stevenson
1999-07-26 17:50                         ` Paul Stevenson
1999-07-26 19:13                         ` François Pinard
1999-07-28 12:15                         ` Robert Bihlmeyer
1999-07-28 14:38                           ` Paul Stevenson
1999-07-17 10:58           ` Gnus and NoCeM Kai Großjohann
1999-07-19 17:53       ` Sudish Joseph
1999-07-15 20:49     ` Justin Sheehy
1999-07-16  4:50     ` Andrew Hobson
1999-07-16  5:37       ` Ken McGlothlen
1999-07-16 14:02         ` Jack Twilley
1999-07-15 21:32 ` Kai Großjohann
1999-07-16 15:28 ` Wes Hardaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3vhbj79hs.fsf@satellite.local.lan \
    --to=reader@newsguy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).