Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and have a prefix of something like ".._echomail_out.13c0000fff3.FR0". Why are the filenames renamed using the directory name and the packets hidden?
---

Sincerely,
Jon Justvig
Raiders Inc BBS
WHQ Whisper-Echo-Net & Legion RPG
telnet://vintgebbsing.com
http://bbs.vintagebbsing.com
---
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Jon Justvig wrote to All on 08-03-18 19:50 <=-

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and
have a prefix of something like ".._echomail_out.13c0000fff3.FR0". Why are the filenames renamed using the directory name and the packets
hidden? ---

What's your binkd.cfg say about folders and where incoming go to. I am almost positive binkd is responsible for putting incoming files in the correct folder.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

... Bill McGarrity scribbled to Jon Justvig in the sand ...

Jon Justvig wrote to All on 08-03-18 19:50 <=-

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and
have a prefix of something like ".._echomail_out.13c0000fff3.FR0". Why are the filenames renamed using the directory name and the packets
hidden? ---

What's your binkd.cfg say about folders and where incoming go to. I am almost positive binkd is responsible for putting incoming files in the correct folder.

inbound /sbbs/echomail/insec
inbound-nonsecure /sbbs/echomail/in

This is the first time this has happened to me in the years I've used BinkD. Why is it renaming my packets with the prefix of my pathnames and hiding
the files?

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: echomail
By: Bill McGarrity to Jon Justvig on Sat Aug 04 2018 09:17 am

".._echomail_out.13c0000fff3.FR0". Why are the filenames renamed

What's your binkd.cfg say about folders and where incoming go to. I am almost positive binkd is responsible for putting incoming files in the correct folder.

Looks like what my uplink is calling this file (being I am the uplink for my new SBBS/BinkD for Linux.) I am curious to know if it's the version of zip or unzip I am running on both systems and the compression parameters for those two proggies. Something is diffently messed up here. I haven't, to my knowledge or remeberance have I made changes to my compression configuration for SBBS (Win32). Also, SBBS (Linux) is brand new as of Aug 2, 2018 and my SBBS Win32 is May 21, 2018. Maybe I need to upgrade?
---

Sincerely,
Jon Justvig
Raiders Inc BBS
WHQ Whisper-Echo-Net & Legion RPG
telnet://vintgebbsing.com
http://bbs.vintagebbsing.com
---
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 08-04-18 09:17, Bill McGarrity wrote to Jon Justvig <=-

What's your binkd.cfg say about folders and where incoming go to. I am almost positive binkd is responsible for putting incoming files in the correct folder.

For incoming files, yes, binkd has to be told to place them in the correct folder. And for outbound, SBBSecho, does the work. Both have to agree on the same places to store things (i.e. by configuring them appropriately), or nothing will work. :)


... Real Programmers do List Processing in FORTRAN.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

... Tony Langdon scribbled to Bill McGarrity in the sand ...

On 08-04-18 09:17, Bill McGarrity wrote to Jon Justvig <=-

What's your binkd.cfg say about folders and where incoming go to. I am almost positive binkd is responsible for putting incoming files in the correct folder.

For incoming files, yes, binkd has to be told to place them in the
correct folder. And for outbound, SBBSecho, does the work. Both have
to agree on the same places to store things (i.e. by configuring them appropriately), or nothing will work. :)

I could swear they are identical, yet the packets still get renamed. I am
even going by a similar BinkD configuration file I used in the past. I am
also curious to know what changes were made in SBBS that might cause this.
I haven't quite nailed it yet. I am thinking of trying BinkIt to see if
the same issue happens and if it does, I will know for sure it is SBBS, if
it isn't then I know it's BinkD. I'll keep tinkering with it and see what
I can come up with. Right now, I run even as FIDOIN as a script to remove
the prefix .. (the part of the file name that Linux reads as to make the
file hidden, unknown to SBBSEcho).

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 08-06-18 02:04, Jon Justvig wrote to Tony Langdon <=-

I could swear they are identical, yet the packets still get renamed. I
am even going by a similar BinkD configuration file I used in the past.
I am also curious to know what changes were made in SBBS that might

Definitely something weird going on. :)


... To a little kid all troubles are big.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Re: echomail
By: Jon Justvig to All on Fri Aug 03 2018 07:50 pm

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and have a prefix of something like ".._echomail_out.13c0000fff3.FR0".

That sounds like a BinkD configuration issue - maybe single back-slashes used in your binkd.cfg file? Either change to use forward-slashes or double-back-slahses.

Why are the
filenames renamed using the directory name and the packets hidden?

Filenames beginnnig with a '.' are "hidden" on *nix systems. What OS are you running? Anyway, it doesn't sound like a Synchronet issue.

digital man

This Is Spinal Tap quote #23:
David St. Hubbins: I envy us.
Norco, CA WX: 90.8oF, 37.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: echomail
By: Jon Justvig to Tony Langdon on Mon Aug 06 2018 02:04 am

even going by a similar BinkD configuration file I used in the past.

If it was used on Windows and you're not using it on Linux, that would explain it.

I am
also curious to know what changes were made in SBBS that might cause this.

None.

digital man

Synchronet/BBS Terminology Definition #46:
SEXYZ = Synchronet External X/Y/ZMODEM file transfer protocol driver
Norco, CA WX: 94.8oF, 31.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

... Digital Man scribbled to Jon Justvig in the sand ...

Re: echomail
By: Jon Justvig to All on Fri Aug 03 2018 07:50 pm

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and have a prefix of something like ".._echomail_out.13c0000fff3.FR0".

That sounds like a BinkD configuration issue - maybe single
back-slashes used in your binkd.cfg file? Either change to use forward-slashes or double-back-slahses.

Single backslashes are used:

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

Why are the
filenames renamed using the directory name and the packets hidden?

Filenames beginnnig with a '.' are "hidden" on *nix systems. What OS
are you running? Anyway, it doesn't sound like a Synchronet issue.

That I figured out already, thus, giving me an idea to create a script
to take out the '.' in front of the filename. My BinkD is Linux and my
uplink is Win32.

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

... Digital Man scribbled to Jon Justvig in the sand ...

Re: Re: echomail
By: Jon Justvig to Tony Langdon on Mon Aug 06 2018 02:04 am

even going by a similar BinkD configuration file I used in the past.

If it was used on Windows and you're not using it on Linux, that would explain it.

I used a similar BinkD configuration I recently had on Linux on my new
Linux VM.

I am
also curious to know what changes were made in SBBS that might cause this.

None.

I don't have a clue to what I did differently this time around. Everything looks okay on both my BinkD server and my Win32 SBBSEcho/Taurus.

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: echomail
By: Jon Justvig to Digital Man on Mon Aug 06 2018 04:28 pm

... Digital Man scribbled to Jon Justvig in the sand ...

Re: echomail
By: Jon Justvig to All on Fri Aug 03 2018 07:50 pm

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and have a prefix of something like ".._echomail_out.13c0000fff3.FR0".

That sounds like a BinkD configuration issue - maybe single back-slashes used in your binkd.cfg file? Either change to use forward-slashes or double-back-slahses.

Single backslashes are used:

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

But those look like forward-slashes to me.

Also, those are outbound directories. I think you were having problems with received (inbound) files. No?

What about all the *other* pathnames specified in your binkd.cfg file?

Why are the
filenames renamed using the directory name and the packets hidden?

Filenames beginnnig with a '.' are "hidden" on *nix systems. What OS are you running? Anyway, it doesn't sound like a Synchronet issue.

That I figured out already, thus, giving me an idea to create a script
to take out the '.' in front of the filename. My BinkD is Linux and my uplink is Win32.

Have you already shared the binkd log output with us? Is it possible your uplink is sending you corrupted filenames?

digital man

This Is Spinal Tap quote #35:
Jeanine Pettibone: You don't do heavy metal in Dubly, you know.
Norco, CA WX: 93.6oF, 27.0% humidity, 8 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: echomail
By: Jon Justvig to Digital Man on Mon Aug 06 2018 04:28 pm

Single backslashes are used:

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

Those are forward slashes.

Nightfox

---
* Synchronet * Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2018 Aug 06 16:28:00, you wrote to Digital Man:

That sounds like a BinkD configuration issue - maybe single
back-slashes used in your binkd.cfg file? Either change to use
forward-slashes or double-back-slahses.

Single backslashes are used:

backslashes lean back to the left ;)

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

[...]

That I figured out already, thus, giving me an idea to create a script
to take out the '.' in front of the filename. My BinkD is Linux and my uplink is Win32.

you should not have to rename anything... are you using FTRANS in your binkd to
try to map linux paths into DOS paths??

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... You can't list hound dogs as dependants on your tax forms.
---
* Origin: (1:3634/12.73)

... Digital Man scribbled to Jon Justvig in the sand ...

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and have a prefix of something like ".._echomail_out.13c0000fff3.FR0".

That sounds like a BinkD configuration issue - maybe single back-slashes used in your binkd.cfg file? Either change to use forward-slashes or double-back-slahses.

Single backslashes are used:

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

But those look like forward-slashes to me.

You're right.

Also, those are outbound directories. I think you were having problems with received (inbound) files. No?

Inbound, correct.

What about all the *other* pathnames specified in your binkd.cfg file?

inbound /sbbs/echomail/insec
inbound-nonsecure /sbbs/echomail/in

Why are the
filenames renamed using the directory name and the packets hidden?

Filenames beginnnig with a '.' are "hidden" on *nix systems. What OS are you running? Anyway, it doesn't sound like a Synchronet issue.

That I figured out already, thus, giving me an idea to create a script
to take out the '.' in front of the filename. My BinkD is Linux and my uplink is Win32.

Have you already shared the binkd log output with us? Is it possible
your uplink is sending you corrupted filenames?

Yeah, their coming from my other system and the other systems process the
files fine and haven't seen any renaming of files on them. So... *shrug*

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

... Nightfox scribbled to Jon Justvig in the sand ...

Re: Re: echomail
By: Jon Justvig to Digital Man on Mon Aug 06 2018 04:28 pm

Single backslashes are used:

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

Those are forward slashes.

Thanks.

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

... mark lewis scribbled to Jon Justvig in the sand ...

On 2018 Aug 06 16:28:00, you wrote to Digital Man:

That sounds like a BinkD configuration issue - maybe single
back-slashes used in your binkd.cfg file? Either change to use
forward-slashes or double-back-slahses.

Single backslashes are used:

backslashes lean back to the left ;)

LOL.

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

[...]

That I figured out already, thus, giving me an idea to create a script
to take out the '.' in front of the filename. My BinkD is Linux and my uplink is Win32.

you should not have to rename anything... are you using FTRANS in your binkd to
try to map linux paths into DOS paths??

No, I have FTRAN commented with a #.

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: echomail
By: Jon Justvig to Digital Man on Tue Aug 07 2018 10:17 pm

... Digital Man scribbled to Jon Justvig in the sand ...

Hi all... I have a situation with my newly fresh SBBS install. When downloading a packet with binkd, the incoming files become hidden and have a prefix of something like ".._echomail_out.13c0000fff3.FR0".

That sounds like a BinkD configuration issue - maybe single back-slashes used in your binkd.cfg file? Either change to use forward-slashes or double-back-slahses.

Single backslashes are used:

domain fidonet /sbbs/echomail/out 1
domain whispnet /sbbs/echomail/out 1
domain league10 /sbbs/echomail/out 1

But those look like forward-slashes to me.

You're right.

Also, those are outbound directories. I think you were having problems with received (inbound) files. No?

Inbound, correct.

What about all the *other* pathnames specified in your binkd.cfg file?

inbound /sbbs/echomail/insec
inbound-nonsecure /sbbs/echomail/in

Why are the
filenames renamed using the directory name and the packets hidden?

Filenames beginnnig with a '.' are "hidden" on *nix systems. What OS are you running? Anyway, it doesn't sound like a Synchronet issue.

That I figured out already, thus, giving me an idea to create a script
to take out the '.' in front of the filename. My BinkD is Linux and my uplink is Win32.

Have you already shared the binkd log output with us? Is it possible your uplink is sending you corrupted filenames?

Yeah, their coming from my other system and the other systems process the files fine and haven't seen any renaming of files on them. So... *shrug*

And do you have binkd.log output to share? If binkd is receiving filenames that are corrupted, then the problem is on the sending (remote) side.

digital man

Synchronet "Real Fact" #37:
Synchronet's Windows Control Panel is built with Borland C++ Builder.
Norco, CA WX: 82.4oF, 45.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

... Digital Man scribbled to Jon Justvig in the sand ...

Re: Re: echomail
By: Jon Justvig to Digital Man on Tue Aug 07 2018 10:17 pm

... Digital Man scribbled to Jon Justvig in the sand ...

And do you have binkd.log output to share? If binkd is receiving
filenames that are corrupted, then the problem is on the sending
(remote) side.

I doubt the filenames are corrupt. I create fileboxes for both
Taurus and SBBSEcho and that seemed to do the trick.

--- MultiMail/Win v0.51
* Synchronet * Stepping Stone BBS - vintagebbsing.com:2325
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)