> On Mon, Nov 24, 2008 at 11:47 AM, D G Teed <donald.teed@...> wrote:
> > When I can't understand the developer's notes, I usually emulate
> > something that works from useful examples.
> As a relatively recent newcomer to Postfix (I've been running qmail since
> 2002 and Postfix since last year) I agree with that statement. More examples
> would definitely be a good thing.
> This mailing list is an absolutely excellent source for information and
> specialist advise. But I also feel that I need to ask unnecessarily simple
> questions just because I can't find an example of what I'm trying do while
> not yet having a sufficient grasp of the Postfix system. Documents often
> feel to me like "expanded RFCs": they state exactly _ and usually in very
> technical terms _ how different parts of the system work. The bridge to
> their application is often not obvious especially to someone who has started
> using the system recently.
This is where the Postfix documentation ends. It's really hard to
provide documentation that is precise, complete, up to date, and
that covers multiple Postfix versions (as with qmail there is no
tradition of forced Postfix upgrades; even this year's advisories
did not affect BSD-ish platforms including MacOS, so you can expect
to find versions from years ago still ticking away).
Writing the "accessible" material is left to other people. Everyone
is welcome to write books or set up Postfix wikis and whatnot, and
they are welcome to cite from the dry reference manuals.