Does anyone know the differences, relationships and/or bugginess of the various









































































































































*ico mailers (and ifcico version)?

AFAIK mbcico was forked from ifcico (but from which version). What about qico?

---
* Origin: (21:3/102)

166
Hello Oli,

Does anyone know the differences, relationships and/or bugginess of
the various *ico mailers (and ifcico version)?

The only one I know is mbcico, it's well behaved.

AFAIK mbcico was forked from ifcico (but from which version). What
about qico?

It was a very long time ago that Michiel Broek must have forked ifcico and I'm not sure which version he started with.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Re: ifcico, mbcico, qico
By: Oli to All on Thu Apr 30 2020 09:44 am

Does anyone know the differences, relationships and/or bugginess of the various *ico mailers (and ifcico version)?

Well, I've played a bit with the *ico mailers - and I'm running ifcico and qico









































































































































on Hub 3.

AFAIK mbcico was forked from ifcico (but from which version). What about qico?

IIRC, I remember reading that mbcico was forked from ifcico. I've been meaning to compare it, because ifcico coredumps on many of the config file settings. (IE: setting debug, or scheduling).

I've found qico somewhat similar to binkd - it can do fileboxes, call an exit on received mail, etc - and it has better debugging. I had to fork it though on









































































































































github and fix zmodem, since it failed on transfers with old software.

You can connect with them on Hub 3 - qico is on 60179 and ifcico is on 60177. While your binkd password is not configure don Hub 3 - you can use a test node of 3/999 and password LETMEIN if you want to play.
...ëîåã



... As a boy, he swallowed a teaspoon. And he hasn't stirred since.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

alterego wrote (2020-04-30):

Does anyone know the differences, relationships and/or bugginess of
the various *ico mailers (and ifcico version)?

Well, I've played a bit with the *ico mailers - and I'm running ifcico
and qico on Hub 3.

AFAIK mbcico was forked from ifcico (but from which version). What
about qico?

IIRC, I remember reading that mbcico was forked from ifcico. I've been meaning to compare it, because ifcico coredumps on many of the config
file settings. (IE: setting debug, or scheduling).

I've found qico somewhat similar to binkd - it can do fileboxes, call an exit on received mail, etc - and it has better debugging. I had to fork
it though on github and fix zmodem, since it failed on transfers with old software.

That was my impression too. I stumbled upon a qico repo yesterday and the config file looked interesting. I'm also interested in the binkp part. Maybe I'll try to compile qico.

---
* Origin: (21:3/102)

alterego wrote (2020-04-30):

You can connect with them on Hub 3 - qico is on 60179 and ifcico is on 60177. While your binkd password is not configure don Hub 3 - you can use
a test node of 3/999 and password LETMEIN if you want to play.

Now I'm stuck at

qico: 30 Apr 20 13:35:31 [10496]: We should not call to 21:3/100 at this time

---
* Origin: (21:3/102)

Oli wrote (2020-04-30):

You can connect with them on Hub 3 - qico is on 60179 and ifcico is
on 60177. While your binkd password is not configure don Hub 3 - you
can use a test node of 3/999 and password LETMEIN if you want to
play.

Now I'm stuck at

qico: 30 Apr 20 13:35:31 [10496]: We should not call to 21:3/100 at this time

I have to admit, I don't understand how qico works.

---
* Origin: (21:3/102)

Re: ifcico, mbcico, qico
By: Oli to alterego on Thu Apr 30 2020 01:40 pm

qico: 30 Apr 20 13:35:31 [10496]: We should not call to 21:3/100 at this time

Hmm, I havent seen that.

But I did have to configure qico.substs so that it would make network calls.

subst 10:2/1 10.1.3.84:10023 CM ifc

I think the CM flag is important.
...ëîåã

... Success usually comes to those too busy to look for it.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

alterego wrote (2020-04-30):

Re: ifcico, mbcico, qico
By: Oli to alterego on Thu Apr 30 2020 01:40 pm

qico: 30 Apr 20 13:35:31 [10496]: We should not call to 21:3/100 at
this time

Hmm, I havent seen that.

But I did have to configure qico.substs so that it would make network calls.

subst 10:2/1 10.1.3.84:10023 CM ifc

I think the CM flag is important.

I used 0:00-23:59, now I changes it to CM, but it doesn't make a difference.

How do you run qico? I tried

qico -cI 21:3/100

but that doesn't seem to work. Is my config wrong or am I using the wrong parameters? If I run qico as a daemon, qctl and qcc just return the help text.

---
* Origin: (21:3/102)

Re: ifcico, mbcico, qico
By: Oli to alterego on Thu Apr 30 2020 02:56 pm

How do you run qico? I tried
qico -cI 21:3/100

So from what i worked out, I think this tries a modem dial.

I use:
qico -i 10.1.3.12:10123 10:2/2

but that doesn't seem to work. Is my config wrong or am I using the wrong parameters? If I run qico as a daemon, qctl and qcc just return the help text.

Are you on a Pi?

I had qctl and qcc work when I was on Intel, but since I've compile it on the Pi, I just get the help screen. Something I'm yet to figure out.

qico -d works though. It if you create outbound mail, it should try to send it. ...ëîåã

... Beware of all enterprises requiring new clothes.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

alterego wrote (2020-04-30):

Re: ifcico, mbcico, qico
By: Oli to alterego on Thu Apr 30 2020 02:56 pm

How do you run qico? I tried
qico -cI 21:3/100

So from what i worked out, I think this tries a modem dial.

I used 21:3/999 instead of 21:3/100 in qico.passwd and qico.substs

Now I see the failed modem dial.

I use:
qico -i 10.1.3.12:10123 10:2/2

That works, with ifc and binkp :)

but that doesn't seem to work. Is my config wrong or am I using the
wrong parameters? If I run qico as a daemon, qctl and qcc just
return the help text.

Are you on a Pi?

I am.

I had qctl and qcc work when I was on Intel, but since I've compile it on the Pi, I just get the help screen. Something I'm yet to figure out.

weird.

qico -d works though. It if you create outbound mail, it should try to
send it.

Ok, I'll try later.

---
* Origin: (21:3/102)

alterego wrote (2020-04-30):

qico -d works though. It if you create outbound mail, it should try to
send it.

30 Apr 20 17:40:13 binkp[14136]: connecting to 21:3/100 at uvacs3kkxybpsc6j4 lujw6s3ihqydxhnephcfemybsdp4lxamniid.onion via socks 127.0.0.1:9050 [binkp]
30 Apr 20 17:40:13 binkp[14136]: TCP/IP connection with socks 127.0.0.1:9050
30 Apr 20 17:40:16 binkp[14136]: starting outbound Binkp session
30 Apr 20 17:40:18 binkp[14136]: address: 21:3/100@fsxnet
30 Apr 20 17:40:18 binkp[14136]: system: Mutura HUB/Linucus BBS
30 Apr 20 17:40:18 binkp[14136]: from: Parkdale AUS
30 Apr 20 17:40:18 binkp[14136]: sysop: Deon George
30 Apr 20 17:40:18 binkp[14136]: phone: -Unpublished-
30 Apr 20 17:40:18 binkp[14136]: flags: [300] CM,INA:alterant.leenooks.net,
IBN:24555,ITN:60177,IBNO
30 Apr 20 17:40:18 binkp[14136]: mailer: (null)
30 Apr 20 17:40:18 binkp[14136]: time: 00:00:00, CM
30 Apr 20 17:40:18 binkp[14136]: we have: 0b mail, 0b files
30 Apr 20 17:40:18 binkp[14136]: options: Binkp/PWD/Plain
30 Apr 20 17:40:18 binkp[14136]: total: 0:00:00 online, 0b sent, 0b received
30 Apr 20 17:40:18 binkp[14136]: session with 21:3/100 successful [ok]
30 Apr 20 17:40:18 binkp[14136]: exiting with rc=0


qico.conf:

if addr 21:3/100
socks 127.0.0.1:9050 *
endif

---
* Origin: (21:3/102)

On 04-30-20 19:21, alterego wrote to Oli <=-

I've found qico somewhat similar to binkd - it can do fileboxes, call
an exit on received mail, etc - and it has better debugging. I had to
fork it though on github and fix zmodem, since it failed on transfers
with old software.

Is your fork of qico readily available?


... From this strange confusion grows a perverse communication.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Re: Re: ifcico, mbcico, qico
By: Vk3jed to alterego on Fri May 01 2020 10:20 am

Is your fork of qico readily available?

Yeah, here:

https://github.com/leenooks/qico
...ëîåã

... Extreme sorrow laughs; extreme joy weeps.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Vk3jed wrote (2020-05-01):

On 04-30-20 19:21, alterego wrote to Oli <=-

I've found qico somewhat similar to binkd - it can do fileboxes,
call an exit on received mail, etc - and it has better debugging. I
had to fork it though on github and fix zmodem, since it failed on
transfers with old software.

Is your fork of qico readily available?

https://github.com/leenooks/qico

---
* Origin: (21:3/102)

On 05-01-20 20:57, alterego wrote to Vk3jed <=-

Is your fork of qico readily available?

Yeah, here:

https://github.com/leenooks/qico

Thanks, will check it out. :)


... The wages of sin are unreported.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 05-01-20 12:43, Oli wrote to Vk3jed <=-

Is your fork of qico readily available?

https://github.com/leenooks/qico

Thanks, I grabbed a copy, will have a play later. :)


... Eschew ampersands & abbreviations, etc.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 30 Apr 2020 at 09:44a, Oli pondered and said...

Does anyone know the differences, relationships and/or bugginess of the various

I have no idea about these specifics, just that the names are
all derived from the original `uucico` (Unix-to-Unix Call-In,
Call-Out) program from the UUCP package distributed with 7th
Edition research Unix.

qico seems like it'd been specific to QWK. ifcico is, I think,
named for the original Fidonet<->UUCP software that bridged
the gap between Fidonet and USENET/the Internet.

There are some interesting historical documents about the
relationship between Fidonet (and by extension FTN) and the
Internet floating around. They may be helpful for gleaning
some of the etymology here.

In general, I think one might accurately say that these three
names are for three packages that do similar things: the first
two are Fidonet mailers, the latter is a QWK mailer.

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

tenser wrote (2020-05-03):

I have no idea about these specifics, just that the names are
all derived from the original `uucico` (Unix-to-Unix Call-In,
Call-Out) program from the UUCP package distributed with 7th
Edition research Unix.

I didn't know that.

qico seems like it'd been specific to QWK. ifcico is, I think,
named for the original Fidonet<->UUCP software that bridged
the gap between Fidonet and USENET/the Internet.

AFAIK all three programs are EMSI and binkp FTN mailers. ifcico is (or was) part of ifmail. qico has no QWK functionality.

---
* Origin: (21:3/102)

On 02 May 2020 at 09:46p, Oli pondered and said...

qico seems like it'd been specific to QWK. ifcico is, I think,
named for the original Fidonet<->UUCP software that bridged
the gap between Fidonet and USENET/the Internet.

AFAIK all three programs are EMSI and binkp FTN mailers. ifcico is (or was) part of ifmail. qico has no QWK functionality.

Ah, no idea then. I was guessing about qico based on the name.

The Unix stuff I can promise you is accurate, though.

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: ifcico, mbcico, qico
By: Oli to alterego on Thu Apr 30 2020 02:56 pm

Hey Oli,

parameters? If I run qico as a daemon, qctl and qcc just return the help text.

Just thought I'd let you know that I've fixed the qctl/qcc on the Pi.
...ëîåã

... I think sex is better than logic, but I can't prove it.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

alterego wrote (2020-05-13):

Hey Oli,

parameters? If I run qico as a daemon, qctl and qcc just return the
help text.

Just thought I'd let you know that I've fixed the qctl/qcc on the Pi.

Very nice! Finally some old-school outbound queue manager :).
I wonder what the countdowns are good for (top and bottom), if this is normal or if there is a locked file or some configuration error.

---
* Origin: (21:3/102)

Re: ifcico, mbcico, qico
By: Oli to alterego on Thu May 14 2020 08:32 am

I wonder what the countdowns are good for (top and bottom), if this is normal or if there is a locked file or some configuration error.

Yeah that I havent figured out yet - admittedly, I dont use it much :)
...ëîåã

... Back up my hard disk? I can't find the reverse switch!
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)