public inbox for
help / color / mirror / Atom feed
Subject: gnats/355: Mail agent output is forwarded by gnatsd
Date: Mon, 04 Mar 2002 01:24:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         355
>Category:       gnats
>Synopsis:       Mail agent output is forwarded by gnatsd
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 04 04:22:36 -0500 2002
>Originator:     Andrew Gray
>Release:        3.999.1

Intel, Linux 2.4.2-2
If the mail agent used to send notification of edits to a
PR generates output then that output is forwarded to the
gnatsd client. This output is not expected by the client.
(For example, Gnatsweb returns to the user a page headed "Error" with the text "Unparseable reply from gnatsd".)
Add or edit the following line to the categories file:
test:*Test Category:gnats-admin:userone
Add the following lines to the responsible file:
userone:User number one:<bad email address>
Submit a PR in the test category.
Connect to the gnatsd server using a telnet client and perform any necessary authentication.
Issue the following commands:
repl <pr_number> State
212 Ok.
213 Ok, now send the field change reason.
/home/gnats/dead.letter... Saved message in /home/gnats/dead.letter
210 Ok.
Change the gnats/ source file to redirect
the standard output of the mail agent to /dev/null:

RCS file: /cvsroot/gnats/gnats/gnats/,v
retrieving revision 1.1
diff -u -p -r1.1
---       22 Dec 1999 04:44:38 -0000      1.1
+++       4 Mar 2002 09:21:03 -0000
@@ -25,4 +25,4 @@


-exec $MAIL_AGENT $@
+exec $MAIL_AGENT $@ > /dev/null


Gnats-prs mailing list

                 reply	other threads:[~2002-03-04  9:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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).