Mailman-Users July 2008

mailman-users@python.org

114 participants
148 discussions

Add "sender's name/email" to BODY of mail as header?

by Mal

I want all mails sent to the list to come from the list's email address... But, in this case, if the user forgets to sign their name at the bottom of their mail body, effectively the mail to the list is anonymous...! Is there a way to add the user name (or email address) to the top of each mail so that the mails have the name of the sender, while the mail itself comes from the list address? I have looked high and low for an answer, but noone seems to have the solution. Thank you! Mal

11 months, 2 weeks

Setting MIME as default for new Non-Digest subscribers

by Steve Reiter

Hi - I have searched FAQ and archives to find an answer. Hoping you can help. I have a new list (with previously imported addresses) for announcements only, and wish these announcements to be received immediately. I set the defaults to allow non-digest and to not allow digest. I wish to send out announcements in html, and so wish to make the default for new subscribers be MIME. While I see a setting under Digest Options (MIME_is_Default_Digest), I don't see any equivalent option under Non-Digest Options... and new subscribers continue to come in as plain text. QUESTIONS: In order to avoid having to manually change this option for each existing subscriber, is there a way to force all existing subscribers to receive MIME in Non-Digest mode? If not, is there a way to force all NEW subscribers to be enrolled with MIME as their default? Also, is there a way to "lock" the MIME switch on, so that users who try to change their option to plain text will be prevented from doing so? Thanks - Steve

10 years, 6 months

Changing the received time on an outgoing authorized email message?

by Paul Key

When authorizing a moderated list posting is it possible to change the date/time on the outgoing authorized list message to the time it was approved instead of the message showing the time it was first received by mailman? Thanks Paul

11 years, 4 months

not really an umbrella?

by Gruver, Sandi

Mailman 2.1.5 on RedHat Linux - How can I set up a new list that sends to multiple existing lists - but only sends one message to each person - even if the person is a member of multiple lists? a. LSOFT calls this a "superlist" b. Can "Mailman" do this? c. In this case, we have a system newsletter that will be sent to multiple lists. I'd like people to receive the message only once, even if they are on more than one of the lists included in the mailing. Thank you, Sandi Gruver Unix system administrator Center for Information Services Bellevue, WA 98004 phone 425.803.9753 fax 425.803.9652

11 years, 11 months

Mailman/Qmail/Plesk Problem

by Douglas G. Phillips

OK, I've got another problem with Qmail/Plesk/Mailman (same customer, rebuilt server). Plesk is 7.5.4 reloaded. Mail delivered fails with "need GID 110 got 101" error. I set up the brute-force wrapper to deliver with GID 110, and set the permissions correctly for it to work. Now, I'm getting the following (broken up into multiple lines for courtesy): qmail: 1157518628.995172 delivery 726: success: group_mismatch_error._Mailman_expected_the_mail_wrapper_script_to_be/ executed_as_one_of_the_following_groups:/[mail,_nobody,_mailman],/ but_the_system's_mail_server_executed_the_mail_script_as_group:_"popuser"./ Try_tweaking_the_mail_server_to_run_the_script_as_one_of_these_groups:/ [mail,_nobody,_mailman],/or_re-run_configure_providing_the_ command_line_option:/'--with-mail-gid=popuser'./Failed_to_start_ /usr/lib/mailman/mail/mailman./did_0+0+1/ I'm about ready to pull my hair out. I even added the popuser user to the mailman group in /etc/passwd. So, that being said, are there any ideas out there? I have been messing with this for a week, and have not come up with anything else to do. -- Douglas G. Phillips Simple Business Solutions ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

12 years, 6 months

Problem with Underscores

by David Relson

I'm running Mailman 2.1.8 and have encountered a problem with email addresses starting with underscores. Using a python script to show list members, the first three members of a list are: 6louisc(a)example.com _santasal(a)example.com a1bformk(a)example.com Using mailman's admin interface, web page http://localhost/mailman/admin/mylist/members has the following: 219 members total, 1 shown [6] A B C D E F G H I J K L M N O P Q R S T U V W Y Z Note that the script shows a user whose name begins with an underscore but the admin interface indicates names beginning with "6" and "A" but none with "_". Is there a patch that fixes this? If not, I'll create one if somebody can point me towards the admin module that determines the "6ABC..." list above? Regards, David

13 years, 5 months

How many domain in one list of mailing list?

by Maickel Pandie

Hi friend, I have some question. in average, How many domain in one list of mailing list in your server? because refer to RFC 2821 message always be sent once for one domain For corporate mailing list how many domain in average? For public mailing list how many domain in average?

13 years, 6 months

MAX_MESSAGE_SIZE limit

by hone+mailman＠oak.cats.ohiou.edu

How would I set a MAX_MESSAGE_SIZE to 5MB, for example, for all lists? Or would this need to be done in the MTA? I would leave the DEFAULT_MAX_MESSAGE_SIZE to 40 KB, but don't want list owners to set it to 0 (unlimited). Don Hone <http://edirectory.ohio.edu/?$search?uid=hone> Ohio University

13 years, 6 months

Re: [Mailman-Users] Receiving filtered commit messages via a Handler

by Alexander Shopov

> Put the handler in the pipeline before Moderate and set Thanx. Worked like a wonder. al_shopov

13 years, 6 months

Re: [Mailman-Users] Permissions on Symbolic Links Files

by b19141＠anl.gov

I wrote (>>): with Mark Sapiro's comments interspersed (>): >>I have on my Mailman 2.1.10 production system and my 2.1.11 test system >>both created from the SourceForge source and installed on Ubuntu dapper >>via packages I built: >> >>mailman% ls -al /var/lib/mailman >>total 40 >>drwxrwsr-x 10 root list 4096 2007-02-28 11:11 . >>drwxr-xr-x 22 root root 4096 2008-04-04 13:31 .. >>lrwxrwxrwx 1 root root 20 2008-06-30 16:13 bin -> /usr/lib/mailman/bin >>lrwxrwxrwx 1 root root 21 2008-06-30 16:13 cron -> /usr/lib/mailman/cron >>lrwxrwxrwx 1 root root 24 2008-06-30 16:13 Mailman -> /usr/lib/mailman/Mailman >>lrwxrwxrwx 1 root root 24 2008-06-30 16:13 scripts -> /usr/lib/mailman/scripts >><<Non-relevant lines from the "ls -al" listing have been removed.>> >>mailman% >>mailman# ls -al /usr/lib/mailman >>total 36 >>drwxr-xr-x 7 root list 4096 2007-02-28 11:11 . >>drwxr-xr-x 48 root root 12288 2008-06-09 12:24 .. >>drwxr-xr-x 2 root list 4096 2008-07-23 14:55 bin >>drwxr-xr-x 2 root list 4096 2008-07-23 14:55 cron >>drwxrwsr-x 2 root list 4096 2008-07-23 14:55 mail >>drwxr-xr-x 11 root list 4096 2008-07-23 14:55 Mailman >>drwxr-xr-x 2 root list 4096 2008-07-23 14:55 scripts >>mailman# >> >>When I run check_perms it complains: >> >> mailman# check_perms >> directory permissions must be 02775: /var/lib/mailman/Mailman >> directory permissions must be 02775: /var/lib/mailman/bin >> directory permissions must be 02775: /var/lib/mailman/cron >> directory permissions must be 02775: /var/lib/mailman/scripts >> Problems found: 4 >> Re-run as list (or root) with -f flag to fix >> mailman# >> >>As Mailman is running fine, I do not want to change the permissions >>on the symbolic links. Is this correct? I have 755 for the permissions >>on the real files to which the symbolic links point. >You can't change the permissions on a symlink itself anyway. Any >attempt to do so will attempt to change the target. >>Is check_perms reporting on the permissions of the symlinks or the >>permissions of the real files to which the symbolic links point? >The targets. >>What problems would I see if I do not have group write not "02" >>on these four files? >Typically these directories are SETGID and group writable. The fact >that they are not SETGID means that anything created subordinate to >them will be created with the group of the creator and not the 'list' >group. In practice the contents of these 4 directories are normally >only read, so as long as everything is world readable, it will work. > >But if you applied a patch to some .py file in the Mailman directory, >Mailman processes running as group 'list' might not have permission to >update the corresponding .pyc file. > >I have to wonder why you are doing this with symlinks at all. It looks >like what you really want is to run configure with > >--prefix=/usr/lib/mailman (the default), and >--with-var-prefix=/var/lib/mailman > >or something similar. When I built my Mailman 2.1.9 and .11 packages for Ubuntu dapper, I took the Ubuntu packaging and made as few changes as possible. All I wanted was that the files be placed in the correct directories for Ubuntu. I used the current source, and I removed all of the Debian/Ubuntu patches except one: 01_defaults.debian.dpatch that makes three changes to the file Mailman/Defaults.py.in: -IMAGE_LOGOS = '/icons/' +IMAGE_LOGOS = '/doc/mailman/images/' -DEFAULT_URL_PATTERN = 'http://%s/mailman/' +DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' -PIDFILE = os.path.join(DATA_DIR, 'master-qrunner.pid') +PIDFILE = "/var/run/mailman/mailman.pid" The other patch files were source changes that I did not want because they were undocumented, and I had no idea for which SourceForge code base they were written. I assumed that the SourceForge source needed no patches. In the file mailman-2.1.11/debian/rules I made a few changes: mailman# diff rules rules.original 38c38 < --with-mail-gid=list --with-cgi-gid=www-data \ --- > --with-mail-gid=daemon --with-cgi-gid=www-data \ 70,71c70 < # The following line was commented by BSFinkel 07/01/2008. < # Debian removs pythonlib in error to fix a problem. < # rmdir debian/$(package)/var/lib/mailman/pythonlib --- > rmdir debian/$(package)/var/lib/mailman/pythonlib 126,128c125 < # The following line was commented by BSFinkel 07/01/2008 because < # the directory "admin" does not exist in Mailman 2.1.10 nor .11. < # cp -a admin/www debian/mailman/usr/share/doc/$(package)/html --- > cp -a admin/www debian/mailman/usr/share/doc/$(package)/html mailman# Of course, the admin line was only commented in 2.1.11, not in 2.1.9. That rules file has two sections of code: ----- Makefile: autoconf ./configure --prefix=/var/lib/$(package) --with-username=list \ --with-groupname=list \ --with-mail-gid=list --with-cgi-gid=www-data \ --without-permcheck --with-mailhost=localhost \ --with-urlhost=localhost ----- binary-arch: checkroot build $(checkdir) # rm -rf debian/mailman && install -d debian/mailman dh_installdirs dh_installdocs ACKNOWLEDGMENTS README* TODO BUGS NEWS FAQ dh_installchangelogs $(MAKE) doinstall prefix=$$(pwd)/debian/mailman/var/lib/$(package) \ var_prefix=$$(pwd)/debian/mailman/var/lib/$(package) \ icondir=$$(pwd)/debian/mailman/usr/share/images/mailman \ ICONDIR=$$(pwd)/debian/mailman/usr/share/images/mailman ----- and I did not want to make any changes to the directories into which Ubuntu/Debian stores the Mailman files. I am assuming that with a straight Debian/Ubuntu package install the same symlinks and directories that I have are present therein. Can someone who has an unmodifed Debian/Ubuntu package for Mailman confirm this? Thanks. I ran the fixup: mailman# check_perms directory permissions must be 02775: /var/lib/mailman/Mailman directory permissions must be 02775: /var/lib/mailman/bin directory permissions must be 02775: /var/lib/mailman/cron directory permissions must be 02775: /var/lib/mailman/scripts Problems found: 4 Re-run as list (or root) with -f flag to fix mailman# check_perms -f directory permissions must be 02775: /var/lib/mailman/Mailman (fixing) directory permissions must be 02775: /var/lib/mailman/bin (fixing) directory permissions must be 02775: /var/lib/mailman/cron (fixing) directory permissions must be 02775: /var/lib/mailman/scripts (fixing) Problems found: 4 Re-run as list (or root) with -f flag to fix mailman# !! check_perms -f No problems found mailman# ls -al /var/lib/mailman/Mailman lrwxrwxrwx 1 root root 24 2008-06-30 16:13 /var/lib/mailman/Mailman -> /usr/lib/mailman/Mailman mailman# ls -al /var/lib/mailman/bin lrwxrwxrwx 1 root root 20 2008-06-30 16:13 /var/lib/mailman/bin -> /usr/lib/mailman/bin mailman# ls -al /var/lib/mailman/cron lrwxrwxrwx 1 root root 21 2008-06-30 16:13 /var/lib/mailman/cron -> /usr/lib/mailman/cron mailman# ls -al /var/lib/mailman/scripts lrwxrwxrwx 1 root root 24 2008-06-30 16:13 /var/lib/mailman/scripts -> /usr/lib/mailman/scripts mailman# ls -ald /usr/lib/mailman/Mailman drwxrwsr-x 11 root list 4096 2008-07-23 14:55 /usr/lib/mailman/Mailman mailman# ls -ald /usr/lib/mailman/bin drwxrwsr-x 2 root list 4096 2008-07-23 14:55 /usr/lib/mailman/bin mailman# ls -ald /usr/lib/mailman/cron drwxrwsr-x 2 root list 4096 2008-07-23 14:55 /usr/lib/mailman/cron mailman# ls -ald /usr/lib/mailman/scripts drwxrwsr-x 2 root list 4096 2008-07-23 14:55 /usr/lib/mailman/scripts mailman# ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

13 years, 6 months

Jump to page: