I agree. A requested one-time email should not require an opt-in. But the
email should state that it is a one-time email, and that you had requested
it. The email should give you the date, time, IP address of when/where it
was requested. At least the receiver stands a chance of remembering he
requested the email and will not report it as spam.
Any opt-in email should also state date, time and IP address as a reminder.
Also, opt-in requests should not be allowed to include ads of any sort.
Opt-in could become the spam if it were allowed to include ads.
The spammers would just fake the requests for the opt-in to cause the opt-in
requests to be sent.
Oh! Where is the line?
No opt-in verification for a one-time email response to a one-time request.
But, if the above was the law, if the spammer were to fake the request, the
email response would be allowed and it could contain spam. So, I have
changed my opinion while typing! Verification for a one time email with an
opt-in is required, and the opt-in can't contain ads.
Guy
-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of Nick
Phillips
Sent: Thursday, August 19, 2004 3:02 AM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] Good Domain List one step closer to reality
(actually two steps)
On Thu, Aug 19, 2004 at 02:10:16AM -0400, John Glube wrote:
would take a lot of consideration on their part. The more
organizations that recognize verified opt-in as a best
practice, the more likely that it will be accepted by bulk
emailers and the less abuse there will be. It's in their
About three months ago, one of the leading email service
providers in the SOHO market place published a study
proving that a verified opt-in mailing list was more
responsive, gave rise to less churn among subscribers and
cut spam complaints dramatically.
Much as I hate to be the one to introduce areas of grey into an
otherwise beautiful black-and-white tableau, I'd like to point
out that they do exist.
As an example, a company is intending to launch a new product.
They publicise it in advance on their website. They invite
visitors to the site to fill in their email address and hence
be notified when the product is actually available. It will be
a one-off mailshot. Perhaps they log the IP addresses from which
the requests are received, along with an accurate time.
Should they really then have to send out a mail to confirm that
the user really wants them to send the other mail in a couple of
months' time?
I don't think so; it just wouldn't be a reasonable and sensible
thing to do.
For anything that's going to be sent on an ongoing basis,
however, I'm definitely right with you. But where exactly is the
line?
Cheers,
Nick
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta features
SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com