Text 1383, 89 rader
Skriven 2012-07-27 22:21:33 av mark lewis (1:3634/12.0)
   Kommentar till text 1366 av Michiel van der Vlist (2:280/5555)
Ärende: daja vu (was: .fidonet)
===============================
 >> No, she did not admit the problem, she gave a bogus explanation that
 >> does not hold water.

 JK> Ok, then you tell me how I can prohibit one single node from having
 JK> his mail seen  by his own system then..

 MvdV> That is not what I claim did happen.

but TM is and has been claining such... even in netmail to me he stated this...

 JK> because I'd love to apply it to _your_ system.

 MvdV> I know that the NAB Troika considered changing the filtering from
 MvdV> all of non Z1 to read only to only filetering certain
 MvdV> individuals, like Björn and me. So you must have an idea on how
 MvdV> to do it. It was discussed in Z1C.

really? hummm...

 JK> You lie constantly about so many things.  The only thing that was
 JK> done here was the flag left in place accidentally for Kim's system
 JK> making it read-only.  I removed it when I checked the config for his
 JK> node, after reading comments here when I had a break during the
 JK> Cooking Echo Picnic this weekend.

 MvdV> It does not compute. A system that is set to read-only can read
 MvdV> all messages written by others. So if Kim was set to read-only
 MvdV> and that was the only problem, he should have been able to read
 MvdV> Torbjorn's messages no matter from where these messages entered
 MvdV> the byte stream. OTOH, messages originating from Kim's system
 MvdV> would not have reached the rest of the net. But the reverse was
 MvdV> the case. 

it is very possible that readonly is used in the opposite direction concerning
importing or not from the remote node instead of transmitting to the remote
node... this depends on the programer's POV and their logic flow... i've done
it more than once and had to go back and flip things around when everyone
testing and using my code was looking at it the other way around...

 JK> #1) I wouldn't doubt someone like YOU prevented Torbjorn's messages
 JK> from getting out just to stir up trouble.

 MvdV> I am not in a position do do that.

he does connect directly with you, does he not? the path lines show such a
connection...

 JK> #2) Look at the nodelist debacle,  and your part in that Michiel..

 MvdV> What "part" do you believe I had in that?

feeding the fire comes to mind ;)

 JK> weren't you were right there in that echo overseas pushing Ward to do
 JK> it?

 MvdV> Why do you believe I was "pushing" Ward to do anything at all? 

why would one not believe what may be read?

 MvdV> Anyway, thos is just a smoke screen. It has nothing to do with
 MvdV> filtering echomail.

no... no smokescreen... just topic drift...

 JK> #3) And aren't you now pushing him to get a Z1 node number by asking
 JK> what's new with getting one here in Z1 while he's in Montana?

 MvdV> Your spy friend must have some "lost in translation" problems... 

who says anyone is translating for janis?

 >> If Kim was accidentally set to read-only, it would not have stopped
 >> Torbjorn's message from reaching him. The read-only works the other
 >> way around. It would have stopped Kim's messages from reaching the
 >> rest of the world. It does not add up.

 JK> If the node is set to read-only, then it doesn't import any traffic
 JK> into the echo you very silly man.

 MvdV> No, if it is set to read-only, it imports messages from the rest
 MvdV> of the network, but messages originating from it are not exported
 MvdV> into the network. 

and there is perfect proof of the opposite logic being employed...

)\/(ark

 * Origin:  (1:3634/12)