Ian Segers wrote to All <=-
Hello All
Just testing my echomail setting fron 1st Choice Core NZ
Thank you
Ian Segers
telnet 1stchoicecore.co.nz
--- SBBSecho 2.27-Win32
* Origin: 1st Choice Core Nz (3:770/330)
Ian Segers wrote to Bill McGarrity <=-
Ian Segers wrote to All <=-
Hello All
Just testing my echomail setting fron 1st Choice Core NZ
Thank you
Ian Segers
telnet 1stchoicecore.co.nz
--- SBBSecho 2.27-Win32
* Origin: 1st Choice Core Nz (3:770/330)
OK... you have it working!!
uumm sort of
X-FTN-AREA SYNC_SYSOPS
X-FTN-MSGID 219.fidonet_syncsyso@3:770/330 1b37a06b xxxxx
same how got to get to time.synchro.net ??
X-FTN-PID Synchronet 3.16c-Win32 Aug 14 2015 MSC 1800
X-FTN-TID SBBSecho 2.27-Win32 r1.261 Aug 14 2015 MSC 1800 X-FTN-SEEN-BY 11/201 14/5 19/33 34/999 90/1 116/18 120/331 123/500 128/187 3
8/389
X-FTN-SEEN-BY 138/393 140/1 218/700 226/50 230/150 240/1120 249/303 261/38 0
0
X-FTN-SEEN-BY 266/404 267/155 282/1056 292/907 908 298/25 300/5 6 320/219 40
/0 10
X-FTN-SEEN-BY 340/100 101 200 400 700 800 393/68 396/45 712/848
801/161 X-FTN-PATH 340/400 261/38
You may want to update to the latest sbbbsecho though. It's now up to 2.33. You can get the latest dev at:
ftp://vert.synchro.net/synchronet
filename: sbbs_dev.zip
I had a look in that file isn't 3.17 version I am 3.16c at the moment
but then again I my have looked in wrong file :)
Ian Segers wrote to All <=-
Hello All
Just another test sorry from 1st Choice Core NZ
Ian
--- SBBSecho 2.27-Win32
* Origin: 1st Choice Core Nz (3:770/330)
Sneaky wrote to Bill McGarrity <=-
Bill McGarrity
Ian Segers wrote to All <=-
Ian
--- SBBSecho 2.27-Win32
* Origin: 1st Choice Core Nz (3:770/330)
Got it but there is a slight issue. Your address is not showing in
either the PATH or SEEN-BYs.
X-FTN-AREA SYNC_SYSOPS
X-FTN-MSGID 252.fidonet_syncsyso@3:770/330 1b390371
X-FTN-PID Synchronet 3.16c-Win32 Aug 14 2015 MSC 1800
X-FTN-TID SBBSecho 2.27-Win32 r1.261 Aug 14 2015 MSC 1800 X-FTN-SEEN-BY 11/201 14/5 19/33 34/999 90/1 116/18 120/331 123/500 128/187 3
8/389
X-FTN-SEEN-BY 138/393 140/1 218/700 226/50 230/150 240/1120 249/303 261/38 0
0
X-FTN-SEEN-BY 266/404 267/155 282/1056 292/907 908 298/25 300/5 6 320/219 40
/0 10
X-FTN-SEEN-BY 340/100 101 200 400 700 800 393/68 396/45 712/848
801/161 X-FTN-PATH 340/400 261/38
As you can see there is no 770/330 in either.
In you sub areas under Network Options, check to see if you have your address in the Fidonet Address field.
Yes I have 3:770/330 in sbbs config/networks/fidonet echomail and network\system address
and in fidonet message groups\message sub-board\sync sysops\network address
in irex hubs node outbound config deafault domain I have
3:770/330@fidonet and I am now
using fd2ftp after the sbbsecho command to sent pkts via irex and seem
to be going to the right
inbound dir on my hub. but as you have pointed out I have seen-by
problem 1 more thing to fix.
Thank you for your help
Ian Segers wrote to Bill McGarrity <=-
Re: Re: Testing
By: Bill McGarrity to Sneaky on Wed Mar 02 2016 02:06:00
Sneaky wrote to Bill McGarrity <=-
Hello Bill
First test for seem-by and path
mark lewis wrote to Bill McGarrity <=-
02 Mar 16 21:17, you wrote to Ian Segers:
X-FTN-PATH 340/400 200 280/464 203/0
Better discuss this with Rob...
don't forget that some FTN tosser are hardcoded to strip seenbys when crossing zone boundaries in fidonet... what i seen in the PATH looks ok other than the OP's address not being listed but they are appearing in
the seenbys with other systems from that zone... that seems to indicate
that seenby stripping is not happening when the message crosses the
zone boundary in fidonet...
Ian Segers wrote to Bill McGarrity <=-
@MSGID: <56D8A4F4.3578.2syncsyso@tequilamockingbirdonline.net>
@TZ: 02d0
Bill McGarrity
X-FTN-SEEN-BY 320/119 340/0 10 100 101 200 400 700 800 423/81 120 712/848 70
/1
X-FTN-PATH 340/400 200 280/464 203/0
Better discuss this with Rob...
Did have bit of a chat about it but no.
But ie
Yes I did see this :-
don't forget that some FTN tosser are hardcoded to strip seenbys when crossing zone boundaries in fidonet... what i seen in the PATH looks ok other than the OP's address not being listed but they are appearing in
the seenbys with other systems from that zone... that seems to indicate
That's true. Never thought to ask if he has in sbbsecho.cfg the zone_blind 4 entry... but it works perfectly in the other network where both PATH and SEEN-BYs show up. It's only Fido where he has the issue.
In sbbsecho.cfg in toggle options I enabled zone blind seen-by and path lines. I take it that is were I was meant to go to do that.
Pkt ie :-
6 08:59:59.All.Ian Segers.test.AREA:SYNC_SYSOPS..TZUTC: 1200..MSGID: 04.fidone
t_syncsyso@3:770/330 1b3dceef..PID: Synchronet 3.16c-Win32 Aug 14 2015 MSC 800
..TID: SBBSecho 2.27-Win32 r1.261 Aug 14 2015 MSC 1800.asxasxasx..sx..xss..---
BBSecho 2.27-Win32. * Origin: 1st Choice Core Nz (3:770/330).SEEN-BY: 340/400 7
0/330 10/116 64/1..PATH: 770/330....
If so thank you
Ian Segers wrote to Bill McGarrity <=-
Re: Re: Testing
By: Bill McGarrity to Ian Segers on Fri Mar 04 2016 19:16:00
Hello Bill,
This is a test to see how my seen-by/path/zone_blind 4
if working or not
Ian Segers wrote to Bill McGarrity <=-
Perfect!!
X-FTN-AREA SYNC_SYSOPS
X-FTN-MSGID 310.fidonet_syncsyso@3:770/330 1b40846b
X-FTN-REPLY 3581.2syncsyso@1:266/404 1b3f6a65
X-FTN-PID Synchronet 3.16c-Win32 Aug 14 2015 MSC 1800
X-FTN-TID SBBSecho 2.27-Win32 r1.261 Aug 14 2015 MSC 1800 X-FTN-SEEN-BY 10/0 1 116 11/1 201 14/5 19/33 34/999 45/2 64/1 77/0 1 90/1 16
/18
X-FTN-SEEN-BY 120/331 123/500 128/187 138/389 393 140/0 1 2 218/700 226/50 3
0/150
X-FTN-SEEN-BY 240/1120 249/303 261/38 100 266/404 267/155 282/1056 292/907 0
8
X-FTN-SEEN-BY 298/25 300/5 6 12 320/219 340/0 10 100 101 200 400 700 800 60/
100
X-FTN-SEEN-BY 393/68 396/45 470/0 100 101 712/848 770/330 801/161 1000/3 X-FTN-PATH 770/330 340/400 261/38
^^^^^^^
Good job!!
Great this good to see that, does this mean the zone_blind 4 is fixed
as well.
Again thank you for your help to sort this out
Ian Segers wrote to Bill McGarrity <=-
Bill McGarrity
I did upgrade to v2.33 but what does this mean :-
sbbsecho 2.33-win32 rev 1.2800 march 6th msc 1800 invoke
with option /les!r and log flag 000000000
the /les!r is in my mail.bat fileso is this okay.
Sneaky wrote to Bill McGarrity <=-
On Sun, 6 Mar 2016 15:47:00 -0500, "Bill McGarrity"
<bill.mcgarrity@VERT> wrote:
Bill McGarrity
I did upgrade to v2.33 but what does this mean :-
sbbsecho 2.33-win32 rev 1.2800 march 6th msc 1800 invoke
with option /les!r and log flag 000000000
the /les!r is in my mail.bat fileso is this okay.
OK.. you need to be a tad more specific. Where did you see that? When mail
comes into the "secure" area you've told Synch, I am sure binkd creates a
semephore that triggers your mail.bat. That's when sbbsecho runs. Is the
above taken from your sbbsecho.log file while you're running in DEBUG mode?
Okay, I run Irex to get packets, when I irex finish I getting the
packet fd\inbound I run a batch file mail which has
sbbsecho /les!r
then ir run the sbbsecho to unpack mail, it apairs before proccessing
the pkts
sbbsecho 2.33-win32 rev 1.2800 march 6th msc 1800 invoke
with option /les!r and log flag 000000000
then it unpacks the mail
and it not taken from sbbsecho.log
this is sbbsecho.log
2016-03-07 08:00:56 Unpacking bundle: d:\bbs\fd\inbound\6DF6919A.MO4 2016-03-07 08:00:57 ERROR smb_addmsg returned 1: duplicate TEXT_BODY:
hash found in message #17
2016-03-07 08:00:59 SBBSecho exiting with error level 0, NetMail(0 imported, 0 exported, 0 packed), EchoMail(15 imported, 0 exported)
just not sure if to run sbbsecho with no commands
or if it okay as is with commands
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 118:32:13 |
Calls: | 8,198 |
Calls today: | 5 |
Files: | 15,442 |
Messages: | 913,460 |
Posted today: | 8 |