From roots-in@roots-l.rootsweb.com Sat Jan 28 13:46:53 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by lists5.rootsweb.com (8.12.8/8.12.8) with ESMTP id k0SKkrtK018107; Sat, 28 Jan 2006 13:46:53 -0700 Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k0SKkqK8008536 for ; Sat, 28 Jan 2006 13:46:52 -0700 Received: from roots-l.rootsweb.com (roots-l [127.0.0.1]) by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k0SIJ2FI028905 for ; Sat, 28 Jan 2006 13:19:02 -0500 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k0SIJ2QP028904 for roots-approved@rootsweb.com; Sat, 28 Jan 2006 13:19:02 -0500 Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41]) by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k0SIDcFI028840 for ; Sat, 28 Jan 2006 13:13:38 -0500 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k0SKfJwU015249 for roots-in@roots-l.rootsweb.com; Sat, 28 Jan 2006 13:41:19 -0700 X-Envelope-From: ncsherman@mindspring.com Sat Jan 28 13:41:19 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by lists5.rootsweb.com (8.12.8/8.12.8) with ESMTP id k0SKfJtK015240 for ; Sat, 28 Jan 2006 13:41:19 -0700 Received: from smtpauth07.mail.atl.earthlink.net (smtpauth07.mail.atl.earthlink.net [209.86.89.67]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k0SKfHGS006114 for ; Sat, 28 Jan 2006 13:41:17 -0700 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=cETOaHsZppwJvXiNuSqPC523NGEFnwZ4jnXr4Sx0d+A81lYo0SzkG6I468KH/ExC; h=Received:Message-ID:X-Priority:Reply-To:X-Mailer:From:To:Subject:Date:MIME-Version:Content-type:X-ELNK-Trace:X-Originating-IP; Received: from [71.143.190.187] (helo=mindspring.com) by smtpauth07.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1F2wsj-00022O-Bi for ROOTS-L@rootsweb.com; Sat, 28 Jan 2006 15:41:13 -0500 Message-ID: <410-220061628204111296@mindspring.com> X-Priority: 3 Reply-To: ncsherman@mindspring.com X-Mailer: EarthLink MailBox 2005.2.15.0 (Windows) From: "NICANA SHERMAN" To: ROOTS-L@rootsweb.com Date: Sat, 28 Jan 2006 14:41:11 -0600 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-ELNK-Trace: 35f21b87c11d3b4b6fb18b2e56ec87b340683398e744b8a402f5eff7e211374f47b3124b2f90818e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 71.143.190.187 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 Sender: roots-in@roots-l.rootsweb.com Subject: [ROOTS-L] RE: blocked messages; ROOTS-L Digest V06 #38 Some ISPs have gone to a blocking heirarchy automated system. Either ALL messages are blocked unless the person or sending entity is ALREADY in the recipient's address book, or up to a certain number of email addresses of known spammers can be blocked, or no messages are blocked. In Earthlink, one can block up to 500 addresses -- but cannot add more, so the spam rebuilds. If you delete the addresses previously blocked, you have to reblock them. Having to delete blocked addresses when the number exceeds 500 is not feasible. Getting 500 spam messages can happen n a matter of a few weeks. The other alternative, to remove all blocking, is not a viable option any more, even with virus protections. That leaves setting up full protection against spam messages that, unfortunately, blocks all senders not already in the recipeint's mailbox. The system Root-L and Digest uses, requesting that answers be mailed to the list to inform everyone is a good way for answers to be made. The questioner will have the listserv address in their address book, and your answer will get through that way. The way Earthlink's Spamblocker works, and possibly other ISP's systems also, is that your message rests in an email to the recipeint in a listing of possible spam messages. The recipient can look at the list and retrieve your message. The message "returned" to the sender is really, in Earthlink's system at any rate, merely letting you know that your message has been blocked as suspect. It is important to make your subject concise and clear, as only about four words are in the subject line on the blocked-message list. There is no way for the recipient user of Spamblocker to tell that system NOT to send the message. It is sent automatically when Earthlink receives your message, and before it gets to the recipient's mailbox. NOTE: if anyone from the Earthlink offices is reading this, sending that message tells the spammers that they have found a live address and frustrates everyone else, including the recipient, a.k.a. "an Earthlink customer"! > I replied to Helen personally but received a message back that I needed > to be added to a list before my message could be sent. I do not like to > respond to such requests. However, I will post my answer to Helen to the > list. I didn't want to send it to everyone, because I do not have time to > do lookups from the cd referenced at this point in time. NICANA SHERMAN ncsherman@mindspring.com