All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Overseers Q. Hawed" <digisnap@govideco.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Some useful advices for your health
Date: Fri, 21 Jul 2006 09:44:33 +0000	[thread overview]
Message-ID: <5792200852.20060721042425@govideco.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 172 bytes --]



_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

[-- Attachment #2: SpamAssassinReport.txt --]
[-- Type: text/plain, Size: 1032 bytes --]

Spam detection software, running on the system "fire-2.osdl.org", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Kernel-janitors mailing list
  Kernel-janitors@lists.osdl.org
  https://lists.osdl.org/mailman/listinfo/kernel-janitors [...] 

Content analysis details:   (5.6 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-1.0 OSDL_HEADER_SUBJECT_BRACKETED Subject starts with []'d phrase
-1.0 OSDL_HEADER_LISTID_KNOWN List-Id contains a known mailing list
 2.9 FORGED_RCVD_FROM_NUM   Received headers forged (numeric hostname)
 2.0 OUTFLUX_THEBAT         X-Mailer is from "The Bat"
 2.8 FORGED_MUA_THEBAT_CS   Mail pretending to be from The Bat! (charset)
-0.1 AWL                    AWL: Auto-whitelist adjustment



                 reply	other threads:[~2006-07-21  9:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5792200852.20060721042425@govideco.com \
    --to=digisnap@govideco.com \
    --cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.