public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Dirk Bergstrom" <dirk@juniper.net>
To: <help-gnats@gnu.org>
Subject: X-GNATS-NOTIFY & the CC list in 4.0
Date: Fri, 21 Dec 2001 19:13:00 -0000	[thread overview]
Message-ID: <C53744A44FBC9B4BAE90EB41D2C09AC205225E@proton.jnpr.net> (raw)
Message-ID: <20011221191300.WPgKWpdQEgBsdp6jkctsDZ4pymWgWDeFsr689C4esvk@z> (raw)

after much testing and digging around the sources, it appears to me that gnats more or less ignores both the X-GNATS-Notify: and Cc: headers of a PR when sending out state-change messages (the "audit-mail" mail-format).

gnatsweb happily populates and reads XGN & Cc headers, leading one to believe that they are useful, but no matter how i mess around in dbconfig, i can't get gnats to generate mail to the addresses in the Cc or XGN headers.

i've tried adding "cc", "x-gnats-notify", "headers[cc]", "$MailCC", and a couple other things to the to-addresses list in the audit-mail mail-format, with no luck.  i dug thru the sources, and found the code that generates headers, but i haven't been able to decipher the twisty maze of structs, enums and subroutine calls that are used to grab email addresses.   from this (mail.h):

/* These addresses are always mapped through the responsible adm
   file.  */
struct mail_address
{
  /* A fixed name.  */
  char *fixedAddress;
  /* A list of addresses to try--each one is tried in turn until a
     non-empty one is found. */
  FieldList addresses;
};

it looks like the source for mail addresses are all gnats fields, and not headers (or "fixed-address" values from the dbconfig file).  actually, they can also be parameters (like "$EditUserEmailAddr"), but there are a limited set of those, and they don't include cc or xgn.

i vaguely remember reading somewhere that X-GNATS-Notify was deprecated, or just plain didn't work, but i can't find such a thing now.  i've searched the manpages, the *.texi files, and the changelogs, and i can't find any mention of them in 4.0.

so, does anyone know what the deal is with these headers?  if they are unsupported, we should either support them in gnats, or remove them from gnatsweb.  if they are supported, somebody needs to tell me how to get at them in a meaningful way.

thanks.

--
Dirk Bergstrom               dirk@juniper.net
_____________________________________________
Juniper Networks Inc.,          Computer Geek
Tel: 707.433.0564           Fax: 707.433.0769

_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2001-12-21 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-17  9:43 Dirk Bergstrom [this message]
2001-11-17 12:27 ` Paul Traina
2001-12-22  8:16   ` Paul Traina
2001-12-21 19:13 ` Dirk Bergstrom
2001-11-18 19:29 Dirk Bergstrom
2001-11-20 17:52 ` Milan Zamazal
2001-12-23 14:13   ` Milan Zamazal
2001-12-22 14:45 ` Dirk Bergstrom
2002-05-21  1:55 ` Lars Henriksen

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=C53744A44FBC9B4BAE90EB41D2C09AC205225E@proton.jnpr.net \
    --to=dirk@juniper.net \
    --cc=help-gnats@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).