Hi there.

I've got a question that has been a thorn in my side for a few days now.

I'm set up via FTN for SportNet. I'm polling directly from 24:24/1. I am set up as 24:150/1 in SBBS, SBBSEcho, and IRex. When SBBSEcho creates a mail packet to send out, it names it 17ee0001.*. If my understanding is correct, shouldn't it be 007e0000.*?

What's happening, is 24:24/1 isn't able to open and import the messages on his end. I'm receiving mail in all areas just fine, but nothing from my system is getting past 24:24/1. I've gone through everything I can think of, and can't figure it out. Any assistance would be most appreciated.

Thanks,

Dan Richter
aka Black Panther
Sysop
Castle Rock BBS
Rio Rancho, NM

---
* Synchronet * Castle Rock BBS - Rio Rancho, NM - telnet:castlero.synchro.net
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: SBBSEcho packet naming
By: Black Panther to All on Sun Nov 20 2016 03:10 pm

Hi there.

I've got a question that has been a thorn in my side for a few days now.

I'm set up via FTN for SportNet. I'm polling directly from 24:24/1. I am set up as 24:150/1 in SBBS, SBBSEcho, and IRex. When SBBSEcho creates a mail packet to send out, it names it 17ee0001.*. If my understanding is correct, shouldn't it be 007e0000.*?

Packets (*.pkt, *.?ut filse) can actually be named anything. I think what you're referring to are bundle filenames. SBBSecho using the Binkley style of bundle naming. The key for that bundle naming is here: http://wiki.synchro.net/ref:fidonet_files#bundle

What's happening, is 24:24/1 isn't able to open and import the messages on his end. I'm receiving mail in all areas just fine, but nothing from my system is getting past 24:24/1. I've gone through everything I can think of, and can't figure it out. Any assistance would be most appreciated.

Does 24:24/1 provide you any more details on *why* they import the messages? I doubt the bundle filenaming is the issue.

digital man

Synchronet/BBS Terminology Definition #45:
SMB = Synchronet Message Base
Norco, CA WX: 62.1oF, 74.0% humidity, 11 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hiya Dan....

Black Panther wrote to All <=-

I've got a question that has been a thorn in my side for a few days
now.

I'm set up via FTN for SportNet. I'm polling directly from 24:24/1. I
am set up as 24:150/1 in SBBS, SBBSEcho, and IRex. When SBBSEcho
creates a mail packet to send out, it names it 17ee0001.*. If my understanding is correct, shouldn't it be 007e0000.*?

What's happening, is 24:24/1 isn't able to open and import the messages
on his end. I'm receiving mail in all areas just fine, but nothing from
my system is getting past 24:24/1. I've gone through everything I can think of, and can't figure it out. Any assistance would be most appreciated.

I sent you email on this. Being your running FD Attach, sbbsecho will create a *.MSG and a *.PKT. The problem is you're sending the netmail but nothing is attached. I explained it all in the email.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
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
--- SBBSecho 3.00-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Digital Man wrote to Black Panther <=-

Re: SBBSEcho packet naming
By: Black Panther to All on Sun Nov 20 2016 03:10 pm

Hi there.

I've got a question that has been a thorn in my side for a few days now.

I'm set up via FTN for SportNet. I'm polling directly from 24:24/1. I am set up as 24:150/1 in SBBS, SBBSEcho, and IRex. When SBBSEcho creates a mail packet to send out, it names it 17ee0001.*. If my understanding is correct, shouldn't it be 007e0000.*?

Packets (*.pkt, *.?ut filse) can actually be named anything. I think
what you're referring to are bundle filenames. SBBSecho using the
Binkley style of bundle naming. The key for that bundle naming is here: http://wiki.synchro.net/ref:fidonet_files#bundle

What's happening, is 24:24/1 isn't able to open and import the messages on his end. I'm receiving mail in all areas just fine, but nothing from my system is getting past 24:24/1. I've gone through everything I can think of, and can't figure it out. Any assistance would be most appreciated.

Does 24:24/1 provide you any more details on *why* they import the messages? I doubt the bundle filenaming is the issue.

He's using sbbsecho as FD/Attach rather than Binkley style.

I'm getting the *.msg but nothing is attached.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
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
--- SBBSecho 3.00-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Re: Re: SBBSEcho packet naming
By: Bill McGarrity to Digital Man on Sun Nov 20 2016 06:22 pm

Digital Man wrote to Black Panther <=-

Re: SBBSEcho packet naming
By: Black Panther to All on Sun Nov 20 2016 03:10 pm

Hi there.

I've got a question that has been a thorn in my side for a few days now.

I'm set up via FTN for SportNet. I'm polling directly from 24:24/1. I am set up as 24:150/1 in SBBS, SBBSEcho, and IRex. When SBBSEcho creates a mail packet to send out, it names it 17ee0001.*. If my understanding is correct, shouldn't it be 007e0000.*?

Packets (*.pkt, *.?ut filse) can actually be named anything. I think what you're referring to are bundle filenames. SBBSecho using the Binkley style of bundle naming. The key for that bundle naming is here: http://wiki.synchro.net/ref:fidonet_files#bundle

What's happening, is 24:24/1 isn't able to open and import the messages on his end. I'm receiving mail in all areas just fine, but nothing from my system is getting past 24:24/1. I've gone through everything I can think of, and can't figure it out. Any assistance would be most appreciated.

Does 24:24/1 provide you any more details on *why* they import the messages? I doubt the bundle filenaming is the issue.

He's using sbbsecho as FD/Attach rather than Binkley style.

I'm getting the *.msg but nothing is attached.

Oh. And what version of SBBSecho is he using?

SBBSecho v3 has *not* been tested for FD/Attach style mailers. It's almost gauranteed not to work in that configuration (and I was considering just removing FD/Attach/ArcMail support since it appeared that no one was using it). Does he *need* to use FD/Attach mode?

digital man

Synchronet/BBS Terminology Definition #21:
FF = Form Feed (ASCII 12, Ctrl-L)
Norco, CA WX: 59.9oF, 79.0% humidity, 6 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

20 Nov 16 15:10, you wrote to All:

I'm set up via FTN for SportNet. I'm polling directly from 24:24/1. I
am set up as 24:150/1 in SBBS, SBBSEcho, and IRex. When SBBSEcho
creates a mail packet to send out, it names it 17ee0001.*. If my understanding is correct, shouldn't it be 007e0000.*?

no... the filenames really don't mean anything... in some cases, like when using a BSO they /might/ mean something but they do not have to...

What's happening, is 24:24/1 isn't able to open and import the
messages on his end. I'm receiving mail in all areas just fine, but nothing from my system is getting past 24:24/1.

what are his logs reporting? without that side of the conversation, everything is just guessing and throwing darts into the wind...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... An expert on the historical significance of cottage cheese.
---
* Origin: (1:3634/12.73)

Re: Re: SBBSEcho packet naming
By: Digital Man to Bill McGarrity on Sun Nov 20 2016 15:57:52

SBBSecho v3 has *not* been tested for FD/Attach style mailers. It's almost gauranteed not to work in that configuration (and I was considering just removing FD/Attach/ArcMail support since it appeared that no one was using i Does he *need* to use FD/Attach mode?

No, I didn't need to use FD/Attach. I was just more familiar with that over anything else. I have changed it, and everything seems to be working fine now. Thank you for the assistance.

Dan Richter
aka Black Panther
Sysop
Castle Rock BBS
Rio Rancho, NM

---
* Synchronet * Castle Rock BBS - Rio Rancho, NM - telnet:castlero.synchro.net
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: Re: SBBSEcho packet naming
By: Black Panther to Digital Man on Sun Nov 20 2016 08:47 pm

Re: Re: SBBSEcho packet naming
By: Digital Man to Bill McGarrity on Sun Nov 20 2016 15:57:52

SBBSecho v3 has *not* been tested for FD/Attach style mailers. It's almost gauranteed not to work in that configuration (and I was considering just removing FD/Attach/ArcMail support since it appeared that no one was using i Does he *need* to use FD/Attach mode?

No, I didn't need to use FD/Attach. I was just more familiar with that over anything else. I have changed it, and everything seems to be working fine now. Thank you for the assistance.

What mailer are you using? What version of SBBSecho?

digital man

Synchronet "Real Fact" #23:
The third ever Synchronet BBS was The Beast's Domain (sysop: King Drafus). Norco, CA WX: 55.9oF, 94.0% humidity, 0 mph WSW wind, 0.01 inches rain/24hrs --- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)