On 2019 Aug 19 09:29:04, you wrote to All:
Have things working but noticed every now and then a file is not processed because a CRC was expected and it didn't match. One specifically is the z1daily files and I checked it and it is good.
you should not be getting CRC mismatches on Z1DAILY files unless
1. the wrong file has been sent,
2. already exists in your inbound,
3. or has been modified since it was hatched...
(eg: bbs archive comment or ad added)
So question is this, besides manually placing the file in sbbs, is
there a way to bypass, add an exeception, etc so tickit will process
it?
there is no "skip CRC" option in tickit (at this time)... personally speaking, i wouldn't want one, either...
on archives with numerical extensions like FTN nodelists (Zxx), there can be only 100 files anyway... 00 through 65/66 will be duplicated four times a year... 66/67 through 99 will be duplicated three times a year...
eg:
00 through 99 == Z00 through Z99
100 through 199 == Z00 through Z99
200 through 299 == Z00 through Z99
300 through 365/366 == Z00 through Z65/Z66
so, chekc your inbound and remove older archives that do not have matching TIC files within some minutes of the file's time stamp...
NOTE: your mailer /may/ increment the extension number if an inbound file if a file of same name already exists in your inbound... this will certainly throw off TIC processing...
)\/(ark
Once men turned their thinking over to machines in the hope that this would set
them free. But that only permitted other men with machines to enslave them.
... A man of my spiritual intensity does not eat corpses. - G. B. Shaw
---
* Origin: (1:3634/12.73)