PS: On re-reading TangentRW's original idea more carefully, I see that we're talking about two very different solutions. While, yes, it's okay to reveal a Member's address to other Members and not to non-Members, we wouldn't need to get that elaborate, and I'm not even sure what a "personal message system contact web page" is. We simply need to avoid broadcasting people's personal email addresses on the Internet, and it would be nice if we could do it all "in-house."

The workaround scenario I've outlined is not much of an imposition once you're used to it, but does have one major flaw: Setting up forwards at your domain registrar depends on your registrar supporting such forwarding of individual addresses, and in sufficient number. Also, each event requires the involvement of the webmaster or other trusted individual, as it would be unwise (and awkward) to give the Domain Registrar password to the dozens of people who set up events, along with having to train them in setting up forwards, hoping they don't mess up the forward or something else, and trusting they won't go exploring through the rest of your registrar account. But apparently there would be no way for WA to set up such forwards within the WA interface?

I totally agree. We have dozens of Organizers (actually, they're Reservationists, and some events are organized by yet another person, so we could used two fields). Their personal addresses would be emailed to nearly 1500 strangers and seen by anyone on the Web. That's NOT acceptable at all, so here's is our complicated workaround.

1. For each event, create an email address for it at our domain. E.g. "BigParty@ourdomainname.com".
2. At our domain registrar, set up a forward for that address. Typically more than one person would be included in each forward (e.g., the reservationist, the manager who oversees events, the organizer, etc.)
3. Create a contact for the event's email address. Just put the address in First Name and in Email. No other fields need to be filled out, except maybe a Note reminding others not to delete it. (Step #5 is the reason for creating the contact.)
4. Set that contact address's email preferences to no auto announcements, no manual emails, so that it won't get our promotional emails. (Our people already get those at their own personal addresses.)
5. In the event's Emails section set Organizer as the Contact address you've set up for that event.
6. Choose the event's Contact address as Reply-to for mass emails related that event (optional). (BTW, I am not pleased that the default reply-to is the email creator's personal address -- many times I have forgotten to change it!)
7. Publish the event address instead of the person's private address.

Unfortunately, once the Reservationist gets a Registration, they still have to reply from their personal address. But hiding that would probably get very complicated (making our workaround seem simple), and at that point they are divulging their personal address to one person at a time, and presumably that person is known to us, or at least a friend, not a fiend.

The point of this proposal is that to assign an event organizers to an event reveals that organizer's email address, which is a violation of the privacy settings for the user's profile.

What probably should be added to this proposal is adding the still publicly obscured organizer's email address to the chain of system message replies for announcements, confirmations, etc.