Does your outbound directory in FastEcho (FE) match the one set in
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 '-<option>' parameters with your netmail packing?
I have problem with FastEcho.
I using a FastEcho with Binkley/Xenia style of outbound and Argus. Problem is when I'm packing a NetMails, arcmail archive is making
but Argus don't see it, I think that FastEcho don't make a *.CLO
file, but echomail is working very good. What Can I do to pack and
send netmail propertly?
My route.fe file[ ...trim.. ]
=== Begin ROUTE.FE ===
=== End ROUTE.FE ===
|Location:||Riverside County, California|
|Nodes:||15 (1 / 14)|