<h1>Memberspace Area for Foodcoop</h1> <h2>Email Alias feature</h2> <h1>Concept</h1> <ul> <li><p>Each team/template will have 2 email alias:</p> <ul> <li>1 for the Coordinators of the team, naming convention of alias for Coordinators: coordos.[week][day][hour]@[domain]</li> <li>1 for the Members of the Team (including the Coordinators): naming convention of alias for Members: service.[week][day][hour]@[domain]</li> </ul></li> <li><p>Alias domain is configured by parameter object:</p> <ul> <li>with key: mail.catchall.domain.</li> <li>value: your email domain (e.g: cooplaloue.fr) When installing module, there is a script to create email alias automatically for each template, so, mail.catchall.domain must exist before installing coop_memberspace module.</li> </ul></li> <li><p>There are 2 main objects to store email alias for each team:</p> <ul> <li>memberspace_alias: store all alias of team (access via Member config menu: Members &gt; Configuration &gt; Memberspace Alias)</li> <li>memberspace_conversation: store all conversation of each topic (access via Member config menu: Members &gt; Configuration &gt; Memberspace Conversation). Every time a new email which sent to specific alias, a new conversation will be created, then after that, all reply of the conversation will be stored within this conversation.</li> </ul></li> </ul> <h1>How Alias works?</h1> <p>Any mail sent to your domain, that doesn&#39;t have a defined mailbox, will be sent to your catchall email. Application fetches the emails with a cron (using the module fetchmail) and dispatches them to corresponding virtual mail address (alias)</p> <p>Note: Make sure you set your created mailbox of Incoming Mail Server as the catch-all.</p>