Opened 18 years ago
Closed 17 years ago
#5203 closed enhancement (fixed)
Configurable name in From header
| Reported by: | Noah Kantrowitz | Owned by: | Emmanuel Blot |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | notification | Version: | devel |
| Severity: | normal | Keywords: | olpc |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Attached is a patch to allow controlling the name portion of the From header in notifications.
Attachments (1)
Change History (8)
by , 18 years ago
| Attachment: | olpc_from_name.diff added |
|---|
comment:2 by , 18 years ago
If am understanding RFC 822 correctly, I do not think so. It is supposed to be a "unique" (i.e. identifiable) indicator of the originator of the message. From is the only one that needs to have the human-readable niceness.
comment:3 by , 18 years ago
It seems from RFC 2822 that in any case, the existing code is not compliant with SMTP:
If the originator of the message can be indicated by a single mailbox and the author and transmitter are identical, the
"Sender:" field SHOULD NOT be used. Otherwise, both fields SHOULD appear.
from_email is used for both fields in the current implementation, and this is wrong.
Nevertheless I have not found a reference to the "human-readable niceness" thing. Would you have a section reference about this point? Sender and From seem to support the same mailbox definition, which may optionally include a display name (that is, the "niceness" thing).
follow-up: 5 comment:4 by , 18 years ago
| Status: | new → assigned |
|---|
(Anyway I think this patch is useful)
comment:5 by , 18 years ago
comment:7 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Patch applied in [5509]. Thanks.
Patch to add option for from name. (against r5255)