Some of you who are recepients of file echos may have noticed some problems with a number of files released in the AFTNBINKD file echo, namely:

File: binkd101-mingw32.zip (97kB), Area: AFTNBINKD, Origin: 2:463/68 File: binkd101-mingw32-ipv6.zip (97kB), Area: AFTNBINKD, Origin: 2:463/68 File: binkd1.1a27-msvc-x64-ipv6.zip (107kB), Area: AFTNBINKD, File: binkd101-binkd2e-zlib-bzlib-bwlim.zip (125kB), Area: AFTNBINKD, File: binkd101-mingw32-ipv6-perldl.zip (556kB), Area: AFTNBINKD, File: binkd101-binkd2e-zlib-bzlib-perl-bwlim.zip (451kB), Area: AFTNBINKD, File: binkd1.1a27-mingw32-ipv6-perldl.zip (559kB), Area: AFTNBINKD, File: binkd2e-0.9.11.zip (59kB), Area: AFTNBINKD, Origin: 2:463/68 File: binkd-0.9.11-msvc6-dll.zip (65kB), Area: AFTNBINKD, File: binkd101-binkd2e-bwlim.zip (74kB), Area: AFTNBINKD, File: binkd101-msvc6-ipv6-perl.zip (549kB), Area: AFTNBINKD, File: binkd9x-0.9.11.zip
(101kB), Area: AFTNBINKD, Origin: 2:463/68 File: binkd1.1a27-binkd2e-bwlim.zip (77kB), Area: AFTNBINKD, File: binkd101-msvc10x32-ipv6.zip (90kB), Area: AFTNBINKD, File: binkd-0.9.11-msvc6.zip (100kB), Area: AFTNBINKD, File: binkd1.1a27-msvc-ipv6-perl.zip (552kB), Area: AFTNBINKD, File: binkd101-msvc10x32-ipv6-static.zip (143kB), File: binkd1.1a27-msvc-ipv6.zip (88kB), Area: AFTNBINKD, File: binkd101-msvc6-binkd9x.zip (83kB), Area: AFTNBINKD, File: binkd101-msvc10x64-ipv6.zip (103kB), Area: AFTNBINKD, File: binkd-0.9.11-mingw.zip (68kB), Area: AFTNBINKD,

Or perhaps you never even saw these files come in on June 29th since your uplink's software couldn't toss them.. (not many but some have reported this to
me).

These overly-long filenames caused some folks problems, so gert andersen is rehatching the files with standard 8X3 file names.

Some in the FTSC-PUBLIC echo (the BinkD maintainers) don't think this is an issue. I do. <g>

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)

On Wed, 03 Jul 2013, Janis Kracht wrote to All:

Or perhaps you never even saw these files come in on June 29th
since your uplink's software couldn't toss them.. (not many but
some have reported this to me).

i don't know if i saw them or not... i would have to look... they would not be moved by my processing, in any case, since my processing is 8.3 based...

These overly-long filenames caused some folks problems, so gert
andersen is rehatching the files with standard 8X3 file names.

ahhh... that's why i have finally seen some traffic in there the last few days...

Some in the FTSC-PUBLIC echo (the BinkD maintainers) don't think
this is an issue. I do. <g>

it is definitely an issue but there is supposedly a method whereby both the LFN
and the 8.3 can be specified and used by the mailers and tic tossers... i forget the details, though... it has been so long since we worked on any of that in frontdoor...

)\/(ark

--- FMail/Win32 1.60
* Origin: (1:3634/12.71)

Hi Mark,

Or perhaps you never even saw these files come in on June 29th
since your uplink's software couldn't toss them.. (not many but
some have reported this to me).

i don't know if i saw them or not... i would have to look... they would not be
moved by my processing, in any case, since my processing is 8.3 based...

I saw your post with the bad tic files list in ftsc_public.. this is what I suspected would happen for a number of people.

These overly-long filenames caused some folks problems, so gert
andersen is rehatching the files with standard 8X3 file names.

ahhh... that's why i have finally seen some traffic in there the last few days...

Yes (thanks Gert!)

Some in the FTSC-PUBLIC echo (the BinkD maintainers) don't think
this is an issue. I do. <g>

it is definitely an issue but there is supposedly a method whereby both the LF
and the 8.3 can be specified and used by the mailers and tic tossers... i forget the details, though... it has been so long since we worked on any of that in frontdoor...

Over here, BBBS just passed the files on with no regard to file name length or who was getting the file. Some of my Downlinks let me know it didn't work that
well for them :( Talk about bad tics.. :(

Also, as I mentioned in ftsc_public, when I tried to manually send a file attach of one of the failed files to one of my downlinks, BBBS didn't have enough space in Subj: line for the filename and the path to the file (/home/ftp/pub/r50/aftnbinkd/binkd1.1a27-binkd2e-zlib-bzlib-p )
^
|
This is where it clipped the Subj: line.

Anyway, we need 8X3 filenames. No doubt in my mind. I haven't asked Kim Heino
about extending the Subj: line.. I'd bet it would be a pia. He may have left room in that particular structure, but I don't know.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)