Re: [Mailman-Users] Maiing list
On Fri, Oct 2, 2009 at 20:49, Lindsay DeVries lind...@gmail.com wrote: Hi there, I'm TA-ing a course, and need to make a mailing list. I've done it before, but can't seem to find where to apply for one again. Thanks! This is a mailing list about the software mailman, which helps you run your own mailing lists. This isn't a list about finding list servers accessible to all ;) That said, the question is common enough that I'm sure you'll find pointers in the list archive. Indeed here's a sample for you: http://www.mail-archive.com/mailman-users@python.org/msg54661.html -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] fight spam !!
We also use Postgrey on our server in addition to SpamAssassin...that also seems to help cut down on spam. Mark --- Mark Ryan Network Administrator Center for Special Needs Populations The Ohio State University 1900 Kenny Road Columbus, OH 43210 (614) 292-0786 phone (614) 292-6505 fax www.csnp.ohio-state.edu -Original Message- From: mailman-users-bounces+ryan.1002=osu@python.org [mailto:mailman-users-bounces+ryan.1002=osu@python.org] On Behalf Of ?? Sent: Sunday, October 04, 2009 2:18 AM To: Khalil Abbas Cc: mailman-users@python.org Subject: Re: [Mailman-Users] fight spam !! Khalil Abbas khillo...@hotmail.com writes: ok now I'm really fed up! this is too freaking much incoming incoming incoming they never stop!!! please, is there anyone who can refer to articles about how to know the source of these messages and how to report them to their ISPs and to there authorities ??? common people MUST be educated about this!! so if we kill 10% of the spam going on it will be a big achievement! SpamAssassin is your friend ..;; Sincerely, -- Why do we have to pay him? What can he do to the three of us? We're stronger than him. We have guns. Why do we have to hand over the money we earned? Fanucci has friends, real brutes. He has connections with the police. He'd like us to tell him our plans because he could set us up for the corps and earn their gratitude. Then they would owe him a favor. That's how he operates. And he has a license from Maranzalla himself to work this neighborhood. -- Vito Corleone and Peter Clemenza, Chapter 14, page 198 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/ryan.1002% 40osu.edu Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Extra space in mime encoded headers
Mark Sapiro wrote: (MIME encoded headers are re- encoded by mailman and spaces are added around each encoded character.) likely my description was based on incorrect assumptions. If clients encoded the entire word instead of just single characters, this wouldn't be an issue. I believe most clients do this, and I think I looked at other messages from this sender (received directly) and the subjects were encoded entirely so I thought this was also the case for the messages transported by mailman. Now I asked him for a mail sent from the same environment as the list messages were and indeed, the 8 bit characters were encoded separately (Microsoft Entourage) - stupid. I told him that... RFC 2047 effectively requires it. ...his mail client is likely broken and he will try Opera next time. Thanks for the detailed explanation. Oliver -- Oliver Betz, Muenchen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Cannot send mail to mailing lists
Hi, I have mailman version 2.1.9 running on a Centos 5.2 64 bit. (Python 2.4.3/Apache 2.2.3/Sendmail 8.13) I'm able to subscribe to newly created mailing lists/Get confirmation e-mails from Mailman on subscription. I'm unable to send e-mails to these lists (which I can confirm by being a member of these lists and not receiving any e-mails when mails are sent to the lists) The logs are clean. I tried to send an email from the command line interface of the mailman server and I can see the mails being sent. Any suggestions on what to check next would be greatly helpful. Thanks a lot. Krishna -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Mon, 5 Oct 2009, Mark Sapiro wrote: You seem to have done your homework well, and to have a good understanding of the issues. You can learn a lot in 5 hours of reading. :) I found http://ndim.fedorapeople.org/stuff/mailman-vhost/ which appears to contain the same patches that were at http://nix.lauft.net/htdocs/mailman/. Thanks for this. This stuff looks a bit old. It's patches against Mailman 2.1.7 and files seem to date back to 2006. The docs talk about what's going to happen in 2008. Does this code patch against 2.1.12? Is there newer code than this or should I get it from git? And is there any more documentation than the ReadMe files on this site? I thought I saw a branch up in the Launchpad project that deals with this. Is that a better place to start than these patches? Are these patches still the recommended way to achieve what I'm looking for? My concerns right now are: 1. I need to implement this on a production system, so it has to implement the ability to have the same list names on multiple domains and domain-specific site passwords. And it needs to be stable (i.e. it needs to work as advertised). 2. I need to deploy this pretty quickly so I need some documentation or at least people willing to help if I get stuck. and 3. I need to know if the changes proposed here (or anywhere) will be compatible with what will eventually be adopted in mainline, or at least that there will be some kind of migration path. I can't really afford to send us down a dead-end path. I'm sorry about all the questions but I'm a bit under the pump here, but I also want to do it right the first time. Any advice anyone can give will be most gratefully received. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Mon, 5 Oct 2009, Mark Sapiro wrote: I just applied the mailman-2.1.7-20060114-to-vhost.patch to the 2.1.12 base and it applied with only two rejects, both of which are easy to fix. Whether the patched code will actually work and meet your requirements, I can't say. I probably can't afford the luxury of testing it, at least not now. I thought I saw a branch up in the Launchpad project that deals with this. Is that a better place to start than these patches? Maybe, but I don't see one at https://code.launchpad.net/mailman?field.lifecycle=ALL. Well it was something like 3 in the morning when I was looking. Let me see... Ok, scrub that. Was something else. Are these patches still the recommended way to achieve what I'm looking for? I don't recommend any of these patches. Multiple Mailman instances is the recommended way for Mailman 2.1 ah. This is what I need to hear. My concerns right now are: 1. I need to implement this on a production system, so it has to implement the ability to have the same list names on multiple domains and domain-specific site passwords. And it needs to be stable (i.e. it needs to work as advertised). I don't see that these patches implement a domain specific site password. hmmm...I see it's listed as an outstanding issue. My recommendation would be to create separate Mailman instances per domain. I know you said originally 3. Multiple installs. I'd rather not do this if I can help it. Not only do I have to make sure that all of them play nice with the mail system (postfix), but I can see the day when we'll want to upgrade, and that's going to mean upgrading something like 7 installations. ergh. This may be a pain if you use a package that isn't designed for it, but I wouldn't do this with a package, I can't see how I could get it to install into different places without a *lot* of gymnastics like chroots. if you install from source and you have Mailman generating aliases and virtual maps for Postfix, all this means is you need to add 7 entries to alias_maps and virtual_alias_maps instead of just one. Ok...This is tarting to sound doable. It also means I can get the most important domains up quickly. Is there any documentation for doing this? I need to have 7 lots of everything, right? And as long as you keep track of your configure commands, upgrading a source install is very easy and straightforward. Upgrading 7 unpatched installations is probably easier than upgrading 1 patched one. Yeah I guess it would be. We know this works, and there will be a migration path to MM 3. That was my other concern about this approach - how to integrate into a unified install once it is officially supported. But if you will be providing an upgrade path from multiple installs then this makes me more comfortable with the idea. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Cannot send mail to mailing lists
On Mon, Oct 05, 2009 at 07:40:25AM -0700, Krishnadas Kossery wrote: I have mailman version 2.1.9 running on a Centos 5.2 64 bit. (Python 2.4.3/Apache 2.2.3/Sendmail 8.13) I'm able to subscribe to newly created mailing lists/Get confirmation e-mails from Mailman on subscription. I'm unable to send e-mails to these lists (which I can confirm by being a member of these lists and not receiving any e-mails when mails are sent to the lists) The logs are clean. Which logs? Mailman's, presumably. Empty logs (on a new install) make me think to qrunner not running: is it? (check, maybe with ps, start with bin/mailmanctl) Is archiving for the lists switched on? Are messages being delivered to the archives? I tried to send an email from the command line interface of the mailman server and I can see the mails being sent. How do you see the mails being sent? Any suggestions on what to check next would be greatly helpful. I'd check MTA config, MTA logs, then working out where (if) messages destined to Mailman were (not) going. -- ``I speak better English than this villain Bush.'' (Muhammed Saeed al-Sahaf, attrib.) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
