Mailman 3 December 1999 - Mailman-Developers

Re: [Mailman-Developers] admin approval page / cvs
by Richard Ellerbrock 13 Dec '99

13 Dec '99

>Hi, > >i'm trying out the 1.2 cvs version of MM... >I like the changes on the approval page... I do have some >suggestions for changes, which should make it a bit easier to >use (this page is an important part of our mailinglist >setup and I've used it alot)... {cut} >3) add an option to send a copy of the message to a certain > email address. I've already hacked something like this > into my local copy of MM, but it just sends the message body, > so any attachments are lost (you can of course retrieve them > with mime tools) I would really like this feature too! -- Richard Ellerbrock richarde(a)eskom.co.za

1 0

latest cvs trouble
by Ricardo Kustner 13 Dec '99

13 Dec '99

Hi, since 1.1/postfix seems to be duplicating some posts a bit too often, i tried to install the latest cvs of MM... first of all, there were some pending posts in config.db, but the new installation doesn't recognize them (i guess this changed in 1.2) so any administrative requests get lost. When I tried posting to the list, i got an error: post: File "/usr/local/mailman/scripts/post", line 83, in ? post: main() post: File "/usr/local/mailman/scripts/post", line 56, in main post: msg = Message.Message(sys.stdin) post: File "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ post: self.rewindbody() post: File "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in rewindbody post: self.fp.seek(self.startofbody) post: IOError : [Errno 29] Illegal seek Ricardo. --

2 4

cvs errors
by Ricardo Kustner 13 Dec '99

13 Dec '99

I noticed the following errors in the CVS version of MM: Dec 13 03:48:05 1999 mailcmd: Traceback (innermost last): mailcmd: File "/usr/local/mailman/scripts/mailcmd", line 52, in ? mailcmd: list.ParseMailCommands() mailcmd: File "/usr/local/mailman/Mailman/MailCommandHandler.py", line 112, in mailcmd: msg = Message.Message(sys.stdin) mailcmd: File "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ mailcmd: self.rewindbody() mailcmd: File "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in r mailcmd: self.fp.seek(self.startofbody) mailcmd: IOError : [Errno 29] Illegal seek I'm not sure what could be causing this, but i got one complaint from somebody who received an error message from postfix when trying to confirm subscribing to the list. Also I've noticed the number of posts to the lists have decreased dramatically, though this saves me a lot of approval work, i hope this doesn't mean some posts are getting lost... Ricardo. --

1 0

Developers Needed for addition of specific feature(s)
by Bill Bumgarner 12 Dec '99

12 Dec '99

I'm looking for some Python/MailMan savvy developers to add some features to MailMan. In particular, we [CodeFab] have a need-- both internally and on a client project-- to augment MailMan such that it can gracefully handle attachments. In particular: - decode MIME (and other formats?) encoded messages upon receipt - file attachments into archive via either the current archive scheme or via WebDAV (WebDAV preferred) - rewrite message such that it contains URLs to the attachements instead of the attachments themselves The overriding goal of this is to solve the above problems in an extremely timely manner and provide all resulting modifications/extensions to MailMan back to the MailMan development community in such a fashion that it can be integrated into future releases. However, we are under a severe time crunch and, as such, it is likely that what we need done and what needs to be done to integrate this into the next release will not be in complete parity-- which is another reason why I would really like to bring a focused MailMan/Python developer into this project to ensure that the short term work will feed directly into a long term, viable integration of this solution into MailMan. The code is not just for CodeFab's benefit-- we have a client that also needs this solution. This client is also interested in helping fund this development effort. The funds are limited and the client [and CodeFab] would both like to be able to further leverage this by generating some positive "we support open source projects & MailMan/Python is really cool" PR-- so we would like to work with a developer or developers that are amicable to having their name thrown into a press release and wouldn't mind signing the standard NDA/contracting style agreements. Let me reiterate-- regardless of contractual agreements necessary to move this forward-- all code developed under this arrangement will be under the GPL. Regardless of whether or not we can find someone to formally assist us, this work has to get done anyway. I would rather see it done with formal assistance from the MailMan development community... If we can't find someone to help from the community, then consider this message a request for comments as to how to best implement the above features and I guess I'll have to go read the "hacking MailMan" HOWTO. :-) thanks, b.bum

1 0

Mailman 1.2 CVS
by Phillip Porch 12 Dec '99

12 Dec '99

I Noticed the following error message in my error log for mailman and wondered if you could give me a pointer to tracking down the problem. beer: lost digest file: /home mailman/list/beer/next-digest (No such file or directory) I also started seeing this message a couple of days ago from the cron daemon. Traceback (innermost last): File "/home/mailman/cron/checkdbs", line 83, in ? main() File "/home/mailman/cron/checkdbs", line 50, in main mlist.SendTextToUser( AttributeError: SendTextToUser ************************************************* Cron: The previous message is the standard output and standard error of one of your cron commands.

2 1

Mailman 1.2 CVS
by Phillip Porch 12 Dec '99

12 Dec '99

I have noticed another quirk. In the archives, with the original version, I had the archive gzipped on the fly. The links would indicate that the text could be obtained gzipped. With the current version, I have elected to not gzip on the fly but to run the cron script to gzip the archives. The gzipping is working fine, but the link on the archive page doesn;t indicate the file is available gzipped. What is needed to update that link? -- Phillip P. Porch <root(a)sco.theporch.com> NIC:PP1573 finger for http://www.theporch.com UTM - 16 514548E 3994397N PGP key

1 0

Re: [Mailman-Developers] admin approval page / cvs
by J C Lawrence 12 Dec '99

12 Dec '99

On Sat, 11 Dec 1999 18:24:49 +0100 Ricardo Kustner <ricardo(a)miss-janet.com> wrote: > Hi, On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >> Agreed. I would like to be able to edit moderated messages, >> given that MailMan would then insert a custom header stating that >> the message had been edited by the moderator. > yes i saw that the textarea data isn't used when approving the > post... the complete message is read from disk when it has been > approved. This is not surprising given that a single message may be several Meg in size (and yes, some of my list posts are that big). >> > message body... maybe the headers should be left out entirely > >> since the subject/from is being mentioned above anyway ? No way. >> The headers are essential to me. > i can understand that the headers may be very usefull sometimes... > what if we meet half way? i just thought of the following > solution: put the message body in a textarea... and put a select > box on top if it that includes the headers... This works badly when you have a large number of messages to approve. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

Re: [Mailman-Developers] admin approval page / cvs
by J C Lawrence 11 Dec '99

11 Dec '99

On Sat, 11 Dec 1999 13:44:04 +0100 Ricardo Kustner <ricardo(a)miss-janet.com> wrote: > 1) message headers: putting the message in a TEXTAREA is a neat > solution :) Agreed. I would like to be able to edit moderated messages, given that MailMan would then insert a custom header stating that the message had been edited by the moderator. > however, when all the message headers are being shown, > you have to scroll the box alot before you see anything about the > message body... maybe the headers should be left out entirely > since the subject/from is being mentioned above anyway ? No way. The headers are essential to me. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

4 3

Re: [Mailman-Developers] admin approval page / cvs
by J C Lawrence 11 Dec '99

11 Dec '99

On Sat, 11 Dec 1999 08:36:14 -0700 Sean Reifschneider <jafo(a)tummy.com> wrote: > On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >> No way. The headers are essential to me. > What about having separate text fields for the headers and the > body? Please, no. I need/want the message exactly as it was sent with no extra munging, implicit edits, ochanges in presentation etc. This is actually one of the main things I like about MM -- it doesn't attempt to package the pending-moderation messages in any way, but presents them to me exactly as they are. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

admin approval page / cvs
by Ricardo Kustner 11 Dec '99

11 Dec '99

Hi, i'm trying out the 1.2 cvs version of MM... I like the changes on the approval page... I do have some suggestions for changes, which should make it a bit easier to use (this page is an important part of our mailinglist setup and I've used it alot)... 1) message headers: putting the message in a TEXTAREA is a neat solution :) however, when all the message headers are being shown, you have to scroll the box alot before you see anything about the message body... maybe the headers should be left out entirely since the subject/from is being mentioned above anyway ? 2) approve/reject/discard ... please move this below the message content... since the normal way is that you read the message first, and then decide what to do with it... 3) add an option to send a copy of the message to a certain email address. I've already hacked something like this into my local copy of MM, but it just sends the message body, so any attachments are lost (you can of course retrieve them with mime tools) i've already changed these things myself... but i don't have a copy of cvs on the production machine so it's not easy to make a patch for it right now... (and to be honest my changes are more 'hacks' than clean code ;) ) Ricardo.

1 0