-
-
Notifications
You must be signed in to change notification settings - Fork 621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[17.0] mail_tracking starting endless email loop #1414
Comments
Hi, @Bart-dh It could be that the original mail had that social/mail_tracking/models/mail_thread.py Lines 65 to 73 in 27f3809
We try to dectect the existing aliases:
In order to discard them social/mail_tracking/models/mail_thread.py Lines 90 to 94 in 27f3809
This is where we retrieve them (in v17 there's a new way to set the catchall with the social/mail_tracking/models/mail_alias.py Lines 10 to 23 in 27f3809
Also check if a partner could have that catchall email set, as it could be that is assigning it directly: social/mail_tracking/models/mail_thread.py Lines 85 to 86 in 27f3809
|
@chienandalu what is the reason for adding extra suggested recipients? To me it looks like extra functionality which is irrelevant to the rest of this module, but I could be mistaken |
It's inside the scope, as Odoo is not considering CC unless a contact matching the email address exists, and this module does it. |
module: mail_tracking
version: 17.0 EE
Odoo.sh hosting
For some reason unknown to me, at some point when sending an email, [email protected] gets added as recipient, resulting in the sent mail returning to Odoo immediately, and starting an endless email loop. A client of ours sent 21k emails this weekend to a supplier because of this loop.
Note that the reply-to is [email protected] instead of [email protected], so I don't know where the default catchall comes from. I have noticed that the module also adds extra suggested recipients though, so maybe this is related.
I have no proof that this module caused the issue, other than it started after installation, and does not happen anymore after deinstallation.
The text was updated successfully, but these errors were encountered: