Closed Bug 282618 Opened 20 years ago Closed 19 years ago

Messages not forward is rfc822.

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: gworley, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0 (MOOX M3)
Build Identifier: Thunderbird version 1.0 (20041206)

MDaemon has an address call whitelist@address.com.   This is a method to
automatically add false positive dectected spam to the SpamAssassin's WhiteList
database so that it will not be dectected as spam again.  These messages need to
be in RFC822 format.    MDaemon is reporting back:

The message(s) you submitted to be white or black listed were not accepted.  You
must submit these messages to MDaemon as attachments of type message/rfc822. 
When using Outlook Express use the 'Forward as attachment' feature.

In the source of the message is the following:

This is a multi-part message in MIME format.
--------------090808070008020907050607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit



--------------090808070008020907050607
Content-Type: message/rfc822;



Reproducible: Always

Steps to Reproduce:
1. Forward Email as attachment
2 [review]. Wait for response
3. Get response that message wasn't in RFC822 format.

Actual Results:  
Email sent back to me rejected by server saying that it isn't in RFC822 format

Expected Results:  
Forwarded the email in RFC format.
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.