Running latest CVS build in Windows, having issues with SBBSECHO or BinkIt, or both. I'm trying to connect to my Fido node and my Events log is spitting out:
8/7 06:52:35p No inbound configured in sbbsecho! Leaving inseucre file as 'C:\SBBS\temp\event\00000064.SA0'.
8/7 06:52:36p No inbound configured in sbbsecho! Leaving inseucre file as 'C:\SBBS\temp\event\0000ffe7.SU0'.
inbound = c:\fido\_IN\
outbound = C:\Fido\_OUT\
TempDirectory = ../temp/sbbsecho
SBBSECHO seems be leaving stuff in the temp folder. What am I missing here?
Running latest CVS build in Windows, having issues with SBBSECHO or BinkIt, or both. I'm trying to connect to my Fido node and my Events log is spitting out:
8/7 06:52:35p No inbound configured in sbbsecho! Leaving inseucre file as 'C:\SBBS\temp\event\00000064.SA0'.
8/7 06:52:36p No inbound configured in sbbsecho! Leaving inseucre file as 'C:\SBBS\temp\event\0000ffe7.SU0'.
Not sure why this is happening, it was working ok recently. Here's some relvant info from sbbsecho.ini if it's needed:
CheckPathsForDupes = true
KillEmptyNetmail = false
AreaAddFromEcholistsOnly = false
SecureEchomail = true
BinkleyStyleOutbound = true
TruncateBundles = false
FuzzyNetmailZones = true
StripLineFeeds = false
ConvertTearLines = false
SysopAliasList = SYSOP
ZoneBlind = false
LogLevel = Informational
SecureInbound = c:\fido\_inSEC\
BundleSize = 2000K
areafile = ../data/areas.bbs
logfile = c:\fido\_log\sbbsecho.log
inbound = c:\fido\_IN\
outbound = C:\Fido\_OUT\
TempDirectory = ../temp/sbbsecho
PacketSize = 250K
ZoneBlindThreshold = 65535
StrictPacketPasswords = true
EchomailNotify = true
BsyTimeout = 12H
BsoLockDelay = 10S
BsoLockAttempts = 60
MaxEchomailAge = 60D
MaxNetmailAge = 0Y
IgnoreNetmailDestAddr = false
IgnoreNetmailRecvAttr = false
IgnoreNetmailLocalAttr = false
DefaultRecipient =
UseFTNDomains = false
[node:1:218/700]
Comment =
AreafixPwd = HITHERE (NOT!)
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = true
Notify = false
Keys =
Status = Normal
SBBSECHO seems be leaving stuff in the temp folder. What am I missing here?
You apparently have an inbound directory, so I'm not sure what's up with that BinkIT error. Is it possible you still have an old sbbsecho.cfg file in your CTRL directory?
Leaving what stuff in what directory? Everything SBBSecho does is (supposed to be at least) logged to your data/sbbsecho.log file. Have you checked that for clues?
[node:1:218/700]
Comment =
AreafixPwd = HITHERE (NOT!)
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = true
Notify = false
Keys =
Status = Normal
maybe you need to fill out this (path name) :
Inbox =
Outbox =
[node:1:218/700]
Comment =
AreafixPwd = HITHERE (NOT!)
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = true
Notify = false
Keys =
Status = Normal
maybe you need to fill out this (path name) :
Inbox =
Outbox =
sbbsecho config program says those lines are for in/out filebox directory. Suggestions for what to enter here since I'm not sure where this config file is documented?
Re: Re: SBBSEcho errors.
By: Lord Time to Android8675 on Sun Aug 07 2016 10:14 pm
[node:1:218/700]
Comment =
AreafixPwd = HITHERE (NOT!)
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = true
Notify = false
Keys =
Status = Normal
maybe you need to fill out this (path name) :
Inbox =
Outbox =
sbbsecho config program says those lines are for in/out filebox directory.
Suggestions for what to enter here since I'm not sure where this config file is documented?
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 214:29:24 |
Calls: | 14,143 |
Calls today: | 1 |
Files: | 295 |
Messages: | 551,118 |