summaryrefslogtreecommitdiff
path: root/scripts/answer_majordomo_mail (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Get rid of answer_majordomo_mail. It's seriously broken in MM2.1, andbwarsaw2001-08-041-39/+0
| | | | of limited value, IMO. Haven't we already taken over the world? :)
* Update the copyright lines to include the years 1999 & 2000.bwarsaw2000-03-211-1/+1
|
* Use the new Mailman.Message.Message objects for the incoming messagebwarsaw1999-11-101-1/+1
|
* Packagizedbwarsaw1998-06-191-7/+8
|
* 1. Use the standard Python invocation #! line to get the interpreterbwarsaw1998-05-261-5/+7
| | | | | | | | | | | | | | 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, calculate path to majordomo.answer.txt file using paths.prefix as the path base.
* Fixed a typo in the zipcode.viega1998-05-261-1/+1
|
* Added copyright notices to all source files where I am legally entitled to ↵viega1998-05-251-0/+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?)
* Incorporated janne sinkkonen's fix, with a bit of a spin of my own.klm1998-04-231-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From janne@avocado.pc.helsinki.fi Thu Apr 23 19:17:15 1998 Date: 16 Apr 1998 02:38:37 +0300 From: Janne Sinkkonen <janne@avocado.pc.helsinki.fi> To: mailman-developers@python.org Cc: ilpo@pcuf.fi Subject: [Mailman-developers] Double Reply-To:, answer_majordomo_mail, archives I have several minor things: First, when the "reply to the list" option of a list is set, it seems that a potential existing Reply-To: is not (always) stripped off. Instead there will be two Reply-To: headers, one for the list, one from the original sender. I guess this is a bug? Second, here's a working answer_majordomo_mail script. The script in 1.0b12 didn't work for me (the patch would be larger than the script itself, hence I include this here): #!/usr/local/bin/python # This is another script that's really just for my use, but # feel free to use it if you know how... import sys f = open('/dev/null', 'w') sys.stderr = f sys.path.append('/home/mailman/mailman/modules') import mm_message, mm_utils msg = mm_message.IncomingMessage() text = open('/home/mailman/mailman/misc/majordomo.answer.txt', 'r').read() mm_utils.SendTextToUser('Your mail to Majordomo...', text, msg.GetSender(), 'mailman-owner') I would also like to ask about the archives. The README says 'integrated with [...] external pipermail'. :) Besides the links and authorization service provided, what does this mean in practice? Should I run piper-hypermail from a crontab or is there something better around somewhere? -- Janne ------------------------------------------------------ Mailman-developers maillist - Mailman-developers@python.org http://www.python.org/mailman/listinfo/mailman-developers
* Initial revisionmailman1998-02-271-0/+25