A few weeks ago, my hosting service received a complaint that my blog was sending spam. I don’t spam, so I checked out what was going on.
I had been using Mark’s Subscribe to Comments plugin which has one flaw: the released version does not support double-opt in. At the time I replied to my hosting company with an explanation and I disabled that plugin. I also went onto SpamCop and replied to the complaint with what I had done to resolve this.
Being tagged a spammer is serious stuff.
Double-opt in is when someone signs up for an e-mail and the first and only e-mail that goes out is one that says “Hey, someone just signed you up for this. If it’s really you, please confirm by clicking on this link. If it’s not you, then please ignore/delete this e-mail and the system will never send you an e-mail again.”
Until the subscriber clicks on that double-opt in link, the person is NOT subscribed. It’s e-mail subscription etiquette 101 and should be adhered to. I am NOT a bulk e-mailer but you have to be responsible on the Internet. SpamHaus has a good explanation here under “confirmed opt-in”.
This is a known issue and now the SVN copy of that plugin now supports Double-Opt in. I got my copy by using this command in my wp-content/plugins directory:
cd wp-content/plugins svn co http://svn.wp-plugins.org/subscribe-to-comments/branches/development stc
That put the svn copy into wp-content/plugins/stc. I went into the admin portion of the plugin and enabled Double-Opt in. A quick test later confirmed that it’s working. Once the 2.2 version is released, I’ll stop using the SVN copy and sync up with the WordPress.ORG copy.
One last item was that I deleted the e-mail of the subscriber who complained and now people who leave comments and want an e-mail on follow up comments will now work in a responsible way.