Subj : One entry point, multiple destination points.
To : mark lewis
From : Eric Renfro
Date : Sat Sep 19 2015 10:57 pm
Re: One entry point, multiple destination points.
By: mark lewis to Eric Renfro on Sat Sep 19 2015 02:40 pm
ML> 19 Sep 15 13:40, you wrote to me:
ER>>>> Here's the situation. One of my downlinks wants to setup their
ER>>>> IRex and FastEcho on thheir system to receive mail, one from me,
ER>>>> one from another link.
ML>>> should be a pretty standard setup...
ML> the ugly part is getting the domain stuff right and being able to pass to
ML> the proper ports as well as ensuring that the firewall is port forwarding
ML> properly AND that any connection tracking helpers the firewall may use are
ML> also configured to recognise the additional ports (eg: iptables and
ML> tracking ftp connections for established connections)...
ML> once everything is set up, then you can easily send to their different
ML> systems as easily as they can have their main system be a hub for their
ML> internal systems... whether they are flying full node addresses or point
ML> addresses...
[snip]
ER>> Is it unreasonable to assign multiple nodelist entries to someone
ER>> running multiple BBS's even if they're behind a single IP/mailer,
ER>> and just have my side route all their IP's to their respective
ER>> mailers? Coming from an NC perspective on that question. hehe
ML> no, it is not unreasonable to assign multiple node numbers to one IP
ML> fronting multiple systems... but don't think of one IP fronting one mailer
ML> unless that mailer is going to be hubbing the mail for all the other
ML> systems... then you've got to look at netmail routing, too, whereas with
ML> individual node numbers, the routing is a cinch and there's not a lot to
ML> be done because it is no different than any other routing...
ML> is that all confusing enough for ya? ;)
Hmmm... So in short, what you're saying is... The guy should be running a
single mailer, and that mailer should contain every AKA for every BBS system
running, and when it receives mail, *.PKT and *.MU* (Etc DOY), to multiple
"inbound" directories, one for each installation of FastEcho to use, and it
will toss what's validly destined to the address of that configured fastecho,
badmailing the rest or deleting it, then deleting each of those inbound
directories after tossing is complete. Running this for each BBS system
installed.
That seems the most likely ideal setup I can think of, to be honest. And since
I'm routing their netmail already anyway.. that should be relatively... Well,
pretty much the same.
This seems like the least complicated and likely most effective way to handle
it, but what pitfalls might this have? ;)
)))[Psi-Jack -//- Decker]
... Screw up your courage! You've screwed up everything else.
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)
