> Could you please explain why there are correct hydra implementations for
> DOS, OS/2, Win32 - and nothing for UNIX?
Why do you ask me? I do not know. I *guess* that's because authors of
hydra did not have enough experience in unix programming.
> > > - Ignoring the case of ?lo files and their contents (for now, I have a
> > > script translating all this to lowercase. But that's not good)
> > Hmm, if someone explains when this is necessary.
> That's easy. You may ask 1:2424/101 when this is necessary. When all mail
> is processed by external programs in other OS ( OS/2 in case of /101 ),
> filenames in the spool are written in uppercase.
> Perhaps you know that people do not use only ifmail+ifnews with ifcico.
> Lots of other mailprocessors work with BSO, too. But not all of them do it
> "right" for ifcico. I doubt it's hard to change this.
I do not see why this explanation by example is "easy". I *know*
that ifmail works in mixed dos/unix environment, that's why it has
`dosoutbound' configuration option. There *may* be problems but
how can I deal with them unless they are clearly explained?
> > > - Correct MSGID susbstitution (personally, I don't need it. But my
> > > uplinks complain about this)
> > ifmail has correct MSGID generator. "os" version has incorrect, and
> > potentially dangerous generator.
> So why almost all the sysops of xUSSR FidoNet area use "incorrect" MSGID
Why do you ask me? Ask them?
> > > - Restore .flos after failed outgoing call. There's no need in this
> > > feature on *my* station, but there're TONS of people who want this.
> > What's that? flo's are not removed after failed sessions.
> I'm sorry, you are wrong. There's even the special patch in tx.sc version
> to create empty .flos when the session was aborted.
Again, ifcico does not remove incompletely processed .flo's for me.
There *may* be a bug and it *may* do it under some conditions, but
I've never seen it and nobody ever demonstrated it to me.
If you are talking about restart of failed polling, this can and should
be done externally. Matter of four lines of shell code.