http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45904
Summary: Email addresses used by Bugzilla
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: web
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: js...@gcc.gnu.org
CC: f...@redhat.com
GCC Bugzilla is currently sending emails with From: address
gcc-bugzilla-nore...@gcc.gnu.org. This is very bad because it means email
replies get a bounce:
Hi! This is the ezmlm program. I'm managing the
g...@gcc.gnu.org mailing list.
This is a generic help message. The message I received wasn't sent to
any of my command addresses.
We need to use a valid address here. Since people may reply to the messages
sent to gcc-bugzilla-noreply at any time in the future, it would be a good idea
to make that address into a valid address for some period of time after the
messages revert back to coming from gcc-bugzilla, and to contact people who
sent messages during the time it bounced to ask them to resend them.
The *envelope* sender can be an invalid address, and should be to avoid bounces
getting filed in bugs, but the header From: address must not be. The critical
problem is the header address which will lose contributions to bug reports
while it remains as is.
