Re: [Mailman-Users] error after migration
nikos wrote: > >This is one: > >Feb 08 16:03:11 2012 (15955) Traceback (most recent call last): > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop > self._onefile(msg, msgdata) > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 191, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose > mlist.ArchiveMail(msg) > File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 217, in >ArchiveMail > h.close() > File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 327, in close > self.write_TOC() > File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 1105, in >write_TOC > toc = open(os.path.join(self.basedir, 'index.html'), 'w') >IOError: [Errno 13] Permission denied: >'/var/lib/mailman/archives/private/mylist/index.html' My best guess is there is some directory in the full path /var/lib/mailman/archives/private/mylist/ that does not have search permission for Mailman's group or the mylist/ ditectory does not have write permission for Mailman's group or the index.html file exists and doesn't have write permission for Mailman's group or this is a SELinux or other security manager issue. Did you migrate the archives by copying the archives/private/mylist tree? If so, you may be able to fix this by following the recommended procedure which is to only copy the archives/private/mylist.mbox/mylist.mbox files and build the pipermail archive with 'bin/arch --wipe mylist' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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] digest-mode not functioning properly
Lluis Montoliu wrote: >the two large list are not sending any digest-mode, with the exact >same settings, even if I decrease the value to 256 or if I trigger >sending a new digest dispatch right now, which does not happen. I'm >totally amazed. I've seen the archives of mailman and, unfortunately, >the problems with digest-mode appear to be rather common, many reports >found, but not really solutions, at least, I could not find the one >that will fix my bug. There is almost certainly a message or messages in the lists/LISTNAME/digest.mbox files for these lists that is causing an exception to be thrown in the scrubber in it's attempt to process the digest. Ask the hosting provider to look for relevant error messages and tracebacks in Mailman's error log. You may have to have the hosting provider just move the lists/LISTNAME/digest.mbox files aside and abandon the current accumulated digests if the hosting provider can't do anything more selective to find and fix the offending messages. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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] Image orientation in scrubbed attachments
Mark, thank you very much for your help, which got me on the right track. Indeed, the problem is that iPad photos, even when they are taken with a portrait orientation, always carry Exif data that claim a landcape orientation. Web browsers and many mail clients orient pictures according to the Exif information. So, to make a long story short, if I remove the incorrect Exif orientation-info from those pictures before sending them to Mailman, they display correctly after scrubbing. Thanks again, -malgosia At 9:04 AM -0800 2/9/12, Mark Sapiro wrote: >malgosia askanas wrote: > >>When scrubbing an image attachment such as a jpeg, Mailman seems to always >>orient it into landscape mode - irrespective of the orientation of the >>original. Is there some way to prevent this? > > >Whatever is doing what you observe, it's not Mailman. It may be the web >browser that opens the link to the scrubbed attachment or something >else, but Mailman makes no changes whatsoever to the content of the >attachment. Mailman just decodes the (presumably base64 encoded) >content and saves it in a file and provides a URL to access the file. > >-- >Mark Sapiro The highway is for gamblers, >San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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] digest-mode not functioning properly
Some more data. Hosting provider can't find anything wrong. I have set a new list, fake users for testing purposes. Set one of them for standard the other for digest-mode and played with size limits and daily and everything worked as expected, in this test list, whereas the two large list are not sending any digest-mode, with the exact same settings, even if I decrease the value to 256 or if I trigger sending a new digest dispatch right now, which does not happen. I'm totally amazed. I've seen the archives of mailman and, unfortunately, the problems with digest-mode appear to be rather common, many reports found, but not really solutions, at least, I could not find the one that will fix my bug. Thanks again for your help and suggestions Lluis Quoting Lluis Montoliu : Dear listers, Suddenly, some users of two mailman (version 2.1.11) lists I am administering have started to complain about digest-mode not functioning properly. In brief, messages are not being sent in digest-mode. Settings are 1024 Kb for size before sending a digest message or daily, if this size isn't reached, new digest volumes should be started daily too. No messages sent. I have tried to trigger the "immediate sending digest-mode" from administration settings (Should Mailman send the next digest right now, if it is not empty?) and no way, nothing happened. I even tried myself, registering one of my email addresses a couple of days ago and setting this to digest-mode (normally I don't use this mode) and nothing, does not work. It looks as if digest-mode stopped working for good. However, standard mode works fine. I have contacted my hosting provider and I am currently awaiting their response, but I decided to share this unexpected troubles in this forum, in case someone has seen it before and there is something I could do from the administrative interface. Thanks for your comments. Lluis -- 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] can I use a mailman list address as a (qmail)sender address?
On Wed, 8 Feb 2012, Stephen J. Turnbull wrote: Yup. But he explained this. The list is the public face of a committee, and at least some outgoing mail should appear to be from the committee. Couldn't this be done by sending from an existing account and spoofing the From line? Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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] Thoughts about migrating to Mailman instead of Sympa (from Majordomo)
It's been a few weeks since the last posting to this thread, but I nonetheless wanted to follow up to provide some sort of closure around one organization's mailing list migration efforts from Majordomo and to also hopefully provide a few interesting tidbits of information to others. Based in part on the incredible responsiveness and assistance from this thread, we have decided to go with Mailman instead of Sympa. We took a few measures to lock down our instance, including all of the following: - Centralized LDAP authentication via Apache's mod_authnz_ldap (http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html) - Removed all subscriber password form fields from the UI so that only auto-generated passwords are used for subscribers (templates/en/listinfo.html and templates/en/options.html) - Changed the back-end for subscriber passwords too so that a form/CGI password can never become the subscriber password (Mailman/Cgi/subscribe.py) - Removed the "auto-generate password" option from the "Create a New List" form so that users had to choose a password, and then removed the password string from the "Your list has been created" emails (templates/en/newlist.txt) - Change the "Password Reminder" text to "Password Reset" and auto-generate a new random password before emailing the subscriber their password (Mailman/Cgi/options.py) - Don't require a Mailman "list creator" password when creating a new list because the site is already locked down via an Apache LDAP module (Mailman/Cgi/create.py) I also wrote an import script from Majordomo into Mailman, thoroughly referencing the excellent contrib/majordomo2mailman.pl script written in 2002 by Heiko that currently lives in the Mailman2 tarball. I was able to translate most Majordomo settings into Mailman. The script also has a --stats option if you just want to get a sense of the distribution of values across all of your Majordomo lists. The script is only on GitHub right now (https://github.com/mayesgr/import_majordomo_into_mailman), but I plan to post it to Mailman's bug tracker once I'm 100% satisfied with it, in the hopes that, if others find it useful, it makes its way into the tarball as well. If you'd like the script improved in any way, please feel free to let me know. (Apologies to all pythonistas, myself included: the script started out as import_majordomo_into_sympa.pl, which are both written in Perl, and then we changed gears when we decided to go with Mailman instead.) Thanks again to everyone for all of your great information and help, Geoff Mayes > -Original Message- > From: mailman-users-bounces+gmayes=uoregon@python.org > [mailto:mailman-users-bounces+gmayes=uoregon@python.org] On > Behalf Of Geoff Mayes > Sent: Thursday, January 19, 2012 10:32 AM > To: mailman-users@python.org > Subject: [Mailman-Users] Thoughts about migrating to Mailman instead of > Sympa (from Majordomo) > > Hello Mailman gurus, > > I hope a general question about Mailman's features and future direction > (along with some Sympa comparisons) are appropriate for this list. > > The University of Oregon is migrating away from Majordomo. We decided > on Sympa because Mailman sends passwords over email while Sympa > provides centralized (e.g. Shibboleth, LDAP, etc) authentication. If Mailman > provided a way around the passwords in the clear issue, I'm pretty sure we'd > go with Mailman because: > - Mailman is more thoroughly used and thus tested (one stat that gets at this > is Alexa Traffic Rank: 165,692 vs 749,729 for Sympa) > - Mailman is more mature (the max bug ID for mailman in its issue-tracking > system is ~913,400; the max bug ID for Sympa is 8,117 and there is still no > bug > category for Sympa's latest version -- 6.1.7 -- even though it has been out > for > over 4 months) > - Mailman has greater branch stability and code reliability (I noticed that > Barry > ran a pre-checkin acceptance suite for the Postgres patch for Mailman 3 > before he checked it in) > - Mailman has a bright and well-documented future (Mailman 3 and its bug > tracker, source code, milestones, etc) > - Mailman has a more active and supportive community, which is very > important in resolving future issues (Mailman had 150 list postings in > December and through mid-January while Sympa had 44; I've been > impressed with Mark Sapiro's responsiveness on this list) > > Does anyone know a way around the emailed passwords issue in Mailman, > clever hacks, certain plugins, or a timeline for Mailman 3's release? I've > written a number of Django apps using my own LDAP module, so I was also > wondering if folks think now is a mature-enough time to perhaps grab > Mailman 3, its Django front-end, and hack together what I'm after? A final, > random question: Mailman 3 is still in alpha, but is it stable given that it's > almost been in alpha for 4 years? > > Many, many thinks for any help, pointers, or information, > > Geoff Mayes > ---
