From danny at puterakembara.org Sat Jan 1 00:35:05 2011 From: danny at puterakembara.org (Danny hendrawan) Date: Sat, 1 Jan 2011 10:35:05 +1100 Subject: [Mailman-Users] Archives heading without domain name In-Reply-To: References: Message-ID: Hi Mark and All, I set my archives list to 'private' mainly to protect email addresses of members being disclosed on the heading. I've set my heading to replace '@' with 'at' but still this can be easilly taken by anyone. i.e. 'john at domain.com' How to set the headings as per your Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ ? i.e. only shows member's name with domain name Happy New New Year. Regards, Danny From mark at msapiro.net Sat Jan 1 02:20:50 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 31 Dec 2010 17:20:50 -0800 Subject: [Mailman-Users] Archives heading without domain name In-Reply-To: References: Message-ID: <8c1a6ed5-206b-4f6d-b66a-c3103117b7bd@email.android.com> "Danny hendrawan" wrote: >How to set the headings as per your Searchable Archives: >http://www.mail-archive.com/mailman-users%40python.org/ ? i.e. only >shows >member's name with domain name Use mail-archive.com as your list's archiver. -- Mark Sapiro - mark at msapiro.net Sent from my Android phone with K-9 Mail. Please excuse my brevity. From umarzuki at gmail.com Sun Jan 2 15:09:01 2011 From: umarzuki at gmail.com (Umarzuki Mochlis) Date: Sun, 2 Jan 2011 22:09:01 +0800 Subject: [Mailman-Users] User unknown in virtual mailbox table In-Reply-To: References: Message-ID: i set in mm_cfg.py like below POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail-server.mydomain.my'] from socket import * try: fqdn = getfqdn() except: fqdn = 'mm_cfg_has_unknown_host_domains' DEFAULT_URL_HOST = "mail-server.mydomain.my" DEFAULT_EMAIL_HOST = "mail-server.mydomain.my" VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST, ) MTA = 'Postfix' and ran # /usr/lib/mailman/bin/withlist -l -a -r fix_url # /usr/lib/mailman/bin/genaliases with the same result as before postconf -n output: alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases, hash:/etc/mailman/aliases allow_min_user = no biff = no bounce_queue_lifetime = 1d broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 delay_warning_time = 0h disable_vrfy_command = yes enable_original_recipient = no home_mailbox = Maildir/ html_directory = no inet_interfaces = all inet_protocols = ipv4 local_recipient_maps = mail_name = iRedMail mail_owner = postfix mail_version = 0.6.1 mailbox_command = /usr/libexec/dovecot/deliver mailbox_size_limit = 15728640 mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man maximal_backoff_time = 4000s maximal_queue_lifetime = 1d minimal_backoff_time = 300s mydestination = $myhostname, localhost, localhost.localdomain, localhost.$myhostname mydomain = mydomain.my myhostname = mail-server.mydomain.my mynetworks = 127.0.0.0/8 mynetworks_style = subnet myorigin = mail-server.mydomain.my newaliases_path = /usr/bin/newaliases.postfix proxy_read_maps = $canonical_maps $lmtp_generic_maps $local_recipient_maps $mydestination $mynetworks $recipient_bcc_maps $recipient_canonical_maps $relay_domains $relay_recipient_maps $relocated_maps $sender_bcc_maps $sender_canonical_maps $smtp_generic_maps $smtpd_sender_login_maps $transport_maps $virtual_alias_domains $virtual_alias_maps $virtual_mailbox_domains $virtual_mailbox_maps queue_directory = /var/spool/postfix queue_run_delay = 300s readme_directory = /usr/share/doc/postfix-2.5.9/README_FILES recipient_bcc_maps = proxy:ldap:/etc/postfix/ ldap_recipient_bcc_maps_domain.cf, proxy:ldap:/etc/postfix/ ldap_recipient_bcc_maps_user.cf recipient_delimiter = + relay_domains = $mydestination, proxy:ldap:/etc/postfix/ ldap_relay_domains.cf relay_recipient_maps = proxy:mysql:/etc/postfix/ mysql_virtual_mailbox_maps.cf sample_directory = /usr/share/doc/postfix-2.5.9/samples sender_bcc_maps = proxy:ldap:/etc/postfix/ldap_sender_bcc_maps_domain.cf, proxy:ldap:/etc/postfix/ldap_sender_bcc_maps_user.cf sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_data_restrictions = reject_unauth_pipelining smtpd_enforce_tls = no smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks,permit_sasl_authenticated, check_helo_access pcre:/etc/postfix/helo_access.pcre smtpd_recipient_restrictions = reject_unknown_recipient_domain, reject_non_fqdn_recipient, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:7777, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_policy_service inet:127.0.0.1:10031 smtpd_reject_unlisted_recipient = no smtpd_reject_unlisted_sender = yes smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = no smtpd_sasl_local_domain = smtpd_sasl_path = dovecot-auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_login_maps = proxy:ldap:/etc/postfix/ldap_sender_login_maps.cf smtpd_sender_restrictions = permit_mynetworks, reject_sender_login_mismatch, permit_sasl_authenticated smtpd_tls_cert_file = /etc/pki/tls/certs/iRedMail_CA.pem smtpd_tls_key_file = /etc/pki/tls/private/iRedMail.key smtpd_tls_loglevel = 0 smtpd_tls_security_level = may tls_random_source = dev:/dev/urandom transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf, proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf unknown_local_recipient_reject_code = 550 virtual_alias_maps = proxy:ldap:/etc/postfix/ldap_virtual_alias_maps.cf, proxy:ldap:/etc/postfix/ldap_virtual_group_maps.cf, proxy:ldap:/etc/postfix/ ldap_sender_login_maps.cf, proxy:ldap:/etc/postfix/ldap_catch_all_maps.cf virtual_gid_maps = static:502 virtual_mailbox_base = /var/vmail virtual_mailbox_domains = proxy:ldap:/etc/postfix/ ldap_virtual_mailbox_domains.cf virtual_mailbox_maps = proxy:ldap:/etc/postfix/ldap_virtual_mailbox_maps.cf virtual_minimum_uid = 502 virtual_transport = dovecot virtual_uid_maps = static:502 after i read http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps i changed & added a few options in mm_cfg.py POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mydomain.my'] POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport' in /etc/mailman # ls -l /etc/mailman/ total 140 -rw-r----- 1 root mailman 41 Dec 8 18:25 adm.pw -rw-rw---- 1 mailman mailman 33942 Jan 3 04:37 aliases -rw-rw---- 1 mailman mailman 77824 Jan 3 04:37 aliases.db -rw-r----- 1 root mailman 41 Dec 8 18:26 creator.pw lrwxrwxrwx 1 root mailman 34 Dec 8 18:12 mm_cfg.py -> /usr/lib/mailman/Mailman/mm_cfg.py -rw-r--r-- 1 root mailman 14114 Jan 23 2008 sitelist.cfg -rw-rw---- 1 mailman mailman 0 Jan 3 04:37 transport-mailman -rw-rw---- 1 mailman mailman 12288 Jan 3 04:37 transport-mailman.db -rw-rw---- 1 root mailman 0 Jan 3 04:37 virtual-mailman -rw-r----- 1 root mailman 12288 Jan 3 04:32 virtual-mailman.db -rwxr-x--- 1 root mailman 141 Jan 3 04:26 virtual_to_transport in /etc/mailman/virtual_to_transport #!/bin/sh sed -r -e 's/(^[^#][^ ]+[ ]+).+$/\1local/' $1 \ > /etc/mailman/transport-mailman /usr/sbin/postmap /etc/mailman/transport-mailman # postconf transport_maps transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf, proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf, hash:/etc/mailman/transport-mailman did i missed anything? -- Regards, Umarzuki Mochlis http://debmal.my From umarzuki at gmail.com Sun Jan 2 17:50:55 2011 From: umarzuki at gmail.com (Umarzuki Mochlis) Date: Mon, 3 Jan 2011 00:50:55 +0800 Subject: [Mailman-Users] User unknown in virtual mailbox table In-Reply-To: References:

Message-ID: after a check on /usr/lib/mailman/Mailman/Defaults.py VAR_PREFIX = '/var/lib/mailman' DATA_DIR = os.path.join(VAR_PREFIX, 'data') so the /path/to/data must be /var/lib/mailman/data which led me to 1. change main.cf ----------- alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf, proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf, hash:/var/lib//mailman/data/transport-mailman 2. move virtual_to_transport to /var/lib/mailman/data 3. virtual_to_transport #!/bin/sh sed -r -e 's/(^[^#][^ ]+[ ]+).+$/\1local/' $1 \ > /var/lib/mailman/data/transport-mailman /usr/sbin/postmap /var/lib/mailman/data/transport-mailman 4. ran # postalias /var/lib/mailman/data/aliases # postalias /etc/postfix/aliases # service postfix reload # /usr/lib/mailman/bin/genaliases but virtual-mailman and transport-mailman does not appear in data folder # ls -l /var/lib/mailman/data/ total 20 -rw-r--r-- 1 mailman mailman 1503 Dec 17 11:28 aliases -rw-r--r-- 1 mailman mailman 12288 Jan 3 08:40 aliases.db lrwxrwxrwx 1 root mailman 25 Dec 8 18:12 sitelist.cfg -> /etc/mailman/sitelist.cfg -rwxr-x--- 1 mailman mailman 159 Jan 3 08:26 virtual_to_transport any hints or advises? Regards, Umarzuki Mochlis http://debmal.my From carnold at electrichendrix.com Sun Jan 2 20:48:16 2011 From: carnold at electrichendrix.com (Chris Arnold) Date: Sun, 2 Jan 2011 14:48:16 -0500 Subject: [Mailman-Users] List on a different domain name? Message-ID: <1EE92C4C-33B9-41DC-BD1B-BA51270ACC98@electrichendrix.com> Just upgraded to 2.1.14 on sles 10 sp3 with oes2. We use to have a domain that mailman was used on, this domain has since expired. We have a couple of other domains that I would like to use mailman on. Maybe I don't fully understand mailman but is there a way to use mailman on other domains? Internal users can still access the expired domain and access mailman but external users can not access mailman from valid domains (did that make sense?). Sent from my iPhone From mark at msapiro.net Sun Jan 2 21:30:26 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 2 Jan 2011 12:30:26 -0800 Subject: [Mailman-Users] User unknown in virtual mailbox table In-Reply-To: Message-ID: Umarzuki Mochlis wrote: >i set in mm_cfg.py like below > >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail-server.mydomain.my'] > >from socket import * >try: > fqdn = getfqdn() >except: > fqdn = 'mm_cfg_has_unknown_host_domains' > >DEFAULT_URL_HOST = "mail-server.mydomain.my" >DEFAULT_EMAIL_HOST = "mail-server.mydomain.my" >VIRTUAL_HOSTS.clear() >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST, ) >MTA = 'Postfix' > >and ran > ># /usr/lib/mailman/bin/withlist -l -a -r fix_url ># /usr/lib/mailman/bin/genaliases > >with the same result as before This should have ensured that all lists had host_name "mail-server.mydomain.my" and since this name is in POSTFIX_STYLE_VIRTUAL_DOMAINS, genaliases should have created aliases and virtual-mailman for all lists. >postconf -n output: > >alias_database = hash:/etc/postfix/aliases >alias_maps = hash:/etc/postfix/aliases, hash:/etc/mailman/aliases Good. [...] You probably should have recipient_delimiter = + for Mailman's VERP like senders. [...] >virtual_alias_maps = proxy:ldap:/etc/postfix/ldap_virtual_alias_maps.cf, >proxy:ldap:/etc/postfix/ldap_virtual_group_maps.cf, proxy:ldap:/etc/postfix/ >ldap_sender_login_maps.cf, proxy:ldap:/etc/postfix/ldap_catch_all_maps.cf If you are using virtual-mailman, you want to add "hash:/etc/mailman/virtual-mailman" to virtual_alias_maps. However, because of your dovecot LDA, you may need to do the transport_maps thing instead. See below. [...] >after i read >http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps > >i >changed & added a few options in mm_cfg.py > >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mydomain.my'] Why did you change this? You must have your list's email domain in POSTFIX_STYLE_VIRTUAL_DOMAINS. According to what you did above, your list's email domain is 'mail-server.mydomain.my', not 'mydomain.my'. >POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport' > >in /etc/mailman > ># ls -l /etc/mailman/ >total 140 >-rw-r----- 1 root mailman 41 Dec 8 18:25 adm.pw >-rw-rw---- 1 mailman mailman 33942 Jan 3 04:37 aliases >-rw-rw---- 1 mailman mailman 77824 Jan 3 04:37 aliases.db >-rw-r----- 1 root mailman 41 Dec 8 18:26 creator.pw >lrwxrwxrwx 1 root mailman 34 Dec 8 18:12 mm_cfg.py -> >/usr/lib/mailman/Mailman/mm_cfg.py >-rw-r--r-- 1 root mailman 14114 Jan 23 2008 sitelist.cfg >-rw-rw---- 1 mailman mailman 0 Jan 3 04:37 transport-mailman >-rw-rw---- 1 mailman mailman 12288 Jan 3 04:37 transport-mailman.db >-rw-rw---- 1 root mailman 0 Jan 3 04:37 virtual-mailman >-rw-r----- 1 root mailman 12288 Jan 3 04:32 virtual-mailman.db >-rwxr-x--- 1 root mailman 141 Jan 3 04:26 virtual_to_transport This all looks correct. >in /etc/mailman/virtual_to_transport >#!/bin/sh >sed -r -e 's/(^[^#][^ ]+[ ]+).+$/\1local/' $1 \ > > /etc/mailman/transport-mailman >/usr/sbin/postmap /etc/mailman/transport-mailman > ># postconf transport_maps >transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf, >proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf, >hash:/etc/mailman/transport-mailman > >did i missed anything? The above seems correct for the transport_maps method, but you shouldn't have changed POSTFIX_STYLE_VIRTUAL_DOMAINS. And Umarzuki Mochlis added in a follow-up: >after a check on /usr/lib/mailman/Mailman/Defaults.py > >VAR_PREFIX = '/var/lib/mailman' >DATA_DIR = os.path.join(VAR_PREFIX, 'data') > >so the /path/to/data must be /var/lib/mailman/data which led me to Except it clearly isn't because your "ls -l /etc/mailman/" above clearly shows all the files in that directory. Perhaps there is something in mm_cfg.py that overrides VAR_PREFIX and DATA_DIR. You might find the FAQ at of interest. >1. change main.cf >----------- >alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases >transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf, >proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf, >hash:/var/lib//mailman/data/transport-mailman > >2. move virtual_to_transport to /var/lib/mailman/data > >3. virtual_to_transport >#!/bin/sh >sed -r -e 's/(^[^#][^ ]+[ ]+).+$/\1local/' $1 \ > > /var/lib/mailman/data/transport-mailman >/usr/sbin/postmap /var/lib/mailman/data/transport-mailman > >4. ran ># postalias /var/lib/mailman/data/aliases ># postalias /etc/postfix/aliases ># service postfix reload ># /usr/lib/mailman/bin/genaliases > >but virtual-mailman and transport-mailman does not appear in data folder > ># ls -l /var/lib/mailman/data/ >total 20 >-rw-r--r-- 1 mailman mailman 1503 Dec 17 11:28 aliases >-rw-r--r-- 1 mailman mailman 12288 Jan 3 08:40 aliases.db >lrwxrwxrwx 1 root mailman 25 Dec 8 18:12 sitelist.cfg -> >/etc/mailman/sitelist.cfg >-rwxr-x--- 1 mailman mailman 159 Jan 3 08:26 virtual_to_transport > > >any hints or advises? Yes. Undo the 4 steps above. Fix POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py and run /usr/lib/mailman/bin/genaliases again. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 2 21:44:07 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 2 Jan 2011 12:44:07 -0800 Subject: [Mailman-Users] List on a different domain name? In-Reply-To: <1EE92C4C-33B9-41DC-BD1B-BA51270ACC98@electrichendrix.com> Message-ID: Chris Arnold wrote: >Just upgraded to 2.1.14 on sles 10 sp3 with oes2. We use to have a domain that mailman was used on, this domain has since expired. We have a couple of other domains that I would like to use mailman on. Maybe I don't fully understand mailman but is there a way to use mailman on other domains? You can use Mailman on any number of domains. The only restriction with standard GNU Mailman 2.1.x is tha list names must be globally unique in the installation. There are 3 components to this. 1) The web server must recognize the appropriate Mailman ScriptAlias, Alias, etc. directives in all the domains. 2) The MTA must know how to deliver the mail to Mailman for all the list addresses. 3) There should be appropriate add_virtualhost() directives and for Postfix integration with Postfix virtual domains, appropriate POSTFIX_STYLE_VIRTUAL_DOMAINS entries in mm_cfg.py. See the FAQ at http://wiki.list.org/x/gIA9 for more, particularly the part about fix_url. >Internal users can still access the expired domain and access mailman but external users can not access mailman from valid domains (did that make sense?). Maybe. You need to make sure the web server will apply the Mailman related configuration directives to the host(s) yoiu want to use. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From yahoo at 8es.com Mon Jan 3 05:02:57 2011 From: yahoo at 8es.com (yahoo) Date: Sun, 02 Jan 2011 23:02:57 -0500 Subject: [Mailman-Users] A basic filtering MIME question Message-ID: <4D214A71.5030901@8es.com> I've been reading the FAQ's etc and asking local advice; but I must be doing something stoopid. MM2.1.3 under Linux, 2.6.18-164.el5 My goal is: a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers & archives. b) /dev/null the attachments, both in delivery and archives. FAQ 1.8 says: > In Mailman 2.1, on the admin page, go to the Content Filtering section. > Change "Should Mailman filter ..." to Yes. If you leave the rest at > default values, including Yes for "Should Mailman convert text/html > parts to plain text?", your list will only distribute plain text > messages with no attachments. And I did so, but I suspect that filter_mime_types &/or pass mime type originally had values that before/in my muddling, have been lost; both are empty now. Suggestions? From jim at wrightthisway.com Mon Jan 3 07:15:54 2011 From: jim at wrightthisway.com (Jim Wright) Date: Mon, 3 Jan 2011 00:15:54 -0600 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user Message-ID: Hi, all. I'm a new user, but I've searched the archives and so far haven't been able to find a fix for my issue. I've set up mailman with postfix and I'm using virtual domains. I've created a test mailing list, and Mailman has successfully emailed me that the list was created. However, I cannot send email to this list without the mail being rejected back as being to an unknown user. Based on all of my reading, I think I've done everything correctly. From my Postfix log, it doesn't appear that the aliases file is being consulted at all, but I am seeing a line indicating that the virtual-mailman file was referenced. Here are the relevant Mailman files: From mm_cfg.py: # Put YOUR site-specific settings below this line. MTA = "Postfix" POSTFIX_STYLE_VIRTUAL_DOMAINS = ['wrightthisway.com', 'themailshack.com'] add_virtualhost('wrightthisway.com', 'wrightthisway.com') add_virtualhost('themailshack.com', 'themailshack.com') sh-3.2# cat aliases # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE # unless you know what you're doing, and can keep the two files properly # in sync. If you screw it up, you're on your own. # The ultimate loop stopper address mailman-loop: /usr/local/mailman/data/owner-bounces.mbox # STANZA START: test # CREATED: Sat Dec 25 18:26:51 2010 test: "|/usr/local/mailman/mail/mailman post test" test-admin: "|/usr/local/mailman/mail/mailman admin test" test-bounces: "|/usr/local/mailman/mail/mailman bounces test" test-confirm: "|/usr/local/mailman/mail/mailman confirm test" test-join: "|/usr/local/mailman/mail/mailman join test" test-leave: "|/usr/local/mailman/mail/mailman leave test" test-owner: "|/usr/local/mailman/mail/mailman owner test" test-request: "|/usr/local/mailman/mail/mailman request test" test-subscribe: "|/usr/local/mailman/mail/mailman subscribe test" test-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe test" # STANZA END: test # STANZA START: mailman # CREATED: Sun Jan 2 22:08:00 2011 mailman: "|/usr/local/mailman/mail/mailman post mailman" mailman-admin: "|/usr/local/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/local/mailman/mail/mailman join mailman" mailman-leave: "|/usr/local/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/local/mailman/mail/mailman owner mailman" mailman-request: "|/usr/local/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/local/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman sh-3.2# cat virtual-mailman # This file is generated by Mailman, and is kept in sync with the binary hash # file virtual-mailman.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you # know what you're doing, and can keep the two files properly in sync. If you # screw it up, you're on your own. # # Note that you should already have this virtual domain set up properly in # your Postfix installation. See README.POSTFIX for details. # LOOP ADDRESSES START mailman-loop at wrightthisway.com mailman-loop # LOOP ADDRESSES END # STANZA START: test # CREATED: Sat Dec 25 18:26:51 2010 test at wrightthisway.com test test-admin at wrightthisway.com test-admin test-bounces at wrightthisway.com test-bounces test-confirm at wrightthisway.com test-confirm test-join at wrightthisway.com test-join test-leave at wrightthisway.com test-leave test-owner at wrightthisway.com test-owner test-request at wrightthisway.com test-request test-subscribe at wrightthisway.com test-subscribe test-unsubscribe at wrightthisway.com test-unsubscribe # STANZA END: test Below is my Postfix config, and a sample of the log when a message is sent to the list. sh-3.2# postconf -n address_verify_sender = <> alias_database = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases alias_maps = hash:/etc/postfix/aliases body_checks = regexp:/etc/postfix/maps/body_checks command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debug_peer_list = 70.116.91.238 default_process_limit = 20 default_rbl_reply = $rbl_code Service unavailable; $rbl_class [$rbl_what] blocked using $rbl_domain${rbl_reason?; $rbl_reason} - see http://$rbl_domain for additional info. If this was actually a legitimate email to a real user, please forward this message to postmaster at wrightthisway.com for assistance. disable_vrfy_command = yes header_checks = regexp:/etc/postfix/maps/header_checks html_directory = no inet_interfaces = all mail_owner = _postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man max_use = 18 message_size_limit = 30000000 mime_header_checks = regexp:/etc/postfix/maps/mime_header_checks mydestination = mydomain = wrightthisway.com myhostname = wrightthisway.com mynetworks_style = subnet newaliases_path = /usr/bin/newaliases queue_directory = /private/var/spool/postfix readme_directory = /usr/share/doc/postfix recipient_delimiter = + relayhost = smtp-server.austin.rr.com sample_directory = /usr/share/doc/postfix/examples sendmail_path = /usr/sbin/sendmail setgid_group = _postdrop show_user_unknown_table_name = no smtpd_data_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_pipelining, permit smtpd_error_sleep_time = 90 smtpd_hard_error_limit = 10 smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, check_recipient_maps smtpd_junk_command_limit = 1 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_recipient_access hash:/etc/postfix/restricted_users, normal_restriction, check_helo_access hash:/etc/postfix/helo_access, check_client_access hash:/etc/postfix/access, check_recipient_access hash:/etc/postfix/access, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, reject_rbl_client fresh15.spameatingmonkey.net, reject_rbl_client dnsbl.njabl.org, reject_rbl_client cbl.abuseat.org smtpd_restriction_classes = normal_restriction, postmaster_policyd_restriction smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_soft_error_limit = 1 strict_rfc821_envelopes = yes tls_random_source = dev:/dev/urandom unknown_address_reject_code = 550 unknown_client_reject_code = 550 unknown_hostname_reject_code = 450 unknown_local_recipient_reject_code = 550 virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf, hash:/usr/local/mailman/data/virtual-mailman virtual_gid_maps = static:27 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 30000000 virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 27 virtual_transport = virtual virtual_uid_maps = static:27 sh-3.2# Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: warning: 70.116.91.238: hostname cpe-70-116-91-238.austin.res.rr.com verification failed: nodename nor servname provided, or not known Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: connect from unknown[70.116.91.238] Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: unknown: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: 70.116.91.238: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: auto_clnt_open: connected to private/anvil Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = connect Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr ident = smtp:70.116.91.238 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/anvil: wanted attribute: status Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: status Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/anvil: wanted attribute: count Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: count Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/anvil: wanted attribute: rate Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: rate Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/anvil: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 220 wrightthisway.com ESMTP Postfix Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_create: SASL service=smtp, realm=(null) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: name_mask: noanonymous Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: Connecting Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: VERSION?1?1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: MECH?PLAIN?plaintext Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: name_mask: plaintext Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: MECH?LOGIN?plaintext Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: name_mask: plaintext Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: MECH?CRAM-MD5?dictionary?active Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: name_mask: dictionary Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: name_mask: active Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: SPID?81760 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: CUID?3 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: COOKIE?e6de66242204d49b2eb1951a09a68c11 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_connect: auth reply: DONE Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_mech_filter: keep mechanism: PLAIN Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_mech_filter: keep mechanism: LOGIN Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_mech_filter: keep mechanism: CRAM-MD5 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: watchdog_pat: 0x1004120a0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: < unknown[70.116.91.238]: EHLO [192.168.1.10] Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-PIPELINING Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-SIZE 30000000 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-ETRN Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: unknown: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: 70.116.91.238: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-AUTH PLAIN LOGIN CRAM-MD5 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-ENHANCEDSTATUSCODES Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250-8BITMIME Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250 DSN Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: watchdog_pat: 0x1004120a0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: < unknown[70.116.91.238]: AUTH PLAIN AGppbUB3cmlnaHR0aGlzd2F5LmNvbQBuYW5hMTk5MA== Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_server_first: sasl_method PLAIN, init_response AGppbUB3cmlnaHR0aGlzd2F5LmNvbQBuYW5hMTk5MA== Jan 2 23:46:45 wrights-Mac-mini dovecot[48385]: auth: mysql: Connected to localhost (postfix) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: xsasl_dovecot_handle_reply: auth reply: OK?1?user=jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 235 2.7.0 Authentication successful Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: watchdog_pat: 0x1004120a0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: < unknown[70.116.91.238]: MAIL FROM: Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: extract_addr: input: Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: smtpd_check_addr: addr=jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: connect to subsystem private/rewrite Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = rewrite Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr rule = local Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr address = jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: address Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: address Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: rewrite_clnt: local: jim at wrightthisway.com -> jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = resolve Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr sender = Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr address = jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: transport Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: transport Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: virtual Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: nexthop Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: nexthop Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: recipient Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: recipient Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 1024 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: resolve_clnt: `' -> `jim at wrightthisway.com' -> transp=`virtual' host=`wrightthisway.com' rcpt=`jim at wrightthisway.com' flags= class=virtual Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: ctable_locate: install entry key jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: extract_addr: in: , result: jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: fsspace: .: block size 4096, blocks free 71821920 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: smtpd_check_queue: blocks 4096 avail 71821920 min_free 0 msg_size_limit 30000000 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250 2.1.0 Ok Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: watchdog_pat: 0x1004120a0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: < unknown[70.116.91.238]: RCPT TO: Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: extract_addr: input: Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: smtpd_check_addr: addr=test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = rewrite Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr rule = local Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr address = test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: address Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: address Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: rewrite_clnt: local: test at wrightthisway.com -> test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = resolve Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr sender = Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr address = test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: transport Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: transport Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: virtual Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: nexthop Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: nexthop Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: recipient Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: recipient Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 1024 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: resolve_clnt: `' -> `test at wrightthisway.com' -> transp=`virtual' host=`wrightthisway.com' rcpt=`test at wrightthisway.com' flags= class=virtual Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: ctable_locate: install entry key test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: extract_addr: in: , result: test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = rewrite Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr rule = local Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr address = "<>" Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: flags Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: address Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: address Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: "<>"@wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/rewrite socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: rewrite_clnt: local: "<>" -> "<>"@wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: >>> START Helo command RESTRICTIONS <<< Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_mynetworks Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: permit_mynetworks: unknown 70.116.91.238 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: unknown: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: 70.116.91.238: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_mynetworks status=0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_sasl_authenticated Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_sasl_authenticated status=1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: >>> START Sender address RESTRICTIONS <<< Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=hash:/etc/postfix/access Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: check_mail_access: jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: ctable_locate: move existing entry key jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: check_access: jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: check_domain_access: wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: check_access: jim@ Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=check_sender_access status=0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: >>> END Sender address RESTRICTIONS <<< Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: >>> START Recipient address RESTRICTIONS <<< Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_mynetworks Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: permit_mynetworks: unknown 70.116.91.238 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: unknown: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: 70.116.91.238: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_mynetworks status=0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_sasl_authenticated Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_sasl_authenticated status=1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: >>> CHECKING RECIPIENT MAPS <<< Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: ctable_locate: move existing entry key test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: recipient_canonical_maps: test at wrightthisway.com: not found Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: recipient_canonical_maps: test: not found Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: recipient_canonical_maps: @wrightthisway.com: not found Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: mail_addr_find: test at wrightthisway.com -> (not found) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: canonical_maps: test at wrightthisway.com: not found Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: canonical_maps: test: not found Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: canonical_maps: @wrightthisway.com: not found Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: mail_addr_find: test at wrightthisway.com -> (not found) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr request = lookup Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr table = mysql:/etc/postfix/mysql_virtual_alias_maps.cf Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr flags = 16448 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr key = test at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/proxymap socket: wanted attribute: status Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: status Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/proxymap socket: wanted attribute: value Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: value Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: private/proxymap socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: dict_proxy_lookup: table=mysql:/etc/postfix/mysql_virtual_alias_maps.cf flags=lock|fold_fix key=test at wrightthisway.com -> status=1 result= Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: maps_find: virtual_alias_maps: hash:/usr/local/mailman/data/virtual-mailman(0,lock|fold_fix): test at wrightthisway.com = test Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: mail_addr_find: test at wrightthisway.com -> test Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: smtpd_check_rewrite: trying: permit_inet_interfaces Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: permit_inet_interfaces: unknown 70.116.91.238 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: before input_transp_cleanup: cleanup flags = enable_header_body_filter enable_automatic_bcc enable_address_mapping enable_milters Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: after input_transp_cleanup: cleanup flags = enable_header_body_filter enable_automatic_bcc enable_address_mapping Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: connect to subsystem public/cleanup Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: public/cleanup socket: wanted attribute: queue_id Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: queue_id Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: BBA681B43CF Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: public/cleanup socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: send attr flags = 178 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: BBA681B43CF: client=unknown[70.116.91.238], sasl_method=PLAIN, sasl_username=jim at wrightthisway.com Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250 2.1.5 Ok Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: watchdog_pat: 0x1004120a0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: < unknown[70.116.91.238]: DATA Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: >>> START Data command RESTRICTIONS <<< Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_mynetworks Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: permit_mynetworks: unknown 70.116.91.238 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 127.0.0.0/8 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostname: unknown ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_hostaddr: 70.116.91.238 ~? 192.168.0.0/22 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: unknown: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: match_list_match: 70.116.91.238: no match Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_mynetworks status=0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_sasl_authenticated Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: generic_checks: name=permit_sasl_authenticated status=1 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 354 End data with . Jan 2 23:46:45 wrights-Mac-mini postfix/cleanup[81788]: BBA681B43CF: message-id= Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: public/cleanup socket: wanted attribute: status Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: status Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: 0 Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: public/cleanup socket: wanted attribute: reason Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: reason Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute value: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: public/cleanup socket: wanted attribute: (list terminator) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: input attribute name: (end) Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: > unknown[70.116.91.238]: 250 2.0.0 Ok: queued as BBA681B43CF Jan 2 23:46:45 wrights-Mac-mini postfix/smtpd[81782]: watchdog_pat: 0x1004120a0 Jan 2 23:46:45 wrights-Mac-mini postfix/qmgr[81789]: BBA681B43CF: from=, size=524, nrcpt=1 (queue active) Jan 2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: to=, relay=virtual, delay=0.1, delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: "test at wrightthisway.com") Jan 2 23:46:45 wrights-Mac-mini postfix/cleanup[81788]: CCF831B43D9: message-id=<20110103054645.CCF831B43D9 at wrightthisway.com> Jan 2 23:46:45 wrights-Mac-mini postfix/qmgr[81789]: CCF831B43D9: from=<>, size=2361, nrcpt=1 (queue active) Jan 2 23:46:45 wrights-Mac-mini postfix/bounce[81791]: BBA681B43CF: sender non-delivery notification: CCF831B43D9 Jan 2 23:46:45 wrights-Mac-mini postfix/qmgr[81789]: BBA681B43CF: removed Jan 2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: CCF831B43D9: to=, relay=virtual, delay=0, delays=0/0/0/0, dsn=2.0.0, status=sent (delivered to maildir) Jan 2 23:46:45 wrights-Mac-mini postfix/qmgr[81789]: CCF831B43D9: removed From jim at wrightthisway.com Mon Jan 3 18:18:02 2011 From: jim at wrightthisway.com (Jim Wright) Date: Mon, 3 Jan 2011 11:18:02 -0600 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user In-Reply-To: References: Message-ID: On Jan 3, 2011, at 12:15 AM, Jim Wright wrote: > Jan 2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: to=, relay=virtual, delay=0.1, delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: "test at wrightthisway.com") Hi, just a followup to my previous message, I have confirmed that the 'test' mailing list I created seems to be listed correctly in the virtual-mailman db, using the following command: sh-3.2# postmap -q test at wrightthisway.com hash:/usr/local/mailman/data/virtual-mailman test sh-3.2# postmap -s hash:/usr/local/mailman/data/virtual-mailman test-confirm at wrightthisway.com test-confirm test-join at wrightthisway.com test-join test-subscribe at wrightthisway.com test-subscribe mailman-loop at wrightthisway.com mailman-loop test at wrightthisway.com test test-admin at wrightthisway.com test-admin test-bounces at wrightthisway.com test-bounces test-leave at wrightthisway.com test-leave test-owner at wrightthisway.com test-owner test-request at wrightthisway.com test-request test-unsubscribe at wrightthisway.com test-unsubscribe From mark at msapiro.net Mon Jan 3 20:06:20 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 3 Jan 2011 11:06:20 -0800 Subject: [Mailman-Users] A basic filtering MIME question In-Reply-To: <4D214A71.5030901@8es.com> Message-ID: yahoo wrote: >I've been reading the FAQ's etc and asking local advice; but I must be >doing something stoopid. > >MM2.1.3 under Linux, 2.6.18-164.el5 2.1.3? This is quite old. Current is 2.1.14. >My goal is: > >a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers >& archives. > >b) /dev/null the attachments, both in delivery and archives. filter_content - Yes filter_mime_types - empty pass_mime_types - multipart message/rfc822 (allows plain text and converted HTML from attached messages. Remove to filter attached messages) text/plain text/html filter_filename_extensions - exe bat cmd com pif scr vbs cpl (these are defaults - this setting doesn't exist in 2.1.3) pass_filename_extensions - empty; default; this setting doesn't exist in 2.1.3) collapse_alternatives - Yes (this setting doesn't exist in 2.1.3) convert_html_to_plaintext - Yes -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Jan 3 20:34:46 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 3 Jan 2011 11:34:46 -0800 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user In-Reply-To: Message-ID: Jim Wright wrote: >However, I cannot send email to this list without the mail being rejected back as being to an unknown user. > >Based on all of my reading, I think I've done everything correctly. From my Postfix log, it doesn't appear that the aliases file is being consulted at all, but I am seeing a line indicating that the virtual-mailman file was referenced. That is correct. Aliases are not consulted because the virtual mapping in virtual-mailman is test at wrightthisway.com test This maps 'test at wrightthisway.com' to 'test'. The unqualified address 'test' is assumed by Postfix to be qualified with $myorigin, which defaults to $myhostname which is 'wrightthisway.com' which is a virtual domain. Aliases only apply to local domains, i.e., those in $mydestination. [...] >sh-3.2# postconf -n >address_verify_sender = <> >alias_database = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases The above should be in alias_maps, not alias_database. Fixing this may solve your problem, but it I suspect it will not be sufficient. >alias_maps = hash:/etc/postfix/aliases [...] >mydestination = At a minimum, mydestination should include localhost. >mydomain = wrightthisway.com >myhostname = wrightthisway.com [...] >virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf, hash:/usr/local/mailman/data/virtual-mailman [...] >Jan 2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: to=, relay=virtual, delay=0.1, delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: "test at wrightthisway.com") In order for aliases to be consulted, delivery must be 'local' not 'virtual' The solution in your case is to put hash:/usr/local/mailman/data/aliases in alias_maps; add localhost to mydestination and put VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' in mm_cfg.py and run Mailman's bin/genaliases to create virtual-mailman mappings like test at wrightthisway.com test at localhost -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rickmorrison at gmail.com Mon Jan 3 23:12:40 2011 From: rickmorrison at gmail.com (Rick Morrison) Date: Mon, 3 Jan 2011 17:12:40 -0500 Subject: [Mailman-Users] Pruning archived messages In-Reply-To: References: Message-ID: On Thu, Dec 9, 2010 at 11:53 PM, Mark Sapiro wrote: > Rick Morrison wrote: > > >I've been asked to restrict our group's Mailman list to showing only the > >last six months of archives. Is there any way to remove archived messages > >older than a certain date and reflect that removal in the archive header's > >"index.html" file? > > > Edit the archives/private/listname.mbox/listname.mbox file to remove > all the older messages. If you don't care about keeping the older > messages at all, just edit the file in place and then run Mailman's > > bin/arch --wipe listname > Thanks to both repliers - this worked well. I ended up using "archivemail" ( http://archivemail.sourceforge.net/manpage.html) for the mbox handling and running the whole thing from a cron-launched Python script. From yahoo at 8es.com Tue Jan 4 03:28:42 2011 From: yahoo at 8es.com (yahoo) Date: Mon, 03 Jan 2011 21:28:42 -0500 Subject: [Mailman-Users] A basic filtering MIME question In-Reply-To: References: Message-ID: <4D2285DA.1080602@8es.com> On 1/3/11 2:06 PM, Mark Sapiro wrote: >> I've been reading the FAQ's etc and asking local advice; but I must be >> doing something stoopid. >> >> MM2.1.3 under Linux, 2.6.18-164.el5 > > > 2.1.3? This is quite old. Current is 2.1.14. I'll ask the local maintainer to upgrade. Ooops, he says there's no RPM we can use {until we fix something else, I assume.} >> My goal is: >> >> a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers >> & archives. >> >> b) /dev/null the attachments, both in delivery and archives. > > > > filter_content - Yes > filter_mime_types - empty > pass_mime_types - > multipart > message/rfc822 (allows plain text and converted HTML from attached > messages. Remove to filter attached messages) > text/plain > text/html > filter_filename_extensions - > exe bat cmd com pif scr vbs cpl > (these are defaults - this setting doesn't exist in 2.1.3) > pass_filename_extensions - empty; default; this setting doesn't exist > in 2.1.3) > collapse_alternatives - Yes (this setting doesn't exist in 2.1.3) > convert_html_to_plaintext - Yes Err, I see all those in our 2.1.3... (I've been helped by Brad who has pointed out some issues I need to better understand.) Thank you. I'll add a comment. FAQ 1.8 is confusing because it does not make it clear what comments relate to 2.0, and what to 2.1. Further, it's discussing both HTML & MIME issues. From mark at msapiro.net Tue Jan 4 04:34:06 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 03 Jan 2011 19:34:06 -0800 Subject: [Mailman-Users] A basic filtering MIME question In-Reply-To: <4D2285DA.1080602@8es.com> References: <4D2285DA.1080602@8es.com> Message-ID: <4D22952E.508@msapiro.net> On 1/3/2011 6:28 PM, yahoo wrote: > On 1/3/11 2:06 PM, Mark Sapiro wrote: >> filter_content - Yes >> filter_mime_types - empty >> pass_mime_types - >> multipart >> message/rfc822 (allows plain text and converted HTML from attached >> messages. Remove to filter attached messages) >> text/plain >> text/html >> filter_filename_extensions - >> exe bat cmd com pif scr vbs cpl >> (these are defaults - this setting doesn't exist in 2.1.3) >> pass_filename_extensions - empty; default; this setting doesn't exist >> in 2.1.3) >> collapse_alternatives - Yes (this setting doesn't exist in 2.1.3) >> convert_html_to_plaintext - Yes > > Err, I see all those in our 2.1.3... Then it's not 2.1.3 because the *_filename_extensions settings didn't appear until 2.1.6 and collapse_alternatives first appeared in 2.1.7. Maybe it's 2.1.13? Or maybe it's 2.1.9 which is the RedHat el5 RPM version. > I'll add a comment. FAQ 1.8 is confusing because it does not make it > clear what comments relate to 2.0, and what to 2.1. > > Further, it's discussing both HTML & MIME issues. Agreed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From yahoo at 8es.com Tue Jan 4 04:58:06 2011 From: yahoo at 8es.com (yahoo) Date: Mon, 03 Jan 2011 22:58:06 -0500 Subject: [Mailman-Users] A basic filtering MIME question In-Reply-To: <4D22952E.508@msapiro.net> References: <4D2285DA.1080602@8es.com> <4D22952E.508@msapiro.net> Message-ID: <4D229ACE.2060801@8es.com> On 1/3/11 10:34 PM, Mark Sapiro wrote: > > Maybe it's 2.1.13? Or maybe it's 2.1.9 which is the RedHat el5 RPM version. My bad; that it is... >> I'll add a comment. FAQ 1.8 is confusing because it does not make it >> clear what comments relate to 2.0, and what to 2.1. >> >> Further, it's discussing both HTML& MIME issues. > > Agreed. From jim at wrightthisway.com Tue Jan 4 06:17:57 2011 From: jim at wrightthisway.com (Jim Wright) Date: Mon, 3 Jan 2011 23:17:57 -0600 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user In-Reply-To: References: Message-ID: <57EBF416-E799-4891-89E0-B91C52588CC3@wrightthisway.com> On Jan 3, 2011, at 1:34 PM, Mark Sapiro wrote: > In order for aliases to be consulted, delivery must be 'local' not > 'virtual' > > The solution in your case is to put > hash:/usr/local/mailman/data/aliases in alias_maps; add localhost to > mydestination and put > > VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' > > in mm_cfg.py and run Mailman's bin/genaliases to create virtual-mailman > mappings like > > test at wrightthisway.com test at localhost Hi, Mark. I appreciate the suggestions, but I was hesitant to reconfigure my postfix that way, for fear of borking my working virtual domains. I should have mentioned earlier that I have my site configured using postfix admin, and after seeing your mention of changing the delivery, that got me thinking about the problem in more depth. I did some new googling using postfixadmin and mailman, and came across this page: http://freemars.org/howto/mailman.html, this got me a lot closer, I just needed to track down the most recent postfix-to-mailman.py script, make the required edits for my site, and I have now successfully created and sent email to my test list. Thanks! From bruceclark at icon.co.za Tue Jan 4 07:27:08 2011 From: bruceclark at icon.co.za (bruce clark) Date: Tue, 4 Jan 2011 08:27:08 +0200 Subject: [Mailman-Users] Selective Filtering Message-ID: <0342E842-7DA3-4115-832A-99E33C1B3A3B@icon.co.za> Good morning from South Africa. Thanks to everyone who replied to my sig file question. I have another - related - question. Is there a way to have a selective filter? i.e I want to remove the images from some users' sig files, but allow images from others. I currently have image/jpeg image/pjpeg image/jpeg image/jpeg image/pjpeg image/jpeg image/pjpeg image/jpeg image/pjpeg image/x-jps in the filter_mime_types field. This is working but there are some users which I would like for it to not apply to. Thanks for any help Regards, Bruce. From mark at msapiro.net Tue Jan 4 19:12:07 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 4 Jan 2011 10:12:07 -0800 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user In-Reply-To: <57EBF416-E799-4891-89E0-B91C52588CC3@wrightthisway.com> Message-ID: Jim Wright wrote: > >I did some new googling using postfixadmin and mailman, and came across this page: http://freemars.org/howto/mailman.html, this got me a lot closer, I just needed to track down the most recent postfix-to-mailman.py script, make the required edits for my site, and I have now successfully created and sent email to my test list. While this may be an acceptable solution for you, you should be aware that use of postfix_to_mailman.py will create the same issues for non-list mail to the list domain that you had originally for list mail. I.e. postfix_to_mailman.py is designed for situations where there is a dedicated domain or domains for list mail only. You can work around this by generating transport maps to map only list addresses to the postfix_to_mailman.py (mailman) transport using the method of the FAQ at substituting 'mailman' for 'local'. But then you could also use aliases with this method by specifying the local transport. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jan 4 19:19:07 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 4 Jan 2011 10:19:07 -0800 Subject: [Mailman-Users] Selective Filtering In-Reply-To: <0342E842-7DA3-4115-832A-99E33C1B3A3B@icon.co.za> Message-ID: bruce clark wrote: > >Thanks to everyone who replied to my sig file question. I have another >- related - question. Is there a way to have a selective filter? i.e I >want to remove the images from some users' sig files, but allow images >from others. > >I currently have > >image/jpeg >image/pjpeg >image/jpeg >image/jpeg >image/pjpeg >image/jpeg >image/pjpeg >image/jpeg >image/pjpeg >image/x-jps > >in the filter_mime_types field. This is working but there are some >users which I would like for it to not apply to. There is no way to apply different content filtering rules for different member's posts without either modifying Mailman/Handlers/MimeDel.py or, to be more upgrade proof, replacing it with a custom version (sse the FAQ at ). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From hammond at txcorp.com Tue Jan 4 23:49:07 2011 From: hammond at txcorp.com (Anne M. Hammond) Date: Tue, 4 Jan 2011 15:49:07 -0700 Subject: [Mailman-Users] Custom message or addition to "Your message to {list} awaits moderator approval" message Message-ID: <60F2340B-81CC-4DF2-97ED-AE35E82CEB1D@txcorp.com> mailman-2.1.9-4.el5 We would like to modify the bounce message that moderated members receive. We have modified Privacy options/Sender filters/Text to include in any rejection notice to be sent to moderated members who post to the list. config_list reports that this field has been updated: # Text to include in any rejection # notice to be sent to moderated members who post to this list. member_moderation_notice = """Include this text. """ However, this is the bounce message that I receive. I am a moderated member of the list. This is the default message: ---------- Your mail to 'Internal' with the subject another test of moderation Is being held until the list moderator can review it for approval. The reason it is being held: Post to moderated list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: ... ---------- What am I missing? Thanks in advance < Anne From jim at wrightthisway.com Wed Jan 5 00:08:53 2011 From: jim at wrightthisway.com (Jim Wright) Date: Tue, 4 Jan 2011 17:08:53 -0600 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user In-Reply-To: References: Message-ID: On Jan 4, 2011, at 12:12 PM, Mark Sapiro wrote: > Jim Wright wrote: >> >> I did some new googling using postfixadmin and mailman, and came across this page: http://freemars.org/howto/mailman.html, this got me a lot closer, I just needed to track down the most recent postfix-to-mailman.py script, make the required edits for my site, and I have now successfully created and sent email to my test list. > > > While this may be an acceptable solution for you, you should be aware > that use of postfix_to_mailman.py will create the same issues for > non-list mail to the list domain that you had originally for list mail. > > I.e. postfix_to_mailman.py is designed for situations where there is a > dedicated domain or domains for list mail only. Right, I did create a separate domain for the lists, I didn't see it as being a huge issue. It was definitely easier than revamping my postfix config. ;) Thanks, Mark! From mark at msapiro.net Wed Jan 5 00:18:56 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 4 Jan 2011 15:18:56 -0800 Subject: [Mailman-Users] Custom message or addition to "Your message to{list} awaits moderator approval" message In-Reply-To: <60F2340B-81CC-4DF2-97ED-AE35E82CEB1D@txcorp.com> Message-ID: Anne M. Hammond wrote: > >We would like to modify the bounce message that moderated members >receive. We have modified Privacy options/Sender filters/Text to >include >in any rejection notice to be sent to moderated members who post to >the list. > >config_list reports that this field has been updated: > ># Text to include in any # href="?VARHELP/privacy/sender/member_moderation_action" >rejection ># notice to be sent to moderated members who post to this list. >member_moderation_notice = """Include this text. >""" > >However, this is the bounce message that I receive. I am a moderated >member of the list. This is the default message: > >---------- > >Your mail to 'Internal' with the subject > > another test of moderation > >Is being held until the list moderator can review it for approval. The text in member_moderation_notice is only sent in a "rejection" notice to the user when the post is rejected because member_moderation_action is Reject. It doesn't apply if member_moderation_action is Hold. Further, it doesn't even apply if the post is held and subsequently rejected by a moderator. In that case, the default rejection reason is still the standard 'Your message was deemed inappropriate by the moderator.' or it's i18n equiovalent. You cannot modify the held post notice for moderated members only. You can create a modified postheld.txt template per the FAQ at , but it will apply to all held posts regardless of reason. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From s.kronenwerth at tuhh.de Tue Jan 4 20:46:40 2011 From: s.kronenwerth at tuhh.de (Sebastian Kronenwerth) Date: Tue, 04 Jan 2011 20:46:40 +0100 Subject: [Mailman-Users] Problem with Postfix/virtual setup, unknown user In-Reply-To: References:

> >causes an undeliverable message by mailman sent to >surname at mailman.lrz-muenchen.de, if the list in a closed list: It is not the umlaut that causes the problem. It is the comma. >Outlook Exchange goes conform with RFC 2047 . You are correct, but this is tricky. The intent of RFC 2047 section 5, rule 3 is that an encoded word such as =?iso-8859-1?Q?Mai=2C_G=FCnter?= when used as the real name portion of an address will not contain any of the characters which are not allowed unquoted in this context, and this is true of that encoded word. However, Mailman looks at the From: header, and because of the way it processes this, it sees an ascii decoded header value which looks like 'Mai, G?nter '. It then parses this and gets two email addresses, 'mai' and 'guenter.mai at lrz.de' because of the unquoted comma. For some purposes, such as determining whether a post is from a list member, Mailman considers all the addresses and will determine that this is from a list member if 'guenter.mai at lrz.de' is a member, but if the post is held for some reason such as 'guenter.mai at lrz.de' is moderated, the notice to the user will be sent to only the first address 'mai' which is invalid. So, yes, you are correct that Mailman is not doing the right thing here. I've developed a patch that I think will fix this without any other side effects. I've attached that as rfc2047.patch.txt. Please try this patch and see if it solves your problems. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rfc2047.patch.txt URL: From mark at msapiro.net Wed Jan 12 02:32:49 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 11 Jan 2011 17:32:49 -0800 Subject: [Mailman-Users] {Disarmed} Re: User unknown in virtual mailbox table In-Reply-To: Message-ID: Umarzuki Mochlis wrote: >> ># postconf -n >alias_database = hash:/etc/postfix/aliases >alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases Good. [...] >mydestination = $myhostname, localhost, localhost.localdomain, >localhost.$myhostname >mydomain = mydomain.my >myhostname = mail-server.mydomain.my So mail-server.mydomain.my is in mydestination and is thus a postfix local domain, yet it seems to use the dovecot LDA rather than Postfix local delivery. [...] >relay_domains = $mydestination, proxy:ldap:/etc/postfix/ >ldap_relay_domains.cf >relay_recipient_maps = proxy:mysql:/etc/postfix/ >mysql_virtual_mailbox_maps.cf But here, $mydestination is a relay domain so possibly relay_recipient_maps is overriding transport_maps and that is why list addresses are relayed to dovecot rather than local [...] >transport_maps = proxy:ldap:/etc/postfix/ldap_transport_maps_user.cf, >proxy:ldap:/etc/postfix/ldap_transport_maps_domain.cf, >hash:/etc/mailman/transport-mailman OK > ># ls -l /etc/mailman/ >total 220 >-rw-r----- 1 root mailman 41 Dec 8 18:25 adm.pw >-rw-rw---- 1 root mailman 33942 Jan 3 16:55 aliases >-rw-r----- 1 root mailman 77824 Jan 3 16:55 aliases.db >-rw-r----- 1 root mailman 41 Dec 8 18:26 creator.pw >lrwxrwxrwx 1 root mailman 34 Dec 8 18:12 mm_cfg.py -> >/usr/lib/mailman/Mailman/mm_cfg.py >-rw-r--r-- 1 root mailman 14114 Jan 23 2008 sitelist.cfg >-rw-rw-r-- 1 root mailman 24376 Jan 3 16:55 transport-mailman >-rw-r--r-- 1 root mailman 45056 Jan 3 16:55 transport-mailman.db >-rw-rw---- 1 root mailman 28283 Jan 3 16:55 virtual-mailman >-rwxr-x--- 1 root mailman 141 Jan 3 16:48 virtual_to_transport OK ># cat /etc/mailman/mm_cfg.py ># -*- python -*- [...] >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail-server.mydomain.my'] Good. [...] >#DEFAULT_URL_HOST = fqdn >DEFAULT_URL_HOST = "mail-server.mydomain.my" >#DEFAULT_EMAIL_HOST = fqdn >DEFAULT_EMAIL_HOST = "mail-server.mydomain.my" >#VIRTUAL_HOSTS.clear() Better to uncomment the above VIRTUAL_HOSTS.clear() but it doesn't affect this issue. ># Because we've overriden the virtual hosts above add_virtualhost ># MUST be called after they have been defined. > >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST, ) Good. [...] >MTA = 'Postfix' >POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport' Good. This all looks good except the Postfix things I noted above. The hash:/etc/mailman/transport-mailman entry in transport_maps should specify the 'local' transport for the list addresses, but somehow this is overriden, possibly by relay_recipient_maps, and the dovecot LDA is used for these addresses. This is why it doesn't work. Exactly what to do to fix it is beyond my Postfix expertise. It seems to me that transport_maps should take priority in defining the transport used for a matching address. Have you redefined the 'local' transport in master.cf to use dovecot? If so, this can't work with Mailman. If so, you could define another transport, say 'reallylocal' to use postfix local delivery, and modify the sed command in /etc/mailman/virtual_to_transport to specify that transport. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Werner.Spirk at lrz.de Wed Jan 12 15:01:28 2011 From: Werner.Spirk at lrz.de (Werner Spirk) Date: Wed, 12 Jan 2011 15:01:28 +0100 (MET) Subject: [Mailman-Users] German umlaut in From-line using outlook exchangewith closed lists In-Reply-To: References: Message-ID: Hello Mark, I put in your patch and it works !! Thank you very much Werner On Tue, 11 Jan 2011, Mark Sapiro wrote: > Werner Spirk wrote: > > > > >Mails sent from outlook exchange will not be sent to a closed list > >when there is a German umlaut within the name like > > > >From: =?iso-8859-1?Q?Mai=2C_G=FCnter?= > > > >in general: > > > >Mail sent > >From: =?iso-8859-1?Q?Surname=2C_Givenname?=

> > > >causes an undeliverable message by mailman sent to > >surname at mailman.lrz-muenchen.de, if the list in a closed list: > > > It is not the umlaut that causes the problem. It is the comma. > > > >Outlook Exchange goes conform with RFC 2047 . > > > You are correct, but this is tricky. The intent of RFC 2047 section 5, > rule 3 is that an encoded word such as > =?iso-8859-1?Q?Mai=2C_G=FCnter?= when used as the real name portion of > an address will not contain any of the characters which are not > allowed unquoted in this context, and this is true of that encoded > word. > > However, Mailman looks at the From: header, and because of the way it > processes this, it sees an ascii decoded header value which looks like > 'Mai, G?nter '. It then parses this and gets two > email addresses, 'mai' and 'guenter.mai at lrz.de' because of the > unquoted comma. > > For some purposes, such as determining whether a post is from a list > member, Mailman considers all the addresses and will determine that > this is from a list member if 'guenter.mai at lrz.de' is a member, but > if the post is held for some reason such as 'guenter.mai at lrz.de' is > moderated, the notice to the user will be sent to only the first > address 'mai' which is invalid. > > So, yes, you are correct that Mailman is not doing the right thing here. > > I've developed a patch that I think will fix this without any other > side effects. I've attached that as rfc2047.patch.txt. Please try this > patch and see if it solves your problems. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > +--------------------------------------------------------------------+ | Werner Spirk . . Tel.: +49 89 35831 8707 | | Leibniz-Rechenzentrum (_) (_) Fax : +49 89 35831 8507 | | Boltzmannstr. 1 | | | | | | 85748 Garching |o| |o| Email: Spirk at lrz.de | | | |/\| | | | Deutschland bei M?nchen http://www.lrz.de/~spirk/ | +--------------------------------------------------------------------+ From Werner.Spirk at lrz.de Wed Jan 12 15:08:56 2011 From: Werner.Spirk at lrz.de (Werner Spirk) Date: Wed, 12 Jan 2011 15:08:56 +0100 (MET) Subject: [Mailman-Users] German umlaut in From-line using outlook exchangewith closed lists In-Reply-To: References: Message-ID: On Wed, 12 Jan 2011, Werner Spirk wrote: > > Hello Mark, > > I put in your patch and it works !! That was mine: the test was sent to an open list sorry -- it didn't do here the diffs ( are the patches correct?): diff Message.py Message.py.orig 1c1 < # Copyright (C) 1998-2011 by the Free Software Foundation, Inc. --- > # Copyright (C) 1998-2009 by the Free Software Foundation, Inc. 154,156c154 < # Actually, just get the raw header as one line in case the < # decoded words contain a comma. < fieldval = Utils.oneline(fieldval, 'us-ascii', raw=True) --- > fieldval = Utils.oneline(fieldval, 'us-ascii') 212c210 < fieldvals = [Utils.oneline(fv, 'us-ascii', raw=True) --- > fieldvals = [Utils.oneline(fv, 'us-ascii') diff Utils.py U.orig UserDesc.py Utils.py Utils.py.orig UserDesc.pyc Utils.pyc Utils.py.roig lxmhs42 mailman/Mailman> diff Utils.py Utils.py.orig 1c1 < # Copyright (C) 1998-2011 by the Free Software Foundation, Inc. --- > # Copyright (C) 1998-2010 by the Free Software Foundation, Inc. 889,892c889 < def oneline(s, cset, raw=False): < if raw: < # Just return the header as one line without decoding < return EMPTYSTRING.join(s.splitlines()) --- > def oneline(s, cset): Werner > > Thank you very much > > Werner > > > > On Tue, 11 Jan 2011, Mark Sapiro wrote: > > > Werner Spirk wrote: > > > > > > > >Mails sent from outlook exchange will not be sent to a closed list > > >when there is a German umlaut within the name like > > > > > >From: =?iso-8859-1?Q?Mai=2C_G=FCnter?= > > > > > >in general: > > > > > >Mail sent > > >From: =?iso-8859-1?Q?Surname=2C_Givenname?=

Once I fixed it to:

It all worked. So the problem was that there were 2 elements called 'language' in the form. Many thanks for the clue. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include From CNulk at scu.edu Thu Jan 20 00:35:06 2011 From: CNulk at scu.edu (C Nulk) Date: Wed, 19 Jan 2011 15:35:06 -0800 Subject: [Mailman-Users] Question about reg expr matches in matches_p (in Moderate.py) Message-ID: <4D37752A.1000308@scu.edu> Hello all, I am getting in my error log frequent entries like the following: Jan 19 14:51:32 2011 (31592) *_these_nonmembers in scu- references non-existent list SCU- To allow list members in several lists to cross post, I have added the appropriate @listname in the accept_these_nonmembers field. For example, there are two lists, ListA and ListB. ListA is in ListB's accept_these_nonmembers (as @ListA) and ListB is in ListA's accept_these_nonmembers (@ListB). The two lists are exclusive of one another (no member is in both lists). To my knowledge, this should work unless the regular expression and/or the listname are case-sensitive. So the question is, should the listnames in the *_these_nonmembers fields be all lowercase, all uppercase, or mixed case? So far, mixed case does not appear to be working. Thanks, Chris From scott at 916networks.com Thu Jan 20 01:06:59 2011 From: scott at 916networks.com (Scott Race) Date: Wed, 19 Jan 2011 17:06:59 -0700 Subject: [Mailman-Users] Attachment size limit (or max_message_size) In-Reply-To: References: Message-ID: Ah, I see what's going on. So for the particular lists were working on, all messages to the list are held for moderation. So, it seems clicking "Accept" will accept the message, even if the message size is too big. We recently (4 months ago) upgraded from Debian 4 to RHEL5. On the previous box, I believe we were running Mailman 2.1.12 (not sure), messages over the max_message_size limit would not hit the list and bounce back to the user with that message. The company I'm working with is hoping the system can kick back messages over the max_message_size before it hits moderation. Is that possible? Would adding GLOBAL_PIPELINE directives to mm_cfg.py get that done? Thanks! Scott -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Wednesday, January 19, 2011 1:22 PM To: Scott Race; mailman-users at python.org Subject: Re: [Mailman-Users] Attachment size limit (or max_message_size) Scott Race wrote: > >Running mailman 2.1.13 on RHEL5. From what I've read, the max_message_size setting in a list will be the max size for the message text (body) plus attachment. Therefore, max_message_size setting of 1000 would be approximately a megabyte for the message and any attachments. Correct. >I've set that for all my list, but can still get a 5MB attachment to go through no problem. Is there something I'm missing? The setting of 1000 should cause any message whose raw size is over 1 MB to be held for moderator approval with reason "Message body is too big: nnnn bytes with a limit of 1000 KB". This will not occur if the message is pre-approved with an Approved: header or first body line, but should occur in other cases. Of course, if a moderator approves it, it will go to the list. If you are sure it isn't working in your case, we'd need to see an actual example message to figure out why. You could send me one off list if you wish. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mcnutt at utk.edu Thu Jan 20 04:43:58 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Thu, 20 Jan 2011 03:43:58 +0000 Subject: [Mailman-Users] Make Install Fails Message-ID: <0CD7A72044B75D478D36624D96C5D4412F9BAF@kmbx1.utk.tennessee.edu> I'm attempting to install Mailman on a Solaris 10 box and I am unable to get past "make install." Sorry - not a unix guy, please use small words and explicit direction. Attached is the results of make install: Creating architecture independent directories... chmod o-r /usr/local/mailman/archives/private Creating architecture dependent directories... for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py; \ do \ .././install-sh -c -m 755 ../build/bin/$f /usr/local/mailman/bin; \ done for f in crontab.in; \ do \ .././install-sh -c -m 644 $f /usr/local/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled; \ do \ .././install-sh -c -m 755 ../build/cron/$f /usr/local/mailman/cron; \ done for i in ./*.jpg ./*.png; \ do \ .././install-sh -c -m 644 $i /usr/local/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/usr/local/mailman/$d; \ .././install-sh -c -m 644 paths.py $dir; \ done .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /export/home/local/mailman/mailman-2.1.9/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' From Richard at Damon-Family.org Thu Jan 20 06:06:05 2011 From: Richard at Damon-Family.org (Richard Damon) Date: Thu, 20 Jan 2011 00:06:05 -0500 Subject: [Mailman-Users] Advice on new install of Mailman to CentOS 5 Message-ID: Hi, I am looking at combining several hosting accounts into a single Virtual Private Server. One of these is being used to support a couple of mailing list running on Mailman 2.1.9 (I know that isn't current, but that is what they give me). The new server will be running CentOS 5, with Plesk Parallels as a control panel (I am not afraid to get down to the command line to do things, but also would claim to be an expert at it either, and the control panel makes some routine tasks easier). The question comes in that the CentOS 5 distribution only has a RPM for Mailman 2.1.9, instead of the recently released 2.1.14, so the question comes do I use the RPM from the distribution and run a version several years old, or is it better to install from a direct download. I am working of a fresh install so I don't need to worry about migrating existing list on the server, but I definitely want to be able to import the existing lists from the old server. (And will probably do at least one dry run of the migration to a different domain name just to make sure I know how to do this and that things work before moving the live site). Richard Damon From mcnutt at utk.edu Thu Jan 20 15:43:55 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Thu, 20 Jan 2011 14:43:55 +0000 Subject: [Mailman-Users] Recovering from Server Fail, was FW: Make Install Fails Message-ID: <0CD7A72044B75D478D36624D96C5D4412F9C3F@kmbx1.utk.tennessee.edu> I've continued to fiddle with this and now have different errors, so I thought I would back up and give ya'll the big picture in case I'm approaching this from the wrong direction. Tuesday morning I had a hardware failure on my old Solaris 10 box. In 25 years in the business, I don't think I've seen a hardware failure as thorough as this that didn't involve smoke. The machine is utterly unrecoverable. So to get back into service, I decided to move the service to a different box. It's also a Solaris box, but is a Sun X4100. I have restored the directory tree from tape, but presume that the executables can't be run on the new platform. What is the quickest way to get mailman back in service? Bill McNutt -----Original Message----- From: mailman-users-bounces+mcnutt=utk.edu at python.org [mailto:mailman-users-bounces+mcnutt=utk.edu at python.org] On Behalf Of McNutt Jr, William R Sent: Wednesday, January 19, 2011 10:44 PM To: mailman-users at python.org Subject: [Mailman-Users] Make Install Fails I'm attempting to install Mailman on a Solaris 10 box and I am unable to get past "make install." Sorry - not a unix guy, please use small words and explicit direction. Attached is the results of make install: Creating architecture independent directories... chmod o-r /usr/local/mailman/archives/private Creating architecture dependent directories... for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py; \ do \ .././install-sh -c -m 755 ../build/bin/$f /usr/local/mailman/bin; \ done for f in crontab.in; \ do \ .././install-sh -c -m 644 $f /usr/local/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled; \ do \ .././install-sh -c -m 755 ../build/cron/$f /usr/local/mailman/cron; \ done for i in ./*.jpg ./*.png; \ do \ .././install-sh -c -m 644 $i /usr/local/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/usr/local/mailman/$d; \ .././install-sh -c -m 644 paths.py $dir; \ done .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /export/home/local/mailman/mailman-2.1.9/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/mcnutt%40utk.edu From mark at msapiro.net Thu Jan 20 20:03:19 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 11:03:19 -0800 Subject: [Mailman-Users] Question about reg expr matches in matches_p (in Moderate.py) In-Reply-To: <4D37752A.1000308@scu.edu> References: <4D37752A.1000308@scu.edu> Message-ID: <4D3886F7.5010701@msapiro.net> On 1/19/2011 3:35 PM, C Nulk wrote: > > So the question is, should the listnames in the *_these_nonmembers > fields be all lowercase, all uppercase, or mixed case? So far, mixed > case does not appear to be working. The list name in @listname entries in *_these_nonmembers must be the internal name of the list, i.e. it is all lower case, and in distros such as cPanel that have munged listnames, it must be the name that's used in the web interface which may be different from the name in the posting address. Again, in cPanel for example, this is the listname_domain name, not simply listname. These are the only case sensitive entries in *_these_nonmembers. regexps and literal addresses are matched case insensitively. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mcnutt at utk.edu Thu Jan 20 20:18:15 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Thu, 20 Jan 2011 19:18:15 +0000 Subject: [Mailman-Users] Recovering from Server Fail, was FW: Make Install Fails Message-ID: <0CD7A72044B75D478D36624D96C5D4412FA104@kmbx1.utk.tennessee.edu> Here's some more information: At step 3.1 of the installation instructions, the ./configure step appears to run to completion, but then ends with a warning: can't change build. I don't get this when I run as root, but the instructions pretty clearly say that I should not be "root" when I run it. Is this the core of my problem? -----Original Message----- From: mailman-users-bounces+mcnutt=utk.edu at python.org [mailto:mailman-users-bounces+mcnutt=utk.edu at python.org] On Behalf Of Mark Sapiro Sent: Thursday, January 20, 2011 2:03 PM To: C Nulk Cc: MailMan Subject: Re: [Mailman-Users] Question about reg expr matches in matches_p (in Moderate.py) On 1/19/2011 3:35 PM, C Nulk wrote: > > So the question is, should the listnames in the *_these_nonmembers > fields be all lowercase, all uppercase, or mixed case? So far, mixed > case does not appear to be working. The list name in @listname entries in *_these_nonmembers must be the internal name of the list, i.e. it is all lower case, and in distros such as cPanel that have munged listnames, it must be the name that's used in the web interface which may be different from the name in the posting address. Again, in cPanel for example, this is the listname_domain name, not simply listname. These are the only case sensitive entries in *_these_nonmembers. regexps and literal addresses are matched case insensitively. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/mcnutt%40utk.edu From mark at msapiro.net Thu Jan 20 20:27:51 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 11:27:51 -0800 Subject: [Mailman-Users] Attachment size limit (or max_message_size) In-Reply-To: Message-ID: Scott Race wrote: >Ah, I see what's going on. So for the particular lists were working on, all messages to the list are held for moderation. So, it seems clicking "Accept" will accept the message, even if the message size is too big. Yes, and further, if the messages are held because the poster is moderated, this hold is applied before any of the miscellaneous holds, so all you know is it is a post from a moderated member, and if you approve it, it is approved even if too big. >We recently (4 months ago) upgraded from Debian 4 to RHEL5. On the previous box, I believe we were running Mailman 2.1.12 (not sure), messages over the max_message_size limit would not hit the list and bounce back to the user with that message. Without source modifications, the message would still be held, not rejected, but the user would be notified if respond_to_post_requests is Yes. >The company I'm working with is hoping the system can kick back messages over the max_message_size before it hits moderation. Is that possible? > >Would adding GLOBAL_PIPELINE directives to mm_cfg.py get that done? Yes, you could reorder the pipeline to put Hold ahead of Moderate, but the downside of this is a non-member post could be held for one of the miscellaneous hold reasons and the moderator may not realize it's a non-member post. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mcnutt at utk.edu Thu Jan 20 20:26:08 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Thu, 20 Jan 2011 19:26:08 +0000 Subject: [Mailman-Users] Recovering from Server Fail, was FW: Make Install Fails In-Reply-To: <0CD7A72044B75D478D36624D96C5D4412FA104@kmbx1.utk.tennessee.edu> References: <0CD7A72044B75D478D36624D96C5D4412FA104@kmbx1.utk.tennessee.edu> Message-ID: <0CD7A72044B75D478D36624D96C5D4412FA126@kmbx1.utk.tennessee.edu> Is this a fatal error for the ./configure step? checking for --with-mailhost... no checking for --with-urlhost... no Traceback (most recent call last): File "conftest.py", line 2, in from socket import * File "/usr/local/lib/python2.6/socket.py", line 46, in import _socket ImportError: ld.so.1: python: fatal: relocation error: file /usr/local/lib/python2.6/lib-dynload/_socket.so: symbol inet_aton: referenced symbol not found checking for default mail host name... Can't open conftest.out checking for default URL host component... Can't open conftest.out checking for strerror... (cached) yes -----Original Message----- From: mailman-users-bounces+mcnutt=utk.edu at python.org [mailto:mailman-users-bounces+mcnutt=utk.edu at python.org] On Behalf Of McNutt Jr, William R Sent: Thursday, January 20, 2011 2:18 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Recovering from Server Fail, was FW: Make Install Fails Here's some more information: At step 3.1 of the installation instructions, the ./configure step appears to run to completion, but then ends with a warning: can't change build. I don't get this when I run as root, but the instructions pretty clearly say that I should not be "root" when I run it. Is this the core of my problem? -----Original Message----- From: mailman-users-bounces+mcnutt=utk.edu at python.org [mailto:mailman-users-bounces+mcnutt=utk.edu at python.org] On Behalf Of Mark Sapiro Sent: Thursday, January 20, 2011 2:03 PM To: C Nulk Cc: MailMan Subject: Re: [Mailman-Users] Question about reg expr matches in matches_p (in Moderate.py) On 1/19/2011 3:35 PM, C Nulk wrote: > > So the question is, should the listnames in the *_these_nonmembers > fields be all lowercase, all uppercase, or mixed case? So far, mixed > case does not appear to be working. The list name in @listname entries in *_these_nonmembers must be the internal name of the list, i.e. it is all lower case, and in distros such as cPanel that have munged listnames, it must be the name that's used in the web interface which may be different from the name in the posting address. Again, in cPanel for example, this is the listname_domain name, not simply listname. These are the only case sensitive entries in *_these_nonmembers. regexps and literal addresses are matched case insensitively. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/mcnutt%40utk.edu ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/mcnutt%40utk.edu From mcnutt at utk.edu Thu Jan 20 20:32:31 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Thu, 20 Jan 2011 19:32:31 +0000 Subject: [Mailman-Users] Rr: Recovering from Server Fail Message-ID: <0CD7A72044B75D478D36624D96C5D4412FA140@kmbx1.utk.tennessee.edu> If I continue to "make install" I get the following error: .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 make: Fatal error: Command failed for target `install-packages' Current working directory /export/home/local/mailman-2.1.9/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' From mark at msapiro.net Thu Jan 20 21:05:21 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 12:05:21 -0800 Subject: [Mailman-Users] Rr: Recovering from Server Fail In-Reply-To: <0CD7A72044B75D478D36624D96C5D4412FA140@kmbx1.utk.tennessee.edu> Message-ID: McNutt Jr, William R wrote: >If I continue to "make install" I get the following error: > >.././install-sh -c -m 755 mailman /usr/local/mailman/scripts >.././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data >for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ >do \ > gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ > (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ >done >/usr/local/lib/python2.6/distutils/dist.py:250: UserWarning: 'licence' distribution option is deprecated; use 'license' > warnings.warn(msg) >src/hangul.c:33: error: syntax error before numeric constant >src/hangul.c:34: error: syntax error before numeric constant >error: command 'gcc' failed with exit status 1 >*** Error code 1 >make: Fatal error: Command failed for target `install-packages' >Current working directory /export/home/local/mailman-2.1.9/misc >*** Error code 1 >The following command caused the error: >for d in bin cron misc Mailman scripts src templates messages tests; \ >do \ > (cd $d; make DESTDIR= install); \ >done >make: Fatal error: Command failed for target `doinstall' There's a lot of stuff in the archives of this list about various solaris installation issues. Try googling "site:mail.python.org inurl:mailman solaris 10 codecs syntax". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jan 20 21:17:13 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 12:17:13 -0800 Subject: [Mailman-Users] Advice on new install of Mailman to CentOS 5 In-Reply-To: Message-ID: Richard Damon wrote: > >The question comes in that the CentOS 5 distribution only has a RPM >for Mailman 2.1.9, instead of the recently released 2.1.14, so the >question comes do I use the RPM from the distribution and run a >version several years old, or is it better to install from a direct >download. Quoting from the FAQ at It is possible to trick Plesk into recognizing newer versions installed manually but it's not for the faint of heart. >I am working of a fresh install so I don't need to worry >about migrating existing list on the server, but I definitely want to >be able to import the existing lists from the old server. (And will >probably do at least one dry run of the migration to a different >domain name just to make sure I know how to do this and that things >work before moving the live site). The actual migration of list data from the old to the new installation should be straightforward as long as the new installation is the same or a newer version. See the initial section of the FAQ at , and note that you may need to run fix_url to update list domains and this should be done prior to regenerating archives. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khillo100 at hotmail.com Thu Jan 20 12:30:31 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Thu, 20 Jan 2011 13:30:31 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: <4D34F892.2030604@msapiro.net> References: <4D34F892.2030604@msapiro.net> Message-ID: by the way, I keep deleting the following: /var/spool/mailman/bounces/*.pck /var/lib/mailman/data/*.pck because they fill up all the space on my small hard drives on my VPS servers.. is that why mailman's bounce processor removes the subscribers or because they does actually bounce until they reach the points limit? Thanks.. -----Original Message----- From: Mark Sapiro Sent: Tuesday, January 18, 2011 4:18 AM To: Khalil Abbas Cc: mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. On 1/17/2011 3:00 PM, Khalil Abbas wrote: > > is there way to tell mailman to send certain number of messages per > hour? The short answer is No, but see the FAQ at for other possible solutions. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From twigbranch at gmail.com Thu Jan 20 20:23:02 2011 From: twigbranch at gmail.com (Stefan Alder) Date: Thu, 20 Jan 2011 11:23:02 -0800 Subject: [Mailman-Users] Friendly email address Message-ID: Hi, I'd like to use Mailman for a distribution list and would prefer that the from address be of the form "Foo Bar " ... rather than just foobar at list.org. Is this possible? How do I need to input this in the configuration? Thanks From mark at msapiro.net Thu Jan 20 21:53:27 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 12:53:27 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: Khalil Abbas wrote: >by the way, I keep deleting the following: > >/var/spool/mailman/bounces/*.pck It looks like BounceRunner has died and is not processing the bounce queue. Chack Mailman's qrunner and error logs for more information. >/var/lib/mailman/data/*.pck Are these heldmsg-listname-*.pck files or bounce-events-*.pck files. If they are held messages, they should be removed with bin/discard or through the moderator interface, and setting the list's max_days_to_hold may help. If they are bounce-events-*.pck files, most of them are probably stale because of dying BounceRunners. Assuming you are not slicing queues, i.e., you have only one qrunner per queue, there should never be more than two of these, one with the PID of the current OutgoingRunner and one with the PID of the current BounceRunner. All the others are dead files left behind when a runner died or was killed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brohler at purdue.edu Thu Jan 20 22:05:27 2011 From: brohler at purdue.edu (Rohler, Brian L) Date: Thu, 20 Jan 2011 16:05:27 -0500 Subject: [Mailman-Users] unsubscribe Message-ID: From twigbranch at gmail.com Thu Jan 20 22:14:20 2011 From: twigbranch at gmail.com (Stefan Alder) Date: Thu, 20 Jan 2011 13:14:20 -0800 Subject: [Mailman-Users] Friendly email address In-Reply-To: References: Message-ID: I'm continuing to try various combinations but without any luck. Don't see this documented either. Any ideas or confirmation that this is not possible would really help. Thanks! On Thu, Jan 20, 2011 at 11:23 AM, Stefan Alder wrote: > Hi, > I'd like to use Mailman for a distribution list and would prefer that > the from address be of the form "Foo Bar " ... rather > than just foobar at list.org. ?Is this possible? ?How do I need to input > this in the configuration? > Thanks > From scott at 916networks.com Thu Jan 20 23:12:15 2011 From: scott at 916networks.com (Scott Race) Date: Thu, 20 Jan 2011 15:12:15 -0700 Subject: [Mailman-Users] Attachment size limit (or max_message_size) In-Reply-To: References: Message-ID: A few final questions to figure this out: 1. Has this always been the design? The client seems to think that on his old server the message would get kicked back before hitting the moderation queue. If so that's cool, just want to make sure I'm not missing something. 2. To make sure I understand - if we were to use GLOBAL_PIPELINE directives in mm_cfg.py to re-order, would that mean that email addresses not signed up and confirmed as members would be able to send to the list and have it go into the modertor's queue? 3. With a list of thousands of users, a 6MB attachment would kill our bandwidth if it went out. If we must moderate, is there any other solution other than the moderator looking at each email and deciding to kick it back due to size? Postfix limiting (ungraceful, I know)? Thanks! Scott -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Thursday, January 20, 2011 11:28 AM To: Scott Race; mailman-users at python.org Subject: Re: [Mailman-Users] Attachment size limit (or max_message_size) Scott Race wrote: >Ah, I see what's going on. So for the particular lists were working on, all messages to the list are held for moderation. So, it seems clicking "Accept" will accept the message, even if the message size is too big. Yes, and further, if the messages are held because the poster is moderated, this hold is applied before any of the miscellaneous holds, so all you know is it is a post from a moderated member, and if you approve it, it is approved even if too big. >We recently (4 months ago) upgraded from Debian 4 to RHEL5. On the previous box, I believe we were running Mailman 2.1.12 (not sure), messages over the max_message_size limit would not hit the list and bounce back to the user with that message. Without source modifications, the message would still be held, not rejected, but the user would be notified if respond_to_post_requests is Yes. >The company I'm working with is hoping the system can kick back messages over the max_message_size before it hits moderation. Is that possible? > >Would adding GLOBAL_PIPELINE directives to mm_cfg.py get that done? Yes, you could reorder the pipeline to put Hold ahead of Moderate, but the downside of this is a non-member post could be held for one of the miscellaneous hold reasons and the moderator may not realize it's a non-member post. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jan 20 23:34:27 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 14:34:27 -0800 Subject: [Mailman-Users] Friendly email address In-Reply-To: Message-ID: Stefan Alder wrote: >I'm continuing to try various combinations but without any luck. >Don't see this documented either. Any ideas or confirmation that this >is not possible would really help. Thanks! > >On Thu, Jan 20, 2011 at 11:23 AM, Stefan Alder wrote: >> Hi, >> I'd like to use Mailman for a distribution list and would prefer that >> the from address be of the form "Foo Bar " ... rather >> than just foobar at list.org. Is this possible? How do I need to input >> this in the configuration? If your Mailman is recent enough and if your list is anonymous_list = Yes the From: will be "Foo Bar " where "Foo Bar" is the list's description. Recent enough is 2.1.6 or later. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jan 20 23:45:51 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 20 Jan 2011 14:45:51 -0800 Subject: [Mailman-Users] Attachment size limit (or max_message_size) In-Reply-To: Message-ID: Scott Race wrote: >A few final questions to figure this out: > >1. Has this always been the design? The client seems to think that on his old server the message would get kicked back before hitting the moderation queue. If so that's cool, just want to make sure I'm not missing something. I don't know what code modifications might have been in place in the old server, but it has always worked this way in Mailman 2.1.x as distributed by the GNU Mailman project. >2. To make sure I understand - if we were to use GLOBAL_PIPELINE directives in mm_cfg.py to re-order, would that mean that email addresses not signed up and confirmed as members would be able to send to the list and have it go into the modertor's queue? Yes, but only if the post were subject to any of the miscellaneous holds processed by Mailman/Handlers/Hold.py. >3. With a list of thousands of users, a 6MB attachment would kill our bandwidth if it went out. If we must moderate, is there any other solution other than the moderator looking at each email and deciding to kick it back due to size? Postfix limiting (ungraceful, I know)? I would recommend a custom handler (see the FAQ at ) to be inserted in the pipeline ahead of Moderate whose job would be only to reject posts that are too big. Alternatively, you could put Hold first, but modify it to reject instead of hold. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From floeff at gmail.com Fri Jan 21 11:19:21 2011 From: floeff at gmail.com (Florian Effenberger) Date: Fri, 21 Jan 2011 11:19:21 +0100 Subject: [Mailman-Users] owner alias bounces In-Reply-To: <4D0C1F3A.6080604@msapiro.net> References: <4D0C1F3A.6080604@msapiro.net> Message-ID: Hi Mark, thanks for your reply, and sorry for my delay! 2010/12/18 Mark Sapiro : > The procedure for adding a host name is > > 1) Put the appropriate add_virtualhost() in mm_cfg.py. > 2) If Postfix is to generate virtual alias maps for this domain, add it > to POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py. > 3) To move any lists to that domain, run fix_url with the -u option on > the list(s) hm, do I get it right that I have to add the hostnames twice in mm_cfg.py when using Postfix, once in add_virtualhost, once in POSTFIX_STYLE_VIRTUAL_DOMAINS? Right now, I have DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST to lists.domain1.tld with the only add_virtualhost line being add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST). In addition, I have set POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.tld', 'lists.domain2.tld'], so the only occurence of domain2 is in POSTFIX_STYLE_VIRTUAL_DOMAINS. However, I have already wondered where to set the web URL. Right now, lists.domain2 still have lists.domain1 e.g. in the List-Archive header. Thanks, Florian From noah-list at enabled.com Thu Jan 20 23:35:42 2011 From: noah-list at enabled.com (Noah) Date: Thu, 20 Jan 2011 14:35:42 -0800 Subject: [Mailman-Users] pck files in /var/lib/mailman/data Message-ID: <4D38B8BE.9090007@enabled.com> Hi there, I have over 61000 heldmsg--.pck files in /var/lib/mailman/data for various mail list. They are binary so I cannot view them. I checked two of the lists that have these files associated with it and mailman does not see held messages via the web GUI. Do I need these messages or can they be deleted? Cheers, Noah From noah-list at enabled.com Thu Jan 20 23:32:32 2011 From: noah-list at enabled.com (Noah) Date: Thu, 20 Jan 2011 14:32:32 -0800 Subject: [Mailman-Users] mailman installation on ubuntu failing In-Reply-To: References: Message-ID: <4D38B800.3090407@enabled.com> > I don't know what the apt-get process does to undo what it had done up > to this point, but at this point, the new Mailman 2.1.9 had been > installed and all that was left to do was any necessary list data > migration. Since there aren't any data format changes between 2.1.9 > and 2.1.11, it was essentially done. > > If the installed package wasn't backed out, you can just manually run > Mailman's bin/update -f, but the real question is where did the 2.1.11 > version come from and why doesn't apt-get know about it? > > If I were you, I would look at Mailman's Mailman/Version.py file for > the version currently installed. If it is 2.1.11, then apt-get > reversed its changes, and what to do depends on whether you want to > leave 2.1.11 in place or overwrite it with 2.1.9. To leave it in > place, do nothing. You should be able to just start Mailman if it > isn't already running. > > To overwrite 2.1.11 with 2.1.9, remove Mailman's > data/last_mailman_version file or edit its contents which are > apparently 0x2010bf0 to something like 0x20108f0 and then re-run the > apt-get. > > On the other hand, if the version of Mailman's Mailman/Version.py file > is 2.1.9, then you have already over written the 2.1.11 version and > you can finish the process by stopping Mailman if it's running, then > run Mailman's > > bin/update -f > > and start Mailman. > okay that worked great - thanks Mark! :) From jlieber at goengineer.com Fri Jan 21 21:07:03 2011 From: jlieber at goengineer.com (John Lieber) Date: Fri, 21 Jan 2011 14:07:03 -0600 Subject: [Mailman-Users] Searching user list for mod bit Message-ID: <49314D57A0408341864E8641BB5285DC7C24557E85@AUSP01VMBX08.collaborationhost.net> Is there a way to search the entire user list for moderation bit. What I would like to do is search the list of users of my mailman lists to see who 'does not' have the moderation bit set. Had a situation the other day where a user replied to one of my lists and it went through because the person that added them unchecked the mod.... Thanks in advance, Johnathen From mcnutt at utk.edu Fri Jan 21 21:52:55 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Fri, 21 Jan 2011 20:52:55 +0000 Subject: [Mailman-Users] Solaris 10 and Python Message-ID: <0CD7A72044B75D478D36624D96C5D4412FB9EC@kmbx1.utk.tennessee.edu> Has anyone successfully made this work on a Sun Solaris 10? I've been at this for three days and no matter what I do, I only manage to change error messages. At this point I've made it through the ./configure step, but it's breaking on make install. It's a Sun Fire x4100 running solaris 10. I've got mailman 2.1.14 and python 2.6.2 If you've made it work under that configuration and are willing so show off your 'leet skills helping me deal with this, please shoot me a note at mcnutt at utk.edu. Bill From mark at msapiro.net Sat Jan 22 02:26:03 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 21 Jan 2011 17:26:03 -0800 Subject: [Mailman-Users] pck files in /var/lib/mailman/data In-Reply-To: <4D38B8BE.9090007@enabled.com> Message-ID: Noah wrote: > >I have over 61000 heldmsg--.pck files in >/var/lib/mailman/data for various mail list. They are binary so I >cannot view them. You can view them with Mailman's bin/dumpdb >I checked two of the lists that have these files >associated with it and mailman does not see held messages via the web >GUI. Do I need these messages or can they be deleted? If the messages do not show up in the admindb GUI for the associated list (usually it's the converse that's true - i.e.people rm the files and the requests.pck data doesn't get updated), the files can be removed, but in all cases it is better to use Mailman's bin/discard to remove them. See the FAQ at . You should also consider using the lists' max_days_to_hold setting to keep large numbers of held messages from accumulating. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khillo100 at hotmail.com Fri Jan 21 10:15:17 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Fri, 21 Jan 2011 11:15:17 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: well, attached are parts of the error and qrunner logs.. I also forgot to mention that I also delete the following files: rm /var/lib/mailman/data/*.pck -f rm /var/lock/mailman/*.* -f the first one also eats up my little space on the hard drive, and the other locks the lists n they can?t send.. what I need to know, why the subscribers are being removed? is it because of misconfiguration of mailman? or because of outside MTA?s like yahoo and hotmail rejecting mail from my servers because I need to control the flow of messages going out from my servers? another thing worth to mention, the servers are not blocked by hotmail because I sent single test messages from all my servers to some of my subscribers that were removed from my lists and they received them with no problems.. Thanks.. -----Original Message----- From: Mark Sapiro Sent: Friday, January 21, 2011 12:21 AM To: Khalil Abbas Subject: Re: [Mailman-Users] control mail distribution .. Khalil Abbas wrote: > >if the bounce runner keeps dying, then why the subscribers keep being >removed?? Because it doesn't die always? You're the one with the logs and other evidence that might enable someone to answer this. >and I understand the conclusion to my previously asked question, >deleting these files does not get the subscribers to be removed right? Right. Deleting *.pck files from /var/spool/mailman/bounce will result in those specific bounce messages (each file is one queued bounce message) being lost and therefore not processed. Likewise, deleting bounce-events-*.pck files from /var/lib/mailman/data/ will in the case of active files result in the bounce information in the file being unprocessed, and in the case of "dead" files have no effect because whatever residual bounce info is in those files is lost. In any event, removing these files will result only in bounce scores not being incremented and subscribers not being removed, not the reverse. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: error.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: qrunnerx.txt URL: From grschmidt at acm.org Sat Jan 22 03:17:08 2011 From: grschmidt at acm.org (Gary R. Schmidt) Date: Sat, 22 Jan 2011 13:17:08 +1100 Subject: [Mailman-Users] Solaris 10 and Python In-Reply-To: References: Message-ID: <4D3A3E24.8040202@acm.org> On 22/01/2011 12:40 PM, "McNutt Jr, William R" wrote: > > Has anyone successfully made this work on a Sun Solaris 10? I've > been at this for three days and no matter what I do, I only manage > to change error messages. At this point I've made it through the > ./configure step, but it's breaking on make install. > > It's a Sun Fire x4100 running solaris 10. I've got mailman 2.1.14 > and python 2.6.2 Worked out of the box for me: ./configure \ --prefix=/data/mailman \ --with-python=/opt/webstack/bin/python \ --with-cgi-gid=webservd \ --with-mailhost=mail.mydomain \ --with-urlhost=www.mydomain \ --with-gcc=no Note that I have SunStudio, WebStack, and Postfix (built from source) on this machine. > If you've made it work under that configuration and are willing so > show off your 'leet skills helping me deal with this, please shoot > me a note at mcnutt at utk.edu. Ask on the list, get answered on the list :->' Cheers, Gary B-) From mcnutt at utk.edu Sat Jan 22 05:10:36 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Sat, 22 Jan 2011 04:10:36 +0000 Subject: [Mailman-Users] Transferring Lists Message-ID: <0CD7A72044B75D478D36624D96C5D4412FBCB4@kmbx1.utk.tennessee.edu> I am recovering from a catastrophic hardware failure. I have a tape backup of mailman, lists and all, and I would like to restore it to the new hardware. I have successfully installed mailman on the new server. Can anyone refer me to a document that will guide me through re-constructing my list from those old files? Bill From mark at msapiro.net Sat Jan 22 19:48:55 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 10:48:55 -0800 Subject: [Mailman-Users] Searching user list for mod bit In-Reply-To: <49314D57A0408341864E8641BB5285DC7C24557E85@AUSP01VMBX08.collaborationhost.net> Message-ID: John Lieber wrote: >Is there a way to search the entire user list for moderation bit. If you have command line access, see the withlist script at . If you don't, see the script at which can output a .csv file by screen scraping the web admin Membership List. You can then import the .csv into a spread sheet and search the "mod" column. The above scripts are mirrored at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From noah-list at enabled.com Sat Jan 22 21:51:38 2011 From: noah-list at enabled.com (Noah) Date: Sat, 22 Jan 2011 12:51:38 -0800 Subject: [Mailman-Users] pck files in /var/lib/mailman/data In-Reply-To: References: Message-ID: <4D3B435A.7050106@enabled.com> On 1/21/11 5:26 PM, Mark Sapiro wrote: > Noah wrote: >> >> I have over 61000 heldmsg--.pck files in >> /var/lib/mailman/data for various mail list. They are binary so I >> cannot view them. > > > You can view them with Mailman's bin/dumpdb > > >> I checked two of the lists that have these files >> associated with it and mailman does not see held messages via the web >> GUI. Do I need these messages or can they be deleted? > > > If the messages do not show up in the admindb GUI for the associated > list (usually it's the converse that's true - i.e.people rm the files > and the requests.pck data doesn't get updated), the files can be > removed, but in all cases it is better to use Mailman's bin/discard to > remove them. See the FAQ at. > > You should also consider using the lists' max_days_to_hold setting to > keep large numbers of held messages from accumulating. thanks so much Mark. is there a way to set the "max_days_to_hold" variable in the mm_cfg.py file so all the lists have the variable set by default? Cheers, Noah > From mark at msapiro.net Sat Jan 22 23:49:58 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 14:49:58 -0800 Subject: [Mailman-Users] owner alias bounces In-Reply-To: Message-ID: Florian Effenberger wrote: > >2010/12/18 Mark Sapiro : > >> The procedure for adding a host name is >> >> 1) Put the appropriate add_virtualhost() in mm_cfg.py. >> 2) If Postfix is to generate virtual alias maps for this domain, add it >> to POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py. >> 3) To move any lists to that domain, run fix_url with the -u option on >> the list(s) > >hm, do I get it right that I have to add the hostnames twice in >mm_cfg.py when using Postfix, once in add_virtualhost, once in >POSTFIX_STYLE_VIRTUAL_DOMAINS? Maybe. It depends on what you are ultimately doing. >Right now, I have DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST to >lists.domain1.tld with the only add_virtualhost line being >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST). OK. That's good. >In addition, I >have set POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.tld', >'lists.domain2.tld'], so the only occurence of domain2 is in >POSTFIX_STYLE_VIRTUAL_DOMAINS. That may be OK. If lists.domain1.tld and lists.domain2.tld are both virtual_alias_domains in postfix or otherwise require virtual_alias_maps, then you need POSTFIX_STYLE_VIRTUAL_DOMAINS as you have it. This controls what lists get entries generated in virtual-mailman for virtual_alias_maps. >However, I have already wondered where to set the web URL. Right now, >lists.domain2 still have lists.domain1 e.g. in the List-Archive >header. You want an additional add_virtualhost like add_virtualhost('lists.domain2.tld', 'lists.domain2.tld') This is so that you can go to http://lists.domain2.tld/mailman/create (or whatever this translates to in your installation) and create a list and it will be created with the proper http://lists.domain2.tld/mailman/ web_page_url and lists.domain2.tld host_name. Also you can use "bin/newlist -u lists.domain2.tld" to create a list properly in this domain, and you can use bin/withlist -l -r fix_url -u lists.domain2.tld existing-listname to fix the web_page_url and host_name for an existing domain2 list (after doing that, you may need to run bin/genaliases to update virtual-mailman). This will make appropriate links with host lists.domain2.tld in the List-* headers in posts, on all dynamic web pages and all new or modified archive pages for the list. However, existing static archive pages will still have "listinfo" links with the old domain. These either have to be ignored, edited manually or updated by rebuilding the list's entire archive with "bin/arch --wipe listname". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Jan 22 23:59:41 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 14:59:41 -0800 Subject: [Mailman-Users] pck files in /var/lib/mailman/data In-Reply-To: <4D3B435A.7050106@enabled.com> Message-ID: Noah wrote: > >is there a way to set the "max_days_to_hold" variable in the mm_cfg.py >file so all the lists have the variable set by default? The default value for new lists is DEFAULT_MAX_DAYS_TO_HOLD All such settings are documented in the Defaults.py file. Changing this and similar settings in mm_cfg.py does not affect existing lists. For that see the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 00:14:50 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 15:14:50 -0800 Subject: [Mailman-Users] Transferring Lists In-Reply-To: <0CD7A72044B75D478D36624D96C5D4412FBCB4@kmbx1.utk.tennessee.edu> Message-ID: McNutt Jr, William R wrote: > >I have a tape backup of mailman, lists and all, and I would like to restore it to the new hardware. > >I have successfully installed mailman on the new server. Can anyone refer me to a document that will guide me through re-constructing my list from those old files? Start with the post at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 03:02:49 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 18:02:49 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: <4D3B8C49.9070303@msapiro.net> On 1/21/2011 1:15 AM, Khalil Abbas wrote: > well, attached are parts of the error and qrunner logs.. I also forgot > to mention that I also delete the following files: > > rm /var/lib/mailman/data/*.pck -f This was covered in my reply at > rm /var/lock/mailman/*.* -f Doing this also removes the master lock whose purpose is to prevent you from starting multiple sets of qrunners. This is bad. > the first one also eats up my little space on the hard drive, and the > other locks the lists n they can?t send.. Also, if lists are being left locked by dead processes, this indicates there are other problems. Do you suffer frequent power outages? > what I need to know, why the subscribers are being removed? is it > because of misconfiguration of mailman? or because of outside MTA?s like > yahoo and hotmail rejecting mail from my servers because I need to > control the flow of messages going out from my servers? You also need to know the underlying causes of all the anomalous things that are occurring in your installation. There are serious problems. Your logs may help. Also see FAQs for info on completely stopping Mailman and starting only after completely stopped and for lock information. If you set bounce_notify_owner_on_disable to Yes on your lists, the list owner will be sent a notice whenever a member's delivery is disabled by bounce. This notice will contain the triggering bounce message. That should help you diagnose the cause. > another thing worth to mention, the servers are not blocked by hotmail > because I sent single test messages from all my servers to some of my > subscribers that were removed from my lists and they received them with > no problems.. Possibly your MTA is treating the "temporary failure" throttling status used by some large ISPs to rate limit your mail as a hard failure and returning a failure DSN to Mailman. The only thing in your error log was one unparseable message which has nothing to do with any of this. >From your qrunner log, I see a SIGHUP from log rotation at Jan 16 04:02:54 2011. Then Mailman is stopped at Jan 16 18:17:53 2011, and started at Jan 16 18:19:41 2011. Then I see Jan 17 00:08:48 2011 (2666) Master qrunner detected subprocess exit (pid: 2712, sig: 6, sts: None, class: BounceRunner, slice: 1/1) [restarting] which says BounceRunner died with Signal 6 (SIGABRT). If it wasn't manually killed, there should be a corresponding error log entry, but the only entry in the error log you provided is from Dec 26 which indicates you weren't looking at the current error log. Then we see a sequence Jan 17 17:11:34 2011 Mailman stopped Jan 17 17:13:29 2011 Mailman started Jan 17 20:29:32 2011 Mailman stopped Jan 17 20:31:34 2011 Mailman started Why all the stopping and starting? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 03:12:22 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 18:12:22 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: <4D3B8C49.9070303@msapiro.net> References: <4D3B8C49.9070303@msapiro.net> Message-ID: <4D3B8E86.3030300@msapiro.net> On 1/22/2011 6:02 PM, Mark Sapiro wrote: > > Jan 17 00:08:48 2011 (2666) Master qrunner detected subprocess exit > (pid: 2712, sig: 6, sts: None, class: BounceRunner, slice: 1/1) [restarting] > > which says BounceRunner died with Signal 6 (SIGABRT). Actually, I think this is wrong. I think it died with Error 6 006 ENXIO No such device or address and not SIGABRT. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khillo100 at hotmail.com Sun Jan 23 03:24:03 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Sun, 23 Jan 2011 04:24:03 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: <4D3B8C49.9070303@msapiro.net> References: <4D3B8C49.9070303@msapiro.net> Message-ID: well I did send an old error file cause the current one is huge.. I think mailman keeps stopping because I reboot the servers everyday to free up the memory.. I have a TV station as a customer having 6 lists with a total of 300,000 subscribers, 50,000 each on the following server: Centos CPU Intel P4 3000 2 GBs RAM 120 Gbs hard drive and they post daily to their lists.. I also have another local Newspaper as a customer having about 100,000 subscribers on 3 lists with a virtual private server with the following specs: Centos 256 MBs Ram 10 GBs Hard drive which I have a hard time cleaning up because of the little space that keeps filling up.. is that the problem? do I need to use bigger hardware ? another thing, the servers doesn?t send directly, the messages are being sent to my hosting servers provider's relay server.. Thanks for everything.. -----Original Message----- From: Mark Sapiro Sent: Sunday, January 23, 2011 4:02 AM To: Khalil Abbas Cc: mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. On 1/21/2011 1:15 AM, Khalil Abbas wrote: > well, attached are parts of the error and qrunner logs.. I also forgot > to mention that I also delete the following files: > > rm /var/lib/mailman/data/*.pck -f This was covered in my reply at > rm /var/lock/mailman/*.* -f Doing this also removes the master lock whose purpose is to prevent you from starting multiple sets of qrunners. This is bad. > the first one also eats up my little space on the hard drive, and the > other locks the lists n they can?t send.. Also, if lists are being left locked by dead processes, this indicates there are other problems. Do you suffer frequent power outages? > what I need to know, why the subscribers are being removed? is it > because of misconfiguration of mailman? or because of outside MTA?s like > yahoo and hotmail rejecting mail from my servers because I need to > control the flow of messages going out from my servers? You also need to know the underlying causes of all the anomalous things that are occurring in your installation. There are serious problems. Your logs may help. Also see FAQs for info on completely stopping Mailman and starting only after completely stopped and for lock information. If you set bounce_notify_owner_on_disable to Yes on your lists, the list owner will be sent a notice whenever a member's delivery is disabled by bounce. This notice will contain the triggering bounce message. That should help you diagnose the cause. > another thing worth to mention, the servers are not blocked by hotmail > because I sent single test messages from all my servers to some of my > subscribers that were removed from my lists and they received them with > no problems.. Possibly your MTA is treating the "temporary failure" throttling status used by some large ISPs to rate limit your mail as a hard failure and returning a failure DSN to Mailman. The only thing in your error log was one unparseable message which has nothing to do with any of this. >From your qrunner log, I see a SIGHUP from log rotation at Jan 16 04:02:54 2011. Then Mailman is stopped at Jan 16 18:17:53 2011, and started at Jan 16 18:19:41 2011. Then I see Jan 17 00:08:48 2011 (2666) Master qrunner detected subprocess exit (pid: 2712, sig: 6, sts: None, class: BounceRunner, slice: 1/1) [restarting] which says BounceRunner died with Signal 6 (SIGABRT). If it wasn't manually killed, there should be a corresponding error log entry, but the only entry in the error log you provided is from Dec 26 which indicates you weren't looking at the current error log. Then we see a sequence Jan 17 17:11:34 2011 Mailman stopped Jan 17 17:13:29 2011 Mailman started Jan 17 20:29:32 2011 Mailman stopped Jan 17 20:31:34 2011 Mailman started Why all the stopping and starting? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 04:45:11 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 22 Jan 2011 19:45:11 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: Khalil Abbas wrote: > >well I did send an old error file cause the current one is huge.. Because of some underlying issue that can't be diagnosed without seeing what's there. For example, what are the error log entries with time stamps around the Jan 17 00:08:48 2011 (2666) Master qrunner detected subprocess exit (pid: 2712, sig: 6, sts: None, class: BounceRunner, slice: 1/1) = [restarting] (i.e. between 00:08:45 and 00:08:48) that might tell what the issue with BounceRunner was. >I think mailman keeps stopping because I reboot the servers everyday to >free up the memory.. That's probably at least part of why you wind up with orphaned /var/lib/mailman/data/bounce-events-*.pck and stale locks. >I have a TV station as a customer having 6 lists >with a total of 300,000 subscribers, 50,000 each on the following >server: > >Centos >CPU Intel P4 3000 >2 GBs RAM >120 Gbs hard drive > >and they post daily to their lists.. > >I also have another local Newspaper as a customer having about 100,000 = >subscribers on 3 lists with a virtual private server with the following = >specs: >Centos >256 MBs Ram >10 GBs Hard drive=20 > >which I have a hard time cleaning up because of the little space that = >keeps filling up.. > >is that the problem? do I need to use bigger hardware ? Maybe. I can't begin to tell you what the underlying issues are without seeing the logs. > >another thing, the servers doesn't send directly, the messages >are being sent to my hosting servers provider's relay server.. So there may be issues with this. There might be indications in Mailman's smtp-failure log, and the disable notices to the owner from Mailman should help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From floeff at gmail.com Sun Jan 23 12:59:13 2011 From: floeff at gmail.com (Florian Effenberger) Date: Sun, 23 Jan 2011 12:59:13 +0100 Subject: [Mailman-Users] owner alias bounces In-Reply-To: References: Message-ID: Hi Mark, 2011/1/22 Mark Sapiro : >>However, I have already wondered where to set the web URL. Right now, >>lists.domain2 still have lists.domain1 e.g. in the List-Archive >>header. > > You want an additional add_virtualhost like > > add_virtualhost('lists.domain2.tld', 'lists.domain2.tld') > > This is so that you can go to http://lists.domain2.tld/mailman/create > (or whatever this translates to in your installation) and create a > list and it will be created with the proper > http://lists.domain2.tld/mailman/ web_page_url and lists.domain2.tld > host_name. Ok, I added this and restarted mailman. > Also you can use "bin/newlist -u lists.domain2.tld" to create a list > properly in this domain, and you can use > > ?bin/withlist -l -r fix_url -u lists.domain2.tld existing-listname > > to fix the web_page_url and host_name for an existing domain2 list > (after doing that, you may need to run bin/genaliases to update > virtual-mailman). That doesn't seem to work for me, it throws out "option -u not recognized". :-( If I manually invoke fix_url.py, the -u option is indeed offered. What'sw rong? > This will make appropriate links with host lists.domain2.tld in the > List-* headers in posts, on all dynamic web pages and all new or > modified archive pages for the list. However, existing static archive > pages will still have "listinfo" links with the old domain. These > either have to be ignored, edited manually or updated by rebuilding > the list's entire archive with "bin/arch --wipe listname". Florian From mark at msapiro.net Sun Jan 23 17:54:13 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 08:54:13 -0800 Subject: [Mailman-Users] owner alias bounces In-Reply-To: References: Message-ID: <4D3C5D35.20406@msapiro.net> On 1/23/2011 3:59 AM, Florian Effenberger wrote: > > 2011/1/22 Mark Sapiro : > >> Also you can use "bin/newlist -u lists.domain2.tld" to create a list >> properly in this domain, and you can use >> >> bin/withlist -l -r fix_url -u lists.domain2.tld existing-listname >> >> to fix the web_page_url and host_name for an existing domain2 list >> (after doing that, you may need to run bin/genaliases to update >> virtual-mailman). > > That doesn't seem to work for me, it throws out "option -u not > recognized". :-( If I manually invoke fix_url.py, the -u option is > indeed offered. What'sw rong? My mistake. That should be bin/withlist -l -r fix_url existing-listname -u lists.domain2.tld The -u option needs to come after the list name. Otherwise it is interpreted as a withlist option rather than a fix_url option. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 18:08:36 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 09:08:36 -0800 Subject: [Mailman-Users] User unknown in virtual mailbox table In-Reply-To: Message-ID: Umarzuki Mochlis wrote: >i finally got it working with dovecot lda by adding >hash:/etc/mailman/virtual-mailman at the end of virtual_alias_maps like so > ># postconf virtual_alias_maps >virtual_alias_maps = proxy:ldap:/etc/postfix/ldap_virtual_alias_maps.cf, >proxy:ldap:/etc/postfix/ldap_virtual_group_maps.cf, proxy:ldap:/etc/postfix/ >ldap_sender_login_maps.cf, proxy:ldap:/etc/postfix/ldap_catch_all_maps.cf, >hash:/etc/mailman/virtual-mailman > >generate virtual-mailman.db > ># cd /etc/mailman ># postmap virtual-mailman > >but how do i automate the generation of virtual-mailman.db incase a new >mailman list were to be created? If you really need the list entries in both virtual_alias_maps and transport_maps, you could simply add /usr/sbin/postmap /etc/mailman/virtual-mailman to the end of your virtual_to_transport file. However, it seems to me unlikely that you actually need both since they both should accomplish the same thing in different ways. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From umarzuki at gmail.com Sun Jan 23 15:47:47 2011 From: umarzuki at gmail.com (Umarzuki Mochlis) Date: Sun, 23 Jan 2011 22:47:47 +0800 Subject: [Mailman-Users] User unknown in virtual mailbox table In-Reply-To: References: Message-ID: 2011/1/17 Mark Sapiro > > > After changing DEFAULT_EMAIL_HOST, you need to run > > bin/withlist -l -a -r fix_url > > (see ) and then > > bin/genaliases again. > > i finally got it working with dovecot lda by adding hash:/etc/mailman/virtual-mailman at the end of virtual_alias_maps like so # postconf virtual_alias_maps virtual_alias_maps = proxy:ldap:/etc/postfix/ldap_virtual_alias_maps.cf, proxy:ldap:/etc/postfix/ldap_virtual_group_maps.cf, proxy:ldap:/etc/postfix/ ldap_sender_login_maps.cf, proxy:ldap:/etc/postfix/ldap_catch_all_maps.cf, hash:/etc/mailman/virtual-mailman generate virtual-mailman.db # cd /etc/mailman # postmap virtual-mailman but how do i automate the generation of virtual-mailman.db incase a new mailman list were to be created? From mark at msapiro.net Sun Jan 23 19:21:25 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 10:21:25 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: <4D3C71A5.1080102@msapiro.net> On 1/23/2011 7:46 AM, Khalil Abbas wrote: > attached are the Jan 16, and Jan 17th logs: error, smtp, qrunner, > locks.. I replaced my domain name with the word (DOMAIN) cause I believe > this is shown to public .. > > there are several smtp-failure files (failure.1, .2, .3...) but they are > all empty (0 bytes size).. The locks log shows one broken expired lock, possibly due to your frequent reboots. The error log shows only unparseable messages but there are over 3000 of them in about 26 hours. Correlation with the qrunner log shows these are all processed by BounceRunner. Thus they are unparseable messages sent to the LIST-bounces addresses. Normally, unparseable messages are spam, but possible they are real bounces from some broken MTA. The next time you have an accumulation of /var/spool/mailman/bounce/*.pck files, examine some of them with Mailman's bin/dumpdb or bin/show_qfiles tool. If they look like legitimate bounce messages, they may give you some information about your bounces, but note that the particular messages that are unparseable do not get scored for any user. If they look like spam, then your problem may just be massive amounts of spam sent to your LIST-bounces addresses. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From floeff at gmail.com Sun Jan 23 20:07:44 2011 From: floeff at gmail.com (Florian Effenberger) Date: Sun, 23 Jan 2011 20:07:44 +0100 Subject: [Mailman-Users] owner alias bounces In-Reply-To: <4D3C5D35.20406@msapiro.net> References: <4D3C5D35.20406@msapiro.net> Message-ID: Hi Mark, > My mistake. That should be > > ?bin/withlist -l -r fix_url existing-listname -u lists.domain2.tld > > The -u option needs to come after the list name. Otherwise it is > interpreted as a withlist option rather than a fix_url option. thanks a lot, that did the trick! ;) Florian From khillo100 at hotmail.com Sun Jan 23 19:36:45 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Sun, 23 Jan 2011 20:36:45 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: <4D3C71A5.1080102@msapiro.net> References: <4D3C71A5.1080102@msapiro.net> Message-ID: well this is much comforting, meaning that there is nothing to worry about the configuration.. I turned on the "Should Mailman notify you, the list owner, when bounces cause a member's subscription to be disabled?" to yes to see what happens.. but still this does not answer the main question, what causes the existing real members to be unsubscribed? is it because hotmail and yahoo are rejecting the mail flow that needs to be controlled? this leads to another question, should this (control mail flow) be considered in the next version of mailman? this will also answer the million dollars question: CAN mailman handle huge lists like those of TV stations like mine (300,000 subscribers)? final question: is there any advice about my current situation (hardware, configuration...etc.)? Thanks mate, you're the best :) -----Original Message----- From: Mark Sapiro Sent: Sunday, January 23, 2011 8:21 PM To: Khalil Abbas Cc: mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. On 1/23/2011 7:46 AM, Khalil Abbas wrote: > attached are the Jan 16, and Jan 17th logs: error, smtp, qrunner, > locks.. I replaced my domain name with the word (DOMAIN) cause I believe > this is shown to public .. > > there are several smtp-failure files (failure.1, .2, .3...) but they are > all empty (0 bytes size).. The locks log shows one broken expired lock, possibly due to your frequent reboots. The error log shows only unparseable messages but there are over 3000 of them in about 26 hours. Correlation with the qrunner log shows these are all processed by BounceRunner. Thus they are unparseable messages sent to the LIST-bounces addresses. Normally, unparseable messages are spam, but possible they are real bounces from some broken MTA. The next time you have an accumulation of /var/spool/mailman/bounce/*.pck files, examine some of them with Mailman's bin/dumpdb or bin/show_qfiles tool. If they look like legitimate bounce messages, they may give you some information about your bounces, but note that the particular messages that are unparseable do not get scored for any user. If they look like spam, then your problem may just be massive amounts of spam sent to your LIST-bounces addresses. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 21:33:54 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 12:33:54 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: Khalil Abbas wrote: >well this is much comforting, meaning that there is nothing to worry about >the configuration.. I turned on the "Should Mailman notify you, the list >owner, when bounces cause a member's subscription to be disabled?" to yes to >see what happens.. > >but still this does not answer the main question, what causes the existing >real members to be unsubscribed? is it because hotmail and yahoo are >rejecting the mail flow that needs to be controlled? When you see some actual disabling bounce notifications, you will hopefully be able to answer that for yourself. Until then, I don't know what causes it. >this leads to another question, should this (control mail flow) be >considered in the next version of mailman? this will also answer the million >dollars question: CAN mailman handle huge lists like those of TV stations >like mine (300,000 subscribers)? Mailman handles large lists and large volumes of mail just fine with appropriately sized hardware and properly configured MTAs. See the FAQ at and note the following quoted from the end of that article. If you're going to be running lists with more than a few thousand members, then you need to have a thorough understanding of how your MTA and Mailman work, and a deep and intimate familiarity with Internet e-mail in general. And of course, you will have to carefully consider how best to tune your MTA and Mailman to work best together. If you're missing any of these prerequisites, you're in for a difficult time. >final question: is there any advice about my current situation (hardware, >configuration...etc.)? Increase your disk storage. These days, when a 500GB drive costs well under $100 US, a production server with 10GB of storage is way too cramped, and your lack of disk space is causing you do do all sorts of questionable things that shouldn't be necessary. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jan 23 22:20:19 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 13:20:19 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: <4D3C9B93.8000505@msapiro.net> On 1/23/2011 12:33 PM, Mark Sapiro wrote: > Khalil Abbas wrote: > >> well this is much comforting, meaning that there is nothing to worry about >> the configuration.. I turned on the "Should Mailman notify you, the list >> owner, when bounces cause a member's subscription to be disabled?" to yes to >> see what happens.. >> >> but still this does not answer the main question, what causes the existing >> real members to be unsubscribed? is it because hotmail and yahoo are >> rejecting the mail flow that needs to be controlled? > > > When you see some actual disabling bounce notifications, you will > hopefully be able to answer that for yourself. Until then, I don't > know what causes it. I also looked more closely at the smtp log you sent earlier. There are a huge number of mailman generated notices that originate from BounceRunner. All lists appear affected. I think these are unrecognized bounce notifications. I have suggested before that there may be a large amount of spam being sent to the LIST-bounces addresses, but there may also be a mail loop of some kind. I suggest that you make sure that each list's (including the 'mailman' list) owner attribute contains only deliverable addresses and that none of the LIST-* addresses are among them. Similarly, if there are any moderator addresses, they must be deliverable and must not include any LIST-* addresses and shouldn't duplicate any owner addresses for the same list. Also try sending an email to the LIST-owner addresses to verify such mail is received. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khillo100 at hotmail.com Sun Jan 23 23:11:55 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Mon, 24 Jan 2011 00:11:55 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: <4D3C9B93.8000505@msapiro.net> References: <4D3C9B93.8000505@msapiro.net> Message-ID: I also forgot to mention something.. I'm managing 57 lists on 18 servers.. some are small lists and some are huge but the thing in common is that they all send a single message to their lists per day.. but I have put my own email address (khillo100 at hotmail dot com) in all of the 57 lists.. and everyday I receive between 30 and 40 emails from the lists but never 57! another thing in common is that all 18 servers never send directly, they go thru the same relay server .. I tried to something, I removed my address from all lists and re-subscribed and I received 57 welcome messages.. but when sending to the lists, only 30 to 40 are received.. any thoughts? -----Original Message----- From: Mark Sapiro Sent: Sunday, January 23, 2011 11:20 PM To: Khalil Abbas Cc: mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. On 1/23/2011 12:33 PM, Mark Sapiro wrote: > Khalil Abbas wrote: > >> well this is much comforting, meaning that there is nothing to worry >> about >> the configuration.. I turned on the "Should Mailman notify you, the list >> owner, when bounces cause a member's subscription to be disabled?" to yes >> to >> see what happens.. >> >> but still this does not answer the main question, what causes the >> existing >> real members to be unsubscribed? is it because hotmail and yahoo are >> rejecting the mail flow that needs to be controlled? > > > When you see some actual disabling bounce notifications, you will > hopefully be able to answer that for yourself. Until then, I don't > know what causes it. I also looked more closely at the smtp log you sent earlier. There are a huge number of mailman generated notices that originate from BounceRunner. All lists appear affected. I think these are unrecognized bounce notifications. I have suggested before that there may be a large amount of spam being sent to the LIST-bounces addresses, but there may also be a mail loop of some kind. I suggest that you make sure that each list's (including the 'mailman' list) owner attribute contains only deliverable addresses and that none of the LIST-* addresses are among them. Similarly, if there are any moderator addresses, they must be deliverable and must not include any LIST-* addresses and shouldn't duplicate any owner addresses for the same list. Also try sending an email to the LIST-owner addresses to verify such mail is received. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From doug.gaff at gmail.com Sun Jan 23 23:51:36 2011 From: doug.gaff at gmail.com (Doug Gaff) Date: Sun, 23 Jan 2011 17:51:36 -0500 Subject: [Mailman-Users] private lists with real name signatures In-Reply-To: <97dd01cb237c$6c387fb0$44a97f10$@com> References: <04a101cafc12$5bc13500$13439f00$@com> <877hmqlk2k.fsf@uwakimon.sk.tsukuba.ac.jp> <002701cafcef$eaa9f2b0$bffdd810$@com> <874ohulgp5.fsf@uwakimon.sk.tsukuba.ac.jp> <97dd01cb237c$6c387fb0$44a97f10$@com> Message-ID: (Sorry to resurrect an old thread, but I recently switched to a VPS, and now finally have access to the mailman install.) As mentioned in the old thread, I'd like add %(member_name) and %(member_address) as variables that can be used in the msg_header and msg_footer fields if desired by the list administrator. The idea is that messages sent to an anonymous mailing list could have msg_header set to this: %(member_name) writes: And in the subscription list, member_name would be the "handle" used by each person. This way, the email addresses stay anonymous, but the messages are still signed. Consider it "semi-anonymous". :) I'm not totally getting the custom handler thing, and I need this only for one of the lists I host. Something the list admin could setup if desired. It seems like a handler would fire for everyone. A better solution, if a hack, would be to modify the mailman source code, but I could use some pointers on where to get started. Thanks, Doug On May 26, 2010, at 1:39 PM, Doug Gaff wrote: LOL. I'll work on the handler. I'm not sure whether I can do this is a shared hosted environment, though. I'm looking into it. -----Original Message----- From: Stephen J. Turnbull [mailto:stephen at xemacs.org] Sent: Wednesday, May 26, 2010 1:24 PM To: Doug Gaff Cc: 'Mark Sapiro'; Mailman-Users at python.org Subject: Re: [Mailman-Users] [Bulk] Re: private lists with real name signatures Doug Gaff writes: > Why isn't %(poster_name) available as a variable to be used in the > msg_footer options on the admin panel? Seems like that would be easier. It's not available because it's not available. Yours is an unusual use case; "normally" the poster's name is available in the From field, or not at all. No malice in this, it just never occurred to anybody to make it available for message headers and footers. This Handler could be added to a future version of Mailman, but 2.x is not planned for further development, and 3.0 is still some months away. No reason for you to wait! From mark at msapiro.net Mon Jan 24 02:14:49 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 17:14:49 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: halil Abbas wrote: >I also forgot to mention something.. I'm managing 57 lists on 18 servers.. >some are small lists and some are huge but the thing in common is that they >all send a single message to their lists per day.. but I have put my own >email address (khillo100 at hotmail dot com) in all of the 57 lists.. and >everyday I receive between 30 and 40 emails from the lists but never 57! > >another thing in common is that all 18 servers never send directly, they go >thru the same relay server .. I agree that mails are getting bounced/dropped, but I can't begin to guess why without seeing actual bounce messages and/or logs from the relay server and/or logs from your local MTA if you use a local MTA between Mailman and the relay server. You may need to talk to the operators of the relay. I know you did and they told you to rate limit your sending, but do they know that is the problem, or is that a non-response? If in fact you do have a local MTA which Mailman delivers to and which then relays to the relay server, you can investigate rate limiting there as discussed in the FAQ at to which you have been previously referred. Let us see some actual bounce messages. We know there are some because bounce processing is removing subscribers, so what do they look like? Also, have you followed up on my following suggestion to verify that all the owner addresses are deliverable. I.e., what happened to the nearly 3000 notices from BounceRunner that were indicated in the smtp log you sent me. >I also looked more closely at the smtp log you sent earlier. There are a >huge number of mailman generated notices that originate from >BounceRunner. All lists appear affected. I think these are unrecognized >bounce notifications. I have suggested before that there may be a large >amount of spam being sent to the LIST-bounces addresses, but there may >also be a mail loop of some kind. I suggest that you make sure that each >list's (including the 'mailman' list) owner attribute contains only >deliverable addresses and that none of the LIST-* addresses are among >them. Similarly, if there are any moderator addresses, they must be >deliverable and must not include any LIST-* addresses and shouldn't >duplicate any owner addresses for the same list. > >Also try sending an email to the LIST-owner addresses to verify such >mail is received. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Jan 24 02:41:08 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 23 Jan 2011 17:41:08 -0800 Subject: [Mailman-Users] private lists with real name signatures In-Reply-To: Message-ID: Doug Gaff wrote: >(Sorry to resurrect an old thread, but I recently switched to a VPS, and now finally have access to the mailman install.) > >As mentioned in the old thread, I'd like add %(member_name) and %(member_address) as variables that can be used in the msg_header and msg_footer fields if desired by the list administrator. The idea is that messages sent to an anonymous mailing list could have msg_header set to this: > >%(member_name) writes: > >And in the subscription list, member_name would be the "handle" used by each person. This way, the email addresses stay anonymous, but the messages are still signed. Consider it "semi-anonymous". :) Presumably these variables would be the poster's name and address, not the recipient's since the latter would require personalized delivery and are already available as # user_address - The address of the user, coerced to lower case. # user_delivered_to - The case-preserved address that the user is subscribed with. # user_name - The user's full name. when delivery is personalized. >I'm not totally getting the custom handler thing, and I need this only for one of the lists I host. Something the list admin could setup if desired. It seems like a handler would fire for everyone. A better solution, if a hack, would be to modify the mailman source code, but I could use some pointers on where to get started. The handler as described at will work for the poster's name. You would need to augment it if you wanted to add the poster's address, but if you were adding the poster's address, it seems it would be easier to just not make the list anonymous in the first place. I don't know why you think modifying the existing code would be better? First, it is easier to make a custom handler operate on only one or a few lists than it is to make code modification do so. See the FAQ at . Second, all the handler would do is make additional substitution variables available for msg_header and msg_footer. It would still be up to the list admin to make use of them. If you need more help with a custom handler than is in the FAQ at , please try to ask a more specific question and we'll try to help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khillo100 at hotmail.com Mon Jan 24 08:35:52 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Mon, 24 Jan 2011 09:35:52 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: ah yes, these to list owner notices I guess are unsubscribe notices.. for I turned on the "Should Mailman notify you, the list owner, when bounces cause a member to be unsubscribed?" to yes.. I tried to send test messages to these addresses, most of them are real subscribers that got kicked off and received my test messages, and some returned back for different reasons like mailbox full and mailbox has been closed and stuff like that .. checking some random files in the /var/spool/mailman/bounces/*.pck I found : ****************** This is the qmail-send program at ______________.\nI\'m afraid I wasn\'t able to deliver your message to the following addresses.\nThis is a permanent error; I\'ve given up. Sorry it didn\'t work out.\n\n<___________ (hotmail.fr address) >:\nConnected to 65.54.188.110 but sender was rejected.\nRemote host said: 421 RP-001 Unfortunately, some messages from ____________ weren\'t sent. Please try again. We have limits for how many messages can be sent per hour and per day. You can also refer to http://mail.live.com/mail/troubleshooting.aspx#errors.\nI\'m not going to try again; this message has been in the queue too long. ****************** checking the error code 421 RP-001 on hotmail I found: *************** The mail server IP connecting to Windows Live Hotmail server has exceeded the rate limit allowed. Reason for rate limitation is related to IP/domain reputation. If you are not an email/network admin please contact your Email/Internet Service Provider for help. *************** so it is a rate limit no? what can be done about this? it says something about ip/domain reputation, is it my domain's reputation or my service provider's relay server's reputation? Thanks.. -----Original Message----- From: Mark Sapiro Sent: Monday, January 24, 2011 3:14 AM To: Khalil Abbas ; mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. halil Abbas wrote: >I also forgot to mention something.. I'm managing 57 lists on 18 servers.. >some are small lists and some are huge but the thing in common is that they >all send a single message to their lists per day.. but I have put my own >email address (khillo100 at hotmail dot com) in all of the 57 lists.. and >everyday I receive between 30 and 40 emails from the lists but never 57! > >another thing in common is that all 18 servers never send directly, they go >thru the same relay server .. I agree that mails are getting bounced/dropped, but I can't begin to guess why without seeing actual bounce messages and/or logs from the relay server and/or logs from your local MTA if you use a local MTA between Mailman and the relay server. You may need to talk to the operators of the relay. I know you did and they told you to rate limit your sending, but do they know that is the problem, or is that a non-response? If in fact you do have a local MTA which Mailman delivers to and which then relays to the relay server, you can investigate rate limiting there as discussed in the FAQ at to which you have been previously referred. Let us see some actual bounce messages. We know there are some because bounce processing is removing subscribers, so what do they look like? Also, have you followed up on my following suggestion to verify that all the owner addresses are deliverable. I.e., what happened to the nearly 3000 notices from BounceRunner that were indicated in the smtp log you sent me. >I also looked more closely at the smtp log you sent earlier. There are a >huge number of mailman generated notices that originate from >BounceRunner. All lists appear affected. I think these are unrecognized >bounce notifications. I have suggested before that there may be a large >amount of spam being sent to the LIST-bounces addresses, but there may >also be a mail loop of some kind. I suggest that you make sure that each >list's (including the 'mailman' list) owner attribute contains only >deliverable addresses and that none of the LIST-* addresses are among >them. Similarly, if there are any moderator addresses, they must be >deliverable and must not include any LIST-* addresses and shouldn't >duplicate any owner addresses for the same list. > >Also try sending an email to the LIST-owner addresses to verify such >mail is received. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From s.watkins at nhm.ac.uk Mon Jan 24 11:29:32 2011 From: s.watkins at nhm.ac.uk (Steff Watkins) Date: Mon, 24 Jan 2011 10:29:32 -0000 Subject: [Mailman-Users] Solaris 10 and Python In-Reply-To: <0CD7A72044B75D478D36624D96C5D4412FB9EC@kmbx1.utk.tennessee.edu> References: <0CD7A72044B75D478D36624D96C5D4412FB9EC@kmbx1.utk.tennessee.edu> Message-ID: <8A17F10FEBA5C841956578C5AD9027D30153937E@HOMER.nhm.ac.uk> > -----Original Message----- > From: mailman-users-bounces+s.watkins=nhm.ac.uk at python.org > [mailto:mailman-users-bounces+s.watkins=nhm.ac.uk at python.org] > On Behalf Of McNutt Jr, William R > Sent: Friday, January 21, 2011 8:53 PM > To: mailman-users at python.org > Subject: [Mailman-Users] Solaris 10 and Python > > Has anyone successfully made this work on a Sun Solaris 10? > I've been at this for three days and no matter what I do, I > only manage to change error messages. At this point I've > made it through the ./configure step, but it's breaking on > make install. Any chance you can post what the failure message your make session returns? [this is me busily digging a very deep hole from which I may never return!] At this point, with no further info, I'm guessing it's most likely that you've probably not got your binary search path or your link library path setup to pick up all the things that make needs. A side question: is this list the best place to discuss mailman build issues? If not, then someone please squeal and the line of banter can be taken off-list. Steff ----- From mcnutt at utk.edu Mon Jan 24 16:43:57 2011 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Mon, 24 Jan 2011 15:43:57 +0000 Subject: [Mailman-Users] List Membership Change Message-ID: <0CD7A72044B75D478D36624D96C5D4412FC7AF@kmbx1.utk.tennessee.edu> I'm still cleaning up after my hardware failure, and I've got a list admin who is complaining about his membership list. Now - what I did was just copy the /lists/* from the old server to the new one and run ./withlist -l -r fix_url LIST_NAME -u new-domain.example.org And bin/arch mylist archives/private/mylist.mbox/mylist.mbox for each list. The complaint follows: "We went from 340 members to 465 in one list and from 102 to 59 in the other." Is there anything else I can do? From mark at msapiro.net Mon Jan 24 18:43:30 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 24 Jan 2011 09:43:30 -0800 Subject: [Mailman-Users] List Membership Change In-Reply-To: <0CD7A72044B75D478D36624D96C5D4412FC7AF@kmbx1.utk.tennessee.edu> Message-ID: McNutt Jr, William R wrote: > >Now - what I did was just copy the /lists/* from the old server to the new one and run >./withlist -l -r fix_url LIST_NAME -u new-domain.example.org >And >bin/arch mylist archives/private/mylist.mbox/mylist.mbox Presumably, you also restored the archives/private/ directory. The bin/arch you should have run is just bin/arch --wipe mylist The mailbox archives/private/mylist.mbox/mylist.mbox is the default so you don't need it in the command. You do need the --wipe, otherwise you are adding the posts from the mbox to those that may already exist in the pipermail archive. >for each list. > >The complaint follows: >"We went from 340 members to 465 in one list and from 102 to 59 in the other." > >Is there anything else I can do? What files exactly did you restore in the lists/LISTNAME/ directory. If there were any config.db* files, these are old residue from a 2.0.x to 2.1.x migration and should be removed. The potential issue is if permissions or possibly some other error prevents the config.pck and fallback config.pck.last from being successfully loaded, Mailman will fall back to the ancient config.db or config.db.last. If this is what happened, you need to recopy the config.pck from backup and rempove config.pck.last and config.db*. If that doesn't help or if there were no config.db* files, then I don't know what the problem could be. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Jan 24 19:40:47 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 24 Jan 2011 10:40:47 -0800 Subject: [Mailman-Users] Solaris 10 and Python In-Reply-To: <8A17F10FEBA5C841956578C5AD9027D30153937E@HOMER.nhm.ac.uk> Message-ID: Steff Watkins wrote: > >A side question: is this list the best place to discuss mailman build >issues? If not, then someone please squeal and the line of banter can be >taken off-list. It's a grey area for Mailman 2.1.x, but it's OK here. The alternative is mailman-developers at python.org, but most of the prior solaris discussion, and there's been a lot, has been here. For Mailman 3, mailman-developers is the place at least until there's a production release. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Jan 24 20:00:01 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 24 Jan 2011 11:00:01 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: Khalil Abbas wrote: > >checking some random files in the /var/spool/mailman/bounces/*.pck I found : > >****************** >This is the qmail-send program at ______________.\nI\'m afraid I wasn\'t >able to deliver your message to the following addresses.\nThis is a >permanent error; I\'ve given up. Sorry it didn\'t work out.\n\n<___________ >(hotmail.fr address) >:\nConnected to 65.54.188.110 but sender was >rejected.\nRemote host said: 421 RP-001 Unfortunately, some messages from >____________ weren\'t sent. Please try again. We have limits for how many >messages can be sent per hour and per day. You can also refer to >http://mail.live.com/mail/troubleshooting.aspx#errors.\nI\'m not going to >try again; this message has been in the queue too long. >****************** > >checking the error code 421 RP-001 on hotmail I found: > >*************** >The mail server IP connecting to Windows Live Hotmail server has exceeded >the rate limit allowed. Reason for rate limitation is related to IP/domain >reputation. If you are not an email/network admin please contact your >Email/Internet Service Provider for help. >*************** > >so it is a rate limit no? Yes it is. But, hotmail is limiting the rate by returning a 421 status which is retryable, but qmail on the relay host is either giving up too soon, or you will never be able to deliver all your mail no matter what you do. >what can be done about this? it says something about ip/domain reputation, >is it my domain's reputation or my service provider's relay server's >reputation? It's your service provider's relay server. I'm surprised they haven't cut you off. Consider that hotmail is rate limiting that server and rejecting (with 421) mail over the limit. This would affect not only your list mail, but mail to hotmail from any other customer of the service provider being sent at the same time. Now, consider what is happening. The relay server gives up retrying the 421 because the "message has been in the queue too long". Either it's "give up" time is way to short, something only the service provider can adjust, but maybe you can tell from when the rejected message was sent, or it keeps retrying for more than a day. If the latter, the implication would seem that hotmail's rate limit does not allow for all the days messages to be delivered in a day. The only solution to that is to get hotmail to raise the rate limit, and only the service provider can do that. Now, there is one other point. When you resubscribed, you got all your notices, so mail sent to one recipient at a time seems to get through. You can cause Mailman to send more messages with fewer recipients per message by putting say SMTP_MAX_RCPTS = 10 in mm_cfg.py. That may help. Otherwise, I don't think there's much you can do except maybe convince your customers to reduce the frequency of their announcements. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khillo100 at hotmail.com Mon Jan 24 20:46:33 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Mon, 24 Jan 2011 21:46:33 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: I'm discussing this with my service provider right now.. I'll tell u what comes up.. by the way, what's the default value for SMTP_MAX_RCPTS ?? Thanks.. -----Original Message----- From: Mark Sapiro Sent: Monday, January 24, 2011 9:00 PM To: Khalil Abbas ; mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. Khalil Abbas wrote: > >checking some random files in the /var/spool/mailman/bounces/*.pck I found >: > >****************** >This is the qmail-send program at ______________.\nI\'m afraid I wasn\'t >able to deliver your message to the following addresses.\nThis is a >permanent error; I\'ve given up. Sorry it didn\'t work out.\n\n<___________ >(hotmail.fr address) >:\nConnected to 65.54.188.110 but sender was >rejected.\nRemote host said: 421 RP-001 Unfortunately, some messages from >____________ weren\'t sent. Please try again. We have limits for how many >messages can be sent per hour and per day. You can also refer to >http://mail.live.com/mail/troubleshooting.aspx#errors.\nI\'m not going to >try again; this message has been in the queue too long. >****************** > >checking the error code 421 RP-001 on hotmail I found: > >*************** >The mail server IP connecting to Windows Live Hotmail server has exceeded >the rate limit allowed. Reason for rate limitation is related to IP/domain >reputation. If you are not an email/network admin please contact your >Email/Internet Service Provider for help. >*************** > >so it is a rate limit no? Yes it is. But, hotmail is limiting the rate by returning a 421 status which is retryable, but qmail on the relay host is either giving up too soon, or you will never be able to deliver all your mail no matter what you do. >what can be done about this? it says something about ip/domain reputation, >is it my domain's reputation or my service provider's relay server's >reputation? It's your service provider's relay server. I'm surprised they haven't cut you off. Consider that hotmail is rate limiting that server and rejecting (with 421) mail over the limit. This would affect not only your list mail, but mail to hotmail from any other customer of the service provider being sent at the same time. Now, consider what is happening. The relay server gives up retrying the 421 because the "message has been in the queue too long". Either it's "give up" time is way to short, something only the service provider can adjust, but maybe you can tell from when the rejected message was sent, or it keeps retrying for more than a day. If the latter, the implication would seem that hotmail's rate limit does not allow for all the days messages to be delivered in a day. The only solution to that is to get hotmail to raise the rate limit, and only the service provider can do that. Now, there is one other point. When you resubscribed, you got all your notices, so mail sent to one recipient at a time seems to get through. You can cause Mailman to send more messages with fewer recipients per message by putting say SMTP_MAX_RCPTS = 10 in mm_cfg.py. That may help. Otherwise, I don't think there's much you can do except maybe convince your customers to reduce the frequency of their announcements. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jan 25 00:18:59 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 24 Jan 2011 15:18:59 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: Khalil Abbas wrote: > >by the way, what's the default value for SMTP_MAX_RCPTS ?? All the settings default values and their documentation is in Defaults.py. # Ceiling on the number of recipients that can be specified in a single SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. Only used with the SMTPDirect DELIVERY_MODULE. SMTP_MAX_RCPTS = 500 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rcarter at pinyon.org Wed Jan 26 02:16:17 2011 From: rcarter at pinyon.org (Russell L. Carter) Date: Tue, 25 Jan 2011 18:16:17 -0700 Subject: [Mailman-Users] postfix-to-mailman.py => mail loops back to myself Message-ID: <4D3F75E1.7070609@pinyon.org> Hi there, I've spent the afternoon attempting to install mailman on debian testing with postfix, following the instructions in /etc/mailman/postfix-to-mailman.py precisely, and I'm getting the classic 'mail for "host" loops back to myself'. From my getting to know the issue sessions with google there appear to be a variety of ways this can show up. Anyway I've checked permissions, am able to create lists and add users with confirmation, etc. But sending from the user to the list bounces with postfix complaining 'loops back to myself'. Q1: I was not previously using postfix virtual domains as described in www.postfix.org/VIRTUAL_README.html, should I be? If so I'll go off and try to figure out how the information in there is related to the instructions in /etc/mailman/postfix-to-mailman.py. However, AFAICT, the two sources appear to have zero intersection even though the concepts are of course are quite similar. If the answer to Q1 is "no", the only change to my existing system was to add a CNAME 'lists.pinyon.org' pointing to 'quine.pinyon.org'. Here is the relevant part of of my long time working main.cf, with the mailman modifications (all checked, many times): ------------------------------------------------------------------ myhostname = quine.pinyon.org mydomain = pinyon.org myorigin = $mydomain mydestination = $myhostname, localhost.$mydomain, $mydomain, mail.$mydomain, www.$mydomain, ftp.$mydomain troupesalamat.com masquerade_domains = pinyon.org relay_domains = lists.pinyon.org $mydestination esturion.net troupesalamat.com relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 ------------------------------------------------------------------ I've tried quite a few permutations of ordering, etc., but no luck. Q2: Any idea what might be the problem? Many thanks! Russell From khillo100 at hotmail.com Wed Jan 26 17:15:26 2011 From: khillo100 at hotmail.com (Khalil Abbas) Date: Wed, 26 Jan 2011 18:15:26 +0200 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: References: Message-ID: well I decreased the SMTP_MAX_RCPTS to only 5 (five) and when checking the mailq every now and then .. some of the 18 servers gave the following: -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 335BB14BB8CA 111316 Wed Jan 26 09:04:29 MAILER-DAEMON (unknown mail transport error) and some of them: -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 7B477146C78 108725 Tue Jan 25 21:14:27 balligho-bounces at ballighoseven.info (system resource problem) I kept rebooting the servers every while to get the mail moving .. and so far I received 27 messages out of 57 lists .. I'll raise it to 10 and try again.. any thoughts ? -----Original Message----- From: Mark Sapiro Sent: Tuesday, January 25, 2011 1:18 AM To: Khalil Abbas ; mailman-users at python.org Subject: Re: [Mailman-Users] control mail distribution .. Khalil Abbas wrote: > >by the way, what's the default value for SMTP_MAX_RCPTS ?? All the settings default values and their documentation is in Defaults.py. # Ceiling on the number of recipients that can be specified in a single SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. Only used with the SMTPDirect DELIVERY_MODULE. SMTP_MAX_RCPTS = 500 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Jan 26 17:19:01 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 26 Jan 2011 08:19:01 -0800 Subject: [Mailman-Users] postfix-to-mailman.py => mail loops back to myself In-Reply-To: <4D3F75E1.7070609@pinyon.org> Message-ID: Russell L. Carter wrote: > >I've spent the afternoon attempting to install mailman on debian >testing with postfix, following the instructions in >/etc/mailman/postfix-to-mailman.py precisely, and I'm getting the >classic 'mail for "host" loops back to myself'. From my getting to >know the issue sessions with google there appear to be a variety of >ways this can show up. Anyway I've checked permissions, am able to >create lists and add users with confirmation, etc. But sending from >the user to the list bounces with postfix complaining 'loops back to >myself'. > >Q1: I was not previously using postfix virtual domains as described in >www.postfix.org/VIRTUAL_README.html, should I be? No. This is irrelevant. You should have a transport mapping that says to use a defined 'mailman' transport for addresses in your lists domain. >If so I'll go off >and try to figure out how the information in there is related to the >instructions in /etc/mailman/postfix-to-mailman.py. However, AFAICT, >the two sources appear to have zero intersection even though the >concepts are of course are quite similar. > >If the answer to Q1 is "no", the only change to my existing system >was to add a CNAME 'lists.pinyon.org' pointing to 'quine.pinyon.org'. >Here is the relevant part of of my long time working main.cf, with the >mailman modifications (all checked, many times): You must not use a CNAME for a mail domain. See the FAQ at . This must be an MX, not a CNAME. >------------------------------------------------------------------ >myhostname = quine.pinyon.org >mydomain = pinyon.org > >myorigin = $mydomain > >mydestination = $myhostname, localhost.$mydomain, $mydomain, > mail.$mydomain, www.$mydomain, ftp.$mydomain troupesalamat.com > >masquerade_domains = pinyon.org > >relay_domains = lists.pinyon.org $mydestination esturion.net troupesalamat.com >relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman >transport_maps = hash:/etc/postfix/transport >mailman_destination_recipient_limit = 1 >------------------------------------------------------------------ > >I've tried quite a few permutations of ordering, etc., but no luck. > >Q2: Any idea what might be the problem? If you have an entry like lists.pinyon.org mailman: in /etc/postfix/transport, and you have a definition like mailman unix - n n - - pipe flags=FR user=mailman:mailman argv=/var/mailman/postfix-to-mailman.py ${nexthop} ${user} in master.cf, and you have an MX rather than a CNAME for lists.pinyon.org, it should work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Jan 26 17:29:38 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 26 Jan 2011 08:29:38 -0800 Subject: [Mailman-Users] control mail distribution .. In-Reply-To: Message-ID: Khalil Abbas wrote: >well I decreased the SMTP_MAX_RCPTS to only 5 (five) and when checking the >mailq every now and then .. some of the 18 servers gave the following: > >-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- >335BB14BB8CA 111316 Wed Jan 26 09:04:29 MAILER-DAEMON > (unknown mail transport >error) This looks like the MTA has some problem delivering a bounce DSN. >and some of them: > >-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- >7B477146C78 108725 Tue Jan 25 21:14:27 >balligho-bounces at ballighoseven.info > (system resource >problem) The MTA has been unable to deliver this message for the indicated reason. It has been successfully delivered from Mailman to the MTA. SMTP_MAX_RCPTS has nothing to do with this. >I kept rebooting the servers every while to get the mail moving The need to do this indicates serious problems with your mail setup in general. I can't help you with this. I don't think I can help you further at all. .. and so >far I received 27 messages out of 57 lists .. > >I'll raise it to 10 and try again.. > >any thoughts ? Just the above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rcarter at pinyon.org Wed Jan 26 17:34:18 2011 From: rcarter at pinyon.org (Russell L. Carter) Date: Wed, 26 Jan 2011 09:34:18 -0700 Subject: [Mailman-Users] postfix-to-mailman.py => mail loops back to myself In-Reply-To: References: Message-ID: <4D404D0A.1060408@pinyon.org> On 01/26/2011 09:19 AM, Mark Sapiro wrote: > Russell L. Carter wrote: >> > > You must not use a CNAME for a mail domain. See the FAQ at > . This must be an MX, not a CNAME. Ah. I was worried about that. Ok. That complicates my setup, but many thanks for the pointer. Russell From knabe at 4j.lane.edu Thu Jan 27 01:14:52 2011 From: knabe at 4j.lane.edu (Troy Knabe) Date: Wed, 26 Jan 2011 16:14:52 -0800 Subject: [Mailman-Users] image filtering Message-ID: <1967D5D2-7BC0-41F0-BDFD-4CB7497D7316@4j.lane.edu> A user just sent a message to a list, and the inline image was removed. Under "Content filtering" I have "Should Mailman filter the content of list traffic according to the settings below?" and No is checked. Where else should I be looking? Thanks -Troy From rcarter at pinyon.org Thu Jan 27 02:35:20 2011 From: rcarter at pinyon.org (Russell L. Carter) Date: Wed, 26 Jan 2011 18:35:20 -0700 Subject: [Mailman-Users] configuration problem In-Reply-To: <4D404D0A.1060408@pinyon.org> References: <4D404D0A.1060408@pinyon.org> Message-ID: <4D40CBD8.7040801@pinyon.org> Installing on debian testing, all packages up to date. Ok, it complicated maintenance a bit too much in my net to dedicate an IP address to lists.domain, so I thought I would try the exact approach as detailed in the install manual with postfix, namely using alias_maps and virtual_alias_domains, etc., leading to a postfix main.cf containing: ----------------------------------------------------------------- # http://www.postfix.org/ADDRESS_REWRITING_README.html#masquerade masquerade_domains = lists.pinyon.org pinyon.org # http://www.postfix.org/virtual.5.html virtual_alias_domains = lists.pinyon.org virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman alias_maps = hash:/etc/aliases hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases ------------------------------------------------------------------ And that worked great! Using the suggested initial 'mailman' list I was able to add subscribers and send/receive, etc. Perfect. I ran into a permissions problem with apache and the private archives, so I thought I would stop at that point, purge the installation, and carefully recreate the configuration from scratch so that I could document the exact steps for mailman installation on my site properly. So I do (leaving the postfix previously working main.cf untouched): $ apt-get remove --purge mailman $ /bin/rm -rf /var/lib/mailman /usr/lib/mailman $ cp [my-saved-working-copy-of-mm_cfg.py] /etc/mailman $ newlist mailman [exact same stuff as before] $ /etc/init.d/mailman start $ /var/lib/mailman/bin/genaliases $ /var/lib/mailman/bin/check_perms -f and I notice that: $ ls -lt /var/lib/mailman/data total 36 -rw-rw---- 1 root list 1132 Jan 26 18:06 aliases -rw-r----- 1 root list 12288 Jan 26 18:06 aliases.db -rw-rw-r-- 1 root list 10 Jan 26 18:04 last_mailman_version -rw-r--r-- 1 root list 14100 Oct 21 22:40 sitelist.cfg Ok, first problem. Where's virtual-mailman (and virtual-mailman.db)? I go to the web interface http://lists.pinyon.org, but there is no 'mailman' list. I try to create the 'mailman' list in the web interface, and I get: Error: List already exists: mailman So... what should I do? Many thanks, Russell --- mm_cfg.py 2011-01-26 18:30:08.000000000 -0700 +++ mm_cfg.py.works 2011-01-26 18:30:28.000000000 -0700 @@ -57,16 +57,16 @@ #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) -DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' +DEFAULT_URL_PATTERN = 'http://%s/' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs -DEFAULT_EMAIL_HOST = 'quine.gb.Pinyon.ORG' +DEFAULT_EMAIL_HOST = 'lists.Pinyon.ORG' #------------------------------------------------------------- # Default host for web interface of newly created MLs -DEFAULT_URL_HOST = 'quine.gb.Pinyon.ORG' +DEFAULT_URL_HOST = 'lists.Pinyon.ORG' #------------------------------------------------------------- # Required when setting any of its arguments. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) @@ -94,8 +94,10 @@ # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. -# MTA='Postfix' - +# RLC: follows /etc/mailman/postfix-to-mailman.py exactly: +MTA='Postfix' +POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.pinyon.org'] +DEB_LISTMASTER = 'postmaster at pinyon.org' #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: From mark at msapiro.net Thu Jan 27 02:48:27 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 26 Jan 2011 17:48:27 -0800 Subject: [Mailman-Users] image filtering In-Reply-To: <1967D5D2-7BC0-41F0-BDFD-4CB7497D7316@4j.lane.edu> Message-ID: Troy Knabe wrote: >A user just sent a message to a list, and the inline image was removed. Under "Content filtering" I have "Should Mailman filter the content of list traffic according to the settings below?" and No is checked. > >Where else should I be looking? First, look at the headers to see if there is a X-Content-Filtered-By: Mailman/MimeDel 2.1.x header indicating Mailman filtered the content. If filter_content is No, there should not be one. Is the list's Non-digest options -> scrub_nondigest set to Yes. If so, all non-plain-text parts will be stored aside and replaced by links to the part content, but if this were the reason, there would have been a link to the content in the message. Other possibilities include "the user didn't remember to attach the image" and "some MTA/MDA between the user and Mailman or between Mailman and you removed it". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jan 27 03:21:43 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 26 Jan 2011 18:21:43 -0800 Subject: [Mailman-Users] configuration problem In-Reply-To: <4D40CBD8.7040801@pinyon.org> Message-ID: Russell L. Carter wrote: >Installing on debian testing, all packages up to date. > >Ok, it complicated maintenance a bit too much in my net to dedicate an >IP address to lists.domain, You didn't need to dedicate an IP address. All you needed was to replace your lists.pinyon.org CNAME quine.pinyon.org. with lists.pinyon.org MX 10 quine.pinyon.org. >so I thought I would try the exact >approach as detailed in the install manual with postfix, namely using >alias_maps and virtual_alias_domains, etc., leading to a postfix >main.cf containing: > >----------------------------------------------------------------- ># http://www.postfix.org/ADDRESS_REWRITING_README.html#masquerade >masquerade_domains = lists.pinyon.org pinyon.org ># http://www.postfix.org/virtual.5.html >virtual_alias_domains = lists.pinyon.org >virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman > >alias_maps = hash:/etc/aliases hash:/var/lib/mailman/data/aliases >alias_database = hash:/etc/aliases >------------------------------------------------------------------ > >And that worked great! Using the suggested initial 'mailman' list >I was able to add subscribers and send/receive, etc. Perfect. > >I ran into a permissions problem with apache and the private archives, >so I thought I would stop at that point, purge the installation, and >carefully recreate the configuration from scratch so that I could >document the exact steps for mailman installation on my site properly. > >So I do (leaving the postfix previously working main.cf untouched): > >$ apt-get remove --purge mailman >$ /bin/rm -rf /var/lib/mailman /usr/lib/mailman >$ cp [my-saved-working-copy-of-mm_cfg.py] /etc/mailman There seems to be something missing here. >$ newlist mailman > [exact same stuff as before] >$ /etc/init.d/mailman start >$ /var/lib/mailman/bin/genaliases >$ /var/lib/mailman/bin/check_perms -f > >and I notice that: > >$ ls -lt /var/lib/mailman/data >total 36 >-rw-rw---- 1 root list 1132 Jan 26 18:06 aliases >-rw-r----- 1 root list 12288 Jan 26 18:06 aliases.db >-rw-rw-r-- 1 root list 10 Jan 26 18:04 last_mailman_version >-rw-r--r-- 1 root list 14100 Oct 21 22:40 sitelist.cfg > >Ok, first problem. Where's virtual-mailman (and virtual-mailman.db)? How did you re-install Mailman. apt-get? Source install? ??? In order to get a virtual-mailman, you first need an mm_cfg.py in the place Mailman is looking for it. This is only /etc/mailman in Debian and certain other packages, not a source install. >I go to the web interface http://lists.pinyon.org, but there is >no 'mailman' list. I try to create the 'mailman' list in the web >interface, and I get: > >Error: List already exists: mailman > >So... what should I do? The list exists, but it's not in the lists.pinyon.org domain. This means that DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST are not 'lists.pinyon.org', at least not in the mm_cfg.py that Mailman is looking at. This could also explain why no virtual-mailman assuming there is POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.pinyon.org'] in mm_cfg.py. Which of the following are you using. The changes in mm_cfg.py.works look OK except the domains in DEFAULT_EMAIL_HOST = 'lists.Pinyon.ORG' and DEFAULT_URL_HOST = 'lists.Pinyon.ORG' should be all lower case. And, I have no idea what lines 74-93 are. Also, see the FAQ at . >--- mm_cfg.py 2011-01-26 18:30:08.000000000 -0700 >+++ mm_cfg.py.works 2011-01-26 18:30:28.000000000 -0700 >@@ -57,16 +57,16 @@ > #------------------------------------------------------------- > # If you change these, you have to configure your http server > # accordingly (Alias and ScriptAlias directives in most httpds) >-DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' >+DEFAULT_URL_PATTERN = 'http://%s/' > PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' > IMAGE_LOGOS = '/images/mailman/' > > #------------------------------------------------------------- > # Default domain for email addresses of newly created MLs >-DEFAULT_EMAIL_HOST = 'quine.gb.Pinyon.ORG' >+DEFAULT_EMAIL_HOST = 'lists.Pinyon.ORG' > #------------------------------------------------------------- > # Default host for web interface of newly created MLs >-DEFAULT_URL_HOST = 'quine.gb.Pinyon.ORG' >+DEFAULT_URL_HOST = 'lists.Pinyon.ORG' > #------------------------------------------------------------- > # Required when setting any of its arguments. > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) >@@ -94,8 +94,10 @@ > # Uncomment if you use Postfix virtual domains (but not > # postfix-to-mailman.py), but be sure to see > # /usr/share/doc/mailman/README.Debian first. >-# MTA='Postfix' >- >+# RLC: follows /etc/mailman/postfix-to-mailman.py exactly: >+MTA='Postfix' >+POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.pinyon.org'] >+DEB_LISTMASTER = 'postmaster at pinyon.org' > #------------------------------------------------------------- > # Uncomment if you want to filter mail with SpamAssassin. For > # more information please visit this website: -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Thu Jan 27 22:42:01 2011 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Thu, 27 Jan 2011 21:42:01 +0000 Subject: [Mailman-Users] To use or not to use content filtering Message-ID: <19792E78AA12F14D9C250101F0DCA01BEBF544@ELROND.hodgsonfamily.org> Hi, I have read various discussions on this list about content filtering settings in Mailman. For the most part, I usually leave content filtering on, and leave the defaults, primarily for protecting list users against malicious attachments (I am enough of an MS veteran now not to care about filtering all HTML). However, over recent months we have had some issues with content filtering on some lists, with users who send emails with disclaimers, where the disclaimer is added as an attachment to the message, and Mailman appears to strip off the actual message, leaving the disclaimer to post to the list, and of course adding in the standard footer. Are people using content filtering in lists where most people are using MS products, and a suitable antivirus package on the MTA as well as a low posting size limit, or are there any tweaks I can make to the content filtering settings that may get some of this stuff through? Thanks. Andrew. From mark at msapiro.net Fri Jan 28 00:45:54 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 27 Jan 2011 15:45:54 -0800 Subject: [Mailman-Users] To use or not to use content filtering In-Reply-To: <19792E78AA12F14D9C250101F0DCA01BEBF544@ELROND.hodgsonfamily.org> Message-ID: Andrew Hodgson wrote: > >However, over recent months we have had some issues with content filtering on some lists, with users who send emails with disclaimers, where the disclaimer is added as an attachment to the message, and Mailman appears to strip off the actual message, leaving the disclaimer to post to the list, and of course adding in the standard footer. I suspect what is happening here is the poster sends an HTML only message. His organization adds a disclaimer as a separate MIME text/plain part and Mailman's content filtering is removing the HTML leaving only the disclaimer. You can avoid this by adding text/html to pass_mime_types and making sure that collapse_alternatives is Yes so multipart/alternative with text/plain and text/html subparts is still replaced by only the text/plain and setting convert_html_to_plaintext according to your desire to have unfiltered HTML converted. >Are people using content filtering in lists where most people are using MS products, and a suitable antivirus package on the MTA as well as a low posting size limit, or are there any tweaks I can make to the content filtering settings that may get some of this stuff through? Agressive content filtering can help with keeping viruses and other malware off the list, but a good malware scanner is probably preferable for that purpose. Content filtering is useful for keeping unwanted things off the list. Unwanted because you don't want to use bandwidth and archive space for images, HTML, proprietary document formats, whatever. Note that if "most people" are using MS products, and they are not restricted, they will post .doc, .docx, .xls and .xlsx attachments. Where does that leave the minority who don't use MS products, not to mention those whose MS products are old enough that they can't handle the XML formats. All MUAs can sensibly display plain text. The same cannot be said for other content types. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From redbullpn at gmail.com Thu Jan 27 21:22:48 2011 From: redbullpn at gmail.com (Roberto Mascarenhas Braga) Date: Thu, 27 Jan 2011 18:22:48 -0200 Subject: [Mailman-Users] Mailman + Postfix + Virtual Domain (LDAP) not working Message-ID: I'm trying to get Mailman working with Postfix as a MTA but with some trouble with virtual domains. I've made setup fine and create my first mailing list, called "mailman". So, as my domain is cdt.unb.br, the list address is mailman at cdt.unb.br. The machine that hosts the mailserver is called mailcdt. So its hostname is mailcdt.cdt.unb.br. If I send a message to mailman at cdt.unb.br - the desired email to the testing list - I cannot receive the message. But if I send the email to mailman at mailcdt.cdt.unb.br (undesired address) I got the message. Here is my config: ___________________________________________________________________________________ *** /etc/mailman/mm_cfg.py *** ___________________________________________________________________________________ POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cdt.unb.br'] from socket import * try: fqdn = getfqdn() except: fqdn = 'mm_cfg_has_unknown_host_domains' DEFAULT_URL_HOST = "mailcdt.cdt.unb.br" DEFAULT_EMAIL_HOST = "cdt.unb.br" VIRTUAL_HOSTS.clear() MTA = 'Postfix' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) ___________________________________________________________________________________ *** /etc/postfix/main.cf ___________________________________________________________________________________ unknown_local_recipient_reject_code = 550 relay_domains = virtual_maps = hash:/etc/postfix/virtual alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases alias_database = hash:/etc/aliases home_mailbox = Maildir/ debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/sbin/sendmail.postfix newaliases_path = /usr/bin/newaliases.postfix mailq_path = /usr/bin/mailq.postfix setgid_group = postdrop html_directory = no manpage_directory = /usr/share/man sample_directory = /usr/share/doc/postfix-2.3.3/samples readme_directory = /usr/share/doc/postfix-2.3.3/README_FILE virtual_mailbox_domains = $mydomain virtual_mailbox_base = /home/vmail virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf virtual_uid_maps = static:500 virtual_gid_maps = static:500 message_size_limit = 30720000 mime_header_checks = regexp:/etc/postfix/mime_header_checks header_checks = regexp:/etc/postfix/header_checks virtual_alias_maps = hash:/etc/mailman/virtual-mailman recipient_delimiter = + From mark at msapiro.net Fri Jan 28 19:38:14 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 28 Jan 2011 10:38:14 -0800 Subject: [Mailman-Users] Mailman + Postfix + Virtual Domain (LDAP) notworking In-Reply-To: Message-ID: Roberto Mascarenhas Braga wrote: > >I've made setup fine and create my first mailing list, called >"mailman". So, as my domain is cdt.unb.br, the list address is >mailman at cdt.unb.br. The machine that hosts the mailserver is called >mailcdt. So its hostname is mailcdt.cdt.unb.br. > >If I send a message to mailman at cdt.unb.br - the desired email to the >testing list - I cannot receive the message. But if I send the email >to mailman at mailcdt.cdt.unb.br (undesired address) I got the message. > >Here is my config: >___________________________________________________________________________________ >*** /etc/mailman/mm_cfg.py *** >___________________________________________________________________________________ >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cdt.unb.br'] > >from socket import * >try: > fqdn = getfqdn() >except: > fqdn = 'mm_cfg_has_unknown_host_domains' > >DEFAULT_URL_HOST = "mailcdt.cdt.unb.br" >DEFAULT_EMAIL_HOST = "cdt.unb.br" >VIRTUAL_HOSTS.clear() >MTA = 'Postfix' >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > >___________________________________________________________________________________ >*** /etc/postfix/main.cf >___________________________________________________________________________________ >unknown_local_recipient_reject_code = 550 >relay_domains = > >virtual_maps = hash:/etc/postfix/virtual >alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases >alias_database = hash:/etc/aliases > >home_mailbox = Maildir/ > >debug_peer_level = 2 >debugger_command = > PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin > xxgdb $daemon_directory/$process_name $process_id & sleep 5 >sendmail_path = /usr/sbin/sendmail.postfix >newaliases_path = /usr/bin/newaliases.postfix >mailq_path = /usr/bin/mailq.postfix >setgid_group = postdrop >html_directory = no >manpage_directory = /usr/share/man >sample_directory = /usr/share/doc/postfix-2.3.3/samples >readme_directory = /usr/share/doc/postfix-2.3.3/README_FILE > >virtual_mailbox_domains = $mydomain >virtual_mailbox_base = /home/vmail >virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf >virtual_uid_maps = static:500 >virtual_gid_maps = static:500 > >message_size_limit = 30720000 > >mime_header_checks = regexp:/etc/postfix/mime_header_checks > >header_checks = regexp:/etc/postfix/header_checks > >virtual_alias_maps = hash:/etc/mailman/virtual-mailman >recipient_delimiter = + Does /etc/mailman/virtual-mailman exist and have entries like mailman at cdt.unb.br mailman mailman-admin at cdt.unb.br mailman-admin ... If so, you may need virtual_alias_domains = cdt.unb.br in main.cf. If not, check the host_name of the 'mailman' list bin/dumpdb lists/mailman/config.pck | grep host_name If the host_name is not cdt.unb.br, run fix_url bin/withlist -l -r fix_url mailman Then, whether or not you needed fix_url, run bin/genaliases -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From redbullpn at gmail.com Fri Jan 28 20:16:49 2011 From: redbullpn at gmail.com (Roberto Mascarenhas Braga) Date: Fri, 28 Jan 2011 17:16:49 -0200 Subject: [Mailman-Users] Mailman + Postfix + Virtual Domain (LDAP) notworking In-Reply-To: References: Message-ID: > Does /etc/mailman/virtual-mailman exist and have entries like > > mailman at cdt.unb.br mailman > mailman-admin at cdt.unb.br mailman-admin Yes. It does exist with the lines above. So I've added virtual_alias_domains = cdt.unb.br to main.cf. Now I got: # postconf | grep virtual_alias_domains proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks virtual_alias_domains = cdt.unb.br Just to check I've made the other steps you told: # /usr/lib/mailman/bin/dumpdb /var/lib/mailman/lists/novalista/config.pck | grep host_name 'digest_footer': '_______________________________________________\n%(real_name)s mailing list\n%(real_name)s@%(host_name)s\n%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s\n', 'host_name': 'cdt.unb.br', 'msg_footer': '_______________________________________________\n%(real_name)s mailing list\n%(real_name)s@%(host_name)s\n%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s\n', So it looks as the host_name is ok, cdt.unb.br. So I didn't run fix_urls. Then I run genaliases and sent a test email again. The I've got the error below: mailcdt postfix/error[8792]: 0CA433806F: to=, relay=none, delay=3.9, delays=3.9/0.03/0/0.03, dsn=5.0.0, status=bounced (User unknown in virtual alias table) Thanks for the help until now. Roberto On Fri, Jan 28, 2011 at 4:38 PM, Mark Sapiro wrote: > Roberto Mascarenhas Braga wrote: >> >>I've made setup fine and create my first mailing list, called >>"mailman". So, as my domain is cdt.unb.br, the list address is >>mailman at cdt.unb.br. The machine that hosts the mailserver is called >>mailcdt. So its hostname is mailcdt.cdt.unb.br. >> >>If I send a message to mailman at cdt.unb.br - the desired email to the >>testing list - I cannot receive the message. But if I send the email >>to mailman at mailcdt.cdt.unb.br (undesired address) I got the message. >> >>Here is my config: >>___________________________________________________________________________________ >>*** /etc/mailman/mm_cfg.py *** >>___________________________________________________________________________________ >>POSTFIX_STYLE_VIRTUAL_DOMAINS ? = ['cdt.unb.br'] >> >>from socket import * >>try: >> ? ?fqdn = getfqdn() >>except: >> ? ?fqdn = 'mm_cfg_has_unknown_host_domains' >> >>DEFAULT_URL_HOST ? = "mailcdt.cdt.unb.br" >>DEFAULT_EMAIL_HOST = "cdt.unb.br" >>VIRTUAL_HOSTS.clear() >>MTA = 'Postfix' >>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) >> >>___________________________________________________________________________________ >>*** /etc/postfix/main.cf >>___________________________________________________________________________________ >>unknown_local_recipient_reject_code = 550 >>relay_domains = >> >>virtual_maps = hash:/etc/postfix/virtual >>alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases >>alias_database = hash:/etc/aliases >> >>home_mailbox = Maildir/ >> >>debug_peer_level = 2 >>debugger_command = >> ? ? ? ? PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin >> ? ? ? ? xxgdb $daemon_directory/$process_name $process_id & sleep 5 >>sendmail_path = /usr/sbin/sendmail.postfix >>newaliases_path = /usr/bin/newaliases.postfix >>mailq_path = /usr/bin/mailq.postfix >>setgid_group = postdrop >>html_directory = no >>manpage_directory = /usr/share/man >>sample_directory = /usr/share/doc/postfix-2.3.3/samples >>readme_directory = /usr/share/doc/postfix-2.3.3/README_FILE >> >>virtual_mailbox_domains = $mydomain >>virtual_mailbox_base = /home/vmail >>virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf >>virtual_uid_maps = static:500 >>virtual_gid_maps = static:500 >> >>message_size_limit = 30720000 >> >>mime_header_checks = regexp:/etc/postfix/mime_header_checks >> >>header_checks = regexp:/etc/postfix/header_checks >> >>virtual_alias_maps = hash:/etc/mailman/virtual-mailman >>recipient_delimiter = + > > > Does /etc/mailman/virtual-mailman exist and have entries like > > mailman at cdt.unb.br ? ? ? ? mailman > mailman-admin at cdt.unb.br ? mailman-admin > ... > > If so, you may need > > virtual_alias_domains = cdt.unb.br > > in main.cf. > > If not, check the host_name of the 'mailman' list > > ?bin/dumpdb lists/mailman/config.pck | grep host_name > > If the host_name is not cdt.unb.br, run fix_url > > ?bin/withlist -l -r fix_url mailman > > Then, whether or not you needed fix_url, run > > ?bin/genaliases > > > -- > Mark Sapiro ? ? ? ?The highway is for gamblers, > San Francisco Bay Area, California ? ?better use your sense - B. Dylan > > From redbullpn at gmail.com Fri Jan 28 20:24:48 2011 From: redbullpn at gmail.com (Roberto Mascarenhas Braga) Date: Fri, 28 Jan 2011 17:24:48 -0200 Subject: [Mailman-Users] Mailman + Postfix + Virtual Domain (LDAP) notworking In-Reply-To: References: Message-ID: I've just noticed that adding virtual_alias_domains = cdt.unb.br to main.cf stops my LDAP Binding. So I removed it and took the original error (unknown user). The virtual-mailman file is fine with the alias. Roberto On Fri, Jan 28, 2011 at 5:16 PM, Roberto Mascarenhas Braga wrote: >> Does /etc/mailman/virtual-mailman exist and have entries like >> >> mailman at cdt.unb.br ? ? ? ? mailman >> mailman-admin at cdt.unb.br ? mailman-admin > > Yes. It does exist with the lines above. So I've added > virtual_alias_domains = cdt.unb.br to main.cf. Now I got: > > # postconf | grep virtual_alias_domains > proxy_read_maps = $local_recipient_maps $mydestination > $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps > $virtual_mailbox_domains $relay_recipient_maps $relay_domains > $canonical_maps $sender_canonical_maps $recipient_canonical_maps > $relocated_maps $transport_maps $mynetworks > virtual_alias_domains = cdt.unb.br > > Just to check I've made the other steps you told: > # /usr/lib/mailman/bin/dumpdb > /var/lib/mailman/lists/novalista/config.pck | grep host_name > ? ?'digest_footer': > '_______________________________________________\n%(real_name)s > mailing list\n%(real_name)s@%(host_name)s\n%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s\n', > ? ?'host_name': 'cdt.unb.br', > ? ?'msg_footer': > '_______________________________________________\n%(real_name)s > mailing list\n%(real_name)s@%(host_name)s\n%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s\n', > > > So it looks as the host_name is ok, cdt.unb.br. So I didn't run fix_urls. > > Then I run genaliases and sent a test email again. The I've got the error below: > > mailcdt postfix/error[8792]: 0CA433806F: to=, > relay=none, delay=3.9, delays=3.9/0.03/0/0.03, dsn=5.0.0, > status=bounced (User unknown in virtual alias table) > > > Thanks for the help until now. > > Roberto > > > > On Fri, Jan 28, 2011 at 4:38 PM, Mark Sapiro wrote: >> Roberto Mascarenhas Braga wrote: >>> >>>I've made setup fine and create my first mailing list, called >>>"mailman". So, as my domain is cdt.unb.br, the list address is >>>mailman at cdt.unb.br. The machine that hosts the mailserver is called >>>mailcdt. So its hostname is mailcdt.cdt.unb.br. >>> >>>If I send a message to mailman at cdt.unb.br - the desired email to the >>>testing list - I cannot receive the message. But if I send the email >>>to mailman at mailcdt.cdt.unb.br (undesired address) I got the message. >>> >>>Here is my config: >>>___________________________________________________________________________________ >>>*** /etc/mailman/mm_cfg.py *** >>>___________________________________________________________________________________ >>>POSTFIX_STYLE_VIRTUAL_DOMAINS ? = ['cdt.unb.br'] >>> >>>from socket import * >>>try: >>> ? ?fqdn = getfqdn() >>>except: >>> ? ?fqdn = 'mm_cfg_has_unknown_host_domains' >>> >>>DEFAULT_URL_HOST ? = "mailcdt.cdt.unb.br" >>>DEFAULT_EMAIL_HOST = "cdt.unb.br" >>>VIRTUAL_HOSTS.clear() >>>MTA = 'Postfix' >>>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) >>> >>>___________________________________________________________________________________ >>>*** /etc/postfix/main.cf >>>___________________________________________________________________________________ >>>unknown_local_recipient_reject_code = 550 >>>relay_domains = >>> >>>virtual_maps = hash:/etc/postfix/virtual >>>alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases >>>alias_database = hash:/etc/aliases >>> >>>home_mailbox = Maildir/ >>> >>>debug_peer_level = 2 >>>debugger_command = >>> ? ? ? ? PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin >>> ? ? ? ? xxgdb $daemon_directory/$process_name $process_id & sleep 5 >>>sendmail_path = /usr/sbin/sendmail.postfix >>>newaliases_path = /usr/bin/newaliases.postfix >>>mailq_path = /usr/bin/mailq.postfix >>>setgid_group = postdrop >>>html_directory = no >>>manpage_directory = /usr/share/man >>>sample_directory = /usr/share/doc/postfix-2.3.3/samples >>>readme_directory = /usr/share/doc/postfix-2.3.3/README_FILE >>> >>>virtual_mailbox_domains = $mydomain >>>virtual_mailbox_base = /home/vmail >>>virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf >>>virtual_uid_maps = static:500 >>>virtual_gid_maps = static:500 >>> >>>message_size_limit = 30720000 >>> >>>mime_header_checks = regexp:/etc/postfix/mime_header_checks >>> >>>header_checks = regexp:/etc/postfix/header_checks >>> >>>virtual_alias_maps = hash:/etc/mailman/virtual-mailman >>>recipient_delimiter = + >> >> >> Does /etc/mailman/virtual-mailman exist and have entries like >> >> mailman at cdt.unb.br ? ? ? ? mailman >> mailman-admin at cdt.unb.br ? mailman-admin >> ... >> >> If so, you may need >> >> virtual_alias_domains = cdt.unb.br >> >> in main.cf. >> >> If not, check the host_name of the 'mailman' list >> >> ?bin/dumpdb lists/mailman/config.pck | grep host_name >> >> If the host_name is not cdt.unb.br, run fix_url >> >> ?bin/withlist -l -r fix_url mailman >> >> Then, whether or not you needed fix_url, run >> >> ?bin/genaliases >> >> >> -- >> Mark Sapiro ? ? ? ?The highway is for gamblers, >> San Francisco Bay Area, California ? ?better use your sense - B. Dylan >> >> > From john_espiro at yahoo.com Fri Jan 28 21:05:17 2011 From: john_espiro at yahoo.com (John Espiro) Date: Fri, 28 Jan 2011 21:05:17 +0100 Subject: [Mailman-Users] Cannot exec /etc/mail/smrsh: Permission denied Message-ID: <4D43217D.3080909@yahoo.com> When I send a message to the mailing list I get: sm-mta[16327]: p0SJuInx016321: SYSERR(root): Cannot exec /etc/mail/smrsh: Permission denied Jan 28 19:56:22 sm-mta[16326]: p0SJuInx016321: to="|/usr/lib/mailman/mail/mailman post LISTNAME", ctladdr=

(8/0), delay=00:00:01, xdelay=00:00:00, mailer=prog, pri=31689, dsn=4.0.0, stat=Operating system error System: Ubuntu 10.10 Server 64bit I've read through this: http://www.gnu.org/software/mailman/mailman-install/node32.html grep smrsh /etc/mail/sendmail.cf ##### $Id: smrsh.m4,v 8.14 1999/11/18 05:06:23 ca Exp $ ##### Mprog, P=/etc/mail/smrsh, F=lsDFM smrsh is in: :/usr/lib/sm.bin In /usr/lib/sm.bin, I ran: ln -s /usr/lib/mailman/mail/mailman mailman In /etc/mail/smrsh, I ran: ln -s /usr/lib/mailman/mail/mailman mailman Still, the problem persists. I am sure this must be a permissions issue, then again, maybe not. Other data: uid=51(smmsp) gid=51(smmsp) groups=51(smmsp),45(sasl) uid=103(smmta) gid=106(smmta) groups=106(smmta),45(sasl) uid=8(mail) gid=8(mail) groups=8(mail) ls -la /etc/mail/smrsh drwsr-sr-x 2 root root 4096 2011-01-28 19:31 . From mark at msapiro.net Sat Jan 29 00:43:09 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 28 Jan 2011 15:43:09 -0800 Subject: [Mailman-Users] Mailman + Postfix + Virtual Domain (LDAP) notworking In-Reply-To: