Digital Man wrote to Bill McGarrity <=-

@MSGID: <55EE404B.2414.2syncsyso@tequilamockingbirdonline.net>
@TZ: 41a4
Re: sbbsecho tossing issues...
By: Bill McGarrity to Digital Man on Sun Sep 06 2015 06:24 pm

Hiya Rob...

Have issue when MakeNL creates an outgoing *.MSG. Looking at the header this is what I see...

1:266/404 5 52p NetMail Folder On. Sun 6 Sep 2015 5:39p
By. MakeNL 3.4.1 24:100/1
To. Coordinator 24:10/0
Re. C:\MakeNL\net100.254
St. Local Pvt File Kill Sent ----------------------------------------------- ---------------------------------

As you can see the addressing is correct.

I'll take your word for it.

This was taken from the header of the *.MSG. As you can see sbbsecho ran FIDOOUT thus the "sent" flag.

In my sbbsecho.cfg I have all my addresses I use locally which are 24:24/0 1, 24:100/0 1

Now, when fidoout runs and converts it over to FLO, why is it saying VIA 1:266/404 and routing it to 1:261/38?

Due to the contents of your sbbsecho.cfg file.

I also have 24:10/0 1 configured as well as a downlink/uplink within sbbsecho. Do I need to add a ROUTE-TO 24:24/0 24:*

If 24:24/0 is your uplink for that network, that makes sense to me.

24:24/0 is me!

As you can see makenl is setting the outgoing address to 24:10/0

I'm at a loss here... any suggestions?

I think you're on the right track with your routing question. If you continue to have problem, the relevant contents of your sbbsecho.cfg
and areas.bbs files might be needed to determine the cause.

This has nothing to do with echomail.... it is strictly a file attach starting out as a *.MSG. Why would sbbsecho not convert the 24:10/1 into the correct binary *ut file so bick can deal with it?

Anyway, I added ROUTE-TO 24:24/0 24:ALL

Let's see what happens...

Thanks


--

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)

Re: sbbsecho tossing issues...
By: Digital Man to Bill McGarrity on Mon Sep 07 2015 18:59:41

Hiya DM....

OK... found out the answer. MakeNL has the ability to add an ITNL kludge which seems to have resolved the issue when sbbsecho tosses the *.msg to a .CUT file. In the CTL file, you musta add INTL in the SUBmit header. It's
using the correct binary address now and the segment is getting attached properly.
--

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!!
--- SBBSecho 3.02-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

mark lewis wrote to Bill McGarrity <=-

08 Sep 15 01:48, you wrote to Digital Man:

OK... found out the answer. MakeNL has the ability to add an ITNL
kludge which seems to have resolved the issue when sbbsecho tosses the *.msg to a .CUT file. In the CTL file, you musta add INTL in the
SUBmit header. It's using the correct binary address now and the
segment is getting attached properly.

that seems to indicate that sbbsecho requires the INTL control line for proper operation...

Yup... adding that is what did the trick...

Learn something new everyday... :)


--

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)