GNOME Bugzilla – Bug 274117
Difficult to post a new message to newsgroups
Last modified: 2009-07-11 12:41:39 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: The 'compose' window should have a visible 'Post To:' field when making a new post to newsgroups Steps to reproduce the problem: 1. Open any newsgroup in the mail reader 2. Click on 'New' to create a new post 3. Now try to figure out how to post your message to the newsgroup Actual Results: The compose window creates an email message by default, with no easy way to convert it to a news post. Expected Results: The name of the current newsgroup should be filled in by default How often does this happen? Every time Additional Information: The right thing happens when 'Reply'ing to a post, but not when sending a new post.
Aha! I see now that the 'Actions' menu has the Post-New-Message item, which is exactly what should happen when I click on the 'New' button while reading a newsgroup. So, can the default response to the 'New' button be conditioned on whether I am reading mail or news?
still in 2.5.5, item is now in the "message" menu
*** Bug 327919 has been marked as a duplicate of this bug. ***
It would be nice that when we are on a newgroup, to have the address of the newsgroup filled in by default.
*** Bug 340602 has been marked as a duplicate of this bug. ***
Relative standard features in news clients (not evo) are the following: When a news group and a news message is selected * "New" or "Post" = post new message to news group (no, not to "folder") * "Followup" = post a reply to the news group * "Reply [to sender]" = reply to sender via email, not via nntp * "Reply all" = "Followup" + "Reply to sender" It is also customary to be able to set "Follow-up to:" which is NOT the same as "Reply to:", the first is a news group, the second is email. Section 3 of rfc 1855 is also pretty relevant here.
Bumping version to a stable release.
*** Bug 383543 has been marked as a duplicate of this bug. ***
*** Bug 569247 has been marked as a duplicate of this bug. ***
*** Bug 550732 has been marked as a duplicate of this bug. ***
Fixed in http://git.gnome.org/cgit/evolution/commit/?id=a1f287ca6bf35d27e5dcb9b89a10f76e9abbd057 See the commit message for discussion. Note, this does not address comment #6, which I'll deal with separately.
*** Bug 577446 has been marked as a duplicate of this bug. ***
*** Bug 577444 has been marked as a duplicate of this bug. ***
*** Bug 588210 has been marked as a duplicate of this bug. ***
*** Bug 588311 has been marked as a duplicate of this bug. ***