Proposal after discussion with Noam, Jimmy, Chris, and Joe
Sending addresses for Agents
*When an agent posts a comment via the website, agent selects from available EmailContactMethods. If none exist, default is a no-reply EmailContactMethod.
Subscribed item prefix option for Subscriptions
* Subscription will have a subscribed item prefix field. If value is yes, then subject lines of messages sent through a subscription will include a prefix showing the email list name of the subscribed item responsible for sending the message to the agent.
Email lists
* Folio will be the default way people create email lists / discussions. It unites message board and email list as concepts.
* Folio has a field called email list name which, when prepended to @<domain> replaces the automatically assigned "To:" address for messages to the Folio
* Item has field called reply-to which selects from "sender address" or "all subscribers to item"
* A Group can have more than one Folio
Email header fields for email lists (sent through Folio subscriptions)
* From: <sending address>@<domain>
* To: <email list name>@<domain>
* Reply-to: <reply-to address>@<domain>
* Subject: {[<email list name>]}[Comment-<id>] <comment title>
Keeping track of who sent the comment
* When someone posts a comment from email, it associates the email contact method with that comment (already works)
* When someone posts a comment from the website, it associates the sending address with that comment.
Longer term idea
* Each agent has a message box that unifies the subscribed to comments they have received together with personal messages.
* Subscription could specify an EmailContactMethod, message box, or both
* Message box would be organized so the user could separate comments by group, etc.
Deme Email integration plan