TIP: Click on subject to list as thread! ANSI
echo: mystic
to: Nicholas Boel
from: mark lewis
date: 2015-04-04 10:21:38
subject: DopeWars for Mystic BBS on SourceForge

On Fri, 03 Apr 2015, Nicholas Boel wrote to mark lewis:

 ml> and you sent it to my 1:3634/12 address?? i've nothing here from 
 ml> you :?

 NB> Bleh, you found it. That's why I don't usually reply via netmail 
 NB> to posted messages, as I don't pay attention to the address I'm 
 NB> replying to.. only the person. :(

not a problem... at one time i was using my laptop and its /12.71 point
installation for most all of my fidonet stuff... since the new hardware is
in place, i'm mostly in the computer room where i can work on it... since
it sits beside my main system, i'm doing more from there when i do fidonet
stuff... the laptop has become wrapped up with other stuff and is not as
easily accessible as it was... that should all be changing in the future
though... there's at least 6 different fidonet connected installations here
so echomail is seen on most of them but netmail is definitely specific to
the destination ;) 

[trim]

 NB> Either that, or your Mystic system banned my IP address.

no ban in place that i found... i think the "MULTILPE" log entry
or whatever it was was indicating that mystic thought you were already
connected... in other words, a stuck connection... especially since the DSL
had dropped quite many times over the course of when it started and when i
was able to fix it...

 NB> I've seen that happen before and have seen the same failed 
 NB> connections with other Mystic systems that I crash mail to. I've 
 NB> asked for a fix for that quite some time ago (binkp should either 
 NB> have it's own connections per minute(s) settings, or at the very 
 NB> least be immune to the current one that covers *every* protocol), 
 NB> but it hasn't been done yet.

i think i understand what you are saying here... i know that binkd and the
argus family have something to limit the number of attempts to connect and
then they have a stand-off time for the delay between attempts plus another
counter for total attempts before a system is marked as uncontactable... i
don't know if those counters, especially the last one, are rest if the
remote system initiates a successful connection, though... they should...
hopefully mystic will expand on things like this... i remember trying to
point out something similar and using FD as an example of what a feature
rich mailer offers... we can only wait and see what happens in the
future...

)\/(ark

* Origin: (1:3634/12)
SEEN-BY: 19/33 34/999 90/1 116/18 120/331 123/500 1406 128/187 135/364 140/1
SEEN-BY: 218/700 226/0 160 230/150 240/1120 249/303 250/1 261/38 100 266/404
SEEN-BY: 266/1413 267/155 280/464 1027 282/1031 1056 292/854 907 908 311/2
SEEN-BY: 320/119 340/400 393/68 396/45 633/267 280 640/384 712/620 848 770/1
SEEN-BY: 801/161
@PATH: 3634/12 123/500 261/38 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™.