Skip to Content
This question has been flagged
2 Replies
5098 Views
Avatar
LudovicL

Hello,

I've found this information on this forum :

The following heuristics are used, in this order:
 * if the message replies to an existing thread by having a Message-Id that matches an existing mail_message.message_id, we take the original message model/thread_id pair and ignore custom_value as no creation will take place
* if the message replies to an existing thread by having In-Reply-To or References matching odoo model/thread_id Message-Id and if this thread has messages without message_id, take this model/thread_id pair and ignore custom_value as no creation will take place (6.1 compatibility)
* look for a mail.alias entry matching the message recipients and use the corresponding model, thread_id, custom_values and user_id. This could lead to a thread update or creation depending on the alias * fallback on provided ``model``, ``thread_id`` and ``custom_values`` 
* raise an exception as no route has been found

I've configured my incoming emails without alias (for now) and now here is how it works :

When I send an email from Odoo client interface and the client answer to this email. I received the answer in Odoo client interface. That's fine !

 When this client send an email, it doesn't go to the odoo client defined. I can see this error in the log :

ValueError: No possible route found for incoming message from Lemaire dupont <lemairedupont@icloud.com> to Ludovic <ludovic@gmail.com> (Message-Id <139A76A5-91A2-4F1C-A144-EE3F371BC567@gmail.com>:). Create an appropriate mail.alias or force the destination model.


How can I solve this ?

Also, for all other emails incoming which are not related to a know client, is it possible to receive them in my dashboard inbox ?

Thanks in advance for you help.

Ludovic 


Avatar
Discard
Avatar
Arsenty Karamurza
Best Answer

 Indeed, it is crazy that such a basic feature as email delivery doesn't work reliably, but it's true.

As for a workaround, I came across an OCA module that sends a rejection notice to the sender, but that's not what we want at all! I mean bothering clients with this fluff is a bit dull, isn't it?

So I'm just going to make that OCA module send rejection notices to our own predefined email address instead..

If you need such a fix too, please just drop me a line at vi3ual[at]gmail.[соm] and I'll just send you a modified module free of any charge.

Regards, 
Arsenty

Avatar
Discard
Avatar
Serpent Consulting Services Pvt. Ltd.
Best Answer

Ludovic,

You may make sure that you have configured the email for incoming server. If the target email being sent matches your configured address, it should simply work. There should be a model linked to the incoming email(like make a lead, applicant, project issue).

It is surely possible to receive email from unknown customers.

For a separate web email interface, we've created an app if it interests you : https://www.slideshare.net/SerpentcsConsulting/odoo-webemail-interface

Thanks.

Avatar
Discard