From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cpe-24-221-98-238.az.sprintbbd.net ([24.221.98.238] helo=lnx1.holmesgrown.com ident=root) by speech.braille.uwo.ca with esmtp (Exim 3.33 #1 (Debian)) id 16Wlle-0004tK-00 for ; Fri, 01 Feb 2002 17:02:46 -0500 Received: from lnx3.holmesgrown.com (steve@lnx3.holmesgrown.com [192.168.1.5]) by lnx1.holmesgrown.com (8.9.3/8.9.3) with ESMTP id PAA20757 for ; Fri, 1 Feb 2002 15:02:47 -0700 Date: Fri, 1 Feb 2002 15:02:59 -0700 (MST) From: Steve Holmes To: Subject: Re: So much Windows Mailer crap on this list... In-Reply-To: <001801c1ab5b$2a387040$93117481@dorm.utexas.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.8 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: As for filtering with procmail, it basically looks at regular expressions to be found in the text (header or body). What I'm wondering, is if I could use procmail to pipe it through a script that would simply strip out the the char-set line so pine won't have anything to complain about? In the mean time, I ot to write to pine support asking about supressing this warning message. When I reported a bug a while back, they got back to me within a few days acknoleging the problem and promised to have it fixed by the next release.