> 
 >  MK> All the log file shows is:
 > 
 >  MK> ----------  Mon 04 Jun 07, FastEcho 1.46; TOSS
 >    7:21:47  Processing 11 inbound packets, 14574504 bytes
 >  MK> +  7:21:47  AF.PKT from 1:138/389 to 1:382/33 (00FE, Type 2+) 
 > 
 > that doesn't look like a proper fidonet PKT name... remove that one from 
 > the directory and see what happens...

Well, it seems to process one at at time, since I couldn't find that file 
after processing.  It then stuck on the nxt one.  And you're right, 1:138/389 
is me, so I don't know what it's doing in there.  Here's my fastecho path 
config:

         NetMail: C:\ELE\IREX\NETMAIL
     Messagebase: C:\ELE\MSGBASE
         Inbound: C:\ELE\IREX\INBOUND
 Unprot. Inbound:
   Temp. Inbound:
   Local Inbound:
        Outbound: C:\ELE\IREX\QUEUE
  Temp. Outbound:
      Semaphores: C:\ELE\SEM
      BBS Config: C:\ELE
    Static queue: C:\ELE\IREX\QUEUE
        Swapping: C:\ELE\FASTECHO
           Rules:

IREX doesn't really have an outbound directory, but instead uses a queue 
directory, which according to the help is where outbound files go.

 > 
 > i do note that it appears to be from you to another system... are you sure 
 > you've got the inbound and outbound directories correct? they definitely 
 > need to be seperate...

 > )\/(ark
 > member, FastEcho Beta Team

 
--- SBBSecho 2.12-Win32