Hello Tommi!

07 Jul 19 19:46, you wrote to me:

 AL>> FastEcho also has a problem with the .PKT forwarding function.

 TK> Oh? Can you tell more about this?

Basically, if you receive a .PKT file destined for one of your downlinks, it 
should be placed unaltered in the temporary outbound, to be archived for the 
destination along with any other mail you are tossing.  However, it appears 
from my testing that certain .PKT header fields (including the .PKT password) 
are overwritten with the password you have defined for that downlink.  Of 
course, this causes an issue if the originating node has a different password 
defined for the destination.  There is also a minor issue with .PKT endings, 
as the forwarded .PKTs end up with an extra 2 NUL bytes tacked onto the end.

 AL>> I sent details to Tobias Burchhardt a few months back, but he
 AL>> wasn't hopeful that he would be able to fix it.

 TK> 

It's too bad, because other than the cross-zone SEEN-BY stripping and these 
issues with forwarding .PKTs, the software is virtually bullet-proof.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)