summaryrefslogtreecommitdiff
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
* Lots of updates to the New Order.bwarsaw2001-03-012-64/+42
| | | | | | | | | main(): Convert to the new Switchboard mechanisms. This means we neither need to instantiate the mailing list, nor create a Message object from stdin. A side effect of this change is that we can't efficiently determine whether this message was destined for the -owner or -admin address (since this script bogusly handles both). We defer this decision to the CommandRunner.
* Update copyright yearsbwarsaw2001-02-282-2/+2
|
* Next round of big i18n patches.bwarsaw2001-02-282-44/+30
| | | | | | | main(): Change the error messages; removed old cruft (we never need to create the MailList object, we just need a valid listname -- we also don't ever need to create a Message object, stdin is fine); change the enqueuing code to use the new Switchboard mechanism.
* import Mailman.i18n._bwarsaw2001-02-161-0/+1
|
* Convert to using the new switchboard interface.bwarsaw2001-02-152-49/+18
|
* main(): Explicitly queue the message to INQUEUE_DIR (see changesbwarsaw2000-12-205-7/+7
| | | | described in qrunner for details).
* main(): Some fixes to handle situations such as sending directly tobwarsaw2000-12-201-8/+27
| | | | | | the non-extension address, and for handling listnames with dashes in them. Also, do better matching of incoming message's target domain with the list's domain.
* Add `auto' script.bwarsaw2000-12-081-1/+1
|
* intermediatebwarsaw2000-12-081-1/+4
|
* Script which can be used to make Postfix automatically recognize newbwarsaw2000-12-081-0/+92
| | | | mailing lists.
* run_main(): Gross and temporary hack to put `_' in the builtins. It'sbwarsaw2000-12-071-0/+9
| | | | | too magical so eventually explicit imports will be added to the appropriate modules.
* Modifications to use extended print syntax.bwarsaw2000-12-072-6/+6
|
* Turn STEALTH_MODE back on for the 2.1 development cycle.bwarsaw2000-12-071-17/+17
| | | | Modifications to use extended print syntax.
* In preparation for 2.0 final, turn on STEALTH_MODEbwarsaw2000-09-291-1/+1
|
* run_main(): Moved the initialization of logger local to None outsidebwarsaw2000-09-271-4/+4
| | | | | the try block. Should have no practical effect, but makes debugging easier.
* get_message(): The filter programs now live in VAR_PREFIX/filters.bwarsaw2000-09-221-1/+1
| | | | Closes David Champion's patch #101331.
* main(): Add the `tolist' flag to the message data, so we can trackbwarsaw2000-09-081-1/+1
| | | | | messages posted to the list (as opposed to message sent to the -admin, -owner, -request addresses, or internally generated).
* print_traceback(), top-level: Remove the Cache-control: and Expires:bwarsaw2000-07-221-4/+0
| | | | | headers. These caused problems with the back button and didn't really solve an existing problem.
* main(): If the message came from the -owner address, set the toownerbwarsaw2000-07-222-6/+22
| | | | | | flag. If it came from the -admin address, set toadmin. The test is against the To: field and checks for string equality with mlist.GetOwnerEmail().
* print_traceback(), top-level: Include HTTP headers "Cache-control:bwarsaw2000-07-201-0/+4
| | | | no-cache" and "Expires: 0" to inhibit caching.
* Add Emacs helper at top of file.bwarsaw2000-07-191-0/+1
|
* All three scripts have now been changed to always quickly queue theirbwarsaw2000-06-145-127/+75
| | | | | | | | | | | | messages to the qfiles directory. This once and for all avoids the possibility that we hit the MTA's command time limit. The mailing list objects are never locked so we can't time out there. They don't need to be locked for message queuing. The penalty is that we do more disk i/o for every message destined to the list, the list-owner or list-request, and messages are not delivered immediately. Both are probably worthy tradeoffs for absolutely guaranteeing that messages never get lost.
* Added a variable STEALTH_MODE which can be set to true to inhibitbwarsaw2000-06-051-38/+49
| | | | | traceback, system, and environment information to the web pages. The information is always still printed to the log files.
* main(): No need to explicitly enqueue the message, sincebwarsaw2000-05-221-5/+2
| | | | | DeliverToList() will now do this automatically if any pipeline module fails.
* main(): Takes no arguments.bwarsaw2000-05-222-2/+2
|
* Robustification of handling mail commands. If any of the followingbwarsaw2000-05-092-8/+44
| | | | | | | fails -- the list name is missing or bogus, or the list lock cannot be acquired within the LIST_LOCK_TIMEOUT time frame -- the message is enqueued for qrunner to try again later. Previously, the message was simply lost!
* Robustification of posting. If any of the following fails -- the listbwarsaw2000-05-082-20/+56
| | | | | | | | | name is missing or bogus, or the list lock cannot be acquired within the LIST_LOCK_TIMEOUT time frame -- the message is enqueued for qrunner to try again later. Previously, the message was simply lost! If DeliverToUser() returns a true value, then this means the message delivery was not completed, and again, the message is enqueued.
* Robustification of posting. If any of the following fails -- the listbwarsaw2000-05-081-38/+53
| | | | | | | | | name is missing or bogus, or the list lock cannot be acquired within the LIST_LOCK_TIMEOUT time frame -- the message is enqueued for qrunner to try again later. Previously, the message was simply lost! If DeliverToList() returns a true value, then this means the message delivery was not completed, and again, the message is enqueued.
* print_environment(): Reveal even more secrets about Mailman'sbwarsaw2000-04-061-7/+37
| | | | | | | | operating environment, namely some key sys module attributes (version, prefix, etc.). We're going to need a way to scale back this reporting for the Web pages in case folks do not want to reveal this much information. And hey, since 2.0 will have no bugs, this stuff is all moot anyway, right? :)
* run_main(): During call to the Cgi's main routine, set sys.stderr tobwarsaw2000-04-041-7/+5
| | | | | | | | the logger object so they can simply sys.stderr.write() to get error messages out to logs/error. No need to set sys.__stderr__ and sys.__stdout__; we're requiring at least Python 1.5.2 now.
* Removed the debugging messages from the main script.bwarsaw2000-03-281-3/+3
|
* Update the copyright lines to include the years 1999 & 2000.bwarsaw2000-03-217-7/+7
|
* Remove the commented out extended open() function, since Python 1.5.2bwarsaw2000-03-211-30/+5
| | | | is going to be required now.
* main(): set the `torequest' attribute to 1 on the message object.bwarsaw2000-02-262-0/+2
|
* main(): Removed debugging hack (adding the MAILMAN_OWNER to the listbwarsaw2000-02-192-2/+6
| | | | | | of recipients). More importantly, flag the message as having been delivered to the -admin address by setting the `toadmin' attribute on the message. This is used by the Replybot handler.
* Be sure to reprime the stderr logger so we get a timestamp on thebwarsaw1999-12-251-0/+1
| | | | "post ending" message (better debugging).
* Added some logging so we can try to figure out why some posts arebwarsaw1999-12-221-0/+2
| | | | taking longer than 16 minutes to complete.
* Port to the new way of handling messages. Also we don't send emailbwarsaw1999-12-162-36/+36
| | | | | when the alias is misconfigured. This will just naturally happen in the error logs.
* Must read stdin into a StringIO object so that its seekable, sincebwarsaw1999-12-141-1/+3
| | | | Message.Message requires this.
* Port to the new bounce handling architecture.bwarsaw1999-12-092-8/+38
|
* Convert message delivery to pipeline architecture by usingbwarsaw1999-11-241-74/+48
| | | | | | | | | | | | | | | | | | | HandlerAPI.DeliverToUser() for fast track delivery of the welcome messages. Stick most code in main() Use LogStdErr Remove the fromusenet cruft -- since Usenet messages are gated to the newsgroup without going through the post script now, this is all unnecessary. Move the sending of postheld.txt to the Hold.py pipeline module, where it really belongs. Plus it won't work here because those exceptions aren't percolated up to the post script. MMLoopingPost exceptions still make it through and are handled here (although I suspect this should go into one of the handlers too).
* Convert message delivery to pipeline architecture by usingbwarsaw1999-11-242-32/+40
| | | | | | | | | HandlerAPI.DeliverToUser() for fast track delivery of the welcome messages. Stick everything in a main(). Simplify error reporting by using Mailman.Logging.Utils.LogStdErr
* Use convenience StringIO modulebwarsaw1999-11-101-5/+1
|
* Several changes to use the new Message objects and interface tobwarsaw1999-11-101-6/+13
| | | | | | | | | | | MailList.Post(), specifically: Message object ctor takes a file-like object, so use StringIO when the data is coming from a string. MailList.Post() no longer takes an approved argument. Setting the `fromusenet' attribute on the message object is enough to let the system know where the message is from.
* Use the new Mailman.Message.Message objects for the incoming messagebwarsaw1999-11-103-3/+3
|
* eradicate "maillist" as a nounbwarsaw1999-05-052-2/+2
|
* current_list => mlistbwarsaw1999-05-032-16/+12
| | | | comment clarification
* Post(): New policy for message loops (e.g. messages that show up atbwarsaw1999-04-161-14/+23
| | | | | | | | | | the mailing list that have a matching X-BeenThere header). Instead of holding such messages for approval, an MMLoopingPost error is raised. This is caught by the post CGI script, which logs this occurance and sends a notice (containing the original message) to the list admin. This way, the admin knows there's a problem and can track the loop down, but isn't so inconvenienced to go the the Web page just to discard the message (the usual disposition).
* tmp_prevent_gate attribute on the MailList objects is gone!bwarsaw1999-03-061-4/+12
| | | | | | | Stick a `fromusenet' attribute on the msg object, value taken from whether there is a magical second argument to the post script (only happens from GatewayManager). Also post message with approved flag set to fromusenet, so message originating on Usenet are pre-approved.
* VERSION is no longer set in configure because it's too hard tobwarsaw1999-01-151-2/+0
| | | | | | | | | | | | propagate version string changes to the public (you have to autoreconf, then reconfigure and reinstall). Now, VERSION is set directory in Defaults.py.in and the Release.py script updates that file directly. Now we just need to run ./config.status and do a re-install. I hope this will make things easier. I'm also bumping the version to 1.0b8, so I can do a release tomorrow.