On Mon, 7 Feb 2011 14:21:39 -0500 (EST), Wietse Venema <wie...@porcupine.org> wrote:
> Except for all those beginners that get into trouble because they > use someone elses cookbook instructions instead of their own > expertise. And instead of being continuously consumed by same beginner questions, wouldn't it be easier to have the most frequent usage cases (and the related cookbooks) well documented in some kind of user continuously improved wiki like dovecot or nginx are doing? My background is qmail not postfix. As such I tend to think much in the lines exposed in DJB's seminal paper "Some thoughts on security after ten years of qmail 1.0" <http://cr.yp.to/qmail/qmailsec-20071101.pdf> Having migrated from Debian to Ubuntu (which unlike Debian early saw Postfix and not Exim as the way to go) and due to crescent spam fighting needs I am a newcomer to Postfix. From the outside the way I see the Postfix project is: - has much of the modular and paranoid untrustworthiness in code of qmail - takes standards compliance very seriously; - very well documented; hélas, scientifically documented!; meaning that it will be possible to find a terse and clean description of almost any aspects of postfix (not so well in the matters related with security encryption, ciphers & protocols) Unfortunately, if you aren't an scientist in this field and/or an expert in Postfix coding you will have a hard time understanding it. [Clear usage cases and (God forbids!) official cookbooks would be an added value.] - has a supportive and vibrant community: knowledgeable, friendly and usually with good humor. And yes I will continue to bother you with questions, bug reports, patches (if I ever will be up to such a difficult job), and all kinds of disruptive ideas. Please excuse my English as it is not my mother tongue. Regards, M.
