Open Bug 362289 Opened 18 years ago Updated 18 years ago

Use contents of Sender: header field as envelope sender if it exists

Categories

(Bugzilla :: Email Notifications, enhancement, P4)

Product:
Bugzilla
Component:
Email Notifications
Type:
enhancement

Tracking

()

People

(Reporter: holmgren, Unassigned)

Details

User-Agent:       Opera/9.02 (X11; Linux i686; U; en)
Build Identifier: 

MessageToMTA() currently uses the contents of the From: header field as the envelope sender (sendmail -f parameter). It would be better if the Sender: field were used if it exists, so that mail is sent with an appropriate return address, should the admin wish to modify the newchangedemail notification template to put the changed in the From: field and Param('mailfrom') in Sender:, just to take an example (bug 126151).

Reproducible: Always




Unfortunately Email::Send::SMTP likewise takes the envelope sender from the From: field as of version 2.181, and it can't be overridden. That's OK in a MUA, but not in this case.
Upstream Bugzilla doesn't include any "Sender" headers, so at this point we're unlikely to fix this here. 

In general, we don't add code to handle things that we don't actually do.

However, if we ever do add any Sender headers, this would make sense.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
I'm sorry but I don't understand your reasoning. Bugzilla *can* include "Sender:" fields, it just doesn't do it in a default installation. Once again, templates *are* supposed to be customized, aren't they? Though it was easier before, when newchangedmail was simply a parameter.

What do you mean "Upstream Bugzilla"? Do you mean that you're only ever going to add features that you planning to use here at bugzilla.mozilla.org? I certainly don't hope so, and I honestly don't think so either. As a prominent example, bugs.kde.org sets From: to the changer and Sender: to owner@bugs.kde.org.

So, considering that the fix is one line (at least for the Sendmail method) and unobtrusive, and that people actually use it, will you please leave it open or at most mark it LATER?
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
I think this makes sense. Although it will be very low priority (patches welcome;).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Okay. Going along with Olav on that.
Priority: -- → P4
You need to log in before you can comment on or make changes to this bug.