Same here.  One of our clients has a mailing list that includes all staff, plus a number of external partners.  To accomplish, they created an AllUsers alias and flipped ON the "include all domain users" switch.  The alias was added as a list subscriber so all employees are automatically subscribed via the AllUsers alias-- a real time-saver and error-saver when you have over 1,800 employees and dozens of new hires per month.

Problem is, if even ONE employee hits the unsubscribe button, it drops the AllUsers recipient from the list, which means the list immediately loses 99% of its recipients.  That happens several times per month.

Our admin opened a ticket months ago with a feature request to give domain admins control over Unsubscribe, but so far it has not been added.  

Exchange has several options for Subscribe/Unsubscribe, one of them being only an admin can remove a user-- a function we use extensively on our Exchange server, but there is no such option on Smartermail.

Please UP-vote this thread if you agree.

 

So, just to be clear, we're talking about the "Unsubscribe from these emails." line at the top of the message in webmail?

I only ask as we may be able to remove that, but not sure there's much we can do in clients that have the same, or similar, functionality. 

We have the same need: it's important to somehow control unintentional clicks on the "Unsubscribe from these emails" link at the top of the webmail message. Webmail users constantly click the link accidentally, and since there's not even a confirmation, they unsubscribe from the lists.

Actually, this would something we'd like to see too. Currently, we control all our mailing lists through API's rather then sending from SM itself. This includes functions in the email for tracking and unsubscribes. If someone were to click that link in the email in the web-client, it would cause problems as our server side databases wouldn't be sync'd at that point since there isn't an option for a webhook lol

+1 on accidental unsubscribes!!! I get 15-30 per week. Webmail users are the only ones who accidentally hit it. its always from missing an attachment link.

Please 

@Derek Curtis - sorry for the late reply.  For some reason this discussion dropped out of my favorites list.

What I'm referring to is the ability for the list creator (list admin, list owner, whatever you want to call them) to control WHO can unsubscribe from a list.

In Exchange, a distribution list can be created to allow members to self-unsubscribe AND there is the option that only a list administrator can add/delete users, which is perfect for guaranteeing an employee cannot unsubscribe themselves from essential corporate communications.

The problem is that in Smartermail, there is no list option to "include all domain users".  That option is only available to aliases.  So, the client had to create an email alias and turn ON the switch labeled "Include all domain users".  

Then they added that alias as the subscriber to a mailing list.  Here's the problem.... because the list sent to a SINGLE recipient (the alias) if ANY domain user hit the Unsubscribe link in webmail (or in their email client if offered), it would unsubscribe the alias itself.  So the next time a blast was sent to the mailing list, instead of 1800 users receiving an email from the CEO, nobody would get it because the alias that included all users had been removed by a single user hitting the Unsubscribe link.

Why use an alias as the sole recipient in this case?  Because-- 1800 users.  Having to MANUALLY maintain that many users, in a company that saw dozens of new-hires and terminations monthly, would have been a huge waste of resources.  And since it would be a manual process, prone to accidental omissions.  Using the "all domain users" enabled alias was the perfect solution for the list always including everyone.... until some knucklehead hit Unsubscribe.

Other question, Why use a list instead of just emailing the alias directly?  Because their leadership wanted all list messages to show the name of the list as the sender.

Short answer is:  Give list admins/owners the OPTION of disallowing users from self-unsubscribing, like Exchange already does.