mailman.git - The GNU Mailing List manager.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Donn Cave's patch #602087 to honor configure's --srcdir switch.	bwarsaw	2002-12-12	1	-1/+1
\|
*	process(): Don't send a results message if we're already sending a	bwarsaw	2002-11-21	2	-2/+4
\| \| \| \|	confirmation message.
*	process(): Set the `respond' flag to false if	bwarsaw	2002-11-21	1	-10/+17
\| \| \| \| \| \| \|	- this is a subscription being confirmed and send_welcome_msg is true - this is an unsub being confirmed and send_goodbye_msg is true We don't need redundant responses.
*	process(): Watch for RFC 2047 encoded From headers and decode the	bwarsaw	2002-10-05	1	-0/+10
\| \| \| \| \|	realname either to a byte string if it contains just ascii characters, or to a unicode.
*	set_show(): Added some missing markup, according to SF bug #553385 by	bwarsaw	2002-08-17	1	-3/+3
\| \| \| \|	Daniel Buchman.
*	process(): Make sure the help.txt template comes from the currently	bwarsaw	2002-08-15	1	-1/+1
\| \| \| \| \| \|	active language, which will be the sender's preferred language if they are a member, or the list's preferred language otherwise. The currently active language is available in the message metadata.
*	process(): Fix for confusing "you were subscribed and your	bwarsaw	2002-07-09	1	-3/+11
\| \| \| \| \| \| \| \| \| \| \| \| \|	confirmation string was invalid" messages. The problem was if the responder left the confirmation string in the Subject: and also copied it to the body, the second processing of the confirmation would find no cookie. So now we always stop after processing the first confirmation command (yes, that means no other commands in the message will be processed, which is fine). We also trim the unprocessed commands in the results to not include identical confirmation strings -- otherwise they'll see their confirmation as unprocessed.
*	process(): Limit the lists returned to those in the same virtual	bwarsaw	2002-05-17	1	-0/+6
\| \| \| \| \|	domain as the list the request was sent to, if VIRTUAL_HOST_OVERVIEW is true.
*	Add a comment	bwarsaw	2002-05-17	1	-0/+1
\|
*	process(): Suggestion by Aaron Birenboim to include the member's	bwarsaw	2002-05-12	1	-0/+12
\| \| \| \| \|	options page url in the help message if the sender is a member of the list.
*	Oops, I guess I forgot to commit this change.	bwarsaw	2002-05-04	1	-2/+3
\| \| \| \| \|	process(): Catch NotAMemberError instead of MMNoSuchUserError. Also, slight rewrite of the result message.
*	New architecture for email commands. Instead of the monolithic (and	bwarsaw	2002-05-02	18	-0/+1298
	unmaintainable) MailCommandHandler.py file, we've now got a framework where each command is implemented in a separate file. This means it's both more extensible and more flexible: - you can easily add new commands for things I haven't thought of <wink>, and the `help' command will automatically adjust - you can disable commands entirely by removing the appropriate file - you can disable, change, or add commands on a per-list (or even per-message or per-sender) basis CommandRunner.py is the module that calls into this framework. Each command is implemented as a cmd_<command>.py file. The `set' command is the most complicated. The help text is currently implemented as module docstrings (for most commands), so the i18n catalogs must be updated. Also the help.txt files will be updated.