View Issue Details

IDProjectCategoryView StatusLast Update
0016927phplist applicationBounce Managementpublic11-05-17 20:30
Reporterlwc 
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionunable to reproduce 
Product Version3.0.5 
Target VersionFixed in Version3.0.6 
Summary0016927: phpList stopped sending me reports
DescriptionBack in v2, after each campaign phpList sent me ("Who gets the reports") a message telling me how many bounces were there and who got unconfirmed.
But since upgrading from 2.10.10 to 3.0.5 I didn't get a single report.
TagsNo tags attached.

Activities

michiel

21-10-13 02:49

manager   ~0052368


what is your setting for http://resources.phplist.com/system/config/send_listadmin_copy

duncanc

21-10-13 05:35

developer   ~0052369

Last edited: 21-10-13 05:36

View 2 revisions

Someone else has told me that they are not receiving bounce reports after upgrading.

A change to bounce processing between 2.10.x and 3.0.x, the else part of the if statement, stops the bounce report being sent when there were no users unsubscribed.

But it also stops the advanced report from being sent too.

$report = '';

if ($download_report) {
  $report .= $GLOBALS['I18N']->get("Report:")."\n$download_report\n";
}

if ($advanced_report) {
  $report .= $GLOBALS['I18N']->get('Report of advanced bounce processing:')."\n$advanced_report\n";
}
if ($unsubscribed_users) {
  $report .= "\n".$GLOBALS['I18N']->get("Below are users who have been marked unconfirmed. The in () is the number of consecutive bounces.")."\n";
  $report .= "\n$unsubscribed_users";
} else {
  # don't send a report email, if only some bounces were downloaded, but no users unsubscribed.
  $report = '';
}

lwc

21-10-13 16:32

reporter   ~0052370

send_listadmin_copy is only defined in admin/init.php (and used in admin/lib.php). As such, I've never touched its default value of true (in admin/init.php).

michiel

22-10-13 13:39

manager   ~0052371

revision 4276

michiel

22-10-13 13:40

manager   ~0052372

ah, hang on. only partly resolved with 4276

duncanc

01-01-14 09:35

developer   ~0052503

See GitHub pull request 17

michiel

11-05-17 20:30

manager   ~0059058

Resolving, but it's not entirely clear if this is fixed. The PR that Duncan refers to was probably before moving it to the current Github location.