Mailman 3 September 2004 - Mailman-Users

Hide list address?
by Ricardo Kleemann 16 Nov '23

16 Nov '23

Hi, Is there any way to configure Mailman such that, for an announcement-only type list, when a message is sent to the list, the To: shows the member's address, rather than the list address? Some list software allows the ability to hide the list address itself, so that address is not advertised. I couldn't find any configuration specific to that.

7 6

MSN and HotMail "Eating" Messages
by fshagan 24 May '07

24 May '07

Recently, my Mailman list users who use either a HotMail or MSN.COM email address have not received any messages. Mailman does not record a "bounce" from these email addresses, but they do not receive any of the list traffic. When trying to send a message to a Mailman list, the user gets the following error message: "This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed." And it lists the Mailman list email address. However, Mailman does not receive a bounce message. (My server is not listed with SpamHaus.org, or any of the other blacklists, so it should not be a spam filter sort of thing). One user requested help from MSN, and they responded with: "You are experiencing this issue because your .Net Passport <user's email address here> Profile (which is extensively used for authentication purposes) is corrupted (not updated). In order to resolve this issue, I would suggest you to Update your .NET passport profile." They follow that with instructions to go to their MSN .NET Passport profile and re-type all the information by hand (not by cut and paste). Then a 15-step procedure is given to delete all cookies, history and temporary internet files and re-set the disk cache (space for files) to 10MB. They believe that will solve the problem but alas, it has not for the 4 users I have with MSN or HotMail email addresses. Anyone else run into this and resolved it? I didn't see anything in the archives. If any of you have users with MSN or HotMail addresses, be advised they probably will not be able to receive emails, but you will not get "bounce" messages. They only way they will know is if they try to post to a Mailman list.

3 2

Membership Management And Other Problems.
by multimedia-fan＠myrealbox.com 21 Mar '06

21 Mar '06

Greetings, I cannot "Set everyone's moderation bit, including those members not currently visible" to on, in the membership management section in any list. I have set OWNERS_CAN_ENABLE_PERSONALIZATION = 1 In /Mailman/mm_cfgy.py But still have the same problem. Also I cannot set or unset digest for all users, any thing I overlooked? This was happening before the changes made in the next issue explained below. In the last couple of days we had to reconfigure reverse mapping in DNS for the server, and now the URLs that Mailman builds in the list admin and info pages are pointing to the old host name, is there a way of correcting this, without re-installing mailman from scratch? Any pointers, clues will be greatly appreciated. Thank you for your assistance.

2 5

Mailman 2.1.5 and virtualdomains and/or subdomains
by Konrad Mauz 08 Sep '05

08 Sep '05

Hi, I'm trying to setting up mailman and having trouble with virtualdomains and subdomains. I need a listing name schema of: xyz(a)a.fh-konstanz.de xyz(a)b.fh-konstanz.de xyz(a)c.fh-konstanz.de and so on. but I can only have "one" xyz list, since the domainname is not part of the "listname" My first workaround was: xyz(a)a.fh-konstanz.de is a-xyz(a)fh-konstanz.de and maps with sendmails virtusers and aliases database. Then I change the preferred hostname in the list configuration to a.fh-konstanz.de, but the sender adress is now a-xyz(a)a.fh-konstanz.de. Is there a better way to handle lists with equal names but different domain/subdomain names? With kind regards, Konrad -- Konrad Mauz Rechenzentrum Fachhochschule Braunegger-Strasse 55, D 78462 Konstanz e-mail: kmauz(a)fh-konstanz.de Tel.: +49(0)7531-206-472

4 5

Successful Panther (MacOS X 10.3) installation steps for Mailman
by Larry Stone 17 Jul '05

17 Jul '05

As requested by Brad, here is: Successful Panther (MacOS X 10.3) installation steps for Mailman This document best recalls my experience installing Mailman (2.1.4 but I assume this is equally valid for 2.1.5 which was current when this was written) on MacOS X 10.3 (Panther). It is largely based on Kathleen Webb's document on installing Mailman and Sendmail on MacOS X 10.2 (Jaguar) (<http://mail.python.org/pipermail/mailman-users/2002-October/022944.html>) which contains some information on tools that can be useful that will not be repeated here. This guide assumes that you have Postfix (which comes with Panther) already configured and operating and that you are familiar with the Unix shell and basic text editing from the shell (vi or emacs). It is intended to help you get Mailman installed. It does not deal with actually using Mailman as there are pleny of other sources of help for that. My notes are incomplete so updates and corrections are welcome. Questions are best asked through the mailman mailing list. ======================================== Step 1) Collect all the things you need. a) You need to download and decompress the Mailman software. (The installation instructions are in step 3.) Download the software from: http://www.list.org/ b) You need to be an administrator of your computer. If you do not have administrator privileges, you will not be able to do this. c) Python comes pre-installed on your computer. It is already functioning and ready for use by Mailman. (To verify you have Python, open the Terminal application. at the % prompt, type: sudo Python -V and then hit the enter/return key. You'll be prompted for your password. When you enter it, the terminal will respond with the Python version. d) Apache web server software comes pre-installed on your computer and has already been configured and is running. e) Postfix is already installed on your computer but is not running by default. You will need to get Postfix configured and started but how to do that is beyond the scope of this document. f) You may need to know how to get into hidden subdirectories. In the Finder, use the Go menu and choose Go to Folder. Type in the path to the hidden folder you need to open. g) You may need to know how to make a new user. You use the System Preferences application [from the Apple menu]. Use the Accounts panel in the System section. h) You need to know how to run the Net Info Manager application. [It is in the Utilities folder in the Applications folder.] You use this to create groups. i) You need to install the Developer Tools that came with your Panther disks or several of the steps won't work. ======================================== Step 2) Set up the user and group needed to run Mailman. I was surprised to find a mailman user already existed. I can only guess that is becuase mailman is included with Panther Server and the account "leaked" into the client version of Panther. Use Netinfo Manager (in Utilities inside Applications) to verify that it is using the following. If mailman does not yet exist, see Kathleen Webb's document to set it up. a) Open the Net Info Manager application. (It is located in the Utilities folder inside the Applications folder.) b) Click on groups in the second column. Click on mailman in the third column. Verify that in the bottom window you see a property "gid" with value 78. c) Click on users in the second column. Click on mailman in the third column. Verify that in the bottom window you see a property "uid" with value 78. Assuming all of the above is there, we're good to go. ======================================== Step 3) Create a folder for mailman in the finder. a) You can choose where to create the folder. I chose to make the mailman folder in the Applications folder. These instructions assume that is where you create the new folder. b) Copy the downloaded and uncompressed mailman-version (e.g. mailman-2.1.5) folder into the new mailman folder in the Applications folder. c) Click on the mailman folder and set the owner and group to mailman with the Show Info command. d) In the Terminal application, type: sudo chmod a+rw,g+ws /Applications/mailman e) Assuming the you are using the mailman-2.1.5 version, in the Terminal application type: cd /Applications/mailman/mailman-2.1.5 sudo ./configure --prefix=/Applications/mailman --with-cgi-gid=70 --with-mail-gid=78 (FYI: on my machine group 70 is www and group 78 is mailman) f) A whole bunch of lines of code will scroll through the Terminal window. When it finishes, in the Terminal window, type: sudo make install cd .. sudo bin/check_perms -f sudo bin/check_perms -f (Repeat the check_perms until no errors are reported. If you end up with problems later, this whole step is probably where the problem will come from. Permissions are important to Mailman.) ======================================== Step 4) Set up your web server to serve the Mailman web pages for subscribing and administrating the mailing list. a) From the Finder, use the Go menu and choose Go to Folder. Type in: /etc/httpd/ b) Select the httpd.conf file. Change its owner to you with Show Info. c) Open httpd.conf with a text editor. Alternatively, skip a and b and using Terminal, type sudo vi /etc/httpd.conf and edit the file with vi (or emacs if you know emacs). Add these lines to the file: ScriptAlias /mailman/ /Applications/mailman/cgi-bin/ Alias /pipermail/ /Applications/mailman/archives/public/ <Directory "/Applications/mailman/archives/public"> Options FollowSymLinks </Directory> d) Save the file and close it. Change the owner back to System with the Show Info if you changed it in step b. e) In the Terminal application, type: sudo su cd /Applications/mailman/cron crontab crontab.in exit sudo /Applications/mailman/bin/mmsitepass xxxx [Replace xxxx with the password you want to use as the master password to the mailman application.] ======================================== Step 5) Configure Postfix to support a separate Mailman alias file. a) Edit your Postix configuration file (/etc/postfix/main.cf) and add: alias_maps=hash:/etc/postfix/aliases, hash:/Applications/Mailman/data/aliases b) Reload postfix with: sudo postfix reload ======================================== Step 6) Configure Mailman a) We need to let Mailman know we're using Postfix. Using you favorite means of text editing, open /Applications/Mailman/mailman mm_cfg.py and add below the line that says "# Put YOUR site-specific settings below this line.": MTA = "Postfix" ======================================== Step 7) Create your site-wide mailing list (mailman). Read the instructions in INSTALL in your mailman source directory (/Applications/Mailman/Mailman-2.1.5). In short, in the Terminal application, type: sudo su cd /Applications/mailman bin/newlist mailman bin/config_list -i data/sitelist.cfg mailman ======================================== Step 8) Configure your system to start Mailman when it is booted. a) Open Terminal and change directory to /Library/StartupItems: sudo su cd /Library/StartupItems b) Create the Mailman startup directory: mkdir Mailman c) Verify the directory ownership and permissions: ls -l You should see one of the lines saying something like: drwxr-xr-x 5 root admin 170 12 May 11:21 Mailman d) If the permissions (rwxr-xr-x) are not correct, type: chmod 755 Mailman e) If the owner (root) or group (admin) is not correct, type: chown root:admin Mailman f) Change directory to the Mailman subdirectory (you will now be in /Library/StartupItems/Mailman): cd Mailman g) Using your favorite method of text editing, create the file Mailman (in /Library/StartupItems/Mailman) with the following contents: #!/bin/sh . /etc/rc.common StartService () { if [ "${MAILMAN:=-NO-}" = "-YES-" ]; then ConsoleMessage "Starting mailman service" cd /Applications/Mailman bin/mailmanctl -s start fi } StopService () { ConsoleMessage "Stopping mailman service" cd /Applications/Mailman bin/mailmanctl stop } RestartService () { if [ "${MAILMAN:=-NO-}" = "-YES-" ]; then ConsoleMessage "Restarting mailman service" cd /Applications/Mailman bin/mailmanctl restart else StopService fi } RunService "$1" h) Using your favorite method of text editing, create the file StartupParameters.plist (in /Library/StartupItems/Mailman) with the following contents: { Description = "Mailman mailing list server"; Provides = ("Mailman"); Requires = ("SMTP"); Uses = ("Network Time", "NFS"); Preference = "None"; Messages = { start = "Starting Mailman"; stop = "Stopping Mailman"; restart = "Reloading Mailman Configuration"; }; } i) Using you favorite method of text editing, open /etc/hostconfig and add the line: MAILMAN=-YES- j) Reboot (Restart) your system. When it finishes rebooting, Mailman should be running. To verify, open Terminal and type: ps -ax | grep python You should see a bunch of lines like this: 434 ?? Ss 0:00.04 python bin/mailmanctl -s start 443 ?? S 4:19.95 /usr/bin/python /Applications/Mailman/bin/qrunner --r 444 ?? S 4:08.58 /usr/bin/python /Applications/Mailman/bin/qrunner --r 445 ?? S 4:11.20 /usr/bin/python /Applications/Mailman/bin/qrunner --r 446 ?? S 4:06.93 /usr/bin/python /Applications/Mailman/bin/qrunner --r 447 ?? S 3:59.35 /usr/bin/python /Applications/Mailman/bin/qrunner --r 448 ?? S 4:16.59 /usr/bin/python /Applications/Mailman/bin/qrunner --r 449 ?? S 4:04.08 /usr/bin/python /Applications/Mailman/bin/qrunner --r 450 ?? S 0:00.85 /usr/bin/python /Applications/Mailman/bin/qrunner --r 16621 std R+ 0:00.00 grep -i python (The numbers will vary. The important thing is that you see the qrunner processes) ======================================== Step 9) Enjoy! At this point, mailman should be ready to use. Read the documentation in your source directory for instructions on setting up your mailing lists.

2 3

[Fwd: Re: [Mailman-Users] .signature to posts]
by Solignani Tiziano 15 Apr '05

15 Apr '05

Charles Sebold said: > On 24 Shevat 5762, Clark Cooper wrote: > >> Is there a way in Mailman to append text to each posts as done with a >> .signature file? > > On the web admin interface, go to page "Regular-member (non-digest) > Options" and change the option labeled "Footer added to mail sent to > regular list members". Is that what you were after? > -- > Charles Sebold 25th of Shevat, BTW how can I add taglines, i.e. random strings picked frpm a text file where they lies every one on a separate line. ALmost every list manager has tag lines administration, but I did not find them in mailman... Cheers, ---- Avv. Tiziano Solignani via Bonesi n. 15 - Vignola (MO) tel. 059 76.19.26 - fax 059 77.04.535 mail: solignani(a)solignani.it web: http://www.solignani.it chat: avv_tiziano_solignani(a)hotmail.com PC Open magazine - www.pcopen.agepe.it "rarest jewel is a true heart" -- ---- Avv. Tiziano Solignani via Bonesi n. 15 - Vignola (MO) tel. 059 76.19.26 - fax 059 77.04.535 mail: solignani(a)solignani.it web: http://www.solignani.it chat: avv_tiziano_solignani(a)hotmail.com PC Open magazine - www.pcopen.agepe.it "rarest jewel is a true heart"

2 1

Where is 'reject' message stored
by Warren Hoffman 24 Jan '05

24 Jan '05

One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments. Thanks!!! --Warren

4 3

Upgrade hell (Debian)
by Deirdre Saoirse Moen 05 Jan '05

05 Jan '05

Upgrade script broke (not the first time). from Mailman import MailList from Mailman.LockFile import TimeOutError from Mailman.i18n import _ I'm getting error: Traceback (most recent call last): File "/usr/lib/mailman/bin/update", line 51, in ? from Mailman.i18n import _ ImportError: No module named i18n It doesn't balk on the line before, so it doesn't seem to be a path issue. When I comment that line out (for grins), it balks on: from Mailman.Queue.Switchboard import Switchboard from Mailman import OldStyleMemberships from Mailman.MemberAdaptor import BYBOUNCE, ENABLED Any clues? -- _Deirdre http://deirdre.net "Cannot run out of time. There is infinite time. You are finite. Zathras is finite. This....is wrong tool." -- Zathras

2 2

Re: [Mailman-Users] Problems with relocating a list
by Kevin W. Gagel 20 Nov '04

20 Nov '04

You probably followed some of my instructions. I've not had a chance to get back to update them. In the mailman list directories you'll find that there are links to the archives. I had the same issue after I did mine, it took a bit to figure it out but simply deleting the links and making new ones to the correct location on the new machine fixed it for me. ----- Original Message Follows ----- From: Anthony Chavez <acc(a)anthonychavez.org> To: mailman-users(a)python.org Subject: [Mailman-Users] Problems with relocating a list Date: Tue, 21 Sep 2004 12:49:13 -0600 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Moving a Mailman list from one server to a new one has been a *very* > smooth process for the most part, but I'm noticing some small quirks in > the wake. > > Here's an account of how I accomplished this. > > 1. Installed Mailman 2.1.5, Postfix 2.1.4, and Apache 2.0.50 on the new > server. These versions exactly match the ones on the old server. > > 2. Went through the process dictated in FreeBSD-post-install-notes, > INSTALL, README, and README.POSTFIX, which essentially involved > editing main.cf, httpd.conf, adding MTA = 'Postfix' to mm_cfg.py and > creating the "mailman" list. > > 3. Under the direction of section 3.4 in the FAQ Wizard, I copied the > data, archives and lists directories from the old server to the new > one. But rather than clobbering the pre-existing directories, I > copied only the *relevant* directories from archives and lists > (i.e. archives/private/listname* and lists/listname). Nothing was > copied from data and the "mailman" list was not copied. > > 4. Ran withlist -l -r fix_url listname && genaliases > > 5. Started postfix and qrunner. > > 6. Configured Apache on the old site to proxy and Postfix to relay to > the new server while DNS changes propagated. > > Now, the aforementioned quirks: > > 1. The old lists are not advertised on the new Web site. > > 2. Apache will not let me access the public archives (that were private > before the move) and I get a 403. I'm sure this has to do with > Apache 2's default deny policy, but not entirely sure how to deal > with it (I'm still somewhat of an Apache 2 newbie, but I've had a few > years experience with 1.x). > > Any assistance would be greatly appreciated. > > Cheers! > > - -- > Anthony Chavez http://www.anthonychavez.org/ > mailto:acc@anthonychavez.org jabber:acc@jabber.anthonychavez.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (Darwin) > > iD8DBQFBUHesbZTbIaRBRXERAoIGAJ0fYE5OA0qsowSA8C15dZ+J/dlGdQCeNbEQ > M0fmXySbfdTfpReNuH3/2hw= > =kfs3 > -----END PGP SIGNATURE----- > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)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/ ==================== Kevin W. Gagel Network Administrator (250) 561-5848 local 448 (250) 562-2131 local 448 -------------------------------------------------------------- The College of New Caledonia, Visit us at http://www.cnc.bc.ca Virus scanning is done on all incoming and outgoing email. --------------------------------------------------------------

3 4

Translation problem
by Luis Fernando C. Talora 17 Oct '04

17 Oct '04

Friends, I´m using some lists in Brazilian Portuguese and noticed some translation errors. Trying to correct some of those errors, I´ve made a few changes on the file /var/mailman/messages/pt_BR/LC_MESSAGES/mailman.po None of the changes I´ve made seemed to appear on the Mailman web interface. Do someone know what am I doing wrong? Thanks! _______________________ Luís Fernando C. Talora ========================================================= Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação. This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. =========================================================

3 2