| |
DF3VI > TOUS 04.08.06 09:07l 24 Lines 1005 Bytes #999 (90) @ WW
BID : U7GDB0II_00U
Read: DG1VV GUEST
Subj: Re: Hacker TU5EX
Path: DB0FHN<DB0FOR<DB0MRW<OK0PPL<DB0RES<DB0GOS<DB0OVN<DB0II
Sent: 060730/1442z @:DB0II.#NRW.DEU.EU [BCM M'Gladbach] obcm1.06 LT:090
From: DF3VI @ DB0II.#NRW.DEU.EU (Patrick)
To: TOUS @ WW
Reply-To: DF3VI @ DB0OVN.#NRW.DEU.EU
X-Info: Sent with login password
Andre,
I think it is quite obvious what happened, and TU5EX has nothing to do with
it, except being the first forward partner AFTER the fault happened.
> R:060725/0230z @:N2BQF.NY.USA.NA [OpenBCM] OBcm1.06b59
> From: VE2DTD @ N2BQF.NY.USA.NA (Alan)
> To: PENSEE @ FRANCA
> X-Info: Sent with login password
>
> R:060717/1037Z @:N2BQF.NY.USA.NA #:17647 [N2BQF.DYNDNS.ORG] FBB7.01.35 alpha
You can see that the mails had been received by N2BQF FBB two weeks ago, and
then been sent to N2BQF BCM five days ago. There the fault happened, some
misconfiguration made FBB sending files to the other BBS that was not in
forward mode due to FBB forwarding even when the partner does NOT respond as
a forward-partner. When these bulletins had been put into forward yesterday
by N2BQF not recogizing this error , there is nothing for ANY receiving BBS to
prevent this.
73, Patrick
Read previous mail | Read next mail
| |
