Completion is a wonderful thing. Dual-homed email servers for the corp, centralized user config (sorta), and openbsd galore. Took me a month and a half to get things running. Then took our team 2 weeks to implement and get running smooth. Wish someone with half an idea about DBs had designed the original postfix admin schema. After implementation I came to the general understanding that it's pretty broken, and about 1 step from the default flat file setup postfix uses. The only benefit I found was that you could multi home it for use with multiple servers. Pray to the might digits that those servers that all need to look at the data are all in the same geographical locale, cause otherwise it's broke.

What's that you say..."what gives with the geographical locale" bit? Lemme explain...

Problem: The company I work for has multiple offices, as do many companies. Two offices act as the primary locations for all the sub-realms work off of. We'll call them office R and T. Office R hosts the realms for offices R, S, and W, while office T hosts the realms for offices T, A, and P. Additionally, all realms hosted by R and T need to access shared mailing lists hosted at office R (which we will call realm L for simplicity).

Solution: Have each location have a different view of the data via a locale flag.

While this sounded great on paper the implementation put a serious thorn in our side as Postfix Admin doesn't gracefully know what to do with multiple views of the data.

I'll post more on this later...