From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dsaklad@zurich.csail.mit.edu Newsgroups: gmane.emacs.help Subject: Spamassassin headers. What you can do with Spamassassin headers and how. Date: 6 Mar 2005 11:10:03 -0800 Organization: http://groups.google.com Message-ID: <1110136203.761645.271050@o13g2000cwo.googlegroups.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: sea.gmane.org 1110135913 23339 80.91.229.2 (6 Mar 2005 19:05:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 6 Mar 2005 19:05:13 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Mar 06 20:05:13 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D813t-0003km-35 for geh-help-gnu-emacs@m.gmane.org; Sun, 06 Mar 2005 20:05:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D81NV-0002RN-Ek for geh-help-gnu-emacs@m.gmane.org; Sun, 06 Mar 2005 14:25:25 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!postnews.google.com!o13g2000cwo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 27 Original-NNTP-Posting-Host: 24.41.3.197 Original-X-Trace: posting.google.com 1110136207 9815 127.0.0.1 (6 Mar 2005 19:10:07 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sun, 6 Mar 2005 19:10:07 +0000 (UTC) User-Agent: G2/0.2 Complaints-To: groups-abuse@google.com Injection-Info: o13g2000cwo.googlegroups.com; posting-host=24.41.3.197; posting-account=tUfEeg0AAADtZGPlIL1HD9BcwcZrfdLZ Original-Xref: shelby.stanford.edu gnu.emacs.help:129015 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org X-MailScanner-To: geh-help-gnu-emacs@m.gmane.org Xref: news.gmane.org gmane.emacs.help:24561 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:24561 How might a provider pull together better, easier ways to explain, instruct a. using less of what might be perceived as jargon and b. using less what might be perceived as arcane references, how might a provider more easily explain, more easily instruct end users with these questions?... end users with areas of expertise not directly applicable to... 1. What can you do with the spamassassin headers?... spamassassin headers have appeared in the headers at the top of messages in emacs rmail. 2. And how do you do the things you can do with the spamassassin headers?... Around the web the instructive material about spamassassin didn't appear to meet the needs of end users, given the usual explanations deferring the matter to another department, the provider, the isp, someone else not me and so on. Or what example or examples are there by way of individual spamassassin hints, tips, pointers, features?... Unrelated, but here's an example of providing hints, tips, points, features http://www.apple.com/pro/tips/