Red Hat Bugzilla – Bug 7359
mail2fax parsing error
Last modified: 2008-05-01 11:37:53 EDT
Mail to fax gateway activated thro linuxconf.
When a valid e-mail is recieved thro sendmail, mail2fax program is
invocated. It tries to split the message from header to send it to fax.
Part of this is made be the mail2fax program.
There is, within mail2fax, a call to the mail2fax_parsename function
(within mailhead.cc) which expects, as is commented in the source code the
e-mail address with one of these formats:
Still, at least Windows' version of both Internet Explorer (5.0 was tested)
and Nestcape Communicator (version 4.04 was tested) send this with the
(note the double quotes at "username"), so mail2fax, in this case, returns
"username" instead of username. Being double quotes a forbidden char
within mail2fax, the program througs away the fax with the
Fax with invalid characters: rejected
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"
For instance, being my name Jeszs M. NAVARRO, Netscape would send:
"Jeszs M. NAVARRO" <user@domain>
"Jesus M. NAVARRO" <user@domain>
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.