Closed Bug 342268 Opened 20 years ago Closed 1 year ago

Posting a message with an empty body through NNTP => not correctly handled

Categories

(MailNews Core :: Composition, defect)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: pascal, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Build Identifier: Thunderbird version 1.5.0.4 (20060516), as well as Mozilla Suite 1.7.13 Thunderbird (and Mozilla as well) allows to post a message to a newsgroup even if the message has an empty body. This gives an error back from the NNTP server; depending on the server (e.g. Microsoft Exchange), the error message may be cryptic. Reproducible: Always Steps to Reproduce: 1. Create a message with an empty body 2. Post it to a newsgroup Actual Results: Error message from the NNTP server. The message contents depends from the server, and may be cryptic. Expected Results: Three possible solutions: 1- Produce a warning before sending. The user should then not be surprised to see an error from the NNTP server. 2- Refuse to send. 3- Generate a dummy empty body and send the message. It is not clear to me if the various RFCs around NNTP allow or not to have an empty body. But all servers I have tested refuse it.
QA Contact: message-compose
bug 3746 comment 32 claims that this is already fixed, and on Trunk, I can confirm that Thunderbird does not send a message if it is empty, but it doesn't warn when doing so apparently...
Assignee: mscott → nobody
URL: N/A
Component: Message Compose Window → MailNews: Composition
Product: Thunderbird → Core
QA Contact: message-compose → composition
nope, it went through...
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Product: Core → MailNews Core
Severity: normal → S3

I'm not sure that an empty body actually violates any RFC or standard, but even if it does, I think the way it's handled now is quite sufficient.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.