| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Connecting to mystic system doesn`t work |
Hello g00r00, On Mon Jun 26 2017 17:43:40, g00r00 wrote to Nicholas Boel: gr> Are you saying on the Mystic side? He's not using Mystic. I know this. gr> Why would binkd say anything about being blocked? Its not the one gr> doing the blocking. If Mystic is sending the text, shouldn't binkd log it? I mean, unless one of the binkd programmers had a feeling the future would bring a "BLOCKED" message and ultimately be programmed to ignore it..? I'm just kinda baffled that it wouldn't log something that another mailer sent to it.. regardless if it's not actually part of the protocol or not. And if binkd would actually display it if it were sent to it, I was just letting you know that I've never seen that blocked message either, so it either isn't logging it, or it isn't actually being sent by Mystic. Or is this something only visable on the Mystic side? Regards, Nick ... "Не знаю. Я здесь только работаю." --- GoldED+/LNX 1.1.5-b20170303* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10) 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: 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™.