Crawly Crypt Collection 1

home *** CD-ROM | disk | FTP | other *** search

/ Crawly Crypt Collection 1 / crawlyvol1.bin / bbs / ios082b / docs / updates.doc < prev

Wrap

Text File | 1992-04-20 | 30KB | 881 lines

----------- UPD 0.60.11 ----------- There was somehow an extra 0 byte after an message in an packet. This one is fixed. The bug reported by Joerg Spilker about the wrong fakenumber in the PATH line fixed. Hoping that the bug in the SEEN-BY with that fakenetnumber is fixed. I've changed the compares to the nodenumber in the packetheader and not to the messageheader. If such an bug appears again, I'll be glad to have that packet. Added keyword NoZone. Problem reported by Bernd. ZmailQ on DOS doesn't regonize the zonenumbers in the SEEN-BY and PATH lines. If NoZone is used, the zonenumbers are not added. We redirected area IOS_BETA via Nest, but ZmailQ had problems with the zone adressing. IOS can now read and write the so called 4d packetheaders, used by frontdoor and d'bridge. The reading goes automatically. If found such an header there is no need for an extra parameter or keyword. However, if IOS must write such an packetheader, to an frontdoor node or point, then it is needed to add an sign after the keyword PassWord The right syntax of that line must be PassWord <nodenumber> !<pasword> # By adding an # after that line, this node/point receives the 4d packetheader. An full used password line looks like PassWord 2:280/3.1 !MYPASS * # what's tells that I'm receiving 4d packetheaders, en 4d messages with an INTL, FMPT an TOPT line. It is possible to send from IOS to IOS with full capacity of that, however, this is not the standard. This make this program so flexable as possible. PS Beware of using pack with those 4d packetheaders. Pack read those headers to know where this packet must be routed. ----------- UPD 0.60.12 ----------- Added keyword PATHcheck Checking if this message is bounced back. If message is bounced, message is not echoed anymore. Please be carefull with messages from an other zone. If the same nodenumber is in in and the message is for example from zone 1, it will then also not echoed. If SEEN-BY has an lot of duplicated nodes, these nodes are already stripped when reading. A bug was found in crunch. An area started with an deleted message was not deleted. Now fixed. -------- UPD 0.61 -------- Removed KAOS problem. File channel is now closed. Can't find the problem of crasch echomail to netmail. It works here good with several setups. Hopally I find that somehow. Changed the check of PATHcheck. The zonenumber is not compared anymore. Only net and nodenumbers are compared. I hope the problem of sending an empty message is over. The header must have at least the sizeof the coressponded messageheader, otherwise IOS reports file lenght problem. The mailer[7] field in the trasharea is set to 0. No problem of moving messages to an other area. Scanmail make an attempt to export this message, but if the SEEN's are correct, only point's nodes that don't have that message, receiving that message. Added : Future of whatarc. Thanx to Vincent, who has give me the source. Now IOS has the capability to regonize the following archives : ARC, LZH and ZIP. I don't exactly know the header of ARJ. There must be added in the config : LZHarchive <archive> <extract command> ARCarchive <archive> <extract command> ZIParchive <archive> <extract command> If no archive is mentioned, like above, the archiver after the Achiver <archiver> is taken as default. This can be whatarc, multiarc or whatsoever. When writing areasize, the name's and path's are checked on NULL pointers. It must work now. I have never seen that problem here, but I think it was an attempt to write an NULL pointer. Outmail doesn't add an INTL line in the netmail if the message is in the same zone. I hope the problem with oMMM is fixed. Things to do ------------ Trying to find the bug Joerg reported about the crash address from echomail to netmail. It seems to be that sometimes the REPLY is'nt readed as well. Here at my setup's it works. Trying to add AKA's in the SEEN's if in the same zone. This will be keyword switched. Look if sometimes the fakenet address is not turned to 4d address in netmail. Add labels in the config. Create outmail as soon as possible. -------- UPD 0.62 -------- Added keyword 'addAKA' Adding address statements in the SEEN's if in the same zone. If you have 2 or more addresses in the same zone like : address 2:280/3.0 address 2:280/301.0 the SEEN's are as followed : SEEN-BY 280/3 301 ..... Added labels in config. The configuration is : #<label> #endlabel #endall where #endlabel tells that this is the end of the label, and #endall tells that all labels are ended. Labels after #endlabel are not regonized anymore. With that labels an keyword is added : Commands <commandline> The switches after the commandline are exactly the same as in the normal commandline. This means, that the import and/or scan etc. parameters can be given after the keyword Commands. Configuration is then, whith labels : #SCANONLY commands -s -c -p #ENDLABEL #IMPORT commands -i -p -l -m -r #ENDLABEL #CRUNCH commands -d #ENDLABEL #DOALL commands -s -c -p -i -l -r -m #ENDLABEL #SCANCRUNCH commands -s -c -p -d #ENDALL ...... If #ENDALL is reached, all labels after that are ignored, in other words, if there was no label aktivated. It is recommanded that the labels are found in the first lines of the configfile. It is possible that some keywords are found in an label, like RealName. It is not recommanded to put Address lines in an label. If for example using multipoint, and an address statement is between an label which is not aktivated, there could be problem with import and scan. The addresses after the areanames in the areas.bbs are then not found, and then scanmail takes the default address. A good use of it could be LogLevel. You can then use different loglevels at scan or import. However, if you wish to make use of different addresses between the labels, make sure that if you have entered an message in an area, the correct address is taken. If for example : ; Areas.bbs <path> IOS_BETA 2:280/3 <path> MYAREA 2:283/1 and you ahave as config : #firstpoint address 2:280/3.1 3003 #endlabel #secondpoint address 2:283/1.25 #endall and start IOS -e firstpoint and you have written an message in MYAREA, the IOS takes as address 2:280/3.1 It is possible that if you are using different zoneaddressing, different addresses can in the labels, however you must be sure that there are no new messages entered. If you want to make use of it : To make 100% sure, add Key lines then also in the labels and start IOS with an minimum of 1 -R in the commandline. Activating an label. You can aktivated 1 label at the time. In the commandline you must add -E <labelname> In the above example you can run import like : -E IMPORT The following switches can't be used after keyword Commands : -E & -H Added ARJ packet regonizing. IOS regonize now ARJ mail, but until there is no full ARJ archiver, this is only for use of extract. The keyword stated with this archiver is : ARJarchive <archiver> <extract command> and is exactly the same as LZHarchive etc. Changed the output of msgreports. The many 0 are over. Bug reported by Joerg, Eddie and Peter Habing, about combined netmail messages are over. Now I'am go to create Outmail. Things I shall add for sure --------------------------- Copy 1 area to another area. This will be in the config as : Copyarea IOS_BETA N_IOS_BETA for example. -------- UPD 0.72 -------- In this version of 0.72.6 is some things changed and added. There was een bug found in the limit if the areas. This is removed. Crash an file appended on the netmail is also direct send to receiver. IOS don't report if secure on, that an node is not found in the config. This is for netmail messages. Move-Mail must now also works. The calculation for outgoing file is now correct. I hope that these problems are now solved. There was just 1 thing what I have removed, what I don't remember. Added the frontdoor option to leave netmail packets unchanged, not packet. This can be switched on with nonetmailpack in the config. If set, recommended only for points, the echomailpackets are first packed, and after that the netmail is scanned. This netmails are not packed, but leaved to PKT file's. IOS send then an mailpacket. I hope you have fun with the program. Things to do ------------ Make an option like Crash-To <nodes .... so that the netmail messages are crahed directly to that node without setting the crashflag on in the message. Also point written an message to that nodes, this messages are crashed. Dupe killer in Inmail, switchable. Check netmailmessages on 3d INTL line numbers. If 3d, turn it to 4d. Message scanned are checked on messagelenght. If to long, > 32 Kb, message is not exported. Keywords active : ApplZone <zone> <outboundpath> RedirectNetMail Event <day> <start hour> <end hour> <command> Keywords down and changed : Down : InCmds OutCmds Changed : Archiver <archiver> <extract commands> <add commands> LzhArchive "" "" "" "" "" "" ARCarchive "" "" "" "" "" "" ZIParchive "" "" "" "" "" "" ARJarchive "" "" "" "" "" "" ^^^^^^^^^ NEW Password <node> <pasword> <type> <3d> <headertype> $<areafixpwd> %<archiver> New are <3d> and %<archiver> <3d> is the sign ^, like # is for packedheadertype 2.2. What it do is send an netmailmessage to an point under 3d INTL line. i.e. his fakenet number. The TOPT is also written. %<archiver> is the type of arcmail packet this node wnats to recieve. This 4 types area allowed : LZHmail ARCmail ZIPmail ARJmail thus it looks like this, (an full password line) : Password 2:280/3.1 PWD # * ^ $PWD %ZIPmail The add commands are from LZHarchive < .... >. Please be carefull with the yoshi LZH packer. He reports 'not .LZS continue [Y/N]' It is recommended to use ZIPmail from Vincent. This is the fast packer for mail without any problems. It is no problem to switch from the one archive to the other archive. For example, point 1 wants to switch from LZH to ZIP. You can easaly add after point 1's password line '%ZIPmail', even if he hasn't collect his LZH mail. IOS regonize the type of arcmail that is on hold for point 1. If you have changed LZH to ZIP, and an new package is coming in, IOS regonize his old package as LZH mail, and turn to LZH. No attempt to add ZIPmail to LZHmail, until he have collect his package, then there is ZIPmail. This works also with poll packages. NEW --- RedirectNetmail This redirect your local netmailmessages. For example, I want to enter an message to Steven on 90:1004/0. In the from field there is 2:280/3.1, and the to field contains NeSt nodenumber. OutMail redirect my message in the from field, and change the nodenumber to my known AKA in zone 90. This origin nodenumber will be 90:4000/103, not 2:280/3.1 This will help to keep just 1 setup for different zones. Also for points, if the origin nodenumber is his fakenetnumber, IOS redirect it to an 4d address. ApplZone <zone> <outboundpath> This is like the Domain statements of Binkley. The zone corresponds to that zone with the Domain. In our example, NeSt is taken. In Binkley.Cfg : Domain Nest.Ftn nest nestlist In Mail,Cfg ApplZone 90 e:\binkley\nest\ The folder 'NEST' is the corresponded word in both keyword. In the mail.cfg the whole path is written down. Don't worry about zoneaddressing in the folder. If this folder doesn't exit, IOS create one. Because this is not our default for Binkley and IOS, the folder created is called 'NEST.05A' Your first address statement in the mail.cfg must be the same as the first in binkley.cfg. If no ApplZone for an zone is found, the default 'Inbound' is token. i.e. if you crash an mail to zone 1, the folder created is OUTBOUND.001 Ourzone, 2, is default OUTBOUND. I'am not ready yet to add domain after the ^aMSGID lines, but I will do that. Event <day> <start hour> <end hour> <command> Execute 'command' between 'start hour' and 'end hour' on 'day' Day can have the following formats : Sun, Mon, Tue, Wed, Thu, Fri, Sat, Wkd, Week, All where 'Wkd' stands for weekend and 'Week' for weekdays not Sat and Sun. The strat and end hour has the format : HH:MM which is from 00:00 to 23:59 max. Command can be any command which can be found in the config, exept for #<...> commands, i.e. labels. An example of an event line can be : Event Wkd 10:00 22:00 Loglevel 2 Event Week 12:00 23:49 LogFile e:\binkley\ios.log Event All 00:00 23:59 Prepare-Poll 2:245/8 ; See part OutMail Event Thu 10:00 12:00 address 2:281/24.1 This is an example. Every command can be put after the event line. This can be usefull with OutMail routing etc. If you wish that some mailpackets are routed differently on an partical day and time. Or, you want to poll an node wich mail packets are normally on hold, on an partical time and day. Also between an label you can have an event to have other parameters to run IOS. #label event wkd 03:00 23:59 commands -i -l -p -r -o event wkd 00:00 00:59 commands -i -l -p -r -o -s -c -d event week 06:00 23:59 commands -i -l -p -r -o event week 00:00 05:59 commands -i -l -p -r -s -c #endall OutMail ------- I'm happy to present OuMail, the part of IOS that some people have waited for. This is also with some keywords. I explain he keywords : Wildcharts & question markes are allowed. Route <Destanation Node> <nodes .......... ------------------------------------------- Netmail messages written to 'nodes' are routed to 'Destanation Node' For example, Route 2:245/8 2:24?/* 2:23?/* All messages written to an node between 2:230/0 to 2:249/999 are routed via node 2:245/8 Route 2:280/0 * All messages are routed to 2:280/0 More Route lines are allowed : Route 90:1004/0 90:* Route 2:245/8 2:24?/* 2:23?/* Route 2:280/0 * It is recommeded that at the last route line is your host with an * after his nodenumber, as in the example. If no route found, IOS make an attempt to find your Boss in the config as you have in your config as : Boss 2:280/3.0 If found, this message goes via your boss. If not found. IOS gives an warning that is message can't be routed. Arc-For <nodes ................. -------------------------------- Nodes that receives arcmail. Example : Arc-For .* 2:280/3 2:245/8 All points receives arc-mail, just as 280/3 and 245/8 Prepare-Poll <nodes ............. --------------------------------- Write an poll file for <nodes>. Here may not be use wildcharts and questionmarks. See for format Arc-For Hold-For <nodes ................. --------------------------------- Put mail on hold for <nodes>. See for format Arc-For Move-Mail <destanation node> <nodes .......... ---------------------------------------------- Move mail for <nodes> to <destanation node>. For example : Move-Mail 2:280/3.1 90:4000/103 Message for 90:4000/103 are packet to the archive of 2:280/3.1 The mailpackets are not mixed packages, i.e. 1 PKT file doesn't contain messages for 90:4000/103 and 2:280/3.1, but each PKT has his own zone addressing. Thus the packet exist from different PKT files. If for example an node has an NeSt connection to an other NeSt node and an point writes an message to that node in an fidonet format. Move-Mail 90:1004/0 2:252/25 If an message written to 2:252/25, this message is the redirected to 90:1004/0 This is only for use of netmail. The packetheader contains the zone 90 addresses, and the message an zone 2 addressing. An INTL line is then added to that message. Possible is : Move-Mail 90:1004/0 2:25?/* Move-Mail 2:280/3.1 90:4000/103 50:100/100 20:100/100 File-Max < Kb > <nodes .......... --------------------------------- Sometimes point send eachother file's via netmail, fileattached messages. If 1 point send to another point an very big file, then the other points have to wait for a long period. If File-Max used, the file transfer is limited by < Kb > for <nodes> File-Max 100 .* Points may not send eachother files bigger then 100 Kb. The sender may send his file, but that point never received that file if the file is bigger than 100 Kb. This can be usefull if you have lots of point who are sending lots of big files to eachother. You can make choices out of points who have een HST or not. File-To <nodes ........ ----------------------- Almost the same as File-Max, execpt here you tell which node/point may receive an file. I hope it not to complicated now. -------- UPD 0.78 -------- Removed bugs : Wrong FLO or HLO file when moving messages. This is corrected. Fileattached messages. File are not set on hold anymore for host. Reverse order FMPT and TOPT. Now TOPT is for FMPT. If redirecting the redirected messageheader is written back. Killall is working now. The messages are deleted. Check of PATH: is now modifyed. Messages with PATH:: are also correct inported with no comment of no PATH line found. If found only PATH: with no number, IOS warns you. For more advant. users, packknown works as followed : check one to our points. No, check to sysop No, check to connected nodes. No, find route. This check is done against the nodes in the passwordlines. For points which boss uses FrontDoor or TosScan : Those utlils are not able to route a file via netmail to an other point if the netmail is packed. For them they can use nonetmailpack in the config. Outmail creates only an packet, not arced. I don't know what's gonne happens when more netmail is in the packet. Things to do ============= There is still an problem with an buserror when updating areasize and lastread. This can be an problem in Craft, that we are checking now. Still when using -L when scanning there is also an buserror. This doesn't appears regulary, also checking. Wrong nodenumbers in netmail with multipoint. Reported Joerg. The possibility to crash mail to another node without setting crashflag on. Rename FLO to HLO or HLO to FLO on events. -------- UPD 0.79 -------- Added in redirection for multipoint, take the correct pointnumber and nodenumber. Seek first the routing this message must go and take from there the correct numbers. Added to routing : Crash-To <nodes..... -------------------- The nodes mentioned after Crash-To are always crashed. No need to set the crashflag on. Points written to this node or his points, also there messages are crashed. If for example : Crash-To 2:252/25 is in the config, and an point writes an message to this node whitout crashflag on this message is direct crashed, also if this message is first routed to his boss, and his boss has this keyword on. Also possible is : Crash-To 2:252/* All messages in 252 net are crashed. Hold-to-Poll <nodes ....... ---------------------------- Change hold files to poll files. If node matched after Hold-to-Poll his mail is changed to poll files. Recommended is to set this in an event. Event Wed 00:00 02:00 Hold-to-Poll 2:280/308 Gatewaying ---------- It is possible to write now to 'GateWay'. If using IOS you been able to be an gateway for several zones. Example : From : Rinaldo Visscher on 2:280/3.1 To : GateWay on 2:280/3 ----------------------[ NETMAIL ]---------------------------------- &To: Joe Jet@90:1000/0.0 <message text> ---------------- This message is written to gateway on 2:280/3 who has connection with NeSt. This message is sended to the node in the &To: field. The outgoing message looks like : From : GateWay on 90:5/0 To : Joe Jet on 90:1000/0 -----------------------[ NETMAIL ]---------------------------------- &From: Rinaldo Visscher@2:280/3.1 <message text> ^aVia GateWay on 2:280/3 <time field> by OutMail ^aVia Node on 90:5/0 <time field> by OutMail If an reply is needed, then the same seq. is needed : From : Joe Jet on 90:1000/0 To : GateWay on 90:5/0 ----------------------[ NETMAIL ]----------------------------------- &To: Rinaldo Visscher@2:280/3.1 <message text> The &To: is case sensitive, &to: is wrong just as &To : The gatewaying can only be done via netmail, not echomail. If you are not an gateway of an zone, OutMail leaves the original message unchanged. The message is not sended anymore so that the sysop can reply to that message. Outbound files -------------- IOS can create now different outbound files. The types : Binkley 2.40 and higher The Box 1.30 and higher For TB compatible outbound files, just add in the config : The-Box This will force IOS to create TB compatible files. Those files are named *.HA, *.NA and *.CA For Binkley compatible files no special keyword needed. The files created then are *.FLO, *.HLO and *.CLO The 3e outboundfiles are not for Binkley versions we are using now. However, if Steven can implement this, this can be used. The files are arced packets, just like The-Box files, only the names are different. The mailpackets don't have an FLO or HLO etc. anymore. The format is, 36 based : NNNnnnPP. <net><node><point>. The extensions are : *.HAT hold files. *.CAT crash files. *.OAT poll files. This to keep it compatible with the older types *.OUT etc. where U stands for Unpacked and A for Arced. This method has more advanges then the old format. There are not so many files in the outbound dir. The mailpackets are not sperated, if 1 doesn't poll for an period, there is only 1 mailpacketfile instead of different file like *.Mo0, *.Tu0 etc. You can easy see the size of the packet. The transfer is faster. To switch this on, just add in the config NewBinkley For The-Box users. It is not recommended to use ApplZone in the config. -------- UPD 0.80 -------- Added in Outmail Hold-Max <size> <nodes ...... ----------------------------- Change an hold file bigger than <size> in an poll file. Size is in Kbytes. If the size limit is exeeded, this file on hold is set to an poll file. This can also be done for point, but not recommended if they are not in the nodelist or phonenumber is unknown. Hold-Max 100 2:245/52 This if the mailpacket is bigger than 100 Kb, the file is set to poll This works only with mailpacketformats *.HA an *.HAT Hold-Del <size> <nodes...... ---------------------------- The same as Hold-Max, but than if the mailpacket has exeeded <size>, the mailpacket is deleted. This also only works with *.HA and *.HAT Usable for points that doesn't poll regulary. MinPacketSize <size> -------------------- IOS goes packing an PKT if the size of the packet is bigger than <size> If not, than the packets remains an *.NM file. Size in bytes There was an bug, that's why this fast new version. The PKT's where not deleted with using newbinkley. Now it is deleted. ================ IOSmail 0.82beta ================ - Mail history file is now ever written - Writes 4D Via lines as they are written by most mail packing utils - New product code list which ranges up to code 0xAB - Bug removed which caused IOS not detecting AreaFix requests. - Lockings against the ABC (Atari BBS Connection) removed - IOS.SYS renamed to IOSMAIL.HIS MAIL.CFG renamed to IOSMAIL.CFG - IOS now writtes and displays PKT-headers with correct month values. - Now, origin line isn't broken if longer than 75 characters, only a warning will be given - If REALNAMEs actived while exporting, the klugdes are only written if the name in the message header differs from the name given by the 'SysOp' statement in the config file - PID lines aren't written anymore - Sysop can send files with unlimited sizes - Logfile format changed to the format used by FrontDoor and related utilitys on the PC. This format is much shorter (smaller logfile, faster writing) and very much more easy to survey Everyone who wants to support this format can get a library (C) from me (Daniel Roesen on 2:243/95.2 or NeST 90:6000/110.2) which makes writing this format very easy. The different log IDs are: + Major changes in action - Minor changes in action # Bundle information * Message information % Result messages = Routing information $ Bundle/Packet size messages ~ External programs ! Warnings ? Error messages > Debug informations These messages could be separately switched off by using the statements 'NoLog' (logfile) and/or 'NoDisplay' (screen) in IOSMAIL.CFG (former MAIL.CFG) Example: I don't want to have message and debug infos in the logfiles but no result messages on screen. Then I use NoLog >* NoDisplay % The sequence of the ID chars is not sensitive. Statement 'loglevel' in IOSMAIL.CFG is not longer recognized by IOS - Added log messages for bundle and packet sizes Some irritating log messages changed - ARJ is now recognized. This was a bug caused by INTEL format of the ARJ archive ID ;-) - Removed 'NoSave' statement. All distribution areas are now REAL distribution only areas. They are NEVER written to disk and skipped while compacting and scanning the message base. The path to the area files is now obsolete in DAREAS.BBS. Leave it out! Example: UNIX.GER 2:243/95 - Packet header output changed - Added reply chain support for the upcoming LED versions (1vw6 and higher) - IOS now sets the 'Message(s) to SysOp' indicator for the upcoming LED versions (1rb1 and higher) - The netmailarea, trasharea and privatebox are now always compacted after scanning. - IOS now uses the archive bit of the header file of each area to determine wether an action should take place if using the '-c' option - Bug fixed that caused IOS to crash if you wanna crash a netmail to a point and in the same run to his boss - Bug removed which caused IOS to bomb if you wanted to route unarced mail to a system which was not in your key lines - Bug removed which sometimes causes IOS to bomb if the -l flag wasn't used. IOS tried to write the LED.NEW out, although IOS hasn't read this file. - Event lines should now work correctly. ATTENTION: IOSmail takes all command parameters in events. So '-r' options are additively parsed. This is not a bug, it's a feature! You can avoid such cases by getting sure that you have no overlapping events. NOTE: The new eventline parser can handle events, which are overlapping the midnight hour. Example: Event All 22:00 03:00 Commands -o - Support for TheBox and BinkleyTerm/ST 2.40 temporarily unaviable. This is caused by the new IOSmail features. TheBox is only able to support 3D addressing. IOS need at least 4D for his basic features. :-) - IOSmail now uses an extra folder for storing his temporary files like unpacket mail bundles. This folder must be specified by the 'MailTemp' command in IOSMAIL.CFG. Example: MailTemp G:\MAILTEMP\ NOTE: This folder MUST NOT be used by other programs. - Bug fixed reported by Steven Green that IOS regarding non-default outbound folders if using a main folder with extension. Example: g:\point.2\nest.05a IOS did: g:\point.05a\ - IOSmail didn't detect LZHmail bundles if the second byte in the archive was ASCII 13 (carriage return). - Bugs regarding Fileattaches removed - New matching algorythm implemented. In former IOSmail versions only '*' and '?' were allowed as wildcards. Now, two new features are added. Some examples: 2:243/{91,93,95}.0 matches to 2:243/91.0, 2:243/93.0 and 2:243/95.0 2:243/95.[1-9] matches to point 1 to 9 of 2:243/95 2:243/95.[136] matches to point 1, 3 and 6 of 2:243/95 In the {} pair a list of possible values can be given, separated by comma. These can by varible length, so {24,243,25} is possible. Also, combinations are possible: 2:243/{[10-15],34,95].0 - New very fast cruncher build into IOSmail - Changed handling of incoming mail + SENT flag not set if message stays at our system + if KillSent or KillAll are active and we decide on importing, that a specific message had to be marked as KILL/SENT then if we are using packknown and the -p switch, the message is NOT saved to the local messagebase (only to a netmailpacket in the MAILTMP folder). Otherwise (not using packknown and -p switch), the mail is saved with KILL/SENT flag to the netmail. - Changed scanning of netmail + All mail which is not yet marked as DELETED or SENT is scanned + Messages which must be exported get the SENT flag on or if KILL/SENT is already set the DELETED flag. - Bug removed which caused that PATH check didn't work - New statement: CrashToPoints If not set, crashmail to points is directed to their boss (old style because points aren't online 24 hours). If set, crashmail is directly addressed to them so if you know, that a point is online, you can crash him a mail. - New password option As you know, '#' lets IOS create 4D packet header compatible to FSC-0039. There's a new option '&' which lets IOSmail create 4D header compatible to FSC-0048. These are the headers which are required by FrontDoor and TosScan. As default for 4D headers you should use the '&' option. If your mail link has problems with these headers (example: he uses ACS) switch to '#'.