From: "Geo." 

Hey, do you guys remember that experiment where someone hooked up an AI to
ICQ and let it have long winded conversations with just random people?

Well it looks like that made quite an impression over at Yahoo, they hired
the bot. See below. Yahoo has this thing going where you send them 5 emails
and they drop the connection, so on a mail server that retries delivery
every 10 minutes, that means a max of 30 emails per hour. If you happen to
generate more, they just back up in the queue.

I recently contacted yahoo postmaster support thru their web form initially
and tried to explain this, then they responded and I tried to explain again
and again and again until I realized, it's a bot.

Geo. (you'll have to read from the bottom up, sorry)

Hello,

Thank you for writing to Yahoo! Mail.

Without any specific SMTP error message, we are unable to effectively
troubleshoot the issue.

Occasionally, interruptions or disruptions in email transmissions over the
Internet will render a message undeliverable. While this is very rare, it
does happen. If you continue to experience this delivery issue, in order to
troubleshoot it, we would appreciate it if you could provide a full SMTP
thread that represents the connection that resulted in the delivery
failure. Please provide:

* The output of a manual SMTP test (typically with telnet) from your
mail server to our servers showing the SMTP conversation leading up to and
including the rejection message.

* Log messages from your mail server showing which IP you connected to
and what responses you got from the remote server at the time you received
the failures.

Again, we appreciate your assistance and apologize for any inconvenience.

Please let us know if you still need assistance so we may assist you further.

Thank you again for contacting Yahoo! Customer Care.

Regards,

Samuel Cyprian

Yahoo! Customer Care
33953531



Original Message Follows:
-------------------------

ok the attachment is below as part of the email body.

pt070430.log:POST 30 Apr 2007 15:38:19.046 P 08383 14205 Start queue yahoo.com (4)
pt070430.log:POST 30 Apr 2007 15:38:19.046 P 02137 14205 try MX lookup for
yahoo.com
pt070430.log:POST 30 Apr 2007 15:38:19.062 P 02138 14205 use MX records for
yahoo.com
pt070430.log:POST 30 Apr 2007 15:38:19.062 M 02103 14205 found 7 records for
yahoo.com using *
pt070430.log:POST 30 Apr 2007 15:38:19.062 M 02104 14205   1:
b.mx.mail.yahoo.com [66.196.97.250] 1 pt070430.log:POST 30 Apr 2007
15:38:19.062 M 02104 14205   2:
f.mx.mail.yahoo.com [68.142.202.247] 1 pt070430.log:POST 30 Apr 2007
15:38:19.062 M 02104 14205   3:
a.mx.mail.yahoo.com [209.191.118.103] 1 pt070430.log:POST 30 Apr 2007
15:38:19.062 M 02104 14205   4:
d.mx.mail.yahoo.com [216.39.53.2] 1 pt070430.log:POST 30 Apr 2007
15:38:19.062 M 02104 14205   5:
g.mx.mail.yahoo.com [206.190.53.191] 1 pt070430.log:POST 30 Apr 2007
15:38:19.062 M 02104 14205   6:
c.mx.mail.yahoo.com [68.142.237.182] 1 pt070430.log:POST 30 Apr 2007
15:38:19.062 M 02104 14205   7:
e.mx.mail.yahoo.com [216.39.53.1] 1 pt070430.log:POST 30 Apr 2007
15:38:19.078 M 00006 14205 Resolved: b.mx.mail.yahoo.com [66.196.97.250]
pt070430.log:POST 30 Apr 2007 15:38:19.109 P 02105 14205 sending
f:\NTmail\Out\yahoo.com\uesdslaa to b.mx.mail.yahoo.com pt070430.log:POST
30 Apr 2007 15:38:19.156 A 02122 14205 220 mta145.mail.re3.yahoo.com ESMTP
YSmtp service ready pt070430.log:POST 30 Apr 2007 15:38:19.156 A 00000
14205 EHLO mail.nls.net
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 02122 14205
250-mta145.mail.re3.yahoo.com
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 02122 14205 250-8BITMIME
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 02122 14205 250-SIZE 31981568
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 02122 14205 250 PIPELINING
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 00000 14205 MAIL
From: SIZE=2700
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 00000 14205 RCPT
To:
pt070430.log:POST 30 Apr 2007 15:38:22.453 A 00000 14205 DATA
pt070430.log:POST 30 Apr 2007 15:38:22.515 A 02122 14205 250 sender
 ok
pt070430.log:POST 30 Apr 2007 15:38:22.515 A 02122 14205 250 recipient
 ok
pt070430.log:POST 30 Apr 2007 15:38:22.515 A 02122 14205 354 go ahead
pt070430.log:POST 30 Apr 2007 15:38:22.515 A 00000 14205 .
pt070430.log:POST 30 Apr 2007 15:38:25.250 A 02122 14205 250 ok dirdel
pt070430.log:POST 30 Apr 2007 15:38:25.250 S 02028 14205 Sent
f:\NTmail\Out\yahoo.com\uesdslaa -> b.mx.mail.yahoo.com [66.196.97.250]
ggaiser{at}nls.net tblevins78{at}yahoo.com 2703 11907.425 pt070430.log:POST 30
Apr 2007 15:38:25.250 P 08374 14205 66.196.97.250 b.mx.mail.yahoo.com
f:\NTmail\Out\yahoo.com\uesdslaa Delivered ggaiser{at}nls.net
tblevins78{at}yahoo.com 2703 11907.425 pt070430.log:POST 30 Apr 2007
15:38:25.265 A 00000 14205 RSET pt070430.log:POST 30 Apr 2007 15:38:25.312
A 02122 14205 250 reset ok pt070430.log:POST 30 Apr 2007 15:38:25.328 A
00000 14205 MAIL From: SIZE=8518
pt070430.log:POST 30 Apr 2007 15:38:25.328 A 00000 14205 RCPT
To:
pt070430.log:POST 30 Apr 2007 15:38:25.328 A 00000 14205 DATA
pt070430.log:POST 30 Apr 2007 15:38:25.375 A 02122 14205 250 sender
 ok
pt070430.log:POST 30 Apr 2007 15:38:25.375 A 02122 14205 250 recipient
 ok
pt070430.log:POST 30 Apr 2007 15:38:25.375 A 02122 14205 354 go ahead
pt070430.log:POST 30 Apr 2007 15:38:25.421 A 00000 14205 .
pt070430.log:POST 30 Apr 2007 15:38:25.875 A 02122 14205 250 ok dirdel
pt070430.log:POST 30 Apr 2007 15:38:25.875 S 02028 14205 Sent
f:\NTmail\Out\yahoo.com\ufodslaa -> b.mx.mail.yahoo.com [66.196.97.250]
chrisodyssey{at}netlink.net dandodyssey{at}yahoo.com 8521 14947.068
pt070430.log:POST 30 Apr 2007 15:38:25.875 P 08374 14205 66.196.97.250
b.mx.mail.yahoo.com f:\NTmail\Out\yahoo.com\ufodslaa Delivered
chrisodyssey{at}netlink.net dandodyssey{at}yahoo.com 8521 14947.068
pt070430.log:POST 30 Apr 2007 15:38:25.890 A 00000 14205 RSET
pt070430.log:POST 30 Apr 2007 15:38:25.921 A 02122 14205 250 reset ok
pt070430.log:POST 30 Apr 2007 15:38:25.937 A 00000 14205 MAIL
From: SIZE=24297
pt070430.log:POST 30 Apr 2007 15:38:25.937 A 00000 14205 RCPT
To:
pt070430.log:POST 30 Apr 2007 15:38:25.937 A 00000 14205 DATA
pt070430.log:POST 30 Apr 2007 15:38:25.968 A 02122 14205 250 sender
 ok
pt070430.log:POST 30 Apr 2007 15:38:25.968 A 02122 14205 250 recipient
 ok
pt070430.log:POST 30 Apr 2007 15:38:25.968 A 02122 14205 354 go ahead
pt070430.log:POST 30 Apr 2007 15:38:26.187 A 00000 14205 .
pt070430.log:POST 30 Apr 2007 15:38:26.796 A 02122 14205 250 ok dirdel
pt070430.log:POST 30 Apr 2007 15:38:26.796 S 02028 14205 Sent
f:\NTmail\Out\yahoo.com\umldslaa -> b.mx.mail.yahoo.com [66.196.97.250]
hetling{at}nls.net akinches{at}yahoo.com 24300 16742.303 pt070430.log:POST 30 Apr
2007 15:38:26.796 P 08374 14205 66.196.97.250 b.mx.mail.yahoo.com
f:\NTmail\Out\yahoo.com\umldslaa Delivered hetling{at}nls.net
akinches{at}yahoo.com 24300 16742.303 pt070430.log:POST 30 Apr 2007
15:38:26.796 A 00000 14205 RSET pt070430.log:POST 30 Apr 2007 15:38:26.843
A 02122 14205 250 reset ok pt070430.log:POST 30 Apr 2007 15:38:26.859 A
00000 14205 MAIL From: SIZE=453769
pt070430.log:POST 30 Apr 2007 15:38:26.859 A 00000 14205 RCPT
To:
pt070430.log:POST 30 Apr 2007 15:38:26.859 A 00000 14205 DATA
pt070430.log:POST 30 Apr 2007 15:38:27.375 A 02122 14205 250 sender
 ok
pt070430.log:POST 30 Apr 2007 15:38:27.375 A 02122 14205 250 recipient
 ok
pt070430.log:POST 30 Apr 2007 15:38:27.375 A 02122 14205 354 go ahead
pt070430.log:POST 30 Apr 2007 15:38:56.890 A 00000 14205 .
pt070430.log:POST 30 Apr 2007 15:38:57.234 A 02122 14205 250 ok dirdel
pt070430.log:POST 30 Apr 2007 15:38:57.234 S 02028 14205 Sent
f:\NTmail\Out\yahoo.com\unqdslaa -> b.mx.mail.yahoo.com [66.196.97.250]
sammy{at}netlink.net filipefamily{at}yahoo.com 453772 12942.992 pt070430.log:POST
30 Apr 2007 15:38:57.234 P 08374 14205 66.196.97.250 b.mx.mail.yahoo.com
f:\NTmail\Out\yahoo.com\unqdslaa Delivered sammy{at}netlink.net
filipefamily{at}yahoo.com 453772 12942.992 pt070430.log:POST 30 Apr 2007
15:38:57.250 A 00000 14205 RSET pt070430.log:POST 30 Apr 2007 15:38:57.281
A 02122 14205 250 reset ok pt070430.log:POST 30 Apr 2007 15:38:57.281 A
00000 14205 MAIL From: SIZE=274077
pt070430.log:POST 30 Apr 2007 15:38:57.281 A 00000 14205 RCPT
To:
pt070430.log:POST 30 Apr 2007 15:38:57.281 A 00000 14205 DATA
pt070430.log:POST 30 Apr 2007 15:38:57.343 A 02122 14205 250 sender
 ok
pt070430.log:POST 30 Apr 2007 15:38:57.343 A 02122 14205 250 recipient
 ok
pt070430.log:POST 30 Apr 2007 15:38:57.343 A 02122 14205 354 go ahead
pt070430.log:POST 30 Apr 2007 15:39:08.500 A 00000 14205 .
pt070430.log:POST 30 Apr 2007 15:39:12.937 A 02122 14205 250 ok dirdel
pt070430.log:POST 30 Apr 2007 15:39:12.937 S 02028 14205 Sent
f:\NTmail\Out\yahoo.com\uqqdslaa -> b.mx.mail.yahoo.com [66.196.97.250]
mindygirl{at}nls.net rtmjofaz{at}yahoo.com 274080 12889.195 pt070430.log:POST 30
Apr 2007 15:39:12.937 P 08374 14205 66.196.97.250 b.mx.mail.yahoo.com
f:\NTmail\Out\yahoo.com\uqqdslaa Delivered mindygirl{at}nls.net
rtmjofaz{at}yahoo.com 274080 12889.195 pt070430.log:POST 30 Apr 2007
15:39:12.937 A 00000 14205 RSET pt070430.log:POST 30 Apr 2007 15:39:12.953
F 02178 14205 ReadFromStream b.mx.mail.yahoo.com 0 bytes (0)
pt070430.log:POST 30 Apr 2007 15:39:12.953 P 08385 14205 66.196.97.250
b.mx.mail.yahoo.com f:\NTmail\Out\yahoo.com\uqqdslaa Disconnected
pt070430.log:POST 30 Apr 2007 15:39:13.671 P 08381 14205 yahoo.com New
queue

> -----Original Message-----
> From: Yahoo! Customer Support [mailto:abuse-admin{at}cc.yahoo-inc.com]
> Sent: Monday, April 30, 2007 4:34 PM
> To: Abuse
> Subject: RE: Defer - nls.net (KMM49177606V65009L0KM)
>
>
> Hello,
>
> Thank you for writing to Yahoo! Mail.
>
> Unfortunately, your message was sent to us as an attachment. Due to
> security purposes, our custom messaging system is unable to access
> attachments and we will need you to forward a copy of the message, as
> opposed to sending it as an attachment.
>
> Please include the following in your report of email abuse to assist
us
> in a prompt and full evaluation:
>
>    1. Original subject line -- Please forward the email with a subject
> identical to the original subject.
>
>    2. Complete headers -- Email programs often display abbreviated
> headers. To learn how to display the full headers in a Yahoo! Mail
> account, please visit the Yahoo! Mail Help Desk at:
>
>    http://help.yahoo.com/help/us/mail/config/config-11.html
>
> If you are using a different client to read your email, please consult
> your email program's help system for more information on viewing full
> headers.
>
>    3. Complete message body -- Please include the complete, unedited
> content of the email message in question. Please do not change or edit
> the message in any way.
>
> If reports of email abuse are missing any one of these three items, it
> may take longer for the Yahoo! Mail Abuse Team to properly investigate
> and take appropriate action. We appreciate your efforts in reporting
> this abuse to Yahoo!.
>
> Thank you again for contacting Yahoo! Customer Care, and we await your
> response.
>
> Regards,
>
> Samuel Cyprian
>
> Yahoo! Customer Care
> 33953531
>
>
>
> Original Message Follows:
> -------------------------
>
> Attached is the detailed log, notice how we get dropped at the end
even
> though there are hundreds of emails still queued. This is how it
works,
> 5
> emails, drop, 5 emails, drop, 5 emails, drop, on and on an on.
>
> Geo.
>
> > -----Original Message-----
> > From: Yahoo! Customer Support [mailto:abuse-admin{at}cc.yahoo-inc.com]
> > Sent: Monday, April 30, 2007 3:16 PM
> > To: Abuse
> > Subject: Re: Defer - nls.net (KMM49174850V60386L0KM)
> >
> >
> > Geo,
> >
> > Thank you for writing to Yahoo! Mail.
> >
> > Without any specific SMTP error message, we are unable to
effectively
> > troubleshoot the issue.
> >
> > Occasionally, interruptions or disruptions in email transmissions
over
> > the Internet will render a message undeliverable. While this is very
> > rare, it does happen. If you continue to experience this delivery
> issue,
> > in order to troubleshoot it, we would appreciate it if you could
> provide
> > a full SMTP thread that represents the connection that resulted in
the
> > delivery failure. Please provide:
> >
> > * The output of a manual SMTP test (typically with telnet) from your
> > mail server to our servers showing the SMTP conversation leading up
to
> > and including the rejection message.
> >
> > * Log messages from your mail server showing which IP you connected
to
> > and what responses you got from the remote server at the time you
> > received the failures.
> >
> > Again, we appreciate your assistance and apologize for any
> > inconvenience.
> >
> > Please let us know if you still need assistance so we may assist you
> > further.
> >
> > Your patience during this process is greatly appreciated.
> >
> > Thank you again for contacting Yahoo! Customer Care.
> >
> > Regards,
> >
> > Samuel Cyprian
> >
> > Yahoo! Customer Care
> > 33953531
> >
> >
> >
> > Original Message Follows:
> > -------------------------
> >
> > Hi Samuel,
> >
> > Thanks for the response.
> >
> > The problem is you only accept 5 emails from our mail server then
you
> > drop
> > the connection, there is no error message, look at the logs at the
> > bottom of
> > this email. Right now there is a queue of about 400 emails so if I
> have
> > the
> > server set to retry delivery every 10 minutes that means 15 emails
per
> > hour
> > will go to yahoo (5 emails and you drop us, 10 minutes later 5 more
> and
> > drop, etc). With 20,000 people we generate more than 15 emails per
> hour
> > during busy hours.
> >
> > Why do you throttle email from us? Is there some way you can
whitelist
> > 216.144.3.10 so that it's not throttled like this? I assume you have
> to
> > do
> > that for larger ISP mail servers and as we have grown we have passed
> the
> >
> > point where the thottling will allow proper email transactions
between
> > yahoo.com and nls.net domains.
> >
> > Geo.
> >
> > ----- Original Message -----
> > From: "Yahoo! Customer Support"

> > To: 
> > Sent: Sunday, April 29, 2007 1:58 PM
> > Subject: Re: Defer - nls.net (KMM49122097V69293L0KM)
> >
> >
> > > Hello,
> > >
> > > Thank you for writing to Yahoo! Mail.
> > >
> > > The Yahoo! Mail team is only able to provide email support at this
> > time.
> > > This is to ensure we're able to continue providing Yahoo! Mail for
> > free.
> > > Your report is important to us, and we strive to answer all
reports
> > > within two business days.
> > >
> > > We appreciate your patience and understanding in this matter.
> > >
> > > We would appreciate it if you could provide more information to
help
> > us
> > > troubleshoot the issue.  Please note that if you are not the
system
> > > administrator for the mail server(s) affected, we encourage you to
> > > contact the administrator so they can address the possible issues
> > > regarding mailings from the mail server.  Please reply to this
email
> > > with the following information:
> > >
> > > * Explain the details of one event with the delivery problems to
> > Yahoo!
> > > Mail. Please provide the entire message, including the full text
of
> > the
> > > error message returned, and full header information.
> > >
> > > Within a Yahoo! Mail account, you can display this information by
> > > clicking the "Full Headers" link located within
the message in the
> > > bottom right-hand corner.
> > >
> > > * The specific server_domain name and IP address of the email
> > server(s)
> > > that have the delivery issue to Yahoo! Mail.
> > >
> > >   IP Address:  xxx.xxx.xxx.xxx
> > >   Mail Server Domain Name:  server_name.domain.com
> > >
> > > * Log messages from your mail server showing which IP you
connected
> to
> > > and what responses you got from the remote server at the time you
> > > received the corresponding failures/timeouts for the event you are
> > > reporting.
> > >
> > > * The results from a plain text message, sent to Yahoo! Mail,
> without
> > > HTML, links, graphics or attachments, from the server having
> delivery
> > > issues. Is the email delivered to Yahoo! Inbox?
> > >
> > > We appreciate your assistance. This information will be helpful in
> > > determining the reason why you are having issues when delivering
> mail
> > to
> > > Yahoo! Mail accounts.
> > >
> > > I await your response so I may resolve your issue.
> > >
> > > Thank you again for contacting Yahoo! Customer Care.
> > >
> > > Regards,
> > >
> > > Samuel Cyprian
> > >
> > > Yahoo! Customer Care
> > > 33953531
> > >
> > >
> > >
> > > Original Message Follows:
> > > -------------------------
> > >
> > > Mail-Id: 1177679731-6495
> > > Name: George Roettger
> > >
> > > What domain(s) are you contacting us about?
> > >  nls.net
> > >
> > > Indicate the specific IP address of the mail server experiencing
the
> > > issue.
> > > 216.144.3.10
> > >
> > > About the problem
> > > Experiencing delivery delays
> > >
> > > Technical details
> > > We have about 20,000 customers who seem to have a lot of
> > > friends on yahoo. You only seem to allow about one email
> > > per minute from our server so many times our queue becomes
> > > quite large (like 400 emails long yesterday) and it makes
> > > customers mad when it takes hours for email to go to a
> > > yahoo address.
> > >
> > > Can you help? There is no spam, it's just idiots sending
> > > each other pictures and stupid emails.
> > >
> > > It has gotten progressively worse as we have gotten bigger
> > > over the past several months. The more email accounts we
> > > host the bigger the queue gets.
> > >
> > > Tracing route to mta-v10.mail.vip.mud.yahoo.com
> > > [209.191.88.247]
> > > over a maximum of 30 hops:
> > >
> > >  1     3 ms     2 ms     1 ms  r-mac1.nls.net [216.144.0.1]
> > >  2     4 ms    10 ms     4 ms  s-cle-mac3.nls.net
> > > [216.144.27.193]
> > >  3    17 ms    15 ms    15 ms  sl-gw4-roa-4-0-
> > > ts2.sprintlink.net [144.228.252.233]
> > >  4    17 ms    15 ms    15 ms  sl-bb20-roa-2-
> > > 3.sprintlink.net [144.232.17.201]
> > >  5    22 ms    37 ms    29 ms  sl-bb22-chi-4-0-
> > > 0.sprintlink.net [144.232.18.36]
> > >  6    19 ms    20 ms    18 ms  sl-bb20-chi-15-
> > > 0.sprintlink.net [144.232.26.5]
> > >  7    24 ms    23 ms    21 ms  sl-st20-chi-13-
> > > 0.sprintlink.net [144.232.20.3]
> > >  8    19 ms    18 ms    17 ms  144.232.8.114
> > >  9    55 ms    23 ms    33 ms  ae-32-
> > > 56.ebr2.chicago1.level3.net [4.68.101.190]
> > > 10    25 ms    18 ms    21 ms  ae-1-
> > > 100.ebr1.chicago1.level3.net [4.69.132.41]
> > > 11    51 ms    51 ms    51 ms  ae-
> > > 3.ebr2.denver1.level3.net [4.69.132.61]
> > > 12    67 ms    59 ms    64 ms  ae-1-
> > > 100.ebr1.denver1.level3.net [4.69.132.37]
> > > 13    71 ms    71 ms    71 ms  ae-
> > > 2.ebr1.dallas1.level3.net [4.69.132.106]
> > > 14    65 ms    61 ms    64 ms  ae-11-
> > > 51.car1.dallas1.level3.net [4.68.122.13]
> > > 15    60 ms    59 ms    65 ms  4.79.180.2
> > > 16    67 ms    69 ms    75 ms  ge-1-1-0-
> > > p130.msr2.mud.yahoo.com [216.115.104.93]
> > > 17    65 ms    67 ms    65 ms  te-8-1.bas-c1.mud.yahoo.com
> > > [68.142.193.5]
> > > 18    72 ms    61 ms    67 ms  mta-
> > > v10.mail.vip.mud.yahoo.com [209.191.88.247]
> > >
> > >  "POST 27 Apr 2007 07:39:37.281 M 00006 2865
> > > "Resolved: ""
> > > e.mx.mail.yahoo.com [216.39.53.1]
> > > POST 27 Apr 2007 07:39:37.984 S 02028 2865 Sent
> > > f:\NTmail\Out\yahoo.com\nceyrlaa -) e.mx.mail.yahoo.com
> > > [216.39.53.1] imjlv{at}nls.net K1loop{at}yahoo.com 19451 1214.496
> > > POST 27 Apr 2007 07:39:38.750 S 02028 2865 Sent
> > > f:\NTmail\Out\yahoo.com\rmeyrlaa -) e.mx.mail.yahoo.com
> > > [216.39.53.1] amehling{at}netlink.net bethstomps{at}yahoo.com
> > > 7587 784.840
> > > POST 27 Apr 2007 07:39:39.437 S 02028 2865 Sent
> > > f:\NTmail\Out\yahoo.com\ycdyrlaa -) e.mx.mail.yahoo.com
> > > [216.39.53.1] houthouse{at}netlink.net
> > > wiggins_sandra{at}yahoo.com 11281 2783.532
> > > POST 27 Apr 2007 07:39:40.171 S 02028 2865 Sent
> > > f:\NTmail\Out\yahoo.com\ydpxrlaa -) e.mx.mail.yahoo.com
> > > [216.39.53.1] baprosser{at}nls.net Krista.Crisp{at}yahoo.com 5121
> > > 37575.757
> > > POST 27 Apr 2007 07:39:40.734 S 02028 2865 Sent
> > > f:\NTmail\Out\yahoo.com\ydswrlaa -) e.mx.mail.yahoo.com
> > > [216.39.53.1] shajon{at}nls.net l_irene2{at}yahoo.com 26605
> > > 60025.393
> > > POST 27 Apr 2007 07:39:40.781 F 02178 2865 ReadFromStream
> > > e.mx.mail.yahoo.com 0 bytes (0)
> > >
> > > in other words, 5 emails and you drop us, then 10 minutes
> > > later 5 more and you drop us, etc etc etc.
> > >
> > > any email, it's 5 emails and a drop
> > >
> > > Other relevant information:
> > > Please contact me at 216-367-7015 if you need any more
> > > info. All I'm asking for is the ability to deliver email
> > > from a growing group of everyday folks.
> > >

>
> [ Attachment 1.2 Type: text/plain]
>

--- BBBS/NT v4.01 Flag-5