205836 - Header's parameter "To:" is not right after the "From: " parameter.

Status: RESOLVED INVALID

(MailNews Core :: Networking: SMTP, defect)

Description

[Maxime Bouffard]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030515
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030515

When the smtp gateway of Interstar inc's LightningFAX for Linux is trying to
retreived an email with a fax number on the "To:" parameter of the e-mail 's
header (example: To: "1112222"<[e-mail]>), the smtp gateway can see the
message but is not able to retreive it from the pop3 server. Mozilla mail agents
users cannot send e-mails to fax machines because of that. The problems lays in
the fact that the "To:" parameter is not right after the "From:" parameter.

Reproducible: Always

Steps to Reproduce:
1.Install and setup correctly Interstar's LightningFAX server, drivers and smtp
gateway to a Linux Box equiped to fax with a loop-start board.
2.Send an e-mail with Mozilla mail agent (mine is 1.4b) with an e-mail address
including a fax number ("1112222"<[e-mail]) be sure the e-mail address is
setup in the config of the smtp gateway.
3. Look at the smtp gateway logs and see that the message cannot be retreived
from the pop3 server.

Actual Results:  
Unable to send fax via e-mail with smtp gateway.

Expected Results:  
Put the "To:" parameter of Mozilla's mail agent mail header right after the
"From:" parameter.

I found this by editing the header sources of the e-mail message and tried to
put the "To:" parameter on other lines in the mail header. This bug must be
really easy to fix, but surely can lead to other problems of the same kind
involving mail headers. I submitted it also to Interstar Inc
(http://www.interstarinc.com/products/lightningfax/features.htm).

Comment 1

[Jo Hermans]

The mail-RFC's don't say anything about the order of the headers. Why is this a
bug in Mozilla ? This looks to me as a bug in LightningFAX.

Comment 2

[Karsten Düsterloh]

It's definitely not a Mozilla bug - headers can be in any order.