| Commit message (Collapse) | Author | Files | Lines |
|
We now discard $PYTHONHOME and $PATH as well as the previously
discarded $PYTHONPATH (which we later hand craft). Just a bit of
extra paranoia.
|
|
the try block. Should have no practical effect, but makes debugging
easier.
|
|
the private archive dir.
|
|
value needs to be wrapped in angle brackets.
|
|
last patch. This caused confirmation requests to have a reply-to
pointing back to the list. Closes bug #115253.
|
|
|
|
|
|
|
|
|
|
2.0 patch.
|
|
and use that class here.
|
|
- add support for decoding subjects in links to next and prev message
if the encodings of the two messages are the same
- change re.sub('"',...) with string.replace('"', ...)
- remove unused __processbody_CGIescape method
- vast simplification and speed up of format_article
(still more to do in methods it calls)
- change logic of loadbody_fromHTML to avoid unnecessary tests
- add slightly optimized mailbox class
|
|
replace open calls with explicit open_ex
add load method with code from __init__
|
|
appearing in index. pipermail generated several indexes by assuming
that date was unique. If two messages arrived with, e.g., the same
author and date, then the author index treated them as identical.
As a result, both messages were archived, but only the last one was
included in the index. Solution is to always include the msgid, which
is unique, in the index key.
Change database keys to combine elements using tuples instead of
string concatenation with \000 as separator.
Fix was accomplished by refactoring on pipermail.Database and its
subclasses. Push index-key generation into common concrete base class
Database; rename abstract base class to DatabaseInterface. Break up
addArticle method into several pieces.
TBD There is still more refactoring to do on Database class.
Because date key has changed, HyperDatabase method to return first and
last date changed to reflect format of date key.
Refactor pipermail.T.add_article into several pieces.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
search engine indexing of index and message pages
|
|
|
|
|
|
|
|
|
|
|
|
keep _charsets dictionary in pickled rep of archive; this allows the
charset for an index page to be set based on the total count of
charsets in all messages
|
|
|
|
|
|
|
|
Support the --with-var-prefix
Also change --with-ownername to --with-username
and --with-ownergroup to --with-groupname
and set these up to propagate into substitutions.
|
|
Specifically,
Describe the new --with-var-prefix option.
Also, change --with-ownername to --with-username
and --with-ownergroup to --with-groupname
|
|
Specifically,
VAR_PREFIX gets substituted here by configure. This is where all the
writable, variable directories in Mailman are installed, such as:
LIST_DATA_DIR = $VAR_PREFIX/lists
LOG_DIR = $VAR_PREFIX/logs
LOCK_DIR = $VAR_PREFIX/locks
DATA_DIR = $VAR_PREFIX/data
QUEUE_DIR = $VAR_PREFIX/qfiles
SPAM_DIR = $VAR_PREFIX/spam
PUBLIC_ARCHIVE_FILE_DIR = $VAR_PREFIX/archives/public
PRIVATE_ARCHIVE_FILE_DIR = $VAR_PREFIX/archives/private
Also, MAILMAN_UID and MAILMAN_GID get substituted here by configure
too.
|
|
Specifically,
HyperArchive.html_TOC_entry(): Don't calculate path to
archives/private here; it's already done for us in mm_cfg.
|
|
Specifically,
The following directories (VAR_DIRS) are installed relative to
VAR_PREFIX:
logs, archives, lists, locks, qfiles,
data, spam, filters, archives/private, archives.public
doinstall: Create directories in VAR_PREFIX.
|
|
Specifically,
FILTERSDIR is relative to VAR_PREFIX (site administrators can add
their own filter programs).
|
|
Specifically,
Install pending_subscriptions.db into $DATADIR, which is calculated
relative to VAR_PREFIX.
|
|
Specifically,
calcversions(): Update the comment since the logs dir is now relative
to VAR_PREFIX.
|
|
Specifically,
main(): the REMOVABLES are relative to VAR_PREFIX now.
|
|
Specifically,
MAILMAN_UID and MAILMAN_GID are now available in mm_cfg, so use these
as the gid to check group-ownership against, and as the user to re-run
the script as if there are errors.
checkall(): Now knows about all of PREFIX, EXEC_PREFIX, and VAR_PREFIX
and checks the permissions of them all. It's smart about knowing when
any of these directories are the same.
|
|
Closes David Champion's patch #101331.
|
|
|
|
|
|
Message-ID: header in posted messages. We define a machine parsable
format containing the listname and the hostname, and if these match
our list's name and hostname, we do not munge the header.
This continues to allow crossposting to multiple gated mailing lists,
but should break loops involving the nntpd in the most common case.
Thanks to Jim Tittsler for pointing out the problem.
|
|
None otherwise pure-ascii archives fail to build.
Other de-Python-2.0-ifications.
|
|
Unit test returns same results in Python 1.5.2, 1.6, and 2.0.
|
|
non-ascii charset.
HyperArch:
call write_index_entry from write_threadindex_entry
more style issues; refactoring of several methods
add ctype, charset, and decode attrs to Article; set based on
Content-Type header and an encoded-words in header
add extra blank lines to html templates so that they interact better
with iso-2022-jp text
handle msg <title> and <h1> tags separately to avoid non-ascii
characters in title
add encoding format to index and message headers
add explicit template for index entry
pipermail:
handle messages with timezone gracefully
catch EOFError when loading archive pickle
fix a few bugs that were hidden by bogus overrides in HyperArch
|