Subj : Binkley To : Marcin Gondek From : Paul Quinn Date : Wed Jul 04 2001 03:13 pm Hi! Marcin, On 03 Jul 01 22:17, Marcin Gondek wrote to All: MG> I have problem with FastEcho. MG> I using a FastEcho with Binkley/Xenia style of outbound and Argus. MG> Problem is when I'm packing a NetMails, arcmail archive is making MG> (ex. *.TU1) MG> but Argus don't see it, I think that FastEcho don't make a *.CLO MG> file, but echomail is working very good. What Can I do to pack and MG> send netmail propertly? Does your outbound directory in FastEcho (FE) match the one set in Argus? If you're bundling mail to other zones, Argus may not be seeing the other zone outbounds created by FE (where the .CLO file is created). I had that problem here a while back, with the names of the outbound directories not being seen by Binkley or BinkD. Only mail for other zones was affected, since FE kept creating domain named directories for Fidonet zones. Are you using the netmail routing that FE creates automatically for each up/down-link, or, are you using a route file (with routing statements like 'ROUTE-TO' & 'DIRECT')? I use "FastEcho.Exe PACK -P -R%TMPDRV%\RouteNet.Fe", with my routing specified in that file. (It was easy for me, as the routing statements were very similar to those used by the FrontDoor mailer Route.Fd file.) Have you tried any '-