Patches item #657951, was opened at 2002-12-23 14:17
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…
Category: Pipermail
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 7
Submitted By: A.M. Kuchling (akuchling)
Assigned to: Nobody/Anonymous (nobody)
Summary: Generate RSS summary in archives
Initial Comment:
Here's a first-draft patch. Things that need fixing:
* The generated RSS feed needs to be validated. (It passed the
W3C's RDF validator, but RSS validators still need to be checked.)
* The date should be given in YYYY-MM-DD format, which requires
parsing the .fromdate attribute.
* How do I get the URL for an archived message? The generated RSS
currently just uses the filename, which is wrong. How do I get
at the PUBLIC_ARCHIVE_URL setting?
* Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them.
We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...)
* The list index page should have a LINK element pointing to
the RSS file.
Please make any comments you have, and I'll rework the patch accordingly.
----------------------------------------------------------------------
>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2003-04-18 18:43
Message:
Logged In: YES
user_id=12800
Andrew, to get the url for the archived message use
mlist.GetBaseArchiveURL(), which knows about private vs.
public archives, the host name and the list name. From
there you should be able to tack on just the part of the
path under "archives/private/listname". See
Mailman/Handlers/Scrubber.py for an example.
Only other minor comment: NUM_ARTICLES can probably go in
Defaults.py.in
----------------------------------------------------------------------
Comment By: Justin Mason (jmason)
Date: 2003-03-26 16:49
Message:
Logged In: YES
user_id=935
big thumbs up from me too. Much better solution than
http://taint.org/mmrss/ ;)
----------------------------------------------------------------------
Comment By: Uche Ogbuji (uche)
Date: 2003-03-17 20:09
Message:
Logged In: YES
user_id=38966
I'd like to add my vote to this item. This is a fantastic
idea, Andrew. Thanks.
--Uche
----------------------------------------------------------------------
Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 15:42
Message:
Logged In: YES
user_id=11375
Updated patch:
* Dates are now rendered as ISO-8601 (date only, not the time of the message)
* By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator.
----------------------------------------------------------------------
Comment By: captain larry (captainlarry)
Date: 2002-12-23 14:36
Message:
Logged In: YES
user_id=147905
Just voting for support here. This is *great* thanks for
the patch and I hope the maintainers include it as soon as
it's appropriate :)
Adam.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-23 14:27
Message:
Logged In: YES
user_id=12800
Deferring until post-2.1
----------------------------------------------------------------------
Comment By: A.M. Kuchling (akuchling)
Date: 2002-12-23 14:21
Message:
Logged In: YES
user_id=11375
Argh; SF choked on the file upload. Attaching the patch again...
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…
Public bug reported:
When a message contains an invalud unicode sequence in its header,
qrunner flat out crashes on that:
May 17 15:32:20 2015 (981) Uncaught runner exception: 'utf8' codec can't decode byte
0xe9 in position 18: invalid continuation byte
May 17 15:32:20 2015 (981) Traceback (most recent call last):
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
self._onefile(msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 239, in process
i18ndesc = uheader(mlist, mlist.description, 'List-Id', maxlinelen=998)
File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 65, in uheader
return Header(s, charset, maxlinelen, header_name, continuation_ws)
File "/usr/lib/python2.7/email/header.py", line 183, in __init__
self.append(s, charset, errors)
File "/usr/lib/python2.7/email/header.py", line 267, in append
ustr = unicode(s, incodec, errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe9 in position 18: invalid
continuation byte
May 17 15:32:20 2015 (981) SHUNTING:
1431869540.389822+156779307d54473d0eb732994bb67eee95733285
A solution for this specific case is to have Mailman/Handlers/CookHeaders.py pass the erorrs='replace' parameter.
I would say that this is actually a bug in python-email, since I think it doesn't make sense to set errors to "strict" rather than something like "replace" when the intention is to parse stuff so free-formed, under-specd
and user-controlled as email. Nonetheless, Mailman already sets errors='replace' in some places so it might aswell add it here.
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1462755
Title:
qrunner crashes on invalid unicode sequence
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1462755/+subscriptions
Public bug reported:
We need a script, documentation, or other procedure to help people
migrate from Mailman 2 to Mailman 3.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/965532
Title:
Need a script to upgrade from MM2 to MM3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/965532/+subscriptions
Public bug reported:
Mailman 3 is essentially five projects:
Mailman Core
Postorius - The Web UI for Mailman
Mailman Client - The REST API Client
HyperKitty - The Archiver for Mailman
Mailman Bundler - Installer for Mailman Suite including all above projects
URL: https://www.gnu.org/software/mailman/
** Affects: mailman
Importance: Undecided
Status: New
** Affects: ubuntu
Importance: Undecided
Status: New
** Affects: debian
Importance: Unknown
Status: Unknown
** Tags: needs-packaging
** Bug watch added: Debian Bug tracker #799292
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799292
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799292
Importance: Unknown
Status: Unknown
** Also affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1609516
Title:
[needs-packaging] GNU Mailman v3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1609516/+subscriptions
Public bug reported:
Setting localhost in postfix_lmtp works against Postfix defaults and
breaks delivery.
Reason: The Postfix lmtp client only uses dns queries by default to
search for hostnames. If the DNS server does not provide an answer for
"localhost" delivery from the lmtp client to mailman fails.
Solution: Provide "127.0.0.1" instead of "localhost". This does not
require DNS and is even faster because it saves DNS lookups.
Example:
hey2(a)mailman.state-of-mind.de
lmtp:[localhost.localdomain]:8024
** Affects: mailman
Importance: Undecided
Status: New
** Tags: 3.0 mailman
--
setting localhost in postfix_lmtp breaks delivery
https://bugs.launchpad.net/bugs/544477
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
MM3 still uses a lot of X- headers, but some of the X- prefixes can be
removed. In general, we can just claim the Mailman- prefix for Mailman
specific headers. Candidates include:
Mailman-Rule-Hits
Mailman-Rule-Misses
Mailman-Version
Mailman-Approved-At
Mailman-LMTP-MailFrom (i.e. X-MailFrom)
Mailman-Copy (or remove this header)
Mailman-Content-Filter (from X-Content-Filtered-By)
Also, fix the outdated comments about add-dup-header in
avoid_duplicates.py and verp.py.
Probably also get rid of X-List-Administrivia (and possibly
reduced_list_headers). These seem unnecessary now.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/883193
Title:
Remove the X- prefix from some headers
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions
Public bug reported:
It looks like there is no way for a MM3 plugin to be signaled for a new
posting.
It would be great if core could provide a notification to the plugins
that have subscribed to this event when a new post occurs.
This notification should carry some interesting information, like the
number of recipients and the message size.
This request is also essential for the MM3-Metrics module
(https://launchpad.net/mm3-metrics).
** Affects: mailman
Importance: Undecided
Status: New
** Tags: events mailman3 metrics modules notification plugins post
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1094696
Title:
Event notifications on postings
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1094696/+subscriptions
Public bug reported:
Mailman Core and Postorius have sets of tests, but could use more
extensive test coverage. This bug is meant to be a repeatable bug
suitable for new contributors (e.g. prospective Google Summer of Code
Students). In short: find a piece of Postorius or Mailman Core that
isn't yet tested and write a test (or set of tests) for it.
Contributors wishing to work on Mailman Core should look at START.rst
and DATABASE.rst for more information about setting up tests.
For Postorius, Florian is working on vcrpy test integration, so new
tests can use that format.
Links to documentation and examples much appreciated to update this bug!
** Affects: mailman
Importance: Undecided
Status: New
** Affects: postorius
Importance: Undecided
Status: New
** Tags: beginner-friendly easy mailman3 repeatable test
** Tags added: easy mailman3
** Also affects: mailman
Importance: Undecided
Status: New
** Description changed:
- Postorius has a set of tests, but it could use more extensive coverage.
- This bug is meant to be a repeatable bug suitable for new contributors
- (e.g. prospective Google Summer of Code Students). In short: find a
- piece of postorius that isn't yet tested and write a test (or set of
- tests) for it.
+ Mailman Core and Postorius have sets of tests, but could use more
+ extensive test coverage. This bug is meant to be a repeatable bug
+ suitable for new contributors (e.g. prospective Google Summer of Code
+ Students). In short: find a piece of Postorius or Mailman Core that
+ isn't yet tested and write a test (or set of tests) for it.
- Florian is working on vcrpy test integration, so new tests can use that
- format.
+ Contributors wishing to work on Mailman Core should look at START.rst
+ and DATABASE.rst for more information about setting up tests.
+
+ For Postorius, Florian is working on vcrpy test integration, so new
+ tests can use that format.
+
+ Links to documentation and examples much appreciated to update this bug!
** Tags added: repeatable
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1414352
Title:
Improve code coverage by adding tests
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1414352/+subscriptions
Public bug reported:
Falcon 0.2 contains a bug in parsing fields with commas and newlines.
We will block the Mailman 3 final release on the release of Falcon 0.3
to PyPI.
** Affects: mailman
Importance: Critical
Assignee: Barry Warsaw (barry)
Status: Triaged
** Tags: mailman3 mailman3-suite-blocker
** Branch linked: lp:~raj-abhilash1/mailman/bugfix
** Tags added: mailman3-suite-blocker
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1446881
Title:
Require Falcon 0.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1446881/+subscriptions
Public bug reported:
Code added to Tagger.py in 2.1.16 to support the from_is_list Wrap
Message option contained a misspelling.
** Affects: mailman
Importance: High
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1251495
Title:
Lists with topics enabled can throw unexpected keyword argument
'Delete' exception.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions