TIP: Click on subject to list as thread! ANSI
echo: mystic
to: Wilfred van Velzen
from: g00r00
date: 2017-06-26 15:34:14
subject: Connecting to mystic system doesn`t work

Wv>  gr> Maybe, but I think that would be up to binkd to do so.
 Wv> 
 Wv> Binkd only knows the binkp protocol. The "blocked"
message is outside
 Wv> that protocol, so just garbage to it, which is ignored. (I suspect)

Yep I am well aware of that.  But I thought you asked about changing it so a
meaningful message appears in the BINKD log.  I am not a binkd developer, so I
can't change the way it logs anything! :)

If your IP is blocked the connection is dropped when you try to connect.  The
way that binkd logs that is not up to me; I'm not sure there is anything I
could do other than to not block it when its blocked.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
SEEN-BY: 57/0 116/102 123/180 130/210 512 154/10 218/630 226/100 250/3 317/2
SEEN-BY: 393/68 633/267 280 640/384 712/620 848 770/0 1 3 100 340 772/0 1 210
SEEN-BY: 772/500
@PATH: 129/215 154/10 770/1 712/848 633/267

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