After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 274117 - Difficult to post a new message to newsgroups
Difficult to post a new message to newsgroups
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other other
: Normal minor
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer] evolution[nntp]
: 327919 340602 383543 550732 569247 577444 577446 588210 588311 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-03-26 20:24 UTC by walt
Modified: 2009-07-11 12:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description walt 2005-03-26 20:24:29 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.
Comment 1 walt 2005-03-26 20:49:43 UTC
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?
Comment 2 André Klapper 2006-01-23 17:08:47 UTC
still in 2.5.5, item is now in the "message" menu
Comment 3 André Klapper 2006-01-23 17:09:49 UTC
*** Bug 327919 has been marked as a duplicate of this bug. ***
Comment 4 Nicolae Fieraru 2006-02-06 09:19:04 UTC
It would be nice that when we are on a newgroup, to have the address of the newsgroup filled in by default.
Comment 5 André Klapper 2006-05-09 09:46:50 UTC
*** Bug 340602 has been marked as a duplicate of this bug. ***
Comment 6 james.baum 2006-05-09 10:36:04 UTC
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.
Comment 7 Matthew Barnes 2008-03-11 00:27:19 UTC
Bumping version to a stable release.
Comment 8 Matthew Barnes 2009-05-20 15:05:17 UTC
*** Bug 383543 has been marked as a duplicate of this bug. ***
Comment 9 Matthew Barnes 2009-05-20 15:06:11 UTC
*** Bug 569247 has been marked as a duplicate of this bug. ***
Comment 10 Matthew Barnes 2009-05-20 17:05:34 UTC
*** Bug 550732 has been marked as a duplicate of this bug. ***
Comment 11 Matthew Barnes 2009-05-20 17:12:05 UTC
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.
Comment 12 Matthew Barnes 2009-05-20 17:16:49 UTC
*** Bug 577446 has been marked as a duplicate of this bug. ***
Comment 13 Matthew Barnes 2009-05-20 17:19:58 UTC
*** Bug 577444 has been marked as a duplicate of this bug. ***
Comment 14 Matthew Barnes 2009-07-10 02:02:49 UTC
*** Bug 588210 has been marked as a duplicate of this bug. ***
Comment 15 Matthew Barnes 2009-07-11 12:41:39 UTC
*** Bug 588311 has been marked as a duplicate of this bug. ***