summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Updated catalogs, including new big5 updates from Yuan-Chen Cheng.bwarsaw2002-06-2725-7587/+14610
|
* Some fixes.wilane2002-06-132-2/+2
|
* Thanks to the goal :) my boss let me some time to update FR translations.wilane2002-06-035-563/+345
| | | | | Great job done by Simone Piunno <pioppo@ferrara.linux.it> with the transchecker... It caught them all.
* New no-more-today template translated.avalon2002-05-291-0/+7
|
* Update to reflect the changes in the english template.avalon2002-05-291-4/+4
|
* InviteNewMember(): Prepend any text given in the mass subscribe pagebwarsaw2002-05-281-5/+13
| | | | | | | | | | | | | | | | to the invitation notification. Also, set an `invitation' attribute on the UserDesc record stored in the pending database. This is a hack so that ProcessConfirmation() can figure out if the subscription request was an invitation or not (easier than adding an INVITATION type to the Pending module). ApprovedAddMember(): Option text argument for passing in prepended text for subscription notifications. ProcessConfirmation(): If the SUBSCRIPTION action was an invitation (based on the magic existance of the `invitation' attribute on the UserDesc record), don't do additional approvals. If the user was invited, we /know/ the admin had to approve of that!
* SendSubscribeAck(): Prepend any text given in the mass subscribe pagebwarsaw2002-05-281-2/+2
| | | | to the subscription notification.
* mass_subscribe(), change_options(): Add a text box on the massbwarsaw2002-05-281-2/+12
| | | | | subscribe page so that the admin can add a custom message to be prepended to the welcome/invite notification.
* FormatSubscriptionMsg(): Fix missing space. Closes bug #555065 bybwarsaw2002-05-281-2/+4
| | | | Simone Piunno.
* Better description of how to set up the init.d mailman script forbwarsaw2002-05-281-2/+5
| | | | | systems that don't support chkconfig. Given by Dario Lopez-K�sten in SF bug # 556260.
* Instead of hardcoding the reason for becoming disabled in thisbwarsaw2002-05-281-2/+2
| | | | | | | message, we pass it in from the caller so that it can be used for other disable reasons. TRANSLATORS TAKE NOTE.
* intermediatebwarsaw2002-05-281-0/+8
|
* Add options to also send disabled notifications for users who havebwarsaw2002-05-281-43/+96
| | | | | | | | been disabled by themselves, the list owner, or for unknown (legacy) reasons. By default we only notify `bounce disabled' members, but you could now do notifications for any other reason. Also, fix the -l/--listname option parsing.
* main(): While we're at it, cruise through thebwarsaw2002-05-281-18/+30
| | | | | hold_and_cmd_autoresponses dictionary to see if any entries can be evicted (we only hold such data for a single day).
* make_response() -> send_response()bwarsaw2002-05-281-5/+15
| | | | | | send_response(): Check whether the sender has reached their autoresponse limit before sending the results of the command. This may not be the right time to do that check.
* ackp(): New helper function.bwarsaw2002-05-281-1/+11
| | | | | | process(): Before sending the sender a notification message, check the X-Ack: and Precedence: headers, and also see if this sender has reached their auto-response limit.
* Bump the DATA_FILE_VERSION and add hold_and_cmd_autoresponses if it'sbwarsaw2002-05-282-1/+2
| | | | missing.
* midnight(): New utility function to calculate the epoch seconds of abwarsaw2002-05-281-0/+9
| | | | date in (year, month, day) format.
* InitVars(): Add a new attribute hold_and_cmd_autoresponses which is abwarsaw2002-05-281-0/+46
| | | | | | | | | | | | | | dictionary mapping sender addresses (they don't have to be members) to a 2-tuple of information (date, count). date is a 3-tuple of (year, month, day) and count is the number of auto-responses sent to the sender today. autorespondToSender(): This method is called whenever we're about to send a response to a -request message, or a hold notification. It returns 1 if the caller should send a normal autoresponse, and 0 otherwise. When we've just exceeded the maximum number of autoresponses, we send a message indicating that no more responses will be sent today (instead of the normal autoresponse).
* New site-wide variable MAX_AUTORESPONSES_PER_DAY which sets the limitbwarsaw2002-05-281-0/+8
| | | | | | on the number of -request and posting-hold responses any one list will send to any one recipient in a single day. This is to stop mail loops with email robots. Default this to 10.
* Some hacks to support notification of disabled delivery for reasonsbwarsaw2002-05-281-6/+31
| | | | | | | | | | | | | | | | | | | other than due to excessive bounces. Specifically, REASONS: sentence fragments for disable reasons (hopefully these can be translated). registerBounce(): The calculation of now and lastbounce was broken because the dst flag should have been set to -1 to let the library pick the right daylight savings time flag value. Use a new helper routine Utils.midnight() to calculate this. sendNextNotification(): Generalize a bit to handle notifications for other reasons. The ApprovedDeleteMember() message is now 'disabled address', and the syslog() message is generalized a bit too. Also, stick the reason sentence fragment into the modified disabled.txt template. TRANSLATORS TAKE NOTE!
* Some new additions.bwarsaw2002-05-282-0/+13
|
* main(): Fixing a bug reported by Danny Terweij. We need to continuebwarsaw2002-05-251-0/+1
| | | | when finding a bogus list name.
* do_list_categories(): Teach this about the attribute transformationsbwarsaw2002-05-251-7/+60
| | | | | | | | | | | | | | | | | on the way out of the mailing list via getValue(). Always defer to getValue() before getattr() is used. This lets us simplify the logic a bit, but we still take care to print useful representations of the data. Use splitlines() instead of assuming lines are \n separated. getPropertyMap(): New function to return the reverse mapping of attribute names to the gui components that define them. FakeDoc: Dummy class definition which defines an API used by the gui components when an error occurs. do_input(): Teach this about the attribute transformations on the way into a mailing list via _setValue(). Yes, this is a non-public method, but there seems to be no other way. :(
* _getValidValue(): Widget types EmailList and EmailListEx may alreadybwarsaw2002-05-251-0/+6
| | | | | | | be lists when this method is called from config_list. If so, just return the value unmodified. Also, add the Topics widget type so config_list doesn't bomb out.
* get_item_gui_value(): Removed an unused local variable.bwarsaw2002-05-251-1/+0
|
* VIRTUAL_HOST_OVERVIEW: Fixed misleading comment. The admin overviewsbwarsaw2002-05-241-3/+3
| | | | are subject to this variable as well.
* main(): Add the `toowner' key to the message metadata so the Replybotbwarsaw2002-05-221-1/+2
| | | | handler will autorespond to -owner emails. Closes SF bug #558909.
* _get_pipeline(): We don't need to send virgin messages through thebwarsaw2002-05-221-1/+1
| | | | Replybot.
* _dispose(): Send the message through the Replybot handler so -requestbwarsaw2002-05-221-3/+6
| | | | emails will be autoresponded. Closes bug #558909.
* process(): toadmin and the -admin address are deprecated.bwarsaw2002-05-221-4/+5
|
* GetConfigInfo(): The -admin address is deprecated.bwarsaw2002-05-221-6/+5
|
* Updated norwegian catalog.avalon2002-05-222-53/+35
|
* resynched with new 2.1b2+ mailman.potpioppo2002-05-222-482/+118
| | | | | | - all bin/pygettext.py's messages are gone - 1 new message (Mailman/Commands/cmd_help.py) - 1 message modified (Mailman/Gui/Privacy.py)
* QuoteHyperChars() -> websafe()bwarsaw2002-05-2214-37/+34
| | | | | Also, use Utils.websafe() consistently throughout, instead of the inconsistent calls to cgi.escape().
* process(): Use Precedence: list instead of bulk for mail list explodedbwarsaw2002-05-221-17/+8
| | | | | | | | messages. prefix_subject(): Since email.Header.Header.encode() already knows how to split long header lines, use this instead of our own attempts. This makes long subject lines much cleaner.
* UserNotification.send(): If the message doesn't already have abwarsaw2002-05-221-0/+5
| | | | | Precedence: header, add Precedence: bulk since these are typically internally crafted messages destined for a single address.
* Add a -l / --listname option (which can appear multiple times) tobwarsaw2002-05-221-2/+18
| | | | limit password sending to a specific list.
* Use version 2.0.4 of the email package.bwarsaw2002-05-223-1/+1
|
* Don't extract the marked strings or docstrings from bin/pygettext.bwarsaw2002-05-2224-3983/+2759
|
* get_senders(): Two fixes: first, make sure the unixfrom addition is abwarsaw2002-05-221-4/+4
| | | | | | 2-tuple with an empty realname item; second, we should extract all matching headers with Message.get_all() to make sure we don't miss anything (even though RFC 2822 says those should only appear once).
* _dispose(): Inhibit replybot when Precedence: is any of bulk, junk, orbwarsaw2002-05-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | list. Chuq gives us the relevant info from the sendmail docs: When the name is found in a "Precedence:" field, the message class is set to num. Higher numbers mean higher precedence. Numbers less than zero have the special property that if an error occurs during pro- cessing the body of the message will not be returned; this is expected to be used for "bulk" mail such as through mailing lists. The default precedence is zero. For example, our list of precedences is: Pfirst-class=0 Pspecial-delivery=100 Plist=-30 Pbulk=-60 Pjunk=-100 People writing mailing list exploders are encouraged to use "Precedence: list". Older versions of sendmail (which discarded all error returns for negative prece- dences) didn't recognize this name, giving it a default precedence of zero. This allows list main- tainers to see error returns on both old and new ver- sions of sendmail.
* process(): Inhibit replybot when Precedence: is any of bulk, junk, orbwarsaw2002-05-221-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | list. Chuq gives us the relevant info from the sendmail docs: When the name is found in a "Precedence:" field, the message class is set to num. Higher numbers mean higher precedence. Numbers less than zero have the special property that if an error occurs during pro- cessing the body of the message will not be returned; this is expected to be used for "bulk" mail such as through mailing lists. The default precedence is zero. For example, our list of precedences is: Pfirst-class=0 Pspecial-delivery=100 Plist=-30 Pbulk=-60 Pjunk=-100 People writing mailing list exploders are encouraged to use "Precedence: list". Older versions of sendmail (which discarded all error returns for negative prece- dences) didn't recognize this name, giving it a default precedence of zero. This allows list main- tainers to see error returns on both old and new ver- sions of sendmail.
* this is betterbwarsaw2002-05-202-7/+7
|
* Point them at 2.0.11bwarsaw2002-05-202-3/+3
|
* Updatesbwarsaw2002-05-205-131/+153
|
* GetRequestURI(): Always cgi.escape() the url retrieved from thebwarsaw2002-05-201-5/+10
| | | | | environment. This closes a cross-site scripting hole in the admin login pages.
* process(), _dispose(): Where we were testing Precedence: againstbwarsaw2002-05-192-4/+5
| | | | "bulk", we now include "junk" and "list" as well.
* now aligned to 2.1beta2pioppo2002-05-197-834/+530
|
* SMART_ADDRESS_MATCH: No longer used anywhere.bwarsaw2002-05-171-11/+4
| | | | Also, added support for Estonian.
generated by cgit v1.3.1 (git 2.54.0) at 2026-08-02 17:16:45 +0000