*** Quoting Sean Dennis from a message to All ***

 SD> let me know.  I'm going to attempt it myself (and try it out), but I
 SD> want to be sure of something: if I do a QWK import from the command
 SD> line, it goes under the sysop's name when importing (I think I got

I never did QWK networking in all the years I ran telegard in the 90's. I 
have a bit in synchronet.

 SD> that right).  Should I set the Network ACS in each of the
 SD> QWK-networked echoes to s255 so only the sysop account can toss mail

Giving someone or something network access, allows it to be tossed without 
checking for to and from names. For example. If you ran a network and you 
were my hub. I may have 5 or six users that post to echoes. Like echomail, I 
could set it up so a batch file sends the qwk messages that were posted on my 
system and my qwk messages would be uploaded without checking names as my 
account, which would not be my personal account, would be a hub account can 
be uploaded, where as if It were a regular account uploading a qwk packet 
then it would check to make usre it was from me.

It all depends on what you want to do, if you just want to not be a hub, then 
yes, you are correct you could upload the qwk packet under your name, so you 
would give yourself network access, this would allow you to upload a packet 
from your hub to your telegard system. And, if posts are made from your 
system. Your hub has to give you network access so your messages from your 
system are not rejected. Synchronet hubs can give out a flag, which only lets 
a user upload/download his packets from the qwk door. Pretty nice. It also 
allows scripting to call out to the hub. I am not sure how you are going to 
set up your transfer of packets.

Mike

--- Telegard v3.09.g2-sp4/mL