Mailman 3 August 2009 - Mailman-Users

رد: Re: Unsubscribe, not disable
by عبدالله حمدي Aug. 30, 2009

Aug. 30, 2009

تم الإرسال من خدمة my Nokia phone ----- الرسالة الأصلية ----- من: Mark Sapiro المرسَل: 2009/08/30 3:27:26 ص إلى: jeffg(a)turners.com; mailman-users(a)python.org الموضوع: Re: [Mailman-Users] Unsubscribe, not disable Mark Sapiro wrote: >Jeff Grossman wrote: >> >>Isn't that what bounce_you_are_disabled_warnings setting does? After this >>many times of sending a you are disabled e-mail, the user is unsubscribed. > > >Exactly! And in case it isn't clear, setting bounce_you_are_disabled_warnings to zero for a list will cause an immediate unsubscribe when the bounce threshold is reached. But, note that there is a bug in Mailman 2.1.11, 2.1.12rc1 and 2.1.12rc2 but not in 2.1.12 and not in 2.1.10 and prior that causes bounce processing to fail when bounce_you_are_disabled_warnings = 0. The attached Bouncer.patch.txt will fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Unsubscribe, not disable
by Thomas Gramstad Aug. 30, 2009

Aug. 30, 2009

How can I make Mailman unsubscribe bouncing addresses instead of disabling them? I'm fine with the default number of days, number of delivery attempts etc., I just want the final action by Mailman to be unsubscribe instead of disable. (This ought to be simple, but I've looked through the Mailman admin web pages several times, and also tried websearches, without being able to find it.) Also, is there a way to unsubscribe all the disabled addresses on a given list with one single command? Thomas Gramstad

3 5

Command line tool to disable delivering for a group of members
by anebi＠iguanait.com Aug. 29, 2009

Aug. 29, 2009

Hi, i have a big part of users that i want to disable delivering for with different reasons. Is there a command line tool that i can use to do this? I need command line tool, because i can automated it, but from screen i need to do checking one by one. Thanks in advanced!

2 2

Re: [Mailman-Users] Very busy list says send_digests failed, Too many links (fwd)
by Mark Sapiro Aug. 28, 2009

Aug. 28, 2009

Ivan Fetch wrote: > > I'm sorry to email you directly, but I believe the below email (sent >twice) is not making it to the mailman-users list. I just checked archives >and don't see the email there either. My re-post from yesterday, seems to >have been accepted by the python.org mail server: > >Aug 27 16:20:23 eros postfix/qmgr[13538]: [ID 197553 mail.info] 169B2C02B: >from=<ifetch(a)du.edu>, size=1764, nrcpt=1 (queue active) >Aug 27 16:20:29 eros postfix/smtp[17110]: [ID 197553 mail.info] 169B2C02B: >to=<mailman-users(a)python.org>, relay=mail.python.org[82.94.164.166]:25, >delay=6.7, delays=0.01/0/5.9/0.73, dsn=2.0.0, status=sent (250 2.0.0 Ok: >queued as A1B94E309) >Aug 27 16:20:29 eros postfix/qmgr[13538]: [ID 197553 mail.info] 169B2C02B: >removed I suspect you are moderated as a recent subscriber and the moderator just hasn't approved the latest posts. This happens. > Have you seen the below - on the mailman-users list, or in a queue >somewhere? No, I haven't seen it, but I can't see the messages waiting moderation. But, see below for my response. >---------- Forwarded message ---------- >Date: Thu, 27 Aug 2009 16:19:58 -0600 (MDT) >From: Ivan Fetch <ifetch(a)du.edu> >To: mailman-users(a)python.org >Subject: Very busy list says send_digests failed, Too many links > >Apologies - this is a re-post, but I didn't see it hit the list in about 19 >hours. > > >Date: Wed, 26 Aug 2009 21:14:00 -0600 (MDT) >From: Ivan Fetch <ifetch(a)du.edu> >To: mailman-users(a)python.org >Subject: Very busy list says send_digests failed, Too many links > >Hello, > > > We had a list get around 30,000 messages today. Eventually, we noticed >emails to this list were really piling up in Mailman's "in" queue, and the >error log showed a lot of: > >Aug 26 13:44:22 2009 (9443) send_digests() failed: [Errno 31] Too many links: >'/mail/mailman/mailman/archives/private/list-name/attachments/20090826/9a8f3979' > > I happened to get around this by setting digestable to know, but would like >to know how I should perhaps clean up after this. Most of the emails to this >list, unfortunately were the result of a run-away program sending emails. Will >the next digest cron job die on this many emails and attachments? Yes, the next cron/senddigests will probably choke too unless you set the list's digest_send_periodic to No. The problem is in the list's lists/LISTNAME/digest.mbox file. Apparently you have a very large number of messages with attachments and with the same Message-ID:. Scrubber is calculating the directory in which to store attachments for this message as /mail/mailman/mailman/archives/private/list-name/attachments/20090826/9a8f3979 (the 9a8f3979 is a hash of the Message-ID:). This directory has so many files in it that the OS will not allow any more to be created - thus, the error 31. You need to either edit the lists/LISTNAME/digest.mbox file and delete all the 'bad' messages, or if you're not concerned about the digest, just remove it. You also should remove the archives/private/list-name/attachments/20090826/9a8f3979 directory. That should be all the cleanup you need to do other that ensuring that the run-away program is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Very busy list says send_digests failed, Too many links
by Ivan Fetch Aug. 28, 2009

Aug. 28, 2009

Hello, We had a list get around 30,000 messages today. Eventually, we noticed emails to this list were really piling up in Mailman's "in" queue, and the error log showed a lot of: Aug 26 13:44:22 2009 (9443) send_digests() failed: [Errno 31] Too many links: '/mail/mailman/mailman/archives/private/list-name/attachments/20090826/9a8f3979' I happened to get around this by setting digestable to know, but would like to know how I should perhaps clean up after this. Most of the emails to this list, unfortunately were the result of a run-away program sending emails. Will the next digest cron job die on this many emails and attachments? Thanks a lot, Ivan.

2 1

Sysadmin/Mailman gig
by Barry Warsaw Aug. 27, 2009

Aug. 27, 2009

A friend of mine forwarded this sysadmin/mailman gig announcement to me. Apparently the Mailman component is fairly high priority. If you're interested, please respond directly to them -- I have no connection to or vested interest in Dreamfish. http://network.dreamfish.com/wiki/Lead_Systems_Administrator_-_Dreamfish_Se… -Barry

1 0

Automatically add virtual-mailman aliases to a Postfix sender access list
by Yeray Gutiérrez Cedrés Aug. 27, 2009

Aug. 27, 2009

I'm new to Mailman and I wonder if there is a proper way to automatically add the addresses created in the virtual-mailman file (when a new list is created) to a list for the check_sender_access postfix restriction. For example, if I create the list "mailmantest", the following is added to the virtual-mailman file: # STANZA START: mailmantest # CREATED: Wed Aug 26 11:32:36 2009 mailmantest(a)domain.tld mailmantest mailmantest-admin(a)domain.tld mailmantest-admin mailmantest-bounces(a)domain.tld mailmantest-bounces mailmantest-confirm(a)domain.tld mailmantest-confirm mailmantest-join(a)domain.tld mailmantest-join mailmantest-leave(a)domain.tld mailmantest-leave mailmantest-owner(a)domain.tld mailmantest-owner mailmantest-request(a)domain.tld mailmantest-request mailmantest-subscribe(a)domain.tld mailmantest-subscribe mailmantest-unsubscribe(a)domain.tld mailmantest-unsubscribe # STANZA END: mailmantest In my Postfix main.cf file I have: smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/lists_relay, reject The /etc/postfix/lists_relay file is like this: mailmantest(a)domain.tld OK mailmantest-admin(a)domain.tld OK mailmantest-bounces(a)domain.tld OK And so on. I'd like those entries in the /etc/postfix/lists_relay file to be created automatically after running "newlist mailmantest". Regards.

2 2

Some questions about mailing list email addresses that messages come from
by anebi＠iguanait.com Aug. 27, 2009

Aug. 27, 2009

Hi, we have installed mailman-2.1.9-4.el5 on Centos 5. What i notice is that when i subscribe or when i receive a message from the mailing list all messages are send from listname-bounce(a)myhostname.tld. Why this happen? Should it send messages using aliases defined in /etc/mailman/aliases? When i unsubscribe from the list, from filed is also listname-bounce@.... What i have done wrong? I have this configuration for this list: moderator = [] description = 'my description' info = 'something here' subject_prefix = '' anonymous_list = 1 first_strip_reply_to = 1 reply_goes_to_list = 0 reply_to_address = '' umbrella_list = 0 umbrella_member_suffix = '-owner' send_reminders = 0 welcome_msg = '' send_welcome_msg = 0 goodbye_msg = '' send_goodbye_msg = 1 admin_immed_notify = 1 admin_notify_mchanges = 0 respond_to_post_requests = 1 emergency = 0 new_member_options = 256 administrivia = 1 max_message_size = 1024 host_name = 'myhostname.domain.tld' include_rfc2369_headers = 0 include_list_post_header = 0 max_days_to_hold = 2 preferred_language = 'en' available_languages = ['en', 'es'] encode_ascii_prefixes = 2 nondigestable = 1 msg_header = '' msg_footer = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s""" scrub_nondigest = False digestable = 0 digest_is_default = 0 mime_is_default_digest = 0 digest_size_threshhold = 0 digest_send_periodic = 1 digest_header = '' digest_footer = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s""" digest_volume_frequency = 1 advertised = 1 subscribe_policy = 1 unsubscribe_policy = 0 ban_list = [] private_roster = 2 obscure_addresses = 1 default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = '' accept_these_nonmembers = [] hold_these_nonmembers = [] reject_these_nonmembers = [] discard_these_nonmembers = [] generic_nonmember_action = 3 forward_auto_discards = 0 nonmember_rejection_notice = '' require_explicit_destination = 1 max_num_recipients = 10 header_filter_rules = [] bounce_processing = 1 bounce_score_threshold = 5.0 bounce_info_stale_after = 7 bounce_you_are_disabled_warnings = 3 bounce_you_are_disabled_warnings_interval = 7 bounce_unrecognized_goes_to_list_owner = 1 bounce_notify_owner_on_disable = 1 bounce_notify_owner_on_removal = 1 archive = 1 archive_private = 0 archive_volume_frequency = 1 nntp_host = '' linked_newsgroup = '' gateway_to_news = 0 gateway_to_mail = 0 news_moderation = 0 news_prefix_subject_too = 1 autorespond_postings = 0 autoresponse_postings_text = '' autorespond_admin = 0 autoresponse_admin_text = '' autorespond_requests = 0 autoresponse_request_text = '' autoresponse_graceperiod = 90 filter_content = 0 pass_mime_types = """multipart/mixed multipart/alternative text/plain""" filter_filename_extensions = """exe bat cmd com pif scr vbs cpl""" pass_filename_extensions = '' collapse_alternatives = True convert_html_to_plaintext = 1 filter_action = 0 topics_enabled = 0 topics_bodylines_limit = 5 topics = []

2 2

mass change the domain name of user email addresses
by Dave Bevis Aug. 27, 2009

Aug. 27, 2009

Is there a script out there or a mailman command that will let me change the domain part of all email addresses to a different domain in all lists? i.e. person1(a)companyA.com changes to person1(a)companyB.com, person2(a)companyA.com changes to person2(a)companyB.com, etc. in all lists and makes the change to all email addresses that have a domain of companyA.com Thanks. Dave Bevis

2 1

MM admin interface wide open
by Ulf Hofemeier Aug. 27, 2009

Aug. 27, 2009

Hi, I'm using MM 2.1.12 and am running into a problem that is rather nasty. In my case the MM admin interface is wide open, which means that I don't need a site admin pwd to access http://mydomain/mailman/admin/mylist. I can click on logout and it will take me to the logout page, but simply removing /logout from the URL will load the admin interface again. Deleting the cookie doesn't help, closing the browser doesn't help. Oh, yeah. The admin interface is accessible via Google as well. *hysteric scream* HELP please! ;-) PS. if you email me, I can provide you with the URL to my MM installation. Thanks. Ulf -- Ulf Hofemeier Programmer / Analyst II Latin American and Iberian Institute ulf(a)ladb.unm.edu

5 8