Re: [Mailman-Users] A few questions about mailman 2.1.14 install onDreamhost
Thanks again for these answers. Now I'm wondering . . . how does one export a mailman user list to mass-add to another list? I've looked everywhere, don't see a way. This is in Mailman 2.1.11 if that matters. Thanks, Howard, Chicago Mark Sapiro wrote: hk wrote: I'm considering the move of a longstanding discussion list with 600+ members from L-Soft Listserv (hosted at a university) to Mailman on Dreamhost (v2.1.14.) There are a few management features I've really grown to like from hosting other lists -- I was hoping if someone can tell me if there's any way to enable them in Mailman (assuming one can't hack Dreamhost's install . . .?) 1) Mark S helped me get a modification set up to a current mailman list I manage that enabled real-time notifications of moderation requests (Thanks again!). Any way to do this here? I don't recall what the issue was in that case, but normally, setting General Options - admin_immed_notify to Yes will cause immediate notification to the admins/moderators of all held messages except those held for 'emergency' moderation. Note that 'emergency' is intended to be used only for emergencies such as a flame war. There are other ways to moderate a list in general. 2) I suspect there's a fair amount of joining and leaving this list each day in its current incarnation, but don't have a way to receive notifications; of course Mailman does have the option of having owners notified when members join and leave, but I'm afraid this could generate too much mail for some moderators. Is there a way to set this preference individually like in Yahoogroups so that a mod who didn't want these messages could not get them, while the other mods still would? No. Or I should say, only by leaving the moderator's address out of the 'owner' and 'moderator' lists which would cause that moderator to receive no notifications at all, which is probably not what you want. 3) I may just be tired but is there a was to set the archives to be available only when logged in? And/or to munge e-mail addresses like on Yahoogroups? Yes, setting Archiving Options - archive_private to private will require authentication to access the archives. Email address obfuscation in the archives is very minimal, i.e. only replacing '@' with ' at '. If you want a public archive with better obfuscation, you can use a third party archiver such as mail-archive.com. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] A few questions about mailman 2.1.14 install onDreamhost
On 1/4/2012 6:05 PM, hk wrote: Now I'm wondering . . . how does one export a mailman user list to mass-add to another list? See the FAQ at http://wiki.list.org/x/aYA9. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] A few questions about mailman 2.1.14 install onDreamhost
hk wrote: I'm considering the move of a longstanding discussion list with 600+ members from L-Soft Listserv (hosted at a university) to Mailman on Dreamhost (v2.1.14.) There are a few management features I've really grown to like from hosting other lists -- I was hoping if someone can tell me if there's any way to enable them in Mailman (assuming one can't hack Dreamhost's install . . .?) 1) Mark S helped me get a modification set up to a current mailman list I manage that enabled real-time notifications of moderation requests (Thanks again!). Any way to do this here? I don't recall what the issue was in that case, but normally, setting General Options - admin_immed_notify to Yes will cause immediate notification to the admins/moderators of all held messages except those held for 'emergency' moderation. Note that 'emergency' is intended to be used only for emergencies such as a flame war. There are other ways to moderate a list in general. 2) I suspect there's a fair amount of joining and leaving this list each day in its current incarnation, but don't have a way to receive notifications; of course Mailman does have the option of having owners notified when members join and leave, but I'm afraid this could generate too much mail for some moderators. Is there a way to set this preference individually like in Yahoogroups so that a mod who didn't want these messages could not get them, while the other mods still would? No. Or I should say, only by leaving the moderator's address out of the 'owner' and 'moderator' lists which would cause that moderator to receive no notifications at all, which is probably not what you want. 3) I may just be tired but is there a was to set the archives to be available only when logged in? And/or to munge e-mail addresses like on Yahoogroups? Yes, setting Archiving Options - archive_private to private will require authentication to access the archives. Email address obfuscation in the archives is very minimal, i.e. only replacing '@' with ' at '. If you want a public archive with better obfuscation, you can use a third party archiver such as mail-archive.com. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] A few questions about mailman 2.1.14 install on Dreamhost
I'm considering the move of a longstanding discussion list with 600+ members from L-Soft Listserv (hosted at a university) to Mailman on Dreamhost (v2.1.14.) There are a few management features I've really grown to like from hosting other lists -- I was hoping if someone can tell me if there's any way to enable them in Mailman (assuming one can't hack Dreamhost's install . . .?) 1) Mark S helped me get a modification set up to a current mailman list I manage that enabled real-time notifications of moderation requests (Thanks again!). Any way to do this here? 2) I suspect there's a fair amount of joining and leaving this list each day in its current incarnation, but don't have a way to receive notifications; of course Mailman does have the option of having owners notified when members join and leave, but I'm afraid this could generate too much mail for some moderators. Is there a way to set this preference individually like in Yahoogroups so that a mod who didn't want these messages could not get them, while the other mods still would? 3) I may just be tired but is there a was to set the archives to be available only when logged in? And/or to munge e-mail addresses like on Yahoogroups? Ugh . . . I think there was a number 4 but maybe it will come back to me. Clarifying questions welcome if anything's not clear. Thanks! hk Chicago -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] a few questions about the NNTP gateway
(Disclaimer: I'm not a Debian maintainer or user) Brad Knowles wrote: On 8/25/07, Manlio Perillo wrote: Do the debian maintainer of Mailman frequent this mailing list? Not so far as I know. Improved contact between our project and the other projects which take our code and create binary packages is one thing that we would like to work on, but of course the two biggest problems are: 1. Finding out which projects are actually doing what with our code AFAICS, The Debian patches to Mailman are here: http://svn.debian.org/wsvn/pkg-mailman/trunk/debian/patches/ If you know who the maintainer of the Debian packages is, and you can light a fire under them to get them to come participate on this list, we'd appreciate that. For anyone interested, the maintainer contact addresses and quite a bit of other info is available on the package info pages: http://packages.debian.org/stable/mail/mailman http://packages.qa.debian.org/m/mailman.html -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Nothing is so simple that it cannot be misunderstood. -- Teague's Paradox pgpusOJXQc5xL.pgp Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Brad Knowles ha scritto: On 8/25/07, Manlio Perillo wrote: Do the debian maintainer of Mailman frequent this mailing list? Not so far as I know. Improved contact between our project and the other projects which take our code and create binary packages is one thing that we would like to work on, but of course the two biggest problems are: [...] That's strange. One of the Debian policicy is the strict contact between the package maintainer and the upstream software authors. The Debian maintainer(s) of Mailman can be easily found at: http://packages.qa.debian.org/m/mailman.html Regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
On 8/26/07, Manlio Perillo wrote: That's strange. One of the Debian policicy is the strict contact between the package maintainer and the upstream software authors. See my previous message on this thread. The Debian maintainer(s) of Mailman can be easily found at: http://packages.qa.debian.org/m/mailman.html And they should already know how to contact us, and where all of our respective resources are. If they're going to be making modifications to our code, the only scalable option is for them to use our mechanisms to send their changes to us, and then it's up to us as to whether or not those are accepted and incorporated into the mainstream codebase. There simply are no other scalable options. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
On 8/26/07, Todd Zullinger wrote: AFAICS, The Debian patches to Mailman are here: http://svn.debian.org/wsvn/pkg-mailman/trunk/debian/patches/ And our development page on SourceForge is at http://sourceforge.net/projects/mailman, although internally all the new work is being maintained through Bazar on Launchpad (see http://wiki.list.org/display/DEV/2007/06/22/Bye+bye+Subversion%2C+Hello+Bazaar). The Debian developers are welcome to send their patches to us through one of these two mechanisms. For anyone interested, the maintainer contact addresses and quite a bit of other info is available on the package info pages: http://packages.debian.org/stable/mail/mailman http://packages.qa.debian.org/m/mailman.html And all of our contact information is at http://www.list.org/, and the related pages. There's no way we can possibly track down every single developer on every single platform that is creating localized patches for Mailman on their platform. The only way this process can possibly work is if they use our mechanisms to send their patches to us. There are no other scalable options. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Brad Knowles wrote: There's no way we can possibly track down every single developer on every single platform that is creating localized patches for Mailman on their platform. The only way this process can possibly work is if they use our mechanisms to send their patches to us. FWIW, I was not suggesting that the Mailman developer's track down the Debian maintainers (or any other packagers). I only provided the links to the Debian info in case someone on this list wanted to contact them and ask about the patches they have. I don't follow the developer list so I don't know if any of the Debian maintainers are on it or if they've submitted any non-debian-specific patches to the Mailman developers. If they haven't, then I think they're being quite negligent -- as, apparently, does the Debian policy guidelines. -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Nothing says, Obey me! like a bloody head on a fence post. -- Stewie Griffin pgpzodbWjrNc6.pgp Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Barry Finkel ha scritto: [...] Sorry for the late response. I think that the lack of documentation in the code can be considered a bug. Then I would have to file a bug report on almost all of the Debian/Ubuntu patches to Mailman. I looked at them all, and I discarded most. I kept a few that were related to where libraries were put. I was not interested in making source code modifications where 1) I don't fully understand the source that comes from SourceForge, and 2) there is no documentation as to what the Debian changes do. It would be nice to know what each change does, but since I am not installing most of them, it really does not matter. Do the debian maintainer of Mailman frequent this mailing list? Regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
On 8/25/07, Manlio Perillo wrote: Do the debian maintainer of Mailman frequent this mailing list? Not so far as I know. Improved contact between our project and the other projects which take our code and create binary packages is one thing that we would like to work on, but of course the two biggest problems are: 1. Finding out which projects are actually doing what with our code And: 2. Motivating them to actually come talk to us about their changes If you know who the maintainer of the Debian packages is, and you can light a fire under them to get them to come participate on this list, we'd appreciate that. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Barry Finkel ha scritto: [...] The patches were, for the most part, undocumented, so I had no idea exactly what they did. Nor did I know if they would fit into the 2.1.9 source, as some of the patches were based on pre-2.1.5 code. Manlio Perillo replied: This was unexpected! Do you have opened a bug report? No, because [...] 2) I have no idea if there is a bug. I Manlio Perillo replied: Sorry for the late response. I think that the lack of documentation in the code can be considered a bug. Then I would have to file a bug report on almost all of the Debian/Ubuntu patches to Mailman. I looked at them all, and I discarded most. I kept a few that were related to where libraries were put. I was not interested in making source code modifications where 1) I don't fully understand the source that comes from SourceForge, and 2) there is no documentation as to what the Debian changes do. It would be nice to know what each change does, but since I am not installing most of them, it really does not matter. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Barry Finkel ha scritto: [...] The patches were, for the most part, undocumented, so I had no idea exactly what they did. Nor did I know if they would fit into the 2.1.9 source, as some of the patches were based on pre-2.1.5 code. Manlio Perillo replied: This was unexpected! Do you have opened a bug report? No, because [...] 2) I have no idea if there is a bug. I Sorry for the late response. I think that the lack of documentation in the code can be considered a bug. Regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Mark Sapiro ha scritto: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manlio Perillo wrote: 1) The messages from the newsgroup are not sent on the mailing list. I don't know why, there is nothing in the error log Is Mailman's cron/gate_news being run every five minutes from Mailman's crontab? Thanks: the cron tab entry is still commented. However I think that this should be documented in the admnistrative web interface. Regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Manlio Perillo Mark Sapiro ha scritto: Is Mailman's cron/gate_news being run every five minutes from Mailman's crontab? Thanks: the cron tab entry is still commented. However I think that this should be documented in the admnistrative web interface. The istallation of the crontab is documented in the installation manual (http://www.list.org/mailman-install/node41.html. I don't think it is appropriate to document cron/gate_news in the web admin interface because the typical list admin can't do anything about it anyway. It is an installation responsibility, not a list admin responsibility. Also, in Mailman as we ship it, the cron/gate_news entry is not commented out. That was done either by your site or by some repackager. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manlio Perillo wrote: 1) The messages from the newsgroup are not sent on the mailing list. I don't know why, there is nothing in the error log Is Mailman's cron/gate_news being run every five minutes from Mailman's crontab? If so, it might somehow be the case that the list's usenet_watermark attribute is greater that the last message number in the newsgroup (e.g., if you changed news servers). - -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGx6TkVVuXXpU7hpMRAqztAJ90Q/r/C0GkJn5Jcsn+7g9rJP+rQwCg5GCe kUtq+eYo8uzq+g+ZvnvT+f8= =Ugix -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
On 8/7/07, Manlio Perillo wrote: Well, having a pre-built packages systems has also some benefits. True enough, and where it makes sense we do make wide use of binary packages for other things on the system. The Debian Secutiry team still supports Debian Sarge. And in theory, if a security problem is found in an upstream package, the fix should be back ported on the Debian package. The crux of that problem is the ... in theory ... part. In practice, we know that they make a lot of modifications that they don't share with us (for whatever reason), and because of all of the internal code changes, we can't be sure that when we fix a bug in our code that they fix the same bug in theirs, or that they don't create other bugs that we don't have. Also, we know that they tend to be slow to update, and they tend to limit the stuff they back-port. So, for critical stuff, I strongly believe that you really do want to run from the source tarballs themselves. Well, the question of email in clear was raised by an it.comp.lang.python newsgroup user. And on this newsgroup, many of us do not use their real email address. If you're used to address obfuscation, then you probably don't know how many news servers out there that are silently throwing away your articles. And you probably do care more about the address obfuscation than getting your articles to the widest possible audience. However, as a system administrator who would be supporting a reasonably large group of people, the problem you've got is that what particular individuals think is good for them is not necessarily good for the group as a whole, and may not even be good for the particular individuals who don't know any better. You will need to choose where to balance the expectations and benefits of single individuals against those of the group, and you will also have to take into account the capabilities of the software. One thing to keep in mind is that e-mail users generally assume that the addresses will not be obfuscated, and so if they start seeing obfuscated addresses then they are likely to be confused -- especially if they try to reply to that person directly. So, they may have a benefit by having their e-mail addresses obfuscated when the cross the gateway, but they don't generally have an expectation that the gateway would do this for them. Overall, obfuscated addresses for e-mail users are a bad thing. In the case of USENET users, they may well be used to the address obfuscation of their choice, and they shouldn't be too surprised to see some users whose addresses are not obfuscated. However, you may not be able to re-generate a valid e-mail address for them based on their obfuscation scheme, so it's going to be difficult to un-scramble that egg. Overall, obfuscated addresses for USENET users may somewhat reduce their spam load, but these days spammers have multiple address snarfing techniques, so any obfuscation that is done is likely to be of minimal real benefit, although they may perceive a much larger benefit than is actually achieved. When you mix these communities via a gateway, you get some interesting problems where the expectations of one group conflict with the expectations of the other. And I'm not sure that anyone here can give you any hard rules to follow in such cases. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Brad Knowles wrote in reply to a posting: And I'm not at all convinced that security problems are not a problem, with Debian or any other OS, for that matter. Especially not with an old binary package that is based on old code that is known to have security flaws. When I was comparing the sources for Ubuntu/Debian Mailman 2.1.5 against the SourceForge 2.1.9 source, I had to check the three security patches in 2.1.9. Two of the patches matched; one was completely different (different code in a different module). I do not have enough knowledge of the internals of Mailman to be able to determine if this third patch resolved the security problem. I ended up building my own Ubuntu package from the 2.1.9 SourceForge source, in the process eliminating almost all of the Debian/Ubuntu patches. The patches were, for the most part, undocumented, so I had no idea exactly what they did. Nor did I know if they would fit into the 2.1.9 source, as some of the patches were based on pre-2.1.5 code. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Barry Finkel ha scritto: Brad Knowles wrote in reply to a posting: And I'm not at all convinced that security problems are not a problem, with Debian or any other OS, for that matter. Especially not with an old binary package that is based on old code that is known to have security flaws. When I was comparing the sources for Ubuntu/Debian Mailman 2.1.5 against the SourceForge 2.1.9 source, I had to check the three security patches in 2.1.9. Two of the patches matched; one was completely different (different code in a different module). I do not have enough knowledge of the internals of Mailman to be able to determine if this third patch resolved the security problem. I ended up building my own Ubuntu package from the 2.1.9 SourceForge source, in the process eliminating almost all of the Debian/Ubuntu patches. The patches were, for the most part, undocumented, so I had no idea exactly what they did. Nor did I know if they would fit into the 2.1.9 source, as some of the patches were based on pre-2.1.5 code. This was unexpected! Do you have opened a bug report? However the life of a Debian package maintainer is not easy. It should maintain a package to a stable version for 1-2 years. Regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Barry Finkel ha scritto: Brad Knowles wrote in reply to a posting: And I'm not at all convinced that security problems are not a problem, with Debian or any other OS, for that matter. Especially not with an old binary package that is based on old code that is known to have security flaws. When I was comparing the sources for Ubuntu/Debian Mailman 2.1.5 against the SourceForge 2.1.9 source, I had to check the three security patches in 2.1.9. Two of the patches matched; one was completely different (different code in a different module). I do not have enough knowledge of the internals of Mailman to be able to determine if this third patch resolved the security problem. I ended up building my own Ubuntu package from the 2.1.9 SourceForge source, in the process eliminating almost all of the Debian/Ubuntu patches. The patches were, for the most part, undocumented, so I had no idea exactly what they did. Nor did I know if they would fit into the 2.1.9 source, as some of the patches were based on pre-2.1.5 code. Manlio Perillo replied: This was unexpected! Do you have opened a bug report? No, because 1) I have built an Ubuntu Mailman package from the 2.1.9 SF source, and I am no longer interested in whatever Debian/Ubuntu did/does with their patches. I built a package, it works, and I know how to build a package from the next Mailman source release. I know which Debian/Ubuntu patches to include (those that put files in the proper Debian directories). 2) I have no idea if there is a bug. I have to assume that the third security patch they put into their Mailman package does resolve the security problem. I really have no way to test, nor do I have a desire to test. What bug do you suspect from what I wrote? -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] a few questions about the NNTP gateway
Hi all. I'm using Mailman 2.1.5. I have enabled the NNTP Gateway but there are some problems. 1) The messages from the newsgroup are not sent on the mailing list. I don't know why, there is nothing in the error log 2) When sending a message to the newsgroup, Mailman does not obscure the email address (there is an obscure_addresses, but it only works for the web archiver) I would like to know if 2) has been implemented in recent Mailman releases. One last thing. What happens when Mailman have to send an email message with a broken Subject header (R: instead of Re) to the newsgroup? Thanks Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
On 8/6/07, Manlio Perillo wrote: I'm using Mailman 2.1.5. BTW, the most recent version of Mailman is 2.1.9, which has a number of new features and some fixes for certain security holes. I'd strongly encourage you to upgrade. I have enabled the NNTP Gateway but there are some problems. 1) The messages from the newsgroup are not sent on the mailing list. I don't know why, there is nothing in the error log Go to the web admin page for your list, then go to the sub-page for Mail-News gateways. Is the news server hostname filled in? Is the newsgroup name filled in? Is the moderation policy set correctly? Do you have the radio buttons set correctly for passing traffic both ways? In your mm_cfg.py file, do you have the correct definitions for the username and password you need to use when logging into the news server to retrieve and post articles? 2) When sending a message to the newsgroup, Mailman does not obscure the email address (there is an obscure_addresses, but it only works for the web archiver) Correct. Mailman does not attempt to obscure addresses when posting mail messages to a newsgroup. I would like to know if 2) has been implemented in recent Mailman releases. Not so far as I know, but it shouldn't be hard to add. However, one problem you'll have is that many news servers will reject your articles, if you use an address obfuscation scheme that they don't support. So, your choices are to not do any obfuscation at all for news articles (which is what Mailman does today), or see if there is some common format of obfuscation that virtually all news servers are known to support. Of course, if they support it then the spammers probably already know about it as well, and anything you can do they are likely to be able to un-do. One last thing. What happens when Mailman have to send an email message with a broken Subject header (R: instead of Re) to the newsgroup? I think what happens is that the subject header will get treated as a normal subject, and may have additional things tacked onto the front of the subject line, whereas normally Mailman would have recognized the Re: portion and potentially tacked those things on between the Re: string(s) and the rest of the subject. But one of the core Mailman developers would be more likely to know the answer to that question, and they're also on this list. Hopefully they'll be able to respond to you within a few days. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Brad Knowles ha scritto: On 8/6/07, Manlio Perillo wrote: I'm using Mailman 2.1.5. BTW, the most recent version of Mailman is 2.1.9, which has a number of new features and some fixes for certain security holes. I'd strongly encourage you to upgrade. Mailman runs on a Debian Sarge server, so this can be a problem without an upgrade to Etch (but security problems are not a problem, with Debian). I have enabled the NNTP Gateway but there are some problems. 1) The messages from the newsgroup are not sent on the mailing list. I don't know why, there is nothing in the error log Go to the web admin page for your list, then go to the sub-page for Mail-News gateways. Is the news server hostname filled in? Yes Is the newsgroup name filled in? Yes Is the moderation policy set correctly? The mailing list is not moderated (but requires subscription), the newsgroup is not moderated, so I have set the value None Do you have the radio buttons set correctly for passing traffic both ways? Yes In your mm_cfg.py file, do you have the correct definitions for the username and password you need to use when logging into the news server to retrieve and post articles? The NNTP server requires no password 2) When sending a message to the newsgroup, Mailman does not obscure the email address (there is an obscure_addresses, but it only works for the web archiver) Correct. Mailman does not attempt to obscure addresses when posting mail messages to a newsgroup. Ok. I would like to know if 2) has been implemented in recent Mailman releases. Not so far as I know, but it shouldn't be hard to add. However, one problem you'll have is that many news servers will reject your articles, if you use an address obfuscation scheme that they don't support. Not sure. As an example I always use an obsured email address on usenet, without problems. But, indeed, I see that on comp.lang.python many people use their real email address. So, your choices are to not do any obfuscation at all for news articles (which is what Mailman does today), or see if there is some common format of obfuscation that virtually all news servers are known to support. Of course, if they support it then the spammers probably already know about it as well, and anything you can do they are likely to be able to un-do. Yes, this is true, unfortunately. One last thing. What happens when Mailman have to send an email message with a broken Subject header (R: instead of Re) to the newsgroup? I think what happens is that the subject header will get treated as a normal subject, and may have additional things tacked onto the front of the subject line, whereas normally Mailman would have recognized the Re: portion and potentially tacked those things on between the Re: string(s) and the rest of the subject. It would be nice if mailman can apply a filter to the subject, and to fix it. But one of the core Mailman developers would be more likely to know the answer to that question, and they're also on this list. Hopefully they'll be able to respond to you within a few days. Thanks and regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
On 8/7/07, Manlio Perillo wrote: Mailman runs on a Debian Sarge server, so this can be a problem without an upgrade to Etch (but security problems are not a problem, with Debian). You could always install Mailman from source on that system, or you may be able to find a pre-built package that is based on the latest source. This is one of the typical problems when using programs from pre-built packages, because you're totally dependant on the person/group/entity that creates the packages. And I'm not at all convinced that security problems are not a problem, with Debian or any other OS, for that matter. Especially not with an old binary package that is based on old code that is known to have security flaws. I help run the Mailman server and the mail servers for python.org, and we use Debian Linux for the OS. But we don't use any binary pre-packaged software, at least not for the critical bits like Mailman. Not so far as I know, but it shouldn't be hard to add. However, one problem you'll have is that many news servers will reject your articles, if you use an address obfuscation scheme that they don't support. Not sure. As an example I always use an obsured email address on usenet, without problems. But, indeed, I see that on comp.lang.python many people use their real email address. In part, that's because we provide the news gateway function for this newsgroup via the mail servers at python.org -- using the same Mailman server and the same mail servers that are used to host this mailing list. Mailman is a Python project, after all. ;) And certainly, addresses that come in from USENET in an obscured fashion will most likely have their messages thrown away by most modern mail servers, even if the Mailman server accepts them and processes them as normal. So, when you run that gateway, you pretty much always want to use real addresses and not make any attempt to obfuscate addresses crossing one way or the other. I think what happens is that the subject header will get treated as a normal subject, and may have additional things tacked onto the front of the subject line, whereas normally Mailman would have recognized the Re: portion and potentially tacked those things on between the Re: string(s) and the rest of the subject. It would be nice if mailman can apply a filter to the subject, and to fix it. There's a limit to what Mailman can do to fix the subject line, at least in terms of out-of-the-box code. If you're a Python programmer, it shouldn't be hard for you to add your own module to the system to handle these things, and to hook that into the appropriate place in the flow of messages through the system. In that case, we'd ask you to contribute your changes back to the project via the Mailman patch page on SourceForge, so that others may benefit from your experience. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few questions about the NNTP gateway
Brad Knowles ha scritto: On 8/7/07, Manlio Perillo wrote: Mailman runs on a Debian Sarge server, so this can be a problem without an upgrade to Etch (but security problems are not a problem, with Debian). You could always install Mailman from source on that system, or you may be able to find a pre-built package that is based on the latest source. This is one of the typical problems when using programs from pre-built packages, because you're totally dependant on the person/group/entity that creates the packages. Well, having a pre-built packages systems has also some benefits. And I'm not at all convinced that security problems are not a problem, with Debian or any other OS, for that matter. Especially not with an old binary package that is based on old code that is known to have security flaws. The Debian Secutiry team still supports Debian Sarge. And in theory, if a security problem is found in an upstream package, the fix should be back ported on the Debian package. I help run the Mailman server and the mail servers for python.org, and we use Debian Linux for the OS. But we don't use any binary pre-packaged software, at least not for the critical bits like Mailman. Ok, thanks. I will try to install the new version. [...] And certainly, addresses that come in from USENET in an obscured fashion will most likely have their messages thrown away by most modern mail servers, even if the Mailman server accepts them and processes them as normal. So, when you run that gateway, you pretty much always want to use real addresses and not make any attempt to obfuscate addresses crossing one way or the other. Well, the question of email in clear was raised by an it.comp.lang.python newsgroup user. And on this newsgroup, many of us do not use their real email address. I think what happens is that the subject header will get treated as a normal subject, and may have additional things tacked onto the front of the subject line, whereas normally Mailman would have recognized the Re: portion and potentially tacked those things on between the Re: string(s) and the rest of the subject. It would be nice if mailman can apply a filter to the subject, and to fix it. There's a limit to what Mailman can do to fix the subject line, at least in terms of out-of-the-box code. If you're a Python programmer, it shouldn't be hard for you to add your own module to the system to handle these things, and to hook that into the appropriate place in the flow of messages through the system. In that case, we'd ask you to contribute your changes back to the project via the Mailman patch page on SourceForge, so that others may benefit from your experience. Ok. Thanks and regards Manlio Perillo -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] A few questions:
I am exploring the features of Mailman 2.1.3 because of a problem I've run into with my Lyris 4.2. For some years I have been running the 200 subscribers version of Lyris 4.2, as a free community list service, but have just run into the 50 list limit and I need to move some of those lists, possibly to an available Mailman server. But I have a few questions about Mailman that I have been unable to answer from the documenation I've been able to find. 1. One of my regular tasks is to look at the delivery logs for the messagea that are sent to the lsits. In Mailman, is it possible to get delivery reports for each message sent to a list. 2. The welcome message is only partly configurable for the list. How can I change the tech part of the welcome message. 3. I use quite a few action phrases in Lyris, and can send a message to the author if a message is blocked because of an action. Is it possible to send a message to a user whenever content filters are invoked in Mailman. Many thanks Jim Swift Alberni Valley Community list service -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] a few questions
Hi, I'm considering switching a list of around 9,000 subscribers to Mailman. Currently we are using eMerge and it's rather bad. I had a few questions, that I hoped you could answer: 1) How large can the mailing list be? Is 9,000 too large? If not, is there a way to tell Mailman not to send all the message all at once -- I am thinking about this so that it all doesn't get bounced back saying too many recipients. 2) Do the subscribers have to always confirm their subscription or can the list owner do this on their behalf? (I am thinking here about data-convertion, and also circumstances where people ask us to subscribe them for us because they can't.) 3) If so, can we do a bulk-add then? Does the web-interface allow this? 3) Lastly can it be made so that the subscribers cannot reply to the list? I believe this is called a closed list? (Our current list is one-way, so to speak, and we wanted it to remain this way.) I'd really appreciate it if you would be able to answer these questions for me. Thanks in advance. Regards, Rama Kesava -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] a few questions
On Tue, 9 Apr 2002 12:37 +0100 Rama Kesava BVTS [EMAIL PROTECTED] wrote: 1) How large can the mailing list be? Is 9,000 too large? If not, is there a way to tell Mailman not to send all the message all at once -- I am thinking about this so that it all doesn't get bounced back saying too many recipients. Please see the FAQ: http://www.python.org/cgi-bin/faqw-mm.py 2) Do the subscribers have to always confirm their subscription or can the list owner do this on their behalf? (I am thinking here about data-convertion, and also circumstances where people ask us to subscribe them for us because they can't.) List-owners can subscribe addresses manually via the web interface or CLI. 3) If so, can we do a bulk-add then? Does the web-interface allow this? Yes. The CLI is more suited however. 3) Lastly can it be made so that the subscribers cannot reply to the list? I believe this is called a closed list? (Our current list is one-way, so to speak, and we wanted it to remain this way.) Yes, tho 2.1 (currently in beta) handles this better than 2.0. -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] a few questions
ok, here it is, I spent some time on this so far so any help would be appreciated. It still looks to me like make doesn't finish. Thanks for your help! On Fri, 11 Jan 2002, C. Bensend wrote: On Fri, 11 Jan 2002, Justin Zygmont wrote: this is a new install, straight from tar.gz and it still doesn't create the wrapper program and who knows what else. Time to see _exactly_ what's happening... Could you use 'script' to document the steps (and all output) you're taking from tarball, right up to where you do an 'ls -l' and don't see a 'wrapper'? Ie, the untarring, the build, and everything. Something isn't quite logical here. Benny ~~ A 'good' landing is one from which you can walk away. A 'great' landing is one after which they can use the plane again. --Rules of the Air, #8 Script started on Sat Jan 12 19:53:50 2002 [mailman]# finger mailman Login: mailman Name: (null) Directory: /home/mailmanShell: /bin/bash Never logged in. Mail last read Tue Jan 1 22:49 2002 (EST) No Plan. [mailman]# cat /etc/passwd |grep mailman mailman:x:650:650::/home/mailman:/bin/bash [mailman]# cat /etc/passwd |grep mailman mailman:x:650: [mailman]# whoami root [mailman]# ls mailman-2.0.8.tgz typescript [mailman]# chgrp mailman . [mailman]# chmod a+rx,g+ws . [mailman]# ls -la total 416 drwxrwsr-x2 mailman mailman 4096 Jan 12 19:53 . drwxr-xr-x 154 root root 4096 Jan 12 17:34 .. -rw-r--r--1 root root 412751 Dec 26 00:27 mailman-2.0.8.tgz -rw-r--r--1 root mailman 0 Jan 12 19:53 typescript [mailman]# cat /etc/sendmail.cf | grep DefaultUser O DefaultUser=mail:mail [mailman]# cat /etc/sendmail.cf | grep mail mail::12:mail mailnull:x:47: mailman:x:650: [mailman]# tar -xzvf mailman* mailman-2.0.8/ mailman-2.0.8/Mailman/ mailman-2.0.8/Mailman/Archiver/ mailman-2.0.8/Mailman/Archiver/Archiver.py mailman-2.0.8/Mailman/Archiver/HyperArch.py mailman-2.0.8/Mailman/Archiver/HyperDatabase.py mailman-2.0.8/Mailman/Archiver/Makefile.in mailman-2.0.8/Mailman/Archiver/__init__.py mailman-2.0.8/Mailman/Archiver/pipermail.py mailman-2.0.8/Mailman/Autoresponder.py mailman-2.0.8/Mailman/Bouncer.py mailman-2.0.8/Mailman/Crypt.py mailman-2.0.8/Mailman/Defaults.py.in mailman-2.0.8/Mailman/Deliverer.py mailman-2.0.8/Mailman/Digester.py mailman-2.0.8/Mailman/EncWord.py mailman-2.0.8/Mailman/Errors.py mailman-2.0.8/Mailman/GatewayManager.py mailman-2.0.8/Mailman/HTMLFormatter.py mailman-2.0.8/Mailman/ListAdmin.py mailman-2.0.8/Mailman/LockFile.py mailman-2.0.8/Mailman/MailCommandHandler.py mailman-2.0.8/Mailman/MailList.py mailman-2.0.8/Mailman/Mailbox.py mailman-2.0.8/Mailman/Makefile.in mailman-2.0.8/Mailman/Message.py mailman-2.0.8/Mailman/Pending.py mailman-2.0.8/Mailman/SecurityManager.py mailman-2.0.8/Mailman/Utils.py mailman-2.0.8/Mailman/Version.py mailman-2.0.8/Mailman/__init__.py mailman-2.0.8/Mailman/aliases.py mailman-2.0.8/Mailman/htmlformat.py mailman-2.0.8/Mailman/mm_cfg.py.dist.in mailman-2.0.8/Mailman/versions.py mailman-2.0.8/Mailman/Bouncers/ mailman-2.0.8/Mailman/Bouncers/BouncerAPI.py mailman-2.0.8/Mailman/Bouncers/Caiwireless.py mailman-2.0.8/Mailman/Bouncers/Catchall.py mailman-2.0.8/Mailman/Bouncers/Compuserve.py mailman-2.0.8/Mailman/Bouncers/DSN.py mailman-2.0.8/Mailman/Bouncers/Exim.py mailman-2.0.8/Mailman/Bouncers/GroupWise.py mailman-2.0.8/Mailman/Bouncers/Makefile.in mailman-2.0.8/Mailman/Bouncers/Microsoft.py mailman-2.0.8/Mailman/Bouncers/Netscape.py mailman-2.0.8/Mailman/Bouncers/Postfix.py mailman-2.0.8/Mailman/Bouncers/Qmail.py mailman-2.0.8/Mailman/Bouncers/SMTP32.py mailman-2.0.8/Mailman/Bouncers/SimpleMatch.py mailman-2.0.8/Mailman/Bouncers/Smail.py mailman-2.0.8/Mailman/Bouncers/Yahoo.py mailman-2.0.8/Mailman/Bouncers/__init__.py mailman-2.0.8/Mailman/Cgi/ mailman-2.0.8/Mailman/Cgi/Auth.py mailman-2.0.8/Mailman/Cgi/Makefile.in mailman-2.0.8/Mailman/Cgi/__init__.py mailman-2.0.8/Mailman/Cgi/admin.py mailman-2.0.8/Mailman/Cgi/admindb.py mailman-2.0.8/Mailman/Cgi/edithtml.py mailman-2.0.8/Mailman/Cgi/handle_opts.py mailman-2.0.8/Mailman/Cgi/listinfo.py mailman-2.0.8/Mailman/Cgi/options.py mailman-2.0.8/Mailman/Cgi/private.py mailman-2.0.8/Mailman/Cgi/roster.py mailman-2.0.8/Mailman/Cgi/subscribe.py mailman-2.0.8/Mailman/Handlers/ mailman-2.0.8/Mailman/Handlers/Acknowledge.py mailman-2.0.8/Mailman/Handlers/AfterDelivery.py mailman-2.0.8/Mailman/Handlers/Approve.py mailman-2.0.8/Mailman/Handlers/CalcRecips.py mailman-2.0.8/Mailman/Handlers/Cleanse.py mailman-2.0.8/Mailman/Handlers/CookHeaders.py mailman-2.0.8/Mailman/Handlers/Decorate.py mailman-2.0.8/Mailman/Handlers/HandlerAPI.py mailman-2.0.8/Mailman/Handlers/Hold.py mailman-2.0.8/Mailman/Handlers/Makefile.in
Re: [Mailman-Users] a few questions (fwd)
Quoting C. Bensend ([EMAIL PROTECTED]): from common.h:27, from ./common.c:20: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory make[1]: *** [common.o] Error 1 Now, to fix it... On one of my linux boxen, I did a 'locate errno.h'. It appears in '/usr/include/errno.h', and from the output of 'rpm -qf /usr/include/errno.h': No, the compiler was looking for linux/errno.h, not errno.h. The word linux is a clue - the include file is part of the kernel distribution, not part of the compiler. If you want to compile just about anything in Linux, you have to install the kernel headers package. -- Paul Tomblin [EMAIL PROTECTED], not speaking for anybody My brother went to Florida, and all he bought me was this stupid election. - George W. Bush -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] a few questions (fwd)
On Sun, 13 Jan 2002, Paul Tomblin wrote: Now, to fix it... On one of my linux boxen, I did a 'locate errno.h'. It appears in '/usr/include/errno.h', and from the output of 'rpm -qf /usr/include/errno.h': No, the compiler was looking for linux/errno.h, not errno.h. The word linux is a clue - the include file is part of the kernel distribution, not part of the compiler. If you want to compile just about anything in Linux, you have to install the kernel headers package. Good point, Paul... Once I re-read this after getting some _sleep_, I noticed my error. Thanks for the correction, hope this helps Justin. :) Benny ~~ A 'good' landing is one from which you can walk away. A 'great' landing is one after which they can use the plane again. --Rules of the Air, #8 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] a few questions (fwd)
Whoops, I meant to cc the list on this - hopefully, it will help someone searching in the archives at a later time, too. :) Benny ~~ A 'good' landing is one from which you can walk away. A 'great' landing is one after which they can use the plane again. --Rules of the Air, #8 -- Forwarded message -- Date: Sat, 12 Jan 2002 23:14:02 -0600 (CST) From: C. Bensend [EMAIL PROTECTED] To: Justin Zygmont [EMAIL PROTECTED] Subject: Re: [Mailman-Users] a few questions On Sat, 12 Jan 2002, Justin Zygmont wrote: ok, here it is, I spent some time on this so far so any help would be appreciated. It still looks to me like make doesn't finish. Thanks for your help! Hey Justin, From your script output: make[1]: Entering directory `/home/mailman/mailman-2.0.8/src' gcc -c -I. -DPREFIX=\/home/mailman\ -DPYTHON=\/usr/bin/python\ -DHELPFUL -g -O2 -g -O2 -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADER S=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 ./common.c In file included from /usr/include/errno.h:36, from common.h:27, from ./common.c:20: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory make[1]: *** [common.o] Error 1 You'll notice that this error came when it entered the directory 'src', where the mail-wrapper.c file lives. Hence, it didn't build _anything_ in that directory. Hence, no wrapper. :( Now, to fix it... On one of my linux boxen, I did a 'locate errno.h'. It appears in '/usr/include/errno.h', and from the output of 'rpm -qf /usr/include/errno.h': hostname (user)% rpm -qf /usr/include/errno.h glibc-devel-2.1.3-15 You need to install the glibc-devel package, and I bet it will work perfectly. :) You _are_ running on linux, if I remember correctly? HTH! Benny ~~ A 'good' landing is one from which you can walk away. A 'great' landing is one after which they can use the plane again. --Rules of the Air, #8 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] a few questions
hmm, I thought I almost had it but when I check, here's what I get: [jzygmont]# rpm -q glibc-devel glibc-devel-2.1.3-15 [jzygmont]# find / -name errno.h find: /proc/6/fd: Permission denied /usr/include/bits/errno.h /usr/include/errno.h /usr/include/sys/errno.h /usr/lib/bcc/include/arch/errno.h /usr/lib/bcc/include/bsd/errno.h /usr/lib/bcc/include/errno.h /usr/lib/bcc/include/generic/errno.h /usr/lib/bcc/include/linux/errno.h /usr/lib/bcc/include/linuxmt/errno.h /usr/lib/bcc/include/msdos/errno.h /usr/lib/bcc/include/sys/errno.h [jzygmont]# exit any ideas? I really have to thank you for your help so far. On Sat, 12 Jan 2002, C. Bensend wrote: On Sat, 12 Jan 2002, Justin Zygmont wrote: ok, here it is, I spent some time on this so far so any help would be appreciated. It still looks to me like make doesn't finish. Thanks for your help! Hey Justin, From your script output: make[1]: Entering directory `/home/mailman/mailman-2.0.8/src' gcc -c -I. -DPREFIX=\/home/mailman\ -DPYTHON=\/usr/bin/python\ -DHELPFUL -g -O2 -g -O2 -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DHAVE_SYSLOG=1 -DSTDC_HEADER S=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VSNPRINTF=1 ./common.c In file included from /usr/include/errno.h:36, from common.h:27, from ./common.c:20: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory make[1]: *** [common.o] Error 1 You'll notice that this error came when it entered the directory 'src', where the mail-wrapper.c file lives. Hence, it didn't build _anything_ in that directory. Hence, no wrapper. :( Now, to fix it... On one of my linux boxen, I did a 'locate errno.h'. It appears in '/usr/include/errno.h', and from the output of 'rpm -qf /usr/include/errno.h': hostname (user)% rpm -qf /usr/include/errno.h glibc-devel-2.1.3-15 You need to install the glibc-devel package, and I bet it will work perfectly. :) You _are_ running on linux, if I remember correctly? HTH! Benny ~~ A 'good' landing is one from which you can walk away. A 'great' landing is one after which they can use the plane again. --Rules of the Air, #8 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] a few questions
are you upgrading your mailman or is it a new install ? Justin Zygmont wrote: when I get to the 'make install' step everythink looks fine except for this last part: Upgrading from version 0x0 to 0x20008f0 no lists == nothing to do, exiting Please let me know if this is still ok, or I have midded something. I cannot get meail man to work and i've tried several times. I just want to verify this to make sure i'm getting it right, --with-mail-gid should be the GID of 'DefaultUser' in /etc/sendmail.cf? the DefaultUser is 'mail' and it's GID is 12 thanks.. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] a few questions
this is a new install, straight from tar.gz and it still doesn't create the wrapper program and who knows what else. On Fri, 11 Jan 2002, Terry Davis wrote: are you upgrading your mailman or is it a new install ? Justin Zygmont wrote: when I get to the 'make install' step everythink looks fine except for this last part: Upgrading from version 0x0 to 0x20008f0 no lists == nothing to do, exiting Please let me know if this is still ok, or I have midded something. I cannot get meail man to work and i've tried several times. I just want to verify this to make sure i'm getting it right, --with-mail-gid should be the GID of 'DefaultUser' in /etc/sendmail.cf? the DefaultUser is 'mail' and it's GID is 12 thanks.. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] a few questions
On Fri, 11 Jan 2002, Justin Zygmont wrote: this is a new install, straight from tar.gz and it still doesn't create the wrapper program and who knows what else. Time to see _exactly_ what's happening... Could you use 'script' to document the steps (and all output) you're taking from tarball, right up to where you do an 'ls -l' and don't see a 'wrapper'? Ie, the untarring, the build, and everything. Something isn't quite logical here. Benny ~~ A 'good' landing is one from which you can walk away. A 'great' landing is one after which they can use the plane again. --Rules of the Air, #8 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] a few questions
when I get to the 'make install' step everythink looks fine except for this last part: Upgrading from version 0x0 to 0x20008f0 no lists == nothing to do, exiting Please let me know if this is still ok, or I have midded something. I cannot get meail man to work and i've tried several times. I just want to verify this to make sure i'm getting it right, --with-mail-gid should be the GID of 'DefaultUser' in /etc/sendmail.cf? the DefaultUser is 'mail' and it's GID is 12 thanks.. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
