Thibault Delavallée e86ee64b0a [MERGE] Mass Mailing branch. The purpose of this branch is to improve the mass mailing using the composer wizard, and a better support of email template values. Mass mailing basically posts a message on a document, without notifying the followers. Options are added that allow to send pure email mass mailing, or to notify followers. Specifying a reply to address is now supported. It by-passes the automatic thread fetching by directly looking for aliases instead of rebuilding threads when processing replies. Some templates have also been updated or added to support mass mailing in CRM.
mail_mail
- added recipient_ids field, that holds specific recipients in addition to email_to; this field replace the recipient_ids parameter of mail_mail.send(), allowing to re-send failed emails, or at least store the whole mail information about recipients,
- updated form view to add some missing fields in the view,
mail_message
- added 'reply_to' field, that holds specific reply_to value, before passing it to the created email notifications,
mail_compose_message
- added 'post' boolean field: whether the message will be posted on the document (using active_model_pool.message_post()), or if it should only be an email (using mail_mail.create()),
- added 'notify' boolean field: if the message is posted on the document, tells whether the followers should be notified of the message,
- added 'same_thread' boolean field: if not set, a custom reply_to will be used and the automatic thread routing in message_process will be py-passed,
email_template
- renamed 'email_recipients' field into 'partner_to' (more coherent: email_to is a list of emails, partner_to is a list of partner ids),
- added default template on res.partner, setting partner_to as obj.id,
- moving mass mailing action from mail to email_template, that now uses the previous template,
mail_compose_message in email_template
- added partner_to, email_to and email_cc to be able to use those fields, that exist on the template, in the wizard
crm
- updated basic lead/opportunity template, setting partner_to as obj.partner_id.id, or email_to as obj.email_from
- added mass mailing action for lead/opportunity that uses the previous template

bzr revid: tde@openerp.com-20130319095505-efv0mdzq2fnwnila
2013-03-19 10:55:05 +01:00
2013-02-21 13:18:25 +01:00
2013-02-21 13:18:25 +01:00
2013-02-21 13:18:25 +01:00
2012-12-21 15:24:02 +01:00
…
2012-10-11 10:52:18 +02:00
2012-10-11 10:52:18 +02:00
…

About OpenERP
-------------

OpenERP is an OpenSource/Free software Enterprise Resource Planning and
Customer Relationship Management software. More info at:

    http://www.openerp.com

Installation on Debian/Ubuntu
-----------------------------

Add the the apt repository

    deb http://nightly.openerp.com/6.1/deb/ ./

in your source.list and type:

    $ sudo apt-get update
    $ sudo apt-get install openerp

Or download the deb file and type:

    $ sudo dpkg -i <openerp-deb-filename>
    $ sudo apt-get install install -f

Installation on RedHat, Fedora, CentOS
--------------------------------------

Install the required dependencies:

    $ yum install python
    $ easy_install pip
    $ pip install .....

Install the openerp rpm

    $ rpm -i openerp-VERSION.rpm

Installation on Windows
-----------------------

    Check the notes in setup.py

Installation on MacOSX
-----------------------

Setuping you first database
---------------------------

Point your browser to http://localhost:8069/ and click "Manage Databases", the
default master password is "admin".

Detailed System Requirements
----------------------------

The dependencies are listed in setup.py

For Luxembourg localization, you also need:

 pdftk (http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/)

S
Description
No description provided
Readme LGPL-3.0
3.4 GiB
Languages
Python 49.6%
JavaScript 47.8%
SCSS 2%
CSS 0.3%
HTML 0.2%