| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
at least 0660. b4b5-archfix can mess these perms up.
|
| |
|
|
|
| |
mailbox processing. It's good enough for the caller of this code to
do the exception handling.
|
| | |
|
| |
|
|
| |
resolved
|
| |
|
|
| |
afterwards.
|
| |
|
|
|
|
|
| |
pulling the Subject out of the command message. That's so later
(e.g. in cmd_confirm.py) we won't try to .lower() a None.
Closes SF bug report # 620032 by Ron Jarrell.
|
| |
|
|
|
|
| |
closes SF patch # 635227.
Also, whitespace normalization.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
just an empty string. This avoids seeing the u'' when no real name
was given.
|
| | |
|
| |
|
|
| |
Personalization".
|
| |
|
|
| |
2, meaning "Full Personalization".
|
| |
|
|
|
| |
Personalization" meaning to additionally munge the To field. Update
the details for this option.
|
| | |
|
| | |
|
| |
|
|
| |
what check_perms expects.
|
| |
|
|
| |
at least 0644 and directories 0755.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hold. Chuq says:
looks like 2.1b4 is evaluating messages slightly out of order. If
I get a large piece of spam (my message limit is 30K, the spam is,
say, 60k), it gets held as too large, before the evaluation can
take place that should reject it as being from a
non-subscriber. Seems to me these evaluations ought to be
reversed...
But I must have had a good reason for changing this in rev 2.102:
----------------------------
revision 2.102
date: 2002/08/23 19:56:08; author: bwarsaw; state: Exp; lines: +1 -1
GLOBAL_PIPELINE: Reordering the modules so that Hold comes before
Moderate.
----------------------------
Unfortunately, the checkin message doesn't give me a clue as to why I
made this change. I'm sure the reason will become evident soon
enough. :(
|
| | |
|
| |
|
|
|
| |
for which we actually have the charset support built into the system.
I think codecs.lookup() is the best way to determine this.
|
| |
|
|
| |
in the language of the create page.
|
| |
|
|
| |
giving it some text and a detail.
|
| |
|
|
|
|
|
|
|
|
|
| |
the membership management pages, the u/i for emergency moderation is
changed. Now, if the list is not being moderated, no indication under
the categories is made (we can change this if people want).
To turn on emergency moderation, you need to go to the General
category under Additional Settings. If you enable emergency
moderation, you will get the big red sign, but no checkbox -- the sign
will be linked to the VARHELP for the emergency option.
|
| |
|
|
|
|
| |
messages. It was too controversial to do To header rewriting by
default, but we might want to re-enabled this for a future version,
probably controlled by a configuration variable.
|
| |
|
|
|
|
| |
personalized messages. It was too controversial to do this by
default, but we might want to re-enabled this for a future version,
probably controlled by a configuration variable.
|
| | |
|
| |
|
|
| |
take note!
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
applied. The problems were twofold:
- The _mlist attribute of Article objects was being pickled, causing
the *-article pickles to be around 10x too big.
- The article template files were being opened and re-read for each
article.
Fixes include pickling only a reference to the mailing list (i.e its
internal name), and caching both the MailList objects and the template
files. Specifically,
quick_maketext(): Front-end to the template cache, this has the same
signature as Utils.maketext(), but it caches as much of the results as
possible.
Article._open_list(): A MailList cache, stolen from Runner.py. Can
you say "re-factor"?
Article.__getstate__(): Don't pickle the _mlist instance, instead,
return an __listname key which contains the internal name of the
mailing list.
Article.__setstate__(): Watch for __listname and call _open_list() to
get a real MailList object.
Everywhere: Use quick_maketext() instead of Utils.make_text() to take
advantage of the template cache.
|
| |
|
|
|
|
|
|
|
|
| |
the lock object. The real problem, as sleuthed out by Dan Mick, was
that the archiver i18n patches added a _mlist attribute to Article
objects, which caused the MailList instances to get pickled into the
*-article pickles.
See fixes to HyperArch.py and HyperDatabase.py for additional
important fixes.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
double %'s.
to_percent(): Vice versa.
|
| |
|
|
| |
Mazioli da Silva.
|
| |
|
|
|
|
|
|
|
| |
where if the list lock couldn't be obtained, we couldn't register the
bounce and the message would get forwarded to the list owners.
Instead, let's just requeue it and try again later.
Note: untested! I'm checking this into cvs so I can test it on
python.org... yes on a live system. ;/
|
| |
|
|
| |
full name.
|
| | |
|
| | |
|
| |
|
|
| |
Mailman's copy of the email package instead of Python's.
|
| | |
|
| | |
|
| | |
|
| | |
|