rckhllwy wrote: I appreciate your efforts, however I don't fully agree with your approach.
The current method before the opt in method was added, is compatible with the Canada's Anti-Spam Legislation with Implicit consent.
i.e. emails are added to the Friends, prospect, past member and members list only after they have been given to us by the visitor. The FTH system already has an unsubscribe feature which has already been used successfully by some of our visitors.
At the very least, if the changes are inevitable, I think that the following cmodifications should be implemented:
1) The opt in message should de-techied a bit. >> There is a segment of the population who may not respond positively
2) The 30 day time limit on opting in should have a reminder step added in. Perhaps the two weeks time point might be a good interval. >> Some of need a reminder . . .they just do.
Double opt-in is what I understand to be current best practice... and is what is needed for GDPR. If you consider the implicit initial consent or supply of information via contact form to be a single opt in, then we are requiring 2nd one... we are closer to double opt in. However, if you read the available references, we really are not truly double opt in, since we allow you to add someone to the list
before we ask them for permission to do that via the opt-in email. My workaround is just to add them in a deactivated, unusable state. However, even with my approach, it really does not exactly meet the high standard of double opt-in...
but we are much closer.
Read the following, for example, which gives specifics about "double opt in":
www.mailjet.com/gdpr/consent/
1. If you have *specific* suggestions on the email, please provide those... I am all ears. Just providing a generalized negative comment on the email does not help us improve it. Specifics please?
2. Yeah, some sort of reminder may be needed. I will need to sort through the technical issues of triggering reminders.
3. If there are any suggestion on making this more usable (other than killing it), please let us know.
BTW, keep in mind that we are not exactly thrilled to add this... 
I think we are basically backed into a corner though, and have to do it to be able to provide FreeToastHost to an international user base and say we are compliant with prevailing privacy laws / regulations with a straight face.