From: jadamson@partners.org (Joel J. Adamson)
To: Don Saklad <dsaklad@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: For nonprogrammers maybe dyslexic, maybe ADD, how can spamassassin headers be filtered so that all or most of the spam messages, rather than mixed in with email, all or most go to a separate email file that can be checked for any false positives?
Date: Mon, 10 Mar 2008 11:04:46 -0400 [thread overview]
Message-ID: <874pber569.fsf@W0053328.mgh.harvard.edu> (raw)
In-Reply-To: <E1JXxtN-0002k5-Pi@fencepost.gnu.org> (Don Saklad's message of "Sat, 08 Mar 2008 07:11:09 -0500")
Don Saklad <dsaklad@gnu.org> writes:
> For nonprogrammers
Become a programmer.
> maybe dyslexic, or maybe ADD,
Please don't post personal information or excuses for not following
advice.
Joel
--
Joel J. Adamson
Biostatistician
Pediatric Psychopharmacology Research Unit
Massachusetts General Hospital
Boston, MA 02114
(617) 643-1432
(303) 880-3109
The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983 and
properly dispose of this information.
prev parent reply other threads:[~2008-03-10 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 12:11 For nonprogrammers maybe dyslexic, maybe ADD, how can spamassassin headers be filtered so that all or most of the spam messages, rather than mixed in with email, all or most go to a separate email file that can be checked for any false positives? Don Saklad
2008-03-08 12:37 ` Bastien
2008-03-10 15:04 ` Joel J. Adamson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874pber569.fsf@W0053328.mgh.harvard.edu \
--to=jadamson@partners.org \
--cc=dsaklad@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).