public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: girgen@partitur.se To: gnats-gnats@sourceware.cygnus.com Subject: gnats/11: file-pr fails to separate email addresses to notify Date: Mon, 11 Oct 1999 17:24:00 -0000 [thread overview] Message-ID: <19991012001418.29402.qmail@sourceware.cygnus.com> (raw) >Number: 11 >Category: gnats >Synopsis: file-pr fails to separate email addresses to notify >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Oct 11 17:24:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Palle Girgensohn >Release: 3.112.1 >Organization: >Environment: FreeBSD-RELEASE-3.0 >Description: file-pr creates a list of email addresses to notify using the Resent-CC mail header. There's a bug that makes it fail separating the addresses with a comma. This can lead to a new mail beeing sent to gnats-admin, which generates a new report. This new mail is in turn generating a new report, a we have an endless loop! The try_append_notify function doesn't use the returned char*, but uses its input argument. >How-To-Repeat: Here's what I had in my categories file: test:*Test Category:girgen:girgen@e.kth.se and submitters: submitters:partitur:Partitur:none:24:gnats-admin:palle@partitur.se and here's the mail header: Resent-CC: gnats-adminpalle@partitur.segirgen@e.kth.se I realize this code in file-pr is quite modified in the current cvs-tree, but this patch should probably be used until that code is in the 3.x branch. >Fix: --- file-pr.c~ Wed Sep 22 01:18:39 1999 +++ file-pr.c Tue Oct 12 01:42:21 1999 @@ -708,7 +708,7 @@ char *try = append_notify (string); if (try != NULL) { - strcat (notify, string); + strcat (notify, try); xfree (try); } } >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~1999-10-11 17: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: 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=19991012001418.29402.qmail@sourceware.cygnus.com \ --to=girgen@partitur.se \ --cc=gnats-gnats@sourceware.cygnus.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: linkBe 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).