Ok, now I started the right activities.

I put one address to my personal blacklist. After this I entered quarantine with my account and accessed blacklist. I selected the last address, deleted it and it stayed deleted. I logged out and logged in again, just to be sure. But this address does not appear again.

Are you using the latest version of SMG (including monitoring)?

No, I'm one version back...  I'm waiting for the usual "dust to settle" before I run the update...

I can delete any "user" blacklist entries from the admin/config/policy rule, but individual users can not delete addresses that they create themselves.

Have you tried BOTH creating and then deleting an address fully from within user quarantine access?  In my experience, it doesn't matter if the user logs in/out.  The address simply will not be deleted at all.

I don't know if it matters, but all my addresses are wildcarded (i.e. "*@acme.com" or "*.acme.com")

No, my address has been added to blacklist by activities on a digest. I assume that this approach is easier for common users. Your way ia a power user activity .

But I will use your way too ...

Unfortunately, there is no automated way to Blacklist an entry which was NOT initially caught by SMG. (at least none that I know of..)

So, for those spammers whose messages are NOT initially caught by SMG (i.e messages get through without issue), users must manually go into the Quarantine, select the Options Tab, and then enter an offending address by hand.

Additionally, SMG is not trapping manually entered addresses based on the SMTP "FROM" field.  It appears it ONLY uses the "Reply-To" field.  This makes it even harder for casual users to understand WHICH address they must use to blacklist an entity (as the "Reply-To" field is not the "sender" they see in the GroupWise client).  (I have a separate posting open on this forum for this issue)

I have seen your other post but did not have time to test it.

I use a lot of "from" address filters and they seem to work but I did not check in depth as you did.

Running update on my "secondary" SMG system now...  It appears I must find my activation code...

Running update on my "secondary" SMG system now...  It appears I must find my activation code...

Yes, you need this to register your operating system and get an additional update.

OK, I updated our "Test" SMG system.  It has been rebooted and is current...

Its still not working.  As a "User", I still can NOT delete a Blacklist record from my personal blacklist.  It should also be noted that this is a completely different SMG installation (TEST vs PRODUCTION) so this issue is not unique to a particular machine.

Maybe I'm just missing something?

I check the box next to the record I want to delete (see below), then click "DELETE".  The check mark disappears but the record is retained...

I do the same:

1.

2. I pressed delete

Gone ...

You have seem my rights above.

Yes, my user has all the same rights (plus "Access Attachments")

This is happening on two different installations, now running two different versions of SMG.

What browser(s) have you tested?  (I'm using firefox but will see if others behave differently)

Chrome and Firefox.

EDGE is also doing the same thing for me...

Any other ideas?

I wonder...

I have two rules in my policy.  One exposes the "Global" Blacklist and the other exposes the "QMS" (users) blacklist.

I wonder, if by clicking on the QMS/Users Blacklist from the policy page (as admin), if it has changed the rights on the underlying file such that users can add entries but not delete them...

Hi Edward - Did you get this resolved?  If not, would you please open a case with support?  -  Thanks, Pam

As with my "other" blacklisting issue...

I need to bring our "production" SMG system up to the current version so we can confirm we are still seeing the same blacklist editing issues with the current version BEFORE I open a case...

Yup, still not allowing anyone to delete personal blacklist entries even after the upgrade to the current release...

I'm wondering if this might be because I had accessed the blacklist via the Policy page (as admin) and the permissions on the associated file got changed once it was touched by admin...  Users can still manually create their own blacklist entries, they just can't delete them...