PE> The file names can be of any format, 72 characters of 
 PE> anything.

 BL> Not if you expect it to do a FREQ it can't.

Actually you can't define them any better than filename. There are so many
different file systems out there (any of which may run with a FidoTech
mailer) that it is up to the system you poll. Some systems are strictly 8.3
(even for magic names) some allow path selectors, and magic names can be
practically anything. Look at Teddy's file list, she runs an Amiga, so many
of the files have long file names (which die when my copy of Bink attempts
to map them to 8.3 locally, because I don't have a HPFS partition to dump
them on...)

 PE> Using which mailer standard?

 BL> You described the ^a control lines in detail. Why is this 
 BL> any different?

 PE> The ^a lines are designed for a mailprocessor to process, 
 PE> which is what this documents. Not the mailer.

 BL> You are going around in circles and I can't be bothered 
 BL> going around again.

There are several layers (anyone for a full layer based description of
FidoTech transport?) each of which regards different things as it's
business and pass the remainder on the the next higher/lower level...

 BL> IMO, If it's in the packet, then it must be defined in the 
 BL> packet standard... wherever or whatever it is going to be 
 BL> used.

It is defined... As text. From the viewpoint of packet processors, the
Subj: line for a Freq is something you are sending to the system at the
other end, and is thus system dependant. Like the difference between '/'
and '\' to divide paths (I'm not even going to think about '%' and other
weird path chars)... Or the drive letters under CP/M having an optional
number as well (A13:FILENAME.EXT)...

About the best you can say is that it is system and implementation dependant.

...Alex.
(Pagan & Proud)

---