On 2019 Mar 26 13:58:30, you wrote to me:

 >> 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...

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

ugh! yeah, that filename looks like how a flo file is named... and the
extension is definitely wrong...

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

i'd report the problem with the archive names and extensions to the the
maintainer but read moer and see becaue it may be something else... if not,
then a report is surely needed...

 >>> 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?

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

i would certainly be testing it... i don't have a current install of mystic
so i can't really help there... i can say that my current system doesn't
seem to have a problem with the few mystic systems connecting here... i'll
have to dig in the logs to find some sessions and what version they are
running and see what filenames they are sending...

i cannot imagine this being a configuration problem unless the sender's
outbound is pointing to the wrong directory and they're sending the files
before mystic has a chance to name them properly when moving them into the
outbound... i've seen that before with other software... is that system
using a filebox for your's instead of the normal outbound??

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
it wrong...
... A violent, unwanted clown on the global stage.
---