Scheduled Report distribution list update now sends only to new recipients

[Lisa Fields Wac]

     I have an existing scheduled report that has been working for two years.  I recently was asked to update the distribution list (remove one person, add three others).  Our sys_user file is up to date with correct email addresses.  I have report_manager and report_admin roles.

     When I look at the scheduled report job, I see see the retained recipients and the new recipients.  However, when I look in the SN Email Outbox, only the new additions are in the recipients block of the scheduled report.  

     Any idea what is preventing the original recipients from receiving the email?  They are still listed in the scheduled email report distribution list.  The one person removed is no longer in the list.

[Shivalika · Accepted solution]

Hi @Lisa Fields Wac 

Yes there can be other reasons like mail had been previously marked as spam by receiver, blocked attachments or large attachments or just a server overload issue. 

I hope I was able to answer your original question and we have the rootcause that they are not being delivered because bounced. You can try sending other mails to these users from system and arrive at specific conclusion. 

Kindly mark all  my  relevant answers as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY*

[Lisa Fields Wac]

We found the final cause:  the bounce back error had occurred enough times to put these three uses on a blocked user list (see redacted screen shot).  Once a developer cleared them from the blocked user list, they were able to get emails again.  

@Shivalika , thank you for starting us in the right direction, that it was a bounced email error.  The blocked list was the final culprit.  I don't know what caused the initial bouncing, but at least we found the way to correct it.

[Shivalika]

Hello @Lisa Fields Wac 

That's great it helped you. Kindly accept my solution as answer, so that my efforts can be recognized and also benefit future readers. 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY