<a name="fetch-mails-into-inbox"></a> <h2>Fetch mails into inbox</h2> <p>In some cases, you may not want to have OpenERP create objects directly on mail arrival, but put them into an inbox for further (possibly manual) processing.</p> <p>This module provides the base for this workflow and elementary UI for processing.</p> <a name="usage"></a> <h3>Usage</h3> <p>Create a fetchmail configuration and use 'Fetchmail inbox' as object to be created on mail arrival. Be sure to check Advanced/Keep original in order not to lose data in the intermediate step via the inbox.</p> <p>Mails fetched from this configuration end up in Settings/Technical/Email/Fetchmail Inbox, where they can be reviewed and eventually used to create new objects or attached to existing objects.</p> <a name="further-development"></a> <h3>Further development</h3> <p>This module deals with emails in a very generic way, which is good for flexibility, but bad for usability. Fortunately, it was developed with extensibility in mind so that it is very simple to write extension modules to ease handling emails for specific models in a more user friendly manner.</p> <p>In simple cases, if you want to force specifying objects of just one model, you can put 'set_default_res_model': 'your.model' into the menu action's context and you're done.</p> <a name="credits"></a> <h3>Credits</h3> <ul class="simple"> <li>icon courtesy of <a class="reference external" href="http://fortawesome.github.io/Font-Awesome/icon/inbox/">http://fortawesome.github.io/Font-Awesome/icon/inbox/</a></li> </ul> <a name="contributors"></a> <h2>Contributors</h2> <ul class="simple"> <li>Holger Brunn &lt;<a class="reference external" href="mailto:hbrunn&#64;therp.nl">hbrunn&#64;therp.nl</a>&gt;</li> <li>Stefan Rijnhart &lt;<a class="reference external" href="mailto:stefan&#64;opener.amsterdam">stefan&#64;opener.amsterdam</a>&gt;</li> </ul>