Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Feature request: message-syntax-checks also for mail?
Date: Sun, 17 Feb 2002 10:59:45 +0100	[thread overview]
Message-ID: <vafit8wwhri.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3y9htsff1.fsf@Janik.cz> (Pavel@Janik.cz's message of "Sat, 16 Feb 2002 14:51:46 +0100")

Pavel@Janik.cz (Pavel Janík) writes:

> message-syntax-checks controls what syntax checks should not be performed
> on outgoing posts. Is it possible to extend its functionality to outgoing
> mail too? I would like to be able to check whether my outgoing e-mails do
> not contain long lines, etc. without playing with hooks etc.

I think the checks are by default performed for mails as well as news
posts.  Gnus asks me quite often whether I want to send a mail with
long lines...

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)



  reply	other threads:[~2002-02-17  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-16 13:51 Pavel Janík
2002-02-17  9:59 ` Kai Großjohann [this message]
2002-02-17 17:24   ` Pavel Janík

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=vafit8wwhri.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).