TIC Processor
Handles FidoNet file echoes — files distributed network-wide
the same way Echomail distributes messages, but with metadata
in a separate .TIC companion file.
Flow
inbound BinkP
↓
.TIC + file land in inbox/<area>/
↓
TIC processor parses .TIC:
Area: SCENE_FILES
File: scene2026-01.zip
Desc: BBS scene news, January
Crc: 12345678
↓
File moves to data/files/<area>/ + description set
↓
File appears in /files/<area>/
Sysop config
/admin/echomail/tic/ — list of TIC areas your node carries.
For each: which local file area to drop into, who's allowed to
upload (your uplink + maybe a few peers), and whether to forward
to downlinks.
Forwarding
If you have nodes peering off you for the same TIC area, the
processor regenerates a fresh .TIC with you in the path and
queues it for outbound BinkP to each downlink.
Checksums
.TIC carries a CRC32. If the file's CRC doesn't match, the
processor moves both into bad/ and logs the mismatch. Manual
intervention required.