From dnewman at networktest.com Mon Nov 1 00:56:08 2010 From: dnewman at networktest.com (David Newman) Date: Sun, 31 Oct 2010 16:56:08 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: References: Message-ID: <4CCE0218.6000507@networktest.com> On 10/31/10 9:09 AM, Mark Sapiro wrote: > David Newman wrote: > >> (Apologies for re-raising a topic I asked about here a couple of years >> ago. The instructions on Sourceforge have changed a bit since then.) >> >> New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual >> domains. Mail sent to/from virtual domains works fine. >> >> Different story with Mailman. Although postfix says a message addressed >> to a list is "sent" to all addresses, subscribers from virtual domains >> on this server do not receive the message. Subscribers on other domains >> not on this server do receive the message. There's no indication of >> trouble in the Mailman logs or in maillog. > > > What exactly does the Postfix log (maillog) say about the delivery to > one of these addresses? maillog says status is "sent" to all list subscribers. The test list, called "s", has one subscriber in domain1.tld on this server (who got the initial welcome to this list message from Mailman but not any messages) and one subscriber in another domain somewhere else (who gets all messages. Again, postfix tells the maillog that a message sent to the list address is "status=sent" to both subscribers. > > >> I've followed the setup instructions here, doing section 6.1.2 before >> 6.1.1 (given the link about doing virtual stuff first): >> >> http://mailman.sourceforge.net/mailman-install/postfix-virtual.html >> http://mailman.sourceforge.net/mailman-install/postfix-integration.html > > > This normally only affects delivery TO a list in a virtual domain. If > done properly, it should not affect delivery to any non-list address > in the virtual domains. Sorry if I was unclear. Mail delivery to and from non-list addresses in virtual domains on this server works fine. The only messages that are not being delivered are those to a subscriber in domain1.tld on this server. (I haven't yet tried subscribing anyone in domain2.tld or domain3.tld.) > > >> I've pasted the config files below. >> >> Thanks in advance for clues on getting Mailman to deliver to virtual >> addresses on this server. > > > This is almost certainly a Postfix issue rather than a Mailman issue. > If there is nothing in Mailman's smtp-failure log, Mailman has > delivered the message whith the local virtual recipients included to > Postfix and Postfix has accepted it. > > See additional comments inline below. > > >> server hostname: >> mail.domain1.tld >> >> virtual domains: >> domain1.tld # (not its real name!) >> domain2.tld >> domain3.tld Just to clarify: domain1.tld is not virtual, in the sense that the server's canonical hostname is mail.domain1.tld. However, addresses defined in this domain are virtual -- these users do not have local accounts on this server. Again, non-list mail to and from these users works as expected. >> >> ----- >> >>from /etc/postfix/main.cf: >> >> .. >> >> myhostname = mail.domain1.tld >> mydomain = domain1.tld >> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >> >> .. >> >> alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases >> >> virtual_alias_maps = >> proxy:mysql:/etc/postfix/sql/forwardings.cf >> proxy:mysql:/etc/postfix/sql/email2email.cf >> hash:/usr/local/mailman/data/domain1-tld >> hash:/usr/local/mailman/data/virtual-mailman > > > Full output from "postconf -n" might help. Here you go: alias_database = hash:/etc/mail/aliases alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases command_directory = /usr/local/sbin config_directory = /etc/postfix daemon_directory = /usr/local/libexec/postfix header_checks = pcre:/etc/postfix/header_checks.pcre mail_owner = _postfix mailq_path = /usr/local/sbin/mailq manpage_directory = /usr/local/man message_size_limit = 27962027 milter_connect_macros = j {daemon_name} v _ milter_default_action = tempfail milter_header_checks = pcre:/etc/postfix/milter_header_checks mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = domain1.tld myhostname = mail.domain1.tld mynetworks = 127.0.0.0/8 newaliases_path = /usr/bin/newaliases proxy_read_maps = proxy:mysql:/etc/postfix/sql/routing.cf proxy:mysql:/etc/postfix/sql/domains.cf proxy:mysql:/etc/postfix/sql/mailboxes.cf proxy:mysql:/etc/postfix/sql/user.cf proxy:mysql:/etc/postfix/sql/group.cf proxy:mysql:/etc/postfix/sql/forwardings.cf proxy:mysql:/etc/postfix/sql/email2email.cf proxy:unix:passwd.byname unix:passwd.byname queue_directory = /var/spool/postfix readme_directory = /usr/local/share/doc/postfix/readme recipient_delimiter = + relay_domains = proxy:mysql:/etc/postfix/sql/routing.cf sample_directory = /etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = _postdrop smtp_tls_cert_file = /etc/ssl/server.crt smtp_tls_key_file = /etc/ssl/private/server.key smtp_tls_security_level = may smtpd_delay_reject = yes smtpd_helo_required = yes smtpd_milters = unix:/tmp/clamav-milter.sock smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unauth_pipelining, reject_invalid_hostname, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_rbl_client zen.spamhaus.org smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = smtpd_sasl_security_options = noanonymous smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/server.crt smtpd_tls_key_file = /etc/ssl/private/server.key smtpd_tls_received_header = yes smtpd_tls_security_level = may smtpd_use_tls = yes strict_rfc821_envelopes = yes transport_maps = proxy:mysql:/etc/postfix/sql/routing.cf unknown_local_recipient_reject_code = 550 virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/sql/forwardings.cf proxy:mysql:/etc/postfix/sql/email2email.cf hash:/usr/local/mailman/data/domain1.tld hash:/usr/local/mailman/data/virtual-mailman virtual_gid_maps = proxy:mysql:/etc/postfix/sql/group.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mailboxes.cf virtual_minimum_uid = 1000 virtual_transport = dovecot virtual_uid_maps = proxy:mysql:/etc/postfix/sql/user.cf > > >> ----- >> >>from /usr/local/mailman/Mailman/mm_cfg.py: >> >> MTA = 'Postfix' >> MAILMAN_SITE_LIST = 'mailman' >> DEFAULT_EMAIL_HOST = 'domain1.tld' >> DEFAULT_URL_HOST = 'mail.domain1.tld' >> DEFAULT_URL_PATTERN = 'https://%s/mailman/' >> PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' >> IMAGE_LOGOS = '/icons/' >> POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias' >> POSTFIX_MAP_CMD = '/usr/local/sbin/postmap' >> POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ] >> # Clear the Defaults.py VIRTUAL_HOSTS entry >> VIRTUAL_HOSTS.clear() >> add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST') > > > The above is backwards. It should be > > add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') > > >> add_virtualhost('domain2.tld', 'domain2.tld') >> add_virtualhost('domain3.tld', 'domain3.tld') > > > However, nothing here affects delivery of mail FROM mailman. > OK > >> ----- >> >> /usr/local/mailman/data/aliases >> >> >> # The ultimate loop stopper address >> mailman-loop: /usr/local/mailman/data/owner-bounces.mbox >> >> # STANZA START: mailman >> # CREATED: Sat Oct 30 11:23:37 2010 >> 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 >> >> # STANZA START: s >> # CREATED: Sat Oct 30 11:35:12 2010 >> s: "|/usr/local/mailman/mail/mailman post s" >> s-admin: "|/usr/local/mailman/mail/mailman admin s" >> s-bounces: "|/usr/local/mailman/mail/mailman bounces s" >> s-confirm: "|/usr/local/mailman/mail/mailman confirm s" >> s-join: "|/usr/local/mailman/mail/mailman join s" >> s-leave: "|/usr/local/mailman/mail/mailman leave s" >> s-owner: "|/usr/local/mailman/mail/mailman owner s" >> s-request: "|/usr/local/mailman/mail/mailman request s" >> s-subscribe: "|/usr/local/mailman/mail/mailman subscribe s" >> s-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe s" >> # STANZA END: s > > > Likewise, the aliases above only affect delivery TO the mailman and s > lists. OK > > >> ----- >> >> /usr/local/etc/mailman/data/domain1-tld: >> >> domain1.tld IGNORE >> @domain1.tld @mail.domain1.tld > > > This file and its reference in virtual_alias_maps is conflicting as > this says domain1.tld is a virtual alias domain and its presence in > mydestination says it's not. Also, this is obsolete in Postfix. The > current method of specifying to postfix that a domain is a virtual > alias domain is to list it in virtual_alias_domains in main.cf. This came from section 6.1.2 of the Mailman docs on integration with postfix. This, along with the part at the top of section 6.1.1 saying to do this stuff first, is perhaps the most confusing part of the Mailman docs. If this method is obsolete in Postfix, it's time to revise these docs (and as a sometime tech writer I volunteer to help once I understand this). Just double-checking: I think you're saying to treat domain1.tld as a virtual alias domain. True? If so I think the changes to do this would be: 1. in main.cf, delete the myhostname and mydomain lines ((not sure these are strictly needed given that postfix gets these anyway from gethostbyname() )) 2. in main.cf, remove $mydomain from $mydestination 3. in main.cf, delete '/usr/local/etc/mailman/data/domain1-tld' from virtual_alias_maps > > >> ----- >> >> /usr/local/mailman/data/virtual-mailman: >> >> # LOOP ADDRESSES START >> mailman-loop at domain1.tld mailman-loop >> # LOOP ADDRESSES END >> >> # STANZA START: s >> # CREATED: Sat Oct 30 11:35:12 2010 >> s at domain1.tld s >> s-admin at domain1.tld s-admin >> s-bounces at domain1.tld s-bounces >> s-confirm at domain1.tld s-confirm >> s-join at domain1.tld s-join >> s-leave at domain1.tld s-leave >> s-owner at domain1.tld s-owner >> s-request at domain1.tld s-request >> s-subscribe at domain1.tld s-subscribe >> s-unsubscribe at domain1.tld s-unsubscribe >> # STANZA END: s > > > And this virtual mapping only affects delivery to the s at domain1.tld > list and it's associated admin addresses, but since domain1.tld is not > in POSTFIX_STYLE_VIRTUAL_DOMAINS (which is correct because it is in > main.cf mydestination which makes it a postfix local domain), why is > this list in virtual-mailman at all. Clearly I'm confused as to whether domain1.tld should or should not be defined as a virtual domain. The Mailman docs on postfix integration say no, but I think you're saying to treat it as a virtual domain. Thanks very much for any further clues. dn > >> ----- > From mark at msapiro.net Mon Nov 1 06:22:52 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 Oct 2010 22:22:52 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: <4CCE0218.6000507@networktest.com> References: <4CCE0218.6000507@networktest.com> Message-ID: <4CCE4EAC.6070503@msapiro.net> On 10/31/10 4:56 PM, David Newman wrote: > On 10/31/10 9:09 AM, Mark Sapiro wrote: >> >> What exactly does the Postfix log (maillog) say about the delivery to >> one of these addresses? > > > maillog says status is "sent" to all list subscribers. The test list, > called "s", has one subscriber in domain1.tld on this server (who got > the initial welcome to this list message from Mailman but not any > messages) and one subscriber in another domain somewhere else (who gets > all messages. > > Again, postfix tells the maillog that a message sent to the list address > is "status=sent" to both subscribers. And what is the rest of the information in those log messages, i.e. the remainder of the sent= and the relay= for example. Please post the entire log line. >> >> >>> I've followed the setup instructions here, doing section 6.1.2 before >>> 6.1.1 (given the link about doing virtual stuff first): >>> >>> http://mailman.sourceforge.net/mailman-install/postfix-virtual.html >>> http://mailman.sourceforge.net/mailman-install/postfix-integration.html >> >> >> This normally only affects delivery TO a list in a virtual domain. If >> done properly, it should not affect delivery to any non-list address >> in the virtual domains. > > Sorry if I was unclear. Mail delivery to and from non-list addresses in > virtual domains on this server works fine. The only messages that are > not being delivered are those to a subscriber in domain1.tld on this > server. (I haven't yet tried subscribing anyone in domain2.tld or > domain3.tld.) You were clear. I was only trying to say that those Postfix configurations only affect mail TO mailman. They don't affect the issue you are asking about. >>> I've pasted the config files below. >>> >>> Thanks in advance for clues on getting Mailman to deliver to virtual >>> addresses on this server. >> >> >> This is almost certainly a Postfix issue rather than a Mailman issue. >> If there is nothing in Mailman's smtp-failure log, Mailman has >> delivered the message whith the local virtual recipients included to >> Postfix and Postfix has accepted it. >> >> See additional comments inline below. >> >> >>> server hostname: >>> mail.domain1.tld >>> >>> virtual domains: >>> domain1.tld # (not its real name!) >>> domain2.tld >>> domain3.tld > > Just to clarify: domain1.tld is not virtual, in the sense that the > server's canonical hostname is mail.domain1.tld. However, addresses > defined in this domain are virtual -- these users do not have local > accounts on this server. Again, non-list mail to and from these users > works as expected. > > >>> >>> ----- >>> >> >from /etc/postfix/main.cf: >>> >>> .. >>> >>> myhostname = mail.domain1.tld >>> mydomain = domain1.tld >>> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >>> >>> .. >>> >>> alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases >>> >>> virtual_alias_maps = >>> proxy:mysql:/etc/postfix/sql/forwardings.cf >>> proxy:mysql:/etc/postfix/sql/email2email.cf >>> hash:/usr/local/mailman/data/domain1-tld >>> hash:/usr/local/mailman/data/virtual-mailman >> >> >> Full output from "postconf -n" might help. > > Here you go: > > alias_database = hash:/etc/mail/aliases > alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases > command_directory = /usr/local/sbin > config_directory = /etc/postfix > daemon_directory = /usr/local/libexec/postfix > header_checks = pcre:/etc/postfix/header_checks.pcre > mail_owner = _postfix > mailq_path = /usr/local/sbin/mailq > manpage_directory = /usr/local/man > message_size_limit = 27962027 > milter_connect_macros = j {daemon_name} v _ > milter_default_action = tempfail > milter_header_checks = pcre:/etc/postfix/milter_header_checks > mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain > mydomain = domain1.tld > myhostname = mail.domain1.tld > mynetworks = 127.0.0.0/8 > newaliases_path = /usr/bin/newaliases > proxy_read_maps = proxy:mysql:/etc/postfix/sql/routing.cf > proxy:mysql:/etc/postfix/sql/domains.cf > proxy:mysql:/etc/postfix/sql/mailboxes.cf > proxy:mysql:/etc/postfix/sql/user.cf > proxy:mysql:/etc/postfix/sql/group.cf > proxy:mysql:/etc/postfix/sql/forwardings.cf > proxy:mysql:/etc/postfix/sql/email2email.cf proxy:unix:passwd.byname > unix:passwd.byname > queue_directory = /var/spool/postfix > readme_directory = /usr/local/share/doc/postfix/readme > recipient_delimiter = + > relay_domains = proxy:mysql:/etc/postfix/sql/routing.cf > sample_directory = /etc/postfix > sendmail_path = /usr/local/sbin/sendmail > setgid_group = _postdrop > smtp_tls_cert_file = /etc/ssl/server.crt > smtp_tls_key_file = /etc/ssl/private/server.key > smtp_tls_security_level = may > smtpd_delay_reject = yes > smtpd_helo_required = yes > smtpd_milters = unix:/tmp/clamav-milter.sock > smtpd_recipient_restrictions = permit_mynetworks, > permit_sasl_authenticated, reject_unauth_destination, > reject_unauth_pipelining, reject_invalid_hostname, > reject_unknown_sender_domain, reject_unknown_recipient_domain, > reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_rbl_client > zen.spamhaus.org > smtpd_sasl_auth_enable = yes > smtpd_sasl_local_domain = > smtpd_sasl_security_options = noanonymous > smtpd_tls_auth_only = yes > smtpd_tls_cert_file = /etc/ssl/server.crt > smtpd_tls_key_file = /etc/ssl/private/server.key > smtpd_tls_received_header = yes > smtpd_tls_security_level = may > smtpd_use_tls = yes > strict_rfc821_envelopes = yes > transport_maps = proxy:mysql:/etc/postfix/sql/routing.cf > unknown_local_recipient_reject_code = 550 > virtual_alias_domains = Here you want virtual_alias_domains = domain2.tld, domain3.tld > virtual_alias_maps = proxy:mysql:/etc/postfix/sql/forwardings.cf > proxy:mysql:/etc/postfix/sql/email2email.cf > hash:/usr/local/mailman/data/domain1.tld and remove the above which may possibly fix your problem. > hash:/usr/local/mailman/data/virtual-mailman > virtual_gid_maps = proxy:mysql:/etc/postfix/sql/group.cf > virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf > virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mailboxes.cf > virtual_minimum_uid = 1000 > virtual_transport = dovecot > virtual_uid_maps = proxy:mysql:/etc/postfix/sql/user.cf > > >> >> >>> ----- >>> >> >from /usr/local/mailman/Mailman/mm_cfg.py: >>> >>> MTA = 'Postfix' >>> MAILMAN_SITE_LIST = 'mailman' >>> DEFAULT_EMAIL_HOST = 'domain1.tld' >>> DEFAULT_URL_HOST = 'mail.domain1.tld' >>> DEFAULT_URL_PATTERN = 'https://%s/mailman/' >>> PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' >>> IMAGE_LOGOS = '/icons/' >>> POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias' >>> POSTFIX_MAP_CMD = '/usr/local/sbin/postmap' >>> POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ] >>> # Clear the Defaults.py VIRTUAL_HOSTS entry >>> VIRTUAL_HOSTS.clear() >>> add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST') >> >> >> The above is backwards. It should be >> >> add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') >> >> >>> add_virtualhost('domain2.tld', 'domain2.tld') >>> add_virtualhost('domain3.tld', 'domain3.tld') >> >> >> However, nothing here affects delivery of mail FROM mailman. >> > > OK > >> >>> ----- >>> >>> /usr/local/mailman/data/aliases >>> >>> >>> # The ultimate loop stopper address >>> mailman-loop: /usr/local/mailman/data/owner-bounces.mbox >>> >>> # STANZA START: mailman >>> # CREATED: Sat Oct 30 11:23:37 2010 >>> 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 >>> >>> # STANZA START: s >>> # CREATED: Sat Oct 30 11:35:12 2010 >>> s: "|/usr/local/mailman/mail/mailman post s" >>> s-admin: "|/usr/local/mailman/mail/mailman admin s" >>> s-bounces: "|/usr/local/mailman/mail/mailman bounces s" >>> s-confirm: "|/usr/local/mailman/mail/mailman confirm s" >>> s-join: "|/usr/local/mailman/mail/mailman join s" >>> s-leave: "|/usr/local/mailman/mail/mailman leave s" >>> s-owner: "|/usr/local/mailman/mail/mailman owner s" >>> s-request: "|/usr/local/mailman/mail/mailman request s" >>> s-subscribe: "|/usr/local/mailman/mail/mailman subscribe s" >>> s-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe s" >>> # STANZA END: s >> >> >> Likewise, the aliases above only affect delivery TO the mailman and s >> lists. > > OK > >> >> >>> ----- >>> >>> /usr/local/etc/mailman/data/domain1-tld: >>> >>> domain1.tld IGNORE >>> @domain1.tld @mail.domain1.tld >> >> >> This file and its reference in virtual_alias_maps is conflicting as >> this says domain1.tld is a virtual alias domain and its presence in >> mydestination says it's not. Also, this is obsolete in Postfix. The >> current method of specifying to postfix that a domain is a virtual >> alias domain is to list it in virtual_alias_domains in main.cf. > > This came from section 6.1.2 of the Mailman docs on integration with > postfix. This, along with the part at the top of section 6.1.1 saying to > do this stuff first, is perhaps the most confusing part of the Mailman > docs. If this method is obsolete in Postfix, it's time to revise these > docs (and as a sometime tech writer I volunteer to help once I > understand this). > > Just double-checking: I think you're saying to treat domain1.tld as a > virtual alias domain. True? No. I'm saying domain1.tld is not currently treated as a virtual domain in Postfix except for the above file and its reference in virtual_alias_maps. I think both the ile and the reference should be removed. > If so I think the changes to do this would be: > > 1. in main.cf, delete the myhostname and mydomain lines ((not sure these > are strictly needed given that postfix gets these anyway from > gethostbyname() )) > > 2. in main.cf, remove $mydomain from $mydestination I think you should leave the above as is. > 3. in main.cf, delete '/usr/local/etc/mailman/data/domain1-tld' from > virtual_alias_maps As I said above, I think you should do this. >> >> >>> ----- >>> >>> /usr/local/mailman/data/virtual-mailman: >>> >>> # LOOP ADDRESSES START >>> mailman-loop at domain1.tld mailman-loop >>> # LOOP ADDRESSES END >>> >>> # STANZA START: s >>> # CREATED: Sat Oct 30 11:35:12 2010 >>> s at domain1.tld s >>> s-admin at domain1.tld s-admin >>> s-bounces at domain1.tld s-bounces >>> s-confirm at domain1.tld s-confirm >>> s-join at domain1.tld s-join >>> s-leave at domain1.tld s-leave >>> s-owner at domain1.tld s-owner >>> s-request at domain1.tld s-request >>> s-subscribe at domain1.tld s-subscribe >>> s-unsubscribe at domain1.tld s-unsubscribe >>> # STANZA END: s >> >> >> And this virtual mapping only affects delivery to the s at domain1.tld >> list and it's associated admin addresses, but since domain1.tld is not >> in POSTFIX_STYLE_VIRTUAL_DOMAINS (which is correct because it is in >> main.cf mydestination which makes it a postfix local domain), why is >> this list in virtual-mailman at all. > > Clearly I'm confused as to whether domain1.tld should or should not be > defined as a virtual domain. The Mailman docs on postfix integration say > no, but I think you're saying to treat it as a virtual domain. No, I'm saying it's not a virtual domain and should not be treated as such. I'm also asking how the above virtual-mailman got created with entries for s*@domain1.tld when domain1.tld is not in POSTFIX_STYLE_VIRTUAL_DOMAINS in the first place? Also, it appears you are taking much too literally. That section describes a complicated situation which is not typically encountered in practice. And yes, it should probably be heavily revised. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California Better use your sense - B. Dylan From tanstaafl at libertytrek.org Mon Nov 1 14:36:57 2010 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Mon, 01 Nov 2010 09:36:57 -0400 Subject: [Mailman-Users] Mailman DOA after power outage crash. In-Reply-To: References: Message-ID: <4CCEC279.6050201@libertytrek.org> On 2010-10-31 7:00 AM, "J.A. Terranson" wrote: > Thanks for the flush information: even though this was a unique > situation (every box in the rack was damaged, several beyond repair > [including the backup server]), living in the middle of the tornado > capital of the world means it could realistically happen again, so > thats a really good one to know. Sounds to me like you should make it a priority to get your servers communicating with your UPS's to perform safe shutdowns for extended power outages? From dnewman at networktest.com Mon Nov 1 20:06:53 2010 From: dnewman at networktest.com (David Newman) Date: Mon, 01 Nov 2010 12:06:53 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: <4CCE4EAC.6070503@msapiro.net> References: <4CCE0218.6000507@networktest.com> <4CCE4EAC.6070503@msapiro.net> Message-ID: <4CCF0FCD.6080200@networktest.com> On 10/31/10 10:22 PM, Mark Sapiro wrote: > On 10/31/10 4:56 PM, David Newman wrote: >> On 10/31/10 9:09 AM, Mark Sapiro wrote: >>> >>> What exactly does the Postfix log (maillog) say about the delivery to >>> one of these addresses? >> >> >> maillog says status is "sent" to all list subscribers. The test list, >> called "s", has one subscriber in domain1.tld on this server (who got >> the initial welcome to this list message from Mailman but not any >> messages) and one subscriber in another domain somewhere else (who gets >> all messages. >> >> Again, postfix tells the maillog that a message sent to the list address >> is "status=sent" to both subscribers. > > > And what is the rest of the information in those log messages, i.e. the > remainder of the sent= and the relay= for example. Please post the > entire log line. Here's a log snapshot of a message sent to s at domain1.tld, a Mailman list with subscribers 'dnewman at networktest.com' and 'dnewman at domain1.tld'. This is after removing 'hash:/usr/local/mailman/data/domain1-tld' from virtual_alias_maps as you suggested and reloading Mailman and postfix. I'm embedded one comment and one question: Nov 1 11:51:29 mail postfix/postfix-script[5384]: refreshing the Postfix mail system Nov 1 11:51:29 mail postfix/master[19348]: reload -- version 2.6.5, configuration /etc/postfix Nov 1 11:51:59 mail postfix/smtpd[32434]: connect from mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains This is a possible clue. I think postfix is set up so that domain1.tld *is* a virtual domain. The server -- Mailserver, an email server appliance from Allard Software -- stores domain info in a SQL database and postfix calls that database here: virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf Anyway, carrying on: Nov 1 11:51:59 mail postfix/smtpd[32434]: A91E1130CB: client=mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/cleanup[25359]: A91E1130CB: message-id=<4CCF0C4E.8000704 at networktest.com> Nov 1 11:51:59 mail postfix/smtpd[32434]: disconnect from mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/qmgr[20853]: A91E1130CB: from=, size=1495, nrcpt=1 (queue active) Nov 1 11:51:59 mail spamd[10619]: spamd: connection from localhost [127.0.0.1] at port 45013 Nov 1 11:51:59 mail spamd[10619]: spamd: processing message <4CCF0C4E.8000704 at networktest.com> for s at mail.domain1.tld:62 Nov 1 11:52:00 mail spamd[10619]: spamd: clean message (-0.0/5.0) for s at mail.domain1.tld:62 in 1.1 seconds, 1467 bytes. Nov 1 11:52:00 mail spamd[10619]: spamd: result: . 0 - T_RP_MATCHES_RCVD scantime=1.1,size=1467,user=s at mail.domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=45013,mid=<4CCF0C4E.8000704 at networktest.com>,autolearn=ham Nov 1 11:52:01 mail postfix/pickup[1233]: 03422130CD: uid=506 from= Nov 1 11:52:01 mail postfix/pipe[16800]: A91E1130CB: to=, orig_to=, relay=spamassassin, delay=1.6, delays=0.33/0.02/0/1.2, dsn=2.0.0, status=sent (delivered via spamassassin service) Nov 1 11:52:01 mail postfix/qmgr[20853]: A91E1130CB: removed Nov 1 11:52:01 mail postfix/cleanup[25359]: 03422130CD: message-id=<4CCF0C4E.8000704 at networktest.com> Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: from=, size=1762, nrcpt=1 (queue active) Nov 1 11:52:01 mail spamd[18056]: prefork: child states: II Nov 1 11:52:01 mail postfix/local[28131]: 03422130CD: to=, relay=local, delay=0.32, delays=0.03/0.02/0/0.26, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post s) Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: removed Nov 1 11:52:02 mail postfix/smtpd[32434]: connect from localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains Nov 1 11:52:02 mail postfix/smtpd[32434]: 80A72130CB: client=localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains Nov 1 11:52:02 mail postfix/cleanup[25359]: 80A72130CB: message-id=<4CCF0C4E.8000704 at networktest.com> Nov 1 11:52:02 mail postfix/smtpd[32434]: disconnect from localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/qmgr[20853]: 80A72130CB: from=, size=2697, nrcpt=2 (queue active) Nov 1 11:52:02 mail spamd[10619]: spamd: connection from localhost [127.0.0.1] at port 5435 Nov 1 11:52:02 mail spamd[10619]: spamd: processing message <4CCF0C4E.8000704 at networktest.com> for dnewman at domain1.tld:62 Nov 1 11:52:07 mail spamd[10619]: spamd: clean message (0.0/5.0) for dnewman at domain1.tld:62 in 4.8 seconds, 2638 bytes. Nov 1 11:52:07 mail spamd[10619]: spamd: result: . 0 - scantime=4.8,size=2638,user=dnewman at domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=5435,mid=<4CCF0C4E.8000704 at networktest.com>,autolearn=ham Nov 1 11:52:07 mail postfix/pickup[1233]: 7027A130CD: uid=506 from= Nov 1 11:52:07 mail postfix/cleanup[25359]: 7027A130CD: message-id=<4CCF0C4E.8000704 at networktest.com> Nov 1 11:52:07 mail postfix/pipe[16800]: 80A72130CB: to=, relay=spamassassin, delay=4.9, delays=0.04/0/0/4.9, dsn=2.0.0, status=sent (delivered via spamassassin service) Nov 1 11:52:07 mail postfix/pipe[16800]: 80A72130CB: to=, relay=spamassassin, delay=4.9, delays=0.04/0/0/4.9, dsn=2.0.0, status=sent (delivered via spamassassin service) I don't understand this entry. Since 's at domain1.tld' never received the message, and since postfix says it was delivered OK, and since there's no indication of trouble in the Mailman logs, what happened to the message? Nov 1 11:52:07 mail postfix/qmgr[20853]: 80A72130CB: removed Nov 1 11:52:07 mail postfix/qmgr[20853]: 7027A130CD: from=, size=2759, nrcpt=1 (queue active) Nov 1 11:52:07 mail spamd[18056]: prefork: child states: II Nov 1 11:52:11 mail postfix/smtp[7413]: 7027A130CD: to=, relay=mail3.networktest.com[69.55.234.104]:25, delay=3.6, delays=0.03/0.04/0.39/3.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as EC0D3256A73) Nov 1 11:52:11 mail postfix/qmgr[20853]: 7027A130CD: removed > > >>> >>> >>>> I've followed the setup instructions here, doing section 6.1.2 before >>>> 6.1.1 (given the link about doing virtual stuff first): >>>> >>>> http://mailman.sourceforge.net/mailman-install/postfix-virtual.html >>>> http://mailman.sourceforge.net/mailman-install/postfix-integration.html >>> >>> >>> This normally only affects delivery TO a list in a virtual domain. If >>> done properly, it should not affect delivery to any non-list address >>> in the virtual domains. >> >> Sorry if I was unclear. Mail delivery to and from non-list addresses in >> virtual domains on this server works fine. The only messages that are >> not being delivered are those to a subscriber in domain1.tld on this >> server. (I haven't yet tried subscribing anyone in domain2.tld or >> domain3.tld.) > > > You were clear. I was only trying to say that those Postfix > configurations only affect mail TO mailman. They don't affect the issue > you are asking about. > > >>>> I've pasted the config files below. >>>> >>>> Thanks in advance for clues on getting Mailman to deliver to virtual >>>> addresses on this server. >>> >>> >>> This is almost certainly a Postfix issue rather than a Mailman issue. >>> If there is nothing in Mailman's smtp-failure log, Mailman has >>> delivered the message whith the local virtual recipients included to >>> Postfix and Postfix has accepted it. >>> >>> See additional comments inline below. >>> >>> >>>> server hostname: >>>> mail.domain1.tld >>>> >>>> virtual domains: >>>> domain1.tld # (not its real name!) >>>> domain2.tld >>>> domain3.tld >> >> Just to clarify: domain1.tld is not virtual, in the sense that the >> server's canonical hostname is mail.domain1.tld. However, addresses >> defined in this domain are virtual -- these users do not have local >> accounts on this server. Again, non-list mail to and from these users >> works as expected. >> >> >>>> >>>> ----- >>>> >>> >from /etc/postfix/main.cf: >>>> >>>> .. >>>> >>>> myhostname = mail.domain1.tld >>>> mydomain = domain1.tld >>>> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >>>> >>>> .. >>>> >>>> alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases >>>> >>>> virtual_alias_maps = >>>> proxy:mysql:/etc/postfix/sql/forwardings.cf >>>> proxy:mysql:/etc/postfix/sql/email2email.cf >>>> hash:/usr/local/mailman/data/domain1-tld >>>> hash:/usr/local/mailman/data/virtual-mailman >>> >>> >>> Full output from "postconf -n" might help. >> >> Here you go: >> >> alias_database = hash:/etc/mail/aliases >> alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases >> command_directory = /usr/local/sbin >> config_directory = /etc/postfix >> daemon_directory = /usr/local/libexec/postfix >> header_checks = pcre:/etc/postfix/header_checks.pcre >> mail_owner = _postfix >> mailq_path = /usr/local/sbin/mailq >> manpage_directory = /usr/local/man >> message_size_limit = 27962027 >> milter_connect_macros = j {daemon_name} v _ >> milter_default_action = tempfail >> milter_header_checks = pcre:/etc/postfix/milter_header_checks >> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >> mydomain = domain1.tld >> myhostname = mail.domain1.tld >> mynetworks = 127.0.0.0/8 >> newaliases_path = /usr/bin/newaliases >> proxy_read_maps = proxy:mysql:/etc/postfix/sql/routing.cf >> proxy:mysql:/etc/postfix/sql/domains.cf >> proxy:mysql:/etc/postfix/sql/mailboxes.cf >> proxy:mysql:/etc/postfix/sql/user.cf >> proxy:mysql:/etc/postfix/sql/group.cf >> proxy:mysql:/etc/postfix/sql/forwardings.cf >> proxy:mysql:/etc/postfix/sql/email2email.cf proxy:unix:passwd.byname >> unix:passwd.byname >> queue_directory = /var/spool/postfix >> readme_directory = /usr/local/share/doc/postfix/readme >> recipient_delimiter = + >> relay_domains = proxy:mysql:/etc/postfix/sql/routing.cf >> sample_directory = /etc/postfix >> sendmail_path = /usr/local/sbin/sendmail >> setgid_group = _postdrop >> smtp_tls_cert_file = /etc/ssl/server.crt >> smtp_tls_key_file = /etc/ssl/private/server.key >> smtp_tls_security_level = may >> smtpd_delay_reject = yes >> smtpd_helo_required = yes >> smtpd_milters = unix:/tmp/clamav-milter.sock >> smtpd_recipient_restrictions = permit_mynetworks, >> permit_sasl_authenticated, reject_unauth_destination, >> reject_unauth_pipelining, reject_invalid_hostname, >> reject_unknown_sender_domain, reject_unknown_recipient_domain, >> reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_rbl_client >> zen.spamhaus.org >> smtpd_sasl_auth_enable = yes >> smtpd_sasl_local_domain = >> smtpd_sasl_security_options = noanonymous >> smtpd_tls_auth_only = yes >> smtpd_tls_cert_file = /etc/ssl/server.crt >> smtpd_tls_key_file = /etc/ssl/private/server.key >> smtpd_tls_received_header = yes >> smtpd_tls_security_level = may >> smtpd_use_tls = yes >> strict_rfc821_envelopes = yes >> transport_maps = proxy:mysql:/etc/postfix/sql/routing.cf >> unknown_local_recipient_reject_code = 550 >> virtual_alias_domains = > > > Here you want > > virtual_alias_domains = domain2.tld, domain3.tld > > >> virtual_alias_maps = proxy:mysql:/etc/postfix/sql/forwardings.cf >> proxy:mysql:/etc/postfix/sql/email2email.cf >> hash:/usr/local/mailman/data/domain1.tld > > and remove the above which may possibly fix your problem. > > >> hash:/usr/local/mailman/data/virtual-mailman >> virtual_gid_maps = proxy:mysql:/etc/postfix/sql/group.cf >> virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf >> virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mailboxes.cf >> virtual_minimum_uid = 1000 >> virtual_transport = dovecot >> virtual_uid_maps = proxy:mysql:/etc/postfix/sql/user.cf >> >> >>> >>> >>>> ----- >>>> >>> >from /usr/local/mailman/Mailman/mm_cfg.py: >>>> >>>> MTA = 'Postfix' >>>> MAILMAN_SITE_LIST = 'mailman' >>>> DEFAULT_EMAIL_HOST = 'domain1.tld' >>>> DEFAULT_URL_HOST = 'mail.domain1.tld' >>>> DEFAULT_URL_PATTERN = 'https://%s/mailman/' >>>> PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' >>>> IMAGE_LOGOS = '/icons/' >>>> POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias' >>>> POSTFIX_MAP_CMD = '/usr/local/sbin/postmap' >>>> POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ] >>>> # Clear the Defaults.py VIRTUAL_HOSTS entry >>>> VIRTUAL_HOSTS.clear() >>>> add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST') >>> >>> >>> The above is backwards. It should be >>> >>> add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') >>> >>> >>>> add_virtualhost('domain2.tld', 'domain2.tld') >>>> add_virtualhost('domain3.tld', 'domain3.tld') >>> >>> >>> However, nothing here affects delivery of mail FROM mailman. >>> >> >> OK >> >>> >>>> ----- >>>> >>>> /usr/local/mailman/data/aliases >>>> >>>> >>>> # The ultimate loop stopper address >>>> mailman-loop: /usr/local/mailman/data/owner-bounces.mbox >>>> >>>> # STANZA START: mailman >>>> # CREATED: Sat Oct 30 11:23:37 2010 >>>> 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 >>>> >>>> # STANZA START: s >>>> # CREATED: Sat Oct 30 11:35:12 2010 >>>> s: "|/usr/local/mailman/mail/mailman post s" >>>> s-admin: "|/usr/local/mailman/mail/mailman admin s" >>>> s-bounces: "|/usr/local/mailman/mail/mailman bounces s" >>>> s-confirm: "|/usr/local/mailman/mail/mailman confirm s" >>>> s-join: "|/usr/local/mailman/mail/mailman join s" >>>> s-leave: "|/usr/local/mailman/mail/mailman leave s" >>>> s-owner: "|/usr/local/mailman/mail/mailman owner s" >>>> s-request: "|/usr/local/mailman/mail/mailman request s" >>>> s-subscribe: "|/usr/local/mailman/mail/mailman subscribe s" >>>> s-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe s" >>>> # STANZA END: s >>> >>> >>> Likewise, the aliases above only affect delivery TO the mailman and s >>> lists. >> >> OK >> >>> >>> >>>> ----- >>>> >>>> /usr/local/etc/mailman/data/domain1-tld: >>>> >>>> domain1.tld IGNORE >>>> @domain1.tld @mail.domain1.tld >>> >>> >>> This file and its reference in virtual_alias_maps is conflicting as >>> this says domain1.tld is a virtual alias domain and its presence in >>> mydestination says it's not. Also, this is obsolete in Postfix. The >>> current method of specifying to postfix that a domain is a virtual >>> alias domain is to list it in virtual_alias_domains in main.cf. >> >> This came from section 6.1.2 of the Mailman docs on integration with >> postfix. This, along with the part at the top of section 6.1.1 saying to >> do this stuff first, is perhaps the most confusing part of the Mailman >> docs. If this method is obsolete in Postfix, it's time to revise these >> docs (and as a sometime tech writer I volunteer to help once I >> understand this). >> >> Just double-checking: I think you're saying to treat domain1.tld as a >> virtual alias domain. True? > > > No. I'm saying domain1.tld is not currently treated as a virtual domain > in Postfix except for the above file and its reference in > virtual_alias_maps. I think both the ile and the reference should be > removed. > > >> If so I think the changes to do this would be: >> >> 1. in main.cf, delete the myhostname and mydomain lines ((not sure these >> are strictly needed given that postfix gets these anyway from >> gethostbyname() )) >> >> 2. in main.cf, remove $mydomain from $mydestination > > > I think you should leave the above as is. > > >> 3. in main.cf, delete '/usr/local/etc/mailman/data/domain1-tld' from >> virtual_alias_maps > > > As I said above, I think you should do this. > > >>> >>> >>>> ----- >>>> >>>> /usr/local/mailman/data/virtual-mailman: >>>> >>>> # LOOP ADDRESSES START >>>> mailman-loop at domain1.tld mailman-loop >>>> # LOOP ADDRESSES END >>>> >>>> # STANZA START: s >>>> # CREATED: Sat Oct 30 11:35:12 2010 >>>> s at domain1.tld s >>>> s-admin at domain1.tld s-admin >>>> s-bounces at domain1.tld s-bounces >>>> s-confirm at domain1.tld s-confirm >>>> s-join at domain1.tld s-join >>>> s-leave at domain1.tld s-leave >>>> s-owner at domain1.tld s-owner >>>> s-request at domain1.tld s-request >>>> s-subscribe at domain1.tld s-subscribe >>>> s-unsubscribe at domain1.tld s-unsubscribe >>>> # STANZA END: s >>> >>> >>> And this virtual mapping only affects delivery to the s at domain1.tld >>> list and it's associated admin addresses, but since domain1.tld is not >>> in POSTFIX_STYLE_VIRTUAL_DOMAINS (which is correct because it is in >>> main.cf mydestination which makes it a postfix local domain), why is >>> this list in virtual-mailman at all. >> >> Clearly I'm confused as to whether domain1.tld should or should not be >> defined as a virtual domain. The Mailman docs on postfix integration say >> no, but I think you're saying to treat it as a virtual domain. > > > No, I'm saying it's not a virtual domain and should not be treated as such. > > I'm also asking how the above virtual-mailman got created with entries > for s*@domain1.tld when domain1.tld is not in > POSTFIX_STYLE_VIRTUAL_DOMAINS in the first place? > > Also, it appears you are taking > > much too literally. That section describes a complicated situation which > is not typically encountered in practice. And yes, it should probably be > heavily revised. Clarity is desirable and too rare in technical writing. I'd be glad to propose revisions to sections 6.1.1 and 6.1.2 of the docs once I understand how this should work. Thanks again for your guidance in troubleshooting. dn > From ifetch at du.edu Tue Nov 2 02:31:26 2010 From: ifetch at du.edu (Ivan Fetch) Date: Mon, 1 Nov 2010 19:31:26 -0600 Subject: [Mailman-Users] Frequent use of clone_member In-Reply-To: <878w1qlvbl.fsf@uwakimon.sk.tsukuba.ac.jp> References: <79C2D3933C76AB41B6D135F3480AC5C957C46D16@EXCH.du.edu> <878w1qlvbl.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <79C2D3933C76AB41B6D135F3480AC5C957C470E5@EXCH.du.edu> HI Stephen, -----Original Message----- From: Stephen J. Turnbull [mailto:stephen at xemacs.org] Sent: Thursday, October 21, 2010 10:13 PM To: Ivan Fetch Cc: mailman-users at python.org Subject: [Mailman-Users] Frequent use of clone_member Ivan Fetch writes: > One possibility we're exploring, is to change a student's mailing > list subscriptions, when they change their forwarding address. We > would iterate through these address changes and run clone_member, > like: > > Clone_member --remove --admin old at our.domain new at outside.domain I can't really comment on the burden on the host, but ISTM that this would be a substantial burden on the students. They would have to remember which account is their real account to make any changes, or to post. This might be non-trivial for students with multiple mailboxes. Students are changing their forward, and we would be trying to "help" them keep mailing list subscriptions pointed to that new forwarding address. We have some mailing lists which are maintained by professors - although students know they are subscribed to the course mailing list, they haven't tended to manage those subscriptions. We are leaning more toward tracking when a forwarding address changes, and sending a helpful email about mailing list memberships which may need to be changed - but not actually changing anything. How about having the forwarding address setup update accept_these_nonmembers, instead? IF we start filling accept_these_nonmembers, this separate source of addresses will need to be cleaned out - this is likely a larger overhead / bucket of hurt, than we want to create. Also, what are you going to do about the old forwarding address? It seems likely that in many cases students will want to do things like receive on their cellphone account but sometimes post from their home ISP, etc. Then they change back, creating a real muddle. OTOH, allowing dead or dormant accounts to post is a potential issue. This is one of the reasons we have begun thinking about sending an informative email, instead of changing addresses. As soon as we start taking it apon ourselves to helpfully change addresses, we will break things for subscribers who have other addresses (which happen to be an old forward) subscribed for a reason. We will still need to do mas-address changes for faculty and staff, who will be moving to MS Exchange - in some cases, they choose to begin using a different form of their email address. I would still be curious to hear from anyone who has input on running clone_member to change 200-300 addresses, as part of a nightly cron job. Thanks, Ivan. From adam-mailman at amyl.org.uk Tue Nov 2 13:33:51 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Tue, 2 Nov 2010 12:33:51 +0000 Subject: [Mailman-Users] Frequent use of clone_member In-Reply-To: <79C2D3933C76AB41B6D135F3480AC5C957C470E5@EXCH.du.edu> References: <79C2D3933C76AB41B6D135F3480AC5C957C46D16@EXCH.du.edu> <878w1qlvbl.fsf@uwakimon.sk.tsukuba.ac.jp> <79C2D3933C76AB41B6D135F3480AC5C957C470E5@EXCH.du.edu> Message-ID: <20101102123351.GK4740@hendricks.amyl.org.uk> On Mon, Nov 01, 2010 at 07:31:26PM -0600, Ivan Fetch wrote: > Ivan Fetch writes: > > > One possibility we're exploring, is to change a student's mailing > > list subscriptions, when they change their forwarding address. We > > would iterate through these address changes and run clone_member, > > like: > > > > Clone_member --remove --admin old at our.domain new at outside.domain > > I can't really comment on the burden on the host, but ISTM that this > would be a substantial burden on the students. They would have to > remember which account is their real account to make any changes, or > to post. This might be non-trivial for students with multiple > mailboxes. > Students are changing their forward, and we would be trying to > "help" them keep mailing list subscriptions pointed to that new > forwarding address. Is this not looking for a technical solution to a social one? (It was the case that both times I was at college (Federal Universities), that my college/university provided address was defined as a contact address, and it was *my* responsibility to ensure I picked up mails sent to that address). > We are leaning more toward tracking when a forwarding address > changes, and sending a helpful email about mailing list memberships > which may need to be changed - but not actually changing anything. How do you manage forwarding, currently? If your email setup uses a database, how about adding (for example) (a) a timestamp, (b) a change-log (the previous value), (c) current value to that, and using the timestamp to calculate if anything needs to be done (and to whom), and then using the values of (b) and (c), to update your lists? (presumably, using something like find_member, and then clone_member or non_members [1]) [1] http://www.msapiro.net/scripts/non_members > How about having the forwarding address setup update > accept_these_nonmembers, instead? > IF we start filling accept_these_nonmembers, this separate source of addresses will need to be cleaned out - this is likely a larger overhead / bucket of hurt, than we want to create. Or you can purge the old addresses, too. Or maybe even go down the sibling list approach, and have foo-acadaemia at lists.example.edu foo-forwarding at lists.example.edu where "official" (institution provided) addresses are always subscribed, and leave -forwarding to be built/manipulated by scripts? (and foo-forwarding to obviously receive foo-acadaemia mails). > Also, what are you going to do about the old forwarding address? It > seems likely that in many cases students will want to do things like > receive on their cellphone account but sometimes post from their home > ISP, etc. Then they change back, creating a real muddle. OTOH, > allowing dead or dormant accounts to post is a potential issue. If there's a time-stamp (or flag, or whatever) included, that's something that could be checked against, and appropriate action (not) taken. > This is one of the reasons we have begun thinking about sending an > informative email, instead of changing addresses. As soon as we start > taking it apon ourselves to helpfully change addresses, we will break > things for subscribers who have other addresses (which happen to be an > old forward) subscribed for a reason. Tricky business. Informative mails will presumably need to include find_member output, or something like that. That said, it pushes the responsibilites over to the user: surely a good thing (assuming they get the mail, and it's not "helpfully" spam-classified by their (web)mail provider. > We will still need to do mas-address changes for faculty and staff, who will be moving to MS Exchange - in some cases, they choose to begin using a different form of their email address. I would still be curious to hear from anyone who has input on running clone_member to change 200-300 addresses, as part of a nightly cron job. find_member accepts regexps. There are a few examples of how to change this sort of thing. You might find my quick-and-dirty googlemail->gmail script [2] something to work from. You might find creagting that request as a new thread might garner more responses. [2] http://blog.amyl.org.uk/2010/06/mailman-googlemail-to-gmail/ (step 2 could trivially be done progmatically) -- "There seems to be something wrong with our bloody ships today" -- David, Vice-Admiral Beatty (re: the Battle of the Jutland) From mark at msapiro.net Tue Nov 2 16:13:58 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 2 Nov 2010 08:13:58 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: <4CCF0FCD.6080200@networktest.com> Message-ID: David Newman wrote: >On 10/31/10 10:22 PM, Mark Sapiro wrote: >> On 10/31/10 4:56 PM, David Newman wrote: >>> On 10/31/10 9:09 AM, Mark Sapiro wrote: >>>> >>>> [...] > >Here's a log snapshot of a message sent to s at domain1.tld, a Mailman list >with subscribers 'dnewman at networktest.com' and 'dnewman at domain1.tld'. > >This is after removing 'hash:/usr/local/mailman/data/domain1-tld' from >virtual_alias_maps as you suggested and reloading Mailman and postfix. > >I'm embedded one comment and one question: > >Nov 1 11:51:29 mail postfix/postfix-script[5384]: refreshing the >Postfix mail system >Nov 1 11:51:29 mail postfix/master[19348]: reload -- version 2.6.5, >configuration /etc/postfix >Nov 1 11:51:59 mail postfix/smtpd[32434]: connect from >mail3.networktest.com[69.55.234.104] >Nov 1 11:51:59 mail postfix/trivial-rewrite[29411]: warning: do not >list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains > >This is a possible clue. I think postfix is set up so that domain1.tld >*is* a virtual domain. The server -- Mailserver, an email server >appliance from Allard Software -- stores domain info in a SQL database >and postfix calls that database here: > >virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf Right. domain1.tld is defined to be a local domain because it is (indirectly) in mydestination. It is also in virtual_mailbox_domains and Postfix wants it to be in one or the other (either local or virtual) not both. Note that if you remove it from mydestination and make it strictly a virtual_mailbox_domain, delivery TO s at domain1.com will stop working. See the FAQ at . >Anyway, carrying on: > >Nov 1 11:51:59 mail postfix/smtpd[32434]: A91E1130CB: >client=mail3.networktest.com[69.55.234.104] >Nov 1 11:51:59 mail postfix/cleanup[25359]: A91E1130CB: >message-id=<4CCF0C4E.8000704 at networktest.com> >Nov 1 11:51:59 mail postfix/smtpd[32434]: disconnect from >mail3.networktest.com[69.55.234.104] >Nov 1 11:51:59 mail postfix/qmgr[20853]: A91E1130CB: >from=, size=1495, nrcpt=1 (queue active) >Nov 1 11:51:59 mail spamd[10619]: spamd: connection from localhost >[127.0.0.1] at port 45013 >Nov 1 11:51:59 mail spamd[10619]: spamd: processing message ><4CCF0C4E.8000704 at networktest.com> for s at mail.domain1.tld:62 >Nov 1 11:52:00 mail spamd[10619]: spamd: clean message (-0.0/5.0) for >s at mail.domain1.tld:62 in 1.1 seconds, 1467 bytes. >Nov 1 11:52:00 mail spamd[10619]: spamd: result: . 0 - >T_RP_MATCHES_RCVD >scantime=1.1,size=1467,user=s at mail.domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=45013,mid=<4CCF0C4E.8000704 at networktest.com>,autolearn=ham > >Nov 1 11:52:01 mail postfix/pickup[1233]: 03422130CD: uid=506 >from= >Nov 1 11:52:01 mail postfix/pipe[16800]: A91E1130CB: >to=, orig_to=, relay=spamassassin, >delay=1.6, delays=0.33/0.02/0/1.2, dsn=2.0.0, status=sent (delivered via >spamassassin service) >Nov 1 11:52:01 mail postfix/qmgr[20853]: A91E1130CB: removed These (A91E1130CB) messages are the receipt if the mail from dnewman at networktest.com to s at domain1.com and its delivery to spamassassin. >Nov 1 11:52:01 mail postfix/cleanup[25359]: 03422130CD: >message-id=<4CCF0C4E.8000704 at networktest.com> >Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: >from=, size=1762, nrcpt=1 (queue active) >Nov 1 11:52:01 mail spamd[18056]: prefork: child states: II >Nov 1 11:52:01 mail postfix/local[28131]: 03422130CD: >to=, relay=local, delay=0.32, >delays=0.03/0.02/0/0.26, dsn=2.0.0, status=sent (delivered to command: >/usr/local/mailman/mail/mailman post s) >Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: removed And these (03422130CD) are the mail being requeued after spamassassin and delivered vi the local alias to Mailman. >Nov 1 11:52:02 mail postfix/smtpd[32434]: connect from localhost[127.0.0.1] >Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not >list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains >Nov 1 11:52:02 mail postfix/smtpd[32434]: 80A72130CB: >client=localhost[127.0.0.1] >Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not >list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains >Nov 1 11:52:02 mail postfix/cleanup[25359]: 80A72130CB: >message-id=<4CCF0C4E.8000704 at networktest.com> >Nov 1 11:52:02 mail postfix/smtpd[32434]: disconnect from >localhost[127.0.0.1] >Nov 1 11:52:02 mail postfix/qmgr[20853]: 80A72130CB: >from=, size=2697, nrcpt=2 (queue active) >Nov 1 11:52:02 mail spamd[10619]: spamd: connection from localhost >[127.0.0.1] at port 5435 >Nov 1 11:52:02 mail spamd[10619]: spamd: processing message ><4CCF0C4E.8000704 at networktest.com> for dnewman at domain1.tld:62 >Nov 1 11:52:07 mail spamd[10619]: spamd: clean message (0.0/5.0) for >dnewman at domain1.tld:62 in 4.8 seconds, 2638 bytes. >Nov 1 11:52:07 mail spamd[10619]: spamd: result: . 0 - >scantime=4.8,size=2638,user=dnewman at domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=5435,mid=<4CCF0C4E.8000704 at networktest.com>,autolearn=ham > >Nov 1 11:52:07 mail postfix/pickup[1233]: 7027A130CD: uid=506 >from= >Nov 1 11:52:07 mail postfix/cleanup[25359]: 7027A130CD: >message-id=<4CCF0C4E.8000704 at networktest.com> >Nov 1 11:52:07 mail postfix/pipe[16800]: 80A72130CB: >to=, relay=spamassassin, delay=4.9, >delays=0.04/0/0/4.9, dsn=2.0.0, status=sent (delivered via spamassassin >service) >Nov 1 11:52:07 mail postfix/pipe[16800]: 80A72130CB: >to=, relay=spamassassin, delay=4.9, >delays=0.04/0/0/4.9, dsn=2.0.0, status=sent (delivered via spamassassin >service) > > >I don't understand this entry. Since 's at domain1.tld' never received the >message, and since postfix says it was delivered OK, and since there's >no indication of trouble in the Mailman logs, what happened to the message? > > >Nov 1 11:52:07 mail postfix/qmgr[20853]: 80A72130CB: removed >Nov 1 11:52:07 mail postfix/qmgr[20853]: 7027A130CD: >from=, size=2759, nrcpt=1 (queue active) >Nov 1 11:52:07 mail spamd[18056]: prefork: child states: II >Nov 1 11:52:11 mail postfix/smtp[7413]: 7027A130CD: >to=, >relay=mail3.networktest.com[69.55.234.104]:25, delay=3.6, >delays=0.03/0.04/0.39/3.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued >as EC0D3256A73) >Nov 1 11:52:11 mail postfix/qmgr[20853]: 7027A130CD: removed There are two message deliveries above. 80A72130CB is the delivery of the message from mailman with two recipients, dnewman at domain1.tld and dnewman at networktest.com, and was processed through spamassassin (there are spamd reports) and the two entries immediately prior to your last comment above say that Postfix's pipe delivery piped the message to spamassassin for both recipients. Then, 7027A130CD is the requeue from spamassassin of the message to dnewman at networktest.com which was then delivered via SMTP to the MTA at mail3.networktest.com. But, there is apparently no requeue from spamassassin of the message to the dnewman at domain1.tld recipient. My guess is that your spamassassin process doesn't properly handle messages with multiple recipients. There are two things you could try. You could set SMTP_MAX_RCPTS = 1 in mm_cfg.py to tell Mailman to deliver each recipient as a separate message. Or, probably better, you could put spamassassin_destination_recipient_limit = 1 in main.cf to cause Postfix to pipe only one recipient at a time to the spamassassin handler (see man 8 pipe). [...] >> Also, it appears you are taking >> >> much too literally. That section describes a complicated situation which >> is not typically encountered in practice. And yes, it should probably be >> heavily revised. > >Clarity is desirable and too rare in technical writing. I'd be glad to >propose revisions to sections 6.1.1 and 6.1.2 of the docs once I >understand how this should work. Thank you. I'd appreciate that. However, it now seems to me that you actually had the Mailman part of Postfix reasonably OK at the outset. The real issue now appears to me the use and configuration of spamassassin filtering in Postfix. Also note, You are doing way too much spamassassin scanning. You are scanning the inbound message before delivering it to Mailman, and then you are scanning the message again on its way from Mailman to the recipients. It might be better to set up a separate listener in Postfix on a different port and have Mailman deliver there and in Postfix only accept mail from Mailman (or localhost) on that port and bypass spamassassin for that mail. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dnewman at networktest.com Wed Nov 3 19:03:36 2010 From: dnewman at networktest.com (David Newman) Date: Wed, 03 Nov 2010 11:03:36 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: References: Message-ID: <4CD1A3F8.3050008@networktest.com> On 11/2/10 8:13 AM, Mark Sapiro wrote: > David Newman wrote: > >> On 10/31/10 10:22 PM, Mark Sapiro wrote: >>> On 10/31/10 4:56 PM, David Newman wrote: >>>> On 10/31/10 9:09 AM, Mark Sapiro wrote: >>>>> >>>>> [...] >> >> Here's a log snapshot of a message sent to s at domain1.tld, a Mailman list >> with subscribers 'dnewman at networktest.com' and 'dnewman at domain1.tld'. >> >> This is after removing 'hash:/usr/local/mailman/data/domain1-tld' from >> virtual_alias_maps as you suggested and reloading Mailman and postfix. >> >> I'm embedded one comment and one question: >> >> Nov 1 11:51:29 mail postfix/postfix-script[5384]: refreshing the >> Postfix mail system >> Nov 1 11:51:29 mail postfix/master[19348]: reload -- version 2.6.5, >> configuration /etc/postfix >> Nov 1 11:51:59 mail postfix/smtpd[32434]: connect from >> mail3.networktest.com[69.55.234.104] >> Nov 1 11:51:59 mail postfix/trivial-rewrite[29411]: warning: do not >> list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains >> >> This is a possible clue. I think postfix is set up so that domain1.tld >> *is* a virtual domain. The server -- Mailserver, an email server >> appliance from Allard Software -- stores domain info in a SQL database >> and postfix calls that database here: >> >> virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf > > > Right. domain1.tld is defined to be a local domain because it is > (indirectly) in mydestination. It is also in virtual_mailbox_domains > and Postfix wants it to be in one or the other (either local or > virtual) not both. > > Note that if you remove it from mydestination and make it strictly a > virtual_mailbox_domain, delivery TO s at domain1.com will stop working. > See the FAQ at . > > >> Anyway, carrying on: >> >> Nov 1 11:51:59 mail postfix/smtpd[32434]: A91E1130CB: >> client=mail3.networktest.com[69.55.234.104] >> Nov 1 11:51:59 mail postfix/cleanup[25359]: A91E1130CB: >> message-id=<4CCF0C4E.8000704 at networktest.com> >> Nov 1 11:51:59 mail postfix/smtpd[32434]: disconnect from >> mail3.networktest.com[69.55.234.104] >> Nov 1 11:51:59 mail postfix/qmgr[20853]: A91E1130CB: >> from=, size=1495, nrcpt=1 (queue active) >> Nov 1 11:51:59 mail spamd[10619]: spamd: connection from localhost >> [127.0.0.1] at port 45013 >> Nov 1 11:51:59 mail spamd[10619]: spamd: processing message >> <4CCF0C4E.8000704 at networktest.com> for s at mail.domain1.tld:62 >> Nov 1 11:52:00 mail spamd[10619]: spamd: clean message (-0.0/5.0) for >> s at mail.domain1.tld:62 in 1.1 seconds, 1467 bytes. >> Nov 1 11:52:00 mail spamd[10619]: spamd: result: . 0 - >> T_RP_MATCHES_RCVD >> scantime=1.1,size=1467,user=s at mail.domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=45013,mid=<4CCF0C4E.8000704 at networktest.com>,autolearn=ham >> >> Nov 1 11:52:01 mail postfix/pickup[1233]: 03422130CD: uid=506 >> from= >> Nov 1 11:52:01 mail postfix/pipe[16800]: A91E1130CB: >> to=, orig_to=, relay=spamassassin, >> delay=1.6, delays=0.33/0.02/0/1.2, dsn=2.0.0, status=sent (delivered via >> spamassassin service) >> Nov 1 11:52:01 mail postfix/qmgr[20853]: A91E1130CB: removed > > > These (A91E1130CB) messages are the receipt if the mail from > dnewman at networktest.com to s at domain1.com and its delivery to > spamassassin. > > >> Nov 1 11:52:01 mail postfix/cleanup[25359]: 03422130CD: >> message-id=<4CCF0C4E.8000704 at networktest.com> >> Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: >> from=, size=1762, nrcpt=1 (queue active) >> Nov 1 11:52:01 mail spamd[18056]: prefork: child states: II >> Nov 1 11:52:01 mail postfix/local[28131]: 03422130CD: >> to=, relay=local, delay=0.32, >> delays=0.03/0.02/0/0.26, dsn=2.0.0, status=sent (delivered to command: >> /usr/local/mailman/mail/mailman post s) >> Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: removed > > > And these (03422130CD) are the mail being requeued after spamassassin > and delivered vi the local alias to Mailman. > > >> Nov 1 11:52:02 mail postfix/smtpd[32434]: connect from localhost[127.0.0.1] >> Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not >> list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains >> Nov 1 11:52:02 mail postfix/smtpd[32434]: 80A72130CB: >> client=localhost[127.0.0.1] >> Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not >> list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains >> Nov 1 11:52:02 mail postfix/cleanup[25359]: 80A72130CB: >> message-id=<4CCF0C4E.8000704 at networktest.com> >> Nov 1 11:52:02 mail postfix/smtpd[32434]: disconnect from >> localhost[127.0.0.1] >> Nov 1 11:52:02 mail postfix/qmgr[20853]: 80A72130CB: >> from=, size=2697, nrcpt=2 (queue active) >> Nov 1 11:52:02 mail spamd[10619]: spamd: connection from localhost >> [127.0.0.1] at port 5435 >> Nov 1 11:52:02 mail spamd[10619]: spamd: processing message >> <4CCF0C4E.8000704 at networktest.com> for dnewman at domain1.tld:62 >> Nov 1 11:52:07 mail spamd[10619]: spamd: clean message (0.0/5.0) for >> dnewman at domain1.tld:62 in 4.8 seconds, 2638 bytes. >> Nov 1 11:52:07 mail spamd[10619]: spamd: result: . 0 - >> scantime=4.8,size=2638,user=dnewman at domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=5435,mid=<4CCF0C4E.8000704 at networktest.com>,autolearn=ham >> >> Nov 1 11:52:07 mail postfix/pickup[1233]: 7027A130CD: uid=506 >> from= >> Nov 1 11:52:07 mail postfix/cleanup[25359]: 7027A130CD: >> message-id=<4CCF0C4E.8000704 at networktest.com> >> Nov 1 11:52:07 mail postfix/pipe[16800]: 80A72130CB: >> to=, relay=spamassassin, delay=4.9, >> delays=0.04/0/0/4.9, dsn=2.0.0, status=sent (delivered via spamassassin >> service) >> Nov 1 11:52:07 mail postfix/pipe[16800]: 80A72130CB: >> to=, relay=spamassassin, delay=4.9, >> delays=0.04/0/0/4.9, dsn=2.0.0, status=sent (delivered via spamassassin >> service) >> >> >> I don't understand this entry. Since 's at domain1.tld' never received the >> message, and since postfix says it was delivered OK, and since there's >> no indication of trouble in the Mailman logs, what happened to the message? >> >> >> Nov 1 11:52:07 mail postfix/qmgr[20853]: 80A72130CB: removed >> Nov 1 11:52:07 mail postfix/qmgr[20853]: 7027A130CD: >> from=, size=2759, nrcpt=1 (queue active) >> Nov 1 11:52:07 mail spamd[18056]: prefork: child states: II >> Nov 1 11:52:11 mail postfix/smtp[7413]: 7027A130CD: >> to=, >> relay=mail3.networktest.com[69.55.234.104]:25, delay=3.6, >> delays=0.03/0.04/0.39/3.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued >> as EC0D3256A73) >> Nov 1 11:52:11 mail postfix/qmgr[20853]: 7027A130CD: removed > > > There are two message deliveries above. > > 80A72130CB is the delivery of the message from mailman with two > recipients, dnewman at domain1.tld and dnewman at networktest.com, and was > processed through spamassassin (there are spamd reports) and the two > entries immediately prior to your last comment above say that > Postfix's pipe delivery piped the message to spamassassin for both > recipients. > > Then, 7027A130CD is the requeue from spamassassin of the message to > dnewman at networktest.com which was then delivered via SMTP to the MTA > at mail3.networktest.com. > > But, there is apparently no requeue from spamassassin of the message to > the dnewman at domain1.tld recipient. > > My guess is that your spamassassin process doesn't properly handle > messages with multiple recipients. > > There are two things you could try. You could set > > SMTP_MAX_RCPTS = 1 > > in mm_cfg.py to tell Mailman to deliver each recipient as a separate > message. > > Or, probably better, you could put > > spamassassin_destination_recipient_limit = 1 > > in main.cf to cause Postfix to pipe only one recipient at a time to the > spamassassin handler (see man 8 pipe). Bingo. Your guess is correct. That one-line addition to main.cf now allows Mailman message delivery to domain1.tld. > > [...] >>> Also, it appears you are taking >>> >>> much too literally. That section describes a complicated situation which >>> is not typically encountered in practice. And yes, it should probably be >>> heavily revised. >> >> Clarity is desirable and too rare in technical writing. I'd be glad to >> propose revisions to sections 6.1.1 and 6.1.2 of the docs once I >> understand how this should work. > > > Thank you. I'd appreciate that. I'd be glad to write this up now that it's working. To whom should I send a draft of the changes? > > However, it now seems to me that you actually had the Mailman part of > Postfix reasonably OK at the outset. The real issue now appears to me > the use and configuration of spamassassin filtering in Postfix. Agreed. With your help, I did make some changes from the Mailman docs, for example removing a separate hash of domain1.tld from virtual_alias_maps. > > Also note, You are doing way too much spamassassin scanning. You are > scanning the inbound message before delivering it to Mailman, and then > you are scanning the message again on its way from Mailman to the > recipients. It might be better to set up a separate listener in > Postfix on a different port and have Mailman deliver there and in > Postfix only accept mail from Mailman (or localhost) on that port and > bypass spamassassin for that mail. OK, thanks. Setting up a separate listener in Postfix via master.cf is no problem for me, but how would I configure Mailman to deliver to that port? thanks again dn > From andrevk at nikhef.nl Wed Nov 3 17:55:29 2010 From: andrevk at nikhef.nl (=?ISO-8859-1?Q?Andr=E9_van_Kan?=) Date: Wed, 03 Nov 2010 17:55:29 +0100 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <4CCB98D9.8030605@msapiro.net> References: <4CCAE41D.2010305@nikhef.nl> <4CCB98D9.8030605@msapiro.net> Message-ID: <4CD19401.10001@nikhef.nl> Hi Mark, Thank you for your reply. > Please post to the list, not to me personally. Point taken. And sure, you are Mark, not Larry, sorry ;-) > However, the above messages, presumably from Mailman's vette log, come > from two different PIDs. Thus, I'm guessing that you are approving these > messages via the admindb web interface, and something is going wrong in > that process resulting in the message being discarded by the admindb CGI > itself. That is right, these are vette-log entries and the approving attempt is done via the admindb web interface. I found out that as soon as the list-administrator just selects the link in the ".... requires approval" message as sent by mailman, ("Reason: Post by non-member to a members-only list") the message is discarded at that very moment! (vette log update detected) After that the following is displayed: |Action to take on all these held messages: |Defer Accept Reject Discard but *no* pending message is there to Accept. > Have you modified admindb.py in any way? No! > Does the web admin interface work? Except for the murdering of pending messages the interface works flawlessly. > What Mailman version is this? mailman-2.1.9-4.el5 (RPM) > How exactly are you approving messages? As said before: by selecting the link in the mailman-sent message. Best regards and thank you for your help, Andr? van Kan ------------------------------------------------------- * Computer Technology Group * Nikhef, Amsterdam * ------------------------------------------------------- From carl at transitionus.org Wed Nov 3 20:11:29 2010 From: carl at transitionus.org (Carl Shuller) Date: Wed, 3 Nov 2010 12:11:29 -0700 Subject: [Mailman-Users] Message text not showing up in digests or archives - Skipped content of type multipart/alternative Message-ID: A sporadic number of messages in digest and archives are showing up with out the original message text and instead "Skipped content of type multipart/alternative" is showing up. I did a search and found a few others had experienced this problem some years ago but there wasn't any real follow up to the original posts, none that were helpful anyway. I was hoping folks on this list might have some insights. Thanks so much. Carl From mark at msapiro.net Thu Nov 4 00:47:00 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 3 Nov 2010 16:47:00 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <4CD19401.10001@nikhef.nl> Message-ID: Andr? van Kan wrote: > >I found out that as soon as the list-administrator just selects the link in >the ".... requires approval" message as sent by mailman, ("Reason: Post >by non-member to a members-only list") the message is discarded at that >very moment! (vette log update detected) > >After that the following is displayed: > |Action to take on all these held messages: > |Defer Accept Reject Discard > >but *no* pending message is there to Accept. This is very unusual. Is there an http proxy server involved here? Can you send me off list a copy of Mailman/Cgi/admindb.py from your system? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 4 02:11:59 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 3 Nov 2010 18:11:59 -0700 Subject: [Mailman-Users] Message text not showing up in digests or archives- Skipped content of type multipart/alternative In-Reply-To: Message-ID: Carl Shuller wrote: >A sporadic number of messages in digest and archives are showing up with out >the original message text and instead "Skipped content of type >multipart/alternative" is showing up. This Scrubber issue was fixed I think in Mailman 2.1.6, The current version is 2.1.14. Perhaps it's time to upgrade. If you can't upgrade, and if you provide your Mailman version, I can probably provide a patch. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dandrews at visi.com Thu Nov 4 02:23:23 2010 From: dandrews at visi.com (David Andrews) Date: Wed, 03 Nov 2010 20:23:23 -0500 Subject: [Mailman-Users] What Causes Random Unsubscribe Notices Message-ID: I run mailman with about 175 lists, and 6000 users, many of whom belong to multiple lists. I have personalized e-mail set to yes, and the following in the footer which produces a personal options link for the user in each message: To unsubscribe, change your list options or get your account info for %(real_name)s: %(user_optionsurl)s Several times a week I get mail from a user saying they got an unsubscribe confirmation message and hadn't done anything to trigger it. I believe them because I have gotten some too. This behavior seems to have started when I started adding personalized footers. Is it somehow caused by the long string of personalized links left in messages when people reply and don't trim off bottom. Some of these message chains can get pretty long. Or, is there something else that causes the generation of seemingly random unsubscribe confirmation messages? Dave David Andrews: dandrews at visi.com Follow me on Twitter: http://www.twitter.com/dandrews920 From mark at msapiro.net Thu Nov 4 02:41:56 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 3 Nov 2010 18:41:56 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: <4CD1A3F8.3050008@networktest.com> Message-ID: David Newman wrote: >On 11/2/10 8:13 AM, Mark Sapiro wrote: >> >> Or, probably better, you could put >> >> spamassassin_destination_recipient_limit = 1 >> >> in main.cf to cause Postfix to pipe only one recipient at a time to the >> spamassassin handler (see man 8 pipe). > >Bingo. Your guess is correct. That one-line addition to main.cf now >allows Mailman message delivery to domain1.tld. Actually, I think the domain1.tld non-delivery was a red herring. I think the real issue is that a post to a list with fewer than SMTP_MAX_RCPTS (default 500) members would be delivered to only one member. >I'd be glad to write this up now that it's working. To whom should I >send a draft of the changes? You can send them off list to me. >> Also note, You are doing way too much spamassassin scanning. You are >> scanning the inbound message before delivering it to Mailman, and then >> you are scanning the message again on its way from Mailman to the >> recipients. It might be better to set up a separate listener in >> Postfix on a different port and have Mailman deliver there and in >> Postfix only accept mail from Mailman (or localhost) on that port and >> bypass spamassassin for that mail. > >OK, thanks. Setting up a separate listener in Postfix via master.cf is >no problem for me, but how would I configure Mailman to deliver to that >port? Set SMTPPORT in mm_cfg.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 4 02:48:51 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 3 Nov 2010 18:48:51 -0700 Subject: [Mailman-Users] What Causes Random Unsubscribe Notices In-Reply-To: Message-ID: David Andrews wrote: >I run mailman with about 175 lists, and 6000 users, many of whom >belong to multiple lists. I have personalized e-mail set to yes, and >the following in the footer which produces a personal options link >for the user in each message: > >To unsubscribe, change your list options or get your account info for >%(real_name)s: >%(user_optionsurl)s > >Several times a week I get mail from a user saying they got an >unsubscribe confirmation message and hadn't done anything to trigger >it. I believe them because I have gotten some too. This behavior >seems to have started when I started adding personalized footers. Is >it somehow caused by the long string of personalized links left in >messages when people reply and don't trim off bottom. Some of these >message chains can get pretty long. It is almost certainly this. >Or, is there something else that causes the generation of seemingly >random unsubscribe confirmation messages? Or maybe the member forwarding an "interesting" list post to someone else who thinks the forward came from a list and wants to unsubscribe. In any case, it is caused by a third party receiving a message with the member's unsubscribe link and following the link. Members can avoid this by always removing the footer from any list post they reply to or forward, or if they can't be bothered to do that, they can just ignore the unsubscribe confirmations they will inevitably receive. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 4 15:12:11 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 04 Nov 2010 07:12:11 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: References: Message-ID: <4CD2BF3B.8040708@msapiro.net> Mark Sapiro wrote: > Can you send me off list a copy of Mailman/Cgi/admindb.py from your > system? I received that. Thank you. Unfortunately, there's nothing there that helps explain this issue. I can work up a patch to provide debug logging, but before I do that, is there anything in Mailman's 'error' log from either the time of the visit to the admindb page or from the time the held post arrived? If so, what's in the error log. If not, is it possible that some non-mailman process has removed any of Mailman's data/heldmsg* files between the holding of the post and the visit to the admindb page? Also, it wouldn't hurt to run Mailman's bin/check_perms to see if there might be permission issues on Mailman's data/ directory. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 4 19:06:04 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 4 Nov 2010 11:06:04 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <1288892922.2042.18.camel@sloeber> Message-ID: Andre van Kan wrote: > >On Thu, 2010-11-04 at 07:12 -0700, Mark Sapiro wrote: >> Mark Sapiro wrote: >> >> > Can you send me off list a copy of Mailman/Cgi/admindb.py from your >> > system? >> >> I received that. Thank you. Unfortunately, there's nothing there that >> helps explain this issue. I can work up a patch to provide debug >> logging, but before I do that, is there anything in Mailman's 'error' >> log from either the time of the visit to the admindb page or from the >> time the held post arrived? > >Not a single entry in any of the log files. > > >> If so, what's in the error log. If not, is >> it possible that some non-mailman process has removed any of Mailman's >> data/heldmsg* files between the holding of the post and the visit to the >> admindb page? > >I don't think so. The message is removed at the >very moment that the link in Mailman's notification >message is activated. I understand that, but the data/heldmsg* file could have been removed external to Mailman before that. >> Also, it wouldn't hurt to run Mailman's bin/check_perms to see if there >> might be permission issues on Mailman's data/ directory. > >See attachment. Mail restarted, just in case ... >I sent a message to the list. Unfortunately there was no message >waiting for me to be accepted and NO entry was in vette. >I think that it would be great if the logging became a bit >more verbose. Thanks in advance. The attached admindb.patch.txt file contains a patch that will log more information to Mailman's 'debug' log. Try applying the patch and then the next time the problem occurs, post the log - note the log may contain passwords; be careful to remove them before posting. -- 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: admindb.patch.txt URL: From andrevk at nikhef.nl Fri Nov 5 14:44:10 2010 From: andrevk at nikhef.nl (=?ISO-8859-1?Q?Andr=E9_van_Kan?=) Date: Fri, 05 Nov 2010 14:44:10 +0100 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: References: Message-ID: <4CD40A2A.9070809@nikhef.nl> > I understand that, but the data/heldmsg* file could have been removed > > external to Mailman before that. I never found any heldmsg* on the system, nor any complaint that such a file could not be written. Maybe could an strace of the appropriate qrunner be of some help? > > The attached admindb.patch.txt file contains a patch that will log more > > information to Mailman's 'debug' log. See attachment. Best regards, Andr? van Kan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: debug URL: From mark at msapiro.net Fri Nov 5 15:48:10 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 05 Nov 2010 07:48:10 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <4CD40A2A.9070809@nikhef.nl> References: <4CD40A2A.9070809@nikhef.nl> Message-ID: <4CD4192A.70707@msapiro.net> On 11/5/2010 6:44 AM, Andr? van Kan wrote: > >> I understand that, but the data/heldmsg* file could have been removed >>> external to Mailman before that. > > I never found any heldmsg* on the system, nor any complaint > that such a file could not be written. Maybe could an strace of > the appropriate qrunner be of some help? > >>> The attached admindb.patch.txt file contains a patch that will log more >>> information to Mailman's 'debug' log. > > See attachment. This excerpt from your log shows one interaction with the admindb interface. > Nov 05 13:20:14 2010 (7482) cgidata = FieldStorage(None, None, []) The above is logged at the beginning of the interaction and says there was no POST data which is expected. > Nov 05 13:20:14 2010 (7482) heldmsg file non-existent, info = (1288958492.854609, 'acvankan at gmail.com', 'test na patch', 'Post by non-member to a members-only list', 'heldmsg-groep3-18.pck', {'lang': 'en', 'listname': 'groep3', 'received_time': 1288958491.90411, '_parsemsg': True, 'tolist': 1, 'pipeline': ['Hold', 'MimeDel', 'Scrubber', 'Emergency', 'Tagger', 'CalcRecips', 'AvoidDuplicates', 'Cleanse', 'CleanseDKIM', 'CookHeaders', 'ToDigest', 'ToArchive', 'ToUsenet', 'AfterDelivery', 'Acknowledge', 'ToOutgoing'], 'version': 3, 'rejection_notice': 'Non-members are not allowed to post messages to this list.'}) > Nov 05 13:20:14 2010 (7482) heldmsg file non-existent, info = (1288958518.006875, 'acvankan at gmail.com', 'test na patch', 'Post by non-member to a members-only list', 'heldmsg-groep3-19.pck', {'lang': 'en', 'listname': 'groep3', 'received_time': 1288958517.782223, '_parsemsg': True, 'tolist': 1, 'pipeline': ['Hold', 'MimeDel', 'Scrubber', 'Emergency', 'Tagger', 'CalcRecips', 'AvoidDuplicates', 'Cleanse', 'CleanseDKIM', 'CookHeaders', 'ToDigest', 'ToArchive', 'ToUsenet', 'AfterDelivery', 'Acknowledge', 'ToOutgoing'], 'version': 3, 'rejection_notice': 'Non-members are not allowed to post messages to this list.'}) Then these two say that there were two held messages, both held as non-member posts to the groep3 list, and in this case, both posted from the same address with subject 'test na patch', The first was received at Fri Nov 5 13:01:31 2010 +0100 and held at Fri Nov 5 13:01:32 2010 +0100. At the time it was held, the message itself should have been saved in Mailman's data/ directory in a file named 'heldmsg-groep3-18.pck'. Likewise, the second was received at Fri Nov 5 13:01:57 2010 +0100 and held at Fri Nov 5 13:01:58 2010 +0100, and the time it was held, the message itself should have been saved in Mailman's data/ directory in a file named 'heldmsg-groep3-19.pck'. The problem is that when the admindb interface CGI attempted to retrieve these message files at Nov 05 13:20:14 2010, the OS said the two files didn't exist. At that point, admindb.py logged the two messages and "discarded" the post in order to clean up the list's request database. This is what caused the vette log entries for these posts, but the real issue is that the posts had already been lost or possibly (highly unlikely) that the OS said the files didn't exist even though they did. So, either the OS lied (unlikely), or the files were removed from Mailman's data/ directory sometime in the 19 or so minutes between the time they were created and the time the admindb.py script ran, or for some reason they weren't successfully created in the first place. I actually think this latter explanation is the most likely, except that this should have resulted in an exception and error log entries at the time the post was held, and this exception should have occurred before the request database was written, so the end result would be that the post was logged and shunted and not held at all. So assuming the OS works this seems to say that either the files were removed in that 19 minute window, or possibly there are two Mailman installations, one used by mailmanctl and the qrunners and one used by the web interface and these two installations both point to the same lists/ directory, but different data/ directories so the the heldmsg-* files are created by IncomingRunner in one directory and looked for by admindb.py in a different directory. Again, this doesn't seem likely. You could look for a data/heldmsg* file immediately after sending a post from a non-member and before going to the admindb interface, or you could strace IncomingRunner when it is processing a non-member post and see if it writes the file. You could also try patching Mailman/ListAdmin.py by finding these lines try: fp = open(os.path.join(mm_cfg.DATA_DIR, filename), 'w') try: if mm_cfg.HOLD_MESSAGES_AS_PICKLES: cPickle.dump(msg, fp, 1) else: g = Generator(fp) g.flatten(msg, 1) fp.flush() os.fsync(fp.fileno()) finally: fp.close() finally: os.umask(omask) in the definition of the HoldMessage method and adding the lines syslog('debug', 'HoldMessage: %s written to %s', filename, mm_cfg.DATA_DIR) to make it try: fp = open(os.path.join(mm_cfg.DATA_DIR, filename), 'w') try: if mm_cfg.HOLD_MESSAGES_AS_PICKLES: cPickle.dump(msg, fp, 1) else: g = Generator(fp) g.flatten(msg, 1) fp.flush() os.fsync(fp.fileno()) syslog('debug', 'HoldMessage: %s written to %s', filename, mm_cfg.DATA_DIR) finally: fp.close() finally: os.umask(omask) This will write an entry to the debug log confirming that the file was written. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From CNulk at scu.edu Wed Nov 10 00:37:02 2010 From: CNulk at scu.edu (C Nulk) Date: Tue, 09 Nov 2010 15:37:02 -0800 Subject: [Mailman-Users] Email command to find out what lists I am on Message-ID: <4CD9DB1E.1020908@scu.edu> Hello all, I searched through the documentation and the archives but I was unable to find what I was looking for. Is there a command I can send to Mailman VIA EMAIL so that Mailman send a list of all the lists of which I am a member back to me VIA EMAIL? I know I can use the web interface to find out all the lists of which I a member. I don't want to get the information through the web interface. I would like to get the information to and from via email. Thanks for any help, Chris From mark at msapiro.net Wed Nov 10 01:07:20 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 9 Nov 2010 16:07:20 -0800 Subject: [Mailman-Users] Email command to find out what lists I am on In-Reply-To: <4CD9DB1E.1020908@scu.edu> Message-ID: C Nulk wrote: > >Is there a command I can send to Mailman VIA EMAIL so that Mailman send >a list of all the lists of which I am a member back to me VIA EMAIL? No. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ajaykajla at gmail.com Wed Nov 10 04:35:30 2010 From: ajaykajla at gmail.com (Ajay Kajla) Date: Wed, 10 Nov 2010 09:05:30 +0530 Subject: [Mailman-Users] Mailman Slow Delivery In-Reply-To: References: Message-ID: Hello All, I have been using mailman+sendmail on a CentOS Linux VPS box, with 2 x Intel(R) Xeon(TM) MP CPU 3.66GHz CPUs, and 2 GB RAM. The list is of around 65000 users. Form the past few weeks server seems to be very slow in delivering mails. I have been receiving mailer approximately with 2 hours delay. *******Mailman is taking 30979.910 seconds for 65660 users******* Oct 31 10:02:28 2010 (7270) <201010310625.o9V6PY9t028494 at xyz.com> smtp to xyz for 65660 recips, completed in 30979.910 seconds *******Whereas another server with came Specs and configuration is just taking 12517.834 for larger (79579) number of users.******* Oct 31 19:10:25 2010 (12027) <201010311653.o9VGrCqX024525 at abc.com> smtp to abc for 79579 recips, completed in 12517.834 seconds Can you please suggest me how to improvise the performance of mailman or how about if I want to migrate the mailman from Sendmail to Exim ? Regards, Ajay From bbands at gmail.com Tue Nov 9 21:52:16 2010 From: bbands at gmail.com (BBands) Date: Tue, 9 Nov 2010 12:52:16 -0800 Subject: [Mailman-Users] Very simple content filtering Message-ID: Hi, We are using Mailman 2.1.9. I'd like to be able to strip potentially dangerous attachments, exe, bat, scr and the like, while leaving virtually everything else about the message intact so that readers see the messages as the composers intended them, often in html with inline graphics and so forth. No combination of settings I have tried seems to accomplish this. What content filtering settings would you recommend? Thanks so much, John From mm at wingenbach.org Tue Nov 9 19:55:24 2010 From: mm at wingenbach.org (John Wingenbach) Date: Tue, 09 Nov 2010 13:55:24 -0500 Subject: [Mailman-Users] Redundant Mailman servers Message-ID: <4CD9991C.10806@wingenbach.org> Hi, I am trying to set up redundant/parallel mailman servers. In order to accomplish this, I will have 3 servers which run mailman on them. One server at a time will be determined to be the "admin" point. However, all three will enable distributing email to the pertinent lists. Obviously, archival of the mail to the lists is not enabled or supported. ADMINSERVER -> points to one of SERVERA, SERVERB or SERVERC Email to the lists gets sent to any of SERVERA, SERVERB or SERVERC (MX distributes to all 3 servers). Configurations from ADMINSERVER are to be sync'd to the other 2 servers. The problem I am running into is that when I duplicate the lists to the other servers, the lists which are "advertised" on the current admin server do not show up as advertised. However, config_list shows the lists as advertised. I am duplicating the following files across the servers: /var/lib/mailman/data/aliases /var/lib/mailman/lists/* What am I missing such that /mailman/admin will display the same set of advertised lists? Thanks, John From andrew at hodgsonfamily.org Wed Nov 10 19:17:57 2010 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Wed, 10 Nov 2010 18:17:57 +0000 Subject: [Mailman-Users] Large list and delivery concerns Message-ID: <3D928760FE9FD24A9F02C485C3F506650D3720B928@ELROND.hodgsonfamily.org> Hi all, Ok, I have dealt with several Mailman lists in the past, however, all have been relatively small number of subscribers (around 60 subscribers being the limit, with around 2-3 messages per day). However, I have now taken on a list of around 350 subscribers receiving around 10-20 posts a day, and wonder what the most efficient way is to send the messages? I am currently using the default of Mailman sending out the message to the MTA (default Debian Exim on localhost) as one message with lots of recipients. Is it best to fan out these deliveries into more than one message by changing SMTP_MAX_RCPTS and using more than one connection by changing SMTP_MAX_SESSIONS_PER_CONNECTION? Any other suggestions? It has gone well so far, the only issue being initially blocked by Yahoo mail servers, however, I am dealing with this separately. Thanks. Andrew. From aaron at campusactivism.org Wed Nov 10 21:21:08 2010 From: aaron at campusactivism.org (Aaron Kreider) Date: Wed, 10 Nov 2010 15:21:08 -0500 Subject: [Mailman-Users] Mailman Crashes Regularly In-Reply-To: References: Message-ID: <4CDAFEB4.6070702@campusactivism.org> Our last mailman crash was at 11:47pm on Nov 7. Here is the qrunner log: I looked at our vps to see if we were hitting any resource limits, but I haven't found any problems. Nov 07 23:47:30 2010 (23778) OutgoingRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:30 2010 (23771) CommandRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:31 2010 (23778) OutgoingRunner qrunner exiting. Nov 07 23:47:31 2010 (23771) CommandRunner qrunner exiting. Nov 07 23:47:30 2010 (23776) IncomingRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:30 2010 (23744) Master watcher caught SIGTERM. Exiting. Nov 07 23:47:30 2010 (23777) NewsRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:30 2010 (23779) VirginRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:31 2010 (23776) IncomingRunner qrunner exiting. Nov 07 23:47:31 2010 (23777) NewsRunner qrunner exiting. Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23771, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23778, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Nov 07 23:47:31 2010 (23779) VirginRunner qrunner exiting. Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23777, sig: None, sts: 15, class: NewsRunner, slice: 1/1) Nov 07 23:47:30 2010 (23780) RetryRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:30 2010 (23770) BounceRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:30 2010 (23767) ArchRunner qrunner caught SIGTERM. Stopping. Nov 07 23:47:31 2010 (23780) RetryRunner qrunner exiting. Nov 07 23:47:31 2010 (23767) ArchRunner qrunner exiting. Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23776, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23779, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Nov 07 23:47:31 2010 (23770) BounceRunner qrunner exiting. Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23767, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23780, sig: None, sts: 15, class: RetryRunner, slice: 1/1) Nov 07 23:47:31 2010 (23744) Master qrunner detected subprocess exit (pid: 23770, sig: None, sts: 15, class: BounceRunner, slice: 1/1) Nov 07 23:49:12 2010 (28002) ArchRunner qrunner started. Nov 07 23:49:12 2010 (28007) NewsRunner qrunner started. Nov 07 23:49:12 2010 (28005) IncomingRunner qrunner started. Nov 07 23:49:12 2010 (28010) VirginRunner qrunner started. Nov 07 23:49:12 2010 (28011) RetryRunner qrunner started. Nov 07 23:49:12 2010 (28004) CommandRunner qrunner started. Nov 07 23:49:12 2010 (28003) BounceRunner qrunner started. Nov 07 23:49:13 2010 (28009) OutgoingRunner qrunner started. Nov 08 00:32:15 2010 (28002) ArchRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28002) ArchRunner qrunner exiting. Nov 08 00:32:15 2010 (27975) Master watcher caught SIGTERM. Exiting. Nov 08 00:32:15 2010 (28003) BounceRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28007) NewsRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28007) NewsRunner qrunner exiting. Nov 08 00:32:15 2010 (28005) IncomingRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28009) OutgoingRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28005) IncomingRunner qrunner exiting. Nov 08 00:32:15 2010 (28009) OutgoingRunner qrunner exiting. Nov 08 00:32:15 2010 (28010) VirginRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28010) VirginRunner qrunner exiting. Nov 08 00:32:15 2010 (28004) CommandRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28004) CommandRunner qrunner exiting. Nov 08 00:32:15 2010 (28011) RetryRunner qrunner caught SIGTERM. Stopping. Nov 08 00:32:15 2010 (28011) RetryRunner qrunner exiting. Nov 08 00:32:15 2010 (28003) BounceRunner qrunner exiting. Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28002, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28004, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28005, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28009, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28010, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28011, sig: None, sts: 15, class: RetryRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28007, sig: None, sts: 15, class: NewsRunner, slice: 1/1) Nov 08 00:32:15 2010 (27975) Master watcher caught SIGTERM. Exiting. Nov 08 00:32:15 2010 (27975) Master qrunner detected subprocess exit (pid: 28003, sig: 15, sts: None, class: BounceRunner, slice: 1/1) The error log was similar to the last one: Nov 08 00:36:20 2010 mailmanctl(14175): No child with pid: 27975 Nov 08 00:36:20 2010 mailmanctl(14175): [Errno 3] No such process Nov 08 00:36:20 2010 mailmanctl(14175): Stale pid file removed. Nov 08 00:36:20 2010 mailmanctl(14185): Traceback (most recent call last): Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 555, in ? Nov 08 00:36:20 2010 mailmanctl(14185): main() Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main Nov 08 00:36:20 2010 mailmanctl(14185): check_for_site_list() Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in check_for_site_list Nov 08 00:36:20 2010 mailmanctl(14185): sitelist = MailList(sitelistname, lock=0) Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in __init__ Nov 08 00:36:20 2010 mailmanctl(14185): execfile(filename, dict) Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ? Nov 08 00:36:20 2010 mailmanctl(14185): from Mailman.MysqlMemberships import MysqlMemberships Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line 49, in ? Nov 08 00:36:20 2010 mailmanctl(14185): import MySQLdb Nov 08 00:36:20 2010 mailmanctl(14185): File "build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ? Nov 08 00:36:20 2010 mailmanctl(14185): File "build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ? Nov 08 00:36:20 2010 mailmanctl(14185): File "build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__ Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 881, in resource_filename Nov 08 00:36:20 2010 mailmanctl(14185): return get_provider(package_or_requirement).get_resource_filename( Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1351, in get_resource_filename Nov 08 00:36:20 2010 mailmanctl(14185): self._extract_resource(manager, self._eager_to_zip(name)) Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1372, in _extract_resource Nov 08 00:36:20 2010 mailmanctl(14185): real_path = manager.get_cache_path( Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 962, in get_cache_path Nov 08 00:36:20 2010 mailmanctl(14185): self.extraction_error() Nov 08 00:36:20 2010 mailmanctl(14185): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 928, in extraction_error Nov 08 00:36:20 2010 mailmanctl(14185): raise err Nov 08 00:36:20 2010 mailmanctl(14185): pkg_resources . ExtractionError : Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the Python egg cache: [Errno 13] Permission denied: '/root/.python-eggs' The Python egg cache directory is currently set to: /root/.python-eggs Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory. Nov 08 00:36:20 2010 mailmanctl(14185): Nov 08 00:37:46 2010 mailmanctl(19488): PID unreadable in: /usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid Nov 08 00:37:46 2010 mailmanctl(19488): [Errno 2] No such file or directory: '/usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid' Nov 08 00:37:46 2010 mailmanctl(19488): Is qrunner even running? Nov 08 00:37:48 2010 mailmanctl(19567): Traceback (most recent call last): Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 555, in ? Nov 08 00:37:48 2010 mailmanctl(19567): main() Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main Nov 08 00:37:48 2010 mailmanctl(19567): check_for_site_list() Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in check_for_site_list Nov 08 00:37:48 2010 mailmanctl(19567): sitelist = MailList(sitelistname, lock=0) Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in __init__ Nov 08 00:37:48 2010 mailmanctl(19567): execfile(filename, dict) Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ? Nov 08 00:37:48 2010 mailmanctl(19567): from Mailman.MysqlMemberships import MysqlMemberships Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line 49, in ? Nov 08 00:37:48 2010 mailmanctl(19567): import MySQLdb Nov 08 00:37:48 2010 mailmanctl(19567): File "build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ? Nov 08 00:37:48 2010 mailmanctl(19567): File "build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ? Nov 08 00:37:48 2010 mailmanctl(19567): File "build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__ Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 881, in resource_filename Nov 08 00:37:48 2010 mailmanctl(19567): return get_provider(package_or_requirement).get_resource_filename( Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1351, in get_resource_filename Nov 08 00:37:48 2010 mailmanctl(19567): self._extract_resource(manager, self._eager_to_zip(name)) Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1372, in _extract_resource Nov 08 00:37:48 2010 mailmanctl(19567): real_path = manager.get_cache_path( Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 962, in get_cache_path Nov 08 00:37:48 2010 mailmanctl(19567): self.extraction_error() Nov 08 00:37:48 2010 mailmanctl(19567): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 928, in extraction_error Nov 08 00:37:48 2010 mailmanctl(19567): raise err Nov 08 00:37:48 2010 mailmanctl(19567): pkg_resources . ExtractionError : Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the Python egg cache: [Errno 13] Permission denied: '/root/.python-eggs' The Python egg cache directory is currently set to: /root/.python-eggs Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory. Nov 08 00:37:48 2010 mailmanctl(19567): >Why do you have >/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py which >imports MysqlMemberships? As far as I know, this is not something that >cPanel Mailman does by default? I'm using the mailman mysql adaptor so the members are stored in mysql On 10/15/2010 8:53 AM, Mark Sapiro wrote: > >> Perhaps your account does not have write access to this directory? You can >> change the cache directory by setting the PYTHON_EGG_CACHE environment >> variable to point to an accessible directory. > [...] > > > The underlying issue here is that Python's MySQLdb was apparently > installed by root in a way that the the Python egg cache directory is > not writeable by the Mailman process. > > You can get rid of the above errors by simply removing > /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py and perhaps > any other /usr/local/cpanel/3rdparty/mailman/lists/*/extend.py files, > but this will defeat your use of MysqlMemberships.py, but since it > doesn't work anyway, and maybe is only installed for the site list, > that shouldn't be too much of an issue. > > Also, please read the FAQ at > . > > Finally, it is not clear to me that the above error is from the crash. > It seems to me it would occur whenever mailmanctl starts. Is this all > that's in Mailman's error log? What's in Mailman's qrunner log? > -- Energy Justice Communities Map Developer - http://www.energyjustice.net/map From CNulk at scu.edu Wed Nov 10 19:22:37 2010 From: CNulk at scu.edu (Chris Nulk) Date: Wed, 10 Nov 2010 10:22:37 -0800 Subject: [Mailman-Users] Email command to find out what lists I am on In-Reply-To: References: <4CD9DB1E.1020908@scu.edu> Message-ID: <4CDA726D0200005000011A1E@GWIAC.scu.edu> Thanks, Mark. Given that I couldn't find anything, I suspected that was the case. Chris >>> On Tuesday, November 09, 2010 at 4:07 PM, Mark Sapiro wrote: C Nulk wrote: > >Is there a command I can send to Mailman VIA EMAIL so that Mailman send >a list of all the lists of which I am a member back to me VIA EMAIL? No. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ifetch at du.edu Wed Nov 10 21:23:17 2010 From: ifetch at du.edu (Ivan Fetch) Date: Wed, 10 Nov 2010 13:23:17 -0700 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux Message-ID: <79C2D3933C76AB41B6D135F3480AC5C957C4753E@EXCH.du.edu> Hello, We are planning to move our Mailman installation from Solaris to Linux, and upgrade in the process. I'd love to hear from anyone who has run production Mailman on Linux. What experiences have list members had with RedHat vs. Ubuntu Mailman packages, vs. compiling Mailman from source? At this point, even though I prefer to use packages when possible, I am leaning toward compiling Mailman from source because of: 1. Red Hat packages are typically more ancient 2. Ubuntu packages seem to include non-standard patches to Mailman (still sorting this out) Additionally, has anyone run into problems with Python packages provided by Red Hat and Ubuntu? Thank you for your time, Ivan. From ifetch at du.edu Wed Nov 10 21:36:45 2010 From: ifetch at du.edu (Ivan Fetch) Date: Wed, 10 Nov 2010 13:36:45 -0700 Subject: [Mailman-Users] Redundant Mailman servers In-Reply-To: <4CD9991C.10806@wingenbach.org> References: <4CD9991C.10806@wingenbach.org> Message-ID: <79C2D3933C76AB41B6D135F3480AC5C957C47542@EXCH.du.edu> Hi John, -----Original Message----- From: mailman-users-bounces+ifetch=du.edu at python.org [mailto:mailman-users-bounces+ifetch=du.edu at python.org] On Behalf Of John Wingenbach Sent: Tuesday, November 09, 2010 11:55 AM To: mailman-users at python.org Subject: [Mailman-Users] Redundant Mailman servers Hi, I am trying to set up redundant/parallel mailman servers. In order to accomplish this, I will have 3 servers which run mailman on them. One server at a time will be determined to be the "admin" point. However, all three will enable distributing email to the pertinent lists. Obviously, archival of the mail to the lists is not enabled or supported. ADMINSERVER -> points to one of SERVERA, SERVERB or SERVERC Email to the lists gets sent to any of SERVERA, SERVERB or SERVERC (MX distributes to all 3 servers). Configurations from ADMINSERVER are to be sync'd to the other 2 servers. The problem I am running into is that when I duplicate the lists to the other servers, the lists which are "advertised" on the current admin server do not show up as advertised. However, config_list shows the lists as advertised. I am duplicating the following files across the servers: /var/lib/mailman/data/aliases /var/lib/mailman/lists/* What am I missing such that /mailman/admin will display the same set of advertised lists? Thanks, John I wonder if this could be the host_name option for the mailing lists, vs. DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST on your two other Mailman servers? In other words, a difference between the Mailman configured email and web server hostnames, among your 3 servers. - Ivan From mark at msapiro.net Thu Nov 11 01:15:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 16:15:40 -0800 Subject: [Mailman-Users] Large list and delivery concerns In-Reply-To: <3D928760FE9FD24A9F02C485C3F506650D3720B928@ELROND.hodgsonfamily.org> Message-ID: Andrew Hodgson wrote: > >I am currently using the default of Mailman sending out the message to the MTA (default Debian Exim on localhost) as one message with lots of recipients. > >Is it best to fan out these deliveries into more than one message by changing SMTP_MAX_RCPTS and using more than one connection by changing SMTP_MAX_SESSIONS_PER_CONNECTION? Lowering SMTP_MAX_RCPTS and/or limiting SMTP_MAX_SESSIONS_PER_CONNECTION will generally not improve performance. All that is done by setting SMTP_MAX_SESSIONS_PER_CONNECTION to a non-zero value is to tell Mailman to close and reopen the SMTP commection to the MTA after that number of transactions. This is to accommodate MTAs that limit the number of transactions in a single session. Likewise, lowering SMTP_MAX_RCPTS only tells Mailman to send more messages with fewer recipients per message. It doesn't add any parallelism to Mailman, although it may enable additional parallelism in the MTA. With current Mailman, there is no way to add parallelism to the delivery of a single post from Mailman to the MTA. >Any other suggestions? > >It has gone well so far, the only issue being initially blocked by Yahoo mail servers, however, I am dealing with this separately. If you ultimately need to introduce parallelism in order to keep OutgoingRunner and Mailman's out/ queue from becoming backlogged with multiple messages, you can "slice" the out queue into segments processed by separate runners. See the section headed ##### # Qrunner defaults ##### in Defaults.py for information. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 11 01:22:54 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 16:22:54 -0800 Subject: [Mailman-Users] Redundant Mailman servers In-Reply-To: <4CD9991C.10806@wingenbach.org> Message-ID: John Wingenbach wrote: > >The problem I am running into is that when I duplicate the lists to the >other servers, the lists which are "advertised" on the current admin >server do not show up as advertised. However, config_list shows the >lists as advertised. I am duplicating the following files across the >servers: > >/var/lib/mailman/data/aliases >/var/lib/mailman/lists/* > >What am I missing such that /mailman/admin will display the same set of >advertised lists? See the FAQ at . Because each of your servers has a different web host name, only one server's name will match the host name in the list's web_page_url attribute and only that server will display the lists. The easiest fix is to set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py. Then the host names don't need to match. The more elaborate fix is to make sure that each hosts DEFAULT_URL_HOST is set appropriately in it's mm_cfg.py and run fix_url after copying lists/*/config.pck. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 11 01:33:06 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 16:33:06 -0800 Subject: [Mailman-Users] Mailman Slow Delivery In-Reply-To: Message-ID: Ajay Kajla wrote: > >I have been using mailman+sendmail on a CentOS Linux VPS box, with 2 x >Intel(R) Xeon(TM) MP CPU 3.66GHz CPUs, and 2 GB RAM. The list is of around >65000 users. > > >Form the past few weeks server seems to be very slow in delivering mails. I >have been receiving mailer approximately with 2 hours delay. > >*******Mailman is taking 30979.910 seconds for 65660 users******* >Oct 31 10:02:28 2010 (7270) <201010310625.o9V6PY9t028494 at xyz.com> smtp to >xyz for 65660 recips, completed in 30979.910 seconds And presumably the "last" users have been seeing over 8 hours delay. Also, possibly Mailman's out/ queue is backlogged. >*******Whereas another server with came Specs and configuration is just >taking 12517.834 for larger (79579) number of users.******* > > >Oct 31 19:10:25 2010 (12027) <201010311653.o9VGrCqX024525 at abc.com> smtp to >abc for 79579 recips, completed in 12517.834 seconds That's still too long to be viable. >Can you please suggest me how to improvise the performance of mailman Go to the FAQ at and search for "performance". >or how >about if I want to migrate the mailman from Sendmail to Exim ? See for information on integrating Exim and Mailman -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 11 01:50:34 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 16:50:34 -0800 Subject: [Mailman-Users] Mailman Crashes Regularly In-Reply-To: <4CDAFEB4.6070702@campusactivism.org> Message-ID: Aaron Kreider quoted me and wrote: > >>Why do you have >>/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py which >>imports MysqlMemberships? As far as I know, this is not something that >>cPanel Mailman does by default? >I'm using the mailman mysql adaptor so the members are stored in mysql The Python MySQLdb package is not installed on your server in a way that it is usable by Mailman. >On 10/15/2010 8:53 AM, Mark Sapiro wrote: >> >>> Perhaps your account does not have write access to this directory? You can >>> change the cache directory by setting the PYTHON_EGG_CACHE environment >>> variable to point to an accessible directory. >> [...] >> >> >> The underlying issue here is that Python's MySQLdb was apparently >> installed by root in a way that the the Python egg cache directory is >> not writeable by the Mailman process. >> >> You can get rid of the above errors by simply removing >> /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py and perhaps >> any other /usr/local/cpanel/3rdparty/mailman/lists/*/extend.py files, >> but this will defeat your use of MysqlMemberships.py, but since it >> doesn't work anyway, and maybe is only installed for the site list, >> that shouldn't be too much of an issue. >> >> Also, please read the FAQ at >> . >> >> Finally, it is not clear to me that the above error is from the crash. >> It seems to me it would occur whenever mailmanctl starts. Is this all >> that's in Mailman's error log? What's in Mailman's qrunner log? And it still looks to me as if this error occurs whenever mailmanctl checks for a site list which is every time it starts. You could remove /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py. That would at least get rid of the error every time mailmanctl starts and move it to the instantiation of any list that has the extend.py. If you want to use MysqlMemberships.py, you will have to install the MySQLdb package in a way that Mailman can use it. I have no clue as to how to properly do this on a cPanel server, but you could try installing it as 'mailman' instead of 'root' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 11 01:58:33 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 16:58:33 -0800 Subject: [Mailman-Users] Very simple content filtering In-Reply-To: Message-ID: BBands wrote: > >We are using Mailman 2.1.9. I'd like to be able to strip potentially >dangerous attachments, exe, bat, scr and the like, while leaving >virtually everything else about the message intact so that readers see >the messages as the composers intended them, often in html with inline >graphics and so forth. No combination of settings I have tried seems >to accomplish this. What content filtering settings would you >recommend? If you want to filter only based on attachment file name extension, set filter_content = Yes filter_mime_types Empty pass_mime_types Empty filter_filename_extensions exe bat cmd com pif scr vbs cpl (or what ever list you want) pass_filename_extensions Empty collapse_alternatives = No convert_html_to_plaintext = No filter_action As desired for messages that consist entirely of parts with file names with the unwanted extension (it is not likely there will be such messages and almost all messages have a text body with no filename). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From aaron at campusactivism.org Thu Nov 11 04:18:53 2010 From: aaron at campusactivism.org (Aaron Kreider) Date: Wed, 10 Nov 2010 22:18:53 -0500 Subject: [Mailman-Users] Mailman Crashes Regularly In-Reply-To: References: Message-ID: <4CDB609D.3050005@campusactivism.org> On 11/10/2010 7:50 PM, Mark Sapiro wrote: > Aaron Kreider quoted me and wrote: >>> Why do you have >>> /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py which >>> imports MysqlMemberships? As far as I know, this is not something that >>> cPanel Mailman does by default? >> I'm using the mailman mysql adaptor so the members are stored in mysql > The Python MySQLdb package is not installed on your server in a way > that it is usable by Mailman. > > Well something is writing data into the mysql table where we store mailman data (and it isn't me). I've got my last time stamp on Nov 2. So it must be at least semi-usable. Aaron From mark at msapiro.net Thu Nov 11 07:05:22 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 22:05:22 -0800 Subject: [Mailman-Users] Mailman Crashes Regularly In-Reply-To: <4CDB609D.3050005@campusactivism.org> References: <4CDB609D.3050005@campusactivism.org> Message-ID: <4CDB87A2.8050402@msapiro.net> On 11/10/2010 7:18 PM, Aaron Kreider wrote: > On 11/10/2010 7:50 PM, Mark Sapiro wrote: >> Aaron Kreider quoted me and wrote: >>>> Why do you have >>>> /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py which >>>> imports MysqlMemberships? As far as I know, this is not something that >>>> cPanel Mailman does by default? >>> I'm using the mailman mysql adaptor so the members are stored in mysql >> The Python MySQLdb package is not installed on your server in a way >> that it is usable by Mailman. >> >> > Well something is writing data into the mysql table where we store > mailman data (and it isn't me). I've got my last time stamp on Nov 2. > So it must be at least semi-usable. Well, possibly the problem is only when mailmanctl instantiates the 'mailman' site list because it runs as root. Try just removing the one /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py file. Then that list will use OldStyleMemberships.py, but since it's not a "user" list, it may be OK that it doesn't use MysqlMemberships.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 11 08:19:29 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 23:19:29 -0800 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: <79C2D3933C76AB41B6D135F3480AC5C957C4753E@EXCH.du.edu> Message-ID: Ivan Fetch wrote: > >We are planning to move our Mailman installation from Solaris to Linux, and upgrade in the process. I'd love to hear from anyone who has run production Mailman on Linux. > >What experiences have list members had with RedHat vs. Ubuntu Mailman packages, vs. compiling Mailman from source? I run Mailman installed from source on CentOS 5 for my production lists. The default Python on this server is the CentOS/RedHat 2.4.3-27.el5 (you need both python and python-devel to install Mailman from source). I also have Python 2.6.5 on this server installed from source. I have installed and run Mailman in production at various times with both Python versions. Currently I'm running Mailman installed with Python 2.6.5. My lists are small to moderate size (<500 members) and low to moderate traffic (zero to two or three dozen posts per list daily). Everything works fine (I fix the Mailman bugs when I find them ;) >At this point, even though I prefer to use packages when possible, I am leaning toward compiling Mailman from source because of: >1. Red Hat packages are typically more ancient >2. Ubuntu packages seem to include non-standard patches to Mailman (still sorting this out) I've never used the Debian/Ubuntu package, but I've had issues with some of their patches. I've fixed the significant problems addressed by the Debian patches, at least those I understand, upstream in 2.1.13 and 2.1.14. >Additionally, has anyone run into problems with Python packages provided by Red Hat and Ubuntu? The RedHat Python 2.4.3 package works for me, but it is old. There are python26 packages in the epel repository, but I haven't used them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From chris.tandiono at gmail.com Thu Nov 11 00:23:00 2010 From: chris.tandiono at gmail.com (Chris Tandiono) Date: Wed, 10 Nov 2010 15:23:00 -0800 Subject: [Mailman-Users] Redundant Mailman servers In-Reply-To: <79C2D3933C76AB41B6D135F3480AC5C957C47542@EXCH.du.edu> References: <4CD9991C.10806@wingenbach.org> <79C2D3933C76AB41B6D135F3480AC5C957C47542@EXCH.du.edu> Message-ID: On Wed, 10 Nov 2010 12:36:45 -0800, Ivan Fetch wrote: > I wonder if this could be the host_name option for the mailing lists, > vs. DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST on your two other Mailman > servers? In other words, a difference between the Mailman configured > email and web server hostnames, among your 3 servers. > > - Ivan Dunno if this is relevant, but yesterday I had a similar problem after putting Mailman behind a reverse proxy that only uses HTTP/1.0 without the Host header to connect to the upstream server. Mailman would complain that there were no lists on localhost and to contact mailman at localhost for help. The solution was to set the host header manually (ProxyPreserveHost for Apache, proxy_set_header Host $host for nginx, etc.). -- Chris From janssen at parc.com Wed Nov 10 16:58:54 2010 From: janssen at parc.com (Bill Janssen) Date: Wed, 10 Nov 2010 07:58:54 PST Subject: [Mailman-Users] bad cron messages from mailman? In-Reply-To: References: Message-ID: <33852.1289404734@parc.com> Hi! I'm a mailman newcomer, and am setting up an installation on a CentOS 5 system. Mailman 2.1.9. I'm getting these messages from cron on that machine: Subject: Cron mailman /usr/lib/mailman/cron/checkdbs From: root at uplib.parc.com (Cron Daemon) Date: Wed, 10 Nov 2010 07:00:01 PST To: janssen at parc.com /bin/sh: mailman: command not found What's wrong here? The cron/crontab.in file has lines like 27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip in it, so I suppose that "mailman" is not on the "mailman" account's PATH, but I don't see how it would ever get on that PATH, either. Do I need to change those lines to read /usr/lib/mailman/mail/mailman, instead of just mailman? Bill From mark at msapiro.net Thu Nov 11 08:33:42 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 Nov 2010 23:33:42 -0800 Subject: [Mailman-Users] bad cron messages from mailman? In-Reply-To: <33852.1289404734@parc.com> Message-ID: Bill Janssen wrote: >Hi! I'm a mailman newcomer, and am setting up an installation on a >CentOS 5 system. Mailman 2.1.9. I'm getting these messages from cron >on that machine: > > Subject: Cron mailman /usr/lib/mailman/cron/checkdbs > From: root at uplib.parc.com (Cron Daemon) > Date: Wed, 10 Nov 2010 07:00:01 PST > To: janssen at parc.com > > /bin/sh: mailman: command not found > >What's wrong here? The cron/crontab.in file has lines like > > 27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip > >in it, so I suppose that "mailman" is not on the "mailman" account's >PATH, but I don't see how it would ever get on that PATH, either. Do I >need to change those lines to read /usr/lib/mailman/mail/mailman, >instead of just mailman? You need to follow the documentation from your packager for installing Mailman, not the source distribution documentation. The basic problem is you have installed a crontab as user mailman's crontab which is designed to be installed as a system crontab in /etc/cron.d. The crontab you have installed has a 6th field between the five days and times fields and the command which for system crontabs is the userid to run under, but for user crontabs is interpreted as the command to run. Either install the file in (e.g.) /etc/cron.d/mailman or remove the 'mailman' entries from between the times and the commands as in 27 3 * * * /usr/lib/mailman/cron/nightly_gzip -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adam-mailman at amyl.org.uk Thu Nov 11 11:36:48 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Thu, 11 Nov 2010 10:36:48 +0000 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: <79C2D3933C76AB41B6D135F3480AC5C957C4753E@EXCH.du.edu> References: <79C2D3933C76AB41B6D135F3480AC5C957C4753E@EXCH.du.edu> Message-ID: <20101111103648.GB20436@hendricks.amyl.org.uk> On Wed, Nov 10, 2010 at 01:23:17PM -0700, Ivan Fetch wrote: > At this point, even though I prefer to use packages when possible, I am leaning toward compiling Mailman from source because of: > 1. Red Hat packages are typically more ancient > 2. Ubuntu packages seem to include non-standard patches to Mailman (still sorting this out) >From what I remember, the Mailman packages for both Debian and Ubuntu are pretty much the same. In such a case, you're reliant on the maintainer updating fixes promptly (or very rarely, the security team), along with necessary modifications to conform with Debian policy. Once one gets around those, one has something that's usable, and not too difficult to operate, but I've not done a source <--> source comparison for a while. I'm lazy, and just use the versions in the repos, but am aware a couple of folks on list either build their own PPAs or use others. > Additionally, has anyone run into problems with Python packages provided by Red Hat and Ubuntu? Not with Ubuntu. I've not used Red Hat on my own boxes for several years, now, mind. -- Experience is what enables you to recognise a mistake the second time you make it. From bbands at gmail.com Thu Nov 11 16:52:58 2010 From: bbands at gmail.com (BBands) Date: Thu, 11 Nov 2010 07:52:58 -0800 Subject: [Mailman-Users] Very simple content filtering In-Reply-To: References: Message-ID: On Wed, Nov 10, 2010 at 4:58 PM, Mark Sapiro wrote: > If you want to filter only based on attachment file name extension, set Thanks Mark, that's what I came too as well. Maybe I am barking up the wrong tree? I thought that my problem was my filtering settings, but maybe not. Messages transmitted by the list are arriving with the footer as an extension. (I am using the default footer text, which serves my purpose well.) John From andrew at hodgsonfamily.org Thu Nov 11 16:52:22 2010 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Thu, 11 Nov 2010 15:52:22 +0000 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: <20101111103648.GB20436@hendricks.amyl.org.uk> References: <79C2D3933C76AB41B6D135F3480AC5C957C4753E@EXCH.du.edu>, <20101111103648.GB20436@hendricks.amyl.org.uk> Message-ID: <3D928760FE9FD24A9F02C485C3F506650D37206773@ELROND.hodgsonfamily.org> Adam McGreggor wrote: >In such a case, you're reliant on the maintainer updating fixes >promptly (or very rarely, the security team), along with necessary >modifications to conform with Debian policy. Yes, I am still waiting for the latest Mailman security patch to be included in the stable Debian repo, and it is a shame imho that we aren't likely to get 2.1.14 in the next Debian release (the latest Debian package seems to be a patched 2.1.13). >Once one gets around those, one has something that's usable, and not >too difficult to operate, but I've not done a source <--> source >comparison for a while. It is easy to install and operate, I will give you that. >I'm lazy, and just use the versions in the repos, but am aware a >couple of folks on list either build their own PPAs or use others. I am thinking of trying to build my own install for the reasons I outlined above, the reasons I am holding off this are: 1. Having to move everything out of the directory structure you get with the Debian package. 2. Knowing what functionality/bug fixes I am getting with the Debian specific patches that I wouldn't otherwise get from the upstream package. Thanks. Andrew. From janssen at parc.com Thu Nov 11 17:26:44 2010 From: janssen at parc.com (Bill Janssen) Date: Thu, 11 Nov 2010 08:26:44 PST Subject: [Mailman-Users] bad cron messages from mailman? In-Reply-To: References: Message-ID: <39441.1289492804@parc.com> Mark Sapiro wrote: > The basic problem is you have installed a crontab as user mailman's > crontab which is designed to be installed as a system crontab in > /etc/cron.d. The crontab you have installed has a 6th field between > the five days and times fields and the command which for system > crontabs is the userid to run under, but for user crontabs is > interpreted as the command to run. > > Either install the file in (e.g.) /etc/cron.d/mailman or remove the > 'mailman' entries from between the times and the commands as in > > 27 3 * * * /usr/lib/mailman/cron/nightly_gzip Thanks! Bill From mark at msapiro.net Thu Nov 11 17:37:24 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Nov 2010 08:37:24 -0800 Subject: [Mailman-Users] Very simple content filtering In-Reply-To: Message-ID: BBands wrote: > >Messages transmitted by the list are arriving with the >footer as an extension. (I am using the default footer text, which >serves my purpose well.) See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From bbands at gmail.com Thu Nov 11 17:45:40 2010 From: bbands at gmail.com (BBands) Date: Thu, 11 Nov 2010 08:45:40 -0800 Subject: [Mailman-Users] Very simple content filtering In-Reply-To: References: Message-ID: On Thu, Nov 11, 2010 at 8:37 AM, Mark Sapiro wrote: > See the FAQ at . Ah, the FAQ to the rescue, much to my embarrassment. Thanks for a wonderful tool. John From mark at msapiro.net Thu Nov 11 17:51:26 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Nov 2010 08:51:26 -0800 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: <3D928760FE9FD24A9F02C485C3F506650D37206773@ELROND.hodgsonfamily.org> Message-ID: Andrew Hodgson wrote: > >I am thinking of trying to build my own install for the reasons I outlined above, the reasons I am holding off this are: > >1. Having to move everything out of the directory structure you get with the Debian package. I'm not sure what the Debian directory structure is, but you should be able to get very close via the --prefix, --exec-prefix and --with-var-prefix options to configure. >2. Knowing what functionality/bug fixes I am getting with the Debian specific patches that I wouldn't otherwise get from the upstream package. I have been through the patches at , and those issues that are addressed that are significant, not Debian specific and that I could understand have all been fixed in Mailman 2.1.14. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From b19141 at achilles.ctd.anl.gov Thu Nov 11 13:24:21 2010 From: b19141 at achilles.ctd.anl.gov (Barry Finkel) Date: Thu, 11 Nov 2010 06:24:21 -0600 (CST) Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: Mail from 'Ivan Fetch ' dated: Wed, 10 Nov 2010 13:23:17 -0700 Message-ID: <20101111122421.2DA122AE6C@atalanta.it.anl.gov> Ivan Fetch wrote: >Hello, > >We are planning to move our Mailman installation from Solaris to Linux, >and upgrade in the process. I'd love to hear from anyone who has run >production Mailman on Linux. > >What experiences have list members had with RedHat vs. Ubuntu Mailman >packages, vs. compiling Mailman from source? > >At this point, even though I prefer to use packages when possible, I am >leaning toward compiling Mailman from source because of: >1. Red Hat packages are typically more ancient >2. Ubuntu packages seem to include non-standard patches to Mailman > (still sorting this out) > >Additionally, has anyone run into problems with Python packages >provided by Red Hat and Ubuntu? Check the archives of the list. I run Mailman 2.1.13 (soon to be 14) on Ubuntu Dapper (to be converted to the latest LTS release). I built my own Mailman package from the SourceForge source because most of the Debian/Ubuntu patches were undocumented as to what they did, and one removed a necessary library. Contact me off-line for more details. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 240, Room 5.B.8 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From renehamburger at students.oakhill.ac.uk Thu Nov 11 14:00:31 2010 From: renehamburger at students.oakhill.ac.uk (Rene Hamburger) Date: Thu, 11 Nov 2010 13:00:31 -0000 Subject: [Mailman-Users] Mailman blocks messages based on reply-to address Message-ID: <006501cb81a0$6f0637a0$4d12a6e0$@students.oakhill.ac.uk> Hi everyone, I am forwarding emails to a mailing list after I have included the original sender's email as the reply-to address. It works fine as long as the reply-to address is not on the actual email list. But when it is, mailman recognises it as being moderated and blocks the email. Is that a feature or a bug? :) The reason we are not running it as a regular moderated list is that I have to edit emails slightly before sending them out and that people not on the list would sometimes ask us to forward them to the list. Any thoughts? Thanks, Rene From mark at msapiro.net Thu Nov 11 21:05:21 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Nov 2010 12:05:21 -0800 Subject: [Mailman-Users] Mailman blocks messages based on reply-to address In-Reply-To: <006501cb81a0$6f0637a0$4d12a6e0$@students.oakhill.ac.uk> Message-ID: Rene Hamburger wrote: > >I am forwarding emails to a mailing list after I have included the original >sender's email as the reply-to address. It works fine as long as the >reply-to address is not on the actual email list. But when it is, mailman >recognises it as being moderated and blocks the email. Is that a feature or >a bug? :) This is a feature. By default, the address(es) in the From: header, the envelope from, the Reply-To: header and the Sender: header are examined in that order and if any of them are a list member, the post is considered to be from the first member found for moderation purposes. The question is, the From: should be your address, so is that address a list member? If not, why not? If so, and you are not moderated, the Reply-To: address should not be considered unless you have overridden the definition of SENDER_HEADERS in mm_cfg.py. If you put this SENDER_HEADERS = ('from', None, 'sender') in mm_cfg.py, i.e. drop reply-to from the default SENDER_HEADERS = ('from', None, 'reply-to', 'sender') then Mailman won't consider the Reply-To: when determining a moderated member post. But, As I say, I don't understand why your own From: is not controlling unless you aren't a list member and are in accept_these_nonmembers instead. If that is the case, why? It provides no security or spoof resistance over your being a member, and if you're really concerned about spoofing, everyone should be moderated and you should post with an Approved: password header. And even with no other changes, posting with an Approved: password header will prevent the post being held regardless of the Reply-To:. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ifetch at du.edu Fri Nov 12 01:51:51 2010 From: ifetch at du.edu (Ivan Fetch) Date: Thu, 11 Nov 2010 17:51:51 -0700 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: References: <79C2D3933C76AB41B6D135F3480AC5C957C4753E@EXCH.du.edu> Message-ID: <79C2D3933C76AB41B6D135F3480AC5C957C475EE@EXCH.du.edu> Hello, Thank you, Mark, Adam, and Andrew for your replies. More below. > -----Original Message----- > From: Mark Sapiro [mailto:mark at msapiro.net] > Sent: Thursday, November 11, 2010 12:19 AM > To: Ivan Fetch; MailMan > Subject: Re: [Mailman-Users] Moving / upgrading Mailman from Solaris to > Linux > > Ivan Fetch wrote: > > > >We are planning to move our Mailman installation from Solaris to > Linux, and upgrade in the process. I'd love to hear from anyone who has > run production Mailman on Linux. > > > >What experiences have list members had with RedHat vs. Ubuntu Mailman > packages, vs. compiling Mailman from source? > > > I run Mailman installed from source on CentOS 5 for my production > lists. The default Python on this server is the CentOS/RedHat > 2.4.3-27.el5 (you need both python and python-devel to install Mailman > from source). I also have Python 2.6.5 on this server installed from > source. I have installed and run Mailman in production at various > times with both Python versions. Currently I'm running Mailman > installed with Python 2.6.5. > > My lists are small to moderate size (<500 members) and low to moderate > traffic (zero to two or three dozen posts per list daily). > > Everything works fine (I fix the Mailman bugs when I find them ;) > > >At this point, even though I prefer to use packages when possible, I > am leaning toward compiling Mailman from source because of: > >1. Red Hat packages are typically more ancient > >2. Ubuntu packages seem to include non-standard patches to Mailman > (still sorting this out) > > > I've never used the Debian/Ubuntu package, but I've had issues with > some of their patches. I've fixed the significant problems addressed > by the Debian patches, at least those I understand, upstream in 2.1.13 > and 2.1.14. What issues have you had with their patches? E.G> the way they have fixed a bug on their own? > >Additionally, has anyone run into problems with Python packages > provided by Red Hat and Ubuntu? > > > The RedHat Python 2.4.3 package works for me, but it is old. There are > python26 packages in the epel repository, but I haven't used them. I will look into the EPEL python, it would be nice to have acces to something somewhat newer than what ships with RHEL. Although ... RHEL 6 is out now. :-) - Ivan From mark at msapiro.net Fri Nov 12 07:05:55 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 11 Nov 2010 22:05:55 -0800 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: <79C2D3933C76AB41B6D135F3480AC5C957C475EE@EXCH.du.edu> Message-ID: Ivan Fetch wrote: > >What issues have you had with their patches? E.G> the way they have fixed a bug on their own? For example, the patch 30_pipermail_threads.patch fixes an obscure bug , but breaks indentation in the threaded archive index for messages with message-ids containing hyphens. Fixed properly upstream in Mailman 2.1.13. The patch 77_header_folding_in_attachments.patch fixes , , but IIRC breaks archiving of messages containing body lines beginning with "From ". Fixed properly upstream in Mailman 2.1.13. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Fri Nov 12 23:43:40 2010 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Fri, 12 Nov 2010 22:43:40 +0000 Subject: [Mailman-Users] Moving / upgrading Mailman from Solaris to Linux In-Reply-To: References: <3D928760FE9FD24A9F02C485C3F506650D37206773@ELROND.hodgsonfamily.org> Message-ID: <3D928760FE9FD24A9F02C485C3F506650D3720B938@ELROND.hodgsonfamily.org> Mark Sapiro wrote: >Andrew Hodgson wrote: >> >>I am thinking of trying to build my own install for the reasons I outlined above, the reasons I am holding off this are: >> >>1. Having to move everything out of the directory structure you get with the Debian package. >I'm not sure what the Debian directory structure is, but you should be able to get very close via the --prefix, --exec-prefix and --with-var-prefix >options to configure. Actually I have just come out the other side of the upgrade, it wasn't too painful. I actually put everything in /usr/local/mailman, as it allowed me to sort the configs etc out without breaking the working install. I built the source on a virtual machine I do other testing on, then copied the mailman directory over to the live system, running fix_perms to ensure everything worked fine. I built it with the user and group of list, and set the mail-gid and cgi-gid according to the Debian package. I stole the scripts from /etc/init.d/mailman, /etc/logrotate.d/mailman and /etc/cron.d/mailman after tweaking a bit to keep the working init, logrotate and cron scripts working. I then changed the Apache configs to point to the new installation, and after stopping the services, moved the archives and lists directories over. I ran the new qrunner and everything started up ok. The only issue I had which had me scratching my head for a bit was that simlinks in /usr/local/mailman/archives/public were broken, these are now fixed. End result: Working Mailman with security patch applied :) If anyone wants more detailed steps please let me know. Thanks. Andrew. From andrevk at nikhef.nl Sat Nov 13 13:12:18 2010 From: andrevk at nikhef.nl (Andre van Kan) Date: Sat, 13 Nov 2010 13:12:18 +0100 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <4CD4192A.70707@msapiro.net> References: <4CD40A2A.9070809@nikhef.nl> <4CD4192A.70707@msapiro.net> Message-ID: <1289650338.1993.44.camel@sloeber> On Fri, 2010-11-05 at 07:48 -0700, Mark Sapiro wrote: > >> I understand that, but the data/heldmsg* file could have been removed > >>> external to Mailman before that. > > > > I never found any heldmsg* on the system, nor any complaint > > that such a file could not be written. Maybe could an strace of > > the appropriate qrunner be of some help? I should have firstly explained the consistency of our recently installed mailsystem: three separate IP-clusters (!) cooperate to handle our e-mail and except for MM they perform very well. (btw, it was designed and installed by an external party) - cluster 1: runs the MTA (Postfix) and MM - cluster 2: runs Horde and the MM-webinterface - cluster 3: runs Cyrus-imapd Cluster 1 and 2 share - via NFS - the MM-lists etc. I found out however that data/heldms* was only available on cluster 1. >From the moment that I shared this directory between cluster 1 and 2 the approved messages were visible with the admin webinterface and approving resulted in a transfer of the messages to cluster2:/var/spool/mailman/in and are waiting there for the things to come. So the problem is partly solved, albeit that the messages still are not delivered, supposedly because cluster 1 should be able to transfer the messages to cluster 3, the IMAP-server (?). So I want to share the directory cluster2:/var/spool/mailman/in with cluster 1 since this cluster is configured to send the messages to the IMAP-server. Does this sound reasonable to you, or should cluster 2 itself better be configured to send the approved messages to the IMAP-server directly? Thank you for your time and useful hints &c. Regards, Andre van Kan From adam-mailman at amyl.org.uk Sat Nov 13 13:46:35 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Sat, 13 Nov 2010 12:46:35 +0000 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <1289650338.1993.44.camel@sloeber> References: <4CD40A2A.9070809@nikhef.nl> <4CD4192A.70707@msapiro.net> <1289650338.1993.44.camel@sloeber> Message-ID: <20101113124635.GN20436@hendricks.amyl.org.uk> On Sat, Nov 13, 2010 at 01:12:18PM +0100, Andre van Kan wrote: > - cluster 1: runs the MTA (Postfix) and MM > - cluster 2: runs Horde and the MM-webinterface > - cluster 3: runs Cyrus-imapd > > Cluster 1 and 2 share - via NFS - the MM-lists etc. I found out however > that data/heldms* was only available on cluster 1. > >From the moment that I shared this directory between cluster 1 and 2 the > approved messages were visible with the admin webinterface and approving > resulted in a transfer of the messages to cluster2:/var/spool/mailman/in > and are waiting there for the things to come. > So the problem is partly solved, albeit that the messages still are not > delivered, supposedly because cluster 1 should be able to transfer the > messages to cluster 3, the IMAP-server (?). Why on earth are you adding in IMAP at this stage? Mailman is designed to deliver via a pipe, to the scripts. I believe that's the case, even with Postfix. > So I want to share the directory cluster2:/var/spool/mailman/in with > cluster 1 since this cluster is configured to send the messages to the > IMAP-server. I suspect that that's a completely wrong approach. > Does this sound reasonable to you, or should cluster 2 itself better be 's/2/1/' > configured to send the approved messages to the IMAP-server directly? 's/to the IMAP-server//' -- "I would nationalise Elizabeth Hurley and allow each of us to claim our share." -- JG Ballard ('lost' NS interview, mid 1990s) From mark at msapiro.net Sat Nov 13 17:15:18 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 13 Nov 2010 08:15:18 -0800 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <1289650338.1993.44.camel@sloeber> References: <4CD40A2A.9070809@nikhef.nl> <4CD4192A.70707@msapiro.net> <1289650338.1993.44.camel@sloeber> Message-ID: <4CDEB996.7080306@msapiro.net> On 11/13/2010 4:12 AM, Andre van Kan wrote: > > I should have firstly explained the consistency of our recently > installed mailsystem: three separate IP-clusters (!) cooperate to > handle our e-mail and except for MM they perform very well. > (btw, it was designed and installed by an external party) > > - cluster 1: runs the MTA (Postfix) and MM > - cluster 2: runs Horde and the MM-webinterface > - cluster 3: runs Cyrus-imapd > > Cluster 1 and 2 share - via NFS - the MM-lists etc. I found out however > that data/heldms* was only available on cluster 1. > From the moment that I shared this directory between cluster 1 and 2 the > approved messages were visible with the admin webinterface and approving > resulted in a transfer of the messages to cluster2:/var/spool/mailman/in > and are waiting there for the things to come. > So the problem is partly solved, albeit that the messages still are not > delivered, supposedly because cluster 1 should be able to transfer the > messages to cluster 3, the IMAP-server (?). The approved message is requeued in cluster 2 /var/spool/mailman/in, but no qrunners are running on cluster 2 so there it sits. This directory (in fact all of the /var/spool/mailman/ directory) must be shared with cluster 1. In fact, all of Mailman's mutable directories except maybe logs should be shared between clusters 1 and 2. The rest of Mailman's directories can be either shared or duplicated as you wish. Assuming this is RedHat's Mailman as indicated by the queues being in /var/spool/mailman, the directories that must be shared are /var/lib/mailman/archives /var/lib/mailman/data /var/lib/mailman/lists /var/lock/mailman /var/spool/mailman Sharing of /var/log/mailman is optional. > So I want to share the directory cluster2:/var/spool/mailman/in with > cluster 1 since this cluster is configured to send the messages to the > IMAP-server. I'm not sure what the IMAP server has to do with it except for the ultimate delivery of "local user" messages from a mailbox or maildir to the user's MUA. Mailman's OutgoingRunner on cluster 1 delivers to Postfix, and delivery from there is handled by Postfix. > Does this sound reasonable to you, or should cluster 2 itself better be > configured to send the approved messages to the IMAP-server directly? No. Don't try to configure cluster 2 to deliver mail from Mailman. This will result in much unnecessary duplication. Just share the directories I indicate above between clusters 1 and 2. Note that it is critically important to share the locks directory (/var/lock/mailman). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From frank.vandamme at gmail.com Mon Nov 15 16:31:22 2010 From: frank.vandamme at gmail.com (Frank Van Damme) Date: Mon, 15 Nov 2010 16:31:22 +0100 Subject: [Mailman-Users] confirm moderator approval Message-ID: Hi, mailman sends messages to the user if his mail is held for approval or when the mail is rejected, but not when approved. Is it possible to configure mailman to send a message to the user when his message is approved? -- Frank Van Damme No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. From mark at msapiro.net Mon Nov 15 17:30:14 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 15 Nov 2010 08:30:14 -0800 Subject: [Mailman-Users] confirm moderator approval In-Reply-To: Message-ID: Frank Van Damme wrote: > >mailman sends messages to the user if his mail is held for approval or >when the mail is rejected, but not when approved. Is it possible to >configure mailman to send a message to the user when his message is >approved? No. If the poster is a list member, presumably she will be notified by receiving her post from the list (if she doesn't use google/gmail) or in a digest, but if she is a non-member or for other reasons doesn't receive her own posts, then she gets no notice from Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From alan at patriot.net Mon Nov 15 19:08:15 2010 From: alan at patriot.net (Alan McConnell) Date: Mon, 15 Nov 2010 13:08:15 -0500 Subject: [Mailman-Users] Backing Up the List of Members Message-ID: <20101115180815.GA4907@patriot.net> Assembled Wisdom! I am big fan of mailman and admin three E-lists managed by mailman. These lists are hosted on remote computers. I am now having the problem: I wish to back up the list of members of a couple of my lists to my home machine. I used to get all the members on one page. Now the members are alphabetized and each initial letter is put on a diffent page. I can still back-up, but it is a laborious process. Is there a command to exhibit all members on one page? or, better yet, is there a command an administrator can invoke to have the members, if possible with their flags, shipped to my home computer? TIA for anticipated help! Alan McConnell -- Alan McConnell : http://patriot.net/users/alan When the ax came into the woods, the trees all said: "Well, at least the handle is one of us." (Turkish folk warning, from 'The Nation') From frank.vandamme at gmail.com Tue Nov 16 09:08:02 2010 From: frank.vandamme at gmail.com (Frank Van Damme) Date: Tue, 16 Nov 2010 09:08:02 +0100 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <20101115180815.GA4907@patriot.net> References: <20101115180815.GA4907@patriot.net> Message-ID: 2010/11/15 Alan McConnell : > Assembled Wisdom! > > I am big fan of mailman and admin three E-lists managed by > mailman. ?These lists are hosted on remote computers. > > I am now having the problem: I wish to back up the list of > members of a couple of my lists to my home machine. ?I used to > get all the members on one page. ?Now the members are alphabetized > and each initial letter is put on a diffent page. ?I can still > back-up, but it is a laborious process. > > Is there a command to exhibit all members on one page? ?or, better > yet, is there a command an administrator can invoke to have the > members, if possible with their flags, shipped to my home computer? > > TIA for anticipated help! /usr/lib/mailman/bin/list_members you can also use "list_lists --bare" to enumerate the lists -- Frank Van Damme No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. From mailman-admin at uni-konstanz.de Tue Nov 16 10:21:27 2010 From: mailman-admin at uni-konstanz.de (Mailman Admin) Date: Tue, 16 Nov 2010 10:21:27 +0100 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <20101115180815.GA4907@patriot.net> References: <20101115180815.GA4907@patriot.net> Message-ID: <4CE24D17.4010905@uni-konstanz.de> Hi On 11/15/2010 07:08 PM, Alan McConnell wrote: > > I am now having the problem: I wish to back up the list of > members of a couple of my lists to my home machine. I used to > get all the members on one page. Now the members are alphabetized > and each initial letter is put on a diffent page. I can still > back-up, but it is a laborious process. > As list admin you can set "General Options" --> "admin_member_chunksize" to a value bigger than the number of currently subscribed members. With that you get the old behaviour back with all members on one page instead of split into seperate alphabetized chunks. With this you don't need access to the console. Kind regards, Christian Mack From malcolm.austen at weald.org.uk Tue Nov 16 10:39:28 2010 From: malcolm.austen at weald.org.uk (Malcolm Austen) Date: Tue, 16 Nov 2010 09:39:28 -0000 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <4CE24D17.4010905@uni-konstanz.de> References: <20101115180815.GA4907@patriot.net> <4CE24D17.4010905@uni-konstanz.de> Message-ID: On Tue, 16 Nov 2010 09:21:27 -0000, Mailman Admin wrote: > On 11/15/2010 07:08 PM, Alan McConnell wrote: >> >> I am now having the problem: I wish to back up the list of >> members of a couple of my lists to my home machine. I used to >> get all the members on one page. Now the members are alphabetized >> and each initial letter is put on a diffent page. I can still >> back-up, but it is a laborious process. > > As list admin you can set > "General Options" --> "admin_member_chunksize" > to a value bigger than the number of currently subscribed members. > With that you get the old behaviour back with all members on one page > instead of split into seperate alphabetized chunks. > > With this you don't need access to the console. A trick I've used on a hosted mailman that has not been updated to have the chunk-size option (it's 2.1.9), is to save the list-admin's subscriber list page at <../mailman/roster/list-name>. This is in two columns (message and digest) and has extra parentheses where delivery is disabled, and the addresses are obfuscated ... but nothing that cannot be unravelled with a few lines of Perl ;-) regards, Malcolm. -- Malcolm Austen, Oxfordshire, England From dunkel at calamus.net Tue Nov 16 11:58:35 2010 From: dunkel at calamus.net (Ulf Dunkel) Date: Tue, 16 Nov 2010 11:58:35 +0100 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <20101115180815.GA4907@patriot.net> References: <20101115180815.GA4907@patriot.net> Message-ID: <4CE263DB.70102@calamus.net> Hi Alan. > Is there a command to exhibit all members on one page? or, better > yet, is there a command an administrator can invoke to have the > members, if possible with their flags, shipped to my home computer? I guess I would do a simple admin request email for the lists every now and then, something in the format: To: _request@ Subject: who This sends an email to your account with a list of all currently stored members of the list. ---HTH, ---UlfDunkel From malcolm.austen at weald.org.uk Tue Nov 16 12:42:27 2010 From: malcolm.austen at weald.org.uk (Malcolm Austen) Date: Tue, 16 Nov 2010 11:42:27 -0000 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <4CE263DB.70102@calamus.net> References: <20101115180815.GA4907@patriot.net> <4CE263DB.70102@calamus.net> Message-ID: On Tue, 16 Nov 2010 10:58:35 -0000, Ulf Dunkel wrote: > I guess I would do a simple admin request email for the lists Thanks for the timely reminder ;-) Even with my 'majordomo with only an email interface' history I do rather tend to forget that Mailman has an email interface. Malcolm. -- Malcolm Austen, Oxfordshire, England From andrew at hodgsonfamily.org Tue Nov 16 13:44:22 2010 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Tue, 16 Nov 2010 12:44:22 +0000 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <4CE263DB.70102@calamus.net> References: <20101115180815.GA4907@patriot.net>,<4CE263DB.70102@calamus.net> Message-ID: <3D928760FE9FD24A9F02C485C3F506650D37206774@ELROND.hodgsonfamily.org> Ulf Dunkel wrote: >Hi Alan. >> Is there a command to exhibit all members on one page? or, better >> yet, is there a command an administrator can invoke to have the >> members, if possible with their flags, shipped to my home computer? >I guess I would do a simple admin request email for the lists every now >and then, [...] The issue I have with the roster email is that it doesn't tell you whether the user is on nomail or digest. We had an issue last week where one of my users moved a lists from Freelists to Mailman, and we had a lot of complaints of users starting to receive mail again after going nomail, and digest users not being on digest. Just something to take note of. Andrew. From malcolm.austen at weald.org.uk Tue Nov 16 14:24:24 2010 From: malcolm.austen at weald.org.uk (Malcolm Austen) Date: Tue, 16 Nov 2010 13:24:24 -0000 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <3D928760FE9FD24A9F02C485C3F506650D37206774@ELROND.hodgsonfamily.org> References: <20101115180815.GA4907@patriot.net> <4CE263DB.70102@calamus.net> <3D928760FE9FD24A9F02C485C3F506650D37206774@ELROND.hodgsonfamily.org> Message-ID: On Tue, 16 Nov 2010 12:44:22 -0000, Andrew Hodgson wrote: > The issue I have with the roster email is that it doesn't tell you > whether the user is on nomail or digest. That's only half true! The email response gives two lists - for message and digest subscribers - but does not flag nomail subscribers. The roster web page I mentioned earlier flags both - two columns for message and digest plus (italic) for those set to nomail. Malcolm. -- Malcolm Austen, Oxfordshire, England From alan at patriot.net Tue Nov 16 15:56:02 2010 From: alan at patriot.net (Alan McConnell) Date: Tue, 16 Nov 2010 09:56:02 -0500 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <4CE263DB.70102@calamus.net> References: <20101115180815.GA4907@patriot.net> <4CE263DB.70102@calamus.net> Message-ID: <20101116145602.GD3889@patriot.net> On Tue, Nov 16, 2010 at 11:58:35AM +0100, Ulf Dunkel wrote: > Hi Alan. > > >Is there a command to exhibit all members on one page? or, better > >yet, is there a command an administrator can invoke to have the > >members, if possible with their flags, shipped to my home computer? > > I guess I would do a simple admin request email for the lists every now > and then, something in the format: > > To: _request@ > Subject: who > > This sends an email to your account with a list of all currently stored > members of the list. I just tried this. It works great! I thank Herr Dunkel as well as the other kind and knowledgeable responders who have weighed in. What a great List! Best wishes to all, Alan McConnell, in Silver Spring MD -- Alan McConnell : http://patriot.net/users/alan We live in a world that is full of mistaken policies, but they are not mistaken for their supporters.(George Stigler) From dunkel at calamus.net Wed Nov 17 08:04:08 2010 From: dunkel at calamus.net (Ulf Dunkel) Date: Wed, 17 Nov 2010 08:04:08 +0100 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <3D928760FE9FD24A9F02C485C3F506650D37206774@ELROND.hodgsonfamily.org> References: <20101115180815.GA4907@patriot.net>, <4CE263DB.70102@calamus.net> <3D928760FE9FD24A9F02C485C3F506650D37206774@ELROND.hodgsonfamily.org> Message-ID: <4CE37E68.50601@calamus.net> Hi Andrew. >> I guess I would do a simple admin request email for the lists every now >> and then, [...] > > The issue I have with the roster email is that it doesn't tell you whether the user is on nomail or digest. We had an issue last week where one of my users moved a lists from Freelists to Mailman, and we had a lot of complaints of users starting to receive mail again after going nomail, and digest users not being on digest. > > Just something to take note of. That's true, but that wasn't the OP's topic. :-) In fact, I myself do a cronjob on my server and have the list files backup'ed somewhere. But the mail interface is really handy. ---UlfDunkel From dunkel at calamus.net Wed Nov 17 08:06:47 2010 From: dunkel at calamus.net (Ulf Dunkel) Date: Wed, 17 Nov 2010 08:06:47 +0100 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <20101116145602.GD3889@patriot.net> References: <20101115180815.GA4907@patriot.net> <4CE263DB.70102@calamus.net> <20101116145602.GD3889@patriot.net> Message-ID: <4CE37F07.4060503@calamus.net> Hi Alan. > I just tried this. It works great! I thank Herr Dunkel as > well as the other kind and knowledgeable responders who have > weighed in. What a great List! Oh, not that seriously, just call me Ulf, please. :-) By the way: If you're on a Mac, I'd recommend Simon to auto-send emails every now and then. A great monitoring app from Dejal Systems. http://www.dsd.net/prod/mac/simon.php?lan=en ---UlfDunkel From mark at msapiro.net Wed Nov 17 15:06:46 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 17 Nov 2010 06:06:46 -0800 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <4CE37F07.4060503@calamus.net> Message-ID: Ulf Dunkel wrote: > >By the way: If you're on a Mac, I'd recommend Simon to auto-send emails >every now and then. A great monitoring app from Dejal Systems. > >http://www.dsd.net/prod/mac/simon.php?lan=en I'm guessing the above was prompted by the delay in Alan's followup reaching the list. This delay was due to a moderation hold and was not a sending delay. Also, I find it curious that in this entire thread, I saw no mention of the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rmj at aviation.org Wed Nov 17 17:13:09 2010 From: rmj at aviation.org (Robert M. Jenney) Date: Wed, 17 Nov 2010 11:13:09 -0500 Subject: [Mailman-Users] Backing Up the List of Members In-Reply-To: <20101116145602.GD3889@patriot.net> References: <20101115180815.GA4907@patriot.net> <4CE263DB.70102@calamus.net> <20101116145602.GD3889@patriot.net> Message-ID: <9B683D1FBD2849B5816BC25AD456EAD1@aviationPC> After corresponding with Alan I also got it to work. The "To" address needs a hyphen (-request) not an underscore (_request). Thanks to both Ulf and Alan for a great tip, Bob ____________________________ Robert M. Jenney, Director Aviation Safety Connection, Inc. 11 Lake Street, Unit #121 Wakefield, MA 01880 USA rmj at aviation.org; (781) 245-1391 Go to http://aviation.org _____ From: mailman-users-bounces+rmj=aviation.org at python.org [mailto:mailman-users-bounces+rmj=aviation.org at python.org] On Behalf Of Alan McConnell Sent: Tuesday, November 16, 2010 9:56 AM To: Ulf Dunkel Cc: mailman-users at python.org Subject: Re: [Mailman-Users] Backing Up the List of Members On Tue, Nov 16, 2010 at 11:58:35AM +0100, Ulf Dunkel wrote: > Hi Alan. > > >Is there a command to exhibit all members on one page? or, better > >yet, is there a command an administrator can invoke to have the > >members, if possible with their flags, shipped to my home computer? > > I guess I would do a simple admin request email for the lists every now > and then, something in the format: > > To: _request@ > Subject: who > > This sends an email to your account with a list of all currently stored > members of the list. I just tried this. It works great! I thank Herr Dunkel as well as the other kind and knowledgeable responders who have weighed in. What a great List! Best wishes to all, Alan McConnell, in Silver Spring MD -- Alan McConnell : http://patriot.net/users/alan We live in a world that is full of mistaken policies, but they are not mistaken for their supporters.(George Stigler) ------------------------------------------------------ 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/rmj%40aviation.org _____ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1153 / Virus Database: 424/3260 - Release Date: 11/16/10 From barellin at owu.edu Wed Nov 17 16:54:04 2010 From: barellin at owu.edu (Brian A. Rellinger) Date: Wed, 17 Nov 2010 10:54:04 -0500 Subject: [Mailman-Users] Digest Specific Messages Message-ID: Hello, We are wondering if it is possible for an email list approver to be able to select some messages for immediate delivery to all subscribers (even if the subscriber has elected digest mode), and send other messages in a digest, again, regardless of user settings. For example, we have 3 emails sent today about events that are scheduled for next week. For each of those messages, the approver would like to select "Send via Digest", at which point, the system would combine the emails into one daily message, irrespective of subscriber specific settings. However, perhaps there is one message sent that day that should go to all users immediately regardless of their preferences. Is that possible? I dug around on the wiki and through the archives and was not able to find this question. Thanks, Brian -- Brian A. Rellinger Executive Director of Information Services Ohio Wesleyan University 61 S. Sandusky Street Delaware, Ohio 43015 Phone: 740-368-3131 http://twitter.com/rellinb http://barellin.blogspot.com/ -- From mark at msapiro.net Thu Nov 18 08:42:14 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 17 Nov 2010 23:42:14 -0800 Subject: [Mailman-Users] Digest Specific Messages In-Reply-To: Message-ID: Brian A. Rellinger wrote: >Hello, >We are wondering if it is possible for an email list approver to be able to >select some messages for immediate delivery to all subscribers (even if the >subscriber has elected digest mode), and send other messages in a digest, >again, regardless of user settings. The short answer is no. If admin_immed_notify is yes, the moderator will receive a notice of the held post which contains the original post. The moderator could add an Urgent: moderator_password header to that post and resend it to the list. The Urgent: header with a valid list admin or moderator password will cause the message to be delivered when processed to all list members both regular and digest including those with delivery disabled. This does not result in delivery of the original post but rather the resent post from the moderator. Also, the Urgent: header must be a true header and not a "first body line" pseudo header. Thus, this can be used to accomplish something like part 1 of your request although it is certainly more cumbersome than you envision. There is no way to get Mailman to send a digest to regular (non-digest) list members -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From halfcountplus at intergate.com Thu Nov 18 17:48:35 2010 From: halfcountplus at intergate.com (MK) Date: Thu, 18 Nov 2010 11:48:35 -0500 Subject: [Mailman-Users] post as administrator Message-ID: <20101118114835.aedfc13c.halfcountplus@intergate.com> I've just started an "announcements only" mail list. That is, I have it set to discard posts from non-members, and to reject posts from members with a explanatory message. This works, however, I cannot post to the list either, although my email is listed as the administrator. I tried subscribing, but then I get treated as a member: my mail is rejected. How can I set this up? Do I have to briefly change the configuration, post my announcement, approve my own post, and then change the configuration back to reject? -- "The angel of history[...]is turned toward the past." (Walter Benjamin) From halfcountplus at intergate.com Thu Nov 18 18:07:19 2010 From: halfcountplus at intergate.com (MK) Date: Thu, 18 Nov 2010 12:07:19 -0500 Subject: [Mailman-Users] post as administrator In-Reply-To: <20101118114835.aedfc13c.halfcountplus@intergate.com> References: <20101118114835.aedfc13c.halfcountplus@intergate.com> Message-ID: <20101118120719.192f574a.halfcountplus@intergate.com> On Thu, 18 Nov 2010 11:48:35 -0500 MK wrote: > How can I set this up? Okay, I've resolved this by unsubscribing myself then adding my address to the "List of non-member addresses whose postings should be automatically accepted". -- "The angel of history[...]is turned toward the past." (Walter Benjamin) From mark at msapiro.net Fri Nov 19 16:24:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 19 Nov 2010 07:24:45 -0800 Subject: [Mailman-Users] post as administrator In-Reply-To: <20101118120719.192f574a.halfcountplus@intergate.com> Message-ID: MK wrote: > >Okay, I've resolved this by unsubscribing myself then adding >my address to the "List of non-member addresses whose postings should >be automatically accepted". As you have seen, the list owner is not a member by default and has no special posting privileges. See the FAQ at . What you have done works OK, but it is subject to unauthorized posts from someone spoofing your address which will be well known if your list is not anonymous. A more secure way to post is to not put your address in accept_these_nonmembers, and post with an Approved: header. See the "How to post to the announcement list" section at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From halfcountplus at intergate.com Fri Nov 19 20:43:07 2010 From: halfcountplus at intergate.com (MK) Date: Fri, 19 Nov 2010 14:43:07 -0500 Subject: [Mailman-Users] post as administrator In-Reply-To: References: <20101118120719.192f574a.halfcountplus@intergate.com> Message-ID: <20101119144307.d0762922.halfcountplus@intergate.com> On Fri, 19 Nov 2010 07:24:45 -0800 Mark Sapiro wrote: > What you have done works OK, but it is subject to unauthorized posts > from someone spoofing your address which will be well known if your > list is not anonymous. It is anonymous, but it is not too many steps from someone making the connection, and since I am promising users no spam: thanks much for that point! A more secure way to post is to not put your > address in accept_these_nonmembers, and post with an Approved: > header. See the "How to post to the announcement list" > section at . Thanks again. Since I am lazy and the list will be very seldom used anyway, I think I will just delete my address from accept_these_nonmembers except temporarily when there needs to be an announcement. But it is nice to at least know about "the right way". -- "The angel of history[...]is turned toward the past." (Walter Benjamin) From halfcountplus at intergate.com Fri Nov 19 20:43:17 2010 From: halfcountplus at intergate.com (MK) Date: Fri, 19 Nov 2010 14:43:17 -0500 Subject: [Mailman-Users] post as administrator In-Reply-To: <91E39539CE412749B03E22697A8F4367089C82@Klinger.gsw.local> References: <20101118114835.aedfc13c.halfcountplus@intergate.com> <91E39539CE412749B03E22697A8F4367089C82@Klinger.gsw.local> Message-ID: <20101119144317.df9693a6.halfcountplus@intergate.com> On Fri, 19 Nov 2010 15:07:24 +0000 Tim Faircloth wrote: > The best way to do this is to subscribe users with the mod option > (first column of the Membership List page), then uncheck the Mod > option for people you want to post to the list. That is also vulnerable to spoofing. -- "The angel of history[...]is turned toward the past." (Walter Benjamin) From halfcountplus at intergate.com Fri Nov 19 20:56:07 2010 From: halfcountplus at intergate.com (MK) Date: Fri, 19 Nov 2010 14:56:07 -0500 Subject: [Mailman-Users] "Edit public HTML" Message-ID: <20101119145607.40425b5f.halfcountplus@intergate.com> I have a list hosted by sourceforge (meaning I only have the web interface to use). The list is set up for announcements only. In a reply to a previous post here, someone pointed me to: http://wiki.list.org/x/3YA9 While I am not using this method, I did notice this part: "if you don't have write access to Mailman's directories and files, then you won't be able to create a customized welcome message for your list. Beginning with Mailman 2.1.6, you can edit the welcome message via the 'Edit the public HTML pages and text files' link in the web admin interface." This caught my attention because I have added a welcome msg which says the list is for announcements only, but this gets added to it in the actual mail: "To post to this list, send your email to:" Which is contradictory. The general information page is similarly confusing. No big deal, but I presume "editing the public HTML pages" might provide a solution. Unfortunately, I cannot find this option... Sourceforge uses ver. 2.1.9. MK -- "The angel of history[...]is turned toward the past." (Walter Benjamin) From mark at msapiro.net Fri Nov 19 21:17:16 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 19 Nov 2010 12:17:16 -0800 Subject: [Mailman-Users] "Edit public HTML" In-Reply-To: <20101119145607.40425b5f.halfcountplus@intergate.com> Message-ID: MK wrote: >This caught my attention because I have added a welcome msg which says >the list is for announcements only, but this gets added to it in the >actual mail: > >"To post to this list, send your email to:" > >Which is contradictory. The general information page is similarly >confusing. > >No big deal, but I presume "editing the public HTML pages" might >provide a solution. Unfortunately, I cannot find this >option... On the same General Options page where you added the welcome_msg text (and other web admin interface pages), at the upper right there should be a column of "Other Administrative Activities" links. One of these is "Edit the public HTML pages and text files". Following that link will take you to a page where you can select and edit "Welcome email text file". You can also edit the "General list information page" from there. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fmouse-mailman at fmp.com Fri Nov 19 21:17:49 2010 From: fmouse-mailman at fmp.com (Lindsay Haisley) Date: Fri, 19 Nov 2010 14:17:49 -0600 Subject: [Mailman-Users] "Edit public HTML" In-Reply-To: <20101119145607.40425b5f.halfcountplus@intergate.com> References: <20101119145607.40425b5f.halfcountplus@intergate.com> Message-ID: <1290197869.8377.82.camel@vishnu.fmp.com> On Fri, 2010-11-19 at 14:56 -0500, MK wrote: > No big deal, but I presume "editing the public HTML pages" might > provide a solution. Unfortunately, I cannot find this > option... > > Sourceforge uses ver. 2.1.9. On the main administrative page menu, it's on the far right - "Edit the public HTML pages and text files" - under Other Administrative Activities. It's in 2.1.12. Isn't this in 2.1.9 also? -- Lindsay Haisley | "Never expect the people who caused a problem FMP Computer Services | to solve it." - Albert Einstein 512-259-1190 | http://www.fmp.com | From halfcountplus at intergate.com Fri Nov 19 21:24:13 2010 From: halfcountplus at intergate.com (MK) Date: Fri, 19 Nov 2010 15:24:13 -0500 Subject: [Mailman-Users] "Edit public HTML" In-Reply-To: References: <20101119145607.40425b5f.halfcountplus@intergate.com> Message-ID: <20101119152413.797dc3cd.halfcountplus@intergate.com> On Fri, 19 Nov 2010 12:17:16 -0800 Mark Sapiro wrote: > On the same General Options page where you added the welcome_msg text > (and other web admin interface pages), at the upper right there should > be a column of "Other Administrative Activities" links. One of these > is "Edit the public HTML pages and text files". There is the "Other Administrative Activities" column, but no "Edit the public HTML pages" -- presumably sourceforge does not want this. Sigh. I guess I'll bug them about it. -- "The angel of history[...]is turned toward the past." (Walter Benjamin) From jbernier at risd.edu Fri Nov 19 22:14:44 2010 From: jbernier at risd.edu (Jeff Bernier) Date: Fri, 19 Nov 2010 16:14:44 -0500 Subject: [Mailman-Users] Can't access list archives Message-ID: Hello all, I changed an existing list's archive from Public to Private, but now cannot access the archive. I am using my list subscriber email address and password, trying to log in to the "Lists Private Archives Authentication" page. Do I need to do something else (other than un-ticking/ticking public/private in the list's web admin interface) to make the archives private, and accessible? I'm running Mailman 2.1.13 Any help is appreciated. Jeff Bernier Office of Information Technology Rhode Island School of Design 401.454.6168 From adamsca at gmail.com Fri Nov 19 23:51:01 2010 From: adamsca at gmail.com (Christopher Adams) Date: Fri, 19 Nov 2010 14:51:01 -0800 Subject: [Mailman-Users] question about logging subscription changes Message-ID: I think that the answer is 'no', but I thought I would check. Do any of the mailman log files show when a subscription is changed from a regular subscription to digest? I have parsed the logs and can't find evidence of this. -- Christopher Adams adamsca at gmail.com From mark at msapiro.net Sat Nov 20 02:44:13 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 19 Nov 2010 17:44:13 -0800 Subject: [Mailman-Users] question about logging subscription changes In-Reply-To: Message-ID: Christopher Adams wrote: >I think that the answer is 'no', but I thought I would check. Do any >of the mailman log files show when a subscription is changed from a >regular subscription to digest? I have parsed the logs and can't find >evidence of this. You are correct. The answer is 'no'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rhaas at rhaas.us Mon Nov 22 15:58:00 2010 From: rhaas at rhaas.us (Richard Haas) Date: Mon, 22 Nov 2010 09:58:00 -0500 Subject: [Mailman-Users] mailman without virtual domains Message-ID: Greetings. I'm installing mailman 2.1.14 onto an Ubuntu server that previously had mailman 2.1.13 installed, and it looks like the 2.1.13 install left some virtual domain artifacts behind, namely: /etc/postfix/transport, containing: [my system's hostname] mailman: ... and the usual postifix transport lines in master.cf: mailman unix - n n - - pipe flags=FR user=list argv=/usr/local/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} I currently have no need for virtual domains, but was wondering: - Is there any advantage besides being able to trivially enable virtual domains, to maintaining a separate transport for mailman? - What is the default transport that should be used by mailman 2.1.14 if no virtual domains are needed -- smtp? Thanks. -- Richard Haas GnuPG public key ID: 1CB7F0E2 -- From mark at msapiro.net Tue Nov 23 02:10:54 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 22 Nov 2010 17:10:54 -0800 Subject: [Mailman-Users] mailman without virtual domains In-Reply-To: Message-ID: Richard Haas wrote: > >I'm installing mailman 2.1.14 onto an Ubuntu server that previously had >mailman 2.1.13 installed, and it looks like the 2.1.13 install left some >virtual domain artifacts behind, namely: > >/etc/postfix/transport, containing: > >[my system's hostname] mailman: > >... and the usual postifix transport lines in master.cf: > >mailman unix - n n - - pipe > flags=FR user=list argv=/usr/local/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} > >I currently have no need for virtual domains, but was wondering: > > - Is there any advantage besides being able to trivially enable virtual >domains, to maintaining a separate transport for mailman? postfix_to_mailman.py is a third party script officially unsupported by the GNU Mailman project. It is used by Debian/Ubuntu and they may or may not provide support for its use. It isn't virtual domain support per se. It is designed to be used where all Mailman lists on a server are in a single domain (often lists.example.com) that has few if any local user addresses. > - What is the default transport that should be used by mailman 2.1.14 if >no virtual domains are needed -- smtp? Postfix local delivery together with aliases, the generation of which can be automated. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Nov 23 02:22:07 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 22 Nov 2010 17:22:07 -0800 Subject: [Mailman-Users] Can't access list archives In-Reply-To: Message-ID: Jeff Bernier wrote: > >On Fri, Nov 19, 2010 at 8:35 PM, Mark Sapiro wrote: > >> What happens when you try to log in? > >When I try to log in, nothing happens. I'm just left at the archives auth >screen with blank entry fields. I made sure I have cookies enabled. I have >tried with both IE and FireFox. Does the resultant page have an "Authorization Failed" or other message at the top? I assume that you can successfully log in to the web admin and admindb interfaces for this list. If the URL you're using to access the archive of this list exactly the same as the admin or admindb URL except for admin or admindb being replaced with private? If you view the source of the archive login page, is the ACTION= URL in the FORM tag also exactly the same as the admin or admindb URL except for admin or admindb being replaced with private? The FAQ at may be relevant, but that would also affect login to the web admin and admindb interface. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sergeimaertens at gmail.com Tue Nov 23 22:10:45 2010 From: sergeimaertens at gmail.com (Sergei Maertens) Date: Tue, 23 Nov 2010 22:10:45 +0100 Subject: [Mailman-Users] Recipient address rejected Message-ID: Hi all, I have been googling around the past day, but I can't seem to get this fixed: >: host mydomain.com[1.2.3.4] > said: 550 5.1.1 : Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) Final-Recipient: rfc822;test2 at mydomain.com Original-Recipient: rfc822; test2 at m ydomain.com Action: failed Status: 5.1.1 Remote-MTA: dns; test2 at mydomain.com Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table These are the most important parts from te configfiles: /etc/postfix/main.cf > myhostname = mydomain.com > > alias_maps = hash:/etc/aliases > > alias_database = hash:/etc/aliases > > myorigin = /etc/mailname > > mydestination = mydomain.com, , localhost > > relayhost = smtprelay.ugent.be > > mynetworks = 127.0.0.0/8 # [::ffff:127.0.0.0]/104 [::1]/128 > > mailbox_command = #procmail -a "$EXTENSION" > > mailbox_size_limit = 0 > > recipient_delimiter = + > > inet_interfaces = all > > inet_protocols = all > > home_mailbox = Maildir/ > > smtpd_sasl_local_domain = > > smtpd_sasl_auth_enable = yes > > smtpd_sasl_security_options = noanonymous > > broken_sasl_auth_clients = yes > > smtpd_recipient_restrictions = >> permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination > > smtp_tls_security_level = may > > smtpd_tls_security_level = may > > smtpd_tls_auth_only = no > > smtp_tls_note_starttls_offer = yes > > smtpd_tls_CAfile = /etc/ssl/certs/cacert.pem > > smtpd_tls_loglevel = 1 > > smtpd_tls_received_header = yes > > smtpd_tls_session_cache_timeout = 3600s > > tls_random_source = dev:/dev/urandom > > transport_maps = hash:/etc/postfix/transport > > mailman_destination_recipient_limit = 1 > > > > DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST are both set to mydomain.com in /etc/mailman/mm_cfg.py. MTA=None /etc/postfix/transport contains: mydomain.com mailman: I followed the guide at https://help.ubuntu.com/community/Mailman Any help, please? I'm getting pretty desperate... Greetings, Sergei -- Sergei Maertens Commissie ICT Home Boudewijn 2010-2011 ICT Home Konvent 2010-2011 Vaste Medewerker Web/ICT VTK 2009-2011 From mark at msapiro.net Tue Nov 23 23:57:43 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 23 Nov 2010 14:57:43 -0800 Subject: [Mailman-Users] Recipient address rejected In-Reply-To: Message-ID: Sergei Maertens wrote: > >>: host mydomain.com[1.2.3.4] >> said: 550 5.1.1 > > : Recipient address rejected: User unknown in local > > recipient table (in reply to RCPT TO command) > > >Final-Recipient: rfc822;test2 at mydomain.com > >Original-Recipient: rfc822; test2 at m >ydomain.com > >Action: failed > >Status: 5.1.1 > >Remote-MTA: dns; test2 at mydomain.com > >Diagnostic-Code: smtp; 550 5.1.1 : Recipient address > > rejected: User unknown in local recipient table > >These are the most important parts from te configfiles: > >/etc/postfix/main.cf > >> myhostname = mydomain.com >> >> alias_maps = hash:/etc/aliases >> >> alias_database = hash:/etc/aliases >> >> myorigin = /etc/mailname >> >> mydestination = mydomain.com, , localhost >> >> relayhost = smtprelay.ugent.be >> >> mynetworks = 127.0.0.0/8 # [::ffff:127.0.0.0]/104 [::1]/128 >> >> mailbox_command = #procmail -a "$EXTENSION" >> >> mailbox_size_limit = 0 >> >> recipient_delimiter = + >> >> inet_interfaces = all >> >> inet_protocols = all >> >> home_mailbox = Maildir/ >> >> smtpd_sasl_local_domain = >> >> smtpd_sasl_auth_enable = yes >> >> smtpd_sasl_security_options = noanonymous >> >> broken_sasl_auth_clients = yes >> >> smtpd_recipient_restrictions = >>> permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination >> >> smtp_tls_security_level = may >> >> smtpd_tls_security_level = may >> >> smtpd_tls_auth_only = no >> >> smtp_tls_note_starttls_offer = yes >> >> smtpd_tls_CAfile = /etc/ssl/certs/cacert.pem >> >> smtpd_tls_loglevel = 1 >> >> smtpd_tls_received_header = yes >> >> smtpd_tls_session_cache_timeout = 3600s >> >> tls_random_source = dev:/dev/urandom >> >> transport_maps = hash:/etc/postfix/transport >> >> mailman_destination_recipient_limit = 1 >> >> >> >> DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST are both set to mydomain.com in >/etc/mailman/mm_cfg.py. >MTA=None > >/etc/postfix/transport contains: >mydomain.com mailman: > >I followed the guide at https://help.ubuntu.com/community/Mailman Which is for installation of the Debian/Ubuntu Mailman package using the officially unsupported by the GNU Mailman project postfix_to_mailman.py script for delivery to Mailman. That said, There is something amis, as your list mail is apparently being handled by Postfix's local transport (per the "User unknown in local recipient table" error) and not by the 'mailman' transport specified in /etc/postfix/transport. Is the mailman transport defined in master.cf? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From scott at 916networks.com Wed Nov 24 00:26:26 2010 From: scott at 916networks.com (Scott Race) Date: Tue, 23 Nov 2010 16:26:26 -0700 Subject: [Mailman-Users] Mailman server consuming entire Internet pipe (dual T1) In-Reply-To: References: Message-ID: Hello, Starting Friday this particular office started having massive Internet trouble (dual T1s). Running a speedtest shows 2.75Mbps download (fine) and about .09Mbps upload (not fine). There are about 15 active lists on this server, a few of the lists have a few thousand members. We traced the network issues to our mailman server. With Mailman server turned off, network is fine. As soon as it comes back up, bandwidth consumed. Using Postfix as the MTA, set the default_process_limit to 3 in the master.cf file. Other settings are postfix defaults (main.cf) Haven't been able to figure out exactly what's up - but I do know if I set an iptables rule to block all inbound port 25 traffic, issues go away - so... I've done some basic testing for open relays, so far I have not found anything indicating it's an open relay. Packet sniffing shows connections from a number of IP addresses to the Mailman server. Outside test shows the hostname is not an open relay, and I can't telnet on port 25 with standard HELO command. All internal mail comes to a Barrucuda spam filter unit. /usr/local/mailman/logs/post shows 19 posts today to the various lists. from my main.cf: mynetworks = 172.10.0.0/16, 127.0.0.0/8 #relay_domains = $mydestination mydestination = $myhostname, $mydomain, localhost myhostname = lists.lists.mydomain.com mydomain = lists.mydomain.com At this point I can't tell if I have a Postfix problem or Mailman problem. Any ideas? Thanks!! Scott From mark at msapiro.net Wed Nov 24 01:15:47 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 23 Nov 2010 16:15:47 -0800 Subject: [Mailman-Users] Mailman server consuming entire Internet pipe (dualT1) In-Reply-To: Message-ID: Scott Race wrote: > >Haven't been able to figure out exactly what's up - but I do know if I set an iptables rule to block all inbound port 25 traffic, issues go away - so... So, assuming you are also blocking port 25 connects from the local host via the loopback interface, you are blocking Mailman's connects to Postfix, thus preventing Mailman from connecting to Postfix and the resultant sending from Postfix of whatever Mailman is sending. Take a look at Mailman's queues, particularly virgin, out and retry to see what's there. Use Mailman's bin/dumpdb to see an individual entry's message and metadata or bin/show_quefiles to see one or more entries' messages. [...] >At this point I can't tell if I have a Postfix problem or Mailman problem. Any ideas? Thanks!! I suspect the actual network traffic is coming from Postfix sending the stuff that Mailman is delivering to it. The question is what is Mailman doing. Check the queues as above and also Mailman's smtp and perhaps other logs. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Wed Nov 24 19:34:28 2010 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Wed, 24 Nov 2010 18:34:28 +0000 Subject: [Mailman-Users] Mailman server consuming entire Internet pipe (dual T1) In-Reply-To: References: Message-ID: <3D928760FE9FD24A9F02C485C3F506650D3720B99D@ELROND.hodgsonfamily.org> Scott Race wrote: [...] >I've done some basic testing for open relays, so far I have not found anything indicating it's an open relay. Packet sniffing shows connections >from a number of IP addresses to the Mailman server. Outside test shows the hostname is not an open relay, and I can't telnet on port 25 with >standard HELO command. All internal mail comes to a Barrucuda spam filter unit. >/usr/local/mailman/logs/post shows 19 posts today to the various lists. The Postfix logs would be of more benefit I think here, as well as the mail queue. You say you route mails through a Barracuda host, do you allow traffic directly into this machine on port 25 externally? Is this machine hosting lists only, and if so, how is the Barracuda/Postfix server verifying recipients as early as possible (in case the domain is receiving large amounts of bounced mail and is rejecting with a full NDR and not a bounce at SMTP stage? Does outbound mail get delivered direct from Postfix or are you smarthosting to the Barracuda? Thanks. Andrew. From scott at 916networks.com Wed Nov 24 19:58:48 2010 From: scott at 916networks.com (Scott Race) Date: Wed, 24 Nov 2010 11:58:48 -0700 Subject: [Mailman-Users] Change list admin password, old one and new one works In-Reply-To: <3D928760FE9FD24A9F02C485C3F506650D3720B99D@ELROND.hodgsonfamily.org> References: <3D928760FE9FD24A9F02C485C3F506650D3720B99D@ELROND.hodgsonfamily.org> Message-ID: In going through some security procedures yesterday, we decided to change our list passwords on all our lists. The new password works, as does the old one still. Restarting mailmanctl process does not fix. We are running Mailman 2.1.13 on RHEL5. Any ideas? Haven't restarted the server yet. Thanks. Scott From scott at 916networks.com Wed Nov 24 19:55:29 2010 From: scott at 916networks.com (Scott Race) Date: Wed, 24 Nov 2010 11:55:29 -0700 Subject: [Mailman-Users] Mailman server consuming entire Internet pipe (dual T1) In-Reply-To: <3D928760FE9FD24A9F02C485C3F506650D3720B99D@ELROND.hodgsonfamily.org> References: <3D928760FE9FD24A9F02C485C3F506650D3720B99D@ELROND.hodgsonfamily.org> Message-ID: Was scrolling through the maillog just now, nothing out of the ordinary other than list traffic that I can tell. So no, all inbound mail comes to the Barracuda, gets cleaned and sent to the Mailman server. Each day about 600 inbound junk mails get blocked and around 50 legit emails. It is hosting just lists only, no other inbound or outbound mail. Outbound does get sent directly out the Postfix and is not sent through any smart host. Good question on the verifying recipients - not quite sure the exact answer - I think the mailman server is processing bounces because I'll see bounced emails in the log to "johnsmith at lists.mydomain.com does not exist". So invalid recipients do seem to hit the Mailman server. Maybe filtering recipients at the Barrcuda could help? On the note of the traffic - today everything is fine. Not sure why for 5 days it was consuming the pipe, but have not found any indication of an open relay or malicious intent. We did throttle back the simulaneous connections, maybe that will help a bit. My Postfix maillog shows a ton of these: (lost connection with spool.santarosa.org[216.222.240.7] while sending end of data -- message may be sent more than once) and (conversation with mail.laguna-hills.ca.us[68.203.215.26] timed out while sending end of data -- message may be sent more than once) 11,968 matches of (lost connection) and 9202 matches of (conversation with) in a log file covering 4 days (Nov 21 01:18 - Nov 24 9:07). One thing that did change was the internal DNS servers on the network, I almost have to assume it has to do with that..... -----Original Message----- From: Andrew Hodgson [mailto:andrew at hodgsonfamily.org] Sent: Wednesday, November 24, 2010 10:34 AM To: Scott Race; mailman-users at python.org Subject: RE: [Mailman-Users] Mailman server consuming entire Internet pipe (dual T1) Scott Race wrote: [...] >I've done some basic testing for open relays, so far I have not found anything indicating it's an open relay. Packet sniffing shows connections >from a number of IP addresses to the Mailman server. Outside test shows the hostname is not an open relay, and I can't telnet on port 25 with >standard HELO command. All internal mail comes to a Barrucuda spam filter unit. >/usr/local/mailman/logs/post shows 19 posts today to the various lists. The Postfix logs would be of more benefit I think here, as well as the mail queue. You say you route mails through a Barracuda host, do you allow traffic directly into this machine on port 25 externally? Is this machine hosting lists only, and if so, how is the Barracuda/Postfix server verifying recipients as early as possible (in case the domain is receiving large amounts of bounced mail and is rejecting with a full NDR and not a bounce at SMTP stage? Does outbound mail get delivered direct from Postfix or are you smarthosting to the Barracuda? Thanks. Andrew. From andrew at hodgsonfamily.org Wed Nov 24 20:14:54 2010 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Wed, 24 Nov 2010 19:14:54 +0000 Subject: [Mailman-Users] Change list admin password, old one and new one works In-Reply-To: References: <3D928760FE9FD24A9F02C485C3F506650D3720B99D@ELROND.hodgsonfamily.org> Message-ID: <3D928760FE9FD24A9F02C485C3F506650D3720B9A2@ELROND.hodgsonfamily.org> Scott Race wrote: >In going through some security procedures yesterday, we decided to change our list passwords on all our lists. >The new password works, as does the old one still. Restarting mailmanctl process does not fix. If the list shared the old password with the site password, then using the old password (i.e, the site password) will get you past most password prompts in Mailman. http://wiki.list.org/pages/viewpage.action?pageId=4030543 Andrew. From scott at 916networks.com Wed Nov 24 20:16:35 2010 From: scott at 916networks.com (Scott Race) Date: Wed, 24 Nov 2010 12:16:35 -0700 Subject: [Mailman-Users] Mailman server consuming entire Internet pipe (dualT1) In-Reply-To: References: Message-ID: Thanks for the reply. So it sounds like my iptables rule: iptables -A INPUT -p tcp --dport 25 -j REJECT also blocks outbound mail too. Is there a preferred way to secure mailman SMTP traffic with iptables? In our case, we would just need an inbound filter that only accepts mail from a few hosts, I thought this would do it, but mailman wouldn't send mail with rules like this: # accept mail from two hosts, drop the rest iptables -A INPUT -p tcp -s 192.168.1.245 --dport 25 -j ACCEPT iptables -A INPUT -p tcp -s 192.168.1.246 --dport 25 -j ACCEPT iptables -A INPUT -p tcp --dport 25 -j REJECT For the queues - I guess it's fine today - still reviewing the logs, and I will use those bin utilities to see the messages, that will be helpful...thanks!! Scott -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Tuesday, November 23, 2010 4:16 PM To: Scott Race; mailman-users at python.org Subject: Re: [Mailman-Users] Mailman server consuming entire Internet pipe (dualT1) Scott Race wrote: > >Haven't been able to figure out exactly what's up - but I do know if I set an iptables rule to block all inbound port 25 traffic, issues go away - so... So, assuming you are also blocking port 25 connects from the local host via the loopback interface, you are blocking Mailman's connects to Postfix, thus preventing Mailman from connecting to Postfix and the resultant sending from Postfix of whatever Mailman is sending. Take a look at Mailman's queues, particularly virgin, out and retry to see what's there. Use Mailman's bin/dumpdb to see an individual entry's message and metadata or bin/show_quefiles to see one or more entries' messages. [...] >At this point I can't tell if I have a Postfix problem or Mailman problem. Any ideas? Thanks!! I suspect the actual network traffic is coming from Postfix sending the stuff that Mailman is delivering to it. The question is what is Mailman doing. Check the queues as above and also Mailman's smtp and perhaps other logs. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 25 00:49:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 24 Nov 2010 15:49:32 -0800 Subject: [Mailman-Users] Mailman server consuming entire Internet pipe (dualT1) In-Reply-To: References: Message-ID: <4CEDA48C.40700@msapiro.net> On 11/24/2010 11:16 AM, Scott Race wrote: > Thanks for the reply. > > So it sounds like my iptables rule: > > iptables -A INPUT -p tcp --dport 25 -j REJECT > > also blocks outbound mail too. Is there a preferred way to secure mailman SMTP traffic with iptables? In our case, we would just need an inbound filter that only accepts mail from a few hosts, I thought this would do it, but mailman wouldn't send mail with rules like this: > > # accept mail from two hosts, drop the rest > iptables -A INPUT -p tcp -s 192.168.1.245 --dport 25 -j ACCEPT > iptables -A INPUT -p tcp -s 192.168.1.246 --dport 25 -j ACCEPT > iptables -A INPUT -p tcp --dport 25 -j REJECT I can't really answer that without knowing much more detail about your Mailman/Barracuda/Postfix configuration, but by default, Mailman delivers output (all list posts and other messages FROM Mailman) via SMTP to the MTA listening on localhost port 25 (127.0.0.1:25). If you reject packets with addressed to port 25, Mailman won't be able to deliver anything. Every message in the out/ queue will result in a connection refused upon attempted delivery and will be logged in Mailman's smtp-failure log and put in the retry/ queue to be retried at intervals of DELIVERY_RETRY_WAIT (default 1 hour) for a total time of DELIVERY_RETRY_PERIOD (default 5 days). Accepting port 25 connects from 192.168.1.245 and 192.168.1.246 probably won't help at all with Mailman's outgoing delivery as those connects come from localhost (127.0.0.1). As far as delivery of Mail to Mailman is concerned, this mail is queued by Postfix in Mailman's queues so it gets to the Barracuda appliance somehow which then delivers it to Postfix on some port other than 25 and Postfix either pipes it to Mailman's mail wrapper based on aliases or perhaps via some script like postfix_to_mailman.py depending on how Postfix is configured, and Mailman's Mail wrapper queues the message for Mailman. If you want to secure all SMTP traffic, I suggest you set up a separate SMTP listener in Postfix on some unused port and tell Mailman to deliver to that port by setting SMTPPORT in mm_cfg.py. Then you can block port 25 with iptables or just configure Postfix to not listen on port 25 at all. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From simonvdm at snowball.co.za Wed Nov 24 08:24:26 2010 From: simonvdm at snowball.co.za (Simon) Date: Wed, 24 Nov 2010 09:24:26 +0200 Subject: [Mailman-Users] Disabling excessive bounces Message-ID: Hello, I'm having trouble with a list where members are continuously disabled due to excessive bounces. I want to disable bounce removal but I'm not sure how. I've fiddled with the settings under bounce processing but so far nothing I do there is helping. I'm new to mailman so sorry if this is basic but Googling the problem has just resulted in more confusion. thanks simon From alexander at edem.g12.br Wed Nov 24 17:36:13 2010 From: alexander at edem.g12.br (=?ISO-8859-1?Q?AlexanDER Franca?=) Date: Wed, 24 Nov 2010 14:36:13 -0200 Subject: [Mailman-Users] Ancient messages Message-ID: <20101124163613.D2CA958999@hm4094.locaweb.com.br> Hi. Excuse my English. I'm in a crisis here. Something went wrong and Mailman stoped working. So, I've run 'mailmanctl -s start' because after the first try Mailman said that there was a lock. And Mailman starts sending again ALL the messages that was sent until today. I mean, every message!! I don't know how to fix that. I've cleaned/removed all files in qfiles directory, restarted Postfix, restarted Mailman, killed all mailman process and start again. After some seconds a huge amount of ancient messages floods my server again. How can I clear EVERYTHING that is stored in Mailman? []s Alexander From gdelfino at umich.edu Wed Nov 24 23:45:17 2010 From: gdelfino at umich.edu (Gustavo Delfino) Date: Wed, 24 Nov 2010 18:15:17 -0430 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" Message-ID: Hello, I am migrating my mailing lists from an old cpanel server into a new CentOS 5.5 server (with Webmin). The old server had mailman 2.1.14 installed, on the new one the latest mailman package available is v2.1.9. As I didn't want want to risk migrating my data from a newer version to an older version, I compiled my own mailman 2.1.14 like this: ./configure --with-cgi-gid=apache And for he most part it seems to be working (web pages work, can create lists and subscribe users, and email notifications are received). But, delivering a message to subscribed users is not working. I am getting this inside /var/log/maillog: Nov 24 14:46:10 admin postfix/virtual[17880]: 94B1C2FA8016: to=<|/usr/local/mailman/mail/mailman post testlist5 at gdsolutions.com.ve>, orig_to=, relay=virtual, delay=0.02, delays=0.01/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "|/usr/local/mailman/mail/mailman post testlist5 at gdsolutions.com.ve") As I have spent days trying to make this work, I decided to ask for help. At this point, I am thinking about recompiling mailman with a custom --with-mail-gid. Any advices? This is my setup: python 2.4.3 postfix 2.3.3 spamassassin installed as a daemon virtual domains & virtual mailboxes I can send full configuration details as needed. Regards, -- Gustavo Delfino GPG key ID: AA4063D6 From mark at msapiro.net Thu Nov 25 16:48:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 25 Nov 2010 07:48:40 -0800 Subject: [Mailman-Users] Disabling excessive bounces In-Reply-To: Message-ID: Simon wrote: > >I'm having trouble with a list where members are continuously disabled due >to excessive bounces. I want to disable bounce removal but I'm not sure how. >I've fiddled with the settings under bounce processing but so far nothing I >do there is helping. I'm new to mailman so sorry if this is basic but >Googling the problem has just resulted in more confusion. Just set Should Mailman perform automatic bounce processing? (Details for bounce_processing) to No on the web admin Bounce processing page. If you want to continue to process bounces, but disable automatic removal, you can't do that, but you could set bounce_you_are_disabled_warnings to a large number so members whose delivery is disabled by bounce would not be removed for years. If you don't want to disable delivery at all due to bouncing, then turn off bounce processing as above. The real solution though is to understand why these members mail is bouncing and to fix that issue. As long as bounce_processing is Yes and bounce_notify_owner_on_disableis Yes, the list owner will be sent a copy of the disabling bounce which may help diagnose the issue. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 25 16:54:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 25 Nov 2010 07:54:40 -0800 Subject: [Mailman-Users] Ancient messages In-Reply-To: <20101124163613.D2CA958999@hm4094.locaweb.com.br> Message-ID: AlexanDER Franca wrote: > >Something went wrong and Mailman stoped working. > >So, I've run 'mailmanctl -s start' because after the first try Mailman said that there was a lock. See the FAQ at and make sure that only one of each of Mailman's qrunners is running. >And Mailman starts sending again ALL the messages that was sent until today. I mean, every message!! > >I don't know how to fix that. > >I've cleaned/removed all files in qfiles directory, restarted Postfix, restarted Mailman, killed all mailman process and start again. > >After some seconds a huge amount of ancient messages floods my server again. > >How can I clear EVERYTHING that is stored in Mailman? If you have emptied all the qfiles/* directories, there is nothing left for Mailman to do. Either the messages are already queued in Postfix, or something else is reposting these messages to Mailman. Examination of Mailman's logs may help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Nov 25 17:13:34 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 25 Nov 2010 08:13:34 -0800 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: References: Message-ID: <4CEE8B2E.2030709@msapiro.net> On 11/24/2010 2:45 PM, Gustavo Delfino wrote: > > And for he most part it seems to be working (web pages work, can > create lists and subscribe users, and email notifications are > received). But, delivering a message to subscribed users is not > working. I am getting this inside /var/log/maillog: > > Nov 24 14:46:10 admin postfix/virtual[17880]: 94B1C2FA8016: > to=<|/usr/local/mailman/mail/mailman post > testlist5 at gdsolutions.com.ve>, > orig_to=, relay=virtual, delay=0.02, > delays=0.01/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: > "|/usr/local/mailman/mail/mailman post > testlist5 at gdsolutions.com.ve") There is some problem with your aliases and virtual maps. It looks like you have installed aliases as virtual_alias_maps instead of alias_maps. Also, the list name in the aliases should be just the name, not the email address unless you have also installed some virtual hosting patch that makes the listname have the domain included. See and if gdsolutions.com.ve is a Postfix virtual domain, see . > As I have spent days trying to make this work, I decided to ask for > help. At this point, I am thinking about recompiling mailman with a > custom --with-mail-gid. Any advices? That won't change this. > This is my setup: python 2.4.3 postfix 2.3.3 spamassassin installed > as a daemon virtual domains & virtual mailboxes I can send full > configuration details as needed. Note that Mailman/Postfix integration as described in the above referenced manual pages is for virtual alias domains and not virtual mailbox domains. You can make this work for list domains that are virtual mailbox domains if necessary. See the FAQ at . If you need further help from this list, we need to see the output of "postconf -n", the contents of mm_cfg.py, and assuming you have "MTA = 'Postfix'" in mm_cfg.py, the output of "ls -l /usr/local/mailman/data". Also, we need to know what if any patches you have installed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geoff at QuiteLikely.com Thu Nov 25 20:52:17 2010 From: geoff at QuiteLikely.com (Geoff Shang) Date: Thu, 25 Nov 2010 21:52:17 +0200 (IST) Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <4CEE8B2E.2030709@msapiro.net> References: <4CEE8B2E.2030709@msapiro.net> Message-ID: On Thu, 25 Nov 2010, Mark Sapiro wrote: > Note that Mailman/Postfix integration as described in the above > referenced manual pages is for virtual alias domains and not virtual > mailbox domains. You can make this work for list domains that are > virtual mailbox domains if necessary. See the FAQ at > . To clear this one up once and for all: It's perfectly possible to use virtual_alias_maps in virtual_mailbox_domains and there's no need to resort to messing with postfix transports. See the commented example at http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox I use this setup all the time and it just works. Geoff. From mark at msapiro.net Thu Nov 25 21:35:26 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 25 Nov 2010 12:35:26 -0800 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailmanpost mylist@mydomain.com" In-Reply-To: Message-ID: Geoff Shang wrote: > >It's perfectly possible to use virtual_alias_maps in >virtual_mailbox_domains and there's no need to resort to messing with >postfix transports. > >See the commented example at >http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox > >I use this setup all the time and it just works. Thanks Geoff. I have updated the FAQ entry to indicate it is not needed in the simple virtual_mailbox_domains case but can be used to generate mappings for other purposes. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rgm at htt-consult.com Thu Nov 25 21:39:48 2010 From: rgm at htt-consult.com (Robert Moskowitz) Date: Thu, 25 Nov 2010 15:39:48 -0500 Subject: [Mailman-Users] !st time install help Message-ID: <4CEEC994.3030307@htt-consult.com> I am new to running Mailman, though a long time user and have been admin for a list or two over the years. The system is Fedora 12, mailman ver 2.1.12-9, with the Amahi Home Server (amahi.org) added. So I am trying to setup mailman as a Amahi webapp. The URL mailman.foo.com right now comes up to the Apache test page, all ready for my to put my index.html into the .../mailman directory. host mailman.foo.com returns the IPv4 IP for my server, so looks like I am all ready to go. I am following the recipe from: http://www.yolinux.com/TUTORIALS/LinuxTutorialMailman.html I run: /usr/lib/mailman/bin/mmsitepass I edit /usr/lib/mailman/Mailman/mm_cfg.py to setup my default URL: DEFAULT_URL_HOST = mailman.foo.com DEFAULT_EMAIL_HOST = foo.com I then run: /usr/lib/mailman/bin/newlist mailman And I get errors: Traceback (most recent call last): File "/usr/lib/mailman/bin/newlist", line 99, in from Mailman import mm_cfg File "/usr/lib/mailman/Mailman/mm_cfg.py", line 86, in DEFAULT_URL_HOST = mailman.foo.com NameError: name 'mailman' is not defined Now I have not setup the URL mailman.foo.com/mailman, is that what it is complaining about (and I think I have to edit the default.py to drop the directory from the URL?)? Or is there suppose to be quotes around the URL (DEFAULT_URL_HOST = 'mailman.foo.com'). Or is it something else? Thanks for any help. We have a postfix/mySQL/CourierMail/SquirelMail app just about ready for Amahi, and adding Mailman would address a number of my needs. From rgm at htt-consult.com Fri Nov 26 01:56:47 2010 From: rgm at htt-consult.com (Robert Moskowitz) Date: Thu, 25 Nov 2010 19:56:47 -0500 Subject: [Mailman-Users] !st time install help In-Reply-To: <4CEEC994.3030307@htt-consult.com> References: <4CEEC994.3030307@htt-consult.com> Message-ID: <4CEF05CF.7080400@htt-consult.com> I am making some progress. I am still getting the error below running /usr/lib/mailman/bin/newlist mailman But I now have mailman.conf linked into my /etc/http/conf.d right so that if I provide the URL http://mailman.foo.com/mailman, I get taken to http://mailman.foo.com/mailman/listinfo with the error: We're sorry, we hit a bug! On 11/25/2010 03:39 PM, Robert Moskowitz wrote: > I am new to running Mailman, though a long time user and have been > admin for a list or two over the years. > > The system is Fedora 12, mailman ver 2.1.12-9, with the Amahi Home > Server (amahi.org) added. > > So I am trying to setup mailman as a Amahi webapp. The URL > mailman.foo.com right now comes up to the Apache test page, all ready > for my to put my index.html into the .../mailman directory. > > host mailman.foo.com > > returns the IPv4 IP for my server, so looks like I am all ready to go. > > I am following the recipe from: > http://www.yolinux.com/TUTORIALS/LinuxTutorialMailman.html > > I run: > > /usr/lib/mailman/bin/mmsitepass > > I edit > > /usr/lib/mailman/Mailman/mm_cfg.py > > to setup my default URL: > > DEFAULT_URL_HOST = mailman.foo.com > DEFAULT_EMAIL_HOST = foo.com > > I then run: > > /usr/lib/mailman/bin/newlist mailman > > And I get errors: > > Traceback (most recent call last): > File "/usr/lib/mailman/bin/newlist", line 99, in > from Mailman import mm_cfg > File "/usr/lib/mailman/Mailman/mm_cfg.py", line 86, in > DEFAULT_URL_HOST = mailman.foo.com > NameError: name 'mailman' is not defined > > Now I have not setup the URL mailman.foo.com/mailman, is that what it > is complaining about (and I think I have to edit the default.py to > drop the directory from the URL?)? > > Or is there suppose to be quotes around the URL (DEFAULT_URL_HOST = > 'mailman.foo.com'). > > Or is it something else? > > Thanks for any help. We have a postfix/mySQL/CourierMail/SquirelMail > app just about ready for Amahi, and adding Mailman would address a > number of my needs. > > From mark at msapiro.net Fri Nov 26 18:19:24 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Nov 2010 09:19:24 -0800 Subject: [Mailman-Users] !st time install help In-Reply-To: <4CEF05CF.7080400@htt-consult.com> Message-ID: Robert Moskowitz wrote: >I am making some progress. I am still getting the error below running >/usr/lib/mailman/bin/newlist mailman > >But I now have mailman.conf linked into my /etc/http/conf.d right so >that if I provide the URL http://mailman.foo.com/mailman, I get taken >to http://mailman.foo.com/mailman/listinfo with the error: > >We're sorry, we hit a bug! And what is the traceback from this that you'll find in Mailman's error log? (more below) >On 11/25/2010 03:39 PM, Robert Moskowitz wrote: [...] >> I edit >> >> /usr/lib/mailman/Mailman/mm_cfg.py >> >> to setup my default URL: >> >> DEFAULT_URL_HOST = mailman.foo.com >> DEFAULT_EMAIL_HOST = foo.com As you note below, these need to be quoted as DEFAULT_URL_HOST = 'mailman.foo.com' DEFAULT_EMAIL_HOST = 'foo.com' Also, assuming they are not identical to the defaults in Defaults.py, you also need to add add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) following the above definitions, and while it is not required, it is good practice to remove the entry that was created by Defaults.py so the whole thing should be as the following 4 lines in mm_cfg.py DEFAULT_URL_HOST = 'mailman.foo.com' DEFAULT_EMAIL_HOST = 'foo.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) >> I then run: >> >> /usr/lib/mailman/bin/newlist mailman >> >> And I get errors: >> >> Traceback (most recent call last): >> File "/usr/lib/mailman/bin/newlist", line 99, in >> from Mailman import mm_cfg >> File "/usr/lib/mailman/Mailman/mm_cfg.py", line 86, in >> DEFAULT_URL_HOST = mailman.foo.com >> NameError: name 'mailman' is not defined >> >> Now I have not setup the URL mailman.foo.com/mailman, is that what it >> is complaining about (and I think I have to edit the default.py to >> drop the directory from the URL?)? >> >> Or is there suppose to be quotes around the URL (DEFAULT_URL_HOST = >> 'mailman.foo.com'). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Nov 26 18:33:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Nov 2010 09:33:32 -0800 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <4CEE8B2E.2030709@msapiro.net> References: <4CEE8B2E.2030709@msapiro.net> Message-ID: <4CEFEF6C.1030004@msapiro.net> On 11/26/2010 5:29 AM, Gustavo Delfino wrote: > > Thank you Mark & Geoff for answering. If using virtual mailboxes complicates matters significantly, I could switch to using regular UNIX accounts for my email addresses for my virtual domains. After all the number of email accounts that I manage is very low, as I mostly forward messages to other domains. > > I don't think that's a problem. > > Find below the requested configuration information: > > > > # postconf -n > > alias_database = hash:/etc/aliases > > alias_maps = hash:/etc/aliases > > command_directory = /usr/sbin > > config_directory = /etc/postfix > > daemon_directory = /usr/libexec/postfix > > debug_peer_level = 2 > > html_directory = no > > inet_interfaces = all > > mail_owner = postfix > > mailq_path = /usr/bin/mailq.postfix > > manpage_directory = /usr/share/man > > mydestination = $myhostname, localhost.$mydomain, localhost > > mydomain = gdsolutions.com.ve > > myhostname = admin.gdsolutions.com.ve > > mynetworks_style = host > > myorigin = $mydomain > > newaliases_path = /usr/bin/newaliases.postfix > > queue_directory = /var/spool/postfix > > readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES > > sample_directory = /usr/share/doc/postfix-2.3.3/samples > > sendmail_path = /usr/sbin/sendmail.postfix > > setgid_group = postdrop > > unknown_local_recipient_reject_code = 550 > > virtual_alias_maps = hash:/etc/postfix/virtual_alias > > hash:/usr/local/mailman/data/aliases > > hash:/usr/local/mailman/data/virtual-mailman The above is the problem. hash:/usr/local/mailman/data/aliases belongs in alias_maps, not in virtual_alias_maps. I.e. virtual_alias_maps = hash:/etc/postfix/virtual_alias hash:/usr/local/mailman/data/virtual-mailman and alias_maps = hash:/etc/aliases hash:/usr/local/mailman/data/aliases > > virtual_gid_maps = static:517 > > virtual_mailbox_base = /home/vmail > > virtual_mailbox_domains = /etc/postfix/virtual_domains > > virtual_mailbox_maps = hash:/etc/postfix/vmailbox > > virtual_uid_maps = static:506 > > > > > > mm_cfg.py: > > MTA = 'Postfix' > > POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'bosque-encantado.org.ve' ] > > DEFAULT_EMAIL_HOST = 'gdsolutions.com.ve' > > DEFAULT_URL_HOST = 'gdsolutions.com.ve' > > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > > DEFAULT_SERVER_LANGUAGE = 'es' There may be an issue here. The above says that you have only one email domain for lists and it is gdsolutions.com.ve. It is mydomain in Postfix, but it is not in mydestination, thus it is not a local domain in Postfix. Its should either be added to mydestination as in mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain or it should be in POSTFIX_STYLE_VIRTUAL_DOMAINS above as in POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'bosque-encantado.org.ve', 'gdsolutions.com.ve' ] Also, the domain 'bosque-encantado.org.ve' is not mentioned as a Mailman virtual host. If you actually have lists in this domain, you should add add_virtualhost('web.host.for.this.domain', 'bosque-encantado.org.ve') to mm_cfg.py where 'web.host.for.this.domain' is 'bosque-encantado.org.ve' or whatever the host portion of URLs for this domain is. > > > > # ls -l /usr/local/mailman/data > > total 68 > > -rw-r----- 1 root mailman 41 Nov 20 11:43 adm.pw > > -rw-rw---- 1 root mailman 6156 Nov 24 15:01 aliases > > -rw-rw---- 1 mailman mailman 12288 Nov 24 15:01 aliases.db > > -rw-r----- 1 root mailman 41 Nov 20 11:44 creator.pw > > -rw-r--r-- 1 root mailman 10 Nov 20 09:12 last_mailman_version > > -rw-rw---- 1 mailman mailman 5 Nov 20 11:38 master-qrunner.pid > > -rw-r--r-- 1 root mailman 14100 Nov 20 11:47 sitelist.cfg > > -rw-rw---- 1 root mailman 1187 Nov 24 15:01 virtual-mailman > > -rw-rw---- 1 mailman mailman 12288 Nov 24 15:01 virtual-mailman.db > > > > Regards, > > > > Gustavo Delfino -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rgm at htt-consult.com Fri Nov 26 21:10:05 2010 From: rgm at htt-consult.com (Robert Moskowitz) Date: Fri, 26 Nov 2010 15:10:05 -0500 Subject: [Mailman-Users] !st time install help In-Reply-To: References: Message-ID: <4CF0141D.4040800@htt-consult.com> THANK YOU! Mailman list is now created... On 11/26/2010 12:19 PM, Mark Sapiro wrote: > Robert Moskowitz wrote: > > >> I am making some progress. I am still getting the error below running >> /usr/lib/mailman/bin/newlist mailman >> >> But I now have mailman.conf linked into my /etc/http/conf.d right so >> that if I provide the URL http://mailman.foo.com/mailman, I get taken >> to http://mailman.foo.com/mailman/listinfo with the error: >> >> We're sorry, we hit a bug! >> > > And what is the traceback from this that you'll find in Mailman's error > log? > > (more below) > > > >> On 11/25/2010 03:39 PM, Robert Moskowitz wrote: >> > [...] > >>> I edit >>> >>> /usr/lib/mailman/Mailman/mm_cfg.py >>> >>> to setup my default URL: >>> >>> DEFAULT_URL_HOST = mailman.foo.com >>> DEFAULT_EMAIL_HOST = foo.com >>> > > > As you note below, these need to be quoted as > > DEFAULT_URL_HOST = 'mailman.foo.com' > DEFAULT_EMAIL_HOST = 'foo.com' > > Also, assuming they are not identical to the defaults in Defaults.py, > you also need to add > > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > > following the above definitions, and while it is not required, it is > good practice to remove the entry that was created by Defaults.py so > the whole thing should be as the following 4 lines in mm_cfg.py > > DEFAULT_URL_HOST = 'mailman.foo.com' > DEFAULT_EMAIL_HOST = 'foo.com' > VIRTUAL_HOSTS.clear() > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > I added these lines and the script ran to create the mailman list. And the URL http://mailman.foo.com/mailman works. Now is there a REASONABLE way to just make the URL http://mailman.foo.com (leaving archives at I think it is suppose to be http://mailman.foo.com/archives)? From mark at msapiro.net Sat Nov 27 02:45:09 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Nov 2010 17:45:09 -0800 Subject: [Mailman-Users] !st time install help In-Reply-To: <4CF0141D.4040800@htt-consult.com> Message-ID: Robert Moskowitz wrote: > >Now is there a REASONABLE way to just make the URL >http://mailman.foo.com (leaving archives at I think it is suppose to be >http://mailman.foo.com/archives)? > If all you want is for http://mailman.foo.com to get the listinfo overview page, this works in Apache RedirectMatch ^[/]+$ /mailman/listinfo I don't know how you'd translate that to Amahi Home Server. If you wan't to drop the '/mailman' from all URLs you would need to change whatever the equivalent of ScriptAlias /mailman/ /path/to/mailman/cgi-bin/ is to something equivalent to ScriptAlias / /path/to/mailman/cgi-bin/ plus the equivalent of RedirectMatch ^[/]+$ /listinfo You would also need to add DEFAULT_URL_PATTERN = 'http://%s/' to mm_cfg.py and run fix_url to update the web_page_url for existing lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vivi at mage.me.uk Fri Nov 26 23:52:47 2010 From: vivi at mage.me.uk (Reza) Date: Fri, 26 Nov 2010 22:52:47 +0000 Subject: [Mailman-Users] mailman not sending my mail to the list. Message-ID: <4CF03A3F.3080305@mage.me.uk> Hi All, I've been trying to send posts to two lists which both run mailman and they seem to be accepting my mail (no errors being sent back after I send mail to the list) but it's nowhere to be found on the lists. I'm not sure if there's a blacklist or something. Could anyone shed some light on the topic. Thank you. From mark at msapiro.net Sat Nov 27 03:03:00 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Nov 2010 18:03:00 -0800 Subject: [Mailman-Users] mailman not sending my mail to the list. In-Reply-To: <4CF03A3F.3080305@mage.me.uk> Message-ID: Reza wrote: >Hi All, I've been trying to send posts to two lists which both run >mailman and they seem to be accepting my mail (no errors being sent back >after I send mail to the list) but it's nowhere to be found on the >lists. I'm not sure if there's a blacklist or something. Could anyone >shed some light on the topic. Thank you. If these are lists on your server, see the FAQ at to start. If not, contact the Mailman admins at the server that hosts the lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Nov 27 04:40:26 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Nov 2010 19:40:26 -0800 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <4CEFEF6C.1030004@msapiro.net> References: <4CEFEF6C.1030004@msapiro.net> Message-ID: <4CF07DAA.5040804@msapiro.net> On 11/26/2010 6:57 PM, Gustavo Delfino wrote: > As directed, I have moved my mailman/data/aliases from virtual_alias_maps to alias_maps. Also I have configured the additional domain as instructed. I now feel that I am getting closer, but unfortunately it didn't worked. > > Then I read the "Mailing Lists" section in http://www.postfix.org/VIRTUAL_README.html and realized that I also needed to put additional aliases in the /etc/postfix/virtual_alias file. I did that and it still doesn't work. It seems like postfix is ignoring the non-virtual aliases (yes I did run postmap .., newaliases, postalias & postfix restart). You shouldn't need to do this. If Mailman is properly configured it will create the necessary virtual mappings in data/virtual-mailman. > This is what I get in the /var/log/maillog when I send a message for distribution: > [...] > Nov 26 21:32:59 admin postfix/qmgr[10066]: BA4F22FA801F: from=, size=2458, nrcpt=1 (queue active) > Nov 26 21:32:59 admin postfix/virtual[10100]: BA4F22FA801F: to=, relay=virtual, delay=0.02, delays=0.01/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "testlist5 at gdsolutions.com.ve") > Nov 26 21:32:59 admin postfix/cleanup[10095]: BE13E2FA801E: message-id=<20101127020259.BE13E2FA801E at admin.gdsolutions.com.ve> There is apparently no entry of the form testlist5 at gdsolutions.com.ve testlist5 in data/virtual-mailman to map the virtual domain address testlist5 at gdsolutions.com.ve to the local (aliased) address testlist5. However, there is such an entry in /etc/postfix/virtual_alias according to the below, so I don't know why this didn't work unless you neglected to run postmap /etc/postfix/virtual_alias after adding those entries. > The updated postfix configuration: > > # postconf -n > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases > command_directory = /usr/sbin > config_directory = /etc/postfix > daemon_directory = /usr/libexec/postfix > debug_peer_level = 2 > html_directory = no > inet_interfaces = all > mail_owner = postfix > mailq_path = /usr/bin/mailq.postfix > manpage_directory = /usr/share/man > mydestination = $myhostname, localhost.$mydomain, localhost > mydomain = gdsolutions.com.ve > myhostname = admin.gdsolutions.com.ve > mynetworks_style = host > myorigin = $mydomain > newaliases_path = /usr/bin/newaliases.postfix > queue_directory = /var/spool/postfix > readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES > sample_directory = /usr/share/doc/postfix-2.3.3/samples > sendmail_path = /usr/sbin/sendmail.postfix > setgid_group = postdrop > unknown_local_recipient_reject_code = 550 > virtual_alias_maps = hash:/etc/postfix/virtual_alias hash:/usr/local/mailman/data/virtual-mailman > virtual_gid_maps = static:517 > virtual_mailbox_base = /home/vmail > virtual_mailbox_domains = /etc/postfix/virtual_domains > virtual_mailbox_maps = hash:/etc/postfix/vmailbox > virtual_uid_maps = static:506 > > # cat /etc/postfix/virtual_domains > gdsolutions.com.ve > bosque-encantado.org.ve > > # cat /etc/postfix/virtual_alias > (...) > testlist5 at gdsolutions.com.ve testlist5 > testlist5-admin at gdsolutions.com.ve testlist5-admin > testlist5-bounces at gdsolutions.com.ve testlist5-bounces > testlist5-confirm at gdsolutions.com.ve testlist5-confirm > testlist5-join at gdsolutions.com.ve testlist5-join > testlist5-leave at gdsolutions.com.ve testlist5-leave > testlist5-owner at gdsolutions.com.ve testlist5-owner > testlist5-request at gdsolutions.com.ve testlist5-request > testlist5-subscribe at gdsolutions.com.ve testlist5-subscribe > testlist5-unsubscribe at gdsolutions.com.ve testlist5-unsubscribe If Mailman is properly configured, the above will be generated in /usr/local/mailman/data/virtual-mailman. > # cat /usr/local/mailman/data/aliases > (...) > testlist5: "|/usr/local/mailman/mail/mailman post testlist5" > testlist5-admin: "|/usr/local/mailman/mail/mailman admin testlist5" > testlist5-bounces: "|/usr/local/mailman/mail/mailman bounces testlist5" > testlist5-confirm: "|/usr/local/mailman/mail/mailman confirm testlist5" > testlist5-join: "|/usr/local/mailman/mail/mailman join testlist5" > testlist5-leave: "|/usr/local/mailman/mail/mailman leave testlist5" > testlist5-owner: "|/usr/local/mailman/mail/mailman owner testlist5" > testlist5-request: "|/usr/local/mailman/mail/mailman request testlist5" > testlist5-subscribe: "|/usr/local/mailman/mail/mailman subscribe testlist5" > testlist5-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe testlist5" The above are good. > # cat /usr/local/mailman/Mailman/mm_cfg.py > (...) > MTA = 'Postfix' > POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'gdsolutions.com.ve', 'bosque-encantado.org.ve' ] > DEFAULT_EMAIL_HOST = 'gdsolutions.com.ve' > DEFAULT_URL_HOST = 'gdsolutions.com.ve' > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > add_virtualhost('bosque-encantado.org.ve', 'bosque-encantado.org.ve') > DEFAULT_SERVER_LANGUAGE = 'es' This looks good too. Do the following: Remove the virtual mappings for testlist5 from /etc/postfix/virtual_alias and run "postmap /etc/postfix/virtual_alias". As root or mailman, run /usr/local/mailman/bin/withlist -l -a -r fix_url and /usr/local/mailman/bin/genaliases This should make sure all your lists are in the gdsolutions.com.ve domain as far as Mailman is concerned and generate the appropriate data/aliases and data/virtual-mailman files. Then retry your test. > Once I get my mailing list at gdsolutions.com.ve working, I'll configure another one at the bosque-encantado.org.ve domain. > > Regards, > > Gustavo Delfino -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gdelfino at umich.edu Sat Nov 27 05:20:34 2010 From: gdelfino at umich.edu (Gustavo Delfino) Date: Fri, 26 Nov 2010 23:50:34 -0430 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <4CF07DAA.5040804@msapiro.net> References: <4CEFEF6C.1030004@msapiro.net> <4CF07DAA.5040804@msapiro.net> Message-ID: <94C6FDC9-0ED7-4111-A403-8188B27E724F@umich.edu> My data/virtual-mailman file was incomplete but now ?after following all the steps that you recommended me? it is complete but I still get the "unknown user: error. I even tried deactivating SpamAssessin but it didn't solved the issue. Nov 26 23:40:50 admin postfix/smtpd[13981]: connect from mail-gx0-f174.google.com[209.85.161.174] Nov 26 23:40:50 admin postfix/smtpd[13981]: 6914D2FA801E: client=mail-gx0-f174.google.com[209.85.161.174] Nov 26 23:40:50 admin postfix/cleanup[13985]: 6914D2FA801E: message-id= Nov 26 23:40:50 admin postfix/qmgr[13909]: 6914D2FA801E: from=, size=2077, nrcpt=1 (queue active) Nov 26 23:40:50 admin spamd[1095]: spamd: connection from admin.gdsolutions.com.ve [127.0.0.1] at port 60336 Nov 26 23:40:50 admin spamd[1095]: spamd: setuid to spam succeeded Nov 26 23:40:50 admin spamd[1095]: spamd: processing message for spam:521 Nov 26 23:40:51 admin spamd[1095]: spamd: clean message (-0.1/5.0) for spam:521 in 1.1 seconds, 2069 bytes. Nov 26 23:40:51 admin spamd[1095]: spamd: result: . 0 - DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL scantime=1.1,size=2069,user=spam,uid=521,required_score=5.0,rhost=admin.gdsolutions.com.ve,raddr=127.0.0.1,rport=60336,mid=,autolearn=ham Nov 26 23:40:51 admin postfix/pickup[13908]: 81B0E2FA801F: uid=521 from= Nov 26 23:40:51 admin postfix/cleanup[13985]: 81B0E2FA801F: message-id= Nov 26 23:40:51 admin postfix/pipe[13986]: 6914D2FA801E: to=, relay=spamd, delay=1.1, delays=0.04/0/0/1.1, dsn=2.0.0, status=sent (delivered via spamd service) Nov 26 23:40:51 admin postfix/qmgr[13909]: 6914D2FA801E: removed Nov 26 23:40:51 admin postfix/qmgr[13909]: 81B0E2FA801F: from=, size=2479, nrcpt=1 (queue active) Nov 26 23:40:51 admin postfix/virtual[13990]: 81B0E2FA801F: to=, relay=virtual, delay=0.02, delays=0.01/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "testlist5 at gdsolutions.com.ve") Nov 26 23:40:51 admin postfix/cleanup[13985]: 858302FA801E: message-id=<20101127041051.858302FA801E at admin.gdsolutions.com.ve> Nov 26 23:40:51 admin postfix/bounce[13991]: 81B0E2FA801F: sender non-delivery notification: 858302FA801E Nov 26 23:40:51 admin postfix/qmgr[13909]: 858302FA801E: from=<>, size=4318, nrcpt=1 (queue active) Nov 26 23:40:51 admin postfix/qmgr[13909]: 81B0E2FA801F: removed Nov 26 23:40:51 admin spamd[25130]: prefork: child states: II Nov 26 23:40:52 admin postfix/smtp[13992]: 858302FA801E: to=, relay=gmail-smtp-in.l.google.com[74.125.45.27]:25, delay=0.64, delays=0/0/0.2/0.43, dsn=2.0.0, status=sent (250 2.0.0 OK 1290830962 f22si6713697anh.145) Nov 26 23:40:52 admin postfix/qmgr[13909]: 858302FA801E: removed Any other idea? Regards, Gustavo Delfino On Nov 26, 2010, at 11:10 PM, Mark Sapiro wrote: (...) > Do the following: > > Remove the virtual mappings for testlist5 from > /etc/postfix/virtual_alias and run "postmap /etc/postfix/virtual_alias". > > As root or mailman, run > > /usr/local/mailman/bin/withlist -l -a -r fix_url > > and > > /usr/local/mailman/bin/genaliases > > This should make sure all your lists are in the gdsolutions.com.ve > domain as far as Mailman is concerned and generate the appropriate > data/aliases and data/virtual-mailman files. > > Then retry your test. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > From mark at msapiro.net Sat Nov 27 06:33:51 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Nov 2010 21:33:51 -0800 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <94C6FDC9-0ED7-4111-A403-8188B27E724F@umich.edu> References: <4CEFEF6C.1030004@msapiro.net> <4CF07DAA.5040804@msapiro.net> <94C6FDC9-0ED7-4111-A403-8188B27E724F@umich.edu> Message-ID: <4CF0983F.5090906@msapiro.net> On 11/26/2010 8:20 PM, Gustavo Delfino wrote: > My data/virtual-mailman file was incomplete but now ?after following all the steps that you recommended me? it is complete but I still get the "unknown user: error. I even tried deactivating SpamAssessin but it didn't solved the issue. > [...] > Nov 26 23:40:51 admin postfix/virtual[13990]: 81B0E2FA801F: to=, relay=virtual, delay=0.02, delays=0.01/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "testlist5 at gdsolutions.com.ve") [...] > > Any other idea? I do not understand the above message. It says that Postfix's virtual delivery module can't find the address testlist5 at gdsolutions.com.ve, but the virtual_alias_maps in data/virtual-mailman map that address to the local address testlist5, so I don't understand the problem. One thing you can try is to put VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'admin.gdsolutions.com.ve' in mm_cfg.py and then rerun /usr/local/mailman/bin/genaliases This will create virtual-mailman entries like testlist5 at gdsolutions.com.ve testlist5 at admin.gdsolutions.com.ve which really shouldn't make any difference, but since admin.gdsolutions.com.ve is in mydestination, it will explicitly map the testlist5 at gdsolutions.com.ve address to a local domain. Another possibility is that there is something in the virtual mailbox maps /etc/postfix/vmailbox that is somehow interfering with the virtual alias maps for the list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gdelfino at umich.edu Sat Nov 27 15:53:56 2010 From: gdelfino at umich.edu (Gustavo Delfino) Date: Sat, 27 Nov 2010 10:23:56 -0430 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <4CF0983F.5090906@msapiro.net> References: <4CEFEF6C.1030004@msapiro.net> <4CF07DAA.5040804@msapiro.net> <94C6FDC9-0ED7-4111-A403-8188B27E724F@umich.edu> <4CF0983F.5090906@msapiro.net> Message-ID: <35CBD9E5-2A2D-478E-890D-66313EFA3F0F@umich.edu> IT WORKED! Nov 27 10:14:56 admin postfix/local[21850]: 8879A2FA801F: to=, relay=local, delay=0.25, delays=0.01/0.09/0/0.15, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post testlist5) You said that this "really shouldn't make any difference", but it did. Is there any other test you want me to try in order to figure out why this works? t h a n k s ! -- Gustavo Delfino On Nov 27, 2010, at 1:03 AM, Mark Sapiro wrote: > On 11/26/2010 8:20 PM, Gustavo Delfino wrote: >> My data/virtual-mailman file was incomplete but now ?after following all the steps that you recommended me? it is complete but I still get the "unknown user: error. I even tried deactivating SpamAssessin but it didn't solved the issue. >> > [...] >> Nov 26 23:40:51 admin postfix/virtual[13990]: 81B0E2FA801F: to=, relay=virtual, delay=0.02, delays=0.01/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "testlist5 at gdsolutions.com.ve") > [...] >> >> Any other idea? > > > I do not understand the above message. It says that Postfix's virtual > delivery module can't find the address testlist5 at gdsolutions.com.ve, but > the virtual_alias_maps in data/virtual-mailman map that address to the > local address testlist5, so I don't understand the problem. > > One thing you can try is to put > > VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'admin.gdsolutions.com.ve' > > in mm_cfg.py and then rerun > > /usr/local/mailman/bin/genaliases > > This will create virtual-mailman entries like > > testlist5 at gdsolutions.com.ve testlist5 at admin.gdsolutions.com.ve > > which really shouldn't make any difference, but since > admin.gdsolutions.com.ve is in mydestination, it will explicitly map the > testlist5 at gdsolutions.com.ve address to a local domain. > > Another possibility is that there is something in the virtual mailbox > maps /etc/postfix/vmailbox that is somehow interfering with the virtual > alias maps for the list. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From mark at msapiro.net Sat Nov 27 16:51:51 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 27 Nov 2010 07:51:51 -0800 Subject: [Mailman-Users] unknown user: "|/usr/local/mailman/mail/mailman post mylist@mydomain.com" In-Reply-To: <35CBD9E5-2A2D-478E-890D-66313EFA3F0F@umich.edu> References: <4CEFEF6C.1030004@msapiro.net> <4CF07DAA.5040804@msapiro.net> <94C6FDC9-0ED7-4111-A403-8188B27E724F@umich.edu> <4CF0983F.5090906@msapiro.net> <35CBD9E5-2A2D-478E-890D-66313EFA3F0F@umich.edu> Message-ID: <4CF12917.4050105@msapiro.net> On 11/27/2010 6:53 AM, Gustavo Delfino wrote: > IT WORKED! > > Nov 27 10:14:56 admin postfix/local[21850]: 8879A2FA801F: to=, relay=local, delay=0.25, delays=0.01/0.09/0/0.15, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post testlist5) > > You said that this "really shouldn't make any difference", but it did. Is there any other test you want me to try in order to figure out why this works? I'm not a Postfix expert, but I can guess what is happening. I'm guessing that when Postfix sees the address testlist5, it assumes that this is testlist5@$myorigin (see ), but in your case, $myorigin is not a local domain so it doesn't work. You could try changing the mm_cfg.py entry to VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' and then rerunning /usr/local/mailman/bin/genaliases I now think that will work too and is more generic and thus is more likely to survive future changes to your Postfix configuration. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rgm at htt-consult.com Sun Nov 28 01:03:56 2010 From: rgm at htt-consult.com (Robert Moskowitz) Date: Sat, 27 Nov 2010 19:03:56 -0500 Subject: [Mailman-Users] !st time install help In-Reply-To: References: Message-ID: <4CF19C6C.20505@htt-consult.com> On 11/26/2010 08:45 PM, Mark Sapiro wrote: > Robert Moskowitz wrote: > >> Now is there a REASONABLE way to just make the URL >> http://mailman.foo.com (leaving archives at I think it is suppose to be >> http://mailman.foo.com/archives)? >> >> > > > If all you want is for http://mailman.foo.com to get the listinfo > overview page, this works in Apache > > RedirectMatch ^[/]+$ /mailman/listinfo > > I don't know how you'd translate that to Amahi Home Server. > I will work through this in a bit, but the Amahi Home Server runs on Fedora 12 uses Apache and for a webapp like mailman, it has its own .conf file in /etc/http/conf.d that is set up with a basic virtual host configuration for webapp/foo/com. It was a small matter to remove much of the original content and put in the mailman.conf specific definitions. Once I get mailman working for Amahi, I will be submitting it to the maintains so that it can be a 'standard' single click app. Or I hope I can get it working well. It will be an addon to what we have done for a postfix mail server for Amahi. > If you wan't to drop the '/mailman' from all URLs you would need to > change whatever the equivalent of > > ScriptAlias /mailman/ /path/to/mailman/cgi-bin/ > > is to something equivalent to > > ScriptAlias / /path/to/mailman/cgi-bin/ > > plus the equivalent of > > RedirectMatch ^[/]+$ /listinfo > > You would also need to add > > DEFAULT_URL_PATTERN = 'http://%s/' > > to mm_cfg.py and run fix_url to update the web_page_url for existing > lists. > > From deansuhr at deansuhr.us Sun Nov 28 21:52:47 2010 From: deansuhr at deansuhr.us (Dean Suhr) Date: Sun, 28 Nov 2010 12:52:47 -0800 Subject: [Mailman-Users] Mailman - trouble creating a second list at an existing virtual host Message-ID: I have a Virtual Alias error problem on my Mac running OSX Server 10.4.6. I realize that is not a completely typical Mailman install, but I think the problem is Postfix to Mailman related ? more on the Postfix side. I have a Mailman list working (for months) ... discuss at lists.MLDfamily.org. I've just created a new list ... discuss-adults at lists.MLDfamily.org. The web interface works fine for the new list and it shows lists.MLDfamily.org as its host_name. http://lists.mldfamily.org/mailman/admin/discuss-adults Both lists show up when I run the following command: /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org But deliveries to the Postfix mail server nets me this error on my local server (i.e. the email is making it fine to my server): Nov 28 11:44:11 darcee postfix/smtpd11450 : NOQUEUE: reject: RCPT from mail-pv0-f170.google.comhttp://74.125.83.170: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table; from= to= proto=ESMTP helo= Deliveries to the initial discuss list at this virtual domain continue to work but discuss-adults give the virtual alias table error. What do I need to do to get this new list into the virtual domain table? I am thinking I am overlooking the obvious - your help is appreciated. I will respond with more config info if it?s necessary. Thanks in advance, Dean -- FWIW, this is the process I used to create the list: (did not need to create the virtual domain since it already existed) Stopped the mail server using server admin sudo /usr/share/mailman/bin/rmlist -a discuss-adults (to remove all residual old list stuff) sudo /usr/share/mailman/bin/newlist discuss-adults sudo /usr/share/mailman/bin/list_lists new list showed up sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org new list did not show up sudo /usr/share/mailman/bin/withlist -l -r fix_url discuss-adults -u lists.MLDfamily.org sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org new list now shows up at the proper virtual domain sudo /usr/share/mailman/bin/genaliases sudo postfix reload failed since mail server was stopped started mail server using server admin To confirm the updates of the virtual alias table I did the following: ls -l /var/mailman/data aliases, aliases.db, virtual-mailman, & virtual-mailman.db all were time stamped the last few minutes Looking inside aliases and virtual-mailman conformed the proper entries. Aliases and virtual-mailman both contained the following stanzas (in addition to others): ~~ # STANZA START: discuss # CREATED: Sun Nov 28 11:39:09 2010 discuss: "|/usr/share/mailman/mail/mailman post discuss" discuss-admin: "|/usr/share/mailman/mail/mailman admin discuss" discuss-bounces: "|/usr/share/mailman/mail/mailman bounces discuss" discuss-confirm: "|/usr/share/mailman/mail/mailman confirm discuss" discuss-join: "|/usr/share/mailman/mail/mailman join discuss" discuss-leave: "|/usr/share/mailman/mail/mailman leave discuss" discuss-owner: "|/usr/share/mailman/mail/mailman owner discuss" discuss-request: "|/usr/share/mailman/mail/mailman request discuss" discuss-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss" discuss-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss" # STANZA END: discuss ~~ # STANZA START: discuss-adults # CREATED: Sun Nov 28 11:39:10 2010 discuss-adults: "|/usr/share/mailman/mail/mailman post discuss-adults" discuss-adults-admin: "|/usr/share/mailman/mail/mailman admin discuss-adults" discuss-adults-bounces: "|/usr/share/mailman/mail/mailman bounces discuss-adults" discuss-adults-confirm: "|/usr/share/mailman/mail/mailman confirm discuss-adults" discuss-adults-join: "|/usr/share/mailman/mail/mailman join discuss-adults" discuss-adults-leave: "|/usr/share/mailman/mail/mailman leave discuss-adults" discuss-adults-owner: "|/usr/share/mailman/mail/mailman owner discuss-adults" discuss-adults-request: "|/usr/share/mailman/mail/mailman request discuss-adults" discuss-adults-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss-adults" discuss-adults-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss-adults" # STANZA END: discuss-adults From mark at msapiro.net Mon Nov 29 17:15:20 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 29 Nov 2010 08:15:20 -0800 Subject: [Mailman-Users] Mailman - trouble creating a second list at anexisting virtual host In-Reply-To: Message-ID: Dean Suhr wrote: >I have a Mailman list working (for months) ... discuss at >lists.MLDfamily.org. I've just created a new list ... discuss-adults at >lists.MLDfamily.org. The web interface works fine for the new list and it >shows lists.MLDfamily.org as its host_name. >http://lists.mldfamily.org/mailman/admin/discuss-adults > >Both lists show up when I run the following command: > /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org > >But deliveries to the Postfix mail server nets me this error on my local >server (i.e. the email is making it fine to my server): >Nov 28 11:44:11 darcee postfix/smtpd11450 : >NOQUEUE: reject: RCPT from mail-pv0-f170.google.comhttp://74.125.83.170: 550 >5.1.1 : Recipient address rejected: User >unknown in virtual alias table; from=3D >to=3D proto=3DESMTP >helo=3D > >Deliveries to the initial discuss list at this virtual domain continue to >work but discuss-adults give the virtual alias table error. > >What do I need to do to get this new list into the virtual domain table? [...] >FWIW, this is the process I used to create the list: >(did not need to create the virtual domain since it already existed) >Stopped the mail server using server admin It isn't necessary to stop the Postfix or Mailman >sudo /usr/share/mailman/bin/rmlist -a discuss-adults (to remove all residual >old list stuff) >sudo /usr/share/mailman/bin/newlist discuss-adults which creates the list in the DEFAULT_URL_HOST domain. >sudo /usr/share/mailman/bin/list_lists new list showed up >sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org new list did >not show up This creates the list in the DEFAULT_URL_HOST domain >sudo /usr/share/mailman/bin/withlist -l -r fix_url discuss-adults -u >lists.MLDfamily.org >sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org new list now >shows up at the proper virtual domain and fix_url "fixed" it , but didn't update virtual-mailman. >sudo /usr/share/mailman/bin/genaliases but the above did, but the fix_url and genaliases could have been avoided by just specifying '-u lists.mldfamily.org' to newlist. >sudo postfix reload failed since mail server was stopped >started mail server using server admin It is not necessary to stop/start or reload Postfix when you make table changes. This is only needed if you make configuration changes such as changing main.cf or master.cf. >To confirm the updates of the virtual alias table I did the following: >ls -l /var/mailman/data aliases, aliases.db, virtual-mailman, & >virtual-mailman.db all were time stamped the last few minutes >Looking inside aliases and virtual-mailman conformed the proper entries. You show the aliases. The virtual-mailman entries should be different. E.g., entries like discuss at lists.mldfamily.org discuss discuss-admin at lists.mldfamily.org discuss-admin etc., and discuss-adults at lists.mldfamily.org discuss-adults discuss-admin-adults at lists.mldfamily.org discuss-admin-adults etc. Are all the entries in virtual-mailman? if not, there may be case sensitivity issues if the values in POSTFIX_STYLE_VIRTUAL_DOMAINS are not all lower case. If the entries for the discuss-adults list are in virtual-mailman, please post the output from sudo postconf -n >Aliases and virtual-mailman both contained the following stanzas (in >addition to others): > >~~ ># STANZA START: discuss ># CREATED: Sun Nov 28 11:39:09 2010 >discuss: "|/usr/share/mailman/mail/mailman post discuss" >discuss-admin: "|/usr/share/mailman/mail/mailman admin discuss" >discuss-bounces: "|/usr/share/mailman/mail/mailman bounces discuss" >discuss-confirm: "|/usr/share/mailman/mail/mailman confirm discuss" >discuss-join: "|/usr/share/mailman/mail/mailman join discuss" >discuss-leave: "|/usr/share/mailman/mail/mailman leave discuss" >discuss-owner: "|/usr/share/mailman/mail/mailman owner discuss" >discuss-request: "|/usr/share/mailman/mail/mailman request discuss" >discuss-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss" >discuss-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss" ># STANZA END: discuss >~~ ># STANZA START: discuss-adults ># CREATED: Sun Nov 28 11:39:10 2010 >discuss-adults: "|/usr/share/mailman/mail/mailman post >discuss-adults" >discuss-adults-admin: "|/usr/share/mailman/mail/mailman admin >discuss-adults" >discuss-adults-bounces: "|/usr/share/mailman/mail/mailman bounces >discuss-adults" >discuss-adults-confirm: "|/usr/share/mailman/mail/mailman confirm >discuss-adults" >discuss-adults-join: "|/usr/share/mailman/mail/mailman join >discuss-adults" >discuss-adults-leave: "|/usr/share/mailman/mail/mailman leave >discuss-adults" >discuss-adults-owner: "|/usr/share/mailman/mail/mailman owner >discuss-adults" >discuss-adults-request: "|/usr/share/mailman/mail/mailman request >discuss-adults" >discuss-adults-subscribe: "|/usr/share/mailman/mail/mailman subscribe >discuss-adults" >discuss-adults-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe >discuss-adults" ># STANZA END: discuss-adults -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From deansuhr at deansuhr.us Tue Nov 30 02:45:47 2010 From: deansuhr at deansuhr.us (Dean Suhr) Date: Mon, 29 Nov 2010 17:45:47 -0800 Subject: [Mailman-Users] Mailman - trouble creating a second list at an existing virtual host In-Reply-To: Message-ID: First, please excuse me if my original post from yesterday posted several times. It appears Google sees my outgoing message as the same ID as the returned list message and silently discards the incoming list message making me thing it was never sent out ... and they have no config option to change this behavior. Arghhh! Mark - thank you for your detailed response. I must confess the obvious. I re-examined virtual-mailman and aliases files. To my surprise the alias entries were not in the virtual-mailman file - I could have sworn I checked that carefully - but my lack of efficiency wit the command line must have caught up with me. I manually created the entries in virtual-mailman and the list is now functioning (delivering) properly. Will I always have to manually post entries into virtual-mailman or is that supposed to happen somewhere along the way? Is there a terminal command line I missed or could have run in addition to cause this to happen automatically? Thanks again - Dean On 11/29/10 8:15 AM, "Mark Sapiro" wrote: > Dean Suhr wrote: > >> I have a Mailman list working (for months) ... discuss at >> lists.MLDfamily.org. I've just created a new list ... discuss-adults at >> lists.MLDfamily.org. The web interface works fine for the new list and it >> shows lists.MLDfamily.org as its host_name. >> http://lists.mldfamily.org/mailman/admin/discuss-adults >> >> Both lists show up when I run the following command: >> /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org >> >> But deliveries to the Postfix mail server nets me this error on my local >> server (i.e. the email is making it fine to my server): >> Nov 28 11:44:11 darcee postfix/smtpd11450 : >> NOQUEUE: reject: RCPT from mail-pv0-f170.google.comhttp://74.125.83.170: 550 >> 5.1.1 : Recipient address rejected: User >> unknown in virtual alias table; from=3D >> to=3D proto=3DESMTP >> helo=3D >> >> Deliveries to the initial discuss list at this virtual domain continue to >> work but discuss-adults give the virtual alias table error. >> >> What do I need to do to get this new list into the virtual domain table? > [...] > >> FWIW, this is the process I used to create the list: >> (did not need to create the virtual domain since it already existed) >> Stopped the mail server using server admin > > > It isn't necessary to stop the Postfix or Mailman > > >> sudo /usr/share/mailman/bin/rmlist -a discuss-adults (to remove all residual >> old list stuff) >> sudo /usr/share/mailman/bin/newlist discuss-adults > > > which creates the list in the DEFAULT_URL_HOST domain. > > >> sudo /usr/share/mailman/bin/list_lists new list showed up >> sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org new list did >> not show up > > > This creates the list in the DEFAULT_URL_HOST domain > > >> sudo /usr/share/mailman/bin/withlist -l -r fix_url discuss-adults -u >> lists.MLDfamily.org >> sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org new list now >> shows up at the proper virtual domain > > > and fix_url "fixed" it , but didn't update virtual-mailman. > > >> sudo /usr/share/mailman/bin/genaliases > > > but the above did, but the fix_url and genaliases could have been > avoided by just specifying '-u lists.mldfamily.org' to newlist. > > >> sudo postfix reload failed since mail server was stopped >> started mail server using server admin > > > It is not necessary to stop/start or reload Postfix when you make table > changes. This is only needed if you make configuration changes such as > changing main.cf or master.cf. > > >> To confirm the updates of the virtual alias table I did the following: >> ls -l /var/mailman/data aliases, aliases.db, virtual-mailman, & >> virtual-mailman.db all were time stamped the last few minutes >> Looking inside aliases and virtual-mailman conformed the proper entries. > > > You show the aliases. The virtual-mailman entries should be different. > E.g., entries like > > discuss at lists.mldfamily.org discuss > discuss-admin at lists.mldfamily.org discuss-admin > etc., and > > discuss-adults at lists.mldfamily.org discuss-adults > discuss-admin-adults at lists.mldfamily.org discuss-admin-adults > etc. > > Are all the entries in virtual-mailman? if not, there may be case > sensitivity issues if the values in POSTFIX_STYLE_VIRTUAL_DOMAINS are > not all lower case. > > If the entries for the discuss-adults list are in virtual-mailman, > please post the output from > > sudo postconf -n > > >> Aliases and virtual-mailman both contained the following stanzas (in >> addition to others): >> >> ~~ >> # STANZA START: discuss >> # CREATED: Sun Nov 28 11:39:09 2010 >> discuss: "|/usr/share/mailman/mail/mailman post discuss" >> discuss-admin: "|/usr/share/mailman/mail/mailman admin discuss" >> discuss-bounces: "|/usr/share/mailman/mail/mailman bounces discuss" >> discuss-confirm: "|/usr/share/mailman/mail/mailman confirm discuss" >> discuss-join: "|/usr/share/mailman/mail/mailman join discuss" >> discuss-leave: "|/usr/share/mailman/mail/mailman leave discuss" >> discuss-owner: "|/usr/share/mailman/mail/mailman owner discuss" >> discuss-request: "|/usr/share/mailman/mail/mailman request discuss" >> discuss-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss" >> discuss-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss" >> # STANZA END: discuss >> ~~ >> # STANZA START: discuss-adults >> # CREATED: Sun Nov 28 11:39:10 2010 >> discuss-adults: "|/usr/share/mailman/mail/mailman post >> discuss-adults" >> discuss-adults-admin: "|/usr/share/mailman/mail/mailman admin >> discuss-adults" >> discuss-adults-bounces: "|/usr/share/mailman/mail/mailman bounces >> discuss-adults" >> discuss-adults-confirm: "|/usr/share/mailman/mail/mailman confirm >> discuss-adults" >> discuss-adults-join: "|/usr/share/mailman/mail/mailman join >> discuss-adults" >> discuss-adults-leave: "|/usr/share/mailman/mail/mailman leave >> discuss-adults" >> discuss-adults-owner: "|/usr/share/mailman/mail/mailman owner >> discuss-adults" >> discuss-adults-request: "|/usr/share/mailman/mail/mailman request >> discuss-adults" >> discuss-adults-subscribe: "|/usr/share/mailman/mail/mailman subscribe >> discuss-adults" >> discuss-adults-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe >> discuss-adults" >> # STANZA END: discuss-adults From mark at msapiro.net Tue Nov 30 03:28:49 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 29 Nov 2010 18:28:49 -0800 Subject: [Mailman-Users] Mailman - trouble creating a second list at anexisting virtual host In-Reply-To: Message-ID: Dean Suhr wrote: >First, please excuse me if my original post from yesterday posted several >times. It appears Google sees my outgoing message as the same ID as the >returned list message and silently discards the incoming list message making >me thing it was never sent out ... and they have no config option to change >this behavior. Arghhh! While all that is correct vis a vis Google, that wasn't the issue here. Your posts were held for moderation because you were a new list member. Your mod flag has now been cleared and your posts will now go directly to the list. If you want to confirm that your post has been received even though Google doesn't show you your post as received from the list, you can check the archives at or you can set your list option "Receive acknowledgement mail when you send mail to the list?" to Yes. [...] >Will I always have to manually post entries into virtual-mailman or is that >supposed to happen somewhere along the way? Is there a terminal command >line I missed or could have run in addition to cause this to happen >automatically? It should happen automatically. I suspect it didn't in your case because of certain case-sensitivities which are really bugs. If you make all your domain names in mm_cfg.py, i.e. DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST, additional domains in add_virtualhost() and domains in POSTFIX_STYLE_VIRTUAL_DOMAINS, all lower case and use all lower case in -u options to newlist or fix_url. Everything should work. The underlying bug is that domains in add_virtualhost() directives are lower-cased by Mailman but are matched case-sensitively to POSTFIX_STYLE_VIRTUAL_DOMAINS so if the POSTFIX_STYLE_VIRTUAL_DOMAINS domains are mixed or upper case, they don't match. If you make everything lower case and run fix_url with a lower case -u domain and then run genaliases, you should be OK. Note that manually editing virtual-mailman is unsafe because if genaliases is ever run, your changes will be lost. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From s.p.foster at leeds.ac.uk Mon Nov 29 17:28:20 2010 From: s.p.foster at leeds.ac.uk (Steve Foster) Date: Mon, 29 Nov 2010 16:28:20 +0000 (GMT) Subject: [Mailman-Users] text/plain flowed wrapping Message-ID: HI Folks, I'm trying to track down where a spurious "!" is being injected into a number of lines in a text/plain message that is being wrapped at about 990 chars. The "!" doesn't appear in the copy in the archive, just the email that is sent out. I've been lookin in the code in pythonlib/email and pythonlib/smtplib but can't see anything glaring. The only mention of RFC3676 is in Handler/Scrubber which appears to be the relevant RFC. Anythoughts? Cheers Steve For example (all chars converted to 'a' due to sensitivity of original): aa aaa aaaaaa aa aaa aaaaaaa, aaa aaaaaaaa aa aaaa aa aaaaaaaa aaaa aaaa aaa aaaa aaaa aa 2007/08 aa aaa aaaaaaa aaaaaaaaa, aa aaaaa aaa aaaa aaa. aaa aaaa aaaaaaaaa aa aaaaa aa aaa aaaaaaaaaaaa aa aaaa aaaaaaaa, aaaaa aaaaaaaaaaa aaaaaaaaaaa aaaaa aaaaaaaa aa aaaaaaaa aaaaaa (aaa), a.a. aaaaaaaa aaaaaaaa a aaaaaa aa aaa aaaaa aa aaa aaaaaaaaa aaaa aa aa aaaaa aa-aaaa. aa aaa aaaaa aa aaa aaaa aaaa, a aaa aaaaaa aa aaaaaaaa aa aaa aaaaaaa; aaaa aa aaaaaaaaaaaa aa aaa aaaaaaaaaa aa aaa aaaaaaaa aaaa. aaaa aaaaaaa aaa aaaaaaaa aa aaaa aaaa aaaa aaa aaa aa 'aaaaaaa aaaaaaaa', aa aaa aaa aaa aaaa aaaaaaaaa, aaa aa aaaaaaa a aaaaaaaaa aaaaaaaa aaaaa aaaaa aaaa aaaaaaaaa aaa aaaaaa aaaaa aa aaaaaaaa aa aaaa aaaaa aaa aaaaaaaaaaa aaaaaaaa aaaaaaa aaaaaa aaaaaaaaa aaa aaaa aaaaaaaaaaa aaaaaaaaa aaaa - aaaa aaaaa aaaa aaaaaa aaaa aa aaa aaaaa aaaaaaa 5-aaaa aaaaaaaa aaaaa aa aaaa aaaaaaaa aaa aaa aaaaaaa aaaaa, aaaaa aa aaa aaaaaaaaaa aaaaaaaa aaaaaaaa (aaa). aa aaa aaaaaa, aa was aaaa aaaaa aaaa aaa aaaaaaaaaaa aaaaaaa aaa 'aaa' aa aaaaaaaa (aaa aaaaaaaa aaaaaaa aa aaa) aaaaa aaaa aa aa aaaaaaa aa aaaaaaaaa aaaa aaaaa aa aaaaaaaaaa aaa aaaaaaa. aaaa aaaaa aaaa aaa aaaaaaaaaaa aaaaaaa aaaaa aaa aaa aaaaa aaaaaaaa aaaaaaa aaaa, aaa aa aaa aaaa aa aaaaa, aaaa aaaa aa aaa aaaaaa-aaaa aaaaaaaaa aaaaaaa. becomes aa aaa aaaaaa aa aaa aaaaaaa, aaa aaaaaaaa aa aaaa aa aaaaaaaa aaaa aaaa aaa aaaa aaaa aa 2007/08 aa aaa aaaaaaa aaaaaaaaa, aa aaaaa aaa aaaa aaa. aaa aaaa aaaaaaaaa aa aaaaa aa aaa aaaaaaaaaaaa aa aaaa aaaaaaaa, aaaaa aaaaaaaaaaa aaaaaaaaaaa aaaaa aaaaaaaa aa aaaaaaaa aaaaaa (aaa), a.a. aaaaaaaa aaaaaaaa a aaaaaa aa aaa aaaaa aa aaa aaaaaaaaa aaaa aa aa aaaaa aa-aaaa. aa aaa aaaaa aa aaa aaaa aaaa, a aaa aaaaaa aa aaaaaaaa aa aaa aaaaaaa; aaaa aa aaaaaaaaaaaa aa aaa aaaaaaaaaa aa aaa aaaaaaaa aaaa. aaaa aaaaaaa aaa aaaaaaaa aa aaaa aaaa aaaa aaa aaa aa 'aaaaaaa aaaaaaaa', aa aaa aaa aaa aaaa aaaaaaaaa, aaa aa aaaaaaa a aaaaaaaaa aaaaaaaa aaaaa aaaaa aaaa aaaaaaaaa aaa aaaaaa aaaaa aa aaaaaaaa aa aaaa aaaaa aaa aaaaaaaaaaa aaaaaaaa aaaaaaa aaaaaa aaaaaaaaa aaa aaaa aaaaaaaaaaa aaaaaaaaa aaaa - aaaa aaaaa aaaa aaaaaa aaaa aa aaa aaaaa aaaaaaa 5-aaaa aaaaaaaa aaaaa aa aaaa aaaaaaaa aaa aaa aaaaaaa aaaaa, aaaaa aa aaa aaaaaaaaaa aaaaaaaa aaaaaaaa (aaa). aa aaa aaaaaa, aa wa! s aaaa aaaaa aaaa aaa aaaaaaaaaaa aaaaaaa aaa 'aaa' aa aaaaaaaa (aaa aaaaaaaa aaaaaaa aa aaa) aaaaa aaaa aa aa aaaaaaa aa aaaaaaaaa aaaa aaaaa aa aaaaaaaaaa aaa aaaaaaa. aaaa aaaaa aaaa aaa aaaaaaaaaaa aaaaaaa aaaaa aaa aaa aaaaa aaaaaaaa aaaaaaa aaaa, aaa aa aaa aaaa aa aaaaa, aaaa aaaa aa aaa aaaaaa-aaaa aaaaaaaaa aaaaaaa. -- Steve Foster Email: s.p.foster at leeds.ac.uk From web at govanhillbaths.com Mon Nov 29 18:01:15 2010 From: web at govanhillbaths.com (Tim) Date: Mon, 29 Nov 2010 17:01:15 +0000 Subject: [Mailman-Users] Django itegration In-Reply-To: References: Message-ID: <4CF3DC5B.5020101@govanhillbaths.com> Hi all, Anybody done the django_mailman thing? I'm sure the documentation could be a bit better. Any help appreciated. Tim From Ralf.Hildebrandt at charite.de Tue Nov 30 16:44:03 2010 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Tue, 30 Nov 2010 16:44:03 +0100 Subject: [Mailman-Users] text/plain flowed wrapping In-Reply-To: References: Message-ID: <20101130154403.GM10924@charite.de> * Steve Foster : > HI Folks, > > I'm trying to track down where a spurious "!" is being injected into > a number of lines in a text/plain message that is being wrapped at > about 990 chars. > > The "!" doesn't appear in the copy in the archive, just the email > that is sent out. I've been lookin in the code in pythonlib/email and > pythonlib/smtplib but can't see anything glaring. The only mention of > RFC3676 is in Handler/Scrubber which appears to be the relevant RFC. > > Anythoughts? Sounds like an MTA issue. Have you checked that? Should be easy using tcpdump or something along these lines. -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From s.p.foster at leeds.ac.uk Tue Nov 30 17:15:58 2010 From: s.p.foster at leeds.ac.uk (Steve Foster) Date: Tue, 30 Nov 2010 16:15:58 +0000 (GMT) Subject: [Mailman-Users] text/plain flowed wrapping In-Reply-To: <20101130154403.GM10924@charite.de> References: <20101130154403.GM10924@charite.de> Message-ID: On Tue, 30 Nov 2010, Ralf Hildebrandt wrote: > Sounds like an MTA issue. Have you checked that? Should be easy using > tcpdump or something along these lines. Already tested that one, put the message through a server with identical setup MTA (except no Mailman) and the message was flowed correctly without the '!'. Cheers Steve -- Steve Foster Email: s.p.foster at leeds.ac.uk Unix team Phone: 0113 343 7225 Information Systems Services Fax: 0113 343 5411 University of Leeds Leeds LS2 9JT From Ralf.Hildebrandt at charite.de Tue Nov 30 17:17:31 2010 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Tue, 30 Nov 2010 17:17:31 +0100 Subject: [Mailman-Users] text/plain flowed wrapping In-Reply-To: References: <20101130154403.GM10924@charite.de> Message-ID: <20101130161731.GN10924@charite.de> * Steve Foster : > On Tue, 30 Nov 2010, Ralf Hildebrandt wrote: > > >Sounds like an MTA issue. Have you checked that? Should be easy using > >tcpdump or something along these lines. > > Already tested that one, put the message through a server with > identical setup MTA (except no Mailman) and the message was flowed > correctly without the '!'. Because 990 Characters is usually the line length limit of an MTA, so I guessed some MAT would truncate (truncate or just insert the "!"?) the message... -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From mark at msapiro.net Tue Nov 30 17:30:43 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 30 Nov 2010 08:30:43 -0800 Subject: [Mailman-Users] text/plain flowed wrapping In-Reply-To: <20101130154403.GM10924@charite.de> References: <20101130154403.GM10924@charite.de> Message-ID: <4CF526B3.5030208@msapiro.net> On 11/30/2010 7:44 AM, Ralf Hildebrandt wrote: > * Steve Foster : >> HI Folks, >> >> I'm trying to track down where a spurious "!" is being injected into >> a number of lines in a text/plain message that is being wrapped at >> about 990 chars. >> >> The "!" doesn't appear in the copy in the archive, just the email >> that is sent out. I've been lookin in the code in pythonlib/email and >> pythonlib/smtplib but can't see anything glaring. The only mention of >> RFC3676 is in Handler/Scrubber which appears to be the relevant RFC. >> >> Anythoughts? > > Sounds like an MTA issue. Have you checked that? Should be easy using > tcpdump or something along these lines. > It could be an MTA issue, but it seems to me more likely to be an MUA issue. The reason I think it is not as likely to be an MTA is if the original is Format="flowed", it would have no long lines so there would be no reason for an MTA to do anything to the message in transmission. It is clearly not a Mailman/Python issue, at least with the versions in use by this list, since the OP as delivered to me from the list and viewed with Thunderbird did not show any spurious "!" or line break in the "before" example text. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From s.p.foster at leeds.ac.uk Tue Nov 30 18:39:25 2010 From: s.p.foster at leeds.ac.uk (Steve Foster) Date: Tue, 30 Nov 2010 17:39:25 +0000 (GMT) Subject: [Mailman-Users] text/plain flowed wrapping In-Reply-To: <4CF526B3.5030208@msapiro.net> References: <20101130154403.GM10924@charite.de> <4CF526B3.5030208@msapiro.net> Message-ID: On Tue, 30 Nov 2010, Mark Sapiro wrote: > On 11/30/2010 7:44 AM, Ralf Hildebrandt wrote: >> Sounds like an MTA issue. Have you checked that? Should be easy using >> tcpdump or something along these lines. >> > > It could be an MTA issue, but it seems to me more likely to be an MUA > issue. The reason I think it is not as likely to be an MTA is if the > original is Format="flowed", it would have no long lines so there would > be no reason for an MTA to do anything to the message in transmission. Just been looking at this in more detail, the message is being sent with the headers: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The encoding is maintained through the Mailman queues and handlers. At some point between it leaving Mailman and coming out the other end of the MTA (sendmail) the encoding gets mangled. I'll dig a bit more deeply in the MTA and see if its playing silly beggers. Cheers Steve -- Steve Foster Email: s.p.foster at leeds.ac.uk Unix team Phone: 0113 343 7225 Information Systems Services Fax: 0113 343 5411 University of Leeds Leeds LS2 9JT From chris.tandiono at gmail.com Tue Nov 30 21:18:01 2010 From: chris.tandiono at gmail.com (Chris Tandiono) Date: Tue, 30 Nov 2010 12:18:01 -0800 Subject: [Mailman-Users] Django itegration In-Reply-To: <4CF3DC5B.5020101@govanhillbaths.com> References: <4CF3DC5B.5020101@govanhillbaths.com> Message-ID: On Mon, 29 Nov 2010 09:01:15 -0800, Tim wrote: > Hi all, > > Anybody done the django_mailman thing? > > I'm sure the documentation could be a bit better. > > Any help appreciated. > Tim Not personally. However, if you add Mailman to your Python path, in your Django views you can just do things like "from Mailman import MailList" or "from Mailman import Utils", which might be a better choice depending on what you want to do. -- Chris From guillaume.chartrand at Collanaud.Qc.Ca Tue Nov 30 16:45:26 2010 From: guillaume.chartrand at Collanaud.Qc.Ca (Guillaume Chartrand) Date: Tue, 30 Nov 2010 15:45:26 +0000 Subject: [Mailman-Users] pending request email unreadable Message-ID: <23A9B7CAD2EEE64F8FC5BF1E8AB5345F0CAD20@csr-exch.Intranet.Collanaud.Qc.Ca> Hi, I receive some pending request for a list who I'm the administrator and moderator and in the message body on the web interface is unreadable, it's just something like that Sm9saSBib25uZXQgZGUgbGFpbmUgbGFpc3PDqSBwb3VyIG1vcnQgYXUgZGVybmllciBJbnRlckNB Q0Ugw6AgQ2hpY291dGltaS4gSWwgZXN0IGJydW4gZXQgYmVpZ2UgYXZlYyBkZXMgb3JlaWxsZXMg ZXQgZGVzIGxhbmnDqHJlcyBwb3VyIGF0dGFjaGVyIGF1IGNvdeKApi4NClF1ZWxxdeKAmXVuIGEg Z2Vsw6kgZGVzIG9yZWlsbGVzIGxlIHdlZWstZW5kIGRlcm5pZXI/Pz8/DQoNCk1hbm9uIExhcGll cnJlDQpNYW5vbiBMYXBpZXJyZQ0KYWdlbnRlIGRlIG1pbGlldSBldCByZXNwb25zYWJsZSBkZSBs J2Vudmlyb25uZW1lbnQNCmNvbnNlaWwgZGUgdmllIMOpdHVkaWFudGUNCkPDqWdlcCBkZSBjaGlj But if I approved this message it's send in readable format for all the user list. Why this can happens? I can't verify if it's appropriate content and I need to approve it to see it, it's not useful. I use mailman 2.1.6 on red hat 4 server with sendmail server and ASSP server to block spam. Some test message appears fine and some other is unreadable. ---------------------------- Guillaume Chartrand Technicien informatique C?gep r?gional de Lanaudi?re Centre administratif, Repentigny (450) 470-0911 poste 7218