LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (34 lines)
Print Reply
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Sat, 4 Feb 2006 20:18:40 -0500
Content-Disposition:
inline
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
quoted-printable
In-Reply-To:
Content-Type:
text/plain; charset=ISO-8859-1
From:
David Phillips <[log in to unmask]>
On 2/4/06, Roger Burns <[log in to unmask]> wrote:
> Here's an informative article from tomorrow's New York Times:
>
>   http://www.nytimes.com/2006/02/05/technology/05AOL.html
>
> And here's an interesting quote from there:
>
> > Users will be able to specify that unpaid messages from a particular
> > person or company should never be treated as spam, as they can do
> > now.
>
> That might be a saving grace for list mail.  But users will in effect
> have to actively opt out of the new no-more-mass-whitelist AOL policy.
> This may be a significant technical barrier for a number of
> unsophisticated users, no matter how easy it may seem for us technical
> wizards.
>
> Also: while users might be allowed to whitelist addresses that appear
> in the From: field, will they be allowed to do so for the Sender:
> field, which is the only way to identify a list's address in incoming
> mail?  If not, then we Listserv people are still up a creek.

I can't speak to AOL's whitelist process, but using Earthlink as an
example, I can whitelist domains (and, Earthlink's whitelist process
seems to look at more than just the From field)

I have no hopes that AOL's individual whitelist process has any reasonableness.

--
David Phillips
Molon Labe !
35° 46' N , 78° 48'W
Lose Not A Minute!

ATOM RSS1 RSS2