I sent in an email to support regarding this bug, but wanted to additionally add to the consensus that I don’t at all like how webflow is handling this critical issue. It’s now 11 days since Dave’s suggested solution and nothing has changed. End-users are still receiving webflow branded emails despite all the money being spent by webflow subscribers on white-labelled solutions and ANYONE they reply, forward to, or a user that changes the site name and email in the URL can still unsubscribe them from receiving business critical communications.
In fact the only change observed as noted by @samliew since this bug report was posted is that this thread has gone from a bug report to general discussion for PR purposes. I simply can’t accept this was an intended change and if it was then I honestly believe that reflects worse on the company than the issue in the first place.
More so I’m disappointed that it was actually given as a serious suggestion that designers independently vet and edit every incoming email? You must be kidding! Even excluding the obscene time requirement for doing this, we’re talking about business data!
I really think you guys need to step back and revisit your code approval process. It’s closed source software so please invite mangers with more business experience and client understanding to offer feedback before release of any code that fundamentally affects white-labeling and client security. It took multiple years for a anti-spammer feature to be added to the mailserver so it clearly wasn’t that urgent. It certainly doesn’t add any confidence in the software that a webflow branded, security hole was deemed to be the optimal solution after all this time.
As others have pointed out, all that was needed was an initial sign up confirmation email when the recipient address is first entered. Frankly I don’t know of any genuine business owner who would unsubscribe from emails from their own website, and if they do, I highly doubt they understood what they were doing. It simply doesn’t make sense to prioritize free users and spammers over genuine clients. If business end-users are seriously unsubscribing from their own emails then I’d put a strong wager that problem is more related to lack of captcha integration in the form itself bringing in a surplus of junk mail.
Do we have an update on the status of this issue? I would also like to see the complete removal of the unsubscribe message if a solution isn’t forthcoming in the next couple of days.
Finally, webflow is charging enough money for subscriptions at this point to outsource some of their clearly and demonstrably less familiar infrastructure and software requirements to more specialized providers like Mandrill etc. Maybe this is an avenue to be considered? Of course there’s always the option of allowing users to use their own mail servers too. I’d take the flexibility of configuring my exchange servers to send email to clients any day over the current implementation.