                                  
                                 
                                 

                        Testing a new Mailer Setup



This Help file tries to offer some simple tips to help cut down the 
need to send test messages. We see these on almost every Net. Its always
the same message, "Hey just a test, If anybody see's this let me know", 
The same message in every base from the same board spread all across the 
country. At first, it may seem like the best way to do things, but after
you've been involved in a fast growing net for a couple of months you begin 
to realize how aggravating it is to wade through all the tests just to 
get to the next "Real" message in the thread. 

With careful thought and a little patience you should be able to find and 
troubleshoot most problems without having to send any test messages at all.
This is especially true if you are already active on one net and are just
adding a new one to your system.

I hope you find some of these tips helpful.

                    

                    
                    A few simple rules for new nodes..



BE PATIENT!, One of the hardest aspects of setting up a mailer is the
tedious chore of setting up redundant path and files names. First you 
have to define these in your BBB'S, then in your tosser and FINALLY in your 
AREAS.BBS file. This means for 100 echo's you may have to type in a similar
pathname 300 TIMES!  This is where you will *CREATE* most of your problems.
You need to remember that your working with at least 3 individual programs
in a basic setup, and they all need to be told where to find your message
bases.

                          
                          First things First



POLL FIRST!, A node should not try to send a message test or otherwise
until he/she has verified their mailer/tosser is properly importing messages 
into the bbs. If a node receives mail, and they are tossed into the proper 
areas, its working. If you end up with alot of BAD MSG's or security viola-
tions, FIX THESE FIRST!. 

Pay attention to your bad_msg/Bad echo directory, Set this up in your mailer 
as a folder. this allows you to read messages that are for Unknown areas, 
Security violations, ETC... When you read messages here you will be able to
compare the name of the area They were destined for with the name of the
areas you have entered into your BBS, Tosser, and Areas file.



                            TEST LAST!



There is no reason to leave test messages in every echo when you 
use the same export address for all the echo's in a net, at this point we 
should know our path and area names are correct by following the rules above.

In my case I use FD And GEcho, When I enter an echo in my tosser I use the
global command to set all export list, seenby and origin address's this way 
I know all the echos are set the same, if one works they all will work.
If the export address's are set the same for all Echo's you will only have to 
send one message to verify it has been sent to the proper address (your HUB).

Now, send one message in an administrative or sysop echo (so the public wont
have to be bothered with it) Pop the top on your favorite beer and wait for 
the reply.

If you need more help with the technical aspects of setting up Frontdoor as 
your Mailer, I would suggest finding a copy of the latest FDHELP file written 
by Marc Persad of Persad Software. Persad Software HQ New York 718) 264-2817
This file can also be found on most Renegade support boards, or Call Peglegg 
Amusements (listed below) for the most recent version. 
          
          (Also available for FREQ under the MAGIC Name of FDHELP)

                           Rex Geissinger/SysOp
                           Peglegg Amusements
                           Santa Ana Ca. (714) 557-0680
                           RGSNet Orange County Hub 50:100/500
