On 2/28/2012 1:54 PM, Steve Campbell wrote: > > > On 2/28/2012 12:25 PM, Brian Evans - Postfix List wrote: >> On 2/28/2012 11:48 AM, Steve Campbell wrote: >>> I'm new to postfix so I've got a lot of learning to do. >> Welcome to Postfix. >> >>> One of the basic questions I have is this: >>> >>> I'm wanting to use bl.spamcop.net. From what I can discern, I've got >>> to put this in my main.cf in a section named >>> smtpd_recipient_restrictions. I don't see that in mine, but I'm >>> guessing I need to create this section (either manually or with >>> postconf(?)). I've found a few examples but they have tons of other >>> things in that section as well. >>> >>> Is the above correct to some degree? >> What you must understand is that Postfix comes with sensible defaults >> for most people. >> When not explicitly overridden, it uses those defaults. > > I've read that. Still, no RBLs exist that I can tell and I need to use > them. >> >> To see the current values of an option, you can use the postconf tool. >> Ex: "postconf smtpd_recipient_restrictions" >> >> That particular option has requirements to be met to keep you from being >> an open relay. >> You should add features by keeping the default and appending what you >> want. > If I add that section manually, and just add the lines that I need, > can I assume that the other defaults are still being used for that > section?
Basic RBL example: smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination, reject_rbl_client rbl.example.com The above example is the defaults plus the RBL. Postfix cares not how it gets there either by your favorite text editor or 'postconf -e' Activation of the restriction comes when a new smtpd process is created OR (if in a hurry, not required) when Postfix is reloaded. Any configuration option in main.cf or master.cf overwrites any defaults. Repeated options has the previous one overwritten. This is why 'postconf -n' is a good viewer to check your work. Brian
