[SC-Help] Re: Getting balcklisted

[Iain]

This is a very good ppint. Many thanks for it. Point well taken and noted! 
:-)

.../Iain


"Mike Easter" <MikeE at ster.invalid> wrote in message 
news:cs3muv$r69$1 at news.spamcop.net...
> Mike Easter wrote:
>> If I receive an item which is 'purely' confirmatory, not promoting
>> itself or its products or its purpose in any way, and whose entire
>> purpose is to tell me that my address has been entered as desirous of
>> wanting to be on that mailing list -- and, that in order for me to be
>> so subscribed then I must click this link or reply this mail, else
>> the subscription process fails -- then I do not report that as spam.
>
> In fact, if the item also included the IP of the browser who entered the
> email address, I would be notifying the abuse desk of the provider for
> that IP address that their client was bogus subscribing people.  Abuse
> desk definitely don't like that business;  they are very sensitive to
> abuse issues because that is their job, and they are highly likely to
> take action on the bogus subscribing person.  So, the timestamp would be
> helpful too, in case the IP was dynamic.
>
> It is more likely for a person who has been bogus subscribed to 'take
> some action' against the bogus subscriber by notifying hir provider's
> abuse than it is for some kind of 'correspondence' to develop between
> the bogus subscribed and the list manager to cause the list manager to
> be notifying the bogus subscriber's provider.  That is, the list manager
> doesn't know any true answers to why a bogus subscription never got
> confirmed, so they can't notify anyone.  The person who was bogus
> subscribed *knows* that they didn't subscribe, so they are in a position
> to be notifying the provider for the bogus subscriber.
>
> -- 
> Mike Easter
> kibitzer, not SC admin
>