All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [SPAM] [LARTC] Help:how to filter P bits and schedule??
Date: Mon, 21 Jun 2004 08:52:01 +0000	[thread overview]
Message-ID: <40D6A1B1.4090604@wildgooses.com> (raw)
In-Reply-To: <20040621094855.5D52.LARTC@schmakk.dk>


>X-Spam-Status: Yes, hits=6.4 required=4.0 tests=BODY_8BITS,
>DNS_FROM_RFCI_DSN, MIME_BASE64_TEXT,MIME_CHARSET_FARAWAY autolearn=no
>X-Spam-Report:  *  1.5 BODY_8BITS BODY: Body includes 8 consecutive 8-bit characters
>1.1 MIME_BASE64_TEXT RAW: Message text disguised using base64 encoding *
>1.4 DNS_FROM_RFCI_DSN RBL: From: sender listed in dsn.rfc-ignorant.org *
>2.5 MIME_CHARSET_FARAWAY MIME character set indicates foreign language
>
>Most of these seems to be because you are from another country, which is
>fine, but theres a lot of stuff you could avoid with very little effort.
>  
>

That's a bit of a pain for foreign language users who don't use the 
roman alphabet.  The only real thing he can obviously change is 
rfc-ignorant.

Perhaps he could change the Base 64, but the standards do say this is ok 
for use where more than the odd letter will require "quoted printable".  
If he did his whole email in quoted printable to a friend it would be x4 
to x5 the size...  Perhaps you can get your mailer to autochoose?

Oh well.  Good luck.  Sorry not sure how to use u32 though...

Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-06-21  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  7:56 [SPAM] [LARTC] Help:how to filter P bits and schedule?? Patrick Petersen
2004-06-21  8:52 ` Ed Wildgoose [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

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

  git send-email \
    --in-reply-to=40D6A1B1.4090604@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=lartc@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.