Hello everybody!

I realize this is kind of how it's supposed to work. My binkd.cfg has one line defining my uplink:
*****
node 2:301/1 * Pa$sw0rd!
*****
(nope, not really my password...)

I have also the following entry:
*****
# Default node flags. Binkd will call an unlisted node if "defnode" defined. defnode *
*****

But this, according to what is in the config file, only concerns outgoing mails anyway. Noob question, probably - how do others deal with mail arricing in the "inbound-nonsecure" folder? Just copy them manually into the normal inbound to be processed? Have there been malicious attacks with manipulated .pkt files that would warrant such a distinction between normal and non-secure inbound mail?

Regards
Fermin


... !:*#/g_lqer{ 8ry]@jvBnGkj (Tagline courtesy of two-year-old)
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: 2:301/123 (2:301/123)

Hello Fermin,

On Monday May 10 2021 12:10, you wrote to All:

But this, according to what is in the config file, only concerns
outgoing mails anyway. Noob question, probably - how do others deal
with mail arricing in the "inbound-nonsecure" folder? Just copy them manually into the normal inbound to be processed?

in binkd.cfg:

exec d:\\fido\\batch\\mailrcvd.bat *

in mailrcvd.bat:

if exist \fido\unsecure\*.pkt move \fido\unsecure\*.pkt \fido\secure\

So I automatically process *.pkt from the unsecure. Compressed mail is another story...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Fermin wrote (2021-05-10):

Noob question, probably - how do others deal with mail
arricing in the "inbound-nonsecure" folder? Just copy them manually into the normal inbound to be processed? Have there been malicious attacks
with manipulated .pkt files that would warrant such a distinction between 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)

Hello Michiel!

10 May 21 12:57, you wrote to me:

But this, according to what is in the config file, only concerns
outgoing mails anyway. Noob question, probably - how do others
deal with mail arricing in the "inbound-nonsecure" folder? Just
copy them manually into the normal inbound to be processed?

in binkd.cfg:
exec d:\\fido\\batch\\mailrcvd.bat *

I actually use "*.pkt" as a file mask, but so far, same difference:
*****
exec !@@c:\\bbs\\_batch\\FMail_In.cmd *.pkt
*****

in mailrcvd.bat:
if exist \fido\unsecure\*.pkt move \fido\unsecure\*.pkt \fido\secure\

I've adapted this and probably somewhat "overengineered" it. "Sharing is caring", so here you go:
********
@echo off
for %%I in ("%~dp0\..") do set "base=%%~fI"

set unk_mail="%base%\transfer\in.unknown\*.pkt"
IF EXIST "%unk_mail%" GOTO MoveUnknown
GOTO ProcessMail

:MoveUnknown
set in="%base%\transfer\in"
move %unk_mail% "%in%"
GOTO ProcessMail

:ProcessMail
%base%\FMail\fmailw32.exe toss /B
%base%\FMail\fmailw32.exe import
%base%\FMail\ftoolsw32.exe AddNew /A
%base%\FMail\fmailw32.exe toss /B
*********

So I automatically process *.pkt from the unsecure. Compressed mail is another story...

One problem/situation/mailtype at a time... ;-)

Regards
Fermin


... Feel free to *S*W*I*P*E* the Taglines if you like `em. ;-)
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: 2:301/123 (2:301/123)