Text 26387, 367 rader
Skriven 2015-07-30 12:05:44 av mark lewis (1:3634/12.73)
Kommentar till text 26363 av David Drummond (3:640/305)
Ärende: Both Are Covered
========================
30 Jul 15 18:24, you wrote to Bill McGarrity:
DD>>> You have presented hearsay.
DD>>> If it its possible, prove it by doing it.
BM>> Fact was provided and if you fail to see that then so be it.
DD> There are no such things as facts, only opinions...
don't let michiel hear/see you say/write that...
BM>> Even Michiel said it was possible under certain circumstances.
DD> It is possible for man to walk on the moon too - but unlikely that you
DD> or I will see it.
i don't know about you but millions of people have seen it...
BM>> Everything you've stated with regard to addresses within PKT's was
BM>> wrong
DD> I have made no claims about addresses in packets, only the absence of
DD> them in echomail messages.
and you've been very wrong in every utterance of that statement...
perhaps this dump of the PKT that five of your messages arrived in on my main
system will convience you? please note the PKT header addresses as well as the
packed message header addresses... if you require a hex dump of the PKT, i can
also provide that so you can dissect the binary headers yourself...
==== Begin "ddproof.txt" ====
PKT Name = *PATH*\inbound\pkt-save\55b9e39a.pkt
Type 2+ Header (FSC-0039/0048)
OrgNode = 500
DstNode = 12
Year = 2015
Month = 6
Day = 30
Hours = 4
Minutes = 43
Seconds = 1
Baud = 0
PktVer = 2
OrgNet = 123
DstNet = 3634
PrdCodL = 255d = FFh HPT
PVMajor = 1
Password = "xxxxxxxx"
QOrgZone = 1
QDstZone = 1
AUXNet = 0
CapValid = 256 swapped : 1
PrdCodH = 16
PVMinor = 9
CapWord = 1 Validation = TRUE
OrigZone = 1
DestZone = 1
OrigPoint = 0
DestPoint = 0
ProdData = 00h 00h 00h 00h -->
End of .PKT header info. Press <enter> to continue
Packet Messages Follow
MsgHeader :
MsgStart = 2
MsgOrigNode = 500
MsgDestNode = 12
MsgOrigNet = 123
MsgDestNet = 3634
MsgAttrib = 0
MsgCost = 0
MsgDateTime = 30 Jul 15 18:24:37
MsgBody :
MsgToUser = Bill McGarrity
MsgFromUser = David Drummond
MsgSubject = Both Are Covered
AREA:FIDONEWS
^aMSGID: 3:640/305 55b9df3e
^aREPLY: 18543.2fidonews@1:266/404 1a1ee187
^aPID: JamNNTPd/Linux 1
^aCHRS: CP850 2
^aTID: CrashMail II/Linux 0.71
On 30/07/2015 9:17 AM, Bill McGarrity -> David Drummond wrote:
DD>> You have presented hearsay.
DD>> If it its possible, prove it by doing it.
BM> Fact was provided and if you fail to see that then so be it.
There are no such things as facts, only opinions...
BM> Even Michiel said it was possible under certain circumstances.
It is possible for man to walk on the moon too - but unlikely that you or I
will see it.
BM> Everything you've stated with regard to addresses within PKT's was
BM> wrong
I have made no claims about addresses in packets, only the absence of them in
echomail messages.
BM> so it is not my problem if you resist logic.
What logic? If you drop a packet of echo mail at my node it will toss the
messages according to their echo tag.
Those messages do NOT contain an address to be forwarded to. How will they
get there?
BM> It's your issue. I really don't care whether you believe it or
BM> not
Why do you insist on claiming it is so if you cannot prove it?
-!- Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101
Thunderbird/31.
! Origin: Somewhere over the rainbow (3:640/305)
SEEN+BY: 18/2 109/500 116/116 123/5 52 57 140 400 500 789 6502 124/5013 5014
SEEN+BY: 140/1 153/757 203/0 226/600 261/38 1466 320/101 111 119 219 322/759
SEEN+BY: 323/120 342/11 806 3634/12
^aPATH: 640/305 384 203/0 320/119 123/500
Press <enter> to continue
MsgHeader :
MsgStart = 2
MsgOrigNode = 500
MsgDestNode = 12
MsgOrigNet = 123
MsgDestNet = 3634
MsgAttrib = 0
MsgCost = 0
MsgDateTime = 30 Jul 15 18:26:08
MsgBody :
MsgToUser = Bill McGarrity
MsgFromUser = David Drummond
MsgSubject = Routing 200MB of echomail via an unsuspecting system
AREA:FIDONEWS
^aMSGID: 3:640/305 55b9df98
^aREPLY: 18544.2fidonews@1:266/404 1a1ee189
^aPID: JamNNTPd/Linux 1
^aCHRS: CP850 2
^aTID: CrashMail II/Linux 0.71
On 30/07/2015 9:17 AM, Bill McGarrity -> David Drummond wrote:
BM>> Which was shown to you..
DD>> Where was this defining echo message sent to and via?
BM> Have you not been following the posts here?
I'm waiting for a "routed" echo message to sho up at my node - the rest is
just hot air.
Put your money where your mouth is - prove it by doing it.
-!- Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101
Thunderbird/31.
! Origin: Somewhere over the rainbow (3:640/305)
SEEN+BY: 18/2 109/500 116/116 123/5 52 57 140 400 500 789 6502 124/5013 5014
SEEN+BY: 140/1 153/757 203/0 226/600 261/38 1466 320/101 111 119 219 322/759
SEEN+BY: 323/120 342/11 806 3634/12
^aPATH: 640/305 384 203/0 320/119 123/500
Press <enter> to continue
MsgHeader :
MsgStart = 2
MsgOrigNode = 500
MsgDestNode = 12
MsgOrigNet = 123
MsgDestNet = 3634
MsgAttrib = 0
MsgCost = 0
MsgDateTime = 30 Jul 15 18:27:43
MsgBody :
MsgToUser = Joe Delahaye
MsgFromUser = David Drummond
MsgSubject = Routing 200MB of echomail via an unsuspecting system
AREA:FIDONEWS
^aMSGID: 3:640/305 55b9dffc
^aREPLY: 53856.fidonews@1:249/303 1a1f8e8b
^aPID: JamNNTPd/Linux 1
^aCHRS: CP850 2
^aTID: CrashMail II/Linux 0.71
On 30/07/2015 12:04 PM, Joe Delahaye -> Michiel van der Vlist wrote:
MV>> Pointing to stone age software where this can happen is pointless if
that
MV>> software is no longer in use today.
JD> There are still nodes in Fidonet who use that stoneage software. When
it no
JD> longer works, they will be gone, but not before. Thus with those
JD> nodes,
it is
JD> still possible.
The route you proving echomessage via them.
I'm still waiting for one to arrive at my node.
-!- Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101
Thunderbird/31.
! Origin: Somewhere over the rainbow (3:640/305)
SEEN+BY: 18/2 109/500 116/116 123/5 52 57 140 400 500 789 6502 124/5013 5014
SEEN+BY: 140/1 153/757 203/0 226/600 261/38 1466 320/101 111 119 219 322/759
SEEN+BY: 323/120 342/11 806 3634/12
^aPATH: 640/305 384 203/0 320/119 123/500
Press <enter> to continue
MsgHeader :
MsgStart = 2
MsgOrigNode = 500
MsgDestNode = 12
MsgOrigNet = 123
MsgDestNet = 3634
MsgAttrib = 0
MsgCost = 0
MsgDateTime = 30 Jul 15 18:28:43
MsgBody :
MsgToUser = Björn Felten
MsgFromUser = David Drummond
MsgSubject = Both Are Covered
AREA:FIDONEWS
^aMSGID: 3:640/305 55b9e038
^aREPLY: 2:203/2 55b98aa2
^aPID: JamNNTPd/Linux 1
^aCHRS: CP850 2
^aTID: CrashMail II/Linux 0.71
On 30/07/2015 12:23 PM, 2:203/2 wrote:
BM>> Everything you've stated with regard to addresses within PKT's was
wrong so it is not my problem if you
BM>> resist logic.
BF> Sorry Bill, but you are wrong and David is right. I know for sure,
BF> I've been programming for FTN for decades. I know the inner workings
BF> (and flaws) perfectly well.
BF> I can easily write a program that sends echomail like netmail, but
BF> I
BF> can never make it have one primary address and after that (AKA
BF> routing)
BF> a second address to forward the message to.
BF> Only Mark knows about mail processors that can *route* (not send!)
BF> echomail, it seems. But as usual it's probably a well guarded secret
BF> what systems are running such archaic anomalies.
It's probably documented in Janis' secret book...
-!- Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101
Thunderbird/31.
! Origin: Somewhere over the rainbow (3:640/305)
SEEN+BY: 18/2 109/500 116/116 123/5 52 57 140 400 500 789 6502 124/5013 5014
SEEN+BY: 140/1 153/757 203/0 226/600 261/38 1466 320/101 111 119 219 322/759
SEEN+BY: 323/120 342/11 806 3634/12
^aPATH: 640/305 384 203/0 320/119 123/500
Press <enter> to continue
MsgHeader :
MsgStart = 2
MsgOrigNode = 500
MsgDestNode = 12
MsgOrigNet = 123
MsgDestNet = 3634
MsgAttrib = 0
MsgCost = 0
MsgDateTime = 30 Jul 15 18:31:49
MsgBody :
MsgToUser = mark lewis
MsgFromUser = David Drummond
MsgSubject = Routing 200MB of echomail via an unsuspecting system
AREA:FIDONEWS
^aMSGID: 3:640/305 55b9e0ec
^aREPLY: 1:3634/12.73 55b97def
^aPID: JamNNTPd/Linux 1
^aCHRS: CP850 2
^aTID: CrashMail II/Linux 0.71
On 30/07/2015 11:29 AM, mark lewis -> David Drummond wrote:
BM>>> Which was shown to you..
DD>> Where was this defining echo message sent to and via?
ml> you must be playing "catch up" with the posts as it has been posted
ml> twice by matt...
So Matt sent it from and to himself?
That doesn't prove shit to us out here in the world.
I want to see a "routed" echo message appear at MY node.
Until then I'm calling Matt a fibber!
--
And the bewildered herd is still believing
Everything they've been told from their birth
-!- Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101
Thunderbird/31.
! Origin: Somewhere over the rainbow (3:640/305)
SEEN+BY: 18/2 109/500 116/116 123/5 52 57 140 400 500 789 6502 124/5013 5014
SEEN+BY: 140/1 153/757 203/0 226/600 261/38 1466 320/101 111 119 219 322/759
SEEN+BY: 323/120 342/11 806 3634/12
^aPATH: 640/305 384 203/0 320/119 123/500
Press <enter> to continue
Logical end of PKT reached.
==== End "ddproof.txt" ====
BM>> so it is not my problem if you resist logic.
DD> What logic? If you drop a packet of echo mail at my node it will toss
DD> the messages according to their echo tag.
and what will it do if those echomail messages' header's destination address
fields contain the address of another system instead of your system's address?
will it still toss them into your message base or will it refuse to toss them
and flag them as badmail or invalid destination somehow?
DD> Those messages do NOT contain an address to be forwarded to. How will
DD> they get there?
BM>> It's your issue. I really don't care whether you believe it or not
DD> Why do you insist on claiming it is so if you cannot prove it?
one only need to look at the specs to see the proof, david...
)\/(ark
... Club Seals, not Sandwiches.
---
* Origin: (1:3634/12.73)
|