On 1/31/98 11:29 AM, David W. Tamkin <dattier@wwa.com> wrote...
>You responded to Bob Brown's post,
>
>| The solution, if you care, is to have instructions somewhere for AOL
>| members on how to un-block your list. I have detailed instructions that
>| /I/ use if anyone wants to email me privately for them.
>
>How is the list manager supposed to deliver those instructions to the
>AOL user?
The best place to put the instructions is any place where people find out
about your list, such as a web site. If you get them before they
subscribe, you'll head off the problem. You can also mention it in your
welcome message for the sake of people who who haven't blocked mail yet,
but might in the future. Of course, this won't do any good for folks who
don't save the welcome message, but that's another topic.
If you have an AOL account, you can try sending them a message through
the AOL mail system, if it's that important.
>Bob had written,
>
>| >OK, AOL... here's what I want you to do about this: Please fix your
>| >mailer system so that your customers can't send mail *to* a domain
>| >they've blocked.
>
>And you replied,
>
>| While I agree with your reasoning (though I wouldn't want it implemented
>| for personal reasons), I don't see that working since Return-Path often
>| has nothing to do with To.
>
>What would you feel about a setup where AOL dispatches the letter anyway but
>(1) warns the sender that it probably cannot be answered and (2) warns the
>recipient [by adding text to the top of the body] that it probably cannot be
>answered?
Once again, since From and Return-Path might have nothing to do with each
other, this won't work.
--
Adam Bailey | Chicago, Illinois
-=-=-=-=-=-=-=-=-| "Do not take life too seriously;
adamb@tezcat.com | you will never get out of it alive."
adamkb@aol.com | - Elbert Hubbard
Finger for PGP | http://www.tezcat.com/~adamb
Follow-Ups:
|
|
