Despite it only tossing pkt's in var/inbound. If not it will leave all .pkt and .PKT alone with no hint what so ever why in the log files. In
my case these pkt's are from valid uplinks.
Note in my system var/inbound is set for both protected and not under option 1.4.2 & .3.
Hello Vincent!
25 May 21 16:07, you wrote to all:
Despite it only tossing pkt's in var/inbound. If not it will
leave all .pkt and .PKT alone with no hint what so ever why in
the log files. In my case these pkt's are from valid uplinks.
Note in my system var/inbound is set for both protected and not
under option 1.4.2 & .3.
This is defeating the purpose of having a separate inbound for secure sessions. The new feature is not needed in your setup; as all packets
would end up being tossed anyway. Having both inbounds set to the
same path is NOT RECOMMENDED as it will leave your system vulnerable
to mail bombs.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,043 |
Nodes: | 16 (0 / 16) |
Uptime: | 89:14:25 |
Calls: | 500,953 |
Calls today: | 2 |
Files: | 109,377 |
D/L today: |
1,107 files (155M bytes) |
Messages: | 304,679 |