| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
simple_04.txt
|
| | |
|
| | |
|
| |
|
|
| |
far.
|
| | |
|
| |
|
|
|
| |
send the password reminder as if it's coming from the "first" public
mailing list. Instead it comes from the "site list".
|
| |
|
|
| |
SimpleWarning can pass this in.
|
| |
|
|
| |
"KeftaMail" and another calling itself "BSN Postfix".
|
| |
|
|
| |
just need to not recognize lines that start with whitespace.
|
| | |
|
| |
|
|
| |
some common warnings).
|
| | |
|
| | |
|
| |
|
|
| |
of limited value, IMO. Haven't we already taken over the world? :)
|
| |
|
|
| |
markings.
|
| | |
|
| |
|
|
|
| |
mode 644 while the latter is installed with mode 775. This lets you
run cron scripts from the command line.
|
| |
|
|
| |
former config variable is going away.
|
| |
|
|
| |
The former config variable is going away.
|
| |
|
|
| |
The former config variable is going away.
|
| |
|
|
| |
The former config variable is going away.
|
| |
|
|
| |
Utils.get_site_email(). The former config variable is going away.
|
| |
|
|
| |
Utils.get_site_email(). The former config variable is going away.
|
| |
|
|
| |
Utils.get_site_email(). The former config variable is going away.
|
| | |
|
| |
|
|
|
| |
MAILMAN_OWNER, use Utils.get_site_email(). The former config
variable is going away.
|
| |
|
|
|
|
| |
MAILMAN_SITE_LIST: Names the "master site list" which must exist, and
from which all site-related email appears to come from
(e.g. password reminders).
|
| |
|
|
| |
Utils.get_site_email(). The former config variable is going away.
|
| |
|
|
| |
docstring.files to update every time.
|
| |
|
|
|
|
|
|
| |
personalization. Specifically, copies of the message are sent back to
the incoming queue, but their pipelines are hardcoded to only Decorate
and ToOutgoing. The original copy goes through the normal delivery
mechanism (but with its metadata['recips'] deleted so it won't
actually get delivered to anyone).
|
| | |
|
| |
|
|
|
|
|
|
|
| |
has a true 'personalized' key), then calculate an additional
dictionary of interpolation variables for the header and footer.
This contains keys specific to the user who is the recipient of
this copy of the message.
decorate(): Take an optional `extradict' of interpolation mappings.
|
| | |
|
| |
|
|
|
|
| |
boxes higher (10 lines instead of 4). Second, if
OWNERS_CAN_ENABLE_PERSONALIZATION, add the config info for the
`personalize' attribute.
|
| |
|
|
|
| |
value is `true'. This allows us to delete the name and have it
removed from the member database.
|
| | |
|
| | |
|
| |
|
|
| |
the argument.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
admins can "personalize" their mailing lists. Personalization is a
new feature where each recipient gets their own copy of the message,
and the headers and footers can include additional information
specific to the user. Since this can impose a greater system burden,
it must be enabled by the site administrator in order for the list
admins to see or set the option.
Note that this currently only works for regular delivery.
GLOBAL_PIPELINE: Add the "Personalize" handler module, which actually
sets the messages up for personalization.
|
| |
|
|
|
|
|
|
| |
GetConfigInfo(): Elaborate the details for admin_immed_notify to make
it clear that the list moderators and the list administrators get
the notification.
Also, spell out "kilobytes".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
show_results(): Elaborate on the "Make your changes text...".
Reorganize the category specific elements so that the "find
member" section is added here instead of in membership_options().
This lets us put an hr in between these sections.
Also, hyperlink "Python regular expression" to point to the
library reference manual's description of regexp syntax.
show_variables(): No longer needs the `form' argument, since it
doesn't call membership_options() any more (that's called directly
from show_results() instead).
membership_options(): Just pass in the subcategory instead of
calculating it here. It's figured out by show_results(). Also,
don't add the "find member" section here; it's also added by
show_results().
Reorganize the big member table to change the sense of the
subscription check box. I've always hated the fact that you turn
/off/ the subscr checkbox to unsubscribe somebody! Instead, now
you turn on the unsub checkbox to unsubscribe them. To make this
standout even more visually, the unsub column is moved to the left
of the name/addr column. I still hate the abbreviations, but
don't have any better ideas. This does improve things though
because the members to be effected (i.e. unsubscribed) stand out
much better now.
mass_subscribe(), mass_remove(): More reorganization to put the
questions in their own table cells. This helps line things up
better, although it isn't perfect. Also, shrink the width of the
text area a bit.
|