Hello all,

I have a problem and can't find the solution, I get TIC files that are always discarded as "XXnnnnnn.bad" extension and remain in /var/spool/ftn/inb/ order.

The problem seems to be the "To" field that always comes from upstream.

No zone or net in the 'To' address (Firstname Lastname, Zone:Net/Node) in TIC /var/spool/ftn/inb/XXnnnnnn.TIC

Do any of you have an idea how I can solve this problem in my Husky configuration?

According to my upstream, I am the only person who has this problem and he
has no idea, he uses "Internet Rex v2.29" on Windows to send the TIC files
and the payload. His other peers MysticBBS would work.

Many thanks for the help

Alisha Manuela Stutz
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)

Re: No zone or net in the 'To' address (Firstname Lastname, Zone:Net/Node)
By: Alisha Stutz to All on Sun Jan 16 2022 10:28 pm

Hi Alisha,

The problem seems to be the "To" field that always comes from upstream.

No zone or net in the 'To' address (Firstname Lastname, Zone:Net/Node) in TIC /var/spool/ftn/inb/XXnnnnnn.TIC

If I read your message correctly...

Your upstream is sending you a file with a corresponding TIC file?

But in said TIC file, the "To" is blank?

Isnt the question then of your upstream, why is his system sending you a TIC file with no "To" value? (Clearly his system knows the TIC file is too you, since its placed in a location that results in your mailer picking it up).


...δεσ∩
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hi deon,

Not quite, when I look into the TIC file, I see the following entry as described

Area Blah
Origin Zone:Net/Node
From Zone:Net/Node
To Alisha Stutz, Zone:Net/Node
File Payload.ext
Replaces Payload.ext
...
...
...

To me it looks like it was requested, because I requested it via Filefix a
few days ago. But just the header information looks wrong to me. That's why I ask how I can fix this condition so that correct information is contained in the "To".

Greetings

Alisha
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)

Hi deon,

Not quite, when I look into the TIC file, I see the following entry as described

Area Blah
Origin Zone:Net/Node
From Zone:Net/Node
To Alisha Stutz, Zone:Net/Node
File Payload.ext
Replaces Payload.ext

That looks like an "advanced" tic file.

Can your link adjust that to a normal tic file with just zone:net/node?

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Alan,

That looks like an "advanced" tic file.

Can your link adjust that to a normal tic file with just zone:net/node?

I have already tried to clarify a lot with him via email, but he says he
can't do anything. He also uses a special software as a tosser, "Internet Rex V2.29", which I don't think is the latest version. However, his statement is that the error must be with me, because all other peers with MysticBBS have
the same problem.

He sent me his entire config of "Internet Rex" because it contains all binary data and it is not possible to check whether I am entered incorrectly or what the problem is exactly.

That's why I'm looking for someone who can help me with this somewhat
outdated setup.

Greetings

Alisha
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)

He sent me his entire config of "Internet Rex" because it contains all binary data and it is not possible to check whether I am entered incorrectly or what the problem is exactly.

Yes, it can be a challenge for nodes to get working together as expected.

That's why I'm looking for someone who can help me with this somewhat outdated setup.

I have not used internet rex for many years but I don't recall it having the capability to toss files or create tics. I could be wrong.

I think the issue resides with the file tosser config. Allfix, htick or perhaps something else altogether.

When working with an MBSE setup I am able to select normal or advanced tic files with the Filemgr. I use the normal variety with my BBBS setup.

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alisha!

17 Jan 22, Alisha Stutz wrote to deon:

Not quite, when I look into the TIC file,
I see the following entry as described

Area Blah
Origin Zone:Net/Node
From Zone:Net/Node
To Alisha Stutz, Zone:Net/Node

Your report was:
No zone or net in the 'To' address (Firstname Lastname, Zone:Net/Node) in TIC /var/spool/ftn/inb/XXnnnnnn.TIC

Now there is a zone and net in the to address. Isn't it?

Whatever this guy told you, the only qualified source for the tic files used in Fidonet can be found in the FTSC file echo. With a quick search i found fsc-0087.001:

+++++++++++++++++++++++
Format of a TIC file:

Addressing:
*In* a tic file any form of FTN address representation from 3d to
FQFA may be used. All File Forwarders must understand the
following formats:
zone:net/node - 3D
zone:net/node.point - 4D
zone:net/node@ftn - 5D - point 0 assumed
zone:net/node.point@ftn - 5D
ftn#zone:net/node.point - fqfa

File Forwarders should have configurable options per site as to the
type of addressing each of it's downlinks can understand. ++++++++++++++++++++++

Imho it's his responsibility to deliver TIC files you can understand.

As for single file request from-to a file area the only relevant "to" information is the aka and the name of the file area. The user name is not required and could be considered as data pollution.

On the other hand: If that's not a Fidonet zone the best practice fidonet agreements do not apply and you are on your own. Try to switch to a link that does send you correct tics.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

On 2022 Jan 19 17:44:30, you wrote to Alisha Stutz:

Whatever this guy told you, the only qualified source for the tic files used in Fidonet can be found in the FTSC file echo. With a quick search i found fsc-0087.001:

that's a very old proposal... it isn't found on the FTSC web site... not even in the old docs directory... i do have it here in my ancient archives, though...

although, the better document to use would be the published standard ;)

fts-5006.001 2016-11-07
TIC file format.
http://ftsc.org/docs/fts-5006.001

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... [ ] Free Country [ ] Drug Free Country Choose One.
---
* Origin: (1:3634/12.73)

Hello Alisha,

Monday January 17 2022, Alisha Stutz wrote to deon:

Not quite, when I look into the TIC file, I see the following entry as described

Area Blah
Origin Zone:Net/Node
From Zone:Net/Node
To Alisha Stutz, Zone:Net/Node
File Payload.ext
Replaces Payload.ext

I updated htick to recognize this format of the "To" field of a TIC file. Please try it.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Moscow, Russia (2:5020/1042)

Hello mark!

20 Jan 22, mark lewis wrote to Kai Richter:

Whatever this guy told you, the only qualified source for the tic
files used in Fidonet can be found in the FTSC file echo. With a
quick search i found fsc-0087.001:

that's a very old proposal...

Thanks for the pointer... My ftsc area stamped april 2021 and the file should be there? I'll check that later. As written i did a quick search (and stopped at the first hit).

although, the better document to use would be the published standard
;)

Well, at least i'd prove it's better to use the "official" docs. Next time i should expand the "use originals" to "use latest originals". :-|

fts-5006.001 2016-11-07

But for this case i think the old file is far more explaining. The example for the to line misses the zone number while other lines do have a zone number.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Michael!

20 Jan 22, Michael Dukelsky wrote to Alisha Stutz:

To Alisha Stutz, Zone:Net/Node

I updated htick to recognize this format of the "To" field of a TIC
file.

allow the so-called "advanced" TIC file format

From my point of view i am lost in translation of social communication components. Alan said it "looks like" and uses "advanced" in "". This is sometimes used to downgrade the word if someone knows that it is not really true.

Don't get me wrong, i love it that you did a quick workaround to keep htick up and running! On the other hand we do support a new tic "advanced standard" that was none before. Those software that use that truly non-standard tic format does not have a reason to change. As a result husky users do not have a problem but the rest of the tick software that does not receive an update have to work around broken tic files.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Friday January 21 2022, Kai Richter wrote to Michael Dukelsky:

To Alisha Stutz, Zone:Net/Node

I updated htick to recognize this format of the "To" field of a
TIC file.

allow the so-called "advanced" TIC file format

From my point of view i am lost in translation of social communication components. Alan said it "looks like" and uses "advanced" in "". This
is sometimes used to downgrade the word if someone knows that it is
not really true.

That is why I wrote "the so-called" and put the word "advanced" in quotes.

Don't get me wrong, i love it that you did a quick workaround to keep htick up and running! On the other hand we do support a new tic
"advanced standard" that was none before.

Nobody said it was a standard.

Those software that use that
truly non-standard tic format does not have a reason to change.

The program using the non-standard TIC files is "Internet Rex". It has been an abandonware for a long time and there is no chance anything may change in it.

As a
result husky users do not have a problem but the rest of the tick
software that does not receive an update have to work around broken
tic files.

Internet Rex will not receive an update and the sysop using it does not want to replace it if I understand it correctly.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Moscow, Russia (2:5020/1042)

On 2022 Jan 23 13:05:54, you wrote to Kai Richter:

Those software that use that truly non-standard tic format does not
have a reason to change.

The program using the non-standard TIC files is "Internet Rex". It has been an abandonware for a long time and there is no chance anything
may change in it.

Allfix v5.xx has "Advanced TIC"... i had a system link up with my system recently and it was sending them... they weren't a problem but i still took the opportunity to talk to their allfix and turn them off...

from the Allfix v5.13 docs:
[...]
Route via

This field contains the address of the system through which
all files and messages for system this should be routed. If
this field is used, then the TIC file mode MUST be set to
"Advanced TIC file". ALLFIX will add one extra field to the
.TIC file, so that the nodes through which any files for this
system are routed know that the files are not for them.
Furthermore, ALLFIX will send the files to the system
specified in this field. That system will have to make sure
that the files are then sent to the correct destination
system.

[...]
Advanced TIC file

Include an advanced .TIC file. The advanced .TIC files
contain the "AreaDesc" verb, the "To" verb, the "Cost"
verb (not yet used by ALLFIX), and the "Ldesc" verb. The
"To" verb is necessary for routing files via other
systems.

[...]


i knew that allfix had some sort of capability of sending TICs and files routed but i never used it and never really looked into it... of course, it also requires that all TIC processors in the path have this capability and have it enabled, too...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Souse: a food item for when scrapple is not disgusting enough.
---
* Origin: (1:3634/12.73)

Hello mark,

Sunday January 23 2022, mark lewis wrote to Michael Dukelsky:

Advanced TIC file

Include an advanced .TIC file. The advanced .TIC files
contain the "AreaDesc" verb, the "To" verb, the "Cost"
verb (not yet used by ALLFIX), and the "Ldesc" verb. The
"To" verb is necessary for routing files via other
systems.

Htick knows the following keywords: file, altfile, areadesc, area, crc, size, date, replaces, from, origin, to, destination, desc, ldesc, seenby, path, pw.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Moscow, Russia (2:5020/1042)