Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: allowing coding invalid systems
Date: Tue, 07 Jun 2005 12:19:26 +0200	[thread overview]
Message-ID: <9emzq2mpu9.fsf@gowron.rz-berlin.mpg.de> (raw)

I have a homebuild function to mail-forward (spam) messages to the
appropriate address. I'd liked to be disturbed as little as possible
by potential problems with these messages, so I switch off some syntax
checks:
,----[(let ...]
|        (message-syntax-checks '((control-chars . disabled)
|                                 (illegible-text . disabled)
|                                 (sender . disabled)))
`----[...body...]

However, since more and more spam is send using wrong coding systems, i.e. 
,----
| charset="unicode-1-1-utf-7"
`----
sending a digest containing this message fails Gnus telling me that
the coding system is not valid.

Is there a way to force sending of such messages? 

If not, would there be a way to check for messages that have the wrong
charset and  exclude them from the digest?

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)



             reply	other threads:[~2005-06-07 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 10:19 Jochen Küpper [this message]
     [not found] ` <9emzq2mpu9.fsf-G2iyDNEOhahHYNAXZw2rCoRsZ6cCL1yJ@public.gmane.org>
2005-07-01 16:54   ` unicode-1-1-utf-7 (was: allowing invalid coding systems) Jochen Küpper
     [not found]     ` <m3ekai79hb.fsf-X+QEHg5KIgm/8B4OpmtwqPxnRIzENc/G@public.gmane.org>
2005-07-02 11:40       ` unicode-1-1-utf-7 Jochen Küpper

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=9emzq2mpu9.fsf@gowron.rz-berlin.mpg.de \
    --to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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 NNTP newsgroup(s).