Re: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-07 Thread Darin Cox 
We add a header via DJM to display the intended recipient so we can track
who reported it as spam in AOL, however, this doesn't work for lists except
to identify the list.

Once we've identified the user or list we contact the user or list owner to
let them know of the problem, and that if they do not avoid future reports
for mail we forward for them and/or use our spam filtering (some customers
opt out of it), then we will be forced to remove any forwarding or list
subscriptions for AOL users.  Once they understand that such reports can
damage the ability to send to AOL at all, they usually comply without
further incident.

As long as the signal to noise ratio is low enough AOL doesn't start
blocking, so a few reports here and there won't hurt you...but we respond to
every one to keep any problems from escalating.

Darin.


- Original Message - 
From: Steve Flook [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 06, 2004 12:43 PM
Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL


On this note, what are other's policy on forwarding client's addresses
to AOL accounts?  We signed up with this feedback loop program quite
some time and realized that 95% of the reported spam's where coming
from forwarded messages to AOL accounts.  In the event of forwarded
messages, our IMail box takes the blame instead of the original MTA.

I have considered creating a policy of not allowing mail forwarding to
AOL accounts for fear of getting blacklisted from AOL.

Steve

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Don Schreiner
 Sent: Wednesday, October 06, 2004 11:37 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [Declude.JunkMail] Client TOS Notifications from AOL

 Kami   John,

 Thanks a ton guys! That was me that registered on the AOL
 feedback loop using our abuse addy, but going back months ago
 and did not realize. So much to keep up with battling Spam!
 Just a few more points on my Declude weight and would not
 have made it to AOL - ohhh well - will keep tweaking our config.

 -Don

 - Original Message -
 From: John Tolmachoff (Lists) [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, October 06, 2004 10:31 AM
 Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL


 Some one at your company signed up and registered to receive
 these feedback
 loop messages.

 http://postmaster.info.aol.com/tools/fbl.html

 John Tolmachoff
 Engineer/Consultant/Owner
 eServices For You

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
  [EMAIL PROTECTED] On Behalf Of Don Schreiner
  Sent: Wednesday, October 06, 2004 7:09 AM
  To: [EMAIL PROTECTED]
  Subject: [Declude.JunkMail] Client TOS Notifications from AOL
 
  Declude Folks,
 
  I need some help figuring out why we are receiving e-mails from
  [EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To
 address
  is [EMAIL PROTECTED] I am not sure if these
 are coming back
 to
  me in our abuse or postmaster account? There is nothing in
 the body of the
  e-mail, only an attachment of e-mail apparently getting
 rejected. Anyone
  else seeing these? The client we host forwards his e-mail
 automatically to
  his AOL account. For example, below is the header of an
 e-mail that was
  attached whereas a spam e-amail appears to have been sent
 to our client
  (lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
  vacant.spiderhost.com is router) which was forwarded to his
 AOL account.
  Unfortunately it did not weight enough under our Declude config, nor
 Sniffer
  to get held as Spam. Any ideas what AOL is doing or what I
 should do to
  eliminate these most appreciated. Worried about getting on
 the wrong side
 of
  AOL. Thanks.
 
  -Don
 
  Return-Path: [EMAIL PROTECTED]
  Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com
 [172.20.64.41])
  by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id
 MAILINXA31-7341621d0d322;
  Tue, 05 Oct 2004 00:03:36 -0400
  Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com
 [65.57.241.197])
  by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
  MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
  Received: from SMTP32-FWD by lamphier.com
(SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
  Received: from pelxavirus3.terra.com.pe [200.48.36.5] by
 SNEEZY.XEROCOM.NET
  with ESMTP
(SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
  Received: from anamaria (unknown [200.106.79.108])
   by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
   Mon,  4 Oct 2004 23:07:07 -0500 (PET)
  Message-ID: [EMAIL PROTECTED]
  To: Undisclosed Recipients
  From: Anni [EMAIL PROTECTED]
  Subject: Proposal
  Date: Mon, 4 Oct 2004 23:03:21 -0500
  MIME-Version: 1.0
  Content-type: text/plain; charset=US-ASCII
  Content-Transfer-Encoding: quoted-printable
  X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
  X-RBL-Warning: HELOBOGUS: Domain

RE: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-07 Thread Steve Flook 
Thanks for the tip Darin.  We've only been blacklisted for about 4 hours
once before.  I don't know the exact threshold either for when they
start blocking unfortunately.  Second level AOL techs couldn't tell me
either when I contacted them.

Steve

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox
 Sent: Thursday, October 07, 2004 10:53 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [Declude.JunkMail] Client TOS Notifications from AOL
 
 We add a header via DJM to display the intended recipient so 
 we can track who reported it as spam in AOL, however, this 
 doesn't work for lists except to identify the list.
 
 Once we've identified the user or list we contact the user or 
 list owner to let them know of the problem, and that if they 
 do not avoid future reports for mail we forward for them 
 and/or use our spam filtering (some customers opt out of it), 
 then we will be forced to remove any forwarding or list 
 subscriptions for AOL users.  Once they understand that such 
 reports can damage the ability to send to AOL at all, they 
 usually comply without further incident.
 
 As long as the signal to noise ratio is low enough AOL 
 doesn't start blocking, so a few reports here and there won't 
 hurt you...but we respond to every one to keep any problems 
 from escalating.
 
 Darin.
 
 
 - Original Message -
 From: Steve Flook [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, October 06, 2004 12:43 PM
 Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL
 
 
 On this note, what are other's policy on forwarding client's addresses
 to AOL accounts?  We signed up with this feedback loop program quite
 some time and realized that 95% of the reported spam's where coming
 from forwarded messages to AOL accounts.  In the event of forwarded
 messages, our IMail box takes the blame instead of the original MTA.
 
 I have considered creating a policy of not allowing mail forwarding to
 AOL accounts for fear of getting blacklisted from AOL.
 
 Steve
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.

Re: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-07 Thread Darin Cox 
I haven't had it happen, but I've been told that with the feedback loop in
place they send you a warning when you near the threshold for being
blacklisted.  I imagine those thresholds are dynamic and/or adjustable,
which is probably why they can't tell you what they are.

Darin.


- Original Message - 
From: Steve Flook [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 07, 2004 11:36 AM
Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL


Thanks for the tip Darin.  We've only been blacklisted for about 4 hours
once before.  I don't know the exact threshold either for when they
start blocking unfortunately.  Second level AOL techs couldn't tell me
either when I contacted them.

Steve

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox
 Sent: Thursday, October 07, 2004 10:53 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [Declude.JunkMail] Client TOS Notifications from AOL

 We add a header via DJM to display the intended recipient so
 we can track who reported it as spam in AOL, however, this
 doesn't work for lists except to identify the list.

 Once we've identified the user or list we contact the user or
 list owner to let them know of the problem, and that if they
 do not avoid future reports for mail we forward for them
 and/or use our spam filtering (some customers opt out of it),
 then we will be forced to remove any forwarding or list
 subscriptions for AOL users.  Once they understand that such
 reports can damage the ability to send to AOL at all, they
 usually comply without further incident.

 As long as the signal to noise ratio is low enough AOL
 doesn't start blocking, so a few reports here and there won't
 hurt you...but we respond to every one to keep any problems
 from escalating.

 Darin.


 - Original Message -
 From: Steve Flook [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, October 06, 2004 12:43 PM
 Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL


 On this note, what are other's policy on forwarding client's addresses
 to AOL accounts?  We signed up with this feedback loop program quite
 some time and realized that 95% of the reported spam's where coming
 from forwarded messages to AOL accounts.  In the event of forwarded
 messages, our IMail box takes the blame instead of the original MTA.

 I have considered creating a policy of not allowing mail forwarding to
 AOL accounts for fear of getting blacklisted from AOL.

 Steve
---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.

RE: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-06 Thread John Tolmachoff \(Lists\) 
Some one at your company signed up and registered to receive these feedback
loop messages.

http://postmaster.info.aol.com/tools/fbl.html

John Tolmachoff
Engineer/Consultant/Owner
eServices For You

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
 [EMAIL PROTECTED] On Behalf Of Don Schreiner
 Sent: Wednesday, October 06, 2004 7:09 AM
 To: [EMAIL PROTECTED]
 Subject: [Declude.JunkMail] Client TOS Notifications from AOL
 
 Declude Folks,
 
 I need some help figuring out why we are receiving e-mails from
 [EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To
address
 is [EMAIL PROTECTED] I am not sure if these are coming back
to
 me in our abuse or postmaster account? There is nothing in the body of the
 e-mail, only an attachment of e-mail apparently getting rejected. Anyone
 else seeing these? The client we host forwards his e-mail automatically to
 his AOL account. For example, below is the header of an e-mail that was
 attached whereas a spam e-amail appears to have been sent to our client
 (lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
 vacant.spiderhost.com is router) which was forwarded to his AOL account.
 Unfortunately it did not weight enough under our Declude config, nor
Sniffer
 to get held as Spam. Any ideas what AOL is doing or what I should do to
 eliminate these most appreciated. Worried about getting on the wrong side
of
 AOL. Thanks.
 
 -Don
 
 Return-Path: [EMAIL PROTECTED]
 Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com [172.20.64.41])
 by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id
MAILINXA31-7341621d0d322;
 Tue, 05 Oct 2004 00:03:36 -0400
 Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com [65.57.241.197])
 by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
 MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
 Received: from SMTP32-FWD by lamphier.com
   (SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
 Received: from pelxavirus3.terra.com.pe [200.48.36.5] by
SNEEZY.XEROCOM.NET
 with ESMTP
   (SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
 Received: from anamaria (unknown [200.106.79.108])
  by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
  Mon,  4 Oct 2004 23:07:07 -0500 (PET)
 Message-ID: [EMAIL PROTECTED]
 To: Undisclosed Recipients
 From: Anni [EMAIL PROTECTED]
 Subject: Proposal
 Date: Mon, 4 Oct 2004 23:03:21 -0500
 MIME-Version: 1.0
 Content-type: text/plain; charset=US-ASCII
 Content-Transfer-Encoding: quoted-printable
 X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
 X-RBL-Warning: HELOBOGUS: Domain pelxavirus3.terra.com.pe has no MX or A
 records [0301].
 X-RBL-Warning: WEIGHT1-9: Total weight between 1 and 9.
 X-Declude-Sender: [EMAIL PROTECTED] [200.48.36.5]
 X-Declude-Spoolname: D1bf42ba100b8f0c3.SMD
 X-Note: CompBiz scanned with Declude JunkMail.
 X-Spam-Tests-Failed: NOABUSE, HELOBOGUS, WEIGHT1-9 [7].
 X-Note: This E-mail was sent from smtp7.terra.com.pe ([200.48.36.5]).
 X-Sender: Sender of E-mail: [EMAIL PROTECTED]
 X-Note: RevDNS Remote Server smtp7.terra.com.pe ([200.48.36.5]).
 X-AOL-IP: 65.57.241.197
 X-Mailer: Unknown (No Version)
 
 Dear Customer,
 =20
 Be the very first listing in the top search engines immediately.
 =20
 Our company will now place any business with a qualified website
 permanently=
  at the top of the major search engines guaranteed never to move.  This
 prom=
 otion includes unlimited traffic and is not going to last long.  If you
 are=20=
 interested in being guaranteed first position in the top search engines at
 a=
  promotional fee, please contact us promptly to find out if you qualify
 via=20=
 email at   [EMAIL PROTECTED]   AND INCLUDE THE URL(s) YOUR ARE INTERESTED
 I=
 N PLACING.  This is not pay per click.=20
 
 The following are examples on Yahoo!, MSN and Alta Vista:
 =20
 Company:  Oahu Dive Center
 URL:   http://oahudivecenter.com
 keyword:   oahu scuba diving
 =20
 Company:  California Moves.com
 URL:   http://steph.cbsocal.com
 keyword:   find a home southern california
 =20
 Sincerely,
 =20
 IGN
 The Search Engine Promotional Consultants
 
 
 ---
 [This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]
 
 ---
 This E-mail came from the Declude.JunkMail mailing list.  To
 unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
 type unsubscribe Declude.JunkMail.  The archives can be found
 at http://www.mail-archive.com.

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.

Re: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-06 Thread Don Schreiner 
Kami   John,

Thanks a ton guys! That was me that registered on the AOL feedback loop
using our abuse addy, but going back months ago and did not realize. So much
to keep up with battling Spam! Just a few more points on my Declude weight
and would not have made it to AOL - ohhh well - will keep tweaking our
config.

-Don

- Original Message - 
From: John Tolmachoff (Lists) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 06, 2004 10:31 AM
Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL


Some one at your company signed up and registered to receive these feedback
loop messages.

http://postmaster.info.aol.com/tools/fbl.html

John Tolmachoff
Engineer/Consultant/Owner
eServices For You

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
 [EMAIL PROTECTED] On Behalf Of Don Schreiner
 Sent: Wednesday, October 06, 2004 7:09 AM
 To: [EMAIL PROTECTED]
 Subject: [Declude.JunkMail] Client TOS Notifications from AOL

 Declude Folks,

 I need some help figuring out why we are receiving e-mails from
 [EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To
address
 is [EMAIL PROTECTED] I am not sure if these are coming back
to
 me in our abuse or postmaster account? There is nothing in the body of the
 e-mail, only an attachment of e-mail apparently getting rejected. Anyone
 else seeing these? The client we host forwards his e-mail automatically to
 his AOL account. For example, below is the header of an e-mail that was
 attached whereas a spam e-amail appears to have been sent to our client
 (lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
 vacant.spiderhost.com is router) which was forwarded to his AOL account.
 Unfortunately it did not weight enough under our Declude config, nor
Sniffer
 to get held as Spam. Any ideas what AOL is doing or what I should do to
 eliminate these most appreciated. Worried about getting on the wrong side
of
 AOL. Thanks.

 -Don

 Return-Path: [EMAIL PROTECTED]
 Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com [172.20.64.41])
 by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id
MAILINXA31-7341621d0d322;
 Tue, 05 Oct 2004 00:03:36 -0400
 Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com [65.57.241.197])
 by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
 MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
 Received: from SMTP32-FWD by lamphier.com
   (SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
 Received: from pelxavirus3.terra.com.pe [200.48.36.5] by
SNEEZY.XEROCOM.NET
 with ESMTP
   (SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
 Received: from anamaria (unknown [200.106.79.108])
  by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
  Mon,  4 Oct 2004 23:07:07 -0500 (PET)
 Message-ID: [EMAIL PROTECTED]
 To: Undisclosed Recipients
 From: Anni [EMAIL PROTECTED]
 Subject: Proposal
 Date: Mon, 4 Oct 2004 23:03:21 -0500
 MIME-Version: 1.0
 Content-type: text/plain; charset=US-ASCII
 Content-Transfer-Encoding: quoted-printable
 X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
 X-RBL-Warning: HELOBOGUS: Domain pelxavirus3.terra.com.pe has no MX or A
 records [0301].
 X-RBL-Warning: WEIGHT1-9: Total weight between 1 and 9.
 X-Declude-Sender: [EMAIL PROTECTED] [200.48.36.5]
 X-Declude-Spoolname: D1bf42ba100b8f0c3.SMD
 X-Note: CompBiz scanned with Declude JunkMail.
 X-Spam-Tests-Failed: NOABUSE, HELOBOGUS, WEIGHT1-9 [7].
 X-Note: This E-mail was sent from smtp7.terra.com.pe ([200.48.36.5]).
 X-Sender: Sender of E-mail: [EMAIL PROTECTED]
 X-Note: RevDNS Remote Server smtp7.terra.com.pe ([200.48.36.5]).
 X-AOL-IP: 65.57.241.197
 X-Mailer: Unknown (No Version)

 Dear Customer,
 =20
 Be the very first listing in the top search engines immediately.
 =20
 Our company will now place any business with a qualified website
 permanently=
  at the top of the major search engines guaranteed never to move.  This
 prom=
 otion includes unlimited traffic and is not going to last long.  If you
 are=20=
 interested in being guaranteed first position in the top search engines at
 a=
  promotional fee, please contact us promptly to find out if you qualify
 via=20=
 email at   [EMAIL PROTECTED]   AND INCLUDE THE URL(s) YOUR ARE INTERESTED
 I=
 N PLACING.  This is not pay per click.=20

 The following are examples on Yahoo!, MSN and Alta Vista:
 =20
 Company:  Oahu Dive Center
 URL:   http://oahudivecenter.com
 keyword:   oahu scuba diving
 =20
 Company:  California Moves.com
 URL:   http://steph.cbsocal.com
 keyword:   find a home southern california
 =20
 Sincerely,
 =20
 IGN
 The Search Engine Promotional Consultants


 ---
 [This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]

 ---
 This E-mail came from the Declude.JunkMail mailing list.  To
 unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
 type unsubscribe Declude.JunkMail.  The archives

Re: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-06 Thread support 
Essentially someone received an email in their AOL acount and marked it as 
SPAM.   Since you setup a feedback loop with AOL they will now send you 
every instance of an email that was reported as SPAM by one of their 
members. 

Darrell

Check out http://www.invariantsystems.com for utilities for Declude And 
Imail.  IMail/Declude Overflow Queue Monitoring, MRTG Integration, and Log 
Parsers. 

Don Schreiner writes: 

Declude Folks, 

I need some help figuring out why we are receiving e-mails from
[EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To address
is [EMAIL PROTECTED] I am not sure if these are coming back to
me in our abuse or postmaster account? There is nothing in the body of the
e-mail, only an attachment of e-mail apparently getting rejected. Anyone
else seeing these? The client we host forwards his e-mail automatically to
his AOL account. For example, below is the header of an e-mail that was
attached whereas a spam e-amail appears to have been sent to our client
(lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
vacant.spiderhost.com is router) which was forwarded to his AOL account.
Unfortunately it did not weight enough under our Declude config, nor Sniffer
to get held as Spam. Any ideas what AOL is doing or what I should do to
eliminate these most appreciated. Worried about getting on the wrong side of
AOL. Thanks. 

-Don 

Return-Path: [EMAIL PROTECTED]
Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com [172.20.64.41])
by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id MAILINXA31-7341621d0d322;
Tue, 05 Oct 2004 00:03:36 -0400
Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com [65.57.241.197])
by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
Received: from SMTP32-FWD by lamphier.com
  (SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
Received: from pelxavirus3.terra.com.pe [200.48.36.5] by SNEEZY.XEROCOM.NET
with ESMTP
  (SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
Received: from anamaria (unknown [200.106.79.108])
 by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
 Mon,  4 Oct 2004 23:07:07 -0500 (PET)
Message-ID: [EMAIL PROTECTED]
To: Undisclosed Recipients
From: Anni [EMAIL PROTECTED]
Subject: Proposal
Date: Mon, 4 Oct 2004 23:03:21 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
X-RBL-Warning: HELOBOGUS: Domain pelxavirus3.terra.com.pe has no MX or A
records [0301].
X-RBL-Warning: WEIGHT1-9: Total weight between 1 and 9.
X-Declude-Sender: [EMAIL PROTECTED] [200.48.36.5]
X-Declude-Spoolname: D1bf42ba100b8f0c3.SMD
X-Note: CompBiz scanned with Declude JunkMail.
X-Spam-Tests-Failed: NOABUSE, HELOBOGUS, WEIGHT1-9 [7].
X-Note: This E-mail was sent from smtp7.terra.com.pe ([200.48.36.5]).
X-Sender: Sender of E-mail: [EMAIL PROTECTED]
X-Note: RevDNS Remote Server smtp7.terra.com.pe ([200.48.36.5]).
X-AOL-IP: 65.57.241.197
X-Mailer: Unknown (No Version) 

Dear Customer,
=20
Be the very first listing in the top search engines immediately.
=20
Our company will now place any business with a qualified website
permanently=
 at the top of the major search engines guaranteed never to move.  This
prom=
otion includes unlimited traffic and is not going to last long.  If you
are=20=
interested in being guaranteed first position in the top search engines at
a=
 promotional fee, please contact us promptly to find out if you qualify
via=20=
email at   [EMAIL PROTECTED]   AND INCLUDE THE URL(s) YOUR ARE INTERESTED
I=
N PLACING.  This is not pay per click.=20 

The following are examples on Yahoo!, MSN and Alta Vista:
=20
Company:  Oahu Dive Center
URL:   http://oahudivecenter.com
keyword:   oahu scuba diving
=20
Company:  California Moves.com
URL:   http://steph.cbsocal.com
keyword:   find a home southern california
=20
Sincerely,
=20
IGN
The Search Engine Promotional Consultants 

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] 

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail.  The archives can be found
at http://www.mail-archive.com.

RE: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-06 Thread Steve Flook 
On this note, what are other's policy on forwarding client's addresses
to AOL accounts?  We signed up with this feedback loop program quite
some time and realized that 95% of the reported spam's where coming
from forwarded messages to AOL accounts.  In the event of forwarded
messages, our IMail box takes the blame instead of the original MTA.

I have considered creating a policy of not allowing mail forwarding to
AOL accounts for fear of getting blacklisted from AOL.

Steve 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Don Schreiner
 Sent: Wednesday, October 06, 2004 11:37 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [Declude.JunkMail] Client TOS Notifications from AOL
 
 Kami   John,
 
 Thanks a ton guys! That was me that registered on the AOL 
 feedback loop using our abuse addy, but going back months ago 
 and did not realize. So much to keep up with battling Spam! 
 Just a few more points on my Declude weight and would not 
 have made it to AOL - ohhh well - will keep tweaking our config.
 
 -Don
 
 - Original Message -
 From: John Tolmachoff (Lists) [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, October 06, 2004 10:31 AM
 Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL
 
 
 Some one at your company signed up and registered to receive 
 these feedback
 loop messages.
 
 http://postmaster.info.aol.com/tools/fbl.html
 
 John Tolmachoff
 Engineer/Consultant/Owner
 eServices For You
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
  [EMAIL PROTECTED] On Behalf Of Don Schreiner
  Sent: Wednesday, October 06, 2004 7:09 AM
  To: [EMAIL PROTECTED]
  Subject: [Declude.JunkMail] Client TOS Notifications from AOL
 
  Declude Folks,
 
  I need some help figuring out why we are receiving e-mails from
  [EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To
 address
  is [EMAIL PROTECTED] I am not sure if these 
 are coming back
 to
  me in our abuse or postmaster account? There is nothing in 
 the body of the
  e-mail, only an attachment of e-mail apparently getting 
 rejected. Anyone
  else seeing these? The client we host forwards his e-mail 
 automatically to
  his AOL account. For example, below is the header of an 
 e-mail that was
  attached whereas a spam e-amail appears to have been sent 
 to our client
  (lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
  vacant.spiderhost.com is router) which was forwarded to his 
 AOL account.
  Unfortunately it did not weight enough under our Declude config, nor
 Sniffer
  to get held as Spam. Any ideas what AOL is doing or what I 
 should do to
  eliminate these most appreciated. Worried about getting on 
 the wrong side
 of
  AOL. Thanks.
 
  -Don
 
  Return-Path: [EMAIL PROTECTED]
  Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com 
 [172.20.64.41])
  by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id
 MAILINXA31-7341621d0d322;
  Tue, 05 Oct 2004 00:03:36 -0400
  Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com 
 [65.57.241.197])
  by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
  MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
  Received: from SMTP32-FWD by lamphier.com
(SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
  Received: from pelxavirus3.terra.com.pe [200.48.36.5] by
 SNEEZY.XEROCOM.NET
  with ESMTP
(SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
  Received: from anamaria (unknown [200.106.79.108])
   by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
   Mon,  4 Oct 2004 23:07:07 -0500 (PET)
  Message-ID: [EMAIL PROTECTED]
  To: Undisclosed Recipients
  From: Anni [EMAIL PROTECTED]
  Subject: Proposal
  Date: Mon, 4 Oct 2004 23:03:21 -0500
  MIME-Version: 1.0
  Content-type: text/plain; charset=US-ASCII
  Content-Transfer-Encoding: quoted-printable
  X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
  X-RBL-Warning: HELOBOGUS: Domain pelxavirus3.terra.com.pe 
 has no MX or A
  records [0301].
  X-RBL-Warning: WEIGHT1-9: Total weight between 1 and 9.
  X-Declude-Sender: [EMAIL PROTECTED] [200.48.36.5]
  X-Declude-Spoolname: D1bf42ba100b8f0c3.SMD
  X-Note: CompBiz scanned with Declude JunkMail.
  X-Spam-Tests-Failed: NOABUSE, HELOBOGUS, WEIGHT1-9 [7].
  X-Note: This E-mail was sent from smtp7.terra.com.pe 
 ([200.48.36.5]).
  X-Sender: Sender of E-mail: [EMAIL PROTECTED]
  X-Note: RevDNS Remote Server smtp7.terra.com.pe ([200.48.36.5]).
  X-AOL-IP: 65.57.241.197
  X-Mailer: Unknown (No Version)
 
  Dear Customer,
  =20
  Be the very first listing in the top search engines immediately.
  =20
  Our company will now place any business with a qualified website
  permanently=
   at the top of the major search engines guaranteed never to 
 move.  This
  prom=
  otion includes unlimited traffic and is not going to last 
 long.  If you
  are=20=
  interested in being guaranteed first position in the top 
 search engines

RE: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-06 Thread John Tolmachoff \(Lists\) 
What I do if the message is legit is forward that notice to the sender and
recipient explaining the AOL report spam button to please take care of this
issue or forwarding messages to AOL addresses will be banned.

John Tolmachoff
Engineer/Consultant/Owner
eServices For You

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
 [EMAIL PROTECTED] On Behalf Of Steve Flook
 Sent: Wednesday, October 06, 2004 9:43 AM
 To: [EMAIL PROTECTED]
 Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL
 
 On this note, what are other's policy on forwarding client's addresses
 to AOL accounts?  We signed up with this feedback loop program quite
 some time and realized that 95% of the reported spam's where coming
 from forwarded messages to AOL accounts.  In the event of forwarded
 messages, our IMail box takes the blame instead of the original MTA.
 
 I have considered creating a policy of not allowing mail forwarding to
 AOL accounts for fear of getting blacklisted from AOL.
 
 Steve
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Don Schreiner
  Sent: Wednesday, October 06, 2004 11:37 AM
  To: [EMAIL PROTECTED]
  Subject: Re: [Declude.JunkMail] Client TOS Notifications from AOL
 
  Kami   John,
 
  Thanks a ton guys! That was me that registered on the AOL
  feedback loop using our abuse addy, but going back months ago
  and did not realize. So much to keep up with battling Spam!
  Just a few more points on my Declude weight and would not
  have made it to AOL - ohhh well - will keep tweaking our config.
 
  -Don
 
  - Original Message -
  From: John Tolmachoff (Lists) [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Wednesday, October 06, 2004 10:31 AM
  Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL
 
 
  Some one at your company signed up and registered to receive
  these feedback
  loop messages.
 
  http://postmaster.info.aol.com/tools/fbl.html
 
  John Tolmachoff
  Engineer/Consultant/Owner
  eServices For You
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
   [EMAIL PROTECTED] On Behalf Of Don Schreiner
   Sent: Wednesday, October 06, 2004 7:09 AM
   To: [EMAIL PROTECTED]
   Subject: [Declude.JunkMail] Client TOS Notifications from AOL
  
   Declude Folks,
  
   I need some help figuring out why we are receiving e-mails from
   [EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To
  address
   is [EMAIL PROTECTED] I am not sure if these
  are coming back
  to
   me in our abuse or postmaster account? There is nothing in
  the body of the
   e-mail, only an attachment of e-mail apparently getting
  rejected. Anyone
   else seeing these? The client we host forwards his e-mail
  automatically to
   his AOL account. For example, below is the header of an
  e-mail that was
   attached whereas a spam e-amail appears to have been sent
  to our client
   (lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
   vacant.spiderhost.com is router) which was forwarded to his
  AOL account.
   Unfortunately it did not weight enough under our Declude config, nor
  Sniffer
   to get held as Spam. Any ideas what AOL is doing or what I
  should do to
   eliminate these most appreciated. Worried about getting on
  the wrong side
  of
   AOL. Thanks.
  
   -Don
  
   Return-Path: [EMAIL PROTECTED]
   Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com
  [172.20.64.41])
   by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id
  MAILINXA31-7341621d0d322;
   Tue, 05 Oct 2004 00:03:36 -0400
   Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com
  [65.57.241.197])
   by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
   MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
   Received: from SMTP32-FWD by lamphier.com
 (SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
   Received: from pelxavirus3.terra.com.pe [200.48.36.5] by
  SNEEZY.XEROCOM.NET
   with ESMTP
 (SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
   Received: from anamaria (unknown [200.106.79.108])
by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
Mon,  4 Oct 2004 23:07:07 -0500 (PET)
   Message-ID: [EMAIL PROTECTED]
   To: Undisclosed Recipients
   From: Anni [EMAIL PROTECTED]
   Subject: Proposal
   Date: Mon, 4 Oct 2004 23:03:21 -0500
   MIME-Version: 1.0
   Content-type: text/plain; charset=US-ASCII
   Content-Transfer-Encoding: quoted-printable
   X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
   X-RBL-Warning: HELOBOGUS: Domain pelxavirus3.terra.com.pe
  has no MX or A
   records [0301].
   X-RBL-Warning: WEIGHT1-9: Total weight between 1 and 9.
   X-Declude-Sender: [EMAIL PROTECTED] [200.48.36.5]
   X-Declude-Spoolname: D1bf42ba100b8f0c3.SMD
   X-Note: CompBiz scanned with Declude JunkMail.
   X-Spam-Tests-Failed: NOABUSE, HELOBOGUS, WEIGHT1-9 [7].
   X-Note: This E-mail was sent from smtp7.terra.com.pe

RE: [Declude.JunkMail] Client TOS Notifications from AOL

2004-10-06 Thread Don Schreiner 
Good question and I am curious too. We actually have a no-forwarding
e-mail policy and not just to AOL. But... sometimes the customer
dictates what they want or will go elsewhere and we then allow on a
case-by-case basis. If we allowed for every customer I bet we would be
blacklisted already. I am still fearful AOL may blacklist on what little
traffic we do have getting forwarded. Thanks.

-Don

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Flook
Sent: Wednesday, October 06, 2004 12:43 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL

On this note, what are other's policy on forwarding client's addresses
to AOL accounts?  We signed up with this feedback loop program quite
some time and realized that 95% of the reported spam's where coming
from forwarded messages to AOL accounts.  In the event of forwarded
messages, our IMail box takes the blame instead of the original MTA.

I have considered creating a policy of not allowing mail forwarding to
AOL accounts for fear of getting blacklisted from AOL.

Steve 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Don Schreiner
 Sent: Wednesday, October 06, 2004 11:37 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [Declude.JunkMail] Client TOS Notifications from AOL
 
 Kami   John,
 
 Thanks a ton guys! That was me that registered on the AOL 
 feedback loop using our abuse addy, but going back months ago 
 and did not realize. So much to keep up with battling Spam! 
 Just a few more points on my Declude weight and would not 
 have made it to AOL - ohhh well - will keep tweaking our config.
 
 -Don
 
 - Original Message -
 From: John Tolmachoff (Lists) [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, October 06, 2004 10:31 AM
 Subject: RE: [Declude.JunkMail] Client TOS Notifications from AOL
 
 
 Some one at your company signed up and registered to receive 
 these feedback
 loop messages.
 
 http://postmaster.info.aol.com/tools/fbl.html
 
 John Tolmachoff
 Engineer/Consultant/Owner
 eServices For You
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
  [EMAIL PROTECTED] On Behalf Of Don Schreiner
  Sent: Wednesday, October 06, 2004 7:09 AM
  To: [EMAIL PROTECTED]
  Subject: [Declude.JunkMail] Client TOS Notifications from AOL
 
  Declude Folks,
 
  I need some help figuring out why we are receiving e-mails from
  [EMAIL PROTECTED] Subject Line: Client TOS Notification, and the Sent To
 address
  is [EMAIL PROTECTED] I am not sure if these 
 are coming back
 to
  me in our abuse or postmaster account? There is nothing in 
 the body of the
  e-mail, only an attachment of e-mail apparently getting 
 rejected. Anyone
  else seeing these? The client we host forwards his e-mail 
 automatically to
  his AOL account. For example, below is the header of an 
 e-mail that was
  attached whereas a spam e-amail appears to have been sent 
 to our client
  (lamphier.com) hosted on our IMail server (sneezy.xerocom.net -
  vacant.spiderhost.com is router) which was forwarded to his 
 AOL account.
  Unfortunately it did not weight enough under our Declude config, nor
 Sniffer
  to get held as Spam. Any ideas what AOL is doing or what I 
 should do to
  eliminate these most appreciated. Worried about getting on 
 the wrong side
 of
  AOL. Thanks.
 
  -Don
 
  Return-Path: [EMAIL PROTECTED]
  Received: from  rly-xa05.mx.aol.com (rly-xa05.mail.aol.com 
 [172.20.64.41])
  by air-xa03.mail.aol.com (v101_r1.4) with ESMTP id
 MAILINXA31-7341621d0d322;
  Tue, 05 Oct 2004 00:03:36 -0400
  Received: from  SNEEZY.XEROCOM.NET (vacant.spiderhost.com 
 [65.57.241.197])
  by rly-xa05.mx.aol.com (v101_r1.5) with ESMTP id
  MAILRELAYINXA55-7341621d0d322; Tue, 05 Oct 2004 00:03:25 -0400
  Received: from SMTP32-FWD by lamphier.com
(SMTP32) id A1BF42BA100B8F0C3; Mon,  4 Oct 2004 23:58:48
  Received: from pelxavirus3.terra.com.pe [200.48.36.5] by
 SNEEZY.XEROCOM.NET
  with ESMTP
(SMTPD32-8.12) id ABF42BA100B8; Mon, 04 Oct 2004 23:58:44 -0400
  Received: from anamaria (unknown [200.106.79.108])
   by pelxavirus3.terra.com.pe (Postfix) with ESMTP id 295EDB7CA4;
   Mon,  4 Oct 2004 23:07:07 -0500 (PET)
  Message-ID: [EMAIL PROTECTED]
  To: Undisclosed Recipients
  From: Anni [EMAIL PROTECTED]
  Subject: Proposal
  Date: Mon, 4 Oct 2004 23:03:21 -0500
  MIME-Version: 1.0
  Content-type: text/plain; charset=US-ASCII
  Content-Transfer-Encoding: quoted-printable
  X-RBL-Warning: NOABUSE: Not supporting [EMAIL PROTECTED]
  X-RBL-Warning: HELOBOGUS: Domain pelxavirus3.terra.com.pe 
 has no MX or A
  records [0301].
  X-RBL-Warning: WEIGHT1-9: Total weight between 1 and 9.
  X-Declude-Sender: [EMAIL PROTECTED] [200.48.36.5]
  X-Declude-Spoolname: D1bf42ba100b8f0c3.SMD
  X-Note: CompBiz scanned with Declude JunkMail.
  X-Spam-Tests-Failed: NOABUSE, HELOBOGUS, WEIGHT1-9 [7].
  X-Note: This E-mail was sent from smtp7.terra.com.pe