Subj : Incoming Netmail from non defined nodes landing in "inbound-nonsecure"
To   : Fermin Sanchez
From : Oli
Date : Mon May 10 2021 12:37 pm

Fermin wrote (2021-05-10):
 FS> Noob question, probably - how do others deal with mail
 FS> arricing in the "inbound-nonsecure" folder? Just copy them manually into
 FS> the normal inbound to be processed? Have there been malicious attacks
 FS> with manipulated .pkt files that would warrant such a distinction between
 FS> normal and non-secure inbound mail?

Have a look in the example binkd.cfg:

#
# Run an external program.
# The "*S" macro in command line substed with S.R.I.F., see !SRIF.TXT
# The "!" before program pathname means immediate program execution
#   after receiving the file.
# *** win32 only:
# The "@" before program pathname means execute program in separate console
# The "@@" before program pathname means execute program in hidden console
# ***
# Macros: *F - complete name of received file,
#         *A0..*A9 - first 10 AKA of remote system,
#         *A*, *A@ - list of all remote AKA separated by spaces
#         *P - password protected [0|1],
#         *L - listed system [0|1]
#         *H - remote hostname or IP,
#         *N - short file name (win32 only).
#

something like:

exec "mv *F /ftn/inbound/secure" /ftn/inbound/non-secure/*.[pP][kK][tT]

(on unix)

---
 * Origin: . (2:280/464.47)

.