Kathy, I've experimented with this a little and basically, correct me if I'm wrong LISTERS, the SMTP_FORWARD_n option will setup a number of daemons that will be used when mailings come to the list to process the requests. I have an entry in my go.user file like this.... SMTP_FORWARD_="2*mailhost" And when I start up listserv I see an additional 2 lsv processes running. --Scott > -----Original Message----- > From: Kathy Montgomery [mailto:[log in to unmask]] > Sent: Thursday, September 07, 2000 11:40 AM > To: [log in to unmask] > Subject: Re: Slow WA > > > We've been having this problem, too, with "wa" crawling (and > LISTSERV overall) > when one of our 1000+ subscriber lists gets a posting. I > just read in this > thread that the SMTP_FORWARD_n variable is the solution. > Could someone clarify > its use for me, with some simple examples? I'm having > trouble understanding the > manual, and I don't want to just experiment... Up to this > point, our LISTSERV > machine has been handling its own mail, but our main mail > server could perhaps > be used to share the load. (And maybe a silly question, but > can SMTP_FORWARD_n > point to "itself" -- i.e, the LISTSERV machine?) > > - Kathy Montgomery > > Scott Allen wrote: > > > I am also trying to find out about this. I have a LISTSERV > implementation > > and regularly send out 1000+ mailings that cause my wa > interface to hang. Is > > this a problem with my config or a "feature" of this version? >