Bug 491096 - Evolution fails to cross-post NNTP properly, violates RFC3977
Summary: Evolution fails to cross-post NNTP properly, violates RFC3977
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-19 13:28 UTC by David Woodhouse
Modified: 2009-06-29 01:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-06-29 01:40:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 587257 0 None None None Never

Description David Woodhouse 2009-03-19 13:28:57 UTC
When cross-posting to multiple news groups, Evolution seems to be submitting _multiple_ messages with the same Message-Id: header, each to only one group. These seem to get eaten by the news server, not entirely surprisingly. RFC3977 says that Message-ID MUST be unique.

Compare Evolution's attempt at cross-posting: http://david.woodhou.se/postdump.cap
With Pine: http://david.woodhou.se/post-dump-3.cap

The important part being that Evolution does this...

post

340 340 <49c24468$0$513$5a6aecb4.net.uk> (desired)

Newsgroups: uk.net.providers.aaisp

Subject: News cross-posts silently discarded?
 ...

post

340 340 <49c24468$1$513$5a6aecb4.net.uk> (desired)

Newsgroups: uk.test

Subject: News cross-posts silently discarded?


While Pine does it in one go:

POST

340 340 <49c246b4$0$511$5a6aecb4.net.uk> (desired)

Path: macbook.infradead.org!dwmw2

Newsgroups: uk.test,uk.net.providers.aaisp

Date: Thu, 19 Mar 2009 13:20:47 +0000

From: David Woodhouse <dwmw2.org>

Subject: Cross-posting, again.

Comment 1 Matthew Barnes 2009-06-29 01:40:19 UTC
Moving this upstream for better visibility.
Please see [1] for further updates.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=587257


Note You need to log in before you can comment on or make changes to this bug.