Subj : Re^2: Binkley
To : Marcin Gondek
From : Paul Quinn
Date : Sat Jul 07 2001 06:52 am
Hi! Marcin,
On 06 Jul 01 08:24, Marcin Gondek wrote to Paul Quinn:
MG> Echomail is working very good, when I'm exporting echomail the
MG> arcmail packet is created and fileattach (*.clo) and all is ok. When
MG> I'm exporting a netmail there only arcmail packet is created, noe
MG> FileAttach.
You should check that:
1. FeSetup->System->'ARCmail Options'->'Archive extensions (Outbound)' have
_not_ been changed from the arcmail standard of naming ("0-9")
2. the 'Status' (ARCmail) for each node is _not_ set to "No attach"
3. you are _not_ using 'FastEcho.Exe Pack -F' in your command-line
4. is it possible that the .CLO files are being processed faster by Argus than
FE can create the arcmail bundle that it points to? Does the option(s) in
FeSetup->System->ARCmail Options->'Mailer semaphores' have effect on Argus?
5. do you have the proper "List" character set for your DOS archiver programs
in FeSetup->System->'Compression Programs'?
6. do you have some systems set as AKA addresses that share a single 'ARCmail
address' in FeSetup->System->'Node Manager', and therefore, they share a single
.CLO file?
7. if the netmails in the primary netmail area have attributes such as Crash,
Direct, Immediate, File/Attach, or File/Request, then they will be bundled into
arcmail bundles of their own, named like: .CUT, .DLO, or .ILO (not sure of that
one). But, they will be different from the usual echomail bundle naming
convention.
If those ideas don't turn up an answer, and the problem isn't caused by
routing, then, I'm stuck for anything further to add. There's only one other
feller I know that uses a FE/Argus combination, but he's flat-out busy at the
moment as I know that if he had time to answer then he would have by now.
Good luck! and keep us posted on developments.
Cheers,
Paul.
--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: He's got a magnet! Everybody stand back! (ZMH only) (3:640/384)
