NA> I have identified a serious problem with BinkD .FLO file management
NA> affecting all versions of D'Bridge from present to past versions. If your
NA> name is not Ward Dossche then please review this carefully.

Was wondering if that issue you found has any relation to this problem:

------------------------

My D'Bridge BBS instance had many pending packets to go to my hub.  It was
polling over and over and sending the packets, but here is what seemed to be
happening:

The packets would send, the hub would receive them.  The hub would then do
nothing with them and the BBS instance never deleted the MSG.* file, but the
*.PKT file would be gone.  The BBS instance would then create another *.PKT
file with 0 bytes and this would happen over and over again.

Not sure what is going on or when this started.

My setup is a bit different in that WWIVTOSS dumps the MSG.* & *.PKT files in
the D'Bridge BBS instance's "Inbound" directory.
---------------------------------

I had reverted my BBS instance back to an earlier 3.99 version, which fixed
it.  I was supposed to call you about this months ago, but normal life has
gotten in the way.  I can call you this weekend if you want to do testing
on my VM.

One other question...  When there is routed netmail going through D'Bridge
(like between my instances), does D'Bridge add or remote the INTL kludge on
the netmail or just pass it through passively?

I'm working on an issue that appears to be only effecting Mystic BBS
netmails going to my BBS.  Mystic doesn't use the MSGID: kludge and there
are no Origin: lines in netmails, so WWIVTOSS isn't grabbing the sender's
node information.  

I believe Mystic uses the INTL kludge, for which I'm trying to add support
to WWIVTOSS to identify and capture that information, so netmails from
Mystic to my BBS works properly and doesn't display my own node information
vs the real sender.

I'm working with Nick to try and capture a netmail that his system creates
before it is sent to me, so I can take a deeper look at the header and try
and update WWIVTOSS to get his node info from it.

- Mark

--- WWIVToss v.1.50