But you see this, right?

Nope...  (Not unless is appears/disappears faster than I can see it...)

Note that I am talking about the USER blacklist see from inside the quarantine options tab as seen by each user (not the QMS Blacklist as seen from the Management Portal)

Right, evanevery  - I missed the blacklist chapter ...

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 ...

Sorry, direct access is working too.

I created an entry *@demo.com, saved it. Logged out, logged in. Delete it and it disappeared. And it stays disappeared ...

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)

OK - I guess its time to update...  Wish me luck!  ;-)

Here are my "user" rights: