From 3bc9d36b774abd706add6515e6e04d93b0e5eda0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thibault=20Delavall=C3=A9e?= Date: Mon, 19 Nov 2012 15:17:40 +0100 Subject: [PATCH] [FIX] message_route: when replying to a message, use its model and res_id, never lost. bzr revid: tde@openerp.com-20121119141740-tjlp1uy4mq4lrg48 --- addons/mail/mail_thread.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/addons/mail/mail_thread.py b/addons/mail/mail_thread.py index ee1a015396b..a809f7e8e2e 100644 --- a/addons/mail/mail_thread.py +++ b/addons/mail/mail_thread.py @@ -341,7 +341,7 @@ class mail_thread(osv.AbstractModel): message = self.pool.get('mail.message').browse(cr, uid, message_ids[0], context=context) _logger.debug('Routing mail with Message-Id %s: direct reply to a private message: %s, custom_values: %s, uid: %s', message_id, message.id, custom_values, uid) - return [(False, 0, custom_values, uid)] + return [(message.model, message.res_id, custom_values, uid)] # 2. Look for a matching mail.alias entry # Delivered-To is a safe bet in most modern MTAs, but we have to fallback on To + Cc values