Fail to return a receipt when Disposition-Notification-To header is on more than one-line



MailNews: Backend
14 years ago
10 years ago


(Reporter: Kalin Kozhuharov, Assigned: Bienvenu)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031018
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031018

I just got a rfc2822 violating mail, i.e. split header with second line NOT
starting with white-space-character and Mozilla(1.5, just built) failed to send
a return receipt (my qmail MTA said: bare LF!).
Then I started experimenting with different versions of the
Disposition-Notification-To header and what I found is that if the header body
is split in two lines (or more?), EVEN CORRECTLY (i.e. with white-space-char at
the beginning), Mozilla cannot send a return receipt.

Reproducible: Always

Steps to Reproduce:
1. Send a mail with Disposition-Notification-To header body split into 2 lines
(perhaps a veeeeery long From address, so it gets split)
2. Open it in Mozilla Mail.
3. Click ok to send the return receipt.

Actual Results:  
If you have a good MTA (qmail), it will report back error. Otherwise undefined,
but possibly a mail with bare LF will be send.

Expected Results:  
Sendidng a RR should happen.

For bare LFs, see:

The mail I've got was sent from:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.0.1) Gecko/20020823
which is probably another bug to be filed.

Mozilla 1.5 does not split the Disposition-Notification-To header into 2 lines,
even when it is veeery long.

An example: rfc correct, but not working header:

Disposition-Notification-To: My mail <CRLF>
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED


10 years ago
Component: MailNews: Return Receipts → MailNews: Backend
QA Contact: grylchan → offline
You need to log in before you can comment on or make changes to this bug.