Mailman 3 March 2006 - Mailman-Users

follow-up to previous posts, exim + mailman + virtualhosts
by Bretton Vine March 20, 2006

March 20, 2006

My requirements are for an installation of mailman and exim on a single server to provide the following functionality: 1. Same named lists, separate lists across domains namely: --> listname(a)domain1.co.za --> listname(a)domain2.co.za 2. Domain name independent configuration of lists i.e. listname(a)domain1.co.za is administered at http://lists.domain1.co.za/mailman/listname listname(a)domain2.co.za is administered at http://lists.domain2.co.za/mailman/listname Can anyone tell me if this is (a) practical and (b) possible, with or without patches etc. If so, where could I find the relevant documentation on to do it? Can the config be setup in mailman or is some magic required with regards DNS, Apache (rewrite, redirect, alias directives etc) and Exim. thanks -- | Bretton Vine | 083 633 8475 | bretton(a)hivemind.net | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "Don't knock masturbation, it's sex with someone I love." ~ Woody Allen, Annie Hall

2 1

vhost patchset for 2.1.7 (Debian, Exim)
by Bretton Vine March 20, 2006

March 20, 2006

Hi, I wonder if anyone can point me in the appropriate direction of some sorely lacking documentation on the patching of mailman to support virtualhosts under exim. Starting here: http://nix.lauft.net/mailman/ It appears that there are two distinct forks to the patchset (please correct me if I'm wrong) Apply [1] to mailman source, then [2] [1] http://nix.lauft.net/mailman/mailman-2.1.7-release-to-20060114.patch [2] http://nix.lauft.net/mailman/mailman-2.1.7-20060114-to-vhost.patch or Apply [A] to mailman source, then [B] [A] http://nix.lauft.net/mailman/mailman-2.1.7-release-to-vhost.patch [B] http://nix.lauft.net/mailman/mailman-vh-2.1.7.patch In both cases I've had to extensively edit the patches (paths etc) to apply correctly to the source on my system and they don't work with Debain sources either. On top of that the sheer lack of documentation (especially if you're a sysadmin and not a python developer) is quite confusing. I haven't found any of the related sites (see below) to be of that much more use either. And where there is documentation related to mailman and exim, I've followed the instructions to the letter in terms of virtualhosts and still have no luck. I'm more than happy to put together whatever documentation is required if I can mine someone's brain who understands the source or how to make the patch sources work properly. What's also interesting is that in the Debian installation of mailman/exim the following files are created in /etc/exim4/conf.d specifically for virtualhosting but using them seems to be an arcane art. I can't seem to get the config working as implied by these files or find additional info about them: /etc/exim4/conf.d/router/420_exim4-config_virt_mailman /etc/exim4/conf.d/transport/50_exim4-config_virt_mailman Any assistance would be appreciated, thanks. (related sites) 1. http://wiki.koumbit.net/VirtualMailman?highlight=%28Virtual%29 2. http://www.exim.org/howto/mailman21.html 3. http://www.tty1.net/virtual_domains_en.html I did manage to get Neil Blakey-Milner's patch working briefly but it wasn't sufficient for my needs. I know him so I contacted him directly but he's unable to assist with tweaking the 2.1.7 patches to my needs. (Neil's original patches) 1. http://mithrandr.moria.org/blog/139.html 2. http://mithrandr.moria.org/blog/151.html -- | Bretton Vine | 083 633 8475 | bretton(a)hivemind.net | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "You have not converted a man because you have silenced him." - John Morley

2 1

Admin email on errors?
by Kurt Werle March 20, 2006

March 20, 2006

I have twice got the following error: --- Mar 14 22:41:58 2006 mailmanctl(54): The master qrunner lock could not be acquired. It appears as though there is a stale master qrunner lock. Try re-running mailmanctl with the -s flag. Mar 14 22:41:58 2006 mailmanctl(54): Mar 14 22:56:02 2006 mailmanctl(48): The master qrunner lock could not be acquired, because it appears as if some process on some other host may have acquired it. We can't test for stale locks across host boundaries, so you'll have to do this manually. Or, if you know the lock is stale, re-run mailmanctl with the -s flag. --- and I can live with that. What is a drag is the fact that it takes a user telling me "hey, why isn't list mail going out?" to find out that mailman has stopped processing. I don't see anywhere in the docs that mailman will send mail to the site admin in the event of a catastrophic error. Am I missing it? Has anyone hacked it in? Do I have to write a cron job that will poll the process list to see if mailman is still running? Has anyone written that already? TIA, Kurt -- kwerle(a)pobox.com http://www.pobox.com/~kwerle/ Tired of spam? Control your Mailserver (or .forward)? http://tess.sf.net

2 5

not archiving posts for one list
by debian March 20, 2006

March 20, 2006

Please, back in February, I set up a mailman (2.1.5 under debian testing) list here called pgc. I posted to it and everything went fine, including the archive of my post. But, now that I am going live, new posts are not visible from the mailman web pages. My original February post is there, but that is all. No postings appear for March. All other lists are working as normal. I have checked all the "archiving" options on the administrator's screen. I have recreated the list, to no avail. I have created another new list and everything is fine. I can browse to the archives: /var/lib/mailman/archives/pgc and all the postings are there. It is just that mailman does not display them. Thanks Joe.

2 3

Advice wanted on option to not include original post in notices
by Mark Sapiro March 20, 2006

March 20, 2006

There have been a couple of threads on the list in the last week or two regarding not sending the content of the original post in reject notices to the (alleged) poster and in owner notifications. I'm considering implementing these options for Mailman 2.2, but I want some feed back to be sure I'm doing what people want and to be sure I'm not overlooking things. Here are my areas of concern. First, should these be site wide mm_cfg.py options or should they be per-list options with a default from mm_cfg.py? In either case, the Defaults.py setting would match current behavior. I see a few different cases of messages including the original. Bounce processing sends unrecognized bounces to the owner if bounce_unrecognized_goes_to_list_owner is on. Since these notices are meaningless without the actual message, I think there is no need for an additional setting here. Also, if bounce_notify_owner_on_disable is on, the owner gets a copy of the triggering bounce, but this should always be a legitimate DSN in response to a message from the list, so I don't see a need to provide an option to exclude the DSN from the notification. The privacy options reject_these_nonmembers, generic_nonmember_action and header_filter_rules can automatically reject a post. Currently, the original post is included. I see a single option (should it be site wide or per list) to control putting the original in the reject notice. The moderator can reject a held post. Currently the original post is not included. I don't see a need to change this. If admin_immed_notify is on, notices of individual held posts are sent to the owners/moderators and these include the original post. I see an option separate from the reject option (and should this be site wide or per list) to put only summary information (From:, Subject: hold reason) in this notice. Note that this last can be 'almost' accomplished currently by turning admin_immed_notify off and increasing the frequency of the cron/checkdbs job from daily to maybe hourly, although this would affect all lists. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Confused About MIME Types
by edcarlsen＠cox.net March 20, 2006

March 20, 2006

All, I am a newbe to mailman and I may ask a dumb question, sorry. I have Mailman 2.1.5 and a list working well. I would like to send an attached PDF file to members on the list. I know there is "Content Filtering" to describe the types of MIME to not allow and they must start with multipart as: multipart/text I don't know MIME well enough to know which types I should not allow to be able to send PDF files attached to a email. Can you point me in the right direction? Thanks in advance. Ed Carlsen

2 1

Archive question
by Stewart, Tom March 20, 2006

March 20, 2006

I inherited a mailman system and need to move some monthly archives from a list called test to the actual mailing list. Both lists are on the same system. Everything I could find indicates to copy the file over to the public or private area and then run \arch --wipe maillistname. When I do that, it justs deletes the .txt and folder that I copied over. What am I missing? Thanks, Tom

2 1

Re: [Mailman-Users] Archive question
by Dragon March 20, 2006

March 20, 2006

Stewart, Tom sent the message below at 08:54 3/20/2006: >I inherited a mailman system and need to move some monthly archives from >a list called test to the actual mailing list. Both lists are on the >same system. > >Everything I could find indicates to copy the file over to the public or >private area and then run \arch --wipe maillistname. > >When I do that, it justs deletes the .txt and folder that I copied over. > >What am I missing? ---------------- End original message. --------------------- Do you have a valid .mbox file in the archive directory? (That directory will be something like /usr/local/mailman/archives/private/listname.mbox and the file in there will be called listname.mbox) If not, arch has nothing to work with as that is the file that the arch script uses to build the archive message files and index. If you want to build a single contiguous archive for both the previous list and the current one, you can concatenate the two .mbox files into a single file named with your list name and an .mbox extension. Once that is done, you can rebuild the archive using the arch script. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

errors after applying virtualhost patches to 2.1.7
by Bretton Vine March 20, 2006

March 20, 2006

After applying the following two patches to the mailman source, compiling and installing on Debian unstable I get the attached errors in my logfiles. Can anyone explain specifically what's going wrong? (The lists do still work though) ----------------------------------------------------------------- Mar 18 14:52:47 2006 (24312) Uncaught runner exception: global name 'Errors' is not defined Mar 18 14:52:47 2006 (24312) Traceback (most recent call last): File "/var/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 234, in ArchiveMail h.close() File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 327, in close self.update_dirty_archives() File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 543, in update_dirty_archives self.update_archive(i) File "/var/lib/mailman/Mailman/Archiver/HyperArch.py", line 1126, in update_archive self.__super_update_archive(archive) File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 447, in update_archive self._update_simple_index(hdr, archive, arcdir) File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 463, in _update_simple_index article = self.database.getArticle(self.archive, msgid) File "/var/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 285, in getArticle article = self.__cache[msgid] = pickle.loads(buf) File "/var/lib/mailman/Mailman/Archiver/HyperArch.py", line 379, in __setstate__ d['_mlist'] = self._open_list(listname) File "/var/lib/mailman/Mailman/Archiver/HyperArch.py", line 344, in _open_list except Errors.MMListError, e: NameError: global name 'Errors' is not defined ----------------------------------------------------------------- regards -- | Bretton Vine | 083 633 8475 | bretton(a)hivemind.net | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "When I am dead, I hope it is said, 'His sins were scarlet, but his books were read'." - Hillaire Belloc

2 2

Unable to post to announcement only list I have setup
by Jody Cleveland March 20, 2006

March 20, 2006

Hello, I've got a list setup where I only want moderators to be able to post to the list. I've got 5 addresses setup as moderators, but when I use one to post to the list, I get a bounce message: We're sorry, this is an announcement only list. We were unable to post your message. I know it must just be a setting I'm missing somewhere. Any ideas what may be wrong with my setup? - jody

2 1