Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
Coopdevs OCB mirror
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Coopdevs
Odoo
Coopdevs OCB mirror
Commits
18ae91ea
Commit
18ae91ea
authored
9 years ago
by
Danimar Ribeiro
Committed by
Martin Trigaux
9 years ago
Browse files
Options
Downloads
Patches
Plain Diff
[FIX] mass_mailing: Check if bounce_alias is not None
If the parameter mail.bounce.alias is not found
parent
eb189259
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
addons/mass_mailing/models/mail_thread.py
+1
-1
1 addition, 1 deletion
addons/mass_mailing/models/mail_thread.py
with
1 addition
and
1 deletion
addons/mass_mailing/models/mail_thread.py
+
1
−
1
View file @
18ae91ea
...
...
@@ -45,7 +45,7 @@ class MailThread(osv.AbstractModel):
email_to
=
decode_header
(
message
,
'
To
'
)
# 0. Verify whether this is a bounced email (wrong destination,...) -> use it to collect data, such as dead leads
if
bounce_alias
in
email_to
:
if
bounce_alias
and
bounce_alias
in
email_to
:
# Bounce regex
# Typical form of bounce is bounce_alias-128-crm.lead-34@domain
# group(1) = the mail ID; group(2) = the model (if any); group(3) = the record ID
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment