TIP: Click on subject to list as thread! ANSI
echo: batpower
to: Paul Quinn
from: mark lewis
date: 2009-04-23 15:01:32
subject: Newsgroup (NG) digests

PQ> Since the JAM messagebase that I use has trouble storing/presenting
 PQ> the full text of digest posts, I'm not getting full value.  In 
 PQ> short, I'm not seeing all there is to see in some NG posts.  I 
 PQ> need to do something about it.  :)

JAM message bases should be good for messages up to 2Gig in size... i know
that back in the heyday, when i was working on my posting tool, i posted
the complete nodelist to my JAM bases numerous times... where i ran into
problems was with the tools i used to read the messages in the JAM bases...
many of those tools were limited in their memory allocation and thus
limited in the size of a message they could display... i don't think that
your problem is with the storage in JAM bases unless the tools you are
using to place those digest posts in the JAM bases are similarly limited
like the readers i speak of above...

all that aside, i can fully understand your reasoning for wanting to split
the digests... personally, i don't do digests prefering instead to get the
invidivial messages sent as they are submitted... it save me some work and
i don't have to think about spliting the digests into individual messages
:)

 PQ> I plan on doing a -very- rudimentary splitting function only, due
 PQ> to the complexity of the structure of digest emails.  (The digests
 PQ> have multiple "From:" and "Date" lines and have
no real delimiter
 PQ> between posts.)  However, there may be a way of doing it with
 PQ> fgrep[386] (-gasp-!), using its character wildcard search ability.

i'd suspect that like other similar *nix formats, the next From: line would
indicate the start of the next message's header... when reading the header,
it is all header until you hit the first blank line... after that,
everything is the body until the next From: line... this provided that the
From: line is the first line of each and every header...

 PQ> Has anyone tried this process yet?  Or, anything similar perhaps? 

i can't say that i have but it should be easy enough to do... i have seen
some digests years ago and i'd be looking to break it apart as described
above... how to do it with DOS tools i have no idea as i'd whip out my
pascal compiler and smack together a quick tool to do it for me... maybe
even something using 4DOS/4NT/4OS2 btm capabilities since they do have line
parsing built right in :)

)\/(ark

* Origin: (1:3634/12)
SEEN-BY: 10/1 3 34/999 120/228 123/500 128/2 140/1 222/2 226/0 249/303 250/306
SEEN-BY: 261/20 38 100 1381 1404 1406 1410 1418 266/1413 280/1027 320/119
SEEN-BY: 393/68 396/45 633/104 260 267 285 640/954 690/682 734 712/0 313 848
SEEN-BY: 800/432 801/161 189 2222/700 2320/100 105 200 2905/0
@PATH: 3634/12 123/500 261/38 633/260 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.