Subj : Re-attach abandoned mail archives?
To : Johan Zwiekhorst
From : Peter Knapper
Date : Sat Oct 18 2003 11:01 am
Hi Johan,
JZ> I've sent you an e-mail with a snapshot picture of the
JZ> SOB window.
Got that thanks. I now know why we see different things. Because I did not have
an orphaned file to be able to "see" the problem, I created one by copying a
valid mail archive file to a fake node number. HOWEVER, the node number I
happened to use was LOWER than the FIRST .FLO file in the list, hence why SOB
here showed it ahead of all KNOWN nodes.
I have now created new orphaned files using node numbers WITHIN the normal
addressing range for the Outbound Area I am using, so I should now be seeing
things as you are seeing them.
In the screen capture you sent, ALL the orphaned files were for the LAST node
number listed, hence they appeared to not be listed in any particular order,
but in fact they WERE listed correctly. Note that the filenames (IE the
address) of all the orphaned files is correct for the node they are listed
under, so ALL of those orphan files could safely be attached back to the .FLO
that appears immediately before the orphans. I also note that some of the DATES
for those files are quite old, are they correct?
So it looks like you would be safe to re-attach all those files to the .FLO for
that node.
JZ> My Binkd/2 0.9.5a (and all versions before that) has a
JZ> tendency to trap regularly. Here's the last time this
JZ> happened:
My binkd 0.9.5 is dated 05-09-03 (dd-mm-yy) and is the Watcom compiler build I
think, not the EMX build. The EMX build seems to have some sort of stability
problem here, but I have bever seen a trap from BinkD. I have 2 machines
running it, one Warp4 FP15, the other Warp4 FP9.
JZ> The Russian binkd authors, however, claim that this
JZ> could be in no way responsible for flow files getting
JZ> deleted and so leaving orphaned mailarchives.
JZ> Nevertheless, *something* seems to be deleting flow
JZ> files on my system on a regular basis (once or twice
JZ> every couple of months!).
That does sound really strange, I can't say I have ever had any issues like
that. I hope to have a screenshot I can send once I get some S/W installed.
Cheers.............pk.
--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
