BBS: TELESC.NET.BR Assunto: htick "issue" De: Nick Boel Data: Mon, 27 Apr 2026 19:24:27 -0500 ----------------------------------------------------------- Hey Mike! On Mon Apr 27 2026 , you wrote: > What I am thinking is that it will move the new ones to the directory, > the old ones (that are not in all CAPS) will still be there, the new > ones will get renamed to something else (like zip.# or the like because > they will never be replaced), and the updated file listing might point > to the wrong/older file. That's not what happens. The only renaming (as in zip.#) is done by binkd in your inbound directory. htick will only rename files to *.bad, or maybe even *.sec due to security issues and/or not having a certain fileechos setup, which would also be in your inbound directory. I don't know if there's a way to make it do it, but htick has never renamed anything in my actual file echos (where they go after they are processed from your inbound). As far as I've seen, if "something.zip" is in the fileecho, and a new "something.zip" arrives via binkd with "REPLACES SOMETHING.ZIP" and htick processes it, it would replace the uppercase version (if there is one) in that directory. If there is no uppercase file named that in there, it will simply ignore the REPLACES command since there is nothing to do, and just overwrite the original "something.zip", without error. Regards, Nick ... Sarcasm: because beating people up is illegal. --- SBBSecho 3.37-Linux * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700) ----------------------------------------------------------- [Voltar]