MSGID: 2:280/464.47 6490178a   
   REPLY: 3:770/100 e34ea0a3   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Paul wrote (2023-06-18):   
      
    PH> I have a node in fsxNet running 21:1/167 and have credentials set up in   
    PH> BinkD for it.   
      
    PH> When it polls BinkD is showing/logging the fidonet AKA for the incoming   
    PH> poll and not the Zone 21 AKA that has been configured at my end.   
      
    PH> I don't have a Fidonet AKA setup in my BinkD for this node, yet my   
    PH> instance of BinkD seems to like/accept it?   
      
   Are you 100% sure that there is not anything about fidonet in you binkd.cfg   
   (or the included config files)? If there is no fidonet AKA, you should get a   
   "(n/a or busy)" for fidonet too. But maybe I'm missing something.   
      
    PH> Any ideas how I can ensure just the Zone 21 is accepted?   
      
   You cannot. It's a flaw of the binkp protocol (inherited from EMSI). The   
   moment you have a password protected session, the incoming connection can dump   
   anything in your ("secure") inbound. That is the reason we have pkt (and tic)   
   passwords.   
      
   You can configure some restrictions with the "skip" and "check-pkthdr"   
   keyword, but I'm not sure, if check-pkthdr secure would prevent it.   
      
   ---   
    * Origin: No REPLY kludge - no reply (2:280/464.47)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/709 123/131 124/5016   
   SEEN-BY: 129/305 153/757 7715 154/10 203/0 218/700 221/0 226/30 227/114   
   SEEN-BY: 229/110 112 113 200 206 275 307 317 426 428 470 550 664 700   
   SEEN-BY: 240/1120 5832 266/512 280/464 5003 5555 282/1038 291/111   
   SEEN-BY: 292/854 8125 301/1 310/31 317/3 320/219 322/757 341/66 234   
   SEEN-BY: 342/200 396/45 423/120 460/58 633/267 280 281 384 410 412   
   SEEN-BY: 633/418 420 509 712/848 770/1   
   PATH: 280/464 633/280 229/426