On Thu, Feb 23, 2006 at 04:48:09PM -0500, JamesDR wrote:
Vivek Khera wrote:
On Feb 23, 2006, at 1:08 PM, Mike Jackson wrote:
So, I suppose the question is: How do you deal with getting forwarded
mail through to AOL without being branded as a spammer?
You stop forwarding email to AOL...
Dave Pooser wrote:
If you are seeing the AOL members addresses then I'd like to know
what you did to receive them, because you appear the only one is
several list I belong to that are discussing this very issue that is
seeing those addresses.
I'd also like to get the AOL member's address,
On Thu, 23 Feb 2006, Gene Heskett wrote:
And exactly what, and where can I get this 'verp'? Many mailing lists
I'm on could make good use of this feature.
If you run a mailing list, read the documentation for your program. If you
don't, ask the person who does run it to read the
From: jp [EMAIL PROTECTED]
On Thu, Feb 23, 2006 at 04:48:09PM -0500, JamesDR wrote:
Vivek Khera wrote:
On Feb 23, 2006, at 1:08 PM, Mike Jackson wrote:
So, I suppose the question is: How do you deal with getting forwarded
mail through to AOL without being branded as a spammer?
You stop
On Friday 24 February 2006 20:11, jdow wrote:
From: jp [EMAIL PROTECTED]
On Thu, Feb 23, 2006 at 04:48:09PM -0500, JamesDR wrote:
Vivek Khera wrote:
On Feb 23, 2006, at 1:08 PM, Mike Jackson wrote:
So, I suppose the question is: How do you deal with getting
forwarded mail through to AOL
jdow wrote:
Of course, if AOL gets away with this then they are not a common carrier
anymore. So they become responsible for their content. Sue them for any
bad content and throw their charges in their face as evidence that they
are not a carrier, they are a content service. Nail their sorry
You don't.
Only idiots use AOL. AOL management are idiots, so it is a good match.
One of those idiot users will push the AOL spam button on forwarded spam,
that marks your server as a spam source to AOL admins.
Nothing you can do about that. Once that happens a few times you're done.
Better to
Mike,
You obviously haven't heard all the news about what AOL and Yahoo are
about to do.
First AOL blocked you be cause one or more of those people you
forward mail for has hit that little button that says This is SPAM.
AOL doesn't really care if the user requested the mail to be
On Thursday February 23 2006 1:25 pm, Peter P. Benac wrote:
Mike,
You obviously haven't heard all the news about what AOL and Yahoo are
about to do.
First AOL blocked you be cause one or more of those people you
forward mail for has hit that little button that says This is SPAM.
AOl will send you what they refer to as a TOS alert wherever anyone hits
that spam button. They are even nice enough to attach the offending
message.
They expect you to immediately remove that user from your lists; however,
they will replace every instance of the AOL members mail address from the
Peter P. Benac wrote:
AOl will send you what they refer to as a TOS alert wherever anyone
hits that spam button. They are even nice enough to attach the
offending message.
They expect you to immediately remove that user from your lists;
however, they will replace every instance of the AOL
On 2/23/06, Peter P. Benac [EMAIL PROTECTED] wrote:
Get enough of those TOS messages in one day and they will still block you
IP address and any IP address that you have assigned to you.
FUD. They don't block multiple IPs at once as far as I can tell.
Furthermore, they have already announced
Very true.. I went around and around with AOL over this every issue for
three days.
I will be happy to forward the dang things to you as well. I may get one
or two that have some how escaped the AOL edits. Those I do receive are
somehow buried in a Receive: mail header.
If you are seeing the
Peter P. Benac wrote:
Very true.. I went around and around with AOL over this every issue
for three days.
After inspecting some TOS reports...
Sometimes (not always) the To: field is replaced with Undisclosed Recipients.
Sometimes the To: field is preserved.
Sometimes the email is
I tried that Matthew. It too was changed to [EMAIL PROTECTED]
What I haven't tried is removing the @aol.com.
Peter P. Benac wrote:
Very true.. I went around and around with AOL over this every issue
for three days.
After inspecting some TOS reports...
Sometimes (not always) the To:
I tried that Matthew. It too was changed to [EMAIL PROTECTED]
What I haven't tried is removing the @aol.com.
In a mailing list manager app I wrote, I simply put a MD5 hash of the
address in the headers. Then I have something to check against the
subscriber list that AOL would never remove
Now that idea has some merit :) I am working on getting Majordomo to add
the parsed header but an encrypted one is a better idea.
Thanks..
I tried that Matthew. It too was changed to
[EMAIL PROTECTED]
What I haven't tried is removing the @aol.com.
In a mailing list manager app I wrote, I
Peter P. Benac wrote:
Mike,
You obviously haven't heard all the news about what AOL and Yahoo are
about to do.
First AOL blocked you be cause one or more of those people you
forward mail for has hit that little button that says This is SPAM.
AOL doesn't really care if the user
DAve wrote:
We have not chosen a course of action yet. It looks as if the only
*solution* is to not send any mail to AOL accounts. From a business
standpoint this is not acceptable. But, if AOL users will tag a
confirmation message as Spam, what's an admin to do?
For an outside-the-box kind
No, because then I could use the system to sign you up for lists you
didn't sign up for. The token (step 6) must be sent to the email
address that was submitted in step 2). Mike
At 11:57 AM -0800 2/23/06, [EMAIL PROTECTED] wrote:
DAve wrote:
We have not chosen a course of action yet. It
Michael Clark wrote:
No, because then I could use the system to sign you up for lists you
didn't sign up for. The token (step 6) must be sent to the email
address that was submitted in step 2). Mike
There are two distinct tokens. One embedded in the email address the user has
to send to, and
Peter P. Benac wrote:
Confirmation elimates bad addresses. The major problem comes
from people too lazy to unsubscribe from a list. They just hit the
spam
button. AOL refuses to acknowledge that is happens. Even when they
were shown the e-mail that their member marked as spam.
Well...
Don't tempt me, though that would pay for the goodmail payments.
Peter P. Benac wrote:
Confirmation elimates bad addresses. The major problem comes
from people too lazy to unsubscribe from a list. They just hit the
spam
button. AOL refuses to acknowledge that is happens. Even when
[EMAIL PROTECTED] wrote:
DAve wrote:
We have not chosen a course of action yet. It looks as if the only
*solution* is to not send any mail to AOL accounts. From a business
standpoint this is not acceptable. But, if AOL users will tag a
confirmation message as Spam, what's an admin to do?
For
On Thu, 23 Feb 2006, Mike Jackson wrote:
that AOL would never remove from the headers. Now if only I could make
Mailman do the same thing...
Enable verp for the list. This sends out every e-mail with a custom
return-address, which you can use to tell who submitted the mail as spam.
On Feb 23, 2006, at 1:08 PM, Mike Jackson wrote:
So, I suppose the question is: How do you deal with getting
forwarded mail through to AOL without being branded as a spammer?
You stop forwarding email to AOL... really.
Other option is to crank up the SA pickiness and tell the customers
On Feb 23, 2006, at 1:25 PM, Peter P. Benac wrote:
Now AOL and Yahoo are going to join forces with GOODMAIL.COM.
If you
want to guarantee delivery to AOL then you must pay homage to
GOODMAIL.COM at a rate of .25 to 1 cent per message. At the same time
they will tighten filters for
Vivek Khera wrote:
On Feb 23, 2006, at 1:08 PM, Mike Jackson wrote:
So, I suppose the question is: How do you deal with getting forwarded
mail through to AOL without being branded as a spammer?
You stop forwarding email to AOL... really.
Other option is to crank up the SA pickiness and
Michael Clark a écrit :
No, because then I could use the system to sign you up for lists you
didn't sign up for. The token (step 6) must be sent to the email address
that was submitted in step 2). Mike
I guess there is no solution for the first message (requesting
confirmation by sending
[EMAIL PROTECTED] a écrit :
Michael Clark wrote:
No, because then I could use the system to sign you up for lists you
didn't sign up for. The token (step 6) must be sent to the email
address that was submitted in step 2). Mike
There are two distinct tokens. One embedded in the email
mouss wrote:
In the case of an aol address, one may require that the browser
connected from an aol IP.
Not practical. AOL offers a lower bring your own connection rate for
people who want to keep the app and the email, but have broadband access
through another provider. As I understand it,
If you are seeing the AOL members addresses then I'd like to know what you
did to receive them, because you appear the only one is several list I
belong to that are discussing this very issue that is seeing those
addresses.
I'd also like to get the AOL member's address, 'cause I don't get
On Thursday 23 February 2006 15:48, Christopher X. Candreva wrote:
On Thu, 23 Feb 2006, Mike Jackson wrote:
that AOL would never remove from the headers. Now if only I could
make Mailman do the same thing...
Enable verp for the list. This sends out every e-mail with a custom
return-address,
33 matches
Mail list logo
