pointlist

Hello, everyone! Point segments from network sysops are accepted for processing with netsoap: From: SysOp, 500:Net/Node.0 To : PntFix, 500:812/1.0 Subj: pointlist The body of the letter contains a point segment (one segment in one letter). It can be like type it in the email editor itself, or paste it from the finished file. Please contact attention - the segment must be sent in plain text form (no archiving/yue), and the segment must be whole, no separate point lines (see example below). The segment itself: Begins with the symbol ';

Hello Eugene! Sun 06-May-2001 07:55, you (500:95/468@ZXNet) wrote a letter to PntFix: P>> The body of the letter contains a point segment (one segment in one letter). His P>> can be typed in the email editor itself, or pasted from a ready-made one P>> file. EP> What to do with long lines (more than 80 characters)? And when inserting a file, line breaks are not inserted. When writing too, if, Of course, don't press inter. Look at the dump of the letter from your grandfather using , at least on this line. It is clearly longer than 80 characters, and the line feed will only here. EP> 500:572/1024 EP> 500:95/1202 Wow. Coincidentally, they are not in the pointlist. ;) With best wishes, Vladimir.

Hello, Vladimir! Mon 07-May-2001 06:24, you (500:322/67@ZXNet) wrote a letter to me: VK>>> Are there any problems with nodelist segments? VK>>> Mazda! The attack won't work? VL>> HZ, you have to try, it may come from you, it may come from someone else VL>> can't get there, so that's why it's done, the netsoap just has to get there. From VL>> 812 is accepted by both netsoap and files. VK> If I put 322ndl.* in the filebox for you, will it reach you? I don’t know, we don’t link with you directly. VK> What if there is also .TIC there? :) Whose address? ;) VK>>> I already forgot where it is on my screw. :) VL>> If attacks continue, we will do it without any problems VK> For transport software, attack is the same bundle. By itself, it is far from VK> will leave, and if with .TIC, in the form of fakha - as much as you like. That's why I'm for fehu. In addition, there is no need to rip it out of it, and it’s just less hemorrhoids. VL>> only names are needed VL>> define so that they are unique for each network and not with anything VL>> intersected. VK> xxxxndl, where xxxx is the network number padded with zeros. And the day number in extension, ok? That is: xxxxndl.129 xxxxpnt.129 In this case, the one who hacks must use the 'Replaces' directive (so as not to junk accumulated). What should the common sheets be called? Like before or something different? With best wishes, Vladimir.

Hello, Sergey! Thu 10-May-2001 09:50, you (500:3432/7@ZXNet) wrote a letter to me: VL>> And the day number in the extension, ok? Ie: VL>> xxxxndl.129 VL>> xxxxpnt.129 VL>> In this case, the one who hacks must use the 'Replaces' directive VL>> (so that junk does not accumulate). SK> Oh great, let's do that. And terminal links can delete these files SK> having set the brains of the fahomemanger. OK. VL>> What should the common sheets be called? Like before or something different? SK> can be left as before, i.e. pnt_zxn.055 and net_zxn.055. OK. SK> Another question about time. Some sheets will be published once a week SK> or with every change? I would do it like with a pointlist: the checker responds to the sender immediately after receiving it segment, and the generator generates sheets once a week. SK> And lastly. We figured out the pointlist format, how it will be now SK> look like nodelist segments, it will be a piece starting with Host or this SK> maybe a full-fledged nodelist? Those. I'm interested in how the checker will process the string SK> with a description of the zone in the segment. Give me the host sheets. There is one zone for everyone, the generator will assign it, and the checker will check hosts and what’s underneath them. With best wishes, Vladimir.