Yes, you are using mystic and not binkd! (couldn't resist ;))...
... , so I have to do more than just slap my name on it and implement "critical" ego-maniacal functions like "Say Hi to the author" into its setup utility!
BinkD is a solid choice though and works well as a mailer for Mystic
if one would choose to use it!
Hi all! Whenever I get an inbound binkp connect, I get the following error:Is
22:07:22 BINKP 1-Error receiving data (size=33 msg=Socket read error 0)
However, when I use fidopoll, I can connect to these systems just fine.
there something I am doing wrong on my end?
implement "critical" ego-maniacal functions like "Say Hi to the
author" into its setup utility!
Wow! You are keeping a close eye on what I do! ;)
BinkD is a solid choice though and works well as a mailer for
Mystic if one would choose to use it!
So the OP has a choice to fix his problem...
there something I am doing wrong on my end?
Yes, you are using mystic and not binkd! (couldn't resist ;))...
Of course he does. Anyone has a choice to use whatever they want. And
when his problem was more than likely operator error, he asks in the appropriate place for some help - which does not require changing
software at all. ;)
Of course he does. Anyone has a choice to use whatever they want.
And when his problem was more than likely operator error, he asks
in the appropriate place for some help - which does not require
changing software at all. ;)
I thought I was asking in the correct place anyway. :D
... , so I have to do more than just slap my name on it and implement "critical" ego-maniacal functions like "Say Hi to the author" into it setup utility!
Wow! You are keeping a close eye on what I do! ;)
BinkD is a solid choice though and works well as a mailer for Mystic if one would choose to use it!
So the OP has a choice to fix his problem...
What echo are you posting in again? Who is keeping a close eye on
who?
Fyi: I'm mainly here because I have a number of links in fidonet and AmigaNet, with mystic systems. So I know what's going on with the bugs that popped up last year...
He's testing against an unreleased version of software, which is what we do before we release things. The released versions of Mystic's mailer work fine and power the FSX hub which has 100+ active downlinks and
actual message activity. He can run a released version or something
else if he wants, or he can choose to help test.
Hello robert,
On Tue Nov 07 2017 18:46:40, robert wolfe wrote to Nicholas Boel:
Of course he does. Anyone has a choice to use whatever they want.
And when his problem was more than likely operator error, he asks
in the appropriate place for some help - which does not require
changing software at all. ;)
I thought I was asking in the correct place anyway. :D
I would sure as hell think so. Some people just like living life one complaint at a time. :(
Fyi: I'm mainly here because I have a number of links in fidonet and
AmigaNet, with mystic systems. So I know what's going on with the
bugs that popped up last year...
What bugs are you looking for updates on that have lasted since last year? There are no known echomail-related bugs on the list, and Mystic moves a LOT of echomail.
If you really do read here for development updates, then you already
know that development stuff isn't really openly discussed here and
hasn't been for a long time. But I don't think what you're saying is true, otherwise you'd simply have asked about the issue you're
"waiting over a year to hear about."
I like testing. I like my Pi :) Mystic is a pretty decent package with what I need to do on the Pi, so as far as running the Pi system, I am going to try and stick with Mystic, even though I don't have much time these days to mod it or work some more on my main system.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 88:58:32 |
| Calls: | 2,069 |
| Calls today: | 2 |
| Files: | 11,134 |
| Messages: | 946,769 |