ml>> mail... i can easily see where "blackhole mailers"
would not be able
 ml>> to perform this action... i can also see where systems that use their
 ml>> mail tosser to route mail would not be able to perform this
 ml>> function... however, systems like frontdoor with its dynamic routing
 ml>> and packing capabilities based on actually storing the transient
 ml>> messages in MSG format should have no problems performing this
 ml>> function...

 RC> Dont know where you come up with this, since I am guilty of
 RC> the above configuration..

which one? the "blackhole mailer" one or the "dynamic
routing and packing" one? i guess you mean the "blackhole"
one?

 RC> I have a *.MSG netmail area, O/T runs against it..

the problem that i see is like this...

a bundle arrives that is unarchived into individual PKTs... the tosser runs
on the PKT files and when it comes across a netmail passing thru to another
system, it stuffs it into a PKT destined for that system or another one up
the "routing chain"... in this case, the message doesn't even hit
the MSG format and thus a netmail tracker and/or other utils can't process
that message...

in otherwords, there are tossers that do not take the intermediate step of
placing a message in MSG format for additional processing capabilities...

 RC> if I removed this keyword from SQUISH.CFG

 RC> Killintransit

 RC> Netmail passing through here would remain in the *.MSG folder,
 RC> even after it was packed out and sent to its next hop.

right and that is not desired for this operation...

now, if (and i'm not saying that it is) squish is one of those that skips
the intermediate step of placing intransit netmail in a MSG area, then if
(yes, another one) it also has a special config verb like
"unpacktomsg" that would cause it to not skip this step AND if
there is a means of having it process inbound only, allow for the execution
of other utils, process outbound only, then it may be possible for this to
work as desired...

does that all make sense? the keys being

1. all netmail must hit MSG format
2. the tosser not go ahead and also do the outbound processing
3. PING (and other utils) can be run against the MSGs
4. the tosser called for outbound processing (including packing since the
intermediate tools have now been run)

better?

it really comes down to the tosser needing to not be efficient and taking
intransit netmail from one PKT directly to another... or that the tosser
support PING internally...

)\/(ark