Re: [Mailman-Users] Hello Question about compile error under OS X10.4.2
According to Mark Sapiro, on 11-9-05 21:23 the word on the street was... See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.021.htp and in particular the linked post at http://mail.python.org/pipermail/mailman-users/2005-July/045693.html Thanks, but I already found those articles and followed their instructions -- they work well until I run make install and encounter this error :( I think you can simply edit /usr/local/mailman/bin/paths.py That was the first thing I tried, without success ... And as I'm trying again now, I've just completed the make step, but can only find paths.py in /usr/local/mailman-2.1.6/misc/ (which is the dir I'm installing from, not to). *some waiting later* Strangely, but happily, it worked now. I have no idea what I did wrong first time round, but make install just exited without errors. Thanks :) Time to get on with the rest of the install :) -- Jakko Westerbeke [EMAIL PROTECTED] http://www.xs4all.nl/~gurth/afv -- 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] Uncaught runner exception: 'utf8' codeccan'tdecode bytes in position 1-4: invalid data
Mark, I found the problematic email, look at this:
...more mail data here
--TB36FDmn/VVEgNH/
Content-Type: application/msword
Content-Disposition: attachment;
filename*=utf-8''C%F3mo%20montar%20un%20servidor%20Samba%20PDC%20en%20una%20red%20de%20m%E1quinas%20MS%20Windows%20XP%
Content-Transfer-Encoding: base64
...more mail data here
--- Mark Sapiro [EMAIL PROTECTED] wrote:
Aliet Santiesteban Sifontes wrote:
Thank's Mark, how could I find the bad message,
You have to look through the digest.mbox file and
find
Content-Disposition: headers. Typically, such a
header might look like
Content-Disposition: attachment;
filename=Some_name.ext
In your case, the value of the filename= will look
garbled.
I'm
worried because If I can make the list work again,
I
have the risk this happens again, is there any
patch
for this??. I think that this can be a potencial
dos
attack to other lists on the net.
There is no patch that I know of. The actual error
occurs in the Python
email library, not in Mailman. The code has changed
between Mailman
2.1.5 and 2.1.6, but not in a way that I think would
avoid the
exception.
You could try replacing the line
fnext =
os.path.splitext(msg.get_filename(''))[1]
in /var/lib/mailman/Mailman/Handlers/Scrubber.py
with
try:
fnext =
os.path.splitext(msg.get_filename(''))[1]
except UnicodeDecodeError:
fnext = ''
--
Mark Sapiro [EMAIL PROTECTED] The highway is
for gamblers,
San Francisco Bay Area, Californiabetter use
your sense - B. Dylan
__
Yahoo! for Good
Donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
--
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] Complaints about MM 2.1.6b4
Thanks for the information. Let me ask one more question along this track of new things mailman 2.1.x included that was done differently than 2.0.x. Under the membership management section, up to some number of e-mail addresses, mailman splits the e-mail addresses into alphabetized sections. One of our list admins would like to have mailman show all of the e-mail addresses in a single window, if possible, or into multiple windows of 50 or 100 e-mail address chunks. The list admin complains that he has to click on the first letter of each section of e-mail addresses to change a setting. Is there a way to do this with mailman 2.1.6b4 with a option in the default.py file or is this something I would have to submit to the mailman developers as a new feature? Regards, Darren Old Dominion University On Fri, 2005-09-09 at 18:38, Mark Sapiro wrote: Darren G Pifer I believe she is saying is that if she is a member of her own list, she still has to approve the message before it goes out. If she was not a member of list and was in the non-member list of addresses for her list, then the mail would go out without approval. I don't know this affects MM processing, if the member address member name has the mod flag set, and she sends to her list, will it still be held for approval? Yes, and that appears to be the issue here. If she is a moderated member, her posts are supposed to be held for approval (or otherwise disposed of according to member_moderation_action). That's what moderated means. It makes no difference whether she is a list owner or moderator herself. If she is moderated, the only way she can post without the post being held is to include an Approved: list_administrator_password line in her post either as a header or as an initial body line. If included in the body, it is best to make it the first line and follow it with a blank line as at least some Mailman versions will remove the line following when removing the Approved: line from the post. Also, she is correct that in Mailman 2.1.x there is no list per se of members who are allowed to post without moderation. You have to turn off moderation individually for those members who you want to post without moderation. It would be simple for someone who knows Mailman and Python to create a withlist script that would turn off moderation for a list of members, but as far as I know there isn't one currently available. In another post in this thread Darren wrote: On Tue, 2005-09-06 at 10:29, Brad Knowles wrote: The newest problem is: Because Classroom is a shared email account, it shows the real sender - who is a member of the list with a check-mark in the MOD box, so it holds the email and waits for administrator approval. Make sure that your MUA properly uses the desired sender address as both the envelope sender and in the header From: and Sender: fields. Or, go into your mm_cfg.py file and change what fields you look at for determining list membership. If you don't have explicit settings for this, see the examples from Defaults.py, then copy them over to mm_cfg.py and change as necessary for your installation. These are settings for envelope sender from Defaults.py which is looking like it is doing the right thing. The setting in Defaults.py is 'USE_ENVELOPE_SENDER = No' which says use the headers as specified in SENDER_HEADERS. How can we confirm that the MUA is doing the right thing? Would this be one of the mailers sendmail would be using, like mlocal? The MUA is the 'user agent' (also called e-mail client) that the user uses to compose and send the mail. This is normally what sets fields such as From: and envelope sender in a mail message. If users want to post using the classroom address, they may need to set up a separate 'account' in their MUA to post from. You can verify what is being done by having them send to you and examining the full headers of the message you receive. Note that there should be a Return-Path: header indicating the envelope sender. But note, It will be only a very short time before students figure out how to post from 'classroom'. That's why this method is not recommended as a secure posting method on a one-way or few-to-many type of list. The secure way to do this is by moderating everyone and giving authorized posters the list password so they can post with an Approved: header. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.034.htp -- Mark Sapiro [EMAIL PROTECTED] 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Mail List Password
I have forgotten the password to one of my mail lists. For the life of me I can't seem to find a way to reset the password. Any help? The control panel would be Plesk 7 -- 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] Mail List Password
Phil, Try the command change_pw in your mailman bin directory. Here's the output of change_pw --help Usage: change_pw [options] Options: --all / -a Change the password for all lists. --domain=domain -d domain Change the password for all lists in the virtual domain `domain'. It is okay to give multiple -d options. --listname=listname -l listname Change the password only for the named list. It is okay to give multiple -l options. --password=newpassword -p newpassword Use the supplied plain text password `newpassword' as the new password for any lists that are being changed (as specified by the -a, -d, and -l options). If not given, lists will be assigned a randomly generated new password. --quiet / -q Don't notify list owners of the new password. You'll have to have some other way of letting the list owners know the new password (presumably out-of-band). --help / -h Print this help message and exit. -- Matt Ryanczak American Registry for Internet Numbers Lead System Administrator On Mon, 2005-09-12 at 13:15 -0400, Phil wrote: I have forgotten the password to one of my mail lists. For the life of me I can't seem to find a way to reset the password. Any help? The control panel would be Plesk 7 -- 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/ryanczak%40arin.net 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] patch to add date to each meassge in mail archiveIndex
Matt Ryanczak wrote: I was asked to make the date for each message in a mailman archive be visible in the index for that month. This required that I modify HyperArch.py and the template file archidxentry.html. I thought others might find this useful so here are the relevant patches for the mailman-2.1.6 source tree. I apologize if this is a duplication of someone else efforts, I searched around and could not find a way to do this in mailman as it was or a patch to do the same. Thanks for developing this patch. It would help for tracking and possible adoption into the base if you would submit it to the Mailman patch tracker at http://sourceforge.net/tracker/?group_id=103atid=300103 You might also add a note to the RFE at http://sourceforge.net/tracker/index.php?func=detailaid=843141group_id=103atid=350103 -- Mark Sapiro [EMAIL PROTECTED] 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://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
[Mailman-Users] Help with Qmail
HI
I have qmail with Centos 3.5, I am trying to install mailman 2.1.6, but
when i send a mail i get this error:
Hi. This is the qmail-send program at ns.asoban.bo.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
[EMAIL PROTECTED]:
vdeliver: Invalid or unknown virtual user 'lista3'
I followed the guide GNU - Mailman and this is my configuration
in Defaults.py
DEFAULT_EMAIL_HOST = 'ns.mydomain.bo'
DEFAULT_URL_HOST = 'ns.mydomain.bo'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
in mm_cfg.py
add_virtualhost('www.mydomain.bo','mydomain.bo')
I create the list whit this command
./newlist --urlhost=www.mydomain.bo --emailhost=mydomain.bo lista3
and add the following to /etc/aliasses
## lista3 mailing list
lista3: |/usr/local/mailman/mail/mailman post lista3
lista3-admin:|/usr/local/mailman/mail/mailman admin lista3
lista3-bounces: |/usr/local/mailman/mail/mailman bounces lista3
lista3-confirm: |/usr/local/mailman/mail/mailman confirm lista3
lista3-join: |/usr/local/mailman/mail/mailman join lista3
lista3-leave:|/usr/local/mailman/mail/mailman leave lista3
lista3-owner:|/usr/local/mailman/mail/mailman owner lista3
lista3-request: |/usr/local/mailman/mail/mailman request lista3
lista3-subscribe:|/usr/local/mailman/mail/mailman subscribe lista3
lista3-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe lista3
Could anyone help me to identified where is the problem?
Thank you
Fabricio Vargas
--
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] patch to add date to each meassge in mail archiveIndex
I was looking for a solution to put the date available in the archives. I have completed the patch as described and get an error when I rebuild my archives - - - File /opt/mailman/Mailman/Archiver/HyperArch.py, line 1005, in write_index_entry datestr = self.get_header(datestr, article) File /opt/mailman/Mailman/Archiver/HyperArch.py, line 1027, in get_header return getattr(article, field) AttributeError: Article instance has no attribute 'datestr' - - - Anyone able to help me with this? --- Andrew Smith Web Developer Tyndale University College Seminary 416-226-6620 (2714) -- [EMAIL PROTECTED] http://www.tyndale.ca http://www.tyndale.ca/it http://www.tyndale.ca/~asmith -- 25 Ballyconnor Court Toronto, Ontario. M2M 4B3 -- Tyndale's Mission is to educate and equip Christians to serve the world with passion for Jesus Christ. --- Mark Sapiro [EMAIL PROTECTED] 9/12/2005 2:06:52 PM Matt Ryanczak wrote: I was asked to make the date for each message in a mailman archive be visible in the index for that month. This required that I modify HyperArch.py and the template file archidxentry.html. I thought others might find this useful so here are the relevant patches for the mailman-2.1.6 source tree. I apologize if this is a duplication of someone else efforts, I searched around and could not find a way to do this in mailman as it was or a patch to do the same. Thanks for developing this patch. It would help for tracking and possible adoption into the base if you would submit it to the Mailman patch tracker at http://sourceforge.net/tracker/?group_id=103atid=300103 You might also add a note to the RFE at http://sourceforge.net/tracker/index.php?func=detailaid=843141group_id=103atid=350103 -- Mark Sapiro [EMAIL PROTECTED] 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://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/asmith%40tyndale.ca Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] mailman stopped working after upgrade
Mailman was working, then a (Gentoo) 'emerge -Davu system' update happened the other day and looks like it broke mailman. daevid portage-logs # ll *mailman* -rw-r--r-- 1 root root 62662 Sep 7 11:34 3485-mailman-2.1.5-r4.log -rw-r--r-- 1 root root 1105 Sep 7 11:34 3486-mailman-2.1.5-r4.log Sep 12 12:16:19 [Mailman mail-wrapper] Group mismatch error. Mailman expected the mail_wrapper script to be executed as group mailman, but_the system's mail server executed the mail script as_group mail. Try tweaking the mail server to run the_script as group mailman, or re-run configure, _providing the command line option `--with-mail-gid=mail'._ Sep 12 12:16:19 [exim] 2005-09-12 12:16:19 1EEtms-00021M-60 ** |/usr/local/mailman/mail/mailman post rbc [EMAIL PROTECTED] R=system_aliases T=address_pipe: Child process of address_pipe transport returned 2 from command: /usr/local/mailman/mail/mailman daevid bin # locate mail_wrapper daevid bin # locate as_group daevid portage-logs # ll /usr/local/mailman/mail/mailman -rwxr-sr-x 1 mailman mailman 7768 Sep 7 11:34 /usr/local/mailman/mail/mailman daevid bin # ll total 372 drwxrwsr-x 2 mailman mailman 4096 Sep 7 11:34 . drwxrwsr-x 20 mailman mailman 4096 Apr 4 13:52 .. -rwxr-xr-x 1 mailman mailman 7612 Sep 7 11:34 add_members -rwxr-xr-x 1 mailman mailman 5406 Sep 7 11:34 arch -rw-r--r-- 1 mailman mailman 3748 Sep 7 11:34 auto -rwxr-xr-x 1 mailman mailman 2559 Sep 7 11:34 b4b5-archfix -rwxr-xr-x 1 mailman mailman 6130 Sep 7 11:34 change_pw -rwxr-xr-x 1 mailman mailman 4264 Sep 7 11:34 check_db -rwxr-xr-x 1 mailman mailman 12223 Sep 7 11:34 check_perms -rwxr-xr-x 1 mailman mailman 6632 Sep 7 11:34 check_perms_grsecurity.py -rwxr-xr-x 1 mailman mailman 5492 Sep 7 11:34 cleanarch -rwxr-xr-x 1 mailman mailman 6409 Sep 7 11:34 clone_member -rwxr-xr-x 1 mailman mailman 12326 Sep 7 11:34 config_list -rwxr-xr-x 1 mailman mailman 1499 Sep 7 11:34 convert.py -rwxr-xr-x 1 mailman mailman 3238 Sep 7 11:34 discard -rwxr-xr-x 1 mailman mailman 4399 Sep 7 11:34 dumpdb -rwxr-xr-x 1 mailman mailman 4951 Sep 7 11:34 find_member -rwxr-xr-x 1 mailman mailman 2633 Sep 7 11:34 fix_url.py -rw-r--r-- 1 mailman mailman 2497 Apr 4 13:52 fix_url.pyc -rwxr-xr-x 1 mailman mailman 3097 Sep 7 11:34 genaliases -rwxr-xr-x 1 mailman mailman 2815 Sep 7 11:34 inject -rwxr-xr-x 1 mailman mailman 2561 Sep 7 11:34 list_admins -rwxr-xr-x 1 mailman mailman 3329 Sep 7 11:34 list_lists -rwxr-xr-x 1 mailman mailman 8316 Sep 7 11:34 list_members -rwxr-xr-x 1 mailman mailman 3165 Sep 7 11:34 list_owners -rwxr-xr-x 1 mailman mailman 21124 Sep 7 11:34 mailmanctl -rw-r--r-- 1 mailman mailman 18995 Sep 7 11:34 majordomo2mailman.pl -rw-r--r-- 1 mailman mailman 5951 Sep 7 11:34 mm-handler -rw-r--r-- 1 mailman mailman 7048 Sep 7 11:34 mm-handler.readme -rwxr-xr-x 1 mailman mailman 2989 Sep 7 11:34 mmsitepass -rwxr-xr-x 1 mailman mailman 5530 Sep 7 11:34 msgfmt.py -rwxr-xr-x 1 mailman mailman 7127 Sep 7 11:34 newlist -rw-r--r-- 1 mailman mailman 2412 Sep 7 11:34 paths.py -rw-r--r-- 1 rootmailman 652 Sep 7 11:34 paths.pyc -rwxr-xr-x 1 mailman mailman 4076 Sep 7 11:34 qmail-to-mailman.py -rwxr-xr-x 1 mailman mailman 9196 Sep 7 11:34 qrunner -rwxr-xr-x 1 mailman mailman 2957 Sep 7 11:34 rb-archfix -rwxr-xr-x 1 mailman mailman 4699 Sep 7 11:34 remove_members -rwxr-xr-x 1 mailman mailman 4256 Sep 7 11:34 rmlist -rwxr-xr-x 1 mailman mailman 3463 Sep 7 11:34 rotatelogs.py -rwxr-xr-x 1 mailman mailman 1346 Sep 7 11:34 show_qfiles -rwxr-xr-x 1 mailman mailman 9664 Sep 7 11:34 sync_members -rwxr-xr-x 1 mailman mailman 11999 Sep 7 11:34 transcheck -rwxr-xr-x 1 mailman mailman 2286 Sep 7 11:34 unshunt -rwxr-xr-x 1 mailman mailman 29648 Sep 7 11:34 update -rwxr-xr-x 1 mailman mailman 963 Sep 7 11:34 version -rwxr-xr-x 1 mailman mailman 8382 Sep 7 11:34 withlist daevid portage-logs # more 3486-mailman-2.1.5-r4.log No updates are necessary. * Running `/usr/local/mailman/bin/check_perms -f` * /usr/local/mailman/cgi-bin/admindb must be set-gid (fixing) /usr/local/mailman/cgi-bin/admin must be set-gid (fixing) /usr/local/mailman/cgi-bin/confirm must be set-gid (fixing) /usr/local/mailman/cgi-bin/create must be set-gid (fixing) /usr/local/mailman/cgi-bin/edithtml must be set-gid (fixing) /usr/local/mailman/cgi-bin/listinfo must be set-gid (fixing) /usr/local/mailman/cgi-bin/options must be set-gid (fixing) /usr/local/mailman/cgi-bin/private must be set-gid (fixing) /usr/local/mailman/cgi-bin/rmlist must be set-gid (fixing) /usr/local/mailman/cgi-bin/roster must be set-gid (fixing) /usr/local/mailman/cgi-bin/subscribe must be set-gid (fixing) /usr/local/mailman/mail/mailman must be set-gid (fixing) Problems found: 12 Re-run as mailman (or root) with -f flag to fix * * Please read /usr/share/doc/mailman-2.1.5-r4/README.gentoo.gz for
Re: [Mailman-Users] patch to add date to each meassge in mail archiveIndex
Andrew, Are you running mailman version 2.1.6? I you like, please send me a copy of your HyperArch.py and I'll take a look at it. I did test this patch out before sending it to the list so I know it works (well, at least for me. -Matt On Mon, 2005-09-12 at 15:14 -0400, Andrew Smith wrote: I was looking for a solution to put the date available in the archives. I have completed the patch as described and get an error when I rebuild my archives - - - File /opt/mailman/Mailman/Archiver/HyperArch.py, line 1005, in write_index_entry datestr = self.get_header(datestr, article) File /opt/mailman/Mailman/Archiver/HyperArch.py, line 1027, in get_header return getattr(article, field) AttributeError: Article instance has no attribute 'datestr' - - - Anyone able to help me with this? --- Andrew Smith Web Developer Tyndale University College Seminary 416-226-6620 (2714) -- [EMAIL PROTECTED] http://www.tyndale.ca http://www.tyndale.ca/it http://www.tyndale.ca/~asmith -- 25 Ballyconnor Court Toronto, Ontario. M2M 4B3 -- Tyndale's Mission is to educate and equip Christians to serve the world with passion for Jesus Christ. --- Mark Sapiro [EMAIL PROTECTED] 9/12/2005 2:06:52 PM Matt Ryanczak wrote: I was asked to make the date for each message in a mailman archive be visible in the index for that month. This required that I modify HyperArch.py and the template file archidxentry.html. I thought others might find this useful so here are the relevant patches for the mailman-2.1.6 source tree. I apologize if this is a duplication of someone else efforts, I searched around and could not find a way to do this in mailman as it was or a patch to do the same. Thanks for developing this patch. It would help for tracking and possible adoption into the base if you would submit it to the Mailman patch tracker at http://sourceforge.net/tracker/?group_id=103atid=300103 You might also add a note to the RFE at http://sourceforge.net/tracker/index.php?func=detailaid=843141group_id=103atid=350103 -- Mark Sapiro [EMAIL PROTECTED] 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://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/asmith%40tyndale.ca 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/ryanczak%40arin.net 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/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mail List Password
At 1:15 PM -0400 2005-09-12, Phil wrote: I have forgotten the password to one of my mail lists. For the life of me I can't seem to find a way to reset the password. Any help? The control panel would be Plesk 7 Go to the Mailman FAQ Wizard at http://www.python.org/cgi-bin/faqw-mm.py and search for plesk. We will try to provide whatever help we can, but because of the way they modify Mailman for integration with Plesk, we will be very limited in what we can do. You could contact the vendor or their support group for assistance. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] patch to add date to each meassge in mail archiveIndex
Mark, Thanks or the information. I'll make sure to go through process of submitting this patch to the community site. -Matt Mark Sapiro wrote: Matt Ryanczak wrote: I was asked to make the date for each message in a mailman archive be visible in the index for that month. This required that I modify HyperArch.py and the template file archidxentry.html. I thought others might find this useful so here are the relevant patches for the mailman-2.1.6 source tree. I apologize if this is a duplication of someone else efforts, I searched around and could not find a way to do this in mailman as it was or a patch to do the same. Thanks for developing this patch. It would help for tracking and possible adoption into the base if you would submit it to the Mailman patch tracker at http://sourceforge.net/tracker/?group_id=103atid=300103 You might also add a note to the RFE at http://sourceforge.net/tracker/index.php?func=detailaid=843141group_id=103atid=350103 -- Mark Sapiro [EMAIL PROTECTED] 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://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] Help with Qmail
I run this script on /var/qmail/aliases #!/bin/sh if [ $# = 1 ]; then i=$1 echo Making links to $i in the current directory... echo |preline /usr/local/mailman/mail/mailman post $i .qmail-$i echo |preline /usr/local/mailman/mail/mailman admin $i .qmail-$i-admin echo |preline /usr/local/mailman/mail/mailman bounces $i .qmail-$i-bounces # The following line is for VERP # echo |preline /usr/local/mailman/mail/mailman bounces $i .qmail-$i-bounces-default echo |preline /usr/local/mailman/mail/mailman confirm $i .qmail-$i-confirm echo |preline /usr/local/mailman/mail/mailman join $i .qmail-$i-join echo |preline /usr/local/mailman/mail/mailman leave $i .qmail-$i-leave echo |preline /usr/local/mailman/mail/mailman owner $i .qmail-$i-owner echo |preline /usr/local/mailman/mail/mailman request $i .qmail-$i-request echo |preline /usr/local/mailman/mail/mailman subscribe $i .qmail-$i-subscribe echo |preline /usr/local/mailman/mail/mailman unsubscribe $i .qmail-$i-unsubscribe fi And now i have the following files on /var/qmail/aliases -rw-r--r--1 root qmail 53 Sep 12 15:59 .qmail-lista3 -rw-r--r--1 root qmail 54 Sep 12 15:59 .qmail-lista3-admin -rw-r--r--1 root qmail 56 Sep 12 15:59 .qmail-lista3-bounces -rw-r--r--1 root qmail 56 Sep 12 15:59 .qmail-lista3-confirm -rw-r--r--1 root qmail 53 Sep 12 15:59 .qmail-lista3-join -rw-r--r--1 root qmail 54 Sep 12 15:59 .qmail-lista3-leave -rw-r--r--1 root qmail 54 Sep 12 15:59 .qmail-lista3-owner -rw-r--r--1 root qmail 56 Sep 12 15:59 .qmail-lista3-request -rw-r--r--1 root qmail 58 Sep 12 15:59 .qmail-lista3-subscribe -rw-r--r--1 root qmail 60 Sep 12 15:59 .qmail-lista3-unsubscribe and i have this in virtualdomains [EMAIL PROTECTED] alias]# more /var/qmail/control/virtualdomains mydomain.bo:mydomain_bo otherdomain.bo:otherdomain_bo but still the problem Hi. This is the qmail-send program at ns.asoban.bo. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: vdeliver: Invalid or unknown virtual user 'lista3' -Mensaje original- De: Mark Sapiro [mailto:[EMAIL PROTECTED] Enviado el: lunes, 12 de septiembre de 2005 15:26 Para: [EMAIL PROTECTED]; mailman-users@python.org Asunto: Re: [Mailman-Users] Help with Qmail Fabricio Vargas wrote: and add the following to /etc/aliasses ## lista3 mailing list lista3: |/usr/local/mailman/mail/mailman post lista3 lista3-admin:|/usr/local/mailman/mail/mailman admin lista3 lista3-bounces: |/usr/local/mailman/mail/mailman bounces lista3 lista3-confirm: |/usr/local/mailman/mail/mailman confirm lista3 lista3-join: |/usr/local/mailman/mail/mailman join lista3 lista3-leave:|/usr/local/mailman/mail/mailman leave lista3 lista3-owner:|/usr/local/mailman/mail/mailman owner lista3 lista3-request: |/usr/local/mailman/mail/mailman request lista3 lista3-subscribe:|/usr/local/mailman/mail/mailman subscribe lista3 lista3-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe lista3 This is not the way aliases work with qmail. See http://www.qmail.org/qmail-manual-html/misc/INSTALL.alias.html -- Mark Sapiro [EMAIL PROTECTED] 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://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
[Mailman-Users] Mailing List Config
This might be a rather simple solution but I can't seem to figure it out. I've set up a Mailman mailing list on my website and I want it to do just a few things: 1. Subscribers send mail to the mailing list address. 2. Everyone in the mailing list gets this message. 3. Any replies made to the messages get sent to everyone as well. Right now it doesn't do this and I can't seem to figure out how to set it up that way. It can be done, right? Thank you. -- Sujay Thomas [EMAIL PROTECTED] www.isujay.com http://www.isujay.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] Mailing List Config
In a flurry of recycled electrons, Sujay Thomas wrote: 1. Subscribers send mail to the mailing list address. 2. Everyone in the mailing list gets this message. 3. Any replies made to the messages get sent to everyone as well. Right now it doesn't do this and I can't seem to figure out how to set it up that way. It can be done, right? If I understand correctly, you want a reply to a list message to go to everyone on the list, not just the originator of the message. If so, set the list as reply to list not reply to poster. OTOH, many people consider that a Bad Thing. Virtually all email programs have a reply-all function, and that should be used if you want to the entire list to see your reply. (flames on this to nla0:) z! -- 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] Help with Qmail
Fabricio Vargas wrote: I run this script on /var/qmail/aliases #!/bin/sh if [ $# = 1 ]; then i=$1 echo Making links to $i in the current directory... echo |preline /usr/local/mailman/mail/mailman post $i .qmail-$i echo |preline /usr/local/mailman/mail/mailman admin $i .qmail-$i-admin echo |preline /usr/local/mailman/mail/mailman bounces $i .qmail-$i-bounces # The following line is for VERP # echo |preline /usr/local/mailman/mail/mailman bounces $i .qmail-$i-bounces-default echo |preline /usr/local/mailman/mail/mailman confirm $i .qmail-$i-confirm echo |preline /usr/local/mailman/mail/mailman join $i .qmail-$i-join echo |preline /usr/local/mailman/mail/mailman leave $i .qmail-$i-leave echo |preline /usr/local/mailman/mail/mailman owner $i .qmail-$i-owner echo |preline /usr/local/mailman/mail/mailman request $i .qmail-$i-request echo |preline /usr/local/mailman/mail/mailman subscribe $i .qmail-$i-subscribe echo |preline /usr/local/mailman/mail/mailman unsubscribe $i .qmail-$i-unsubscribe fi And now i have the following files on /var/qmail/aliases -rw-r--r--1 root qmail 53 Sep 12 15:59 .qmail-lista3 -rw-r--r--1 root qmail 54 Sep 12 15:59 .qmail-lista3-admin -rw-r--r--1 root qmail 56 Sep 12 15:59 .qmail-lista3-bounces -rw-r--r--1 root qmail 56 Sep 12 15:59 .qmail-lista3-confirm -rw-r--r--1 root qmail 53 Sep 12 15:59 .qmail-lista3-join -rw-r--r--1 root qmail 54 Sep 12 15:59 .qmail-lista3-leave -rw-r--r--1 root qmail 54 Sep 12 15:59 .qmail-lista3-owner -rw-r--r--1 root qmail 56 Sep 12 15:59 .qmail-lista3-request -rw-r--r--1 root qmail 58 Sep 12 15:59 .qmail-lista3-subscribe -rw-r--r--1 root qmail 60 Sep 12 15:59 .qmail-lista3-unsubscribe and i have this in virtualdomains [EMAIL PROTECTED] alias]# more /var/qmail/control/virtualdomains mydomain.bo:mydomain_bo otherdomain.bo:otherdomain_bo but still the problem Hi. This is the qmail-send program at ns.asoban.bo. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: vdeliver: Invalid or unknown virtual user 'lista3' Since you've found the above script, you've probably seen the information at http://www.list.org/mailman-install/qmail-issues.html. Beyond this, you are more likely to find help for this issue from qmail folks than from Mailman folks. See for example http://cr.yp.to/lists.html#qmail. -- Mark Sapiro [EMAIL PROTECTED] 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://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] Mailman with MHonArc
On Mon, Sep 12, 2005 at 02:59:08PM -0700, Elvis Fernandes wrote: Does anyone know if this mailman-MhonArc combination will work? There are a couple of ways you can do this: - http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.004.htp - http://www.openinfo.co.uk/mm/index.html I use Richard Barnett / OpenInfo's patches; they are easy to install provided you follow the instructions and work perfectly. George -- [EMAIL PROTECTED] pgp1qdsiPwljc.pgp Description: PGP signature -- 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
[Mailman-Users] subscribe silently fails to moderated list
I have a list where subscription fails if you use the email subscription interface. The list is moderated, but nothing shows up in the logs after the initial inject in the sendmail logs. There is nothing in vette or subscribe, the request just disappears into the ether. -- --Matt -- 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] subscribe silently fails to moderated list
Matt Doughty wrote: I have a list where subscription fails if you use the email subscription interface. The list is moderated, but nothing shows up in the logs after the initial inject in the sendmail logs. There is nothing in vette or subscribe, the request just disappears into the ether. Have you checked the alias for the -subscribe address? What happens if you mail the -join address or send a subscribe command to the -request address. Have you checked the 'error' log? If you do bin/dumpdb lists/listname/pending.pck do you see the pending confirmation? -- Mark Sapiro [EMAIL PROTECTED] 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://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
[Mailman-Users] Mailman + Sendmail
I've had mailman running for years and have only recently started having some delivery problems with it. I originally chalked it up to a particular set of users within the one list that I am on (we host a bunch of lists for others), but, after some investigation, I have been unable to narrow down the source of the problem. Essentially, we have users A, B, C, and D. AB have accounts local to the mailman/mail server and CD have accounts elsewhere. Now, when any user emails to the list, mailman receives the message, then spawns off 4 (right now, I have nodupes deselected for everyone) messages in the sendmail queue. If sendmail had just recently been started (aka: within the past 5 minutes), the message will go through just fine. However, in most cases, the messages (all with the same message ID) hang in the queue forever.. or, at least, until sendmail gets restarted at which time all of the messages get delivered. At this point, one would say It's sendmail, as did I. I dug, and dug, but could not repeat the scenario without mailman in the loop. I could send email to each user directly, I could create an alias called 'test' with each of the users in the alias, and then have any one of them mail to test to have it successfully send that out to everyone. I looked in the logs on mailman, and saw nothing out of the ordinary. I'm pretty much at a loss as to where else to turn. I tried deleting the list and re-adding it, I tried deleting the list and creating one under a different name.. I tried upgrading to Mailman 2.1.6. So far, everything is consistent. I was thinking of trying to set mailman to send only one message per connection or something just to see if the other messages would process and just leave the hanging ones out there (not sure how to set this, though). I searched the archives, too, but didn't have much luck there as I was not sure how to narrow down the search enough (I couldn't come up with good search terms). Any ideas/help/pointers would be much appreciated! Thanks! -Rich -- 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] Mailman + Sendmail
I did some further analysis and discovered that the messages (with the same message ID) were showing up in the ps output as processing from queue. Digging a little further, I tried killing off the sendmail processes that were processing those requests, and I saw the following appear in the mailman log: Sep 12 20:53:28 2005 (24387) Low level smtp error: (4, 'Interrupted system call'), msgid: [EMAIL PROTECTED] So.. that got me thinking that Mailman was somehow not ending the connection properly OR that my sendmail install really didn't like handling multiple messages in one stream (I'm blanking as to why). With all of that in mind, I set : SMTP_MAX_SESSIONS_PER_CONNECTION = 1 MAX_DELIVERY_THREADS = 0 SMTP_MAX_RCPTS = 1 And things started working. Odd.. Now, I know that this is definitely NOT ideal or optimal.. But, what could be going wrong? I tried reducing the SMTP_MAX_SESSIONS_PER_CONNECTION to 0 for my tests, and the problem crept back. I moved that back to 1, then set SMTP_MAX_RCPTS to 0, and the problem crept back. Only the config above seemed to work.. My mind is a jumbled mess thinking about this, but if anyone has any ideas.. I'm all ears. :) -Rich I've had mailman running for years and have only recently started having some delivery problems with it. I originally chalked it up to a particular set of users within the one list that I am on (we host a bunch of lists for others), but, after some investigation, I have been unable to narrow down the source of the problem. Essentially, we have users A, B, C, and D. AB have accounts local to the mailman/mail server and CD have accounts elsewhere. Now, when any user emails to the list, mailman receives the message, then spawns off 4 (right now, I have nodupes deselected for everyone) messages in the sendmail queue. If sendmail had just recently been started (aka: within the past 5 minutes), the message will go through just fine. However, in most cases, the messages (all with the same message ID) hang in the queue forever.. or, at least, until sendmail gets restarted at which time all of the messages get delivered. At this point, one would say It's sendmail, as did I. I dug, and dug, but could not repeat the scenario without mailman in the loop. I could send email to each user directly, I could create an alias called 'test' with each of the users in the alias, and then have any one of them mail to test to have it successfully send that out to everyone. I looked in the logs on mailman, and saw nothing out of the ordinary. I'm pretty much at a loss as to where else to turn. I tried deleting the list and re-adding it, I tried deleting the list and creating one under a different name.. I tried upgrading to Mailman 2.1.6. So far, everything is consistent. I was thinking of trying to set mailman to send only one message per connection or something just to see if the other messages would process and just leave the hanging ones out there (not sure how to set this, though). I searched the archives, too, but didn't have much luck there as I was not sure how to narrow down the search enough (I couldn't come up with good search terms). Any ideas/help/pointers would be much appreciated! Thanks! -Rich -- 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] mailman stopped working after upgrade
Yes, it has the flags, but what is the value of the ${MAILGID}
parameter? The error message you received says it's 'mailman' and
should be 'mail'.
Your original post says:
daevid portage-logs # ll /usr/local/mailman/mail/mailman
-rwxr-sr-x 1 mailman mailman 7768 Sep 7 11:34
/usr/local/mailman/mail/mailman
Thus, the wrapper was recompiled with the upgrade on Sep 7 and that's
when things quit working so this is the likely cause.
# id mail
uid=8(mail) gid=12(mail) groups=12(mail),408(shadow)
# id mailman
uid=280(mailman) gid=280(mailman) groups=280(mailman),16(cron)
# ls -l /usr/local/mailman/mail/mailman
-rwxr-sr-x 1 mailman mailman 7768 Sep 12 15:47
/usr/local/mailman/mail/mailman
I tried to emerge mailman again today just incase that helped. Same results.
daevid portage-logs # ll *mailman*
-rw-r--r-- 1 root root 62662 Sep 7 11:34 3485-mailman-2.1.5-r4.log
-rw-r--r-- 1 root root 1105 Sep 7 11:34 3486-mailman-2.1.5-r4.log
-rw-r--r-- 1 root root 62663 Sep 12 15:47 3528-mailman-2.1.5-r4.log
-rw-r--r-- 1 root root 1105 Sep 12 15:48 3529-mailman-2.1.5-r4.log
From the .log file:
checking for --with-permcheck... yes
checking for --with-username... mailman
checking for user name mailman... okay
checking for --with-groupname... mailman
checking for group name mailman... okay
checking permissions on /usr/local/mailman... okay
checking for mail wrapper group; i.e. --with-mail-gid... mailman
checking for CGI wrapper group; i.e. --with-cgi-gid... apache
I am using Exim as my MTA BTW:
[ebuild R ] mail-mta/exim-4.50-r1 +X -dnsdb -exiscan -exiscan-acl +ipv6
-ldap -lmtp -mailwrapper -mbox +mysql -nis +pam +perl -postgres -sasl +ssl
-syslog +tcpd 1,401 kB
But I don't believe that's changed since:
daevid portage-logs # ll *exim*
-rw-r--r-- 1 root root 23369 Jul 7 00:57 3190-exim-4.50-r1.log
-rw-r--r-- 1 root root 242 Jul 7 00:57 3191-exim-4.50-r1.log
--
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] mailman stopped working after upgrade
Mark said, Yes, it has the flags, but what is the value of the ${MAILGID}
parameter? The error message you received says it's 'mailman' and should be
'mail'.
And looking at the log, he seems to be correct:
Sep 12 12:16:19 [Mailman mail-wrapper] Group mismatch error. Mailman
expected the mail_wrapper script to be executed as group mailman, but_the
system's mail server executed the mail script as_group mail. Try tweaking
the mail server to run the_script as group mailman, or re-run configure,
_providing the command line option `--with-mail-gid=mail'._
But the .ebuild script sets it to gid 280, shouldn't it be 8? why is that?
Is that the problem? How can I fix that. Re-emerging doesn't let me change
those .ebuild values. MD5 errors and such.
APACHEGID=81
MAILGID=280
src_compile() {
econf \
--prefix=${INSTALLDIR} \
--with-mail-gid=${MAILGID} \
--with-cgi-gid=${APACHEGID} \
|| die configure failed
make || die make failed
}
# ll /etc/exim/exim.conf
-rw-r--r-- 1 root root 29452 Apr 29 13:54 /etc/exim/exim.conf
# User and group for Mailman, should match your --with-mail-gid
# switch to Mailman's configure script.
# Value is normally mailman
MM_UID=mailman
MM_GID=mailman
So, these match what the comment says there, and what the .ebuild is doing.
I'm so confused. *sigh*
--
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] mailman stopped working after upgrade
Daevid Vincent wrote:
Mark said, Yes, it has the flags, but what is the value of the ${MAILGID}
parameter? The error message you received says it's 'mailman' and should be
'mail'.
And looking at the log, he seems to be correct:
Sep 12 12:16:19 [Mailman mail-wrapper] Group mismatch error. Mailman
expected the mail_wrapper script to be executed as group mailman, but_the
system's mail server executed the mail script as_group mail. Try tweaking
the mail server to run the_script as group mailman, or re-run configure,
_providing the command line option `--with-mail-gid=mail'._
But the .ebuild script sets it to gid 280, shouldn't it be 8? why is that?
Is that the problem? How can I fix that. Re-emerging doesn't let me change
those .ebuild values. MD5 errors and such.
APACHEGID=81
MAILGID=280
src_compile() {
econf \
--prefix=${INSTALLDIR} \
--with-mail-gid=${MAILGID} \
--with-cgi-gid=${APACHEGID} \
|| die configure failed
make || die make failed
}
# ll /etc/exim/exim.conf
-rw-r--r-- 1 root root 29452 Apr 29 13:54 /etc/exim/exim.conf
# User and group for Mailman, should match your --with-mail-gid
# switch to Mailman's configure script.
# Value is normally mailman
MM_UID=mailman
MM_GID=mailman
So, these match what the comment says there, and what the .ebuild is doing.
I'm so confused. *sigh*
As well you should be at this point. The wrapper is telling you that it
expects to be executed as group 'mailman', and it looks from what
you've presented that it was in fact built that way. It also seems you
can't change it in your update package.
The wrapper also complains that it is not being executed as group
'mailman', but rather as group 'mail'. This is the confusing part
because it seems from the above that you are telling Exim to invoke
the wrapper as group 'mailman' yet the wrapper is telling you it is
being invoked as group 'mail'. I would look carefully at the Exim
configuration to be sure that
MM_UID=mailman
MM_GID=mailman
are in the right place and are not being overridden somewhere else.
--
Mark Sapiro [EMAIL PROTECTED] 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://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] Mailman + Sendmail
Rich West wrote: I did some further analysis and discovered that the messages (with the same message ID) were showing up in the ps output as processing from queue. Digging a little further, I tried killing off the sendmail processes that were processing those requests, and I saw the following appear in the mailman log: Sep 12 20:53:28 2005 (24387) Low level smtp error: (4, 'Interrupted system call'), msgid: [EMAIL PROTECTED] This could be normal if SMTP_MAX_SESSIONS_PER_CONNECTION = 0 since in this case, Mailman (SMTPDirect) will never close the connection from its side. However, the specific error message comes out of the bulkdeliver() method which indicates Mailman is still involved in an SMTP transaction. I.e., it is probably waiting for a response from sendmail. So.. that got me thinking that Mailman was somehow not ending the connection properly OR that my sendmail install really didn't like handling multiple messages in one stream (I'm blanking as to why). Or sendmail wasn't responding to the completion of the DATA command, or ... With all of that in mind, I set : SMTP_MAX_SESSIONS_PER_CONNECTION = 1 MAX_DELIVERY_THREADS = 0 SMTP_MAX_RCPTS = 1 And things started working. Odd.. Not so odd yet, I think. Now, I know that this is definitely NOT ideal or optimal.. But, what could be going wrong? I tried reducing the SMTP_MAX_SESSIONS_PER_CONNECTION to 0 for my tests, and the problem crept back. Now I think it's odd, but what happens in this case right after 'mailmanctl restart'? Does it work for the first few mails and then the problem comes back. If so, it could be that the problem only occurs after a few transactions on an open connection. I moved that back to 1, then set SMTP_MAX_RCPTS to 0, and the problem crept back. Only the config above seemed to work.. Now this I too find puzzling. My mind is a jumbled mess thinking about this, but if anyone has any ideas.. I'm all ears. :) Setting SMTP_MAX_SESSIONS_PER_CONNECTION = 1 is not particularly costly. It just means Mailman closes the SMTP connection after each transaction and reopens it for the next transaction. This is not too costly. Setting MAX_DELIVERY_THREADS which appeared in 2.0 beta 3 appears to be ignored in current versions. There are no references to it outside of Defaults.py Setting SMTP_MAX_RCPTS = 1 may impact performance, but maybe not as much as one would think. This list (mailman-users) uses personalized delivery which amounts to the same thing (at least for regular as opposed to digest deliveries). If you need SMTP_MAX_RCPTS = 1, then you've paid the price and you can VERP all deliveries (for better bounce processing) and personalize your lists for essentially no extra charge. -- Mark Sapiro [EMAIL PROTECTED] 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://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
