Hi All,
I was wondering if anyone here is running synchronet bbs version 3
for windows and using dos frontdoor. (Frontdoor 2.33 mL; Multiline) I
am looking for the exebbs.bat as well as the mailer.bat and some information how I should configure frontdoor. I also have internet
rex to transport the mail to my hub, but it can not send it if it
does not get put (tossed) into the correct directory.
BEGIN Filenames and Paths System from frontdoor
Filenames and Paths System
C:\FD\ NetMail C:\FD\MAIL\
Files C:\FD\INBOUND\
SecFiles C:\FD\INBOUND\
Packets C:\FD\PACKETS\
Log file C:\FD\FD.LOG
Banner
Nodelist C:\FD\NODELIST\
No BBS
Bad BPS
HMB files
HMB extra
JAM extra
TempPath $[TMP]
Semaphore C:\FD\SEMS\
MailExit C:\FD\SEMS\MAIL.SEM
END Filenames and Paths System
Thanks for any help in advance,
- Greg
BEGIN Filenames and Paths System from frontdoor
Filenames and Paths System
C:\FD\ NetMail C:\FD\MAIL\
Files C:\FD\INBOUND\
SecFiles C:\FD\INBOUND\
Packets C:\FD\PACKETS\
Log file C:\FD\FD.LOG
Banner
Nodelist C:\FD\NODELIST\
No BBS
Bad BPS
HMB files
HMB extra
JAM extra
TempPath $[TMP]
Semaphore C:\FD\SEMS\
MailExit C:\FD\SEMS\MAIL.SEM
END Filenames and Paths System
BEGIN Filenames and Paths System from frontdoor
Filenames and Paths System
C:\FD\ NetMail C:\FD\MAIL\
Files C:\FD\INBOUND\
SecFiles C:\FD\INBOUND\
this is not a good idea... these two should be different... secfiles
is for known secure (password protected) inbounds... the other is insecure...
BEGIN Filenames and Paths System from frontdoor
Filenames and Paths System
C:\FD\ NetMail C:\FD\MAIL\
Files C:\FD\INBOUND\
SecFiles C:\FD\INBOUND\
this is not a good idea... these two should be different... secfiles
is for known secure (password protected) inbounds... the other is insecure...
And that should be the name of the directory: INSECURE...just as a reminder of how insecure anything landing in tha directory can
be...
SecFiles C:\FD\INBOUND\
this is not a good idea... these two should be different... secfiles
is for known secure (password protected) inbounds... the other is
insecure...
And that should be the name of the directory: INSECURE...just as a
reminder of how insecure anything landing in tha directory can
be...
good point! but, sadly, not all areas can use fully spelled out
directory names... this one, however, fits perfectly into the 8.3
format! ;) :)
good point! but, sadly, not all areas can use fully spelled out
directory names... this one, however, fits perfectly into the 8.3
format! ;) :)
Kinda like putting a European echo name into FastEcho. Their
tendency to insert a . between two words doesn't always work out
like it should.
good point! but, sadly, not all areas can use fully spelled out
directory names... this one, however, fits perfectly into the 8.3
format! ;) :)
Kinda like putting a European echo name into FastEcho. Their
tendency to insert a . between two words doesn't always work out
like it should.
it works fine for echotags... however, not all software creates area
names based on the tags and not all software can handle long
filenames...
FWIW: those dots in the area names have their origination in the
usenet newsgroups formats...
the dots were seen as directory separators so there was easy
conversion... i do it here with my JAMbases but am still limited to
8.3 lengths for each of them...
eg:
alt.audio.pro X:\JAM\GRPS\ALT\AUDIO\PRO rec.audio.pro.live-sound X:\JAM\GRPS\REC\AUDIO\PRO\LIVE-SND rec.arts.movies.production.sound X:\JAM\GRPS\REC\ARTS\MOVIES\PRODUCTI.ON\SOUND
MSG areas can also easily use this style...
Kinda like putting a European echo name into FastEcho. Their
tendency to insert a . between two words doesn't always work out
like it should.
it works fine for echotags... however, not all software creates area
names based on the tags and not all software can handle long
filenames...
FE software uses self-generated numbers to define an area and
filenames, IF it's an auto-added area.
That makes it awfully hard to find which directory is which when
you're wanting to look at msgs, etc...
I use shortened names to define such directorys. Windows doesn't
mind a 20 character directory, but a DOS interface will shorten it
back to an 8.3 name and use a tild followed by a number to define
the last 9-inf.xxx names. So for convenience of the sysop sake, I
still use 8 characters for directorys and 8.3 names for files.
FWIW: those dots in the area names have their origination in the
usenet newsgroups formats...
That figures.
the dots were seen as directory separators so there was easy
conversion... i do it here with my JAMbases but am still limited to
8.3 lengths for each of them...
eg:
alt.audio.pro X:\JAM\GRPS\ALT\AUDIO\PRO rec.audio.pro.live-sound X:\JAM\GRPS\REC\AUDIO\PRO\LIVE-SND rec.arts.movies.production.sound X:\JAM\GRPS\REC\ARTS\MOVIES\PRODUCTI.ON\SOUND
I hate that alt.crap.stuff.goes.here format.
Yes, I know that 'special' characters like ~\!,#$%^&*() etc.,
don't work there.
MSG areas can also easily use this style...
I suppose. But that crap's not my style.
Kinda like putting a European echo name into FastEcho. Their
tendency to insert a . between two words doesn't always work out
like it should.
it works fine for echotags... however, not all software creates area
names based on the tags and not all software can handle long
filenames...
FE software uses self-generated numbers to define an area and
filenames, IF it's an auto-added area.
yes... that formula is FE + CRC16 of the TAG, IIRC but i'd have to go digging to confirm that...
That makes it awfully hard to find which directory is which when
you're wanting to look at msgs, etc...
which is why i always go back with the areas.bbs file and fesetup to rename and move the messages to the new area name...
yes, it is a PITA when there are several dozen to do... try it with several hundred ;)
i've done it and it takes a lot of time... especially when
one has to also reconfigure their editor (Frontdoor's FM) and their
BBS for the new areas...
I use shortened names to define such directorys. Windows doesn't
mind a 20 character directory, but a DOS interface will shorten it
back to an 8.3 name and use a tild followed by a number to define
the last 9-inf.xxx names. So for convenience of the sysop sake, I
still use 8 characters for directorys and 8.3 names for files.
as we all do who still use software that doesn't know what a long
filename is ;)
FWIW: those dots in the area names have their origination in the
usenet newsgroups formats...
That figures.
the dots were seen as directory separators so there was easy
conversion... i do it here with my JAMbases but am still limited to
8.3 lengths for each of them...
eg:
alt.audio.pro X:\JAM\GRPS\ALT\AUDIO\PRO
rec.audio.pro.live-sound X:\JAM\GRPS\REC\AUDIO\PRO\LIVE-SND
rec.arts.movies.production.sound
X:\JAM\GRPS\REC\ARTS\MOVIES\PRODUCTI.ON\SOUND
I hate that alt.crap.stuff.goes.here format.
that's the way that FIDO message areas were configured at one time,
too... don't let your aversion of NNTP style namings get in the way
;)
just remember that all it is is directory tree with each dot being
the '\' or '/'... the last one is either a directory fill of "single message per file" files (akin to MSG) or the last one is a single
file with multiple messages in it...
Yes, I know that 'special' characters like ~\!,#$%^&*() etc.,
don't work there.
that depends on the software and the OS...
MSG areas can also easily use this style...
I suppose. But that crap's not my style.
over the years, i've found it much nicer to have a directory tree structure for message storage...
Let me know if you receive this massage I have decided to fall back
to my old setup FD / FMAIL / ELEBBS + Irex (New)
Until I get the kinks worked out with Snynchonet BBS. Netmail seems
to be a challenge. As is scanning / packing sending mail. Inbound
tosses ok, but could have better statistics when tossing mail.
Platinum Xpress Mailer (DOS) does this the best I have ever seen.
Default full screen editor within SBBS is less then desired as well.
Irex is now registered 1000 node lic. may be a bit overkill,
but I wanted more then enough nodes, I would hate to be in a bind
with not enough nodes for the future. I have had new nodes every few monthes. If this trend continues I will need the space.
06 Oct 12 23:30, Gregory J. Deyss wrote to Roy Witt:Whew! for a while I thought that it was not working.
Let me know if you receive this massage I have decided to fall back
to my old setup FD / FMAIL / ELEBBS + Irex (New)
Got it...a bit delayed in my reply...
I have been looking online for quite sometime for a solution, have not found one yet. A lot of the documentationUntil I get the kinks worked out with Snynchonet BBS. Netmail seems
to be a challenge. As is scanning / packing sending mail. Inbound
tosses ok, but could have better statistics when tossing mail.
I'd think there would be a configerable switch for that.
yes really I like the stats that it indicates, percentage of the mail packet remaining as it tosses the mail. Currently fmail does the same thing but not asPlatinum Xpress Mailer (DOS) does this the best I have ever seen.
Really? That's a first.
yes the full screen editor is a mess.Default full screen editor within SBBS is less then desired as well.
Probably.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 143:24:25 |
Calls: | 500,263 |
Calls today: | 1 |
Files: | 95,201 |
D/L today: |
101 files (65,439K bytes) |
Messages: | 464,614 |