Bug 7359
Summary: | mail2fax parsing error | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jesus Navarro <jesus_navarro> |
Component: | linuxconf | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | jack |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:47:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jesus Navarro
1999-11-26 22:34:25 UTC
Well, a bit more about *when* mail clients will send the From: field between doble quotes. Outlook seems to be very "stubborn", it seems that always will send it so. Netscape, on the other hand seems to only do so when "nasty" characters appear. For instance, being my name Jeszs M. NAVARRO, Netscape would send: "Jeszs M. NAVARRO" <user@domain> "Jesus M. NAVARRO" <user@domain> but... Jesus M NAVARRO <user@domain> That is, if 8bit chars found, then it uses double quotes, so it does if a dot "." appears, but it doesn't worry about blanks. Outlook would send even "NAVARRO" between double quotes. I don't know if it's "legal" send the From: field (the one of the header, nothing about the envelope's From field) quoted or not, but it really seems to me the solution goes through modifying mail2fax_parsename method to take care about the "Name" <user@domain> structure... Well... Jacques Gelinas has been working: he has provided me with a new version of mail2fax which workarounds the problem... Closing because we don't ship linuxconf anymore Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |