Hi Mark,
>> -> If I ant to use BBBS' internal email capabilities... and route
>> -> they email thru my isp can the commandline to send email out also
>> -> include my username and password? My isp requires it... or should
>> -> I not use BBBS' internal email?
>>> It might depend on your internet provider. If you don't have a
>>> static IP address like I do here, then you will most likely have to
>>> use your ISP's SMTP server as a "smart host,"
>> he is trying to use his provider as a smarthost but they require
>> authentication in the form of his username and password (at least)...
>> He can supply the necessary info with bbbs's smtpd command,
>> username/password, etc. I think that's what he was asking.. maybe
>>
>yeah, that's the way i read it, too... and not knowing bbbs' options, i though
> i'd toss out another option that may work for him and others as well as
>offering another way of handling email from other machines on their networks..
Ok, understand. The thing with bbbs is you have all these daemons built in
BBBSD, (like httpd,https,telnet,binkp, geez, I dunno.. tons of the suckers
well, here's the list:
===================cut here===============
filegate~$ ./bbbsd
Usage: bbbsd [min] [max] [mode:port{:binkp}{:ssl}]
{mode...} {priority} {quiet}
{dev:ip} {fork} {uid:loginname}
Parameters:
min First nodenumber to be used.
max Last nodenumber to be used.
mode Service name (see below).
port Port number for this service.
"binkp" Force BinkP mode (telnetd and rawd only).
"ssl" Force SSL mode (https, stelnet, ...).
priority Priority (see bcfg4://local/os/).
"quiet" Be quiet, don't output anything.
"dev:ip" Bind only to IP address.
"fork" Fork to background.
"uid" Set client's uid and gid.
Service Port User node Service Port User node
-------------------------- --------------------------
ftpd 21 Yes smtpd 25 No
telnetd 23 Yes tpd 37 No
httpd 80 Yes fingerd 79 No
httpd:ssl 443 Yes popd 110 No
rawd 24554 Yes identd 113 No
popd:ssl 995 No
mrtgd 16425 No
==================cut here========================
Now of course, you can assign these to whatever ports you like if the standard
doesn't work for you for whatever reason.. Like me running ftp on port 60721,
etc.
>in our case, all emails go to our internal smtp server and if the connection i
> down, they sit there until they can be delivered... the first thing this does
> is to cut back on the support questions of why they can't connect to the
> outbound smtp server when the internet connection is down ;) O:)
IIRC, that was the same way I ran BBBS's daemon. It would just keep trying
until whenever
Right now though I'm running my own server over here on filegate.net with
postfix.
I tried using bbbs's daemon just 'cause I could .. you know, you're paying
for the daemon so why not? :) Truthfully though, all the daemons in BBBS are
enabled even in the trial version. Nothing is crippled in the trial version
so you can really test it out. I forget now how long I ran it before I was
comfortable in registering it, that it could do everything I needed it to do..
I might have even waited 6 months.. can't remember now. :)
Haven't been sorry
Take care,
Janis
--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)
|
