Hi All!

Does anyone here have or know of a utility which can detect abandoned mail archives (mailarchives without an entry in the corresponding flow file) in a binkley-style outbound directory and re-attach them to the node they were destined for? I would like an OS/2 utility, but a DOS utility will do fine as well. No Windows here.

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hi All!

Does anyone here have or know of a utility which can
detect abandoned mail archives (mailarchives without an
entry in the corresponding flow file) in a binkley-
style outbound directory and re-attach them to the node
they were destined for? I would like an OS/2 utility,
but a DOS utility will do fine as well. No Windows here.

Possibly BONK (DOS) or SOB (Son of Bonk), if I am remembering the utilities correctly..... Bonk allowed for some cleanup of the outbound mail directories.
I'm not sure of all the options it allows with orphaned files.... It's been a
while since I've used such a utility.

Yaboom also comes to mind, but I don't remember the details for that utility....

Take care.....

Bob Jones, 1:343/41



--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hi Johan,

Does anyone here have or know of a utility which can
detect abandoned mail archives (mailarchives without an
entry in the corresponding flow file) in a binkley-
style outbound directory and re-attach them to the node
they were destined for? I would like an OS/2 utility,
but a DOS utility will do fine as well. No Windows here.

Have a look for SOB (Son of Bonk), its an OS/2 PM utility that should be able to that. Look for SOB_110.ZIP, about 150KB, dated 1994.

Cheers...........pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hi Peter!

In your message to me, dated <Wednesday October 08 2003 21:12>, you wrote:

Does anyone here have or know of a utility which can
detect abandoned mail archives (mailarchives without an
entry in the corresponding flow file) in a binkley-
style outbound directory and re-attach them to the node
they were destined for? I would like an OS/2 utility,
but a DOS utility will do fine as well. No Windows here.

PK: Have a look for SOB (Son of Bonk), its an OS/2 PM utility that should
PK: be able to that. Look for SOB_110.ZIP, about 150KB, dated 1994.

As far as I can see, SOB can delete 'lost' mail archives, but not re-attach them.

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hi Bob!

In your message to me, dated <Tuesday October 07 2003 21:44>, you wrote:

Does anyone here have or know of a utility which can
detect abandoned mail archives (mailarchives without an
entry in the corresponding flow file) in a binkley-
style outbound directory and re-attach them to the node
they were destined for? I would like an OS/2 utility,
but a DOS utility will do fine as well. No Windows here.

BJ: Possibly BONK (DOS) or SOB (Son of Bonk), if I am remembering the
BJ: utilities correctly..... Bonk allowed for some cleanup of the
BJ: outbound mail directories. I'm not sure of all the options it allows
BJ: with orphaned files.... It's been a while since I've used such a
BJ: utility.

BONK and SOB both clean up the outbound by deleting stray files. Neither will re-attach stray mail archives.

BJ: Yaboom also comes to mind, but I don't remember the details for that
BJ: utility....

I can't find that one on the internet...

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Does anyone here have or know of a utility which can
detect abandoned mail archives (mailarchives without an
entry in the corresponding flow file) in a binkley-
style outbound directory and re-attach them to the node
they were destined for? I would like an OS/2 utility,
but a DOS utility will do fine as well. No Windows here.

BJ: Possibly BONK (DOS) or SOB (Son of Bonk), if I am remembering the
BJ: utilities correctly..... Bonk allowed for some cleanup of the
BJ: outbound mail directories. I'm not sure of all
the options it allows
BJ: with orphaned files.... It's been a while since I've used such a
BJ: utility.

BONK and SOB both clean up the outbound by deleting
stray files. Neither will re-attach stray mail archives.

Ok. Then I guess I need to ask, what is allowing files to get detached from the mail archives with out the files getting transfered? If the detached files
are not zero length then there is a problem somewhere that needs correcting, and not with a kludge that just reattaches them to the outbound flow files.....
If they are zero length, the bonk or sob will allow for cleanup.....

BJ: Yaboom also comes to mind, but I don't remember the details for that
BJ: utility....

I can't find that one on the internet...

May have to dig into my archives to see what comes up by that name....

Ok, look for file YABP120.ZIP (an OS/2 port). I have a copy on my bbs in one of my old (archive) file areas. This one came down the fernwood file distribution some time ago. Looks like I have an older DOS version as YABOM110.ARJ, also in one of my old file areas.

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Johan Zwiekhorst (2:292/100) wrote to Bob Jones at 00:00 on 09 Oct 2003:

BONK and SOB both clean up the outbound by deleting stray files.
Neither will re-attach stray mail archives.

BJ: Yaboom also comes to mind, but I don't remember the details for that
BJ: utility....

I can't find that one on the internet...

David Nugent's InspectA may do the job for you. I can get a copy to you if you
can't find one on the Web.

Take care,

Steven Horn (steven_a_horn@yahoo.ca)
Moderator, ALASKA_CHAT
--- timEd/386 1.10.y2k+
* Origin: Yukon Mail (northof60.tzo.com), Whitehorse,Canada (1:17/67)

Hi Johan,

PK>> Have a look for SOB (Son of Bonk), its an OS/2 PM
PK>> utility that should
PK>> be able to that. Look for SOB_110.ZIP, about 150KB, dated 1994.

As far as I can see, SOB can delete 'lost' mail
archives, but not re-attach them.

Highlight the "lost" archive then press Right Mouse Button. Select the "unorphan" option. I think that one does it.

Cheers.....................pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Following up a message from Bob Jones to Johan Zwiekhorst About Re-attach abandoned mail archives?:

Yaboom also comes to mind, but I don't remember the details for that utility....

I do not know if the author is still around, at least by internet. I do not see
him in my nodelist.


YaBom V3.00
Yet Another Binkley Outbound Manager
A fully 5D aware Outbound Manager/Packer/Scheduler
Berin Lautenbach 1991-1995
3:620/248@fidonet
blautenb@auug.org.au

I. Introduction

Just after Binkley Term 2.50 was released, I decided to convert from
Front Door. It was something I'd wanted to do for a while, but I run
quite a few points off the system, as well as operating in two
domains, and the idea of converting from 4D (nearly 5D) aware
software to pointnets didn't do much for me :>. When Binkley 2.50 was
released, I jumped in feet first, and converted over, thinking that
software would be released very quickly to support the 5D address
system of the new Binkley. I was wrong. After a few weeks of
fudging mail packing, I got a bit fed up and decided to write my own.
(I ran a Remote Access system, and use IMail for Echo Mail,
converting the file attaches to ?LO files using this little beast).
YaBom is the result.

YaBom is a complete Binkley Term outbound handler. It packs all
Netmail into the correct bundle types for the correct destinations,
preserving all message attributes (such as packing crash messages
into a *.CUT file), and preserves all file attach attributes (such as
Delete and Truncate when sent).

It also schedules all the mail in the outbound area according to
timed events set up in an external route file, very similar to that
used in QMail or Front Door, thus allowing you to poll nodes or send
mail at particular times, according to particular nodes, during the
day.

The third major feature of YaBom is that it provides an outbound
manager, allowing you to manipulate the outbound area, down to
deleting messages and files WITHIN an outbound packet, and changing
outbound types by hand. This allows the Sysop of a Binkley Board to
handle the mail properly according to his/her needs.

All this is done with full 5D support, and the outbound manager uses
the V7 nodelist to look up systems. To run most effectively it must
also have its own (small) index file that allows it to look up nets
quickly and efficiently.

Hope this helps. Keep us posted.

We are a fine board trying to make it better.
http://www.pris.bc.ca/ghannah
ghannah@pris.bc.ca
Cheers! Gord
-=Team OS/2=-
--- timEd/2 1.10.y2k+
* Origin: Marsh BBS (c), Dawson Creek, BC Canada (1:17/23.1)

Gord Hannah (1:17/23.1) wrote to Johan Zwiekhorst at 18:17 on 09 Oct 2003:

Yaboom also comes to mind, but I don't remember the details for that utility....

I do not know if the author is still around, at least by internet.
I do not see him in my nodelist.

YaBom V3.00
Yet Another Binkley Outbound Manager
A fully 5D aware Outbound Manager/Packer/Scheduler
Berin Lautenbach 1991-1995
3:620/248@fidonet
blautenb@auug.org.au

Try 'berin@ozemail.com.au'. It seems he's doing a lot of work with Debian.

Take care,

Steven Horn (steven_a_horn@yahoo.ca)
Moderator, ALASKA_CHAT
--- timEd/386 1.10.y2k+
* Origin: Yukon Mail (northof60.tzo.com), Whitehorse,Canada (1:17/67)

Hi Steven!

In your message to me, dated <Wednesday October 08 2003 20:46>, you wrote:

SH: David Nugent's InspectA may do the job for you. I can get a copy to
SH: you if you can't find one on the Web.

I have it. InspectA doesn't seem to be able to un-orphan orphaned mail archives.

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hi Peter!

In your message to me, dated <Thursday October 09 2003 19:24>, you wrote:

PK: Highlight the "lost" archive then press Right Mouse Button. Select the
PK: "unorphan" option. I think that one does it.

Yes, that works. Unfortunately, SOB doesn't seem to able to show me ONLY the orphaned files, which means I have to check for each file manually if there's an entry in the corresponding flow file. I really wanted a utility that would do this automatically, without any human intervention. If there's no such utility, I'll guess it's time to write a Rexx script to do this myself...

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hello Johan.

07 Oct 03 20:40, you wrote to All:

Does anyone here have or know of a utility which can detect abandoned
mail archives (mailarchives without an entry in the corresponding flow file) in a binkley-style outbound directory and re-attach them to the
node they were destined for? I would like an OS/2 utility, but a DOS utility will do fine as well. No Windows here.

It is one of the reasons why I do not like running system that uses attachments. I found fileboxes to be much cleaner and these problems nonexistent. As to your problem, if you are familar with how BSO works then you can simply reattach them manually. I know of no utility to detect this.

Perhaps now that someone is working on squishmail, filebox support can be added?

Matt

e-mail: matt [at] thunderdome.ws | icq: 16568532 | yahoo: mbedynek

---
* Origin: Thunderdome Server Project - http://fido.thunderdome.ws/ (1:106/1)

Hi Johan,

PK: Highlight the "lost" archive then press Right Mouse Button. Select the
PK: "unorphan" option. I think that one does it.

Yes, that works. Unfortunately, SOB doesn't seem to
able to show me ONLY the orphaned files,

I don't have any orphaned files at the moment so I can't be sure, however from memory, the orphaned files ALWAYS show up at the top of the list, BEFORE any .FLO files. Normally SOB lists files in this order -
All unrecognised files (EG: BinkD .ILO and .TRY files),
All unattached packet files,
Then for each valid .?UT and .?LO file found -
.?UT and .?LO files are listed in Network/Node order,
All files listed INSIDE the previous .?UT or .?LO file.

All unattached files should be included in those 2 groups right at the top of the list. You may also wish to use -
Options ==> File Filtering

to try and isolate your files. I don't have any "bad" mail packets at the moment so I can't tell exactly what happens, but SOB probably can do what you want.

I really wanted a
utility that would do this automatically, without any
human intervention.

Then a PM app is probably not a lot of use for unattented operation. Do you frequently have a lot of orphaned files? Its rare that I see them here.

Cheers...................pk.


--- Maximus/2 3.01
* Origin: === NZCC Maxie BBS. Ak, NZ +64 9 444-0989 === (3:772/1)

Johan Zwiekhorst (2:292/100) wrote to Steven Horn at 16:48 on 11 Oct 2003:

I have it. InspectA doesn't seem to be able to un-orphan orphaned
mail archives.

Now there's a bummer.:-)

Take care,

Steven Horn (steven_a_horn@yahoo.ca)
Moderator, ALASKA_CHAT
--- timEd/386 1.10.y2k+
* Origin: Yukon Mail (northof60.tzo.com), Whitehorse,Canada (1:17/67)

Hello Johan!

11 Oct 03 16:49, Johan Zwiekhorst wrote to Peter Knapper:

manually if there's an entry in the corresponding flow file. I really wanted a utility that would do this automatically, without any human intervention. If there's no such utility, I'll guess it's time to
write a Rexx script to do this myself...

Considered doing that too, since the filename algorithms are simple enough...but once I researched my mailer logs I discovered that they were successfully sent as the identical number of bytes as the orphan file. It seems to be the truncate that was failing for me and not the transfer. Wouldn't
surprise me if there were some access collions, as I have multiple nodes and apps pointed to the same outbound dir on a Netware server.

Might take a look at yours, if you haven't checked that already.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

It is one of the reasons why I do not like running
system that uses attachments. I found fileboxes to be
much cleaner and these problems nonexistent. As to
your problem, if you are familar with how BSO works
then you can simply reattach them manually. I know of
no utility to detect this.

Perhaps now that someone is working on squishmail,
filebox support can be added?

You will need to toss a message over to the Tub echo if you want such a discussion to happen concerning Squish.... I'll admit, we have other priorities to handle before extending Squish at this time....

Take care......

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hello Matt!

Oct 11 18:35 03, Matt Bedynek wrote to Johan Zwiekhorst:

Perhaps now that someone is working on squishmail, filebox support
can be added?

I was thinking of that, but I'm affraid to damage the style of Squish.. Well understand me well, SquishMail is a small tosser with good features, but if I add to mutch to it, it would not be small anymore..

That's small is good for leaf nodes/points which doesn't require too mutch features.

Regards,
Bo

--- Msged/LNX 6.1.2 (Linux/2.4.22-1-586tsc (i586))
* Origin: The Night Express, Roennede Dk (2:236/100)

Hello Bo.

13 Oct 03 22:06, you wrote to me:

Some features could be added with minimal impact. For example, two features i think would be powerful to squish would be filebox support and perl hooks. It's
already got just about everything it needs.

I was thinking of that, but I'm affraid to damage the style of
Squish.. Well understand me well, SquishMail is a small tosser with
good features, but if I add to mutch to it, it would not be small anymore..

That's small is good for leaf nodes/points which doesn't require too
mutch features.

Matt

e-mail: matt [at] thunderdome.ws | icq: 16568532 | yahoo: mbedynek

---
* Origin: Thunderdome Server Project - http://fido.thunderdome.ws/ (1:106/1)

Some features could be added with minimal impact. For
example, two features i think would be powerful to
squish would be filebox support and perl hooks. It's
already got just about everything it needs.

While I think I understand what you want for file box support, it might not be as simple as you think. The current squish can be setup to append compressed mail bundles, and also to limit mail bundle sizes. Since I've only had limited
experience with file box support (as implemented in BinkD), I don't see how know eactaly how the (to me) arbitrary file box directory naming is supposed to
work..... That could cause a problem for squish.....

As to the perl hooks, I don't know what you would want them to do.

Please take this conversation to the TUB echo for further discussion of Squish.
I don't know of any version of Binkley that supports filebox support (or I haven't used Binkley in that way and have forgotten Bink's support of such), so
I don't think this is an appropriate discussion to continue here. If BinkleyTerm does support it, please point me to the options that take advantage
of fileboxes.

I was thinking of that, but I'm affraid to damage the style of
Squish.. Well understand me well, SquishMail is a small tosser with
good features, but if I add to mutch to it, it would not be small anymore..

Yup.....

That's small is good for leaf nodes/points which doesn't require too
mutch features.

Squish is also good enough for a hub, especially when used with BinkleyTerm for
a mailer.

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hello Matt!

Oct 13 16:41 03, Matt Bedynek wrote to Bo Simonsen:

Some features could be added with minimal impact. For example, two features i think would be powerful to squish would be filebox support
and perl hooks. It's already got just about everything it needs.

Filebox would be okay.. But perl hooks.. You can allready write Dynamic Linked Liberies for it, I fixed it last weekend, so the msgtracking module works..

Regards,
Bo

--- Msged/LNX 6.1.2 (Linux/2.4.22-1-586tsc (i586))
* Origin: The Night Express, Roennede Dk (2:236/100)

Hello, Bob!

Replying to a message of Bob Jones to Matt Bedynek:

appropriate discussion to continue here. If BinkleyTerm does support
it, please point me to the options that take advantage of fileboxes.

I was thinking of that, but I'm affraid to damage the style of

I use BinkleyTerm/2's fileboxes! This is from my Binkley.CFG:

; private outbound directory for some specific nodes
; all files you put in there will get transmitted and deleted
;NodeExtraDir 618:618/2 d:bt\out\george

I don't use it anymore, but it IS there and it DOES work, folks.

There's no need for Squish to be doing this. BT does it already if I understand this thread correctly...

Later,
Sean

// hausmaus@darktech.org | ICQ: 19965647 | AIM: eekahausmaus

--- FleetStreet 1.27.3.8d
* Origin: Midnight's Hour BBS - telnet: midnightshour.darktech.org (1:11/200)

appropriate discussion to continue here. If BinkleyTerm does support
it, please point me to the options that take advantage of fileboxes.

I was thinking of that, but I'm affraid to damage the style of

I use BinkleyTerm/2's fileboxes! This is from my Binkley.CFG:

Ok. Is this version 2.60 or one of the other lines (XE or...)....

; private outbound directory for some specific nodes
; all files you put in there will get transmitted and deleted ;NodeExtraDir 618:618/2 d:bt\out\george

I don't use it anymore, but it IS there and it DOES work, folks.

Good....

There's no need for Squish to be doing this. BT does
it already if I understand this thread correctly...

That's not it. At least one person would like to see Squish support the filebox for where it tosses packets..... As you show, the filebox stuff is arbitrary directories that have to be specified per node..... This could significantly blow up memory used to hold configuration information if used heavily.....

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hello, Bob!

Replying to a message of Bob Jones to Sean Dennis:

Ok. Is this version 2.60 or one of the other lines (XE or...)....

BT/2 XE-2.60 Beta XH7 (mxcomm).

That's not it. At least one person would like to see Squish support
the filebox for where it tosses packets..... As you show, the
filebox stuff is arbitrary directories that have to be specified per node..... This could significantly blow up memory used to hold configuration information if used heavily.....

I was using that setup for 56 nodes when I was RC11 and a mail hub... I never noticed any problems with memory leakage, usage, etc. Then again, my BBS is on
a 850mhz machine w/256MB RAM, so I just may not have noticed anything. :>

Just my two cents-was trying to help. :)

Later,
Sean

// hausmaus@darktech.org | ICQ: 19965647 | AIM: eekahausmaus

--- FleetStreet 1.27.3.8d
* Origin: Midnight's Hour BBS - telnet: midnightshour.darktech.org (1:11/200)

Hi Matt!

In your message to Johan Zwiekhorst, dated <Saturday October 11 2003 18:35>, you wrote:

MB: attachments. I found fileboxes to be much cleaner and these problems
MB: nonexistent. As to your problem, if you are familar with how BSO
MB: works then you can simply reattach them manually. I know of no
MB: utility to detect this.

I do know how BSO works, but solving the problem manually is not feasible for me. My outbound usually contains several hundred files, so trying to find orphaned mail archives among those manually would take me all day (if not longer).

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hi Mike!

In your message to me, dated <Saturday October 11 2003 21:16>, you wrote:

MT: enough...but once I researched my mailer logs I discovered that they
MT: were successfully sent as the identical number of bytes as the orphan
MT: file. It seems to be the truncate that was failing for me and not the
MT: transfer. Wouldn't surprise me if there were some access collions, as
MT: I have multiple nodes and apps pointed to the same outbound dir on a
MT: Netware server.
MT: Might take a look at yours, if you haven't checked that already.

Hadn't thought of that. I will check. Thanks for the tip!

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hi Peter!

In your message to me, dated <Sunday October 12 2003 12:49>, you wrote:

Yes, that works. Unfortunately, SOB doesn't seem to
able to show me ONLY the orphaned files,

PK: I don't have any orphaned files at the moment so I can't be sure,
PK: however from memory, the orphaned files ALWAYS show up at the top of
PK: the list, BEFORE any .FLO files. Normally SOB lists files in this
PK: order -

No, orphaned mail archives are shown below the ?LO file they belong to. You have to check visually if all archives listed are mentioned in the ?LO file. The ones that aren't, are the orphaned files. That's a LOT of work if you have several hundred outbound files!

PK: Options ==> File Filtering

That allows me to have SOB list only the ?LO files and all mail archives, but I
can't get it to show me only the orphans.

PK: Then a PM app is probably not a lot of use for unattented operation.
PK: Do you frequently have a lot of orphaned files? Its rare that I see
PK: them here.

Yes, it happens on a regular basis. I don't know yet why they occur, but I suspect binkd to be the culprit. I use squish 1.11 for OS/2 as my mailprocessor
and binkd 0.9.5a (I intend to upgrade to 0.9.5/stable this weekend) as the mailer.

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Am 14 Oktober 2003 schrieb Sean Dennis an Bob Jones:

;NodeExtraDir 618:618/2 d:bt\out\george

I don't use it anymore, but it IS there and it DOES work, folks.

That's no problem at all with Squish:

Have a look at compress.cfg.

You can introduce whatever you want to happen with an outbound pkt when defining specific "archivers" and adding those settings in squish.cfg pointing to specific FTN addresses.

I use this feature for myself since years to run multiple gateways and do some more things this way. Even FTN <-> FAX or FTN <-> Database (like mySQL or Postgresql, DB2, ...) is possible without much tinkering. I can't see any real limit.

cu, Dieter

---
* Origin: Wndos s god fr cmnicaton (2:2476/14)

Hi Johan,

PK: I don't have any orphaned files at the moment so I can't be sure,
PK: however from memory, the orphaned files ALWAYS show up at the top of
PK: the list, BEFORE any .FLO files. Normally SOB lists files in this
PK: order -

No, orphaned mail archives are shown below the ?LO file
they belong to.

Not here they don't, all files that are NOT listed in a .FLO file show at the top, before any .FLO file entries. EG If there were TWO files to send to a node
SOB would show 5 lines for that node -
The .FLO file name against the node address,
The entry in the .FLO file pointing at the first file to be moved,
The Arcmail entry for the first file,
The entry in the .FLO file pointing at the second file to be moved,
The Arcmail entry for the second file.

Either there is another setting that controls this or we are talking about different things. I am using SOB v1.10, however I also have v1.00 around here. I don't suppose you have a mix of v1.00 .DLL and 1.10 .EXE or something like that?

I use squish 1.11 for OS/2 as my mailprocessor and
binkd 0.9.5a (I intend to upgrade to 0.9.5/stable this
weekend) as the mailer.

Pretty much the same here, except I am using binkd/2 0.9.5. All my background mail processing is handled by one task that serialises access to the outbound areas by the mail handling tasks (Squish, NEF, etc), and forces the programs to
run individually in sequence, so processing clashes cannot ocurr. Are you able to do something like this?

Cheers....................pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hi Peter!

In your message to me, dated <Thursday October 16 2003 22:33>, you wrote:

No, orphaned mail archives are shown below the ?LO file
they belong to.

PK: Not here they don't, all files that are NOT listed in a .FLO file show
PK: at the top, before any .FLO file entries. EG If there were TWO files
PK: to send to a node SOB would show 5 lines for that node - The .FLO file
PK: name against the node address, The entry in the .FLO file pointing at
PK: the first file to be moved, The Arcmail entry for the first file, The
PK: entry in the .FLO file pointing at the second file to be moved, The
PK: Arcmail entry for the second file.

I've sent you an e-mail with a snapshot picture of the SOB window. It clearly shows that SOB lists the .FLO file first, then all entries in it, then the filenames destined for that node (both the ones included in the FLO and the orphaned ones). I can find no way to change that order or to have SOB identify the orphans for me.

PK: Either there is another setting that controls this or we are talking
PK: about different things. I am using SOB v1.10, however I also have
PK: v1.00 around here. I don't suppose you have a mix of v1.00 .DLL and
PK: 1.10 .EXE or something like that?

I don't think so. SOB shows version 1.10 and there is no DLL -- just an EXE, a HLP and an INI.

PK: Pretty much the same here, except I am using binkd/2 0.9.5. All my
PK: background mail processing is handled by one task that serialises
PK: access to the outbound areas by the mail handling tasks (Squish, NEF,
PK: etc), and forces the programs to run individually in sequence, so
PK: processing clashes cannot ocurr. Are you able to do something like
PK: this?

Yes. I have a script running in the background which uses a flag file created by BinkD to know when it has to start processing mail and files. That script checks if there are any *.?SY files in the outbound first, because then it doesn't process any mail until these are gone. When the actual processing begins, it will do nodelist segment processing first, then file distribution processing, then squish for mail processing.

My Binkd/2 0.9.5a (and all versions before that) has a tendency to trap regularly. Here's the last time this happened:

09-11-2003 00:01:00 SYS3175 PID 97c8 TID 0001 Slot 004f F:\OS2\FIDONET\TCPIP\BINKD.EXE
c0000005
00021d90
P1=00000001 P2=35353a32 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=002005a2 ECX=002005a2 EDX=35353a32
ESI=00000000 EDI=00000000
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:00021d90 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:001454b0 SSACC=f0f3 SSLIM=ffffffff
EBP=ffffffff FLG=00012246

BINKD.EXE 0002:00001d90


The Russian binkd authors, however, claim that this could be in no way responsible for flow files getting deleted and so leaving orphaned mailarchives. Nevertheless, *something* seems to be deleting flow files on my system on a regular basis (once or twice every couple of months!).

Kind regards,

._|~/_

e-mail: johan@zwiekhorst.be_NOSPAM (home)
web: http://www.zwiekhorst.be (personal)
http://www.diskidee.be (our e-zine!)
--- Maximus-CBCS v3.01
* Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay' (2:292/100)

Hi Johan,

I've sent you an e-mail with a snapshot picture of the
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.

My Binkd/2 0.9.5a (and all versions before that) has a
tendency to trap regularly. Here's the last time this
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.

The Russian binkd authors, however, claim that this
could be in no way responsible for flow files getting
deleted and so leaving orphaned mailarchives.
Nevertheless, *something* seems to be deleting flow
files on my system on a regular basis (once or twice
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)