This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Future of gccbug



On Nov 7, 2003, at 6:40 PM, Andreas Schwab wrote:


Daniel Berlin <dberlin@dberlin.org> writes:

I have a feeling something is changing the message-id on us when it sends
it to a remote server, but not when it sends it locally to the list
delivery process.

It appears that none of the follow-up messages have a message-id when sent
out by bugzilla, so that they get one generated by the MTA. Only the
first message of a bug has the previously mentioned message-id format.


Yup.
It's a problem in Bugzilla, but i'm not sure how to do this, since we
1. Send out each email seperately (IE it's not processing them as a group)
2. We only know whether a bug email is because of a new bug or not.


I'll see what i can come up with.

These are two message-ids of the mails I received for a bug where I'm on
the cc list:


Message-ID: <20031106044749.14931.qmail@sources.redhat.com>
Message-ID: <20031106044749.14953.qmail@sources.redhat.com>

This is the reference in the mails:

References: <20030407161600.10339.ubell@sleepycat.com>

Andreas.

--



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]