MSGID: 1:153/757.0 1c7690a6
REPLY: 2:292/854.180 637e0f0d
TZUTC: -0800
CHRS: LATIN-1 2
>> My first problem is that FIDO-REQ is generating hundreds of dupes in
>> Aftershock and I have no idea why. Normally SBBSEcho handles dupes
>> perfectly, but not for that echo.

> What is FIDO-REQ? Regular echo? I need to subscribe to it for problem
> investigation. I do not see this echo in Areafix of Ward. Will ask him
> if it possible to make this echo available for me.

This is a bit complicated.

A node in Z1 is posting very big messages, over 400k. Those messages are
tossing OK here but when they pass through some nodes that don't support
messages over a certain size (64k, I think) they can get mangled. I see two
mangled messages without correct header info or MSGID. For every good message
I see here I see two mangled messages also. This issue will reveal itself
differently at different nodes with different tossers.

If I read the situation correctly that nodes "New file Announcement" keeps
growing every day because the already announced files are not being cleared so
they get announced again day after day. The message size grows a little every
day.

That node seems to be on auto pilot so that will keep on happening until he
gets in front of his keyboard again.

His packets are valid, just quite large and growing every day.

--- BBBS/Li6 v4.10 Toy-6
 * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 123/120 131
SEEN-BY: 129/305 134/100 153/135 757 7715 154/10 218/700 840 220/70
SEEN-BY: 221/6 226/17 30 227/114 229/110 111 112 113 114 206 317 424
SEEN-BY: 229/426 428 470 550 664 700 250/5 8 266/512 267/800 282/1038
SEEN-BY: 298/25 305/3 317/3 320/219 322/757 342/200 396/45 633/280
SEEN-BY: 712/848 770/1 3634/12
PATH: 153/757 221/6 218/840 770/1 317/3 229/426