| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | was: STOP THE DUPES, now: OH SHIT! |
Denise, at 08:15 on May 20 1997, you wrote to Niels Petersen ...
>>> Well I just deleted the dupe packet to Christian, so I'll
>>> have to wait until the next mail pkt to test.
NP>> Did it work ??
NP>> Don't keep me in suspense !!!
DW> Unfortunately no, it didnt, and according to everything I've
DW> heard so far it probably wont, the main problem is that
DW> FMAIL doesnt like recieving and tossing to a "different"
DW> node/point address, so at the moment I'm having to do
DW> unsecure tosses to accept the mail from .27, since I have
DW> the mail set to export to .375 which only creates one dupe
DW> packet instead of two, which in itself is ok, as I have
DW> caught all the dupe packets so far 8-)
Dunno what happened there, or with Neils. I received 200 bounced netmails
this morning from Marwick's (R54C) system, containing all LOC_SYSOP
messages. I don't know whether my system burped or Neils BUT...
my log shows:
------[snip]------
# 20 May 21:16:16 BINK Connect 14400/Arq/V32/Lapm/V42Bis
* 20 May 21:16:19 BINK Compuware (3:640/305.12{at}fidonet)
------[snip]------
: 20 May 21:16:20 BINK Session method: ZedZap
+ 20 May 21:16:52 BINK CPS: 1596 (51095 bytes) Efficiency: 110%
------[snip]------
I don't think there would have been 51k of traffic in 24hours in this echo...
All of the messages were addressed to the various people at address 3:712/305
I have trapped all outbound to that address in case it burps again.
David
@EOT:
--- Msgedsq/2 3.10
* Origin: The JabberWOCky +61 7 3868 1597 (3:640/305)SEEN-BY: 640/305 670/213 711/934 712/305 610 @PATH: 640/305 712/610 711/934 |
|
| 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™.