= Сообщение: 279 из 12494 ======================================= ENET.SYSOP = От : Ulrich Schroeter 2:240/1120 03 Dec 13 03:06:51 Кому : Henri Derksen 03 Dec 13 03:06:51 Тема : NetMail to Point 1. FGHI : area://ENET.SYSOP?msgid=2:240/1120@fidonet+529d533e На : area://ENET.SYSOP?msgid=2:280/1208@FidoNet+a60f5060 = Кодировка сообщения определена как: LATIN-1 ================================ ============================================================================== Hi Henri,
Thursday November 28 2013 17:54, you wrote to me:
HD> Hello Ulrich, WD>> As a reminder ... from now till Nov.30 netmail must be sent to WD>> 2:292/854.1 WD>> ...
HD>> D:\FD\REDIR.EXE HD>> D:\FD\REDIR1.EXE HD>> REM Eerst de NetMail voor de SysOp Point 0 redirecten naar Point 1 HD>> REM ... HD>> CD D:\FD\ITRACK HD>> D:\FD\ITRACK\ITRACK US>> ... HD>> REM End of UniCorn.bat US>> hmm, interesting .... US>> why you're not using one program for all instead of using 3 US>> programs ?-)
HD> It is historically growth this way.
mostly on all our systems =;)
US>> itrack can handle all this stuff =;-)
HD> Could be, but IT has disadvantages too, HD> one of it is, that it is not Y2K ready ;-(.
oups ?-) did I've missed something ?-) my itrack works since the mid 90's =;)
HD> And there were other negative points too, allthough I can not name it HD> now. One of the biggest problems were the netmails to and for AllFix HD> and AreaMgr.
select statements works with multiple selections ... eg. selectTo myAKA .... here you can add &!Areamgr
a definition with a list of areamgr names, so areamgr, allfix or whatever other administrative names works on you system that requires exclusion in the scans
Also on inbound scanning you can select all mails to your aka except the mails to "Areamgr" names definition to move the mails into another folder so the areamgr and allfix later can process the area requests
all you have to do is to define a new datablock, that lists all the names of all your managers and add the Areamgr block as exclusion in the select statements
to select all outgoing mails, you probably have a construct like selectTo !OwnAka so all mails not addressed to one of your own akas will be selected for the final routing and packaging
US>> including mails copying and forwarding to a cosysop or sysop US>> point.
US>> ah, it requires some itrack programming that you have no US>> experience for ?-)
HD> Not only that. The older programs do its work after many time of HD> puzzling. The problems were the AllFix netmail messages to my uplinks, HD> wich must not be copied to my BBS netmail area, arg ;-(
then insert an exclusion into the select statements =;)
HD> The same happend to received netmail for my EchoMailAreaManager HD> IMail. HD> That's why I use first Redir.exe and after that Redir1.exe. HD> It is the same program, but with an other configfile. HD> So there are at least 5 kinds of netmail to be handled. HD> 1. NetMail from me to AllFix for my UpLinks.
move to outbound, should be the netmails be copied before sending ?
HD> 2. NetMail to Imail AreaLink for my UniCorn BBS Node. HD> 3. Netmail to AllFix for my UniCorn BBS Node.
insert the exclusion statement for areamgr mails after itrack let them process by the managers itrack + tosser + ticker
HD> 4. NetMail to me at Point 0 as the SysOp of UniCorn BBS
define 2 blocks, one for all your akas, the 2nd block for all your names and variations should the mail be moved to another folder ? selectTo myOwnAKAs &myOwnNames move netmails
HD> 5. NetMail to users at Point 0 as a user of UniCorn BBS.
if a user registers on your bbs, add some scripting, to add the new users name into one special include file, that lists all your bbs users by name with a block name like BBSusers, you can use this block to exclude these users from handling in select statements similar to the areamgr definitions. after itrack + tosser + ticker handling, you can add a bbs-import for the users netmails
HD> First pack the AllFix.msg for my UpLinks to a pkt with Imail IMPACK, HD> so that it is not handled by my own AllFix, arg.
allfix can handle all allfix netmails by his own, if its from the own system or for an uplink ... so you have not to do some special handling here allfix walks thru the netmail folder, sees some mails to Allfix, but still notices, that its "not for us" as the destinition aka is != ourOwnAKA so leaves the messages untouched If a message to your system is still handled by allfix, the Rcv flag signals allfix, that this message still has been handled
HD> Second start Imail IMALNK to handle messages to it. HD> Third start AllFix to handle messages for it. HD> Forth reroute NetMail for the SysOp to point 1 HD> Fifth move netmail for UniCorn BBS users to the BBS NetMail area with HD> MBUtil.exe
HD> Between each run, it seemed necesarry to correct for wrong y2k dates HD> of the used mailprograms with FXPKTDAT.BAT.
at least itrack and allfix handles datetimes correct. don't know if there is an imail bug with dates ... so I see only 2 possible steps where a fixpktdate is required, before starting with the first program and probably after imail (if imail has a problem with datetimes)
HD> Step 6 is running ITrack for received NetMail messages to other HD> systems than Point 0 (=Zero), i.e. Points or nodes checkecd agains the HD> NodeLists and PointLists for FidoNet and AcoNet.
HD> As many systems do not run a BBS anymore, HD> this is less of a problem to their Node SysOps. HD> Years ago I found it a sport to handle its NetMail all the right way, HD> wich succeeded after many tries and corrections. HD> So I donot like or want to start that puzzle again.
HD> As I am mutiple handicapped, HD> I do not have the energy to make large changes any more. HD> For the same reason, I write fewer than I really wanted to. HD> It is a pitty, but I have to accept that.
I can imagine how you're feels ....
so all my notes are only pointers where I see optimizations that all can be handled by one program, where you use 3 or more ...
so if you have some sparetime and you see it sporty you can ask me some more questions, how to realize the new block definitions, and modified select statements
its upto you, to later implement it, or leave it as is ... its _your_ system and you have to handle it .... I'm sitting far away =;)
HD> Sorry for people waiting (long) for an answer from me. HD> But I still read every message in the areas I am connected to. HD> And somethimes I will write one or respond to. HD> Thanks for your comment.
HD> Greetings from Henri. HD> $ Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 HD> (2:280/1208)
