[Mailman-Users] Re: Search box for archives
On 9/11/22 2:00 AM, Odhiambo Washington wrote: What is the simplest way to add a searchbox for the archives? Because my list archives are open and regularly crawled, I tell my user to just use their favorite search engine, enter the list name, and the term they're looking for. You could probably code a simple form to do that for you. I had considered MonHarc back in the day, but never got around to implementing it. And since it's probably not secure these days (see previous message in this thread) I'm glad I didn't. -- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108 -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
Re: [Mailman-Users] Migrating a list to a new email address
Mark's fix: If your Mailman is at least 2.1.16, all you need to do is set SUBSCRIBE_FORM_SECRET = 'Some string unique to your site in mm_cfg.py, and that attack will no longer work. Is working fine. But thanks for the alternative suggestions. I've got a copy of fail2ban ready to install but just haven't had time to configure it yet. On Wed, May 20, 2015 at 9:07 AM, Adam McGreggor adam-mail...@amyl.org.uk wrote: On Wed, May 20, 2015 at 02:38:01PM +0100, David Osborne wrote: On 15/05/15 05:32, Bill Christensen wrote: I long ago routed real users to an alternative signup, but the spam keeps coming, unrelenting, and are now anywhere between 1k and 10k per day. One of our lists was spammed in a similar way. The approach I took was to configure Apache to allow requests to /mailman/subscribe only when the referring page was on our server: I've used mod_security/fail2ban in the past, both work as well as might be expected. […] This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Hum. -- Celebrity can be malign in that it becomes a form of idolatry, and people live their lives vicariously through the rich and famous rather than attending to their own lives. -- John Sentamu -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: list
Great! I fixed the list name uppercase problem and enough of the permissions and group assignments to get things running again last night. I still need to comb through and make sure that everything that's supposed to be is in the Mailman group, but that'll happen soon and the other major lists we run continue to work as intended. Thanks for your help! On Mon, May 18, 2015 at 11:07 PM, Mark Sapiro m...@msapiro.net wrote: On 05/17/2015 10:14 PM, Bill Christensen wrote: On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro m...@msapiro.net wrote: If this is a one-time occurrence, It was just a glitch. Maybe someone manually ran cron/gate_news as a user not in Mailman's group. If you get these every 5 minutes, there is a permissions issue, probably with the user running this cron not being mailman, because if the locks directory were not group mailman and group writable, lots more would be broken. Yes, definitely every 5 minutes. There is a permissions issue on the locks directory. If you do ls -la /opt/local/var/mailman/locks/ you should see something similar to drwxrwsr-x 2 rootmailman 4096 May 18 20:11 . drwxrwsr-x 9 rootmailman 4096 May 10 2008 .. -rw-rw-r-- 2 mailman mailman 62 May 19 2015 master-qrunner -rw-rw-r-- 2 mailman mailman 62 May 19 2015 master-qrunner.host.pid There may or may not be other files, but the two master-qrunner files should be there and everything should be mailman's group (owner is not important) and both . and .. should have permissions as shown. If all this is correct, then either cron/gate_news is not running as the Mailman user (where is its crontab and what's in it?) or there may be some SELinux, apparmor or other security policy issue. date post(12068): post script, list not found: listname The post script invoked by /path/to/mailman/mail/mailman post listname in your fetchmail script says listname doesn't exist. Mailman mischief log says: Hostile listname: listname This is consistent with the 'post script' report and says that listname contains one or more characters not in the Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The default setting only allows letters, digits, '-', '+', '_', '.' and '='. Does listname contain characters outside this set or whatever set you've specified? Nope, it's four uppercase letters. No spaces, no punctuation. List names are always all lower-case. The list may have a real_name attribute which is mixed case but it must differ only in case from the list's internal name. The name in the pipe to 'mailman/mail/mailman post listname' command MUST be all lower case. I checked the messages waiting in Gmail. They're all small enough, no worrisome attachments or anything. I tried marking the oldest as read just in case it was jamming up the works, but the others are still in a logjam. Because fetchmail can't deliver to the list until you fix the listname you pass to the 'mailman' wrapper if that's the issue. Yes, there are still 5 messages waiting in Gmail. Fetchmail apparently hasn't marked them as read as it can't put them anywhere. Yes. As far as I can tell, the list name is correct. I checked bin/list_lists /etc/aliases /etc/postfix/virtual /etc/fetchmailrc and ran sudo newaliases it was lower case in a few places, so I changed those to upper case to match, just in case. That was the reverse of what you should have done. Hopefilly, the name of the list's directory in the /opt/local/var/mailman/lists/ directory is all lower case. It must also be all lower case in fetchmailrc and in the commands in /etc/aliases. I.e. an alias could be LISTNAME: '|/path/to/mailman/mail/mailman post listname' LISTNAME-admin: '|/path/to/mailman/mail/mailman admin listname' But it should match /etc/postfix/virtual, but it's best if it's all lower case. But then if fetchmail is delivering directly to /path/to/mailman/mail/mailman, none of the postfix stuff matters as it isn't used. then stopped/started Mailman. No change. I decided to take a chance and used your clone_list script to make a copy, moved the original archives to a backup location, then removed the original list and cloned back from the copy to the original name. Ran check_perms -f and checked them manually as well. All looks correct. And yet, it's still throwing the same errors. One improvement - after correcting permissions manually on listname.mbox/listname.mbox I can get to the archives again. They were -rw-rw-r-- 1 root staff and I set them to -rwxrwxr-x 1 root staff to match other working lists with public archives. It's a file. +x is not necessary on files. archives/private/listname.mbox should be drwxrwsr-x (note the SETGID), but no x of the file is needed (it's not executable). And I hope listname is all lower case. Also, it appears
Re: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: list
On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro m...@msapiro.net wrote: On 05/17/2015 01:58 PM, Bill Christensen wrote: I'm using Gmail for all our email addresses, and pulling the mail into Mailman using Fetchmail. It's been working fine for years. One of my more important lists recently started getting this in the Fetchmail console: post script, list not found: listname fetchmail: Error writing to MDA: Broken pipe and the Mailman error log says: date gate_news(12061): IOError : [Errno 13] Permission denied: '/opt/local/var/mailman/locks/gate_news.lock.site FQDN.12061.0' This is probably not related. Do you even have any lists with Mail-News gateways - gateway_to_mail = Yes?. Mailman's cron/gate_news runs by default every five minutes and does use this lock to prevent concurrent updates. I would also expect to see entries like 'Could not acquire gate_news lock' in the fromusenet log. No news gateways. If this is a one-time occurrence, It was just a glitch. Maybe someone manually ran cron/gate_news as a user not in Mailman's group. If you get these every 5 minutes, there is a permissions issue, probably with the user running this cron not being mailman, because if the locks directory were not group mailman and group writable, lots more would be broken. Yes, definitely every 5 minutes. date post(12068): post script, list not found: listname The post script invoked by /path/to/mailman/mail/mailman post listname in your fetchmail script says listname doesn't exist. Mailman mischief log says: Hostile listname: listname This is consistent with the 'post script' report and says that listname contains one or more characters not in the Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The default setting only allows letters, digits, '-', '+', '_', '.' and '='. Does listname contain characters outside this set or whatever set you've specified? Nope, it's four uppercase letters. No spaces, no punctuation. In the smtp-failure log I'm seeing Message size exceeds fixed limit In General Options = Maximum length in kilobytes (KB) of a message body. Use 0 for no limit. I have '0'. These two things are unrelated. The message in smtp-failure says Mailman attempted to send a message which was larger than the MTA would accept. In Postfix for example, this is the main.cf parameter message_size_limit. Ok. I checked the messages waiting in Gmail. They're all small enough, no worrisome attachments or anything. I tried marking the oldest as read just in case it was jamming up the works, but the others are still in a logjam. I've run the check permissions script ( with -f), it changes nothing. It appears that there are 5 messages waiting for delivery, though I don't see them in any of the queues. If Mailman is retrying the smtp-failure, the message would be in Mailman's 'retry' queue until Mailman eventually gives up. Or, they could be still in the gmail inbox since fetchmail probably wouldn't delete them as it couldn't deliver them. Yes, there are still 5 messages waiting in Gmail. Fetchmail apparently hasn't marked them as read as it can't put them anywhere. This appears to have started around the time that I upgraded from Mailman 2.1.17 (or so) to 2.1.20 That list is also not archiving properly, so it clearly has problems The listname problem would mess up a lot, but it looks like there would be nothing to archive since nothing for that list is getting posted. Makes sense. All the other lists on the server are working fine as far as I can tell. Any ideas as to what's wrong? First, what's the list name? Once you fix that issue, that may be all, or there may be shunted messages in Mailman's shunt queue to be unshunted. As far as I can tell, the list name is correct. I checked bin/list_lists /etc/aliases /etc/postfix/virtual /etc/fetchmailrc and ran sudo newaliases it was lower case in a few places, so I changed those to upper case to match, just in case. then stopped/started Mailman. No change. I decided to take a chance and used your clone_list script to make a copy, moved the original archives to a backup location, then removed the original list and cloned back from the copy to the original name. Ran check_perms -f and checked them manually as well. All looks correct. And yet, it's still throwing the same errors. One improvement - after correcting permissions manually on listname.mbox/listname.mbox I can get to the archives again. They were -rw-rw-r-- 1 root staff and I set them to -rwxrwxr-x 1 root staff to match other working lists with public archives. Then I looked at mailman/lists/. The list in question was owned by my user, not root like the rest of them (possibly a result of clone list? the only two with that user were this list and the clone I had made earlier). Changed that to match the rest
[Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: list
Mark, Adding the line SUBSCRIBE_FORM_SECRET = 'Some string unique to your site in mm_cfg.py definitely made a huge difference to the spam registration problem I was having. Looks like I may not need to migrate the list to a new address after all. One more problem to solve. I'm using Gmail for all our email addresses, and pulling the mail into Mailman using Fetchmail. It's been working fine for years. One of my more important lists recently started getting this in the Fetchmail console: post script, list not found: listname fetchmail: Error writing to MDA: Broken pipe and the Mailman error log says: date gate_news(12061): IOError : [Errno 13] Permission denied: '/opt/local/var/mailman/locks/gate_news.lock.site FQDN.12061.0' date post(12068): post script, list not found: listname Mailman mischief log says: Hostile listname: listname In the smtp-failure log I'm seeing Message size exceeds fixed limit In General Options = Maximum length in kilobytes (KB) of a message body. Use 0 for no limit. I have '0'. I've run the check permissions script ( with -f), it changes nothing. It appears that there are 5 messages waiting for delivery, though I don't see them in any of the queues. This appears to have started around the time that I upgraded from Mailman 2.1.17 (or so) to 2.1.20 That list is also not archiving properly, so it clearly has problems All the other lists on the server are working fine as far as I can tell. Any ideas as to what's wrong? -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migrating a list to a new email address
Excellent. I didn't know about the clone_list script. On 5/15/15 12:21 AM, Mark Sapiro wrote: Privacy options... - Subscription rules - subscribe_policy st to Require approval and then discard all requests. when you say discard all requests, is there a way to do that automatically? Without email notices to the owner address? -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Migrating a list to a new email address
Hi all, I have a long running list with thousands of subscribers that needs to move to a new set of email addresses. The existing list is announce-only, so doesn't get a whole lot of traffic - typically at most a few outgoing emails a year. But some time back a bot started sending spam registrations via hits to the web server in the form domain name /mailman/subscribe.cgi/bwbnewsletter?email=bogus_registrant@somedomain.tldmailto:ruanwe...@hotmail.comfullname=pw=123456789pw-conf=123456789language=endigest=0email-button=Subscribe. I long ago routed real users to an alternative signup, but the spam keeps coming, unrelenting, and are now anywhere between 1k and 10k per day. I'm thinking that the best way to deal with this is to move everything, including the archives, to a newly created list on the same domain name. The alternative signup method i've set up works, so if i set the new list to Advertise this list... = NO in Privacy, I'm hoping the spammers won't figure out that the new mailman list exists. I could also set it up as a closed list if that's possible since the new registrations will be entered manually in bulk, though I don't see any settings which disallow all subscriptions. So I'd like confirmation on how to move a list to a new address under the same domain. I figure I need to: 1) take a backup copy of the oldlistname.mbox file in /archives/private 2) take a copy of the current subscriber list (already done using the list_members command) 3) create the new list, aliases, etc and associated email addresses 4) remove /archives/private/newlistname.mbox 5) rename oldlistname.mbox to newlistname.mbox 5b) do I need to replace all instances of oldlistname with newlistname everywhere they occur in the .mbox file? Would doing so cause any problems? 6) rebuild the archives 7) test the new list 8) bulk subscribe the subscriber list to newlistname 9) delete the old list Did I miss anything? Thanks in advance. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Cron command?
Hi all, I recently updated and my digests stopped going out (I was able to push out the waiting digest manually by doing /opt/local/share/mailman/cron/senddigests so I know the function is working). My old notes tell me the command for cron is: sudo /opt/local/share/mailman/cron/crontab -u mailman crontab.in I also tried sudo /opt/local/share/mailman/cron -u mailman crontab.in since that appears to be the current location of crontab.in but that's getting me 'command not found' and cron: illegal option -- u usage: cron [-s] [-o] [-x debugflag[,...]] debugflags: ext sch proc pars load misc test bit Any ideas on this? -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The right way to reply to a mailing list
On 3/20/15 8:52 AM, Tanstaafl wrote:
On 3/19/2015 6:47 PM, Lindsay Haisley fmo...@fmp.com wrote:
In many mail user agents, when you press the Reply button the program
will analyze the headers, determine that the post being replied to came
from a list and offer a Reply to List option in addition to a simple
reply, which generally goes privately to the original poster.
I'd really like to know which email user agents really do this.
In my experience, none of the ones used by 99+% of the worlds population
actually use do this.
Thunderbird. ('Reply to list' for listservs, 'Reply all' if more than
one recipient in a non-list conversation)
Others like Gmail will offer 'reply all' if there's more than one
recipient.
And what you get when you hit 'reply' will depend on what the list sets
as the reply-to address. In Mailman we have the option of setting it to
the list address OR the sender. Some of mine go to sender (typically
lists whose participants tend to go far off topic frequently), some go
to the list.
A couple of quick rules of thumb I use for responses: If I can answer
an original question definitively in one or two lines and it's not
likely to spark a long thread, I will top post.
Otherwise, I most often use the trim-and-interleave, or if it makes
sense (as in this post), bottom posting. In general, follow the
convention most used in the list or conversation in question.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archiving problems
On 1/26/15 11:27 PM, Mark Sapiro wrote: On 01/26/2015 09:12 PM, Bill Christensen wrote: All the archives work when in private state. But I had to manually change the owner of all the publicly available list archives to _www in private in order for them to be readable. Otherwise they get a big Forbidden message. Should *all* the lists be _www? Everything in archives/private, or just the archive folders and not the mbox folders? The archives/private folder itself is already _www. Thanks for your continued tolerance and assistance. For public archives to work, the web server needs to be able to search the archives/private directory that the archives/public/ symlinks point into. Normally this only requires that the archives/private/ directory itself, not any subordinates, be either o+x or owned by the web server user. The subordinate LISTNAME and LISTNAME.mbox directories are normally rwxrwsr-x and Mailman's group so Mailman can read and write them and subordinates will be created in Mailman's group and the web server can read and search them. It's only archives/private itself which is in Mailman's group and either rwxrws--x or if rwxrws---, owned by the web server user. Otherwise, ownership doesn't matter. See http://www.list.org/mailman-install/node9.html. Well, I had it all working on Monday night. I got a report today that someone was getting Forbidden again. The owner of the list in question (and only that one list, not any of the other publicly archived lists - which have not seen any posts in the last two days) had changed back from _www to root. CHOWNing it back to _www again brings up the archive, but then it was only showing the last two days worth of archives (owner of those posts: _mailman, the rest were root). Rebuilding the archives with --wipe and running Check perms -f (which is already cron jobbed to run every night) made the rest of them visible again. What do i need to do so that I don't have to jump these hoops daily? Thanks yet again. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archiving problems
On 1/25/15 7:27 PM, Mark Sapiro wrote: On 01/25/2015 05:21 PM, Stephen J. Turnbull wrote: Mark Sapiro writes: The solution is simple: rm -r archives/private/* You mean rm -r archives/public/*, don't you? As given it erases all the data, no? Oh My yes! Absolutely! I hope nobody does the former. Thanks for catching this Steve. Ok, I removed the public archives. I didn't rm -r, just copied them elsewhere in case this didn't work. Our digest goes out at noon (and did). I assume that qualifies as the next time it does anything to the list. Four new messages went through the list since then as well. The public archive folder didn't rebuild. Tail on the error log says: mlist.Save() File /opt/local/share/mailman/Mailman/MailList.py, line 574, in Save self.CheckHTMLArchiveDir() File /opt/local/share/mailman/Mailman/Archiver/Archiver.py, line 241, in CheckHTMLArchiveDir makelink(privdir, pubdir) File /opt/local/share/mailman/Mailman/Archiver/Archiver.py, line 49, in makelink os.symlink(old, new) OSError: [Errno 2] No such file or directory Your thoughts? FYI, this is on Mac 10.9.5, non-server version, if that makes any difference. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archiving problems
On 1/26/15 9:32 PM, Mark Sapiro wrote: On 01/26/2015 06:08 PM, Mark Sapiro wrote: You weren't supposed to remove/move archives/private, just the subordinate listname directories. And once again, I misspoke (mistyped). I again meant the subordinate listname directories under archives/public, not archives/private. Mailman expects archives/public to exist, but the subordinates which are supposed to be symlinks into archives/private are checked and added/removed if necessary each time the list object is saved because the list's archive_private setting might have changed necessitating the addition or removal of symlinks. Ok. I put the archives/public folder back. Toggling the archives setting on the publicly archived lists from public to private and back again created the symlinks. So far so good. All the archives work when in private state. But I had to manually change the owner of all the publicly available list archives to _www in private in order for them to be readable. Otherwise they get a big Forbidden message. Should *all* the lists be _www? Everything in archives/private, or just the archive folders and not the mbox folders? The archives/private folder itself is already _www. Thanks for your continued tolerance and assistance. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Archiving problems
Hi folks, I recently discovered that all my lists stopped archiving back in October. I have no clear idea as to what caused that, but I suspect that it may have occurred as part of some hardware and software upgrades I did around that time. I'm still stuck back at Mailman 2.1.13 because the port system I use hasn't updated in ages and I haven't had time to tackle it myself. I was able to bring most of the archives up to date manually, but one fairly active one with public archives is still only showing through October 2014. When I run that manually it shows that it's processing posts beyond the last one seen in the web-visible archives and updates the index for 1st quarter 2015, but still no visibility and the files in archive/public aren't updated. The files in archive/private *are* updated... How do I make the public archives reflect what's in private? Thanks. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] OS X Question --- yes I know sigh
The MacPorts version works - I've been using it for years - but note that it's a good number of dot-revisions behind the current Mailman version, which is at least 2.1.18 and has some fixes I'd like to see. Unfortunately, nobody's actively maintaining the port. I thought about doing it myself, but my combination of day job and side job doesn't allow me the time to do a lot of deep work learning how to do things like that. On 11/24/14, 8:55 PM, Ed Ravin wrote: On Sun, Nov 23, 2014 at 04:54:09PM -0700, David Dodell wrote: Hi, I know from past experience that the OS X version of Mailman is met with some contempt because of what Apple did with it .. but I have it working well for several years on a 10.7.5 Lion Server, and it has been very stable. Note that there's also a version from MacPorts: $ port list mailman mailman@2.1.13 mail/mailman [this is on my Mountain Lion box, your mileage may vary] -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Group mismatch again.
On 7/11/14 6:26 PM, Mark Sapiro wrote: On 07/10/2014 11:13 AM, Bill Christensen wrote: The setup: Moving from Mac OS 10.8.5 to 10.9.4, on a MAMP setup, everything installed using MacPorts. Upgrading MySQL, PHP, and PostgreSQL in the process. MacPorts hasn't upgraded Mailman beyond 2.1.13 (a separate issue I may want to address later). Right now I'm doing test runs on a backup to make sure all the pieces and parts will work properly when I do the update for real. I have all the other parts in place but I'm now getting the dreaded group mismatch error from Mailman. When I first installed everything I installed Mailman before PostgreSQL, and the feedback told me that I needed either to compile Mailman as --with-mail-gid=postgresql or change the mail server (standard Mac installation of Postfix) to run as group _mailman. I uninstalled and reinstalled Mailman and now it's telling me that I need to compile Mailman as --with-mail-gid=staff. I changed the setting in MacPorts' file from --with-mail-gid=_mailman to --with-mail-gid=staff and attempted to reinstall, but I'm getting an error that it's Unable to open port - invalid command name '--with-mail-gid=staff'. Anyone have any ideas of where to go from here? This is really an Apple issue, at least the way you're going about it. Have you asked Apple? However, you say you (only) changed --with-mail-gid=_mailman to --with-mail-gid=staff, and whereas the install worked with --with-mail-gid=_mailman, after the change it complains invalid command name '--with-mail-gid=staff'. I really know nothing about the OS X server Mailman or even where you made that change, but in 'standard' Mailman that would be an option to configure and configure would never make that exact complaint. Are you sure you didn't introduce an extraneous newline or similar that would cause --with-mail-gid=staff to be interpreted as a command rather than an option to a prior command? Figured it out. It was syntax problems: First, I had added a comment as a note to myself within the configure_args block, so that if I needed to revert I'd have the exact line. I should have known not to put it in the block. After I moved the comment to before the block, I left the comment with a trailing \, as that was at the end of the original line. Unfortunately, that threw things off also. Removing the \ got the installation working correctly and it's now up and running. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Group mismatch again.
Hey folks, I'm doing an upgrade/reinstall on one of my servers, and when I put Mailman back on I'm getting a group mismatch error. It's happened to me before, but I don't remember the exact procedure to make it work properly. The setup: Moving from Mac OS 10.8.5 to 10.9.4, on a MAMP setup, everything installed using MacPorts. Upgrading MySQL, PHP, and PostgreSQL in the process. MacPorts hasn't upgraded Mailman beyond 2.1.13 (a separate issue I may want to address later). Right now I'm doing test runs on a backup to make sure all the pieces and parts will work properly when I do the update for real. I have all the other parts in place but I'm now getting the dreaded group mismatch error from Mailman. When I first installed everything I installed Mailman before PostgreSQL, and the feedback told me that I needed either to compile Mailman as --with-mail-gid=postgresql or change the mail server (standard Mac installation of Postfix) to run as group _mailman. I uninstalled and reinstalled Mailman and now it's telling me that I need to compile Mailman as --with-mail-gid=staff. I changed the setting in MacPorts' file from --with-mail-gid=_mailman to --with-mail-gid=staff and attempted to reinstall, but I'm getting an error that it's Unable to open port - invalid command name '--with-mail-gid=staff'. Anyone have any ideas of where to go from here? I'd rather not do a direct download/compile of Mailman if possible, as MacPorts spreads the pieces and parts into a number of directories and I'd probably have a heck of a time getting all the paths working correctly again. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
Thanks.
Running the patch I got:
patching file /path/to/mailman/Mailman/Cgi/subscribe.py
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 53 with fuzz 1 (offset -1 lines).
(with the actual path in there)
When trying to run a subscription I got the We hit a bug error.
Error log says (among other stuff):
admin(12818): File /opt/local/share/mailman/Mailman/Cgi/subscribe.py,
line 56
if listname = 'problem_list':
^
SyntaxError: invalid syntax
where 'problem_list' had been replaced by the actual list name.
The same happens on other lists as well.
Comparing subscribe.py with subscribe.py.bak, it appears that it's in there
as written.
Any ideas?
On Tue, May 13, 2014 at 5:10 PM, Mark Sapiro m...@msapiro.net wrote:
On 05/13/2014 12:54 PM, Bill Christensen wrote:
Sorry to be dense, but how do I apply that patch?
1)Save the patch to a file.
2)Edit the file with an editor that won't change indentation or wrap or
fill lines, i.e. a text editor, not a word processor, and change
problem_list in the line
+if listname = 'problem_list':
to the all lower case name of the list. If you wanted to apply it to a
few, but not all lists, you could change the line to something like
+if listname in ('problem_list', 'list2', 'list3'):
Note that the quotes around the literal list names are important, but
there are no quotes around the variable listname.
3) Give the command
cp /path/to/mailman/Mailman/Cgi/subscribe.py
/path/to/mailman/Cgi/Mailman/subscribe.py.bak
(all on one line)
4) Give the command
patch /path/to/mailman/Cgi/Mailman/subscribe.py /path/to/edited/patch
(all on one line)
5) Go to a URL like http://your.server/Mailman/subscribe/problem_list
Note you don't need to restart Mailman first as this patch only affects
web accesses which are always new CGI processes.
The possible results are:
1) A page that says
Error
Web subscribe not allowed /problem_list/
This says all is good.
2) A page that says
problem_list Subscription results
You must supply a valid email address.
This says the patch wasn't applied or for some other reason (maybe
problem_list not changed or misspelled) isn't working.
3) a page that says
...
We hit a bug.
...
This says there is something broken in the patched module. You can leave
it broken which will disable all subscribes or maybe only problem_list
subscribes depending on the exact error, or you can copy the
subscribe.py.bak file from step 3) back over subscribe.py.
In any case, Mailman's error log will have an exception and traceback
from what went wrong.
--
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
https://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:
https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
On 5/14/14 10:35 AM, Mark Sapiro wrote: Sorry, that's my mistake. It should be if listname == 'problem_list': i.e., ==, not =. Comparing subscribe.py with subscribe.py.bak, it appears that it's in there as written. I was wondering about that. Thanks. Now the problem_list is disallowed from web subscriptions and the other lists are allowed and working properly. The problem_list gets we hit a bug, but since I've taken the subscription form off the listinfo page the only ones who will get that are the spammers. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
Here you go:
admin(38814): [- Traceback --]
admin(38814): Traceback (most recent call last):
admin(38814): File /opt/local/share/mailman/
scripts/driver, line 112, in run_main
admin(38814): main()
admin(38814): File /opt/local/share/mailman/Mailman/Cgi/subscribe.py,
line 63, in main
admin(38814): syslog('vette', 'subscribe: Forbidden list %s: %s\n',
listname, e)
admin(38814): UnboundLocalError: local variable 'e' referenced before
assignment
admin(38814): [- Python Information -]
(sorry, accidentally hit reply instead of reply list)
On Wed, May 14, 2014 at 6:52 PM, Mark Sapiro m...@msapiro.net wrote:
On 05/14/2014 10:42 AM, Bill Christensen wrote:
The problem_list gets we hit a bug, but since I've taken the
subscription form off the listinfo page the only ones who will get that
are the spammers.
It shouldn't get that. There is still something wrong with the patch or
its application. If you post the traceback from the error, I'll see what
it is.
--
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
https://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:
https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual Mailman broke!
Do you have the virtual domains listed at the end of
../mailman/mailman/mm_cfg.py ?
Something like:
DEFAULT_EMAIL_HOST = '103.greenbuilder.com'
DEFAULT_URL_HOST = '103.greenbuilder.com'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('builderswithoutborders.org','builderswithoutborders.org')
That should take the bytesmith domain out of the mix.
On Wed, May 14, 2014 at 6:26 PM, Jan Steinman j...@bytesmiths.com wrote:
I'm using the Mailman and postfix that came bundled with MacOS X 10.6
(Snow Leopard) on a Mac Mini Server.
I have problems adding new lists using the web interface. It's been a
problem forever, but I've forgotten the magic fixes to magic files that
I've done in the past to correct it.
I have a number of small non-profits that I host websites for, and each
has one or more Mailman lists. I run my own DNS and MTA using the domain
bytesmiths.com. All these virtual domain lists were working, until I
added a new list to one of them. It failed to accept the new mailman list
address after adding the new list through the Mailman web interface.
So then I started poking around, and noticed the new list did not appear
like other functioning lists in /var/mailman/data files. I carefully added
the new list by editing aliases and virtual-mailman files that warned
ominously do not edit! and ran newaliases(1). I verified that the .db
files are newer than the edited text files.
Well, now NONE of my virtual domains work any more. They fail by
redirecting to the base domain. For example, mail to new list
gl...@virtualdomain.org -- previously working -- fails with a bounce
that gl...@bytesmiths.com doesn't exist.
Rather than deluge you with config files and error logs, I thought I'd
post the symptoms first, to see if anyone could point me in the right
direction, or could request specific config/log info.
My gratis customers are being very understanding, given the vast amounts
they are paying me, but needless to say, I'd like to get them back up ASAP!
Does anyone know what's going on, and how to fix it? What additional
information can I provide?
Thanks in advance for any advice offered!
No, Plaintiffs to not have a fundamental right to own and use a dairy
cow or a dairy herd... No, Plaintiffs do not have a fundamental right to
consume the milk from their own cow... No, Plaintiffs do not have a
fundamental right to produce and consume the foods of their choice... --
Patrick J. Fiedler
Jan Steinman, EcoReality Co-op
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
That did the trick.
Thanks again.
On Wed, May 14, 2014 at 11:39 PM, Mark Sapiro m...@msapiro.net wrote:
On 05/14/2014 07:58 PM, Bill Christensen wrote:
Here you go:
admin(38814): [- Traceback --]
admin(38814): Traceback (most recent call last):
admin(38814): File /opt/local/share/mailman/
scripts/driver, line 112, in run_main
admin(38814): main()
admin(38814): File /opt/local/share/mailman/Mailman/Cgi/subscribe.py,
line 63, in main
admin(38814): syslog('vette', 'subscribe: Forbidden list %s: %s\n',
listname, e)
admin(38814): UnboundLocalError: local variable 'e' referenced before
assignment
admin(38814): [- Python Information -]
My apologies again. The line
syslog('vette', 'subscribe: Forbidden list %s: %s\n', listname,
e)
should be
syslog('vette', 'subscribe: Forbidden list %s', listname)
Again, I apologize for posting an untested so simple, how can it be
wrong patch. sorry for the confusion.
--
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
https://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:
https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
I finally got a chance to look over the logs today; this is a widely distributed attack, so address blocking is probably futile. Sorry to be dense, but how do I apply that patch? Thanks On Fri, May 9, 2014 at 3:19 PM, Mark Sapiro m...@msapiro.net wrote: On 05/09/2014 12:12 PM, Bill Christensen wrote: Is there a way that I can just have it affect this one problematic list? If I change the name of cgi-bin/subscribe and any references to it (at least until the next update), do you think that will make a difference? It seems to me the easiest way to do this is to apply the attached patch to Mailman/Cgi/subscribe.py. Change problem_list to the actual list name and if you don't want the logging, remove the syslog line. But as others have suggested, look at your web server logs (or the subscribe confirmation emails) to get the IP address(es) that are submitting them. If they all come from a single IP or netblock, block that with iptables or whatever firewall you have. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
Very wide. Vietnam, China, New York, France just at a quick look. I'm looking into fail2ban now. Thanks to those of you who have mentioned it. On Tue, May 13, 2014 at 3:12 PM, Robert Heller hel...@deepsoft.com wrote: At Tue, 13 May 2014 14:54:26 -0500 Bill Christensen billc_li...@greenbuilder.com wrote: I finally got a chance to look over the logs today; this is a widely distributed attack, so address blocking is probably futile. How widely? It *could* be a /16 subnet (eg distributed over 2^^16 address) somewhere in an 'odd' part of the world (somewhere your potential subscriber base is not likely to be from). Even if it is widely distributed, fail2ban might do what you need. The *worst* the fail2ban would do is make things difficult for a *few* legit subscription requesters. Sorry to be dense, but how do I apply that patch? Thanks On Fri, May 9, 2014 at 3:19 PM, Mark Sapiro m...@msapiro.net wrote: On 05/09/2014 12:12 PM, Bill Christensen wrote: Is there a way that I can just have it affect this one problematic list? If I change the name of cgi-bin/subscribe and any references to it (at least until the next update), do you think that will make a difference? It seems to me the easiest way to do this is to apply the attached patch to Mailman/Cgi/subscribe.py. Change problem_list to the actual list name and if you don't want the logging, remove the syslog line. But as others have suggested, look at your web server logs (or the subscribe confirmation emails) to get the IP address(es) that are submitting them. If they all come from a single IP or netblock, block that with iptables or whatever firewall you have. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/billc_lists%40greenbuilder.com -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com -- Robert Heller -- 978-544-6933 / hel...@deepsoft.com Deepwoods Software-- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
On 5/8/14 12:02 PM, Mark Sapiro wrote: On 05/08/2014 09:31 AM, Bill Christensen wrote: Question 1: Is it possible to reverse the order of approval and confirmation when requiring both? The admin then can reject all those with duplicates, only allowing the (presumably real) single subscription requests to send out a confirmation request. It would require significant code changes. If so, how would that be done? Question 2: Any other suggestions on how to handle this? Currently running mailman 2.1.13_0 (Next stop is to MacPorts list to see if the maintainer will update the port to the latest version) There are mitigations which may help in Mailman 2.1.16. See https://bugs.launchpad.net/mailman/+bug/1082746. Ok, great. I temporarily removed the signup form from the listinfo page in hopes of stemming the tide, and replaced it with a request to use the site's contact form so that we can manually add interested subscribers. I purposely don't have a subscribe email address set up for this list. But somehow they're still coming in - another 1300+ since yesterday. What other holes can I plug? Thanks. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Subscription flood
On 5/9/14 1:25 PM, Mark Sapiro wrote: On 05/09/2014 10:46 AM, Bill Christensen wrote: I temporarily removed the signup form from the listinfo page in hopes of stemming the tide, and replaced it with a request to use the site's contact form so that we can manually add interested subscribers. I purposely don't have a subscribe email address set up for this list. But somehow they're still coming in - another 1300+ since yesterday. They probably aren't using the subscribe form on the listinfo page but rather posting the data directly to the subscribe CGI. Try moving mailman's cgi-bin/subscribe aside to totally disable web subscribe. I expect that will affect my other lists as well, no? Is there a way that I can just have it affect this one problematic list? If I change the name of cgi-bin/subscribe and any references to it (at least until the next update), do you think that will make a difference? -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Subscription flood
Hi all, I've got a problem with one of my lists where it's being flooded with spurious subscription requests. The list was set to require subscription confirmation; the innocent victims whose addresses were used for the subscription requests started complaining, as they'd get anywhere from 2 to 400 (!) confirmation requests in a day from a list they'd never even heard of. About 12 hrs ago I switched it to require Admin approval. 500+ subscription requests - mostly in batches of 5-10 from the same address - have come through since then. I attempted requiring both confirmation and admin approval, but the order of operations is that the admin isn't asked to approve until a confirmation comes through. That's no help to the victims receiving the confirm requests. Question 1: Is it possible to reverse the order of approval and confirmation when requiring both? The admin then can reject all those with duplicates, only allowing the (presumably real) single subscription requests to send out a confirmation request. If so, how would that be done? Question 2: Any other suggestions on how to handle this? Currently running mailman 2.1.13_0 (Next stop is to MacPorts list to see if the maintainer will update the port to the latest version) -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Group mismatch returns.
Recent upgrade borked my setup.
Group Mismatch error once again, and adding the configure line
--with-mail-gid=staff
and removing the line
--with-mail-gid=${mmgroup}
as suggested doesn't fix it.
What to do? How can I keep this from happening whenever I do a major
upgrade/reinstall on my server?
--
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] Group mismatch returns.
On 10/11/11 7:01 PM, Mark Sapiro wrote:
Bill Christensen wrote:
Recent upgrade borked my setup.
[Prior posts indicate this is Mac OS 10.7 server]
Group Mismatch error once again, and adding the configure line
--with-mail-gid=staff
and removing the line
--with-mail-gid=${mmgroup}
as suggested doesn't fix it.
What to do? How can I keep this from happening whenever I do a major
upgrade/reinstall on my server?
These are really questions for Apple. I'm not aware of anyone on this
list other than you who is running Mac OS X server Mailman.
I'm using the 'client' version of Mac OSX, not the 'server' version.
I'm not using the Apple-provided version of Mailman. I use Macports,
which downloads the source directly from Sourceforge/lists.org.
I think
most people have had more success by completely ripping out the
supplied Mailman and installing from source. See the FAQ at
http://wiki.list.org/x/O4A9.
Much of that is ancient history or relates primarily to the OSXserver
version.
Fortunately, I figured out what the problem was. Though I had installed
with --with-mail-gid=staff, I hadn't also run a check_perms -f. That
was apparently the missing puzzle piece.
--
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] Setup problem with Mailman
Hi all, (cross posted to Macports-users and Mailman-users lists, as I'm not sure where the answer to the problem is more likely to come from) I upgraded a server the other day to Mac OS 10.7, and due to a new version of Macports required an uninstall/reinstall of Mailman. As seems to be the usual case, the new Mailman/Fetchmail install needs some tweaks to get it working right - the Dreaded Group Mismatch Error in Mailman, SSL required but configured --without-ssl in Fetchmail, etc... I've fought my way through all of those, but... Currently it's telling me that the location of the MDA, which in the previous Fetchmailrc file was /opt/local/libexec/mailman/mail/mailman and worked fine before the upgrade, is a directory which doesn't exist. And that's true, it doesn't. So, the question is, where did it move to? Where *should* Fetchmail be told that the Mailman MDA is? Thanks for relieving my frustration. -- 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] Setup problem with Mailman
Correction:
The problem below occurred because Mailman had run into an error and
hadn't installed that directory. I figured that one out and it's
installing again.
Now I'm back to a Group Mismatch error once again, and adding the
configure line
--with-mail-gid=staff
(and removing the line --with-mail-gid=${mmgroup} ) as suggested doesn't
fix it.
Next step? It seems I go through this every time I do an install of
Mailman...
On 10/10/11 8:52 PM, Bill Christensen wrote:
Hi all,
(cross posted to Macports-users and Mailman-users lists, as I'm not
sure where the answer to the problem is more likely to come from)
I upgraded a server the other day to Mac OS 10.7, and due to a new
version of Macports required an uninstall/reinstall of Mailman.
As seems to be the usual case, the new Mailman/Fetchmail install needs
some tweaks to get it working right - the Dreaded Group Mismatch Error
in Mailman, SSL required but configured --without-ssl in Fetchmail,
etc... I've fought my way through all of those, but...
Currently it's telling me that the location of the MDA, which in the
previous Fetchmailrc file was /opt/local/libexec/mailman/mail/mailman
and worked fine before the upgrade, is a directory which doesn't
exist. And that's true, it doesn't.
So, the question is, where did it move to? Where *should* Fetchmail
be told that the Mailman MDA is?
Thanks for relieving my frustration.
___
macports-users mailing list
macports-us...@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
--
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] Problem with help2man update
Attempting to do updates tonight, I ran into problems with upgrading help2man. I was able to manually update most other ports. The log for help2man says: :info:configure configure: error: perl module Locale::gettext required :info:configure shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_help2man/work/help2man-1.38.4 ./configure --prefix=/opt/local --enable-nls returned error 1 :error:configure Target org.macports.configure returned: configure failure: shell command failed (see log for details) :debug:configure Backtrace: configure failure: shell command failed (see log for details) port installed shows (among many others): gettext @0.18.1.1_0 gettext @0.18.1.1_2 (active) help2man @1.38.2_0 (active) p5-locale-gettext @1.05_3 (active) and port outdated shows: The following installed ports are outdated: help2man 1.38.2_0 1.38.4_0 ghostscript9.00_4 9.01_0 ImageMagick6.6.6-3_0 6.6.7-8_0 I'm hoping I don't have to go in and hack the port file for the two ports that are dependent on help2man so that they're looking for 1.38.2_0 instead of 1.38.4_0. Any better solutions? Thanks. -- 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] Archive 3rd Party List
At 10:31 AM -0600 4/17/09, Jim Redman wrote: I subscribe to a mailing list that has no archive capabilities. I don't really want to try to take over the list, but would like to archive the messages as a service to other list users. Would it be possible to do this with Mailman? Or does anyone have an alternate system that may be better capable to do this? Create a Mailman list, subscribe the Mailman list address to the original list. I don't think you even have to subscribe the original to Mailman (if you do, set it for No Mail to avoid infinite loops). You should be able to set Mailman to accept all mail from the original list. It'll be automatically archived. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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
[Mailman-Users] Check_perms reports invalid syntax?
Hi all, I'm setting up a new server with Mailman. After installing I tried bin/check_perms -f and got: file bin/check_perms, line 44 ''' ^ Syntax error: invalid syntax I'm running Python 2.5.1. My existing server, running Mailman 2.1.11/Python 2.3, has the same line and no problems with it. Any ideas? Do I need to upgrade or patch Python, and if so which 2.5 or better version works with Mailman? thanks -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Timestamp on approved msg
At 8:23 AM -0700 10/9/08, Mark Sapiro wrote: Bill Christensen wrote: Is there a way to change the timestamp on mail to moderated lists to display the time it is approved/sent by Mailman instead of the time of the orignal sender's post? Only by changing the source code, and it isn't a good idea. RFC 2822 Sec. 3.6.1 [1] specifies the meaning of the Date: header and says in part: The origination date specifies the date and time at which the creator of the message indicated that the message was complete and ready to enter the mail delivery system. snip... [1] http://www.cse.ohio-state.edu/cgi-bin/rfc/rfc2822.html The only required header fields are the origination date field and the originator address field(s). I had a feeling we'd be up against something like that. But many a non-moderated listserv typically replaces the FROM header with the listserv's reply address, do they not? For instance, this header from a Sourceforge list doesn't appear to display any info other than [EMAIL PROTECTED], and I suspect the timestamp is that of the listserv, not the original sender: Delivered-To: [EMAIL PROTECTED] Received: by 10.210.41.16 with SMTP id o16cs466769ebo; Wed, 8 Oct 2008 12:49:01 -0700 (PDT) Received: by 10.140.157.5 with SMTP id f5mr5391922rve.267.1223495340192; Wed, 08 Oct 2008 12:49:00 -0700 (PDT) Return-Path: [EMAIL PROTECTED] Received: from ch3.sourceforge.net (ch3.sourceforge.net [216.34.181.60]) by mx.google.com with ESMTP id 5si187618wrh.31.2008.10.08.12.48.59; Wed, 08 Oct 2008 12:49:00 -0700 (PDT) Received-SPF: pass (google.com: domain of [EMAIL PROTECTED] designates 216.34.181.60 as permitted sender) client-ip=216.34.181.60; Authentication-Results: mx.google.com; spf=pass (google.com: domain of [EMAIL PROTECTED] designates 216.34.181.60 as permitted sender) [EMAIL PROTECTED] Received: from www by b55xhf1.ch3.sourceforge.com with local (Exim 4.69) (envelope-from [EMAIL PROTECTED]) id 1Knexj-000480-Mc; Wed, 08 Oct 2008 19:44:47 + To: [EMAIL PROTECTED] From: SourceForge.net [EMAIL PROTECTED] Subject: [webcalendar - Help / Troubleshooting] RE: upgrade strategy Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Message-Id: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Date: Wed, 08 Oct 2008 19:44:47 + Not to say that just because someone else is doing it against the rules that I should be allowed to as well, of course. I don't have enough clout to circumvent the mail rules the way some of the big guys do. You could look at Mailman/ListAdmin.py at the point where it adds the X-Mailman-Approved-At: header to an approved message. You could also add a Resent-Date: header, and your user's MUAs may sort on that. Worth a try. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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
[Mailman-Users] Timestamp on approved msg
Hi all, Is there a way to change the timestamp on mail to moderated lists to display the time it is approved/sent by Mailman instead of the time of the orignal sender's post? Sometimes there's a fairly long lag between the original post and when it goes to the list, and the list mail displays below the fold (out of sight) in busy user's mailbox. In some cases that lag is intentional in order to release announcements at the most advantageous time. If it's not visible in the user's box it kinda defeats the purpose. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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
[Mailman-Users] Admin getting bug on one list
I can't get into the admin on a single list. Tried permissions repair, no help. Tried replacing config.pck, no help Tried replacing config.pck.last, no help Error log says: OSError: [Errno 22] Invalid argument: '/usr/local/mailman/lists/aen/config.pck.last' Where to next? -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Admin getting bug on one list
Bill Christensen wrote: I can't get into the admin on a single list. Tried permissions repair, no help. Tried replacing config.pck, no help Tried replacing config.pck.last, no help Error log says: OSError: [Errno 22] Invalid argument: '/usr/local/mailman/lists/aen/config.pck.last' Where to next? At 12:05 PM -0700 9/29/08, Mark Sapiro wrote: Post the entire traceback from the error log. Here you go: Sep 29 12:55:06 2008 admin(23693): admin(23693): [- Mailman Version: 2.1.11 -] admin(23693): [- Traceback --] admin(23693): Traceback (most recent call last): admin(23693): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(23693): main() admin(23693): File /usr/local/mailman/Mailman/Cgi/admin.py, line 199, in main admin(23693): mlist.Save() admin(23693): File /usr/local/mailman/Mailman/MailList.py, line 570, in Save admin(23693): self.__save(dict) admin(23693): File /usr/local/mailman/Mailman/MailList.py, line 542, in __save admin(23693): os.unlink(fname_last) admin(23693): OSError: [Errno 22] Invalid argument: '/usr/local/mailman/lists/aen/config.pck.last' admin(23693): [- Python Information -] admin(23693): sys.version = 2.3 (#1, Sep 13 2003, 00:49:11) [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] admin(23693): sys.executable = /usr/bin/python admin(23693): sys.prefix = /System/Library/Frameworks/Python.framework/Versions/2.3 admin(23693): sys.exec_prefix = /System/Library/Frameworks/Python.framework/Versions/2.3 admin(23693): sys.path= /System/Library/Frameworks/Python.framework/Versions/2.3 admin(23693): sys.platform= darwin admin(23693): [- Environment Variables -] admin(23693): HTTP_REFERER: http://aen.austineconetwork.org/mailman/admin/aen admin(23693): SERVER_SOFTWARE: Apache/2.0.52 (Unix) mod_fastcgi/2.4.2 PHP/4.3.8 mod_ssl/2.0.52 OpenSSL/0.9.7l admin(23693): SCRIPT_NAME: /mailman/admin admin(23693): SERVER_SIGNATURE: addressApache/2.0.52 (Unix) mod_fastcgi/2.4.2 PHP/4.3.8 mod_ssl/2.0.52 OpenSSL/0.9.7l Server at aen.austineconetwork.org Port 80/address admin(23693): admin(23693): REQUEST_METHOD: POST admin(23693): HTTP_KEEP_ALIVE: 300 admin(23693): SERVER_PROTOCOL: HTTP/1.1 admin(23693): QUERY_STRING: admin(23693): CONTENT_LENGTH: 36 admin(23693): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(23693): HTTP_USER_AGENT: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16 admin(23693): HTTP_CONNECTION: keep-alive admin(23693): SERVER_NAME: aen.austineconetwork.org admin(23693): REMOTE_ADDR: 205.238.129.194 admin(23693): PATH_TRANSLATED: /Volumes/Apache2/domains/AustinEcoNetwork.org/aen admin(23693): SERVER_PORT: 80 admin(23693): SERVER_ADDR: 205.238.129.194 admin(23693): DOCUMENT_ROOT: /Volumes/Apache2/domains/AustinEcoNetwork.org admin(23693): PYTHONPATH: /usr/local/mailman admin(23693): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/admin admin(23693): SERVER_ADMIN: [EMAIL PROTECTED] admin(23693): HTTP_HOST: aen.austineconetwork.org admin(23693): HTTP_CACHE_CONTROL: max-age=0 admin(23693): REQUEST_URI: /mailman/admin/aen admin(23693): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(23693): GATEWAY_INTERFACE: CGI/1.1 admin(23693): REMOTE_PORT: 55930 admin(23693): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5 admin(23693): CONTENT_TYPE: application/x-www-form-urlencoded admin(23693): HTTP_ACCEPT_ENCODING: gzip,deflate admin(23693): PATH_INFO: /aen -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Admin getting bug on one list
At 12:48 PM -0700 9/29/08, Mark Sapiro wrote: Bill Christensen wrote: Sep 29 12:55:06 2008 admin(23693): admin(23693): [- Mailman Version: 2.1.11 -] admin(23693): [- Traceback --] admin(23693): Traceback (most recent call last): admin(23693): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(23693): main() admin(23693): File /usr/local/mailman/Mailman/Cgi/admin.py, line 199, in main admin(23693): mlist.Save() admin(23693): File /usr/local/mailman/Mailman/MailList.py, line 570, in Save admin(23693): self.__save(dict) admin(23693): File /usr/local/mailman/Mailman/MailList.py, line 542, in __save admin(23693): os.unlink(fname_last) admin(23693): OSError: [Errno 22] Invalid argument: '/usr/local/mailman/lists/aen/config.pck.last' Mailman is trying to save the current list configuration which it does by the following steps: 1. Save the data to a unique temp name. 2. Remove (unlink) config.pck.last 3. Link the name config.pck.last to the file config.pck 4. Rename the temp name to config.pck This is the safe way to essentially rename the old config.pck as config.pck.last and save the new data as config.pck. In steps 2. and 3. we ignore non existant errors, but raise all the rest. In your case, when we try to remove '/usr/local/mailman/lists/aen/config.pck.last' at step 2, we are getting the [Errno 22] Invalid argument: error from the OS. What does ls -l /usr/local/mailman/lists/aen/ show? config.pck config.pck.bak config.pck.last config.pck.safety (plus backup copies of each of those which I made) plus a whole bunch of config.pck.temp.ns.greenbuilder.com. where is some number plus pending.pck request.pck I've tried putting in each of the three backup versions (.bak, .last, .safety) in as config.pck with appropriate owner (as determined by other working lists), no luck there. Also tried a backup from several days ago. Is it necessary to stop/start mailman and/or repair permissions or anything else between each attempt? -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Admin getting bug on one list
At 2:40 PM -0700 9/29/08, Mark Sapiro wrote: Bill Christensen wrote: At 12:48 PM -0700 9/29/08, Mark Sapiro wrote: Bill Christensen wrote: Sep 29 12:55:06 2008 admin(23693): admin(23693): [- Mailman Version: 2.1.11 -] admin(23693): [- Traceback --] admin(23693): Traceback (most recent call last): admin(23693): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(23693): main() admin(23693): File /usr/local/mailman/Mailman/Cgi/admin.py, line 199, in main admin(23693): mlist.Save() admin(23693): File /usr/local/mailman/Mailman/MailList.py, line 570, in Save admin(23693): self.__save(dict) admin(23693): File /usr/local/mailman/Mailman/MailList.py, line 542, in __save admin(23693): os.unlink(fname_last) admin(23693): OSError: [Errno 22] Invalid argument: '/usr/local/mailman/lists/aen/config.pck.last' Mailman is trying to save the current list configuration which it does by the following steps: 1. Save the data to a unique temp name. 2. Remove (unlink) config.pck.last 3. Link the name config.pck.last to the file config.pck 4. Rename the temp name to config.pck This is the safe way to essentially rename the old config.pck as config.pck.last and save the new data as config.pck. In steps 2. and 3. we ignore non existant errors, but raise all the rest. In your case, when we try to remove '/usr/local/mailman/lists/aen/config.pck.last' at step 2, we are getting the [Errno 22] Invalid argument: error from the OS. What does ls -l /usr/local/mailman/lists/aen/ show? config.pck config.pck.bak config.pck.last config.pck.safety ls with the '-l' option! I'm trying to see what it is about config.pck.last that might be causing the [Errno 22] Invalid argument: error when Mailman tries to unlink it. Ok. Here's the full list: Hmmm, just noticed that this time around config.pck has -rw-r- instead of -rw-rw Looking back, most of my other attempts had -rw-rw -rw-r- 1 nobody mailman 372763 29 Sep 12:43 config.pck -rw-r- 1 billcmailman 372763 29 Sep 11:49 config.pck.bak -rw-rw 1 mailman mailman 372763 29 Sep 12:43 config.pck.last -rw-r- 1 mailman mailman 372695 29 Sep 11:48 config.pck.last.bak -rw-rw 1 root mailman 372695 29 Sep 12:20 config.pck.safety -rw-rw 1 nobody mailman 372760 27 Sep 21:15 config.pck.tmp.ns2.greenbuilder.com.1684 -rw-rw 1 nobody mailman 372760 27 Sep 21:15 config.pck.tmp.ns2.greenbuilder.com.1691 -rw-rw 1 nobody mailman 372760 27 Sep 21:15 config.pck.tmp.ns2.greenbuilder.com.1695 -rw-rw 1 nobody mailman 372760 29 Sep 08:26 config.pck.tmp.ns2.greenbuilder.com.20146 -rw-rw 1 mailman mailman 372760 29 Sep 09:00 config.pck.tmp.ns2.greenbuilder.com.20511 -rw-rw 1 root mailman 372760 29 Sep 09:00 config.pck.tmp.ns2.greenbuilder.com.20513 -rw-rw 1 nobody mailman 372760 29 Sep 09:18 config.pck.tmp.ns2.greenbuilder.com.20636 -rw-rw 1 nobody mailman 372936 29 Sep 09:19 config.pck.tmp.ns2.greenbuilder.com.20646 -rw-rw 1 nobody mailman 372760 29 Sep 09:32 config.pck.tmp.ns2.greenbuilder.com.20837 -rw-rw 1 nobody mailman 372760 29 Sep 10:26 config.pck.tmp.ns2.greenbuilder.com.21470 -rw-rw 1 nobody mailman 372760 29 Sep 10:28 config.pck.tmp.ns2.greenbuilder.com.21507 -rw-rw 1 mailman mailman 372760 29 Sep 10:51 config.pck.tmp.ns2.greenbuilder.com.21536 -rw-rw 1 mailman mailman 372760 29 Sep 10:51 config.pck.tmp.ns2.greenbuilder.com.21539 -rw-rw 1 nobody mailman 372760 29 Sep 10:30 config.pck.tmp.ns2.greenbuilder.com.21558 -rw-rw 1 nobody mailman 372760 29 Sep 10:46 config.pck.tmp.ns2.greenbuilder.com.21741 -rw-rw 1 nobody mailman 372760 29 Sep 10:46 config.pck.tmp.ns2.greenbuilder.com.21750 -rw-rw 1 nobody mailman 372760 29 Sep 11:32 config.pck.tmp.ns2.greenbuilder.com.22337 -rw-rw 1 nobody mailman 372760 29 Sep 11:34 config.pck.tmp.ns2.greenbuilder.com.22386 -rw-rw 1 nobody mailman 372760 29 Sep 11:37 config.pck.tmp.ns2.greenbuilder.com.22411 -rw-rw 1 nobody mailman 372760 29 Sep 11:37 config.pck.tmp.ns2.greenbuilder.com.22418 -rw-rw 1 nobody mailman 372760 29 Sep 11:37 config.pck.tmp.ns2.greenbuilder.com.22419 -rw-rw 1 nobody mailman 372760 29 Sep 11:40 config.pck.tmp.ns2.greenbuilder.com.22439 -rw-rw 1 nobody mailman 372760 29 Sep 11:40 config.pck.tmp.ns2.greenbuilder.com.22449 -rw-rw 1 mailman mailman 372683 29 Sep 12:00 config.pck.tmp.ns2.greenbuilder.com.22548 -rw-rw 1 nobody mailman 372760 29 Sep 11:46 config.pck.tmp.ns2.greenbuilder.com.22550 -rw-rw 1 nobody mailman 372760 29 Sep 11:49 config.pck.tmp.ns2.greenbuilder.com.22610 -rw-rw 1 nobody mailman 372695 29 Sep 11:50 config.pck.tmp.ns2.greenbuilder.com.22618 -rw-rw 1 nobody mailman 372683 29 Sep 11:58 config.pck.tmp.ns2
Re: [Mailman-Users] Admin getting bug on one list
At 3:24 PM -0700 9/29/08, Mark Sapiro wrote: It looks like at least once, you had removed config.pck and Mailman had fallen back to config.pck.last - this is where the config.pck.safety came from. It actually appears that some saves of the list are succeeding and that maybe it is only the admin CGI that's failing. Does the list appear to work otherwise? Yes, mail from approved senders is going through. This is a moderated list though, so there are a number of messages stacked up waiting for admin approval. What does ls -ld /usr/local/mailman/lists/aen give: the permissions should be drwxrwsr-x and the group should be mailman. The owner is normally root or the web server (nobody?) depending on how the list was created. Yes, it's drwxrwsr-x and the owner and group match all the other (working) lists -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Admin getting bug on one list
At 4:18 PM -0700 9/29/08, Mark Sapiro wrote: Is this Mac OS X? If so, see http://mail.python.org/pipermail/mailman-users/2005-January/042256.html. Unfortunately, the links in that post are all invalid. They should be http://mail.python.org/pipermail/mailman-users/2004-August/038697.html http://mail.python.org/pipermail/mailman-users/2005-January/041638.html http://mail.python.org/pipermail/mailman-users/2005-January/041650.html http://mail.python.org/pipermail/mailman-users/2004-July/038384.html and the FAQ at http://wiki.list.org/x/O4A9. The post at http://mail.python.org/pipermail/mailman-users/2004-July/038384.html indicates that that poster's problem was solved by simply removing config.pck.last. It is OK to do that as long as there is a good config.pck. If you're unsure, you could try just renaming config.pck.last. The key is that there be no config.pck.last when you go to the admindb page. Yes, it is Mac Thanks. Renaming config.pck.last let me in. Looks like all is well now. I'll have to remember this one. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Greetings .. and some Questions
At 1:21 PM -0400 9/17/08, Jeffrey Lake - Admin wrote: hello, I love MailMan .. but I am having some problems that I hope someone here can help with. I run a web-server that has MailMan installed by Cpanel. Most of my clients use MailMan in one way or another, as do I. What I need to do is fix a minor problem, approximently half the URL's MailMan creates are missing the 'www' portion of the link, this causes a little problem when users log-in with the 'www' in the URL then get sent to a URL with out the 'www' they are forced to log-in again .. this gets a little annoying .. That sounds more like a problem in how you have your web server and/or DNS service configured than a Mailman problem. We set up our domains such that www.domain.com and domain.com will point to the same files, as the www portion is really rather redundant. There would have to be entries in DNS for both, as well as entries in your apache httpd.conf (or similar for whatever webserver you might be using) to achieve this. I can reach any of our hosted lists using www.domain.com/mailman/listinfo/listname or domain.com/mailman/listinfo/listname as a result. Now for a problem releated to my web-site .. I have been attempting to get my installs of MailMan to use my SSL cert, as I want the entire site behind the SSL, If I add that to the mm_cfg.py everybodies MailMan on the server wants to run with 'https' which causes all kinds of errors .. I'll leave the answer to this one to those who are more familiar with Mailman. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Harvesting of email addresses for spam from archives
At 6:13 PM +0100 9/8/08, David Beaumont wrote: I notice this list's archives are not standard mailman format! I assume by 'this list' you mean [EMAIL PROTECTED] In what way are the archives not standard? Thanks I mean the archives at http://www.mail-archive.com/mailman-users%40python.org/ Ours are at http://lists.shire.net/pipermail/dbamain/ On ours you will see the emails have the ' at ' obscuration. Yours don't seem to show the email in any form. How do we change to your format? David At a quick glance it doesn't look like it would be all too terribly difficult to change. When I was using Mhonarc for the archives on one of my lists (before moving to Mailman last spring), I had a script that would change [EMAIL PROTECTED] to [EMAIL PROTECTED]. If I recall, it simply used a regex that looked for characters followed by an @ followed by more characters. It then replaced everything from the @ to the next space with It appears that the code which does the obfuscation is in ($prefix)/Mailman/Mailman/Archiver/HyperArch.py between lines 280 and 290 in 2.1.11. (I'm sure someone will correct me if that's wrong info) -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Rv: many problems
At 10:33 AM -0700 9/5/08, Jaione Arrieta wrote: Thank you for the answers and yes the problem is wit= h the server that doesn=C2=B4t allow more than 400 mails an hour and my= list has 500 members, Sounds like you have a problem there. If this is an announcement list (where you might have some control over the timing of messages being sent, as opposed to a discusion list where you won't) you might be able to temporarily split the list into two. If it's a discussion, you'd be better off moving it again OR getting the current server admin to allow more than 400 emails/hour. _and what makes me more mad is that my contract with them was that the mailman work properly, Well, technically Mailman *is* working properly. It's the throttled mail gateway that's getting you. I'm looking for the best option= and I after going through the list you guys sent me I like EMWD=C2=A0 caus= e they have a mailman hosting=C2=A0 _that=C2=B4s all I need cause my web is= in another server_but I have contacted them twice already (yesterday and t= his morning)and haven=C2=B4t had any answer yet Maybe because you're ranting and sound like a potentially high-maintainence client. (-; Actually, they say that they've attempted to contact you but it's bounced from your Yahoo address twice. We also host Mailman lists. I hadn't spoken up before now because we're relatively new to Mailman, having just switched over in March from another list software that we've been running for many years. And because I was busy with other stuff - like working on a long overdue overhaul of our own site. Before I can make you an offer I'd need to know the topic of your list and get an idea of your message load - how many messages per week or month on average, and what the averages is of the total megabytes used. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Web interface down
At 4:14 PM -0700 8/26/08, Mark Sapiro wrote: Bill Christensen wrote: I'm having trouble with the web interface again. I added a couple new lists today and stopped/started both fetchmail and mailman to make sure they would pick up the new addresses. It appears that my lists are still running and the pipermail archives are still working, but I can't get in to the admin via the web on any lists, including the new ones. I'm getting the Bug in Mailman version 2.1.9 screen. Everything was good until I stopped/started. Stopping and starting Mailman has no effect on the web interface unless somehow a config.pck got corrupted in the process. What is in Mailman's error log? Whenever you get the Bug in Mailman ... response on the web interface, you have to find the corresponding error and traceback in Mailman's error log. That may be only the beginning of diagnosing the problem, but without that, it could be literally anything. Thanks, I got that figured out yesterday. I went ahead and did an update to 2.1.11 and got that and a few other little glitches cleared up. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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
[Mailman-Users] Web interface down
Hey folks, I'm having trouble with the web interface again. I added a couple new lists today and stopped/started both fetchmail and mailman to make sure they would pick up the new addresses. It appears that my lists are still running and the pipermail archives are still working, but I can't get in to the admin via the web on any lists, including the new ones. I'm getting the Bug in Mailman version 2.1.9 screen. Everything was good until I stopped/started. I'm running Apache2. NOT SELinux. I've done permission fixes. I've looked for corrupt config files using: echo noop.py def noop(mlist): return ./withlist -a -r noop (all showed unlocked) I've checked the logs. No sign of anything specific there. I can't find the cause. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] line returns missing
Also jumping in late on this thread. I've seen the same happen in the archives. For instance, this original message is not wrapped: http://pec4u.org/pipermail/watchdogs/2008-July/000763.html but this reply to it wraps the quoted text from the first just fine: http://pec4u.org/pipermail/watchdogs/2008-July/000764.html (both of these display properly wrapped in my Eudora/Mac) It appears that a fair number of pipermail archived posts aren't wrapped. Any way to keep that from happening? -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Hard drive is full
At 1:19 PM -0400 7/10/08, Simon wrote: This doesn't help you much now, but this is why it is a good idea to keep anything that stores data (mail, temp directories, etc) on a separate partition from your / directory. On that note... is there anything to look out for with moving the archives elsewhere? Can they just be moved and a symlink put in their place? Or is it best to define the path in a config file (and if so, which one)? Thanks -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Inaccessible public archives
At 6:59 PM -0700 7/4/08, Mark Sapiro wrote: Bill Christensen wrote: I just moved my Mailman/Apache/Postfix server to a new hard drive, and in the process managed to make the public archives inaccessible. Private archives work fine, as does everything else as far as I can tell. I suspect that the problem has to do with my renaming the root hard drive (though of course the paths would typically still be /usr/local/mailman/ which accounts for most everything still working). I've tried switching to private archives and back again in the hope of building a new working symlink, but there's no difference. I made no changes to the Apache config file, and all the paths and rules there look like they should work. Any ideas where else I should search for a fix? What does Apache say when you try to access a public archive? What's in Apache's error log? Symbolic link not allowed. Is SELinux or some other security policy management involved? nope. What are the ownership and permissions of /usr/local/mailman/archives/private ? In particular, is it either owned by the apache user or o+x ? they were were drwxrws--- nobody mailman private drwxrwsr-x billc mailman public I looked on the old hd and found them set as drwxrwx--- billc mailman private drwxrwxr-x billc mailman public I tried a perms fix, but that didn't do the trick. So I tried changing them to that. Bad idea, now I'm getting a we've hit a bug in mailman 2.1.9... message when logging in to the web interface. I tried another perms fix, and the symptoms are unchanged. Help, Mr Wizard! I have no idea how to set an rws to get it back to broken but generally functional. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Inaccessible public archives
Thanks. That and fixing a missing symlink did the trick. At 7:24 AM -0700 7/5/08, Mark Sapiro wrote: chmod g+s will do it, but just to make sure everything is right, do it this way: chmod 2770 /usr/local/mailman/archives/private chown nobody:mailman /usr/local/mailman/archives/private chmod 2775 /usr/local/mailman/archives/public Then put the Options +FollowSymLinks in an appropriate Directory block in the Apache config. -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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
[Mailman-Users] Inaccessible public archives
Hi folks, I just moved my Mailman/Apache/Postfix server to a new hard drive, and in the process managed to make the public archives inaccessible. Private archives work fine, as does everything else as far as I can tell. I suspect that the problem has to do with my renaming the root hard drive (though of course the paths would typically still be /usr/local/mailman/ which accounts for most everything still working). I've tried switching to private archives and back again in the hope of building a new working symlink, but there's no difference. I made no changes to the Apache config file, and all the paths and rules there look like they should work. Any ideas where else I should search for a fix? -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.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] Help! Recipient list too long message is held for approval
The acceptable number of recipients can be adjusted at: http://list domain/mailman/admin/listname/privacy/recipient Ceiling on acceptable number of recipients for a posting. (Details for max_num_recipients) Defaults to 10 At 8:48 AM -0700 5/23/08, Knabe, Troy wrote: On 5/23/08 8:14 AM, webct [EMAIL PROTECTED] wrote: Hi, We are using mailman which comes with Mac OS X server 10.5. I think, I have set it up correctly for most of the part but there is one lingering issue with sending a message with other email addresses. I get Recipient list too long error message and the email is held for moderator's approval. How do I make mailman remember to send messages across with long list of recipients. Thanks. fuzbuz. Under Privacy Optionis and Recipient Filters there is a Ceiling on acceptable number of recipients for a posting. I believe the default value is 10. This has nothing to do with the number of list members, but the number of other addresses in the To:, CC:, and BCC: fields of the email that causes this be invoked. -Troy -- 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/knabe%404j.lane.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.htp -- 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/billc_lists%40greenbuilder.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.com/ -- 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] Major problems with privacy and mailman lists and harvesters
PROTECTED] (modified from the orig to save the innocent author from a deluge of spam, at least on **my** account), without even submitting the form! We need to rethink how we can adequately keep emails out of spammers hands. And, yes, it's kinda unhandy not read a message and not be able to fire an email off to the author directly. But to make it easy for list subscribers, is to make it easy for spammers, who probably have already joined the list, and are delighted to get email addresses, any which way they can. Most discussion on mailing lists do not require any address other than the the mailing list itself. To take a discussion offline, I propose a few ideas: 1. the mailing list allows the users to specify a phone-number, an irc channel and identity that they can be reached by, or some other method to contact the author, that is NOT an email address. This info is kept private, and the button at the bottom of the archived letters could give you this info. The person wanting to privately discuss the letter could then call the user or contact them via irc/jabber/whatever, and either discuss the matter there and then, or the author could voluntarily give the other party his email address at that time. Or file a list message, and ask the author to contact him, and give out a phone number, whatever. I thought about integrating spamgourmet throw-away email addresses, but really, that wouldn't help. Spammers could simply request, get the throw-away, spam it, and toss it. The user himself is the only one who can usefully hand out throw-away addresses. If you think mailman doesn't have to worry about this sort of thing, keep in mind that mailman has swiftly become probably the top mailing list software on the web. That spammers would not be interested in mining mailing lists for their tens of thousands of valid addresses is foolhardy thinking. That thinking the options that mailman provides now is adequate to keep spammers from harvesting email addrs, is just plain wrong. That datamining and de-obfuscation are NOT being done specifically for mailman lists is wishful thinking. Mailman needs to pay attention to the fact that spammers would **love** to use their mailing list installations to ship spam for them, AND ALSO that spammers will want to harvest email addresses from the web interface AND the mailings themselves. We need to lock down mailman, or at least make it an option! Simply put, in messages sent to users, the only email that should be found anywhere in a recieved message, is the recipient's. In the archived messages, absolutely no email addresses at all. Not even obfuscated. If we follow this pattern, the spammers will not be able to use mailman lists for any useful purpose. They'll have to hack the web sites to get the lists. murf -- Steve Murphy Software Developer Digium -- 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/billc_lists%40greenbuilder.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.com/ -- 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] GNU Mailmain 2.1.9: Filtering Messages based onwords in the body of an email?
At 12:20 PM -0700 5/20/08, Mark Sapiro wrote: Steve wrote: Is it possible to set up GNU Mailman 2.1.9 to filter on URLs or other keywords in the body of an email? Not without implementing a custom handler http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.067.htp or modifying source code. Assuming that the rant URLs are known, couldn't he just use the spam filter? -- Bill Christensen http://greenbuilder.com/contact/ Green Building Professionals Directory: http://directory.greenbuilder.com Sustainable Building Calendar: http://www.greenbuilder.com/calendar/ Green Real Estate: http://www.greenbuilder.com/realestate/ Straw Bale Registry: http://sbregistry.greenbuilder.com/ Books/videos/software: http://bookstore.greenbuilder.com/ -- 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] Still sticking: gmail = fetchmail = mailman=postfix
On 3/19/08, Mark Sapiro [EMAIL PROTECTED] wrote: A group mismatch will result in the wrapper exiting with a non-zero status and issuing a message which should appear somewhere. Other errors should be logged in Mailman's error log. If it gets that far. I'm suspecting that there's a problem with a domain alias, which I'll want to test before going any further. If you want to verify the Mailman is working completely once a message hits the mailman/qfiles/in/ queue, you can use mailman/bin/inject to put a message in the in/ queue. I'm unclear on the use of mailman/bin/inject. The only options given are -l for list and -q for queue. Then it says filename is the name of the plaintext message file to inject. If omitted, standard input is used. Ok... but there doesn't seem to be any way to designate a file name (my obvious guess at -filename didn't do it), and without it a call to python inject -l testlist appears to be sitting there waiting for more input. Sorry to have to keep bothering the list with this stuff. I'm looking forward to getting it running smoothly and moving a bunch of lists over from a rather ancient listserv software. -- 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
