Re: [Mailman-Users] Yum install of mailman on CentOS 5
Hi Duncan, is SELinux enabled? [EMAIL PROTECTED] root]# getenforce If SELinux is enforcing set it temporary into permissive mode by [EMAIL PROTECTED] root]# setenforce 0 and check your webinterface again. Timm Mark Sapiro schrieb: Duncan Drury wrote: After bringing the RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo directive into my vhost directive block, listinfo also started working. I think that the mailman.conf file created by the rpm might work fine on a server where there is only a single domain, but not for those hosting other websites. It shouldn't matter. In my installation, I have RedirectMatch ^/mailman[/]*$ /mailman/listinfo in the main configuration prior to any VirtualHost blocks, and it works just fine for the main server and all virtual hosts. I don't specify a scheme or a host in my redirect target which just defaults them to the scheme and host of the original URL which is more appropriate in a virtual host environment - you don't want to redirect http://virt1.example.com/mailman to http://virt2.example.com/mailman/listinfo - but I don't think that difference should cause the problem you see. (I have reported this latter situation at https://bugzilla.redhat.com/show_bug.cgi?id=455185). -- 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] Deleting Mailman Mbox
Carlos Williams wrote: I have no idea what happened to my mailman installation. As far as I can tell from a very basic administrative and user level, it works perfect with my Postifx install. Only only noticed this was a problem when I started to migrate my mailman data to a new email server I am building to replace this old hardware. When I go to /var/lib/mailman/archives/private - I then see the mailman.mbox directory. This directory repeats over and over: [EMAIL PROTECTED] mailman.mbox]# pwd /var/lib/mailman/archives/private/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox I have never seen anything like this and so far this is the only one I have seen so far with this problem. My only solution to fix it is to delete everything recursive from /var/lib/mailman/archives/mailman.mbox. I don't know if this is going to break anything or what. I notice in my other *.mbox directories, there is always a file that ends in *.mbox. Someone else reported a similar symptom a month or two ago. (I just tried to find this in the archive, and I see it was you, not someone else.) I have no idea how this happened. I suspect somehow instead of mailman.mbox/mailman.mbox being a file, it somehow became a link back to its parent. If this is the case, even rm -rf /var/lib/mailman/archives/mailman.mbox may not succeed because it may loop indefinitely, but it's worth a try. At worst, you might be able to mv /var/lib/mailman/archives/mailman.mbox junk. Then you could create a new /var/lib/mailman/archives/mailman.mbox directory and empty /var/lib/mailman/archives/mailman.mbox/mailman.mbox file with the same ownership and permissions as the good ones. -- 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://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] Deleting Mailman Mbox
On Mon, Jul 14, 2008 at 11:33 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Someone else reported a similar symptom a month or two ago. (I just tried to find this in the archive, and I see it was you, not someone else.) Yes - I reported this during my migration help email. It was me... I have no idea how this happened. I suspect somehow instead of mailman.mbox/mailman.mbox being a file, it somehow became a link back to its parent. If this is the case, even rm -rf /var/lib/mailman/archives/mailman.mbox may not succeed because it may loop indefinitely, but it's worth a try. At worst, you might be able to mv /var/lib/mailman/archives/mailman.mbox junk. Then you could create a new /var/lib/mailman/archives/mailman.mbox directory and empty /var/lib/mailman/archives/mailman.mbox/mailman.mbox file with the same ownership and permissions as the good ones. So I think I am simply going to just rm -rf /var/lib/mailman/archives/private/mailman.mbox/mailman.box This will retain the first mailman.box directory which is expected to be there and then remove everything beyond that. I will then assume at some point Mailman will attempt to re-generate a mailbox.mbox file in that directory. Do you think this is a bad idea? -- 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] Runaway python process
I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we had a mail loop which pounded our list server. The mail loop has been fixed but there is a python process that is consuming an entire cpu. Further inspection of this process reveals: qrunner --runner=ArchRunner:0:1 -s I'm assuming that ArchRunner is a process that archives incoming messages and that mailman is in the process of archiving all those thousands of messages that were received due to the mail loop. I've been searching the mailman site and also googling to find a way to discard all those bogus messages. I'm getting pressure to fix this fast because people cannot log in to the web interface because the server is pegged due to this process. So, 1) I'd like to know if I'm going down the right path assuming mailman is busy archiving all those messages and 2) How can I get it to stop? I'm going to log into the web interface even though it will forever to get the page to come up and I will try disabling archiving fir the affected list. Not sure if that will stop the archiving that is already happening or not but I'm going to give it a try. -- Andy -- 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] Runaway python process
Andy Cravens wrote: I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we had a mail loop which pounded our list server. The mail loop has been fixed but there is a python process that is consuming an entire cpu. Further inspection of this process reveals: qrunner --runner=ArchRunner:0:1 -s I'm assuming that ArchRunner is a process that archives incoming messages and that mailman is in the process of archiving all those thousands of messages that were received due to the mail loop. I've been searching the mailman site and also googling to find a way to discard all those bogus messages. I'm getting pressure to fix this fast because people cannot log in to the web interface because the server is pegged due to this process. So, 1) I'd like to know if I'm going down the right path assuming mailman is busy archiving all those messages and 2) How can I get it to stop? I'm going to log into the web interface even though it will forever to get the page to come up and I will try disabling archiving fir the affected list. Not sure if that will stop the archiving that is already happening or not but I'm going to give it a try. End original message. - I'd suggest killing the archive runner process. And then disabling archiving in the web interface. Then you can go in and remove the offending files from qfiles/archive (though exactly what needs to be done there I am not certain). You probably also want to remove the offending messages from the mbox files for the lists and then rebuild the archives without them, though there are issues with possibly breaking links to messages in the archives. Once you have things cleaned up, you can restart mailman and re-enable archiving. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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] Runaway python process
Dragon wrote: Andy Cravens wrote: I'm running Mailman 2.1.9 on Solaris 10. Sometime this weekend we had a mail loop which pounded our list server. The mail loop has been fixed but there is a python process that is consuming an entire cpu. Further inspection of this process reveals: qrunner --runner=ArchRunner:0:1 -s I'm assuming that ArchRunner is a process that archives incoming messages and that mailman is in the process of archiving all those thousands of messages that were received due to the mail loop. I've been searching the mailman site and also googling to find a way to discard all those bogus messages. I'm getting pressure to fix this fast because people cannot log in to the web interface because the server is pegged due to this process. So, 1) I'd like to know if I'm going down the right path assuming mailman is busy archiving all those messages and 2) How can I get it to stop? I'm going to log into the web interface even though it will forever to get the page to come up and I will try disabling archiving fir the affected list. Not sure if that will stop the archiving that is already happening or not but I'm going to give it a try. End original message. - I'd suggest killing the archive runner process. And then disabling archiving in the web interface. Then you can go in and remove the offending files from qfiles/archive (though exactly what needs to be done there I am not certain). You probably also want to remove the offending messages from the mbox files for the lists and then rebuild the archives without them, though there are issues with possibly breaking links to messages in the archives. Once you have things cleaned up, you can restart mailman and re-enable archiving. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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/acravens%40uen.org Security Policy: http://wiki.list.org/x/QIA9 Problem solved. I already killed that qrunner process so that I could edit the archive options via the web interface. The key was deleting the 25,000 files from qfiles/archive. and then restarting mailman. I probably deleted some other legit archives to other lists in the process but at least we're back up. Probably should have done a selective delete by grepping for the list name within the file but oh well... Thanks for pointing me to qfiles/archive. I learned something. -- Andy -- 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] Can't create list
On Sun, Jul 13, 2008 at 03:03:41PM -0700, Mark Sapiro wrote:
Because those host names are not in the VIRTUAL_HOSTS dictionary. You
could put something like
add_virtualhost('192.168.1.1', '192.168.1.1')
in mm_cfg.py and then create a list in the '192.168.1.1' domain, but
don't do that because the domain '192.168.1.1' will appear everywhere
in that list's links and addresses and it won't work from outside your
LAN.
I tried it from work and got the same problem, virtual host unknown: vidiot.com
MB
--
e-mail: [EMAIL PROTECTED]/~\ The ASCII
[I've been to Earth. I know where it is. ] \ / Ribbon Campaign
[And I'm gonna take us there.Starbuck 3/25/07] X Against
Visit - URL: http://vidiot.com/ / \ HTML Email
--
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] Feature Request: Selective Mass Subscription
Zbigniew Szalbot writes: 1/ Mailman as a discussion list - like the one we're having here. I don't imagine spammers would be setting up their lists as discussion list, would they? I don't actually imagine big time spammers using mailman. They're all about botnets. Big time spammers won't use Mailman, true, but we can't predict how they will format their messages. If formatting messages like Mailman discussion lists makes it more likely they'll be delivered to end users, they'll do that. They avoid getting return mail simply by not running MTA servers! I'd love to see Mailman giving me an option to create either discussion or announcement list with pre-set features for each of them. One of these pre-sets could be in fact the presence or absence of mass-subscribe feature defined per list during list creation. Barry for Mailman 3 has been talking about making Mailman easier to configure, and I'm sure Mark would consider adding improved config tools to 2.2. But (my impression is that) all of the developers have Usenet/devel list backgrounds. Clear and detailed lists of needed features, eg, what currently unconfigurable behavior needs to be configurable, and how. So the mass subscribe feature is a good example of a configuration need, and it needs not only to be on/off, but some kind of rate limit seems to be desirable. (Even though Cyndi's ISP decided not to allow it, it was attractive enough that they considered it seriously.) I think these features would be best described on the wiki (but there doesn't seem to be an obvious place for the community's wishlist as opposed to developer proposals), and discussed on mailman-developers. However, if I understand the current trends, discussion lists are dropped in favour of online forums and newsletter/marketing tools are more and more sought after. On the other hand, the people who can actually contribute code to Mailman are so far more versed in the discussion lists. This is a market to gain for Mailman but it currently lacks a few features to do that. Well, my post is slowly getting off topic But IMO it would be quite on-topic for mailman-developers. This kind of post would be more effective in inciting dev activity if more focused. Eg, rather than talking about markets to gain, which sounds good but generally doesn't attract a lot of dev effort, talk about specific tasks and their needs, and the specific features that could be extended or added to satisfy them. Remember, AIUI at least, the devs have little experience with these usages so concrete details of requirements would be very helpful. -- 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] mailman servers coordination: find spammers
I often see addresses popping up and subscribing to all visible lists on my servers. Sometimes they're a curious individual, and most times they are spammers harversting addresses (as these are open only to admin). I wonder what the coding price would be, if it can even work with mailman, to create a central trusted DB which watched subscription trends? 1. It could be used for security. 2. It could fight spammers on the mailman front. 3. If we deal with the security and privacy implications of the first two, or want a constructive cause--collect cool trends and provide with a mailing lists index by tag words and activity. Think technorati.. This of course, is just a neat idea. Thoughts? Thanks, Gadi. -- 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] mailman servers coordination: find spammers
First, I think it would have better luck on the developers mailing list :) But as for the idea, I think it could work, but someone would have to provide the hosting for the database that would hold all the info. And we would have to figure out who would be a trusted source to report the spam My spam might be your ham... I need lunch hehe In general though I like the idea and would love to hear from others on it as well :) On Jul 14, 2008, at 1:25 PM, Gadi Evron wrote: I often see addresses popping up and subscribing to all visible lists on my servers. Sometimes they're a curious individual, and most times they are spammers harversting addresses (as these are open only to admin). I wonder what the coding price would be, if it can even work with mailman, to create a central trusted DB which watched subscription trends? 1. It could be used for security. 2. It could fight spammers on the mailman front. 3. If we deal with the security and privacy implications of the first two, or want a constructive cause--collect cool trends and provide with a mailing lists index by tag words and activity. Think technorati.. This of course, is just a neat idea. Thoughts? Thanks, Gadi. -- 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/japruim%40raoset.com Security Policy: http://wiki.list.org/x/QIA9 -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 11287 James St Holland, MI 49424 www.raoset.com [EMAIL PROTECTED] -- 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] mailman servers coordination: find spammers
The problem I see with this is much like the DNSBLs and Block lists (spamhaus?). As Jason put it, one person's spam could very much be another person's ham, so mail starts getting rejected by those who outright trust such a database and it is hell trying to get removed from those said lists. Not to mention, there is so much forgery and many changes to spam tricks that even SA has to keep up with it. :-( Personally, I think spam filtering/watching/fighting should be done per server, per user, etc. Would be real nice if the ISP's would start doing that... My opinion. :-) Jason Pruim wrote: First, I think it would have better luck on the developers mailing list :) But as for the idea, I think it could work, but someone would have to provide the hosting for the database that would hold all the info. And we would have to figure out who would be a trusted source to report the spam My spam might be your ham... I need lunch hehe In general though I like the idea and would love to hear from others on it as well :) On Jul 14, 2008, at 1:25 PM, Gadi Evron wrote: I often see addresses popping up and subscribing to all visible lists on my servers. Sometimes they're a curious individual, and most times they are spammers harversting addresses (as these are open only to admin). I wonder what the coding price would be, if it can even work with mailman, to create a central trusted DB which watched subscription trends? 1. It could be used for security. 2. It could fight spammers on the mailman front. 3. If we deal with the security and privacy implications of the first two, or want a constructive cause--collect cool trends and provide with a mailing lists index by tag words and activity. Think technorati.. This of course, is just a neat idea. Thoughts? Thanks, Gadi. -- 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/japruim%40raoset.com Security Policy: http://wiki.list.org/x/QIA9 -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 11287 James St Holland, MI 49424 www.raoset.com [EMAIL PROTECTED] -- 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/zipfel%40greenacrestechnology.com 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
[Mailman-Users] Updated mmfold.py
A long time ago I wrote a small Python script to allow me to easily manage
held messages for a number of Mailman-managed mailing lists. It worked well
for me, but was still a bit cumbersome because it required me to enter the
admin or moderator password for each list. I fixed that a few days ago,
allowing urls to include the admpw parameter, e.g.:
http://mail.python.org/mailman/admindb/list1?admpw=XYZABC
This makes it *much* easier to use. I can now run through the held messages
in 11 Python-related lists in less than a minute (most lists don't actually
have any held messages) with a shell function like this:
function mmcheck {
for url in \
http://mail.python.org/mailman/admindb/list1?admpw=XYZABC \
http://mail.python.org/mailman/admindb/list2?admpw=ABCXYZ \
http://mail.python.org/mailman/admindb/list3?admpw=FOOBAR \
http://mail.python.org/mailman/admindb/list4?admpw=BARFOOD \
...
; do
python ~/tmp/py/mmfold.py $url
done
}
The output looks like this:
% mmcheck
no messages await review for spambayes
no messages await review for spambayes-dev
2 items sent to browser for review
no messages await review for python-3000
no messages await review for python-mode
no messages await review for pydotorg
no messages await review for python-dev
1 items sent to browser for review
1 items sent to browser for review
no messages await review for csv
1 items sent to browser for review
Only those lists with pending messages generate pages in my web browser.
Just wait for the function to finish and then visit the resulting pages
(generally each will pop up in a separate tab, though I suspect that depends
on your default browser).
Unless you're running this on a shared machine there should be little risk
in recording list passwords in a file. (If you manage several lists you
probably have them recorded online somewhere anyway.)
The updated mmfold.py script is here:
http://www.webfast.com/~skip/python/mmfold.py
Let me know if you have any questions or comments.
--
Skip Montanaro - [EMAIL PROTECTED] - http://www.webfast.com/~skip/
--
ELON MUSK: If fuel cells were good, don't think you'd see them somewhere, like
maybe in a laptop or a cell phone or a $200 million military satellite maybe?
And yet, where do you see them?
SPENCER MICHELS: You don't.
ELON MUSK: Exactly.
--
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] mailman servers coordination: find spammers
Gadi, I think we could certainly do this, but we would need to carefully vette the subscriptions to try to keep the more advanced spammers from sneaking in. Feel free to discuss this with me offline, if you like. -- Brad Knowles Sent from my iPhone On Jul 14, 2008, at 10:25 AM, Gadi Evron [EMAIL PROTECTED] wrote: I often see addresses popping up and subscribing to all visible lists on my servers. Sometimes they're a curious individual, and most times they are spammers harversting addresses (as these are open only to admin). I wonder what the coding price would be, if it can even work with mailman, to create a central trusted DB which watched subscription trends? 1. It could be used for security. 2. It could fight spammers on the mailman front. 3. If we deal with the security and privacy implications of the first two, or want a constructive cause--collect cool trends and provide with a mailing lists index by tag words and activity. Think technorati.. This of course, is just a neat idea. Thoughts? Thanks, Gadi. -- 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/brad%40shub-internet.org 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] Feature Request: Selective Mass Subscription
Hi there, Stephen J. Turnbull: This is a market to gain for Mailman but it currently lacks a few features to do that. Well, my post is slowly getting off topic But IMO it would be quite on-topic for mailman-developers. This kind of post would be more effective in inciting dev activity if more focused. Eg, rather than talking about markets to gain, which sounds good but generally doesn't attract a lot of dev effort, talk about specific tasks and their needs, and the specific features that could be extended or added to satisfy them. Remember, AIUI at least, the devs have little experience with these usages so concrete details of requirements would be very helpful. You're absolutely right, but given that I cannot really sponsor new Mailman features I felt not quite an appropriate person to suggest them. I am trying to give some of my time to handle Polish translation of Mailman but this is about all I can give to this project. If there's a space to do so and people willing to discuss what it would take to make Mailman more marketing-wise friendly tool, I'd be happy to contribute. :) Kind regards, -- Zbigniew Szalbot www.LCWords.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 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] Deleting Mailman Mbox
Mark Sapiro writes: I have no idea how this happened. I suspect somehow instead of mailman.mbox/mailman.mbox being a file, it somehow became a link back to its parent. If this is the case, even rm -rf /var/lib/mailman/archives/mailman.mbox may not succeed because it may loop indefinitely, but it's worth a try. Also try rm -f /var/lib/mailman/archives/mailman.mbox/mailman.mbox (no -r option), which should work if the target is a symlink. -- 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] Can't create list
On Mon, Jul 14, 2008 at 07:04:46PM -0700, Mark Sapiro wrote: Put the following in mm_cfg.py DEFAULT_URL_HOST = 'vidiot.com' DEFAULT_EMAIL_HOST = 'vidiot.com' Those two lines were there. VIRTUAL_HOSTS.clear() Don't see this mentioned in the Defaults.py file. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) Missed this being described in the Defaults.py file. Thanks for pointing it out. We'll see how far I get tomorrow. MB -- e-mail: [EMAIL PROTECTED]/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- 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] honeypot lists Re: mailman servers coordination: find spammers
On Mon, 14 Jul 2008, Krystal Zipfel wrote: The problem I see with this is much like the DNSBLs and Block lists (spamhaus?). As Jason put it, one person's spam could very much be another person's ham, so mail starts getting rejected by those who outright trust such a database and it is hell trying to get removed from those said lists. Not to mention, there is so much forgery and many changes to spam tricks that even SA has to keep up with it. :-( Personally, I think spam filtering/watching/fighting should be done per server, per user, etc. Would be real nice if the ISP's would start doing that... My opinion. :-) Well, one immediate solution that helps is starting another list or two, as a honeypot, and seeing who subscribes. Gadi. Jason Pruim wrote: First, I think it would have better luck on the developers mailing list :) But as for the idea, I think it could work, but someone would have to provide the hosting for the database that would hold all the info. And we would have to figure out who would be a trusted source to report the spam My spam might be your ham... I need lunch hehe In general though I like the idea and would love to hear from others on it as well :) On Jul 14, 2008, at 1:25 PM, Gadi Evron wrote: I often see addresses popping up and subscribing to all visible lists on my servers. Sometimes they're a curious individual, and most times they are spammers harversting addresses (as these are open only to admin). I wonder what the coding price would be, if it can even work with mailman, to create a central trusted DB which watched subscription trends? 1. It could be used for security. 2. It could fight spammers on the mailman front. 3. If we deal with the security and privacy implications of the first two, or want a constructive cause--collect cool trends and provide with a mailing lists index by tag words and activity. Think technorati.. This of course, is just a neat idea. Thoughts? Thanks, Gadi. -- 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/japruim%40raoset.com Security Policy: http://wiki.list.org/x/QIA9 -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 11287 James St Holland, MI 49424 www.raoset.com [EMAIL PROTECTED] -- 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/zipfel%40greenacrestechnology.com 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/ge%40linuxbox.org 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] Can't create list
Mike Brown wrote: I tried it from work and got the same problem, virtual host unknown: vidiot.com Then vidiot.com is not a url host in the VIRTUAL_HOSTS dictionary. Put the following in mm_cfg.py DEFAULT_URL_HOST = 'vidiot.com' DEFAULT_EMAIL_HOST = 'vidiot.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) -- 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://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] Deleting Mailman Mbox
Carlos Williams wrote: So I think I am simply going to just rm -rf /var/lib/mailman/archives/private/mailman.mbox/mailman.box This will retain the first mailman.box directory which is expected to be there and then remove everything beyond that. I will then assume at some point Mailman will attempt to re-generate a mailbox.mbox file in that directory. Do you think this is a bad idea? No. I think it is a good idea. -- 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://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
