-=> On 11-12-19 07:20, poindexter FORTRAN wrote to All <=-

 pF> So, given that my power utility company is promising years of
 pF> preventative power outages, I'm revisiting moving my BBS and mailer to
 pF> a VPS.

Might be a wise move for you.

 pF> I've run Synchronet for years under Windows and wanted to understand
 pF> how other people here configure their BBSes when running under *nix.

 pF> Do you run another web server like Apache or Nginx and then set up
 pF> Synchronet as a sgi handler to handle .ssjs files? Or use Synchronet as
 pF> your primary web server? Or configure another web server as a reverse
 pF> proxy?

Depends what you want to do.  Web access is available but not a high priority
for me.

 pF> Ditto for mail - I'd like to be able to use procmail and other
 pF> anti-spam tools, not sure how I'd have one MTA on the system answer for
 pF> incoming mail and then hand off to Synchronet.

You could do that.  I think SBBS has some anti spam tools, but from memory they
rely on RBLs, which I don't like to do, because the RBLs can sometimes be a bit
over the top.  I prefer to use them as input for something like SpamAssassin.

 pF> Or, do you just have Synchronet handling everything?

 pF> Lastly, do you use a software firewall on the box?

That's easily done, because Linux has iptables available.

 pF> I'm trying to imagine a setup where I had a public IP on the front-end
 pF> services (like Nginx/Sendmail), and then routed to a Synchronet bound
 pF> on a private IP on the same interface, but that might be
 pF> overcomplicating the issue.

Again, depends what you want, and it might actually be better to use iptables
to do any port redirection or blocking necessary onto the same IP.  That way,
user facing services like telnet/SSH can be handled directly by Synchronet,
while anything you want something infront of Synchronet can be setup that way.


... BULLFIGHTER: 1 little man against a 1/2 ton of pissed off pot roast.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux