Multiple bounce handling problems #3408

Closed
opened 2026-02-20 16:05:02 -05:00 by deekerman · 4 comments
Owner

Originally created by @lazka on GitHub (Nov 19, 2018).

Issue

  • Imported bounce emails are not always linked with the campaign logs
  • Imported bounce emails are not detected as hard bounces
  • Marking emails as invalid based on hard bounces doesn't work

Related issues: #5980, #5898, #1578

Expected Behavior

When SuiteCRM fetches a bounce email over IMAP it should show up in the
campaign stats and on hard bounces it should mark the email as invalid.

Actual Behavior

Even though there is a proper bounce email imported it doesn't show up in the
campaign stats and on hard bounces the email address isn't marked as invalid.

Possible Fix

I've opened the PR #6505 to fix this

Steps to Reproduce

  1. Set up bounce handling in SuiteCRM
  2. Create campaign and add a contact with a non-existing email address
  3. Send a campaign email
  4. Watch the bounce inbox and wait until the email is read
  5. Check the the campaign stats

Your Environment

  • SuiteCRM Version used: 7.10.10
  • Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 63
  • Environment name and version (e.g. MySQL, PHP 7): PHP7.2
  • Operating System and version (e.g Ubuntu 16.04): CentOS 7
Originally created by @lazka on GitHub (Nov 19, 2018). #### Issue * Imported bounce emails are not always linked with the campaign logs * Imported bounce emails are not detected as hard bounces * Marking emails as invalid based on hard bounces doesn't work Related issues: #5980, #5898, #1578 #### Expected Behavior When SuiteCRM fetches a bounce email over IMAP it should show up in the campaign stats and on hard bounces it should mark the email as invalid. #### Actual Behavior Even though there is a proper bounce email imported it doesn't show up in the campaign stats and on hard bounces the email address isn't marked as invalid. #### Possible Fix I've opened the PR #6505 to fix this #### Steps to Reproduce 1. Set up bounce handling in SuiteCRM 2. Create campaign and add a contact with a non-existing email address 3. Send a campaign email 4. Watch the bounce inbox and wait until the email is read 5. Check the the campaign stats #### Your Environment * SuiteCRM Version used: 7.10.10 * Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Firefox 63 * Environment name and version (e.g. MySQL, PHP 7): PHP7.2 * Operating System and version (e.g Ubuntu 16.04): CentOS 7
Author
Owner

@samus-aran commented on GitHub (Nov 30, 2018):

Ideally you would relate the PR to close all the other (now) duplicate issues without having to create this new one.
I'll mark the other issues are duplicates and this supersedes this. Thanks for the contribution!

@samus-aran commented on GitHub (Nov 30, 2018): Ideally you would relate the PR to close all the other (now) duplicate issues without having to create this new one. I'll mark the other issues are duplicates and this supersedes this. Thanks for the contribution!
Author
Owner

@lazka commented on GitHub (Nov 30, 2018):

Ideally you would relate the PR to close all the other (now) duplicate issues without having to create this new one.

OK, I'll do that in the future!

@lazka commented on GitHub (Nov 30, 2018): > Ideally you would relate the PR to close all the other (now) duplicate issues without having to create this new one. OK, I'll do that in the future!
Author
Owner

@personman commented on GitHub (May 9, 2019):

What's the current status of this, @lazka? Do you expect your fixes to be merged soon? If not, do you have a fork with this merged in? Thanks!

@personman commented on GitHub (May 9, 2019): What's the current status of this, @lazka? Do you expect your fixes to be merged soon? If not, do you have a fork with this merged in? Thanks!
Author
Owner

@lazka commented on GitHub (May 9, 2019):

I don't know the merge-status of this, but the SuiteCRM devs have been very active in getting my proposed fixes merged so far, so I'm hopeful :)

btw. you can append ".patch" to the PR url to get a git patch file you can apply locally (with git am for example): https://github.com/salesagility/SuiteCRM/pull/6505.patch

@lazka commented on GitHub (May 9, 2019): I don't know the merge-status of this, but the SuiteCRM devs have been very active in getting my proposed fixes merged so far, so I'm hopeful :) btw. you can append ".patch" to the PR url to get a git patch file you can apply locally (with `git am` for example): https://github.com/salesagility/SuiteCRM/pull/6505.patch
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SuiteCRM-SuiteCRM#3408
No description provided.