On 5/11/2015 9:28 AM, [email protected] wrote: > Hello > > I'm going to be setting up my first production Postfix server in a VPS. > It'll be the staticIP front-end to a full standalone mail server on my home > LAN that's now stuck behind a dynamic IP. > > Over the past couple of weeks I've been reading the documentation and > playing with the various instance types locally. > > There's a million ways to do everything, and they all seem to work well! :-) > > I just want to ask a couple of questions to narrow down my options to the > right & best "fit". > > This planned server in the VPS needs to do ONLY the following > > (1) anti-spam on inbound mail > (2) forward inbound mail to the home server on its dynamic IPv4 (or over IPv6) > (3) store inbound mail if the home server/connection is down, then deliver it > when it's up again > (4) act as a smarthost that the home server sends through, so the external > 'net "sees" mail from the VPS' static IP. > (5) make sure that ALL local mail on the VPS is only sent to an > "[email protected]" address on the home server; I.e., NO local mail > delivery. > > My main questions are: > > (1) What are the nominal, specific Postfix instances that I need to do that > ^^ that? By any chance is there a single example that you might know of for > that simple combined config? > (2) Should I configure all that in only one instance, or is there a good > reason to use Postfix's "multi-instance" setup? > > -Gornle >
Don't try to do this all at once, there are too many moving parts. Work on the gateway and home server separately; get one working, then work on the other. Don't try to configure spam filtering on the gateway until after you get the basic postfix config working. http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient For your VPS gateway, this should get you started: http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Note that it's important for the gateway to have a list of valid recipients. This can either be be a list you maintain as relay_recipient_maps, or let postfix do it for you with "reject_unverified_recipient" For your home server, start here: http://www.postfix.org/STANDARD_CONFIGURATION_README.html#local_network You'll also want to set the VPS as relayhost, and set some controls so the home system accepts mail ONLY from the VPS -- easiest way to do that is add the VPS IP to the home system mynetworks, then add something like this to main.cf: smtpd_client_restrictions = permit_mynetworks reject You most likely won't need multi-instance support, but that may depend on the details of your future spam filtering config. -- Noel Jones
