From: Romain Francoise <romain@orebokech.com>
Subject: Re: Unprintable characters
Date: Mon, 10 Jan 2005 14:18:35 +0100 [thread overview]
Message-ID: <87acrh5sno.fsf@orebokech.com> (raw)
In-Reply-To: <87mzvhh3g2.fsf@nwalsh.com> (Norman Walsh's message of "Mon, 10 Jan 2005 07:30:05 -0500")
Norman Walsh <ndw@nwalsh.com> writes:
> Lots of spam contains unprintable characters. Is there anyway to make
> gnus default to ignoring this situation instead of asking me if I'm
> sure I want to send them?
Frob `message-syntax-checks', the `illegible-text' check is what you're
looking for.
--
Romain Francoise <romain@orebokech.com> | Every sky is blue, but not
it's a miracle -- http://orebokech.com/ | for me and you.
prev parent reply other threads:[~2005-01-10 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 12:30 Norman Walsh
[not found] ` <87mzvhh3g2.fsf-wnzGKDmzZYLQT0dZR+AlfA@public.gmane.org>
2005-01-10 12:51 ` Jochen Küpper
2005-01-10 13:10 ` Francis Litterio
2005-01-10 13:19 ` Romain Francoise
2005-01-10 13:18 ` Romain Francoise [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=87acrh5sno.fsf@orebokech.com \
--to=romain@orebokech.com \
/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).