Hi Simon and Stan.
On Fri, 08 Apr 2011 15:19 +0200, "Simon Brereton" <simon.brere...@dada.net> wrote: > There's a ton of howtos out there - I'm sure you can find one that suits > all your needs. The nice thing about this one is that it'll keep you on > the track you've been advised on - i.e. keeping things simple and adding > features as you go. I'm a big believer in learning what to do by learning what not to do, too. I've read enough comments that say Multiple Instance can simplify things, I'd really like to find just one complete example of configuration files for a simple Multiple Instance setup. Something that does "Accepting Server with SSL Certificates + Content Filter + Delivering Server" would be real nice. Looking at one screw at a time isn't helping me figure out how to build my first tractor. > I would recommend using amavis for your spam and virus checking though. I looked at that amavis configuration. That's more meat than I want to chew. And i don't see what it does for me better, faster or cheaper. Like everyone keeps suggesting, I think keeping it as simple as I can is a good thing for me. > Personally, I don't think you need multiple instances. I'm getting pretty clear that you can do it all lots of different ways, and you don't really need any single bit. Just about making smart choices. Mine will likely be different than the next fella's. > If the book you got was The Book of Postfix That's the one. UPS says Monday or Tuesday. > If in doubt, ask and remember that most defaults are there for a reason. > Consider the implications before changing them (but some will need to be > changed to suit your set-up). I see how the defaults are set up, and how you override them as required in main.cf and master.cf files. I still want to see an example of how you do that when you have 2 main.cf and 2 master.cf files. What goes where? These SSL certificates we have need to be plugged into the configuration files. If I do the simple two instance example, do I have to put them in both sets of configuration files? That seems kind of silly to me. I'd think one's the main source for all the config information, and the other inherits or overrides. But I asked about that a bit earlier and I think Daniel said, > From these questions your conceptual framework is wrong. Avoid forming > bad mental frameworks that have to be torn down later. Let the advanced > stuff be a pleasant fuzz. Honestly I'm not real sure what that means. Thought I'd try to figure it out some. On Fri, 08 Apr 2011 08:55 -0500, "Stan Hoeppner" <s...@hardwarefreak.com> wrote: > http://www.hardwarefreak.com/fqrdns.pcre That's more that 1500 lines of repetitive looking stuff. Although I think it's mainly to do with "answering nicely", feels like a whistle or bell right now. > Now would be a good time to look into the "everything under > smtpd_recipient_restrictions" main.cf style. This is the currently > preferred main.cf layout for most setups. Makes things easier on you, > the OP. Sounds like good advice. I keep bumping into that in online how-to articles. The book looks like it's got something to say about it too. > > . Then look at content filtering (spam, virus and other objectionable > > content) > > I'd probably reverse the order or priority of these last two. I'm not clear on what you mean. Isn't the idea of sending mail from PostFix through something like Spam Assassin to deal with "objectionable content"? > > . Then look at more advanced controls like grey-listing and postscreen Grey-listing I don't know anything about yet. You call postscreen "advanced". Other folks keep saying do it later, too. When I read it's documentation, it sure seems like it's the newest, simplest way I've seen to use blocking lists like Spamhaus and Barracuda. If I don't use postscreen, I don't see how I use those lists. Did I miss something else? Thanks to you both. Jeremy Alsten
