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 260995 - Newsgroups: header in emails makes replies malfunction
Newsgroups: header in emails makes replies malfunction
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[nntp]
: 265927 306525 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-07-01 18:17 UTC by Dagmar d'Surreal
Modified: 2021-05-19 11:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dagmar d'Surreal 2004-07-01 18:17:59 UTC
Description of Problem:
If an email has a Newsgroups: header in it (as is
the case with some mailing lists, in particular
Beyond Linux From Scratch when someone posts to
the NNTP server and the post is then relayed out
to the mailing list) when one clicks Reply for the
_email_ Evolution will attempt to post an NNTP
reply to an mbox: which just isn't going to work.


Steps to reproduce the problem:
1. Email yourself something with an email
containing the Newsgroups: header.
2. Select it in the message list pane for your
inbox and try to reply to it.
3. That's all.

Actual Results:
Instead of the email having a To: field, it will
have the Post-To: button with something like
"mbox:/home/dagmar/.evolution/mail/local/blfs.support"
as the value.


Expected Results:
It should attempt to reply to the sender.


How often does this happen?
All the time as far as I can tell.

Additional Information:
I'm currently recompiling 1.5.9.2 with
--enable-nntp=no to make it explicit that it
shouldn't have any NNTP support.  I didn't specify
either way at all for this compile, and the
configure script help appears to indicate the
default is to not enable it, so I would think it
wouldn't even try to do this.
Comment 1 Simon Geard 2004-09-15 01:55:53 UTC
*** bug 265927 has been marked as a duplicate of this bug. ***
Comment 2 Jeffrey Stedfast 2005-02-04 20:26:25 UTC
the way reply works doesn't depend on what folder type the message
lives in (in fact it can't depend on that because the folder types are
all abstract so we can't tell the difference between nntp folders vs
imap vs mbox vs maildir, etc)

no idea how to solve this...
Comment 3 Martin Kretzschmar 2005-02-09 17:11:08 UTC
bug 266529 says, emptying the Post-To: entry and readding To: would be
a workaround. However, that doesn't work, this error alert box is
displayed:

"Cannot send message: no recipients defined.."
Comment 4 André Klapper 2005-09-25 01:43:45 UTC
retargetting from very ancient 2.1 milestones to just ancient 2.3 milestones.
it just sucks to click several target milestone values.

sorry for the noise.
Comment 5 Karsten Bräckelmann 2006-02-06 22:22:36 UTC
*** Bug 306525 has been marked as a duplicate of this bug. ***
Comment 6 Karsten Bräckelmann 2006-02-06 22:32:43 UTC
Please see bug 306525 for some details, examples and discussion.

* Bug 306525 comment 1 has an attachment 47253 [details] screenshot, to see the result.
* Bug 306525 comment 3 offers some details how to reproduce this issue with the
  snippet given in bug 306525 comment 0.

Possible solution (see bug 306525 comment 9):
There is a filter to filter on source-account. Use this. If the source account is not a NNTP account, we never ever should post the reply to the group -- unless specifically requested by "Post Reply".


Inheriting Cc's from that duplicate, setting Version properly.
Comment 7 Karsten Bräckelmann 2006-02-06 22:35:52 UTC
Adding partha to Cc as well. Setting usability keyword.

Vardhan: If not 2.5, then definitely 2.7 later, once it is available as a Target Milestone. This is not Future.
Comment 8 Christoph Wickert 2009-10-18 10:47:57 UTC
Still happens in evolution 2.26.3. The value of the Post-To field creates strange folders that cannot be deleted as described in bug 598249.

In 2.28.x the situation is a little better. There is no Post-To and the To field is no longer greyed out, so one can manually add recipients.

For more details about the current situation please take a look at my report in Red Hat bz: https://bugzilla.redhat.com/show_bug.cgi?id=528839
Comment 9 Christoph Wickert 2009-10-18 10:52:40 UTC
This is a violation of RFC 2076:
"Followup-To:
...
In e-mail, this header may occur in a message which is sent to both e-mail and Usenet News, to show where follow-up in Usenet news is wanted. The header does not say anything about where follow-up in e-mail is to be sent."

http://tools.ietf.org/html/rfc2076#section-3.5
Comment 10 Milan Crha 2010-01-08 17:18:23 UTC
(In reply to comment #8)
> In 2.28.x the situation is a little better. There is no Post-To and the To
> field is no longer greyed out, so one can manually add recipients.

From what I understand this bug report it is fixed in actual stable, thus I'm closing this. Feel free to reopen if I misunderstood it. Thanks.
Comment 11 Christoph Wickert 2010-01-08 17:51:33 UTC
Milan, it is not fixed in 2.28.2: Although the mail has a valid Reply-To, the To: field is empty when I choose reply. When I choose "Reply to all" I get the mailing list in the To: field but not the sender in CC as one would expect.

To summarize:
1. The nntp header should not make the mail being handled differently, this means that
2. "Reply" should reply to Reply-To: and
3. "Reply to all" should Reply to Reply-To: and to From: directly.

Please reopen, I don't have sufficient privileges.
Comment 12 Milan Crha 2010-01-11 10:25:04 UTC
OK, I firstly thought that empty To is a new thing, but thinking of it now you've right, it can be dealt with it in this bug report.
Comment 13 André Klapper 2021-05-19 11:57:16 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.