| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Hello |
26 Apr 08 22:44, Richard Webb wrote to Roy Witt:
RW>> RUles on zmh would cover I think. AS the capability is advertised
RW>> in the nodelist by a phone number in the appropriate field I'd
RW>> venture to guess that during zmh a system should be reachable by it.
>> Since P4 is so ancient and the ZC has made policy that circumvents a
>> lot of it, ZMH won't help you. I once had a policy complaint filed
>> against me because I passworded a node from connecting here. Both
>> the RC10 and the ZC1 decided in my favor upon appeal by the
>> complainant, but the ZC2, then acting as the IC, reversed their
>> decisions and upheld the complaint. The case was then presented
>> before the ZCC and they reversed the IC's decison. This resulted in
>> the eventual termination of that IC and policy went down hill from
>> there.
RW> Had to do that once to a guy back in my hubbing days in southeastern
RW> Iowa. A kid ran a bbs, was getting echomail. He wouldn't kick in his
RW> share of cost recovery though so I unlinked him. I refused to route
RW> his netmail even.
I opted out of the CR program in net202 when I got my internet dialup
link. The NC and my hub weren't very happy about that.
RW> NOw remember I was not a nc or anything, just a local hub.
RW> I let others in my locale within my cost recovery plan that I fed
RW> know that I wasn't feeding the kid echomail and that nobody else
RW> should feed him. Kid dropped fidonet and became a point. Swore up and
RW> down he wasn't using echomail on his bbs, but then a friend of mine
RW> proved differently. I had suspicions anyway when some of the echoes
RW> he was carrying got linked to another system that formerly didn't
RW> carry them.
His boss node shouldn't have allowed that kid to use him like that.
RW> FEllow feeding the kid wouldn't not feed the kid echomail but went to
RW> another source for it. YET he still wanted to route netmail within
RW> our net through me instead of call the nc or the system direct. so I
RW> changed his session and packet passwords .
As a point, he had no right to file a PC anyway.
RW> DIfference is, he never filed a policy complaint. HE remained part
RW> of homenet, a qwk based network and rdopped fido soon thereafter .
Whatever floated his boat.
PS got your netmail drop. I didn't notice it until I opened Argus and
there was a connect from you. I modified my mail tosser's batch file to
look for pkts and zips in Argus inbound, move them to a secure folder in
Irex and process them in the Irex inbound.
R\%/itt
--- Twit(t) Filter v2.1 (C) 2000
* Origin: SATX Alamo Area Net * South * Texas, USA * (1:397/22)SEEN-BY: 10/1 3 11/201 14/300 34/999 106/1 120/228 123/500 134/10 140/1 222/2 SEEN-BY: 226/0 249/303 261/20 38 100 1381 1404 1406 1418 266/1413 280/1027 SEEN-BY: 320/119 396/45 633/260 267 712/848 801/161 189 2222/700 2320/100 105 SEEN-BY: 2905/0 @PATH: 397/22 123/500 261/38 633/260 267 |
|
| 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™.