Many thanks for this.
as you say..
By default the option is set to yes to include the SuperAdmin in the member’s list
yes, strange that in my case this wasn’t set. I may possibly have turned this off because I didn’t want editors to change an entry ownership to me.
However, if (as super admin), I created a bulletin, with the above set to no, then there is no way to delete it, even if you set the above to yes after you send a bulletin. The reason for this is that in the database table, there appears to be no field ’ with a value ‘1’ for that bulletin. So, to delete I had to go to this file: core.messages.php and temporarily remove this:
AND b.bulletin_group = ".$DB->escape_str($SESS->userdata['group_id'])."
about line 3398. This allows the bulletin to be shown to super admin for the purpose of deleting (as in your attached image). Of course, put this line back straight away after!
So, I guess, I am saying there is an anomaly. A super admin can always send a bulletin, but a super admin may not recieve it in the CP - and, more critically cannot delete it. A simple fix, would be that bulletins are always sent to Super admins, whatever the settings!