From: kevin.blalock@gmail.com   
      
   On Saturday, August 21, 2021 at 10:20:30 AM UTC-5, g00r00 wrote:   
   > KB> + Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)    
   > KB> ! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156    
   > KB>    
   > KB> This I do not understand, as it is clearly configured under the echomail    
   > KB> nodes.    
   >    
   > It seems there is a small error in the message text there which I've just   
   fixed    
   > up.    
   >    
   > That error means that you have a password set in your entry for 46:1/156 but    
   > the PKT file itself did not have the password you configured.    
   >    
   > (Or it means you have no active configuration for 46:1/156 but you've   
   already    
   > mentinoned that you do).    
   >    
   > In the next build it will properly report "PKT password does not match   
   password    
   > set for 46:1/156".    
   >    
   > ... What was the best thing before sliced bread?   
      
      
   Thank you for the reply, g00r00! I woke up to an email from the hub operator   
   that he normally doesn't setup a PKT password unless asked. Funny, it was on   
   the application. Anyhow, rant off.. ;) It is working as expected now, and   
   thank you for all your    
   hard work! Now to go finish reading the whatsnew file.. so many updates! WOO!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)