summaryrefslogtreecommitdiff
path: root/scripts/post
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* 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.
* Use Util.maketext() and move post held message intobwarsaw1998-08-291-16/+8
| | | | templates/postheld.txt
* SendTextToUser() no longer takes a raw argumentbwarsaw1998-08-291-2/+1
|
* Changing policy about when notifications are sent for posts held forklm1998-08-131-6/+2
| | | | | | | | | | | | | | | | | approval - notifications are now sent even for suspected spam. I was experimenting with avoiding alerting spammers to spam filtering, but i've come to realize that: - Not notifying prevents non-spammers from getting any feedback when they inadvertantly trip a spam sensitivity, and - It's probably best to blast stuff back at spammers. In the common case that the return addresses are useless, no harm, and if the return addrs are good, then the more people using the spam protection, the more spam the spammer gets in response. The moral is, forthrightness is the best policy. Even if it does expose our measures and up the ante in the spam war, security via obscurity is a poor, and often misguided, approach.
* Using new, tidy mechanism for getting putting a StampedLogger onklm1998-08-031-7/+2
| | | | stderr. (I expect we should do this for all the scripts.)
* Don't need to check whether the list is locked before doing the unlockklm1998-07-171-2/+1
| | | | - new version of Unlock takes care of that.
* Check for existing lock before unlocking.klm1998-07-151-2/+2
| | | | | | | | | | | | | | | | | QUESTION: The MailList.Unlock() method currently raises two different AttributeErrors when the list is not currently locked (depending on whether or not the lock was previously created). This certainly seems like the wrong exception. We could make .Unlock() check for the lock and return a better exception, or we could have it just return if the list is not locked. I'm inclined towards the latter, but it changes the character of the list locking interface a wee bit. I think it ought to be changed, one way or the other. John, what's your inclination? Ken
* StampedLogger now comes out of the Mailman.Logging.StampedLoggerbwarsaw1998-07-061-3/+3
| | | | | module (we should really create a mail driver similar to the CGI driver).
* Packagizedbwarsaw1998-06-191-9/+13
|
* Add Unlock() calls where appropriate, and add lock = 0 to MailListviega1998-06-131-3/+1
| | | | constructor actuals when the list doesn't need to be locked.
* Modified post to take a second optional argument. If the second argumentviega1998-05-311-2/+7
| | | | | | | | is present, post realizes that it was called by the News->Mail gateway, and tells the mailing list not to Mail->News gateway anything. Actually, thinking about it, it is probably better to set a field in each message object saying "Don't send me to news!". I'll probably adjust that after I get to test the code.
* 1. Use the standard Python invocation #! line to get the interpreterbwarsaw1998-05-261-9/+8
| | | | | | | | | | | | | | | | | | | | | | | | from $PATH 2. Do no direct sys.path munging in this file. Import the `paths' module, which is created during the configure process, and which performs all necessary path munging (and exports some useful variables too). 3. Remove RCS crud Also: Removed all hardcoded absolute paths. Instead, calculate paths using paths.prefix as the base. Change ''' TQS to """ so as not to confuse font-lock. !!!! When calling SendTextToUser(), set the new optional argument raw=1 so that the text body will not be wrapped/filled. The checkin that implements wrapping and filling has not yet been made. Note that it would be nice if just the templated text could be wrapped/filled and the err_msg left alone, but that's currently too hard to separate.
* Fixed a typo in the zipcode.viega1998-05-261-2/+2
|
* Added copyright notices to all source files where I am legally entitled to ↵viega1998-05-251-1/+16
| | | | | | | do so. Added a copy of the GNU GPL. Added information about mailman-users in README, and reworded some text in there (made the credits less verbose... perhaps they should move to a credits file?)
* Set stderr to the logger, to get errors logged if they occur.mailman1998-04-101-3/+8
|
* Preparing to package a distribution - add __version__ info.mailman1998-04-091-0/+3
|
* In addition to moderated messages, recognize error messages associatedmailman1998-04-081-2/+6
| | | | with spam and do not notify the sender that their message is being held.
* Add modest module docstring (while i happened to be there).mailman1998-04-031-4/+8
|
* Do not send out "holding for approval" messages when the reason formailman1998-03-181-2/+5
| | | | the hold is list moderation.
* Removed spurious and dangerous /tmp debugging output file - unwritableklm1998-03-081-3/+2
| | | | existence of the would silently prevent the post.
* Initial revisionmailman1998-02-271-0/+69
generated by cgit v1.3.1 (git 2.54.0) at 2026-08-16 18:12:17 +0000