Sveiki All!

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 (ex. *.TU1) 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?
TIA

____________________________________________________________
[ Marcin Gondek / Drixter ][ REC 48 ][ drixter@metech.com.pl ]
[ 2:48/911@FidoNet ][ Utopia Mail System ][ ICQ UIN 99230394 ]

\\UTOPIA has been up for: 1 day(s), 4 hour(s), 41 minute(s), 18 second(s)
---
* Origin: Utopia Mail System +48-22-6692785 22:00-06:00 CET (2:480/128)

Sveiki Paul!

Wednesday July 04 2001 22:13, you wrote to me:

Does your outbound directory in FastEcho (FE) match the one set in
Argus?

Yes, echomail is working good.

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.

All is for zone 2

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')?

My route.fe file

=== Begin ROUTE.FE ===
Route-to 2:480/112 2:480/112.* 2:481/* 2:482/* 2:484/* 2:48/*
Route-to 2:480/112 2:480/46.* 2:480/58.* 2:480/82.* 2:480/106.*
Route-to 2:480/112 2:480/109.* 2:480/110.* 2:480/115.* 2:480/120.*
Route-to 2:480/112 2:480/125.* 2:480/133.*
Route-to 2:480/112 1:* 4:* 5:* 6:* 2:*
Route-to 2:467/70 2:460/* 2:4600/*
Route-to 2:467/70 2:461/* 2:4613/* 2:4614/* 2:4615/* 2:4616/*
Route-to 2:467/70 2:462/* 2:4621/* 2:4623/* 2:4624/* 2:4625/* 2:4626/* 2:4627/*
Route-to 2:467/70 2:463/* 2:4631/* 2:4632/* 2:4633/* 2:4634/* 2:4635/*
Route-to 2:467/70 2:464/* 2:4641/* 2:4642/* 2:4643/* 2:4646/* 2:4647/* 2:4648/*
Route-to 2:467/70 2:465/* 2:4651/* 2:4652/* 2:4653/* 2:4654/* 2:4655/* 2:4656/* Route-to 2:467/70 2:4657/* 2:4658/*
Route-to 2:467/70 2:466/* 2:467/* 2:468/* 2:469/*
Route-to 2:480/33 2:480/33.* 2:480/17.* 2:480/37.* 2:480/51.* 2:480/57.* Route-to 2:480/33 2:480/65.* 2:480/66.* 2:480/70.* 2:480/100.*
Route-to 2:480/127 2:480/127.* 2:480/32.* 2:480/124.* 2:480/130.* 2:480/135.* Route-to 2:480/128.9 2:480/128.9
Route-to 2:480/128.123 2:480/128.123
Route-to 2:2432/200 2:2432/200.*
Route-to 2:2432/200 3:*
Route-to 2:5020/1951 2:5020/1951.* 2:5020/*
Direct MYPOINTS
=== End ROUTE.FE ===

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?

yep, not working.

____________________________________________________________
[ Marcin Gondek / Drixter ][ REC 48 ][ drixter@metech.com.pl ]
[ 2:48/911@FidoNet ][ Utopia Mail System ][ ICQ UIN 99230394 ]

\\UTOPIA has been up for: 0 day(s), 2 hour(s), 21 minute(s), 29 second(s)
---
* Origin: Utopia Mail System +48-22-6692785 22:00-06:00 CET (2:480/128)

Hi! Marcin,

On 03 Jul 01 22:17, Marcin Gondek wrote to All:

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
(ex. *.TU1)
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?

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 '-<option>' parameters with your netmail packing?

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: "How do I set my phaser to tickle?" (ZMH only) (3:640/384)

Hi! Marcin,

On 04 Jul 01 22:48, Marcin Gondek wrote to Paul Quinn:

My route.fe file
=== Begin ROUTE.FE ===

[ ...trim.. ]

=== End ROUTE.FE ===

I'm not a routing expert, but I had a long look at yours and saw some redundancy. Keep in mind that the routing file is read by FE, top-down, so that the last statement to mention a node or wildcard will affect its routing.

Here's what I recommend:
=== Begin ROUTE.FE ===
; Other zones routing:
Route-to 2:480/112 1:* 4:* 5:* 6:* 2:*
Route-to 2:2432/200 3:*
; MyZone routing (these are exceptions to the first line):
Route-to 2:467/70 2:460/* 2:4600/*
Route-to 2:467/70 2:461/* 2:4613/* 2:4614/* 2:4615/* 2:4616/*
Route-to 2:467/70 2:462/* 2:4621/* 2:4623/* 2:4624/* 2:4625/* 2:4626/* 2:4627/*

Route-to 2:467/70 2:463/* 2:4631/* 2:4632/* 2:4633/* 2:4634/* 2:4635/*
Route-to 2:467/70 2:464/* 2:4641/* 2:4642/* 2:4643/* 2:4646/* 2:4647/* 2:4648/*

Route-to 2:467/70 2:465/* 2:4651/* 2:4652/* 2:4653/* 2:4654/* 2:4655/* 2:4656/* Route-to 2:467/70 2:4657/* 2:4658/*
Route-to 2:467/70 2:466/* 2:467/* 2:468/* 2:469/*
; MyNet routing:
Route-to 2:480/33 2:480/*
; MyNet exceptions:
Route-to 2:480/112 2:480/112.* 2:481/* 2:482/* 2:484/* 2:48/*
Route-to 2:480/112 2:480/46.* 2:480/58.* 2:480/82.* 2:480/106.*
Route-to 2:480/112 2:480/109.* 2:480/110.* 2:480/115.* 2:480/120.*
Route-to 2:480/112 2:480/125.* 2:480/133.*
Route-to 2:480/127 2:480/127.* 2:480/32.* 2:480/124.* 2:480/130.* 2:480/135.*
; Net 5020:
Route-to 2:5020/1951 2:5020/*
; The parasites<giggle>:
Direct MYPOINTS
=== End ROUTE.FE ===

Have a good look and see what you think. I would welcome comments from others as well. As I say, I'm no expert, and, I haven't had a lot of experience with large routing systems.

As an afterthought: if your echomail is flowing well through Argus, then you may be looking for something that isn't supposed to happen. When FE packs either local or in-transit netmail, it will use an existing mail packet if one exists already for an up/down-link. Have you got an arcmail packet viewer like
InspectA, so that you can view the contents of your outbound arcmail? Perhaps your packed netmails have been packed-up in them, and you're looking for newly-created arcmail bundles that aren't supposed to be there. :-)

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: Damn it! I wanna be _their_ aliens. (ZMH only) (3:640/384)