Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.SYSOP   33806
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23541
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12847
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4193
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13586
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16053
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/22012
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   900
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/4785
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   2802
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/13066
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/4277
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   28533
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/2020
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 5949, 105 rader
Skriven 2013-01-23 19:02:06 av Nicholas Boel (17148.fidonews)
   Kommentar till text 5936 av mark lewis (1:3634/12.42)
Ärende: Z4
==========
  Re: Z4
  By: mark lewis to Nicholas Boel on Wed Jan 23 2013 11:24 am

 ML> i take most anyone's side when i see them being treated and spoken to
 ML> unfairly or unjustly... "most anyone" because some do deserve what they
 ML> have sown in the past... but that's going down a trail we don't really
 ML> want to travel, right?

And I only take things to another level when I'm talked to like that first.
Apparantly you don't see that part, though.

 ML> these are public areas just like newsgroups... if you don't want any input
 ML> from others in the same room, then take the conversation private...
 ML> otherwise, don't complain about input from others in public places... but
 ML> you already know this...

I don't complain about it. I reply in the same tone that was used with me. Even
a little better if the original topic was diverted by the person jumping into
the conversation.

 ML> hopefully things will cool off more, now...

Doubtful. Some people just like to stick their nose where it doesn't belong.
They've probably done it for far too long to change now.

 NB>> Here -- if the applicant is willing to apply, and pay attnetion, it
 NB>> takes 1/4th the time it does to go through someone that follows the
 NB>> way it was done 20 years ago. Maybe people should rethink this,
 NB>> but.. who the fuck am I to get involved with what people have been
 NB>> fuckin' up for 10+ years. 

 ML> what??

My point there is that the newly aquired "point" I setup went about 3-4 weeks
waiting for a reply from the RC -- who swore he sent a netmail back to him at
that "temporary" address. When the applicant polled the RC for this netmail
that was supposed to be there, nothing was received. This happened 3-4 times,
while I emailed the RC and let him know that his "temporary" node number wasn't
working properly, he refused to do so much as look into the issue, let alone
fix what was wrong to help this applicant further along his process.

 NB>> HAHA. Perfect. I figured you would say that. Even after a rescan of
 NB>> your logs, you might even say that again.

 ML> logs?? i simply read the messages...

Very possible that you read them in the wrong order. I get this echo from the
origin, since the "shenannegans" occurred awhile back.

 ML> what "so many things"?? send in the application via netmail... what else
 ML> is required?? netmail HAS to work... it is the backbone of fidonet...
 ML> everything travels via netmail of some sort... yes, even the file
 ML> distribution stuff...

While this was done a few times, netmail wasn't replied to properly, therefore
the RC stated that the applicant's netmail wasn't setup properly, when in fact
it was the RCs setup that wasn't working properly. God forbid he would admit
that, though.

 ML> gotta wonder why that is? you do know you can't send a netmail to an
 ML> applying node's new address when their mailer is not flying the new
 ML> address they don't even know they have, right?? and polling using the temp
 ML> address when there's more than one new node using that address is also a
 ML> problem because mail for the one applicant may be picked up by the other
 ML> applicant when both are flying the same temp address... so, how would you
 ML> do it??

That's a great question, but the applicant still doesn't have a node number,
even though he has successfully routed netmail through my system to that RC as
well, after the fact that he sent 3-4 direct netmails using that "temporary"
node number he was provided with -- which was admitted to be received by the
RC every time. When the RC said he replied with further instructions, the
applicant polled his system using the temporary node number (I went over his
configuration to make sure it was correct even), and there was no mail received
from the RCs system.

While trying to figure out the issue, the applicant called him voice (which he
was told to do) and asked why he hasn't gotten a response from him yet. All the
applicant said he was greeted with was a cocky, high-horsed attitude stating
that the applicant's configuration was wrong, and that he wouldn't get a node
number until he could successfully send netmail (WHICH HE ALREADY DID ON
NUMEROUS OCCASIONS, yet nothing was received in return). How does that
compute? [sigh]

 NB>> Oddly enough, I set this guy up in about 15 minutes as a point
 NB>> here, which goes to show that the mentioned RC didn't have a proper
 NB>> configuration for his "temporary" node.

 ML> using only fidonet technology and netmail??

Yep. This fidonet "point" now has a node number in my othernet as well, after
successfully netmailing me as well as my areafix to setup his own areas (for
both networks). So where did the original problem lie?

 ML> BTW: why do yo think i spend so much time correcting others and educating
 ML> new folks??

It's appreciated. Maybe some people that have been around here quite some time
need a refresher course. :(

Regards,
Nick

--- SBBSecho 2.20-Linux
 * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)