public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
Subject: Re: What will I dislike about GNATS?
Date: Thu, 10 Jun 2004 10:57:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1075 bytes --]

Jeff Blaine wrote:
> Coming from the world of Req and having looked into RT and roundup,
> what makes GNATS stand out in comparison?  I don't necessarily mean
> "What makes GNATS better?"  I am curious to hear of its quirks or odd
> modes of workflow if they exist.  I've browsed the docs and FAQ.

I think the biggest complaint people have is over GNATS poor
understanding of MIME.  Currently, much of this can be avoided through
the use of procmail scripts and auto-responders.  I have a custom
procmail script that does a pretty good job of filtering out marked
spam, viruses, and overly large emails.  HTML-only emails are converted
to text, and emails that fail to enter the queue are saved to separate
mail folders.  If you're interested in the RC file, just send me an
email and I'll forward it to you. 

MIME-handling enhancement is one of those big TODO's that would bring
GNATS around to modern email technology.

Chad Walstrom <> 
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

  reply	other threads:[~2004-06-09 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 18:45 Jeff Blaine
2004-06-10 10:57 ` Chad Walstrom [this message]
2004-06-10 20:24   ` Mel Hatzis
2004-06-10 20:58     ` Yngve Svendsen

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:

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

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).