		README for mbfido.


	Netmail tracking.

General disclaimer; I hate netmail trackers, but they aren't completely useless
if you know what you are doing. All trackers that simply rely on world 
nodelists won't do the job, they breakdown ftn networks simply because
nodelists are never up to date and mail will get lost and bounced when it
should arrive. That's the reason why I build in a netmail tracker which you
only can manipulate by rewriting the source, or switch it off in the setup
program.

Netmail tracking is done in different levels. The further the message must go
from your node, the checking will be more relaxed. I allways assume that you
know who your neighbours are (nodes in your net). You know more or less know
about nodes in your own region. For the rest of the world, you can never be
sure they exist. This all has to do with nodelists distribution. Most networks
have own netlists, you can have them fast and they should be reliable. Your
region lists will be reasonable accurate, but there's at least 1 week 
behind the real situation. About world nodelists, everybody knows the thruth,
some regions and zones are several months behind reality.

So if are are going to do netmail tracking we must face all these facts. In
the mbsetup program under "edit fidonetworks" you can define 3 nodelists.
The first should be the world nodelist, the second one the region list, and
maybe the third the regions network list. If the last lists aren't defined
netmail tracking will be relaxed, ie. only zones are checked. If you have a
region list, networks in your region must exist. This is quite simple too.
If you have a network list (the third entry in the setup), nodes in your
network are checked. If this list is older than 8 days, this check is skiped.

This aproach works fine if youre a hub or host in a network, you can check 
netmail from outside your network. For sending messages to other networks
and zones, simply assume that the receiving networks do their checks.



	Dupe Checking.

Echomail dupes are checked on the following information: The AREA:tag, the
subject, the origin line, the message date and the MSGID kludge. All these
fields are added and the resulting 32 bits CRC value is stored in a database.


	Opmerkingen:

Toss echomail: optie kopieren sysop echomail naar personal area.

Check PKT destination moet optie zijn.

Notify sysop if badmail/dupemail etc.

Aanbrengen Re: in subject regels, ook nummeren, zie FS?-???? 

Netmail switch - Kill empty messages

Expand filenames van inkomende file attaches. Nuttig voor download van 
netmail + attach

Netmail import: set PVT flag. Kan ik niet kontroleren, mijn eigen uplink zet
die vlag niet!

Echomail scan: strip LF, soft CR, INTL, FMPT TOPT SEEN-BY PATH. Add tearline + 
origin line.

Netmail scan: add INTL, FMPT en TOPT

Switch -Force, kijk niet naar *.JAM files tijdens scan. Is nu default.

Create mail PKT volgens FTS-1, FTS-$, FSC-39 rev. 4, compat mode, 2+ 
PKT header, capability word en capability word validation copy.

Herkennen 2+ (FSC-39), (FSC-48 rev. 2), Type 2.2 (FSC-45).

