Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.SYSOP   33804
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23526
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12841
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4186
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13572
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16052
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22010
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   898
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4784
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2765
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13057
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4276
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   28319
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2008
DOS_INTERNET   0/196
duplikat   6000
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
Möte FIDONEWS_OLD4, 37224 texter
 lista första sista föregående nästa
Text 1701, 125 rader
Skriven 2012-07-31 22:40:08 av Michiel van der Vlist (2:280/5555)
     Kommentar till en text av mark lewis (1:3634/12.0)
Ärende: Ward's Z1 node number
=============================
Hello mark,

On Monday July 30 2012 17:47, you wrote to me:

 MvdV>>> If it was send and not received it was lost wasn't it?

 ml>> it may still be in route... your nads stuff has added a lot of
 ml>> hops to messages arriving here that used to be only two or three
 ml>> hops away...

The NADS is not used for netmail routing. Only for echomail distribution.

 MvdV>> What makes you think it was routed?

 ml> it is but one possibility... there are only two...

I can't think of a third, but you insist that an application fopr a node number
should not be routed, but the first thing you come up with is that it is held
up in the routing. When the first and prefeable option is to send it direct, a
routing problem would not be on top of my list.

 ml>> BUT an application for a node number is supposed to be delivered
 ml>> DIRECT

 MvdV>> Is it? Please point me to the part of P4 where it says that
 MvdV>> then netmail with the application MUST be sent direct.

 ml> i didn't say "MUST" ;)

Indeed, you said "is supposed". So tell me where it says it "is supposed". I
can't find it anywhere in P4. Though I agree that it is better to send it
direct, as that right away demonstrated the ability to do so, nowhere in policy
does it say anything about not routing it.

 ml> however, one would be very trusting if they sent in an application
 ml> containing session, packet, area manager and file manager passwords
 ml> via routed netmail...

That's another story. a new node may want to set up a secure connection with
his NC, but if he does not want echomail or files from him, there is no need. I
have secure connections with many of the nodes in my net, but not with all.

 ml> i have, personally, never gotten an application sent to me via routed
 ml> netmail... everyone who wants a node number in this network is pointed
 ml> to the 3634.APP file to download and follow the instructions contained
 ml> within... that is our official application form and we have not
 ml> deviated from it since i joined this net...

Aw.. c'mon. In this day and age, there is no need for all that formality. I do
not have an application form, never had. I just tell em what I need to know to
complete the application and they give me the information. One way or another.

 ml> with folk in some cases but those cases are few and far between... the
 ml> application must arrive via netmail and

I am not that strict.

 ml> i must be able to respond to them via netmail before i issue a node
 ml> number...

Oh sure. I will not complete the final step until I am sure that direct netmail
works both ways.

 ml>> and with the proper FROM address if one is going to go strictly
 ml>> by policy as you seem to be trying to do...

 MvdV>> What makes you think that an improper FROM address- i.e. an
 MvdV>> address that causes problems for the coordinator that receives
 MvdV>> it - was used?

 ml> it is a possibility...

Extremely unlikely. The only thing that will cause problems is the use of an
existing node number that is in use by someone else. Anything else points to a
musconfiguration of the NC's system. Ward is not so stupid as to use an
existing node number in use by someone else.

 ml> the instructions for getting a node number are contained in P4 Section
 ml> 2.2 paragraphs 4 and 5... they also indicate that you may be contacted
 ml> for more information PLUS that one should wait for up to two weeks for
 ml> the request to be processed...

Yeah, yeah... When the coordinator is not on holiday, in these days of almost
instantaneous fido communication, there is no reason why it should take two
weeks.  That two week period was never meant to give the coordinator an excuse
to drag his feet. Plus that by now it is over a month since the first contact
over this issue.

 ml>> my understanding, as of 30 minutes ago, is that the NC that ward
 ml>> was pointed to has not received any application from ward yet...

It is my understanding that the NC that Ward was pointed to is 1:140/0.

 ml> my understanding is that R17C pointed him to the proper NC... all
 ml> according to policy...

All according to policy .. sure.

But not according to common sense if the RC and the NC that he is referred to
are the same person. If Bob wanted him to have a number in net 1:140 instead of
a RIN in R17, he could just have swicthed hats on the fly and continued.
Instead of going through a charade to gain another two weeks of delay..

 ml>>  THAT application has not arrived for processing...

Bullshit.

 MvdV>> So it was lost in the mail...

 ml> no, it has simply not arrived... it may still be sitting on the
 ml> sending machine

If it is still on the sending machine, it was not sent.

 ml>  if it only operates on certain days and/or at certain
 ml> times... look at ward's spotty posting in this very echo for some
 ml> evidence of that...

If Ward says that it is sent, then of course that is all taken into account.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
 * Origin: http://www.vlist.org (2:280/5555)