Now that I have echomail working correctly, I need a little help with netmail. How do I set that area up so SBBS can distinguish it from echomail? Also, how does SBBS compile a nodelist? In the event I want to send mail to an node other than my hub, how does SBBS find the user in the nodelist?
Now that I have echomail working correctly, I need a little help with netmail. How do I set that area up so SBBS can distinguish it from echomail?
Also, how does SBBS compile a nodelist?
In the event I want to send mail to an node other than my hub, how
does SBBS find the user in the nodelist?
Next, do you run binkdwin via a timed event, or do we depend on fidoin/fidoout to create semaphores that kick off binkdwin?
Next, do you run binkdwin via a timed event, or do we depend on
fidoin/fidoout to create semaphores that kick off binkdwin?
binkd runs all the time so it can receive inbound connections for mail and file
transfers... the only thing we used fidoin and fidoout for are to trigger the mail handler to toss or scan mail for packaging and sending... the actual mailer, binkd, stays running all the time and will create the fidoin semaphore when new mail arrives... sbbs does the fidoout thing... a default configuration
sends the echomail immediately once it is saved... we changed our setup so that
we scan outbound echomail at a timed interval... that gives folks a chance to edit or delete an echomail they wrote if they want/need to...
Re: Netmail Area
By: mark lewis to Joe Bruchis on Fri May 05 2017 10:59:30
Next, do you run binkdwin via a timed event, or do we depend on
fidoin/fidoout to create semaphores that kick off binkdwin?
binkd runs all the time so it can receive inbound connections for
mail and file transfers... the only thing we used fidoin and
fidoout for are to trigger the mail handler to toss or scan mail
for packaging and sending... the actual mailer, binkd, stays
running all the time and will create the fidoin semaphore when new
mail arrives... sbbs does the fidoout thing... a default
configuration sends the echomail immediately once it is saved...
we changed our setup so that we scan outbound echomail at a timed interval... that gives folks a chance to edit or delete an
echomail they wrote if they want/need to...
I believe Joe runs DB, thus the binkdwin. That too however, can be
set to run in the background like binkd.
First Synchronet does not use a nodelist, so no need to compile
one. Binkd will handle netmail, but you will likely have to
configure it with the address of that node. As for netmail and synchronet, you dont need a special area. If I remember correctly,
you go to Netmail settings in your configuration setup. Netmail is internal to Synchronet, and there is no actual area to setup,
unlike echomail.
AFAIK the netmail is placed in the user's private mail area automatically... there is no netmail area...
Also, how does SBBS compile a nodelist?
it does not...
In the event I want to send mail to an node other than my hub, how
does SBBS find the user in the nodelist?
it does not... you have to know this information beforehand and
enter it correctly... then the routing configuration takes over as
to whether the netmail goes routed or direct...
Next, do you run binkdwin via a timed event, or do we depend on fidoin/fidoout to create semaphores that kick off binkdwin?
binkd runs all the time so it can receive inbound connections for
mail and file transfers... the only thing we used fidoin and
fidoout for are to trigger the mail handler to toss or scan mail
for packaging and sending... the actual mailer, binkd, stays
running all the time and will create the fidoin semaphore when new
mail arrives... sbbs does the fidoout thing... a default
configuration sends the echomail immediately once it is saved... we changed our setup so that we scan outbound echomail at a timed
interval... that gives folks a chance to edit or delete an echomail
they wrote if they want/need to...
so, binkd creates fidoin after the session is complete... then sbbs
sees the fidoin semaphore and fires up sbbsecho which tosses the
mail into sbbs... sbbs handles fidoout when configured and sbbsecho
scans out the mail, packages it and places it in the binkd outbound
for binkd to send...
I believe Joe runs DB, thus the binkdwin. That too however, can be
set to run in the background like binkd.
Hi Joe, sorry for the delayed reply. I was out-of-town over the weekend.
I think I understand how netmail works in SBBS now. Thaks for the info.
Regards,
I believe Joe runs DB, thus the binkdwin. That too however, can be
set to run in the background like binkd.
I do run DB, however only to poll my uplink (Roger Nelson) via timed events. I am understanding that I will need to run it as a service so that it will send mail when entered in the BBS.
Good. (again <G>) You could always just run binkd, if you dont use
any of the other features of DB. The mail is not compatible with
Synch, or I would be using it. I have it set up here as well.
Good. (again <G>) You could always just run binkd, if you dont use
any of the other features of DB. The mail is not compatible with
Synch, or I would be using it. I have it set up here as well.
Joe, have you tried any of the following:
* Run DB as a front-end to poll your uplink via a schedule (not as a server or service). Disable the mail tosser.
* Have a batch file copy the packets from DB inbound to SBBS inbound
* Have DB toss the mail in its inbound as a timed event
* Have SBBS toss the mail in its inbound as a timed event
* Have SBBS send outbound normally as it is sent from the BBS
* Have any mail you enter in DB's editor or other configured editor sent as normal after you enter it (crash via outgoing poll to your uplink).
* NOTE: You can run "BinkdWin -v binkd.cfg" as a process and still run the DB binkd to poll your uplink. I have tried it successfully.
OR OPTION 2:
* Receive and send mail with your uplink via DB by polling your uplink (not as a server)
* Read respond to mail as normal within DB or configured editor.
* Get an FTP feed for the BBS separate from the feed from your uplink for receiving and sending mail. I know of free FTP feeds that are avalable.
* Receive and send mail with your uplink via DB by polling your uplink (not as a server)
* Read respond to mail as normal within DB or configured editor.
* Get an FTP feed for the BBS separate from the feed from your
uplink for
receiving and sending mail. I know of free FTP feeds that are avalable.
I think over the years I have tried some of that. I still have a
live phone line and modem on the BBS. The odd person and sysop,
still use that. For those users calling in on POTS, I use Taurus
(32 bit) and a utility that transfers the call to Synchronet, as a
telnet connection. I have not tried to do that with DB since it
is not 32 bit (yet at least).
I think over the years I have tried some of that. I still have a
live phone line and modem on the BBS. The odd person and sysop,
still use that. For those users calling in on POTS, I use Taurus
(32 bit) and a utility that transfers the call to Synchronet, as a
telnet connection. I have not tried to do that with DB since it
is not 32 bit (yet at least).
Yes. I can see how those constraints pose special problems.
I think I am going to opt for a ftp feed for the BBS. I'll do my personal editing in Timed and personal tossing, packing, sending and receiving in DB. That will solve it for me.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495935:28:17 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,933 |