TIP: Click on subject to list as thread! ANSI
echo: mystic
to: OLI
from: WILFRED VAN VELZEN
date: 2020-04-10 18:04:00
subject: Re: 255 character long

Hi Oli,

On 2020-04-10 17:04:23, you wrote to me:

 Ol> Interesting. At least two nodes in fsxnet received bad packages with
 Ol> scrambled messages. The origin line of 292/854 were in the To, From or
 Ol> Subject field. There were also some empty messages in this area with
 Ol> 2:292/854 in the origin line, but otherwise completely empty. But how do
we
 Ol> know that 292/384 is causing the problems? It could be 261/38 too (less
 Ol> likely though).

It happend when 2:292/854 reset his PC earlier this week when he returned from
the hospital, that caused some problematic pkts to be exported from his system.
Today there was another event with the same symptoms. This happend before
several times when he returned from his holidays in the states for example...

 Ol> Using something like this with fidoweb-style echo routing has to
 Ol> create some problems at some point. Like loops and dupes.

Some are caught on my system when they have an older date (like >60 days). And
dupes are of course also caught. Everything else that is more or less a legit
message (although from:, subject: and body are empty for instance) passes
through... But this caused irex to crash on one of my downlinks.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

SOURCE: echomail via QWK@docsplace.org

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™.