TZUTC: -0500   
   MSGID: 72980.sync@723:320/1 2c4bb70f   
   REPLY: 53877.sync@1:103/705 2c4a8048   
   PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0   
   TID: SBBSecho 3.24-Linux master/ad9ab307f Mar 18 2025 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: CP437 2   
   >  > > That did not work either but thanks anyway   
      
   >  > I am sorry if you already did so and I missed it, but could you post the   
   >  > output from one of these failed connects?   
      
   > See message 1094   
      
   > The connect eventually works, but not until after it throws  the invalid   
   > password error   
      
   IIRC, I get invalid password errors from some connections when there is no   
   mail to send or receive.  I also see inbound connections where that   
   happens.  I have a node that, for whatever reason, calls twice -- one right   
   after the other.  The first one works like normal but, because the node   
   just picked up their mail, the second one shows an invalid password error.   
      
   Not sure what causes that but as long as the mail is moving I usually   
   ignore it.   
      
      
    * SLMR 2.1a * "Mmmmmmmm.....doughnuts."   
   ---   
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426