| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Type-10 (Draft 3) Int |
->> Perhaps then wildmail! will be so good as to inform us of the RIGHT p
->> since no FTS standards appear to have anything to say on the matter?
->> :)
JM> Here's the reason Ian.
JM> Several editors put the TOPT or FMPT lines BEFORE the INTL line. When
JM> WILDMAIL! processes it, it hasn't even established a 3D address yet via
JM> the use of a INTL line (Gotta have a Zone first). So when it encounters
JM> a TOPT/FMPT line, it has no 3D address to append it to turn it into a 4D
JM> address.
JM> Remember, you have to have a 3D address BEFORE you can have a point off
JM> of it. So all those editors have to do is make sure they place the
JM> TOPT/FMPT lines AFTER the INTL kludge line in the message body and then
JM> WILDMAIL! will handle it just fine.
that's definitely a sign of a shortsighted programmer... they should
utilize a "build as you go" format of coding for this... i know
that i do mainly as there is no guarantee of control line placement in
messages EXCEPT for the AREA: line... anything else is basically a
free-for-all
JM> My new ViaMAIL! can deal with this situation however. Something about
JM> putting the cart before the horse here fits real well.
hehe, i guess... but i see nothing wrong with the following (yes it's
pascal) code other than i'm doing it online, it's not complete, and it's
not fully tested but i'm sure the idea is clear... BTW: no, this doesn't
take into account any domain or 5D type stuff... it is simply something for
the Type 2 PKTs out there...
origaddrcmplt := '';
origaddrzone := '';
origaddrnode := '';
origaddrpnt := '';
destaddrcmplt := '';
destaddrzone := '';
destaddrnode := '';
destaddrpnt := '';
while not eof() do
begin
searchfokludges(pktname,tmpbuffer);
if buffpos('^aTOPT:',tmpbuffer) > 0 then
origaddrpnt := getkludge('^aTOPT',tmpbuffer);
if buffpos('^aFMPT:',tmpbuffer) > 0 then
destaddrpnt := getkludge('^aFMPT',tmpbuffer);
etc... etc... etc...
end;
origaddrcmplt := origaddrzone + ':' + origaddrnode + '/' + origaddrnode;
if origaddrpnt '' then
origaddrcmplt := origaddrcmplt + '.' + origaddrpnt;
destaddrcmplt := destaddrzone + ':' + destaddrnode + '/' + destaddrnode;
if destaddrpnt '' then
destaddrcmplt := destaddrcmplt + '.' + destaddrpnt;
)\/(ark
* Origin: (1:3634/12)SEEN-BY: 13/13 37/100 50/99 102/735 104/821 105/103 107/411 119/88 129/11 SEEN-BY: 138/146 153/800 920 157/586 167/90 200/204 201/505 203/512 992 SEEN-BY: 204/200 205/625 209/720 7211 239/1 245/6910 260/742 261/1137 270/101 SEEN-BY: 270/102 103 104 211 280/1 801 282/1 4073 283/657 292/4 511 876 SEEN-BY: 320/119 321/1 332/1 334/201 341/70 344/3 345/12 346/25 348/105 SEEN-BY: 362/37 367/1 385/100 387/31 396/1 402/311 403/150 405/0 406/100 SEEN-BY: 430/105 600/348 620/243 626/660 632/348 640/206 230 305 820 821 822 SEEN-BY: 640/823 700/101 711/409 410 413 430 808 809 934 712/515 713/888 SEEN-BY: 724/10 800/1 2002/2002 2430/1423 2433/225 2602/100 2604/104 2613/5 SEEN-BY: 2624/306 2630/1001 3401/308 3611/18 3615/7 50 7104/2 @PATH: 3634/12 170/400 396/1 270/101 209/720 640/820 711/409 808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.