Bill,
If you are willing to do the graphics, and keep them relatively small, I
don't see any reason why we wouldn't add them to the site. Right now we are
doing the collaborative editing in the Wiki, but eventually, I think that
we'd move the primary content into the main part of the web site, and use
that Wiki page for additional commentary. It really depends upon what
happens with the Wiki technology used here in the future. Right now it
doesn't resemble the rest of the web site look and feel at all, and it is
technically disjoint (runs on a separate host).
In any event, getting back to the topic at hand ...
I agree with you that "internal" might be the right name for the SMART_HOST
example. What you might do, which I think you're starting to do, is
introduce the SMART_HOST and Secondary MX ideas as illustrative examples,
talk about setting up RemoteDelivery with a gateway and a matcher, then go
back to each example separately, and show how to implement it.
Perhaps something like:
Implementing SMART_HOST, Secondary MX, or Load Balancing
Basic overview of the issue.
Configuring RemoteDelivery to use a gateway
- mention the need for setting up the spool
Configuring James as a SMART_HOST
- detailed example
- the role of the different RemoteDelivery instances
Configuring James as a Secondary MX
- detailed example
- setting up DNS, and role of MX preference
Configuring James for Load Balancing
- detailed example
- setting up the DNS. How load balancing works
Combinations
- examples
Summary
This probably shouldn't go all on one page. We'd start on one page, and
have links to details. But the nice thing about the Wiki is that we can
play with the structure as we go.
Note about load balancing. James doesn't have to refuse connections to
cause load balancing to occur. By setting up a number of MX records with
the same priority, the RFC mandates that they be chosen randomly, thus
assuring load balancing behavior over peers.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
