Hello Mark,

>> I also  forgot to mention until I had posted my last message that the
>> expected mail bundle file extension from this uplink is not the usual
>> .su[0-9,a-z], Etc. But is instead .[a-z][0-9,a-z]. If I open the oddly
>> named mail bundles and extract the PKT's the PKT's then toss  fine.

> ummm... i'm confused by the extension stuff... are you saying that they were
>coming in with only two characters and not in the normal format? please give a
> example of one of them... not a regex...

An example filename is 0000ffe4.s0 although the filename extensions can
range from 0000ffe4.a0 to 0000ffe4.z9. I have tried renaming an individual
file to a more expected filename like 0000ffe4.su0 and then attempted to 
toss it. But HPT still considers it a security violation and renames the 
file to 0000ffe4.sec and moves it to a separate directory.

But.. If I manually unpack the 0000ffe4.a0 file and extract the .PKT files.
The extracted .PKT file(s) will toss fine without errors. 

>> I have since requested the uplink to send only uncompressed PKT files
>> and have gotten a confirmation of my request. In fact several PKT's
>> have arrived and were tossed without error. That isn't going to keep
>> me from wanting to find the actual cause of what was  happening and
>> why.

> what software is that system running?

Mystic. BUT, I am don't feel it right for me to at this point put the
responsibility for the issue on the sender or the receiver of the mail
files. We are both currently checking setups and testing. I also have a 
local installation of Mystic that I can use for testing purposes.

Jeff


--- BBBS/Li6 v4.10 Toy-4