From jerome at jolimont.fr Tue Jul 5 19:47:23 2016 From: jerome at jolimont.fr (=?UTF-8?B?SsOpcsO0bWU=?=) Date: Wed, 6 Jul 2016 01:47:23 +0200 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain Message-ID: <20160706014723.6065447c@bouzin.lan> Hi. I'm trying to configure mailman/postfix with virtual domains. Both postfix and mailman are installed using Debian packages. Postfix works with virtual domains domain1.tld and domain2.tld. I would like Mailman to serve mailing lists on lists.domain1.tld and lists.domain2.tld. I've been reading these, of course: http://www.gnu.org/software/mailman/mailman-install/postfix-integration.html http://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html AFAIU, postfix_to_mailman.py is not needed and not recommended, so I'd avoid it if possible: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718284 It appears in the configuration, but I tried both with and without. Here are (hopefully comprehensive) config files excerpts : ------------------------------------------------------------ mailman mm_cfg.py ------------------------------------------------------------ DEFAULT_EMAIL_HOST = 'lists.domain1.tld' DEFAULT_URL_HOST = 'domain1.tld' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost ('domain2.tld', 'lists.domain2.tld') MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'lists.domain1.tld', 'lists.domain2.tld', ] ------------------------------------------------------------ ------------------------------------------------------------ postfix main.cf ------------------------------------------------------------ myorigin = domain1.tld mydomain = domain1.tld myhostname = domain1.tld # System users alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all # Virtual users virtual_mailbox_base = /var/mail/vmail/ virtual_mailbox_domains = proxy:pgsql:/etc/postfix/virtual-domains.cf virtual_mailbox_maps = proxy:pgsql:/etc/postfix/virtual-mailbox-maps.cf virtual_uid_maps = static:113 virtual_gid_maps = static:121 virtual_alias_maps = proxy:pgsql:/etc/postfix/virtual-alias-maps.cf, hash:/var/lib/mailman/data/virtual-mailman # Dovecot dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # Mailman # cf. /etc/mailman/postfix-to-mailman.py # relay_domains = lists.domain1.tld, lists.domain2.tld # relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman # transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 ------------------------------------------------------------ postfix master.cf ------------------------------------------------------------ mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} ------------------------------------------------------------ ------------------------------------------------------------ postfix transport ------------------------------------------------------------ lists.domain1.tld mailman: lists.domain2.tld mailman: ------------------------------------------------------------ ------------------------------------------------------------ DNS for domain1 ------------------------------------------------------------ @ 3600 IN A xxx.xxx.xxx.xxx lists 3600 IN A xxx.xxx.xxx.xxx @ 3600 IN MX 10 domain1.tld. @ 3600 IN TXT "v=spf1 a mx -all" ------------------------------------------------------------ I created a test list 'test at lists.domain1.tld' using mailman's bin/newlist. ------------------------------------------------------------ mailman aliases ------------------------------------------------------------ mailman: "|/var/lib/mailman/mail/mailman post mailman" mailman-admin: "|/var/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/var/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/var/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/var/lib/mailman/mail/mailman join mailman" mailman-leave: "|/var/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/var/lib/mailman/mail/mailman owner mailman" mailman-request: "|/var/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/var/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe mailman" test: "|/var/lib/mailman/mail/mailman post test" test-admin: "|/var/lib/mailman/mail/mailman admin test" test-bounces: "|/var/lib/mailman/mail/mailman bounces test" test-confirm: "|/var/lib/mailman/mail/mailman confirm test" test-join: "|/var/lib/mailman/mail/mailman join test" test-leave: "|/var/lib/mailman/mail/mailman leave test" test-owner: "|/var/lib/mailman/mail/mailman owner test" test-request: "|/var/lib/mailman/mail/mailman request test" test-subscribe: "|/var/lib/mailman/mail/mailman subscribe test" test-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe test" ------------------------------------------------------------ ------------------------------------------------------------ mailman virtual-mailman ------------------------------------------------------------ mailman at lists.domain1.tld mailman mailman-admin at lists.domain1.tld mailman-admin mailman-bounces at lists.domain1.tld mailman-bounces mailman-confirm at lists.domain1.tld mailman-confirm mailman-join at lists.domain1.tld mailman-join mailman-leave at lists.domain1.tld mailman-leave mailman-owner at lists.domain1.tld mailman-owner mailman-request at lists.domain1.tld mailman-request mailman-subscribe at lists.domain1.tld mailman-subscribe mailman-unsubscribe at lists.domain1.tld mailman-unsubscribe test at lists.domain1.tld test test-admin at lists.domain1.tld test-admin test-bounces at lists.domain1.tld test-bounces test-confirm at lists.domain1.tld test-confirm test-join at lists.domain1.tld test-join test-leave at lists.domain1.tld test-leave test-owner at lists.domain1.tld test-owner test-request at lists.domain1.tld test-request test-subscribe at lists.domain1.tld test-subscribe test-unsubscribe at lists.domain1.tld test-unsubscribe ------------------------------------------------------------ Test 1: Connecting to the server's webmail and sending a mail to the test list. I get this error: (expanded from ): user unknown I read the FAQ (http://wiki.list.org/x/uYA9) and double checked I do have a A record for lists.domain1.tld. Test 2: Sending a mail to the test list using my mail client, the SMTP being the server itself (postfix/dovecot). The message does not even leave the mail client. I get this error: 554 5.7.1 : Relay access denied Since both methods use the same SMTP, I wonder why I get this difference between both tests. I tried both commenting / uncommenting the 'transport_maps' line transport_maps = hash:/etc/postfix/transport in main.cf, which, IIUC, should activate/deactivate postfix_to_mailman.py, and it didn't make any difference. I'd appreciate any hint. I obviously lack postfix expertise and my config is likely to contain blatant issues. Unfortunately, I didn't find any step-by-step guide. The tutorials I found either have virtual domains but no subdomain, or a dedicated 'lists' subdomain but for only one domain, no multiple virtuals. And most of them use postfix_to_mailman.py which I understand should be avoided. (Also, please redirect me if this is not the right place to ask.) Thanks. -- J?r?me From mark at msapiro.net Tue Jul 5 23:08:51 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 5 Jul 2016 20:08:51 -0700 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain In-Reply-To: <20160706014723.6065447c@bouzin.lan> References: <20160706014723.6065447c@bouzin.lan> Message-ID: <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> On 7/5/16 4:47 PM, J?r?me wrote: > > AFAIU, postfix_to_mailman.py is not needed and not recommended, so I'd > avoid it if possible: That's good. > Here are (hopefully comprehensive) config files excerpts : > > ------------------------------------------------------------ > mailman mm_cfg.py > ------------------------------------------------------------ > > DEFAULT_EMAIL_HOST = 'lists.domain1.tld' > DEFAULT_URL_HOST = 'domain1.tld' > > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > add_virtualhost ('domain2.tld', 'lists.domain2.tld') > > MTA = 'Postfix' > > POSTFIX_STYLE_VIRTUAL_DOMAINS = [ > 'lists.domain1.tld', > 'lists.domain2.tld', > ] The above is all good. > ------------------------------------------------------------ > > > ------------------------------------------------------------ > postfix main.cf > ------------------------------------------------------------ > > myorigin = domain1.tld > mydomain = domain1.tld > myhostname = domain1.tld > > # System users > alias_maps = hash:/etc/aliases You need to add hash:/var/lib/mailman/data/aliases to alias_maps. > alias_database = hash:/etc/aliases > > mydestination = localhost > relayhost = > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > mailbox_size_limit = 0 > recipient_delimiter = + > inet_interfaces = all > > # Virtual users > virtual_mailbox_base = /var/mail/vmail/ > virtual_mailbox_domains = proxy:pgsql:/etc/postfix/virtual-domains.cf > virtual_mailbox_maps = proxy:pgsql:/etc/postfix/virtual-mailbox-maps.cf > virtual_uid_maps = static:113 > virtual_gid_maps = static:121 > virtual_alias_maps = proxy:pgsql:/etc/postfix/virtual-alias-maps.cf, > hash:/var/lib/mailman/data/virtual-mailman > > # Dovecot > dovecot_destination_recipient_limit = 1 > virtual_transport = dovecot > > # Mailman > # cf. /etc/mailman/postfix-to-mailman.py > # relay_domains = lists.domain1.tld, lists.domain2.tld > # relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman > # transport_maps = hash:/etc/postfix/transport > mailman_destination_recipient_limit = 1 transport_maps is commented which is good. mailman_destination_recipient_limit = 1 is for postfix_to_mailmam, but it won't hurt as you aren't using the 'mailman' transport. > ------------------------------------------------------------ > postfix master.cf > ------------------------------------------------------------ > > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} > > > ------------------------------------------------------------ > > ------------------------------------------------------------ > postfix transport > ------------------------------------------------------------ > > lists.domain1.tld mailman: > lists.domain2.tld mailman: The 'mailman' transport in main.cf and the references to it in postfix/transport are all unused (a good thing because it's all postfix-to-mailman stuff) because transport_maps is commented. > ------------------------------------------------------------ > mailman aliases > ------------------------------------------------------------ Which is unreferenced which is the problem. Add it to alias_maps. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jimpop at gmail.com Wed Jul 6 09:21:27 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Wed, 6 Jul 2016 09:21:27 -0400 Subject: [Mailman-Users] Filtering out Digest replies Message-ID: I've been inspired by something I read somewhere else. I have long thought that mailing lists should be configured to reject messages with a Subject of "Re: [the subject format for the list's digest messages]". Maybe a scan of the message content for a copy of the digest prologue would be a good idea as well. and now I want to implement something like this. Will this generic Spam filter work: Subject: Re: \[.*\] .* Digest, Vol [0-9]+, Issue [0-9]+ Tia, -Jim P. From malcolm.austen at weald.org.uk Wed Jul 6 09:44:39 2016 From: malcolm.austen at weald.org.uk (Malcolm Austen) Date: Wed, 06 Jul 2016 14:44:39 +0100 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: Message-ID: On Wed, 06 Jul 2016 14:21:27 +0100, Jim Popovitch wrote: > I've been inspired by something I read somewhere else. > > I have long thought that mailing lists should be > configured to reject messages with a Subject of > "Re: [the subject format for the list's digest messages]". > Maybe a scan of the message content for a copy > of the digest prologue would be a good idea as well. > > and now I want to implement something like this. > > Will this generic Spam filter work: > > Subject: Re: \[.*\] .* Digest, Vol [0-9]+, Issue [0-9]+ As I hold such catches rather than bin them, I get by with a slew of less fancy regexps against any header. They all pretty much like - ^subject:.*digest.* with checks for test, spam, virus, scam, help, ... Some are worth being slightly fancy on, eg - ^subject:.*\btest.* - so latest gets through :-) Don't forget - ^subject:.*The results of your email commands - and the final triplet so messages with no subject get caught, see Mark's post: https://mail.python.org/pipermail/mailman-users/2007-March/056119.html Malcolm. -- Malcolm Austen GENUKI trustee Pedigree User Group Oxfordshire FHS or From bryan at skiblack.com Wed Jul 6 10:29:00 2016 From: bryan at skiblack.com (Bryan Blackwell) Date: Wed, 6 Jul 2016 10:29:00 -0400 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: Message-ID: > On Jul 6, 2016, at 9:21 AM, Jim Popovitch wrote: > > I've been inspired by something I read somewhere else. > > I have long thought that mailing lists should be > configured to reject messages with a Subject of > "Re: [the subject format for the list's digest messages]". > Maybe a scan of the message content for a copy > of the digest prologue would be a good idea as well. > > and now I want to implement something like this. > > > Will this generic Spam filter work: > > Subject: Re: \[.*\] .* Digest, Vol [0-9]+, Issue [0-9]+ > > > Tia, > > -Jim P. Mine is simpler than that. Name of the list is VirtualVairs, thus: Subject: .*VirtualVairs Digest, Vol.* --Bryan From Greg.Lindsay at microsoft.com Tue Jul 5 23:19:53 2016 From: Greg.Lindsay at microsoft.com (Greg Lindsay) Date: Wed, 6 Jul 2016 03:19:53 +0000 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: References: Message-ID: Hi, I am running Mailman v 2.1.20 & have been trying to filter out Chinese spam messages with no luck. A few typical subjects are below: Subject: ??????????????????? Subject: ?1?1?1???1?1?? Subject: ?????????????????? Under Privacy options/Spam filters I have created header filters such as the three below. These aren't working. I was under the impression that [abcd] will discard all mail with a, b, c, or d in the subject line. I've tried including a hundred characters and a single character, but neither works. ^Subject:\*[????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????] ^Subject:\?utf-8\?B\?[56] ^Subject:\*[????????] What am I doing wrong here? Is there something about the character encoding that prevents this filter from working? Thanks, -Greg From jimpop at gmail.com Wed Jul 6 11:07:18 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Wed, 6 Jul 2016 11:07:18 -0400 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: Message-ID: On Wed, Jul 6, 2016 at 10:29 AM, Bryan Blackwell wrote: > >> On Jul 6, 2016, at 9:21 AM, Jim Popovitch wrote: >> >> I've been inspired by something I read somewhere else. >> >> I have long thought that mailing lists should be >> configured to reject messages with a Subject of >> "Re: [the subject format for the list's digest messages]". >> Maybe a scan of the message content for a copy >> of the digest prologue would be a good idea as well. >> >> and now I want to implement something like this. >> >> >> Will this generic Spam filter work: >> >> Subject: Re: \[.*\] .* Digest, Vol [0-9]+, Issue [0-9]+ >> >> >> Tia, >> >> -Jim P. > > Mine is simpler than that. Name of the list is VirtualVairs, thus: > > Subject: .*VirtualVairs Digest, Vol.* > > --Bryan Do people feel there is a need for a new Sender filter option "Process Digest Replies" (Accept|Hold|Reject|Discard) ? -Jim P. From mark at msapiro.net Wed Jul 6 11:56:29 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Jul 2016 08:56:29 -0700 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: References: Message-ID: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> On 7/5/16 8:19 PM, Greg Lindsay via Mailman-Users wrote: > Hi, > > I am running Mailman v 2.1.20 & have been trying to filter out Chinese spam messages with no luck. A few typical subjects are below: > > Subject: ??????????????????? > Subject: ?1?1?1???1?1?? > Subject: ?????????????????? > > Under Privacy options/Spam filters I have created header filters such as the three below. These aren't working. I was under the impression that [abcd] will discard all mail with a, b, c, or d in the subject line. I've tried including a hundred characters and a single character, but neither works. > > ^Subject:\*[????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????] > > ^Subject:\?utf-8\?B\?[56] > > ^Subject:\*[????????] > > What am I doing wrong here? Is there something about the character encoding that prevents this filter from working? There are a couple of things here. Your 3 regexps above have no space after Subject:. That notwithstanding, none of them will match what you're trying to match. The second appears to be an attempt to match an RFC2047 encoded word, but the encoded word would begin '=?utf-8?B?...' and your regexp is missing the '='. I'm not sure what the first and third are doing with the literal asterisk. However, this is not the real problem. The real issue is that the headers matched by the header_filter_rules regexps have been RFC2047 decoded and then encoded in Mailman's character set for the list's preferred language. If the list's preferred language is not one whose character set is utf-8 or some Chinese character set, this probably results in Subject: ??????... -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Jul 6 12:22:38 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Jul 2016 09:22:38 -0700 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: Message-ID: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> On 7/6/16 8:07 AM, Jim Popovitch wrote: >> >>> On Jul 6, 2016, at 9:21 AM, Jim Popovitch wrote: >>> >>> I've been inspired by something I read somewhere else. >>> >>> I have long thought that mailing lists should be >>> configured to reject messages with a Subject of >>> "Re: [the subject format for the list's digest messages]". >>> Maybe a scan of the message content for a copy >>> of the digest prologue would be a good idea as well. >>> >>> and now I want to implement something like this. There is a custom handler at that holds messages for various reasons including digest subjects and quoting digest boiler plate. > Do people feel there is a need for a new Sender filter option "Process > Digest Replies" > (Accept|Hold|Reject|Discard) ? This could be good for Mailman 3. I'm reluctant to do this in 2.1 because it really should be 'end of life'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jimpop at gmail.com Wed Jul 6 14:37:07 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Wed, 6 Jul 2016 14:37:07 -0400 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> Message-ID: On Wed, Jul 6, 2016 at 12:22 PM, Mark Sapiro wrote: > On 7/6/16 8:07 AM, Jim Popovitch wrote: >>> >>>> On Jul 6, 2016, at 9:21 AM, Jim Popovitch wrote: >>>> >>>> I've been inspired by something I read somewhere else. >>>> >>>> I have long thought that mailing lists should be >>>> configured to reject messages with a Subject of >>>> "Re: [the subject format for the list's digest messages]". >>>> Maybe a scan of the message content for a copy >>>> of the digest prologue would be a good idea as well. >>>> >>>> and now I want to implement something like this. > > > There is a custom handler at > that holds messages for > various reasons including digest subjects and quoting digest boiler plate. > > >> Do people feel there is a need for a new Sender filter option "Process >> Digest Replies" >> (Accept|Hold|Reject|Discard) ? > > > This could be good for Mailman 3. I'm reluctant to do this in 2.1 > because it really should be 'end of life'. I get that, but 2.1 is going to be around for at least several more years considering LTS distros, etc. Those distros will most certainly upgrade Mailman for fixes/improvements, whereas probably not to do a major switch to mm3 (plus supported dependencies, etc) -Jim P. From Greg.Lindsay at microsoft.com Wed Jul 6 13:51:34 2016 From: Greg.Lindsay at microsoft.com (Greg Lindsay) Date: Wed, 6 Jul 2016 17:51:34 +0000 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> Message-ID: Thanks for the reply. I was going off some examples I found, but should have known better than to use a \* in the regexp. This is likely what is causing the filters to fail. The encoding example was something I was trying based off another thread I found, but I've deleted this rule. I assume the text box that is asking to input a "Spam Filter Regexp" will attempt to match all text in the header. Since all headers include the text "Subject:" and that is the area of the header that I want to filter, this is why "^Subject:" is specified. If I eliminate the literal asterisk and just change this to an asterisk, i.e.: "^Subject:*" that should take care of the space, right? Sometimes the mails come in with mixed Chinese and English characters, so if an English character is first in the subject and my filter specifies that it must be a space followed by a Chinese character, then the filter would fail to catch this...I think what is needed is this: ^Subject:*[list of all Chinese characters here] I don't understand the use of an equals sign in the regexp. Isn't this implied? Thanks, -Greg -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+greg.lindsay=microsoft.com at python.org] On Behalf Of Mark Sapiro Sent: Wednesday, July 6, 2016 8:56 AM To: mailman-users at python.org Subject: Re: [Mailman-Users] Chinese characters spam filter? On 7/5/16 8:19 PM, Greg Lindsay via Mailman-Users wrote: > Hi, > > I am running Mailman v 2.1.20 & have been trying to filter out Chinese spam messages with no luck. A few typical subjects are below: > > Subject: ??????????????????? > Subject: ?1?1?1???1?1?? > Subject: ?????????????????? > > Under Privacy options/Spam filters I have created header filters such as the three below. These aren't working. I was under the impression that [abcd] will discard all mail with a, b, c, or d in the subject line. I've tried including a hundred characters and a single character, but neither works. > > ^Subject:\*[?????????????????????????????????????????????????????????? > ??????????????????????????????????????????????????????????????] > > ^Subject:\?utf-8\?B\?[56] > > ^Subject:\*[????????] > > What am I doing wrong here? Is there something about the character encoding that prevents this filter from working? There are a couple of things here. Your 3 regexps above have no space after Subject:. That notwithstanding, none of them will match what you're trying to match. The second appears to be an attempt to match an RFC2047 encoded word, but the encoded word would begin '=?utf-8?B?...' and your regexp is missing the '='. I'm not sure what the first and third are doing with the literal asterisk. However, this is not the real problem. The real issue is that the headers matched by the header_filter_rules regexps have been RFC2047 decoded and then encoded in Mailman's character set for the list's preferred language. If the list's preferred language is not one whose character set is utf-8 or some Chinese character set, this probably results in Subject: ??????... -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://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: https://mail.python.org/mailman/options/mailman-users/greg.lindsay%40microsoft.com From mark at msapiro.net Wed Jul 6 15:41:04 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Jul 2016 12:41:04 -0700 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> Message-ID: <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> On 7/6/16 10:51 AM, Greg Lindsay wrote: > > I assume the text box that is asking to input a "Spam Filter Regexp" > will attempt to match all text in the header. The regexps match against a block of text which consists of the all of the message and sub-part headers RFC 2047 decoded and separated by newline characters and matched in multiline mode so that '^' matches the beginning of the string or immediately following a newline. > Since all headers > include the text "Subject:" and that is the area of the header that I > want to filter, this is why "^Subject:" is specified. Correct. > If I eliminate > the literal asterisk and just change this to an asterisk, i.e.: > "^Subject:*" that should take care of the space, right? Regexps are not globs. Asterisk doesn't mean 0 or more of anything. It is a repetition which means 0 or more of the preceding. "^Subject:*" will match the beginning of the string or a newline followed by 'Subject' followed by 0 or more ':'. You would want "^Subject:.*" to match Subject: followed by 0 or more of any character. See . > Sometimes the > mails come in with mixed Chinese and English characters, so if an > English character is first in the subject and my filter specifies > that it must be a space followed by a Chinese character, then the > filter would fail to catch this...I think what is needed is this: > > ^Subject:*[list of all Chinese characters here] That should be ^Subject:.*[list of all Chinese characters here] except that if your list's preferred language is English and you haven't changed Mailman's character set for English from ASCII to UTF-8, the text you are matching against won't contain any Chinese characters because the decoded headers are converted to the character set of the list's preferred language and all the Chinese characters will be converted to '?'. You might try something like ^Subject:.*\?{4,} This will match any subject that contains 4 or more non-ascii characters in a row. Unfortunately, it will also match Subject: WTF is happening here???? but you could try some number other than 4 but greater than 1 > I don't understand the use of an equals sign in the regexp. Isn't > this implied? I was referring to an RFC 2047 encoded word which you were apparently trying to match with ^Subject:\?utf-8\?B\?[56] except the literal RFC2047 encoding would not be '?utf-8?B?...'. It would be '=?utf-8?B?...'. I.e. the '=' is part of the string you would be trying to match. See . However, you can't match RFC2047 encodings with header_filter_rules because the headers you are matching against have already been RFC2047 decoded. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jerome at jolimont.fr Wed Jul 6 16:51:38 2016 From: jerome at jolimont.fr (=?UTF-8?B?SsOpcsO0bWU=?=) Date: Wed, 6 Jul 2016 22:51:38 +0200 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain In-Reply-To: <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> References: <20160706014723.6065447c@bouzin.lan> <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> Message-ID: <20160706225138.6799c97d@bouzin.lan> Hi. Thank you Mark for your detailed answer. Le Tue, 5 Jul 2016 20:08:51 -0700, Mark Sapiro a ?crit : > > # System users > > alias_maps = hash:/etc/aliases > > You need to add hash:/var/lib/mailman/data/aliases to alias_maps. Indeed I didn't do that. It is indicated in the docs : http://www.gnu.org/software/mailman/mailman-install/postfix-integration.html but I guess I assumed this applied only to non-virtual domains. Sorry about that. Now, I'm wondering. The note in the docs says: > Mailman's support of virtual domains is limited in that list names > must be globally unique within a single Mailman instance, i.e., two > lists may not have the same name even if they are in different > domains. I understand I can't have two lists with the same name on the server, like list at lists.domain1.tld and list at lists.domain2.tld as they would conflict. But may I have a mailbox like test at domain1.tld and a list like test at lists.domain1.tld ? Since the alias reads test: "|/var/lib/mailman/mail/mailman post test" test-admin: "|/var/lib/mailman/mail/mailman admin test" ... I assumed mailman would have everything called "test at ..." be directed to mailman. Thinking twice, this file is used for local aliases, so it would only conflict with system users/aliases, not virtual aliases. Or not conflict at all ? I'm not sure... Avoiding conflicts is the reason I'm using the 'lists' subdomain. Back to the subject, I added hash:/var/lib/mailman/data/aliases to alias_maps and I'm still getting the same error : (expanded from ): user unknown (I did restart Postfix, even Mailman, I even restarted the whole server.) Any known potential cause for this? I don't think there is more to the config than what I already sent. I'm not sure how it all works. AFAIU, virtual-mailman makes sure that test at lists.domain1.tld -> test and then, aliases makes sure that test -> "|/var/lib/mailman/mail/mailman post test" It looks like the first step succeeds, but then postfix appends domain1.tld to test before looking up in aliases. Could it be related to that feature that makes postfix append $myorigin to unqualified recipient addresses. (http://www.postfix.org/BASIC_CONFIGURATION_README.html#myorigin) As a quick test, if I connect as local user and send a message using mail nobody here's what I get in the logs: postfix/pipe[2909]: 0EC5AC15D: to=, orig_to=, relay=dovecot, delay=0.11, delays=0.04/0.01/0/0.07, dsn=5.1.1, status=bounced (user unknown) This seems to indicate that the postfix configuration is wrong, as /etc/aliases are also broken. Looks like it boils down to a postfix configuration issue, so it may be out of scope here... I can find references on the Internet to issues that seem related, but didn't find any satisfying answer. In any case, here's the whole Postix config: -------------------------------------------------------- postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases append_dot_mydomain = no biff = no config_directory = /etc/postfix disable_vrfy_command = yes dovecot_destination_recipient_limit = 1 inet_interfaces = all mailbox_size_limit = 0 mydestination = localhost mydomain = domain1.tld myhostname = domain1.tld mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = domain1.tld recipient_delimiter = + relayhost = smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_required = yes smtpd_helo_restrictions = warn_if_reject reject_non_fqdn_helo_hostname, warn_if_reject reject_invalid_helo_hostname smtpd_recipient_restrictions = warn_if_reject reject_invalid_hostname, warn_if_reject reject_non_fqdn_hostname, warn_if_reject reject_non_fqdn_sender, warn_if_reject reject_non_fqdn_recipient, warn_if_reject reject_unknown_sender_domain, warn_if_reject reject_unknown_recipient_domain, permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination smtpd_relay_restrictions = smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_sender_restrictions = warn_if_reject reject_unknown_sender_domain, warn_if_reject reject_non_fqdn_sender smtpd_tls_cert_file = /etc/ssl/certs/dovecot.pem smtpd_tls_key_file = /etc/ssl/private/dovecot.pem smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes virtual_alias_maps = proxy:pgsql:/etc/postfix/virtual-alias-maps.cf, hash:/var/lib/mailman/data/virtual-mailman virtual_gid_maps = static:121 virtual_mailbox_base = /var/mail/vmail/ virtual_mailbox_domains = proxy:pgsql:/etc/postfix/virtual-domains.cf virtual_mailbox_maps = proxy:pgsql:/etc/postfix/virtual-mailbox-maps.cf virtual_transport = dovecot virtual_uid_maps = static:113 -------------------------------------------------------- Thanks. -- J?r?me From mark at msapiro.net Wed Jul 6 17:43:33 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Jul 2016 14:43:33 -0700 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain In-Reply-To: <20160706225138.6799c97d@bouzin.lan> References: <20160706014723.6065447c@bouzin.lan> <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> <20160706225138.6799c97d@bouzin.lan> Message-ID: On 7/6/16 1:51 PM, J?r?me wrote: > > But may I have a mailbox like test at domain1.tld and a list like > test at lists.domain1.tld ? > > Since the alias reads > > test: "|/var/lib/mailman/mail/mailman post test" > test-admin: "|/var/lib/mailman/mail/mailman admin test" > ... > > I assumed mailman would have everything called "test at ..." be directed > to mailman. The way Mailman-Postfix integration works the 'virtual-mailman' alias_maps will map 'test at lists.domain1.tld' to the local name 'test' and alias maps will deliver the local 'test' to mailman. If you have an actual local user 'test' as long as Postfix delivers to that user via the 'local' transport, it will honor the alias and deliver to Mailman. > Thinking twice, this file is used for local aliases, so it would only > conflict with system users/aliases, not virtual aliases. That is correct. If domain1.tld is a virtual domain (virtual mailbox domain or virtual alias domain), it depends what transport is ultimately used to deliver the mail to test at domain1.tld. If, for example, this is dovecot, it won't consult alias_maps and will deliver to the user's mailbox. > Or not conflict at all ? I'm not sure... > > Avoiding conflicts is the reason I'm using the 'lists' subdomain. > > > Back to the subject, I added hash:/var/lib/mailman/data/aliases to > alias_maps and I'm still getting the same error : > > (expanded from > ): user unknown > > (I did restart Postfix, even Mailman, I even restarted the whole > server.) > > Any known potential cause for this? > > I don't think there is more to the config than what I already sent. > > > I'm not sure how it all works. AFAIU, virtual-mailman makes sure that > > test at lists.domain1.tld -> test > > and then, aliases makes sure that > > test -> "|/var/lib/mailman/mail/mailman post test" > > It looks like the first step succeeds, but then postfix appends > domain1.tld to test before looking up in aliases. > > Could it be related to that feature that makes postfix append $myorigin > to unqualified recipient addresses. > > (http://www.postfix.org/BASIC_CONFIGURATION_README.html#myorigin) There is a possible fix for this. Set VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' in mm_cfg.py and rerun Mailman's bin/genaliases. You don't need to restart Mailman immediately, just before you create a new list, but do it anyway. This will change the virtual-mailman mappings to things like test at lists.domain1.tld test at localhost. > As a quick test, if I connect as local user and send a message using > > mail nobody > > here's what I get in the logs: > > postfix/pipe[2909]: 0EC5AC15D: to=, > orig_to=, relay=dovecot, delay=0.11, delays=0.04/0.01/0/0.07, > dsn=5.1.1, status=bounced (user unknown) > > This seems to indicate that the postfix configuration is wrong, > as /etc/aliases are also broken. Note 'relay=dovecot'. Dovecot does not consult aliases. If setting VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' doesn't solve the issue, please post all the Postfix log entries related to the failed delivery. I think it will work, but if not, you may have to resort to the method at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From thomas at ifi.uio.no Wed Jul 6 21:19:50 2016 From: thomas at ifi.uio.no (Thomas Gramstad) Date: Thu, 7 Jul 2016 03:19:50 +0200 (CEST) Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> Message-ID: On Wed, 6 Jul 2016, Jim Popovitch wrote: > On Wed, Jul 6, 2016 at 12:22 PM, Mark Sapiro wrote: >> On 7/6/16 8:07 AM, Jim Popovitch wrote: >>>> >>>>> On Jul 6, 2016, at 9:21 AM, Jim Popovitch wrote: >>>>> >>>>> I've been inspired by something I read somewhere else. >>>>> >>>>> I have long thought that mailing lists should be >>>>> configured to reject messages with a Subject of >>>>> "Re: [the subject format for the list's digest messages]". >>>>> Maybe a scan of the message content for a copy >>>>> of the digest prologue would be a good idea as well. >>>>> >>>>> and now I want to implement something like this. >> >> >> There is a custom handler at >> that holds messages for >> various reasons including digest subjects and quoting digest boiler plate. >> >> >>> Do people feel there is a need for a new Sender filter option "Process >>> Digest Replies" >>> (Accept|Hold|Reject|Discard) ? Definitely. I'd love to have that. >> This could be good for Mailman 3. I'm reluctant to do this in 2.1 >> because it really should be 'end of life'. > > I get that, but 2.1 is going to be around for at least several > more years considering LTS distros, etc. Those distros will > most certainly upgrade Mailman for fixes/improvements, whereas > probably not to do a major switch to mm3 (plus supported > dependencies, etc) There is also the issue of listadmin, the script for command line processing of list moderation requests. I'm not sure this script is being updated currently, and so probably does not work with Mailman 3(?). If so that is a show stopper for me, I'd never update to a Mailman version that can't be run via the command line. I have a lot of smaller mailing lists, and running them via web interface would be so time consuming that it would in practise be undoable. Thomas Gramstad From jerome at jolimont.fr Thu Jul 7 04:43:36 2016 From: jerome at jolimont.fr (=?UTF-8?Q?J=C3=A9r=C3=B4me?=) Date: Thu, 07 Jul 2016 10:43:36 +0200 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain In-Reply-To: References: <20160706014723.6065447c@bouzin.lan> <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> <20160706225138.6799c97d@bouzin.lan> Message-ID: <880c3dadbf72c956c7276c9263a45c3f@jolimont.fr> Thanks again, Mark, for the detailed explaination. Le 2016-07-06 23:43, Mark Sapiro a ?crit?: > On 7/6/16 1:51 PM, J?r?me wrote: > VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' This was the missing part. I did it and now it works. Should this be mentionned in the doc page ? https://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html I don't know how specific it is. >From a quick search, it only appears in a doc page which has an explicit "not recommended" label: https://wiki.list.org/DOC/Integrating%20Mailman%20with%20postfix -- J?r?me From livingsky at gmail.com Wed Jul 6 13:38:46 2016 From: livingsky at gmail.com (Bob Lydiate) Date: Wed, 6 Jul 2016 11:38:46 -0600 Subject: [Mailman-Users] Mailman installation does not work Message-ID: I am reinstalling Mailman after having to change servers. I am using Ubuntu 16.04, Apache, Postfix, Mailman. I have apache and postfix both working and serving mail and web. I have installed and re-installed Mailman a couple of times to try and get it working right and now have no idea what is creating the problem that stops it from working. I have several issues that I can identify, and I am sure there are several that I have missed. Problem 1 When I run 'check_perms -f' it tells me that the permissions on /var/lib/mailman/cron bad group (has:root, expected list) (fixing) this problem is repeated with 9 other scripts. When I check the actual directory '/var/lib/mailman' I find that these files are all links to '/usr/lib/*; where the correct group is set. When I try to access the web interface, I am asked if I want to open a file called 'admin' instead of opening a webpage called admin. when I run '/etc/init.d/mailman start' or the equivalent for postfix or apache, I get no errors. I did alter the config setup to have mydomain.ca rather than lists.mydomain.ca, but that is the only change I made to the config as it came through. I have checked the archives and have searched out the issues that I suspect, but have found nothing that worked to fix these issues. Bob From mark at msapiro.net Thu Jul 7 12:02:50 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Jul 2016 09:02:50 -0700 Subject: [Mailman-Users] Mailman installation does not work In-Reply-To: References: Message-ID: <1766996e-decb-54bf-bc01-070ab5ff4937@msapiro.net> On 7/6/16 10:38 AM, Bob Lydiate wrote: > > Problem 1 > When I run 'check_perms -f' it tells me that the permissions on > /var/lib/mailman/cron bad group (has:root, expected list) (fixing) > this problem is repeated with 9 other scripts. When I check the actual > directory '/var/lib/mailman' I find that these files are all links to > '/usr/lib/*; where the correct group is set. You can ignore the check_perms error. It comes about because the Debian (and hence Ubuntu) package patches check_perms to use os.lstat rather than os.stat and thus looks at the mode and group of the symlink instead of the target. The mode and group of the symlink are irrelevant and can't be changed anyway. > When I try to access the web interface, I am asked if I want to open a file > called 'admin' instead of opening a webpage called admin. This is an issue with your Apache config. See . > when I run '/etc/init.d/mailman start' or the equivalent for postfix or > apache, I get no errors. OK. > I did alter the config setup to have mydomain.ca rather than > lists.mydomain.ca, but that is the only change I made to the config as it > came through. What exactly did you change? > I have checked the archives and have searched out the issues that I > suspect, but have found nothing that worked to fix these issues. What exactly are your issues? What doesn't work? What do you do that produces a result different from what you expect, and what is the result? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 7 12:34:07 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Jul 2016 09:34:07 -0700 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain In-Reply-To: <880c3dadbf72c956c7276c9263a45c3f@jolimont.fr> References: <20160706014723.6065447c@bouzin.lan> <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> <20160706225138.6799c97d@bouzin.lan> <880c3dadbf72c956c7276c9263a45c3f@jolimont.fr> Message-ID: On 7/7/16 1:43 AM, J?r?me wrote: > > Le 2016-07-06 23:43, Mark Sapiro a ?crit : > >> VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' > > This was the missing part. I did it and now it works. > > Should this be mentionned in the doc page ? > > https://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html It is explained in Defaults.py ;) It probably should be mentioned on that page, and that page should probably be rewritten anyway, as it is more complicated than necessary. I'll work on it. Thanks for the feedback. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From livingsky at gmail.com Thu Jul 7 14:02:29 2016 From: livingsky at gmail.com (Bob) Date: Thu, 7 Jul 2016 12:02:29 -0600 Subject: [Mailman-Users] Mailman installation does not work In-Reply-To: <1766996e-decb-54bf-bc01-070ab5ff4937@msapiro.net> References: <1766996e-decb-54bf-bc01-070ab5ff4937@msapiro.net> Message-ID: <577E9935.4090702@gmail.com> Thanks for responding Mark. My replies to your comments are below. On 2016-07-07 10:02 AM, Mark Sapiro wrote: > On 7/6/16 10:38 AM, Bob Lydiate wrote: >> Problem 1 >> When I run 'check_perms -f' it tells me that the permissions on >> /var/lib/mailman/cron bad group (has:root, expected list) (fixing) >> this problem is repeated with 9 other scripts. When I check the actual >> directory '/var/lib/mailman' I find that these files are all links to >> '/usr/lib/*; where the correct group is set. > > You can ignore the check_perms error. It comes about because the Debian > (and hence Ubuntu) package patches check_perms to use os.lstat rather > than os.stat and thus looks at the mode and group of the symlink instead > of the target. The mode and group of the symlink are irrelevant and > can't be changed anyway. Thank you for pointing this out. I was hoping that this was the case. > >> When I try to access the web interface, I am asked if I want to open a file >> called 'admin' instead of opening a webpage called admin. > > This is an issue with your Apache config. See > . > I have done what this page says as far as I can tell and it still doesn't serve up a webpage. What I have in '/etc/apache2/sites-enabled/mailman.conf' is AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted Options FollowSymlinks AllowOverride None Require all granted AllowOverride None Require all granted >> when I run '/etc/init.d/mailman start' or the equivalent for postfix or >> apache, I get no errors. > > OK. > > >> I did alter the config setup to have mydomain.ca rather than >> lists.mydomain.ca, but that is the only change I made to the config as it >> came through. > > What exactly did you change? from /etc/mailman/mm_cfg.py DEFAULT_EMAIL_HOST = 'faithwalk.ca' DEFAULT_URL_HOST = 'faithwalk.ca' and from /etc/apache2/sites-enabled/mailman.conf ServerName faithwalk.ca DocumentRoot /var/www/ ErrorLog /var/log/apache2/lists-error.log CustomLog /var/log/apache2/lists-access.log combined Options FollowSymLinks AllowOverride None Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/ ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm ScriptAlias /create /usr/lib/cgi-bin/mailman/create ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo ScriptAlias /options /usr/lib/cgi-bin/mailman/options ScriptAlias /private /usr/lib/cgi-bin/mailman/private ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ > >> I have checked the archives and have searched out the issues that I >> suspect, but have found nothing that worked to fix these issues. > > What exactly are your issues? What doesn't work? What do you do that > produces a result different from what you expect, and what is the result? > The things that I am searching out are the things mentioned above plus mail not being delivered through the list. I am pretty focused on figuring out the web interface problem first as it was the first problem I noticed. I have figured out that mailman is working, I can create lists and add members through the command line, but the list mail is not getting delivered. The mail log says it was sent, but I do not receive it on any of the addresses I added to my testlist. From mark at msapiro.net Thu Jul 7 18:03:28 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Jul 2016 15:03:28 -0700 Subject: [Mailman-Users] Mailman installation does not work In-Reply-To: <577E9935.4090702@gmail.com> References: <1766996e-decb-54bf-bc01-070ab5ff4937@msapiro.net> <577E9935.4090702@gmail.com> Message-ID: <7046ca53-b13a-0645-78c4-c5d76db3b4ae@msapiro.net> On 7/7/16 11:02 AM, Bob wrote: > > On 2016-07-07 10:02 AM, Mark Sapiro wrote: >> On 7/6/16 10:38 AM, Bob Lydiate wrote: >> >>> When I try to access the web interface, I am asked if I want to open >>> a file >>> called 'admin' instead of opening a webpage called admin. >> >> This is an issue with your Apache config. See >> . >> > > I have done what this page says as far as I can tell and it still > doesn't serve up a webpage. What I have in > '/etc/apache2/sites-enabled/mailman.conf' is > > > AllowOverride None > Options ExecCGI > AddHandler cgi-script .cgi > Require all granted > > > Options FollowSymlinks > AllowOverride None > Require all granted > > > AllowOverride None > Require all granted > Plus more below... >> >>> I did alter the config setup to have mydomain.ca rather than >>> lists.mydomain.ca, but that is the only change I made to the config >>> as it >>> came through. >> >> What exactly did you change? > from /etc/mailman/mm_cfg.py > DEFAULT_EMAIL_HOST = 'faithwalk.ca' > DEFAULT_URL_HOST = 'faithwalk.ca' > > and from /etc/apache2/sites-enabled/mailman.conf > > ServerName faithwalk.ca > DocumentRoot /var/www/ > ErrorLog /var/log/apache2/lists-error.log > CustomLog /var/log/apache2/lists-access.log combined > > > Options FollowSymLinks > AllowOverride None > > > Alias /pipermail/ /var/lib/mailman/archives/public/ > Alias /images/mailman/ /usr/share/images/mailman/ > ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin > ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb > ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm > ScriptAlias /create /usr/lib/cgi-bin/mailman/create > ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml > ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo > ScriptAlias /options /usr/lib/cgi-bin/mailman/options > ScriptAlias /private /usr/lib/cgi-bin/mailman/private > ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist > ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster > ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe > ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ > Your Apache config looks OK. Have you enabled mod_cgi? > The things that I am searching out are the things mentioned above plus > mail not being delivered through the list. I am pretty focused on > figuring out the web interface problem first as it was the first problem > I noticed. I have figured out that mailman is working, I can create > lists and add members through the command line, but the list mail is not > getting delivered. The mail log says it was sent, but I do not receive > it on any of the addresses I added to my testlist. See . Also, when you say "The mail log says it was sent" do you mean you see entries in /var/log/mail.log saying the mail to a final recipient was successfully delivered to that recipient's MX. If so, the problem is between that MX and the final recipient's mailbox. If that's not what you mean, what is in the mail.log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From phirayam at fredhutch.org Thu Jul 7 18:58:59 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Thu, 7 Jul 2016 22:58:59 +0000 Subject: [Mailman-Users] Message discarded without reason logged in vette Message-ID: So, I found a 10 year old post where Mark Sapiro described some of the reasons why "Message discarded" with only a message id and no reason happens: Examples are when nothing is left after content filtering, a post from a moderated user when action is discard, a post from a non-member in discard_these_nonmembers, a post from a non-member with generic action discard, some cases of a text/html post when ARCHIVE_HTML_SANITIZER = 0 and a post matching a header_filter_rule with discard action. I was wondering if there was a more complete list someplace? Mostly because I had this happen to one of my users 3 weeks ago, and I think that I've managed to rule out everything that Mark wrote back then. Thanks, -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phirayam at fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease From mark at msapiro.net Thu Jul 7 20:51:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Jul 2016 17:51:40 -0700 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: References: Message-ID: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> On 7/7/16 3:58 PM, Hirayama, Pat wrote: > So, I found a 10 year old post where Mark Sapiro described some of the reasons why "Message discarded" with only a message id and no reason happens: > > Examples are when nothing is left after content filtering, a post from > a moderated user when action is discard, a post from a non-member in > discard_these_nonmembers, a post from a non-member with generic action > discard, some cases of a text/html post when ARCHIVE_HTML_SANITIZER = > 0 and a post matching a header_filter_rule with discard action. > > I was wondering if there was a more complete list someplace? Mostly because I had this happen to one of my users 3 weeks ago, and I think that I've managed to rule out everything that Mark wrote back then. If the message in the vette log is "Message discarded, msgid: <...>", that message is only produced in standard Mailman by IncomingRunner when a handler raises DiscardMessage. Again in standard Mailman, the only Handlers that do that are: MimeDel - content filtering removes the entire message and filter_action is other than Reject Moderate - a post is from a moderated member with member_moderation_action Discard - a post is from a non-member in discard_these_nonmembers or with generic_nonmember_action Discard Scrubber - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = 0 (not the default, and this only applies if scrub_nondigest is Yes) SpamDetect - when a message matches KNOWN_SPAMMERS - A post is From: a domain with DMARC p=reject (or maybe quarantine) and dmarc_moderation_action is Discard - a message matches header_filter_rules with Discard action or with Reject action and the message is to -owner This is the current complete list for standard GNU Mailman. It is essentially the same as in the old post with the addition of dmarc_moderation_action. If your Mailman is from a downstream package or has local mods, you can grep -r DiscardMessage /path/to/Mailman/Handlers to see if there are others -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From raj at mischievous.us Thu Jul 7 18:33:20 2016 From: raj at mischievous.us (Richard Johnson) Date: Thu, 7 Jul 2016 15:33:20 -0700 Subject: [Mailman-Users] How to actively read the list online? Message-ID: Hi! I'm hoping there's a quick answer to this. I looked but can't find it online. As of yesterday, I'm now running a mailing list for an interest group of about 50 people. I've run many other lists in the past, all using mailman, and never encountered the unique situation I'm seeing here. We moved the list of participants from a Yahoo Group. Some people were receiving individual messages and some were receiving digests. Those are fine. The people who are a problem are the ones who were *not* receiving any messages, but were instead reading the list online! They're used to seeing the entire list of messages on a web page and having it update automatically (I think). I haven't ever read a Yahoo Group list online, so I'm not sure. Is there any way to setup a web page which would automatically update to show the most recent messages in the archive? I have an archive setup and it receives a copy of the messages fairly quickly, but it doesn't update automatically and also anyone looking at it would need to update their URL at least every month, since the messages are organized by month. Anyone have something? Any help is much appreciated! /raj From mark at msapiro.net Fri Jul 8 11:50:36 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Jul 2016 08:50:36 -0700 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: References: Message-ID: On 7/7/16 3:33 PM, Richard Johnson wrote: > > Is there any way to setup a web page which would automatically update to show the most recent messages in the archive? I have an archive setup and it receives a copy of the messages fairly quickly, but it doesn't update automatically and also anyone looking at it would need to update their URL at least every month, since the messages are organized by month. It depends on whether the list's archives are public or not. If they are public, you might consider a third party archive service like mail-archive.com. See for an example that might fill your need, although I don't know if it refreshes for new posts. Otherwise, you could possibly create your own web page to serve your archive in the manner you desire. This might not be difficult for public archives as the archives themselves are all static files. For private archives, you would need an authentication scheme which would presumably need to talk to Mailman. I'm not aware of anyone having done this. The Mailman 3 HyperKitty archiver provides a different UI which may be good for you (see ), but I don't think it refreshes with new posts either. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From phirayam at fredhutch.org Fri Jul 8 12:00:34 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Fri, 8 Jul 2016 16:00:34 +0000 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> Message-ID: Thanks, Mark. WRT Content filtering -- if filter_content is set to NO, then nothing else in that section should apply, right? That is, even if there is stuff defined for pass_mime_types and filter_filename_extensions? Thanks, -p -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+phirayam=fredhutch.org at python.org] On Behalf Of Mark Sapiro Sent: Thursday, July 7, 2016 5:52 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/7/16 3:58 PM, Hirayama, Pat wrote: > So, I found a 10 year old post where Mark Sapiro described some of the reasons why "Message discarded" with only a message id and no reason happens: > > Examples are when nothing is left after content filtering, a post from > a moderated user when action is discard, a post from a non-member in > discard_these_nonmembers, a post from a non-member with generic action > discard, some cases of a text/html post when ARCHIVE_HTML_SANITIZER = > 0 and a post matching a header_filter_rule with discard action. > > I was wondering if there was a more complete list someplace? Mostly because I had this happen to one of my users 3 weeks ago, and I think that I've managed to rule out everything that Mark wrote back then. If the message in the vette log is "Message discarded, msgid: <...>", that message is only produced in standard Mailman by IncomingRunner when a handler raises DiscardMessage. Again in standard Mailman, the only Handlers that do that are: MimeDel - content filtering removes the entire message and filter_action is other than Reject Moderate - a post is from a moderated member with member_moderation_action Discard - a post is from a non-member in discard_these_nonmembers or with generic_nonmember_action Discard Scrubber - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = 0 (not the default, and this only applies if scrub_nondigest is Yes) SpamDetect - when a message matches KNOWN_SPAMMERS - A post is From: a domain with DMARC p=reject (or maybe quarantine) and dmarc_moderation_action is Discard - a message matches header_filter_rules with Discard action or with Reject action and the message is to -owner This is the current complete list for standard GNU Mailman. It is essentially the same as in the old post with the addition of dmarc_moderation_action. If your Mailman is from a downstream package or has local mods, you can grep -r DiscardMessage /path/to/Mailman/Handlers to see if there are others -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://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: https://mail.python.org/mailman/options/mailman-users/phirayam%40fredhutch.org From raj at mischievous.us Fri Jul 8 12:08:10 2016 From: raj at mischievous.us (Richard Johnson) Date: Fri, 8 Jul 2016 09:08:10 -0700 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: References: Message-ID: <3860B6BD-C9CC-448F-9B8C-3CBA5B44C66C@mischievous.us> Thanks for the reply and thanks for showing me a working link for HyperKitty. I saw mention of HyperKitty on the net but didn't see any example screens, so I wasn't sure if it would be worth the trouble of downloading/installing or not. It actually looks like the closest match to what I was looking for, but it's true that I don't know if it does automatic updates. I'll check into HyperKitty. Thanks! /raj > On Jul 8, 2016, at 8:50 AM, Mark Sapiro wrote: > > On 7/7/16 3:33 PM, Richard Johnson wrote: >> >> Is there any way to setup a web page which would automatically update to show the most recent messages in the archive? I have an archive setup and it receives a copy of the messages fairly quickly, but it doesn't update automatically and also anyone looking at it would need to update their URL at least every month, since the messages are organized by month. > > > It depends on whether the list's archives are public or not. If they are > public, you might consider a third party archive service like > mail-archive.com. See > for an example > that might fill your need, although I don't know if it refreshes for new > posts. > > Otherwise, you could possibly create your own web page to serve your > archive in the manner you desire. This might not be difficult for public > archives as the archives themselves are all static files. For private > archives, you would need an authentication scheme which would presumably > need to talk to Mailman. > > I'm not aware of anyone having done this. > > The Mailman 3 HyperKitty archiver provides a different UI which may be > good for you (see > ), > but I don't think it refreshes with new posts either. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://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: https://mail.python.org/mailman/options/mailman-users/raj%40mischievous.us From mark at msapiro.net Fri Jul 8 12:27:27 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Jul 2016 09:27:27 -0700 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> Message-ID: <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> On 7/8/16 9:00 AM, Hirayama, Pat wrote: > > WRT Content filtering -- if filter_content is set to NO, then nothing else in that section should apply, right? That is, even if there is stuff defined for pass_mime_types and filter_filename_extensions? That's correct. Note that what I wrote below applies only to the exact log entry "Message discarded, msgid: <...>". It seems that's the one you've seen, but there can be other messages such as "No command, message discarded, msgid: <...>" which is logged for messages sent to the -request address with no command or to -confirm with incorrect format. > > -----Original Message----- ... > If the message in the vette log is "Message discarded, msgid: <...>", > that message is only produced in standard Mailman by IncomingRunner when > a handler raises DiscardMessage. Again in standard Mailman, the only > Handlers that do that are: > > MimeDel > - content filtering removes the entire message and filter_action is > other than Reject > > Moderate > - a post is from a moderated member with member_moderation_action Discard > - a post is from a non-member in discard_these_nonmembers or with > generic_nonmember_action Discard > > Scrubber > - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = > 0 (not the default, and this only applies if scrub_nondigest is Yes) > > SpamDetect > - when a message matches KNOWN_SPAMMERS > - A post is From: a domain with DMARC p=reject (or maybe quarantine) > and dmarc_moderation_action is Discard > - a message matches header_filter_rules with Discard action or with > Reject action and the message is to -owner -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From phirayam at fredhutch.org Fri Jul 8 12:33:45 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Fri, 8 Jul 2016 16:33:45 +0000 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> Message-ID: <46712_1467995634_577FD5F2_46712_4662_1_AE5F7147890F3544BFCDB1594A4329C9E6C471D0@adama.fhcrc.org> Hi Mark, This is the message (from just a few minutes ago, in fact): Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> I am stumped. The sender is a non-moderated member. She is in fact, listed as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does not appear to be set. dmarc_moderation_action is set to ACCEPT. header_filter_rules = []. As near as I can tell, everywhere in the admin interface where one can select "Discard" is not checked. -p -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, July 8, 2016 9:27 AM To: Hirayama, Pat ; mailman-users at python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/8/16 9:00 AM, Hirayama, Pat wrote: > > WRT Content filtering -- if filter_content is set to NO, then nothing else in that section should apply, right? That is, even if there is stuff defined for pass_mime_types and filter_filename_extensions? That's correct. Note that what I wrote below applies only to the exact log entry "Message discarded, msgid: <...>". It seems that's the one you've seen, but there can be other messages such as "No command, message discarded, msgid: <...>" which is logged for messages sent to the -request address with no command or to -confirm with incorrect format. > > -----Original Message----- ... > If the message in the vette log is "Message discarded, msgid: <...>", > that message is only produced in standard Mailman by IncomingRunner when > a handler raises DiscardMessage. Again in standard Mailman, the only > Handlers that do that are: > > MimeDel > - content filtering removes the entire message and filter_action is > other than Reject > > Moderate > - a post is from a moderated member with member_moderation_action Discard > - a post is from a non-member in discard_these_nonmembers or with > generic_nonmember_action Discard > > Scrubber > - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = > 0 (not the default, and this only applies if scrub_nondigest is Yes) > > SpamDetect > - when a message matches KNOWN_SPAMMERS > - A post is From: a domain with DMARC p=reject (or maybe quarantine) > and dmarc_moderation_action is Discard > - a message matches header_filter_rules with Discard action or with > Reject action and the message is to -owner -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 8 12:54:45 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Jul 2016 09:54:45 -0700 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> Message-ID: <8ea0ddc9-a3c9-fa0c-1c81-ecc4dfa89c7e@msapiro.net> On 7/8/16 9:33 AM, Hirayama, Pat wrote: > > This is the message (from just a few minutes ago, in fact): > > Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> > > I am stumped. The sender is a non-moderated member. She is in fact, listed as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does not appear to be set. dmarc_moderation_action is set to ACCEPT. header_filter_rules = []. The fact that she is listed as a moderator is irrelevant to this. Just to be sure, do 'ps -fww 3892' and verify that the process is IncomingRunner. Also note that starting with Mailman 2.1.19, the log message includes the name of the handler that raised the discard. See and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lucio at lambrate.inaf.it Fri Jul 8 12:44:47 2016 From: lucio at lambrate.inaf.it (Lucio Chiappetti) Date: Fri, 8 Jul 2016 18:44:47 +0200 (CEST) Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: References: Message-ID: On Fri, 8 Jul 2016, Mark Sapiro wrote: > On 7/7/16 3:33 PM, Richard Johnson wrote: >> Is there any way to setup a web page which would automatically update >> to show the most recent messages in the archive? > It depends on whether the list's archives are public or not. [...] For > private archives, you would need an authentication scheme which would > presumably need to talk to Mailman. I have been participating in discussion lists both with public and private archives (as well as in usenet newsgroups :-)) and managing some of them locally or remotely *using the mailman native archiving* and I do not see any difference or difficulties between the two. Usually the archive (all those which I have seen are by month, and can be sorted by thread, date or author) is updated as soon as I receive a copy of a post. It is true that in case of private archives the users will have to autenticate on the mailman site. I.e. they have to be mailing list members. So your problem is that some former users do not want to receive a mail but JUST access the archives ? They could be members of the mailing list set to "NO MAIL", couldn't they ? (I have a small, 25 or so members list, where 22 are full (voting) members, and 3 are observers (former members). All receive normal messages, but when I issue a call-for-votes I set the 3 observers to NO MAIL, send the message, then reset them to normal mail reception. This simply prevents the observers to send me back votes which will not be counted anyhow.) -- ------------------------------------------------------------------------ Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ Do not like Firefox >=29 ? Get Pale Moon ! http://www.palemoon.org From phirayam at fredhutch.org Fri Jul 8 13:37:30 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Fri, 8 Jul 2016 17:37:30 +0000 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: <8ea0ddc9-a3c9-fa0c-1c81-ecc4dfa89c7e@msapiro.net> References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> <8ea0ddc9-a3c9-fa0c-1c81-ecc4dfa89c7e@msapiro.net> Message-ID: Hi Mark, 3892 is the IncomingRunner process. And I'm still running 2.1.9, since that is what was provided with CentOS 5.x. I will have to upgrade that box soon to CentOS 7.x -- which comes with 2.1.15. -p -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, July 8, 2016 9:55 AM To: Hirayama, Pat ; mailman-users at python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/8/16 9:33 AM, Hirayama, Pat wrote: > > This is the message (from just a few minutes ago, in fact): > > Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> > > I am stumped. The sender is a non-moderated member. She is in fact, listed as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does not appear to be set. dmarc_moderation_action is set to ACCEPT. header_filter_rules = []. The fact that she is listed as a moderator is irrelevant to this. Just to be sure, do 'ps -fww 3892' and verify that the process is IncomingRunner. Also note that starting with Mailman 2.1.19, the log message includes the name of the handler that raised the discard. See and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 8 14:33:19 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Jul 2016 11:33:19 -0700 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> <8ea0ddc9-a3c9-fa0c-1c81-ecc4dfa89c7e@msapiro.net> Message-ID: On 7/8/16 10:37 AM, Hirayama, Pat wrote: > Hi Mark, > > 3892 is the IncomingRunner process. > > And I'm still running 2.1.9, since that is what was provided with CentOS 5.x. I will have to upgrade that box soon to CentOS 7.x -- which comes with 2.1.15. Do you have an example message? If not, have her Cc: you on the next post. I might be able to see something in the headers of the message. Also, you could patch IncomingRunner as indicated at (and restart Mailman) to get the handler name. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mneedham at hdfgroup.org Fri Jul 8 13:11:39 2016 From: mneedham at hdfgroup.org (Matthew Needham) Date: Fri, 8 Jul 2016 17:11:39 +0000 Subject: [Mailman-Users] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc Message-ID: Is there a succinct way to list "auxiliary" addresses that are configured in a list? By "auxiliary" I'm referring to addresses other than member, owner, or moderator, since those are easy to find with list_owners and find_members. I'm trying to practice better list hygiene, and remove all relevant address when someone leaves the organization. The best way I've currently found is use a foreach loop to grab each list's config.pck and run dumpdb against it. I then filter out the uninteresting addresses and manually scan the results for relevant addresses. I can't simply grep the output for relevant addresses, because a subscriber john.doe at domain.com may be allowed (or disallowed) to post from jd123 at free-email.com. I don't mind the manual scanning, but parsing the output if dumped is time consuming. I'm guessing there's a way to grep for the relevant settings and all relevant following lines, but my regex skills have not been up to the task. I took a look at https://www.msapiro.net/scripts/non_members, but it appears to require that I know the addresses in advance, and not allow me to discover the relevant addresses. It also doesn't support ban_list, which is admittedly a rare occurrence for me, but I don't know if there are other unincluded settings I should be considering. I suppose this raises a question of other possible list hygiene best-practices. Besides removing subscriptions and removing/reassigning administrator or moderator responsibilities, when else should I be doing to clean up when someone leaves? Thanks! -- Matthew Needham mneedham at hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 From mark at msapiro.net Fri Jul 8 18:39:34 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Jul 2016 15:39:34 -0700 Subject: [Mailman-Users] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc In-Reply-To: References: Message-ID: <7e45a6a5-b5eb-3860-2880-5d4d99f905da@msapiro.net> On 7/8/16 10:11 AM, Matthew Needham wrote: > Is there a succinct way to list "auxiliary" addresses that are configured in a list? By "auxiliary" I'm referring to addresses other than member, owner, or moderator, since those are easy to find with list_owners and find_members. Since it was trivial to do, I just created . Try it. Note that the output is a bit cleaner if you redirect stderr from the withlist command to /dev/null. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From phirayam at fredhutch.org Fri Jul 8 19:32:41 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Fri, 8 Jul 2016 23:32:41 +0000 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> <8ea0ddc9-a3c9-fa0c-1c81-ecc4dfa89c7e@msapiro.net> Message-ID: All, User was reusing an old message that was previously sent to the list, and then using Outlook's 'Send Again' feature, which caused the message to contain headers that mailman placed into the original message. When the IncomingRunner process saw the message come through 'again', it discarded the message. Thanks to Mark Sapiro (mark_at_msapiro.net) for catching that those headers were there when they shouldn't have been! -p -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, July 8, 2016 11:33 AM To: Hirayama, Pat ; mailman-users at python.org Subject: Re: [Mailman-Users] Message discarded without reason logged in vette On 7/8/16 10:37 AM, Hirayama, Pat wrote: > Hi Mark, > > 3892 is the IncomingRunner process. > > And I'm still running 2.1.9, since that is what was provided with CentOS 5.x. I will have to upgrade that box soon to CentOS 7.x -- which comes with 2.1.15. Do you have an example message? If not, have her Cc: you on the next post. I might be able to see something in the headers of the message. Also, you could patch IncomingRunner as indicated at (and restart Mailman) to get the handler name. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 8 21:32:37 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Jul 2016 18:32:37 -0700 Subject: [Mailman-Users] Message discarded without reason logged in vette In-Reply-To: References: <7cb08640-21ba-00fd-6424-d72f1d203df3@msapiro.net> <46712_1467993635_577FCE23_46712_3876_1_AE5F7147890F3544BFCDB1594A4329C9E6C470D8@adama.fhcrc.org> <8cc6ec8c-1dcc-b490-3172-99c0e8da709c@msapiro.net> <8ea0ddc9-a3c9-fa0c-1c81-ecc4dfa89c7e@msapiro.net> Message-ID: On 7/8/16 4:32 PM, Hirayama, Pat wrote: > > User was reusing an old message that was previously sent to the list, and then using Outlook's 'Send Again' feature, which caused the message to contain headers that mailman placed into the original message. When the IncomingRunner process saw the message come through 'again', it discarded the message. The offending header was X-BeenThere: with the list name. This causes the Approve handler to raise LoopError which is a subclass of DiscardMessage to discard the message. In compiling the original list of reasons for this discard, I looked for subclasses of DiscardMessage, but I missed this one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From manuel at escapade.ch Sat Jul 9 04:24:28 2016 From: manuel at escapade.ch (Manuel Goepfert) Date: Sat, 9 Jul 2016 10:24:28 +0200 Subject: [Mailman-Users] mailman and yahoo Message-ID: <4E64AE9E-0034-46DA-9BCD-7331C4FAF89B@escapade.ch> Hi All, I?m facing since a few weeks if not even more some issue when a registered user using yahoo.com email address sends an email to one of the list that mailman manages. As the list is configured to send emails on behalf of the user to the members of the list, this triggers some anti spam mecanism that puts the message in the spam folders of the different recipients even worth, the email is rejected by some mail servers. The consequence is that the email addresses get at the end removed from the list because of bounces as the origin email address @yahoo.com is not legitimately sent from a yahoo email server. Looking at some documentation I found out that this was a known problem and that it was addressed in on e of the mailman version. So I upgraded to 2.1.18 that included that fix but I?m still facing this problem. Do you guys have the same issue and if yes are you able to mitigate it in any way ? I do have spf,dkim and dmark in place for the domain used to send emails. Thanks for your feedback. Kind regards, Manu From mark at msapiro.net Sat Jul 9 11:41:04 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 9 Jul 2016 08:41:04 -0700 Subject: [Mailman-Users] mailman and yahoo In-Reply-To: <4E64AE9E-0034-46DA-9BCD-7331C4FAF89B@escapade.ch> References: <4E64AE9E-0034-46DA-9BCD-7331C4FAF89B@escapade.ch> Message-ID: <19858fcf-6b4d-25cc-3823-e925d9a13608@msapiro.net> On 7/9/16 1:24 AM, Manuel Goepfert wrote: > > Looking at some documentation I found out that this was a known problem and that it was addressed in on e of the mailman version. So I upgraded to 2.1.18 that included that fix but I?m still facing this problem. > > Do you guys have the same issue and if yes are you able to mitigate it in any way ? Now that you have upgraded, you need to set the list's Privacy options... -> Sender filters -> dmarc_moderation_action to Munge From or Wrap Message. Wrap Message is better from a standards compliant point of view, but tends to have issues with some MUAs, particularly on mobile devices, so Munge From is often the better choice. If you have done this and are still having issues with mail From: a yahoo.com user being bounce by recipient ISPs, are the messages being munged or wrapped so that these messages as sent from the list are From: user name via list name list at example.com? If not, something is wrong. Do you see messages like 'DNS lookup for dmarc_moderation_action for list list_name not available' or 'DNSException: Unable to query DMARC policy for user at yahoo.com (_dmarc.yahoo.com) ...' in Mailman's error log? Do you see 'DMARC lookup ...' messages in Mailman's vette log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From futatuki at poem.co.jp Fri Jul 8 21:04:52 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI) Date: Sat, 9 Jul 2016 10:04:52 +0900 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> Message-ID: <57804DB4.8030906@poem.co.jp> Hi, On 07/07/16 04:41, Mark Sapiro wrote: > That should be > > ^Subject:.*[list of all Chinese characters here] > > except that if your list's preferred language is English and you haven't > changed Mailman's character set for English from ASCII to UTF-8, the > text you are matching against won't contain any Chinese characters > because the decoded headers are converted to the character set of the > list's preferred language and all the Chinese characters will be > converted to '?'. > > You might try something like > > ^Subject:.*\?{4,} > > This will match any subject that contains 4 or more non-ascii characters > in a row. Unfortunately, it will also match > > Subject: WTF is happening here???? > > but you could try some number other than 4 but greater than 1 How about using 'backslashreplace' instead of 'replace' to encode to list's preferred language in Mailman/Handlers/SpamDetect.py ? Then, desirable pattern in this case seems to be ~Subject.*(\\u[0-9a-f]{4}){4} It also matches strings like 'What does the string "\\u6709\\u9650\\u516c\\u53f8" mean?', though. === modified file 'Mailman/Handlers/SpamDetect.py' --- Mailman/Handlers/SpamDetect.py 2016-01-18 23:56:58 +0000 +++ Mailman/Handlers/SpamDetect.py 2016-07-09 00:47:33 +0000 @@ -86,7 +86,7 @@ # unicode it as iso-8859-1 which may result in a garbled # mess, but we have to do something. uvalue += unicode(frag, 'iso-8859-1', 'replace') - headers += '%s: %s\n' % (h, uvalue.encode(cset, 'replace')) + headers += '%s: %s\n' % (h, uvalue.encode(cset, 'backslashreplace')) return headers -- Yasuhito FUTATSUKI From futatuki at poem.co.jp Sat Jul 9 09:07:48 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI) Date: Sat, 9 Jul 2016 22:07:48 +0900 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <57804DB4.8030906@poem.co.jp> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> Message-ID: <5780F724.8080905@poem.co.jp> On 07/09/16 10:04, I wrote: > How about using 'backslashreplace' instead of 'replace' to encode to > list's preferred language in Mailman/Handlers/SpamDetect.py ? > > Then, desirable pattern in this case seems to be > > ~Subject.*(\\u[0-9a-f]{4}){4} ^Subject:.*(\\u[0-9a-f]{4,5}){4} (CJK Unified Ideographs Extension uses code point scope >= u+20000) Of course, you can specify code point scope more pricisely, not to match other than Chinese characters. -- Yasuhito FUTATSUKI From manuel at escapade.ch Sat Jul 9 12:08:16 2016 From: manuel at escapade.ch (Manuel Goepfert) Date: Sat, 9 Jul 2016 18:08:16 +0200 Subject: [Mailman-Users] mailman and yahoo In-Reply-To: <19858fcf-6b4d-25cc-3823-e925d9a13608@msapiro.net> References: <4E64AE9E-0034-46DA-9BCD-7331C4FAF89B@escapade.ch> <19858fcf-6b4d-25cc-3823-e925d9a13608@msapiro.net> Message-ID: <4570209B-5FEA-4395-BD93-017D91828A5D@escapade.ch> > Le 9 juil. 2016 ? 17:41, Mark Sapiro a ?crit : > > On 7/9/16 1:24 AM, Manuel Goepfert wrote: >> >> Looking at some documentation I found out that this was a known problem and that it was addressed in on e of the mailman version. So I upgraded to 2.1.18 that included that fix but I?m still facing this problem. >> >> Do you guys have the same issue and if yes are you able to mitigate it in any way ? > > > Now that you have upgraded, you need to set the list's Privacy > options... -> Sender filters -> dmarc_moderation_action to Munge From or > Wrap Message. > > Wrap Message is better from a standards compliant point of view, but > tends to have issues with some MUAs, particularly on mobile devices, so > Munge From is often the better choice. > Thanks Mark, I have set that parameter to ? Munge From ? and will report back on the next user sending an email from a Yahoo account Manu From mark at msapiro.net Sat Jul 9 12:14:18 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 9 Jul 2016 09:14:18 -0700 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <57804DB4.8030906@poem.co.jp> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> Message-ID: On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: > > How about using 'backslashreplace' instead of 'replace' to encode to > list's preferred language in Mailman/Handlers/SpamDetect.py ? That's an interesting idea. I'll look at doing that for the next release. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mneedham at hdfgroup.org Mon Jul 11 11:35:17 2016 From: mneedham at hdfgroup.org (Matthew Needham) Date: Mon, 11 Jul 2016 15:35:17 +0000 Subject: [Mailman-Users] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc In-Reply-To: <7e45a6a5-b5eb-3860-2880-5d4d99f905da@msapiro.net> References: <7e45a6a5-b5eb-3860-2880-5d4d99f905da@msapiro.net> Message-ID: <86022A3A-500B-4E28-A11D-53BD19945A25@hdfgroup.org> Mark, > On Jul 8, 2016, at 17:39 PM, Mark Sapiro wrote: > > On 7/8/16 10:11 AM, Matthew Needham wrote: >> Is there a succinct way to list "auxiliary" addresses that are configured in a list? By "auxiliary" I'm referring to addresses other than member, owner, or moderator, since those are easy to find with list_owners and find_members. > > Since it was trivial to do, I just created > . Try it. Thanks! However, I'm seeing "ValueError: zero length field name in format" whether I run it for all lists or one: [root at lw4 mailman]# ./bin/withlist -a -r list_etc Importing list_etc... Running list_etc.list_etc()... Loading list hdf5lib_lists.hdfgroup.org (unlocked) Traceback (most recent call last): File "./bin/withlist", line 299, in main() File "./bin/withlist", line 274, in main r = [do_list(listname, args, func) for listname in Utils.list_names()] File "./bin/withlist", line 202, in do_list return func(m, *args) File "/usr/local/cpanel/3rdparty/mailman/bin/list_etc.py", line 29, in list_etc print('List:{}'.format(mlist.real_name)) ValueError: zero length field name in format Finalizing [root at lw4 mailman]# ./bin/withlist -r list_etc hdf-forum_lists.hdfgroup.org Importing list_etc... Running list_etc.list_etc()... Loading list hdf-forum_lists.hdfgroup.org (unlocked) Traceback (most recent call last): File "./bin/withlist", line 299, in main() File "./bin/withlist", line 277, in main r = do_list(listname, args, func) File "./bin/withlist", line 202, in do_list return func(m, *args) File "/usr/local/cpanel/3rdparty/mailman/bin/list_etc.py", line 29, in list_etc print('List:{}'.format(mlist.real_name)) ValueError: zero length field name in format Finalizing Have I missed something? Thanks again. -- Matthew Needham mneedham at hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 From mark at msapiro.net Mon Jul 11 15:22:47 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2016 12:22:47 -0700 Subject: [Mailman-Users] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc In-Reply-To: <86022A3A-500B-4E28-A11D-53BD19945A25@hdfgroup.org> References: <7e45a6a5-b5eb-3860-2880-5d4d99f905da@msapiro.net> <86022A3A-500B-4E28-A11D-53BD19945A25@hdfgroup.org> Message-ID: <5783F207.7020800@msapiro.net> On 07/11/2016 08:35 AM, Matthew Needham wrote: > > Thanks! However, I'm seeing "ValueError: zero length field name in format" whether I run it for all lists or one: > > [root at lw4 mailman]# ./bin/withlist -a -r list_etc > Importing list_etc... > Running list_etc.list_etc()... > Loading list hdf5lib_lists.hdfgroup.org (unlocked) > Traceback (most recent call last): > File "./bin/withlist", line 299, in > main() > File "./bin/withlist", line 274, in main > r = [do_list(listname, args, func) for listname in Utils.list_names()] > File "./bin/withlist", line 202, in do_list > return func(m, *args) > File "/usr/local/cpanel/3rdparty/mailman/bin/list_etc.py", line 29, in list_etc > print('List:{}'.format(mlist.real_name)) > ValueError: zero length field name in format > Finalizing The issue is this "'List:{}'.format(mlist.real_name)" requires Python 2.7. With Python 2.6 it needs to be 'List:{0}'.format(mlist.real_name). For older versions, there is no format string method, so string interpolation as in 'List:%s' % mlist.real_name needs to be used. I have updated the scripts at and the mirror at to work with older Python versions. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mneedham at hdfgroup.org Mon Jul 11 17:37:29 2016 From: mneedham at hdfgroup.org (Matthew Needham) Date: Mon, 11 Jul 2016 21:37:29 +0000 Subject: [Mailman-Users] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc In-Reply-To: <5783F207.7020800@msapiro.net> References: <7e45a6a5-b5eb-3860-2880-5d4d99f905da@msapiro.net> <86022A3A-500B-4E28-A11D-53BD19945A25@hdfgroup.org> <5783F207.7020800@msapiro.net> Message-ID: <9C0EFDCF-5D9A-475E-B9D5-04FE26E7B035@hdfgroup.org> Thanks, Mark. That works perfectly. -- Matthew Needham mneedham at hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 From mark at msapiro.net Mon Jul 11 23:51:28 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2016 20:51:28 -0700 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> Message-ID: <57846940.1080109@msapiro.net> On 07/09/2016 09:14 AM, Mark Sapiro wrote: > On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: >> >> How about using 'backslashreplace' instead of 'replace' to encode to >> list's preferred language in Mailman/Handlers/SpamDetect.py ? > > > That's an interesting idea. I'll look at doing that for the next release. I've done this. See . I hijacked an old bug/patch at to pin this to. Much of that patch had already been implemented and I didn't do the Unicode normalization part which I still may do, although I have concerns about existing lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jul 12 00:49:14 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2016 21:49:14 -0700 Subject: [Mailman-Users] Mailman 2 + Postfix + virtual domains + lists subdomain In-Reply-To: References: <20160706014723.6065447c@bouzin.lan> <6b509fa7-f4b6-2f41-b07e-f755f74b66be@msapiro.net> <20160706225138.6799c97d@bouzin.lan> <880c3dadbf72c956c7276c9263a45c3f@jolimont.fr> Message-ID: <578476CA.7080505@msapiro.net> On 07/07/2016 09:34 AM, Mark Sapiro wrote: > On 7/7/16 1:43 AM, J?r?me wrote: >> >> Le 2016-07-06 23:43, Mark Sapiro a ?crit : >> >>> VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' >> >> This was the missing part. I did it and now it works. >> >> Should this be mentionned in the doc page ? >> >> https://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html I have added info about VIRTUAL_MAILMAN_LOCAL_DOMAIN to the manual section at and also clarified a bit of the rest of that page and added to the Note at to emphasize that those steps are needed even with virtual domains. All the online mirrors have been updated. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Tue Jul 12 03:03:35 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 12 Jul 2016 16:03:35 +0900 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> Message-ID: <22404.38471.848834.276379@turnbull.sk.tsukuba.ac.jp> Mark Sapiro writes: > On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: > > > > How about using 'backslashreplace' instead of 'replace' to encode to > > list's preferred language in Mailman/Handlers/SpamDetect.py ? I see you've already done this, but ... I would consider xmlrefreplace as well. xmlrefs are something most people (users/moderators) have seen, backslash they're not going to recognize unless they're programmers. At an earlier stage, you could also just do a trial re-encoding with the list preferred codec, set errors = 'strict', catch the Exception, and re-raise as a Hold (or Discard, according to per-list policy). (Then discard the output.) I would prefer this solution, I think, as creating regexps turns out to be an issue for many list owners. People would have to learn not to use emoji in headers, of course, or suffer moderation delays or even discards. To the extent that this is only for the moderation interface, you could also use UTF-8 for the UI. Then the moderator would be able to see the emoji, rather than the owner having to bake in such knowledge in the regexps. FWIW, YMMV, etc From stephen at xemacs.org Tue Jul 12 03:04:48 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 12 Jul 2016 16:04:48 +0900 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> Message-ID: <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> Thomas Gramstad writes: > There is also the issue of listadmin, the script for command line > processing of list moderation requests. I'm not sure this script > is being updated currently, and so probably does not work with > Mailman 3(?). I don't know if it's been integrated yet, but mailmanclient has a nice command interpreter that a GSoC student built for us. Even if your particular use case isn't supported yet, it will be easy to do so. I think you'll also find Postorius much more efficient than the current web interface. That may not be enough since you say managing moderation with the current interface is out of the question, but since moderation is an activity that needs human input, and UI changes (ie, use of command line) were enough to make it feasible, Postorius is something you should look at before deciding to stay with a product after end-of-line. Steve From stephen at xemacs.org Tue Jul 12 03:09:31 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 12 Jul 2016 16:09:31 +0900 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: References: Message-ID: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> Lucio Chiappetti writes: > So your problem is that some former users do not want to receive a mail > but JUST access the archives ? No. > They could be members of the mailing list > set to "NO MAIL", couldn't they ? Yes, they will be set up as "no mail". The problem is that a typical web forum these days is not a static page, it's a web app that is self-refreshing. So as a forumn user, you have a window or tab opened on the forum, you go to bed, and in the morning the page is 11 posts longer than when you left. Pipermail doesn't do that for you since it serves static pages. I'm not sure how easy it would be to have HyperKitty (Mailman 3's bundled archiver) do it, but I don't think it does now -- historically our use case is to provide URLs for people to refer to later. Yes, it's very easy to refresh a page (just one click or hotkey). The problem is that these users are not going to *remember* to do that because that "forum" will be the odd one for them. You may not think that's important, but I imagine the OP does. I'm not going to try to change your mind (I'm pretty much a BOFH on several of my mailing lists, sometimes that's the right way to go), but we're here on Mailman-Users to help him get the effect he wants. We don't want to tell him he "should" be willing to ask his users to change their habits. Steve From lucio at lambrate.inaf.it Tue Jul 12 04:26:42 2016 From: lucio at lambrate.inaf.it (Lucio Chiappetti) Date: Tue, 12 Jul 2016 10:26:42 +0200 (CEST) Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> References: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> Message-ID: On Tue, 12 Jul 2016, Stephen J. Turnbull wrote: > The problem is that a typical web forum these days is not a static page, > it's a web app that is self-refreshing. So as a forumn user, you have a > window or tab opened on the forum, you go to bed, and in the morning the > page is 11 posts longer than when you left. I see. Not sure how "typical" such behaviour is. Personally (coming from Usenet, and used to read Usenet forums, i.e. newsgroups, via a MAIL client) I sort-of hate forums, or at least the "maze of little forums all different". I can stand only PhpBB operated forums, and these are NOT auto-refreshing (or at least they aren't in the way I use them ... I do keep the forum permanently logged on, but I press a "new posts" button to refresh the page when I WANT to see if there are new messages ... since threads are archived in reverse chronological order, most recent first, I have to take note of the time of the most recent message before clicking to see whether there is anything new or not after clicked. In my opinion a forum is little more than a chat, and I do not care about it being archived forever (although de facto PhpBB forums do it, Usenet feeds expired after a while), while a mailing list archive is something for serious work. In this case a reference to a PRECISE url for that message on that date of that month is mandatory. Anyhow, getting a self-refreshing html page is just a matter of adding a tag to the Not sure if there is an easy provision to customize the mailman archive pages with such a tag -- ------------------------------------------------------------------------ Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ Do not like Firefox >=29 ? Get Pale Moon ! http://www.palemoon.org From jdd at dodin.org Tue Jul 12 04:28:40 2016 From: jdd at dodin.org (jdd) Date: Tue, 12 Jul 2016 10:28:40 +0200 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> References: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> Message-ID: <86894281-cc73-b231-9e06-4552730934cc@dodin.org> Le 12/07/2016 ? 09:09, Stephen J. Turnbull a ?crit : > The problem is that a typical web forum these days is not a static > page, it's a web app that is self-refreshing. So as a forumn user, (...) being in vacantion, I didn't follow the hole thread, forgive me :-( but couldn't gmane be a solution? http://gmane.org/ jdd From jimpop at gmail.com Tue Jul 12 10:24:31 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Tue, 12 Jul 2016 10:24:31 -0400 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> Message-ID: On Tue, Jul 12, 2016 at 3:04 AM, Stephen J. Turnbull wrote: > is something you should look at before deciding to stay with a product > after end-of-line. Doesn't this list traffic and interest prove that mm2x is nowhere near end of life? I mean the interest is here, should that be actively discouraged? -Jim P. From ginesgb at gmail.com Tue Jul 12 07:10:38 2016 From: ginesgb at gmail.com (Gines Granados Bayona) Date: Tue, 12 Jul 2016 13:10:38 +0200 Subject: [Mailman-Users] Error unknown virtual host mailman Message-ID: Hello everyone, I'm new in mailman and just made an installation of zero mailman, with potsfix on centos 6. I have an error when trying to create a new list in which shows me: Error: Unknown virtual host... *** *** *** *** I do not know what parameter settings I could make wrong, or should change and though I've read several forums, I see that the fix are settings are different , do We can indicate that parameter must change? Greetings and thank you -- Este mensaje se dirige exclusivamente a su destinatario. Puede contener informaci?n confidencial sometida a secreto profesional o cuya divulgaci?n este prohibida, en virtud de la legislaci?n vigente. No esta permitida su divulgaci?n, copia o distribuci?n a terceros sin la autorizaci?n previa y por escrito del remitente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. This e-mail is intended exclusively for the individual or entity to which it is addressed and may contain confidential or legally privileged information, which may not be disclosed under current legislation. Any form of disclosure, copying or distribution of this e-mail is strictly prohibited, save with written authorisation . If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. From stephen at xemacs.org Tue Jul 12 13:14:18 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 13 Jul 2016 02:14:18 +0900 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: <86894281-cc73-b231-9e06-4552730934cc@dodin.org> References: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> <86894281-cc73-b231-9e06-4552730934cc@dodin.org> Message-ID: <22405.9578.83150.64607@turnbull.sk.tsukuba.ac.jp> jdd writes: > but couldn't gmane be a solution? > > http://gmane.org/ It would be better than pipermail, though, I think I prefer HyperKitty to GMane. But for forum users, I don't think it would be close enough. Specifically, I don't think GMane serves whole threads as a single page; you have to click on next post. I don't know whether there's an autorefresh on the header, either. It won't be a lot like the experience with many forums (eg, Discourse). From stephen at xemacs.org Tue Jul 12 13:17:32 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 13 Jul 2016 02:17:32 +0900 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: References: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> Message-ID: <22405.9772.835666.532808@turnbull.sk.tsukuba.ac.jp> Lucio Chiappetti writes: > Personally (coming from Usenet, and used to read Usenet forums, i.e. > newsgroups, via a MAIL client) I sort-of hate forums, Then you're definitely welcome here! :-) > Anyhow, getting a self-refreshing html page is just a matter of adding a > tag to the Sure, but if the page itself is static (as in a conventional mailing list archive), that won't help. The archive host has to be prepared to feed *new* pages, not refresh the old one, when accessed. From mark at msapiro.net Tue Jul 12 13:25:32 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2016 10:25:32 -0700 Subject: [Mailman-Users] Error unknown virtual host mailman In-Reply-To: References: Message-ID: <5785280C.3070207@msapiro.net> On 07/12/2016 04:10 AM, Gines Granados Bayona wrote: > Hello everyone, I'm new in mailman and just made an installation of zero > mailman, with potsfix on centos 6. I have an error when trying to create a > new list in which shows me: > Error: Unknown virtual host... *** *** *** *** It appears you are trying to create the list via the web create UI as that is the only thing which issues the exact "Unknown virtual host" error message. That error basically says that the host name in the URL that you went to, e.g. http://host_name/mailman/create, does not exist in Mailman's VIRTUAL_HOSTS dictionary which is created by add_virtualhost directives in Defaults.py and mm_cfg.py. I'm guessing from your '*** *** *** ***' that you actually used an IP address when visiting that page, possibly an 'internal network' one. You don't want to create the list with such an address for its web host. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jdd at dodin.org Tue Jul 12 13:38:33 2016 From: jdd at dodin.org (jdd) Date: Tue, 12 Jul 2016 19:38:33 +0200 Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: <22405.9578.83150.64607@turnbull.sk.tsukuba.ac.jp> References: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> <86894281-cc73-b231-9e06-4552730934cc@dodin.org> <22405.9578.83150.64607@turnbull.sk.tsukuba.ac.jp> Message-ID: Le 12/07/2016 ? 19:14, Stephen J. Turnbull a ?crit : > It would be better than pipermail, though, I think I prefer HyperKitty > to GMane. sure, if you have mailman 3 suite :-) siome forums also have mialing list gateway, for example: https://doc.tiki.org/Forum+and+Mailing+List+Synchronization jdd From mark at msapiro.net Tue Jul 12 14:47:48 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2016 11:47:48 -0700 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <22404.38471.848834.276379@turnbull.sk.tsukuba.ac.jp> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> <22404.38471.848834.276379@turnbull.sk.tsukuba.ac.jp> Message-ID: <57853B54.1050608@msapiro.net> On 07/12/2016 12:03 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: > > > > > > How about using 'backslashreplace' instead of 'replace' to encode to > > > list's preferred language in Mailman/Handlers/SpamDetect.py ? > > I see you've already done this, but ... > > I would consider xmlrefreplace as well. xmlrefs are something most > people (users/moderators) have seen, backslash they're not going to > recognize unless they're programmers. I have now switched to xmlcharrefreplace instead of backslashreplace as I agree this will be easier to explain and understand. I was uncertain about this at first because I didn't know that xmlcharrefreplace wouldn't use entity names in some cases, but it appears that it only uses numeric references. > At an earlier stage, you could also just do a trial re-encoding with > the list preferred codec, set errors = 'strict', catch the Exception, > and re-raise as a Hold (or Discard, according to per-list policy). > (Then discard the output.) I would prefer this solution, I think, as > creating regexps turns out to be an issue for many list owners. > > People would have to learn not to use emoji in headers, of course, or > suffer moderation delays or even discards. I think this will have too many undesired effects. Not just emoji, but accented latin or CJK characters, etc. in display names would I think be real problems, even on English language lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jul 12 15:22:04 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2016 12:22:04 -0700 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> Message-ID: <5785435C.7010904@msapiro.net> On 07/12/2016 07:24 AM, Jim Popovitch wrote: > On Tue, Jul 12, 2016 at 3:04 AM, Stephen J. Turnbull wrote: >> is something you should look at before deciding to stay with a product >> after end-of-line. > > Doesn't this list traffic and interest prove that mm2x is nowhere near > end of life? I mean the interest is here, should that be actively > discouraged? It depends on how you define "end of life". Granted there will be MM 2.1 lists in use for a very long time. There may still even be Mailman 2.0 lists in active use. The real question is not how long there will be users, but how long will Mailman 2.1 be actively supported and maintained, and whether it makes sense for new installations to use a package with little or no further development in sight vs. one with an active and growing development and support community. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Tue Jul 12 22:00:19 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 13 Jul 2016 11:00:19 +0900 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> Message-ID: <22405.41139.585014.823624@turnbull.sk.tsukuba.ac.jp> Jim Popovitch writes: > On Tue, Jul 12, 2016 at 3:04 AM, Stephen J. Turnbull wrote: > > is something you should look at before deciding to stay with a product > > after end-of-line. > > Doesn't this list traffic and interest prove that mm2x is nowhere near > end of life? I mean the interest is here, should that be actively > discouraged? Note that I very carefully avoided the term "end of life". LISP lives! (though it has long since been title-cased). The interest that matters is not in being a v2.1 user -- we know about that. It's in providing support to v2.1 users. Mark's is waning (aside from repeatedly stating that 2.1 releases are not going to continue for much longer, he's already supporting 3.x lists for at least two organizations and seemed to be enjoying himself hugely at the sprint on Mailman 3 at PyCon). I'm definitely committed to Mailman 3, and I'm finding the time I spend on this list a burden. All the other developers have long since found the exit. Whose interest in this task is waxing? I'm not going to say that user-supported software whose core developers have moved on can't work (eg, qmail), but it's rare. And this particular thread requires a programmer to hack on it. Are there volunteers? If not, the way forward is Mailman 3. Of course those who are perfectly satisfied with Mailman 2 can keep using it, and keep supporting each other with tips about regexps etc: "bitrot" is a myth. But new features will be added to Mailman 2 only if they are one-liners, as I interpret Mark's changes for the last couple of years. Steve From futatuki at poem.co.jp Wed Jul 13 00:15:17 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI) Date: Wed, 13 Jul 2016 13:15:17 +0900 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <57853B54.1050608@msapiro.net> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> <22404.38471.848834.276379@turnbull.sk.tsukuba.ac.jp> <57853B54.1050608@msapiro.net> Message-ID: <5785C055.9000905@poem.co.jp> On 07/13/16 03:47, Mark Sapiro wrote: > On 07/12/2016 12:03 AM, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> > On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: >> > > >> > > How about using 'backslashreplace' instead of 'replace' to encode to >> > > list's preferred language in Mailman/Handlers/SpamDetect.py ? >> >> I see you've already done this, but ... >> >> I would consider xmlrefreplace as well. xmlrefs are something most >> people (users/moderators) have seen, backslash they're not going to >> recognize unless they're programmers. > > > I have now switched to xmlcharrefreplace instead of backslashreplace as > I agree this will be easier to explain and understand. I was uncertain > about this at first because I didn't know that xmlcharrefreplace > wouldn't use entity names in some cases, but it appears that it only > uses numeric references. I don't have strong objection to switch to xmlcharrefreplace because my main subject is to distinguish '?' from replaced characters. But personally I prefer backslashreplace for looking up Unicode table, for numeric reference of xmlcharreplace seems to use decimal, while backslashreplace uses hexadecimal, and most of Unicode table uses hexadecimal for express code point like U+4E8C. >> At an earlier stage, you could also just do a trial re-encoding with >> the list preferred codec, set errors = 'strict', catch the Exception, >> and re-raise as a Hold (or Discard, according to per-list policy). >> (Then discard the output.) I would prefer this solution, I think, as >> creating regexps turns out to be an issue for many list owners. >> >> People would have to learn not to use emoji in headers, of course, or >> suffer moderation delays or even discards. > > I think this will have too many undesired effects. Not just emoji, but > accented latin or CJK characters, etc. in display names would I think be > real problems, even on English language lists. I suggest to use variable to select handler from 'replace' (for backword compatibility), 'xmlcharrefreplace', or 'backslashreplace' in mm_cfg.py. I think it is better to hold string attributes of mm_cfg and mlist class as Unicode than site_language code or list's preferred language code encoded (but I know it is so trouble to do so). -- Yasuhito FUTATSUKI From ginesgb at gmail.com Wed Jul 13 07:00:54 2016 From: ginesgb at gmail.com (Gines Granados Bayona) Date: Wed, 13 Jul 2016 13:00:54 +0200 Subject: [Mailman-Users] Mailman-Users Digest, Vol 149, Issue 16 In-Reply-To: References: Message-ID: Hello, well to everybody, thank you very much Mark Sapiro mark at msapiro.net, i do the steps and it has worked effectively, but It weirdest other error has occurred, I now send email that is outside the local network on Internet but lan I can not send email giving errors like that attached, what do I lacked configure now? Thank you very much ******-request@*****.net Mailing list subscription confirmation notice for mailing list Rancid We have received a request from 172.23.9.193 for subscription of your email address, "ginesgb at gmail.com", to the sistemas.rancid@******.net mailing list. To confirm that you want to be added to this mailing list, simply reply to this message, keeping the Subject: header intact. Or visit this web page: http:// *****.*****.net/mailman/confirm/******/852fac84b3c566cec81644cc46c6b62d95f82bbc Or include the following line -- and only the following line -- in a message to ****************-request@*****.****.net: confirm 852fac84b3c566cec81644cc46c6b62d95f82bbc Note that simply sending a `reply' to this message should work from most mail readers, since that usually leaves the Subject: line in the right form (additional "Re:" text in the Subject: is okay). ************************************ Jul 13 12:43:29 2016 (8111) All recipients refused: {'ginesgb@******.net': (550, '5.1.1 : Recipient address rejected: User unknown in local recipient table')}, msgid: Jul 13 12:43:29 2016 (8111) delivery to ginesgb@******.net failed with code 550: 5.1.1 : Recipient address rejected: User unknown in local recipient table 2016-07-12 21:22 GMT+02:00 : > Send Mailman-Users mailing list submissions to > mailman-users at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/mailman-users > or, via email, send a message with subject or body 'help' to > mailman-users-request at python.org > > You can reach the person managing the list at > mailman-users-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Users digest..." > > Today's Topics: > > 1. Error unknown virtual host mailman (Gines Granados Bayona) > 2. Re: How to actively read the list online? (Stephen J. Turnbull) > 3. Re: How to actively read the list online? (Stephen J. Turnbull) > 4. Re: Error unknown virtual host mailman (Mark Sapiro) > 5. Re: How to actively read the list online? (jdd) > 6. Re: Chinese characters spam filter? (Mark Sapiro) > 7. Re: Filtering out Digest replies (Mark Sapiro) > > > ---------- Mensaje reenviado ---------- > From: Gines Granados Bayona > To: mailman-users at python.org > Cc: > Date: Tue, 12 Jul 2016 13:10:38 +0200 > Subject: [Mailman-Users] Error unknown virtual host mailman > Hello everyone, I'm new in mailman and just made an installation of zero > mailman, with potsfix on centos 6. I have an error when trying to create a > new list in which shows me: > Error: Unknown virtual host... *** *** *** *** > I do not know what parameter settings I could make wrong, or should change > and though I've read several forums, I see that the fix are settings are > different , do We can indicate that parameter must change? > > Greetings and thank you > > -- > Este mensaje se dirige exclusivamente a su destinatario. Puede contener > informaci?n confidencial sometida a secreto profesional o cuya divulgaci?n > este prohibida, en virtud de la legislaci?n vigente. No esta permitida su > divulgaci?n, copia o distribuci?n a terceros sin la autorizaci?n previa y > por escrito del remitente. Si ha recibido este mensaje por error, le > rogamos nos lo comunique inmediatamente por esta misma v?a y proceda a su > destrucci?n. > > > This e-mail is intended exclusively for the individual or entity to which > it is addressed > and may contain confidential or legally privileged information, which may > not be disclosed under current legislation. Any form of disclosure, copying > or distribution of this e-mail is strictly prohibited, save with written > authorisation . If you have received this message in error, please notify > the sender immediately by e-mail and delete all copies of the message. > > > > ---------- Mensaje reenviado ---------- > From: "Stephen J. Turnbull" > To: jdd > Cc: mailman-users at python.org > Date: Wed, 13 Jul 2016 02:14:18 +0900 > Subject: Re: [Mailman-Users] How to actively read the list online? > jdd writes: > > > but couldn't gmane be a solution? > > > > http://gmane.org/ > > It would be better than pipermail, though, I think I prefer HyperKitty > to GMane. > > But for forum users, I don't think it would be close enough. > Specifically, I don't think GMane serves whole threads as a single > page; you have to click on next post. I don't know whether there's an > autorefresh on the header, either. It won't be a lot like the > experience with many forums (eg, Discourse). > > > > ---------- Mensaje reenviado ---------- > From: "Stephen J. Turnbull" > To: Lucio Chiappetti > Cc: Mailman list > Date: Wed, 13 Jul 2016 02:17:32 +0900 > Subject: Re: [Mailman-Users] How to actively read the list online? > Lucio Chiappetti writes: > > > Personally (coming from Usenet, and used to read Usenet forums, i.e. > > newsgroups, via a MAIL client) I sort-of hate forums, > > Then you're definitely welcome here! :-) > > > Anyhow, getting a self-refreshing html page is just a matter of adding a > > tag to the > > Sure, but if the page itself is static (as in a conventional mailing > list archive), that won't help. The archive host has to be prepared > to feed *new* pages, not refresh the old one, when accessed. > > > > > ---------- Mensaje reenviado ---------- > From: Mark Sapiro > To: mailman-users at python.org > Cc: > Date: Tue, 12 Jul 2016 10:25:32 -0700 > Subject: Re: [Mailman-Users] Error unknown virtual host mailman > On 07/12/2016 04:10 AM, Gines Granados Bayona wrote: > > Hello everyone, I'm new in mailman and just made an installation of zero > > mailman, with potsfix on centos 6. I have an error when trying to create > a > > new list in which shows me: > > Error: Unknown virtual host... *** *** *** *** > > > It appears you are trying to create the list via the web create UI as > that is the only thing which issues the exact "Unknown virtual host" > error message. > > That error basically says that the host name in the URL that you went > to, e.g. http://host_name/mailman/create, does not exist in Mailman's > VIRTUAL_HOSTS dictionary which is created by add_virtualhost directives > in Defaults.py and mm_cfg.py. > > I'm guessing from your '*** *** *** ***' that you actually used an IP > address when visiting that page, possibly an 'internal network' one. You > don't want to create the list with such an address for its web host. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > > ---------- Mensaje reenviado ---------- > From: jdd > To: > Cc: mailman-users at python.org > Date: Tue, 12 Jul 2016 19:38:33 +0200 > Subject: Re: [Mailman-Users] How to actively read the list online? > Le 12/07/2016 ? 19:14, Stephen J. Turnbull a ?crit : > > It would be better than pipermail, though, I think I prefer HyperKitty >> to GMane. >> > > sure, if you have mailman 3 suite :-) > > siome forums also have mialing list gateway, for example: > > https://doc.tiki.org/Forum+and+Mailing+List+Synchronization > > jdd > > > > > ---------- Mensaje reenviado ---------- > From: Mark Sapiro > To: "Stephen J. Turnbull" > Cc: mailman-users at python.org > Date: Tue, 12 Jul 2016 11:47:48 -0700 > Subject: Re: [Mailman-Users] Chinese characters spam filter? > On 07/12/2016 12:03 AM, Stephen J. Turnbull wrote: > > Mark Sapiro writes: > > > On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: > > > > > > > > How about using 'backslashreplace' instead of 'replace' to encode to > > > > list's preferred language in Mailman/Handlers/SpamDetect.py ? > > > > I see you've already done this, but ... > > > > I would consider xmlrefreplace as well. xmlrefs are something most > > people (users/moderators) have seen, backslash they're not going to > > recognize unless they're programmers. > > > I have now switched to xmlcharrefreplace instead of backslashreplace as > I agree this will be easier to explain and understand. I was uncertain > about this at first because I didn't know that xmlcharrefreplace > wouldn't use entity names in some cases, but it appears that it only > uses numeric references. > > > > At an earlier stage, you could also just do a trial re-encoding with > > the list preferred codec, set errors = 'strict', catch the Exception, > > and re-raise as a Hold (or Discard, according to per-list policy). > > (Then discard the output.) I would prefer this solution, I think, as > > creating regexps turns out to be an issue for many list owners. > > > > People would have to learn not to use emoji in headers, of course, or > > suffer moderation delays or even discards. > > > I think this will have too many undesired effects. Not just emoji, but > accented latin or CJK characters, etc. in display names would I think be > real problems, even on English language lists. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > > ---------- Mensaje reenviado ---------- > From: Mark Sapiro > To: mailman-users at python.org > Cc: > Date: Tue, 12 Jul 2016 12:22:04 -0700 > Subject: Re: [Mailman-Users] Filtering out Digest replies > On 07/12/2016 07:24 AM, Jim Popovitch wrote: > > On Tue, Jul 12, 2016 at 3:04 AM, Stephen J. Turnbull > wrote: > >> is something you should look at before deciding to stay with a product > >> after end-of-line. > > > > Doesn't this list traffic and interest prove that mm2x is nowhere near > > end of life? I mean the interest is here, should that be actively > > discouraged? > > > It depends on how you define "end of life". Granted there will be MM 2.1 > lists in use for a very long time. There may still even be Mailman 2.0 > lists in active use. > > The real question is not how long there will be users, but how long will > Mailman 2.1 be actively supported and maintained, and whether it makes > sense for new installations to use a package with little or no further > development in sight vs. one with an active and growing development and > support community. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > -- Este mensaje se dirige exclusivamente a su destinatario. Puede contener informaci?n confidencial sometida a secreto profesional o cuya divulgaci?n este prohibida, en virtud de la legislaci?n vigente. No esta permitida su divulgaci?n, copia o distribuci?n a terceros sin la autorizaci?n previa y por escrito del remitente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. This e-mail is intended exclusively for the individual or entity to which it is addressed and may contain confidential or legally privileged information, which may not be disclosed under current legislation. Any form of disclosure, copying or distribution of this e-mail is strictly prohibited, save with written authorisation . If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. From futatuki at poem.co.jp Wed Jul 13 07:38:55 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI) Date: Wed, 13 Jul 2016 20:38:55 +0900 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <5785C055.9000905@poem.co.jp> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> <22404.38471.848834.276379@turnbull.sk.tsukuba.ac.jp> <57853B54.1050608@msapiro.net> <5785C055.9000905@poem.co.jp> Message-ID: <5786284F.5010407@poem.co.jp> On 07/13/16 13:15, I wrote: > On 07/13/16 03:47, Mark Sapiro wrote: >> On 07/12/2016 12:03 AM, Stephen J. Turnbull wrote: >>> At an earlier stage, you could also just do a trial re-encoding with >>> the list preferred codec, set errors = 'strict', catch the Exception, >>> and re-raise as a Hold (or Discard, according to per-list policy). >>> (Then discard the output.) I would prefer this solution, I think, as >>> creating regexps turns out to be an issue for many list owners. >>> >>> People would have to learn not to use emoji in headers, of course, or >>> suffer moderation delays or even discards. >> >> I think this will have too many undesired effects. Not just emoji, but >> accented latin or CJK characters, etc. in display names would I think be >> real problems, even on English language lists. > > I suggest to use variable to select handler from 'replace' (for backword > compatibility), 'xmlcharrefreplace', or 'backslashreplace' or 'strict' with catching Exception > in mm_cfg.py. > I think it is better to hold string attributes of mm_cfg and mlist class > as Unicode than site_language code or list's preferred language code > encoded (but I know it is so trouble to do so). And then on pattern matching on message pipeline is done with Unicode rather than list's prefered language. -- Yasuhito FUTATSUKI From lucio at lambrate.inaf.it Wed Jul 13 08:37:44 2016 From: lucio at lambrate.inaf.it (Lucio Chiappetti) Date: Wed, 13 Jul 2016 14:37:44 +0200 (CEST) Subject: [Mailman-Users] How to actively read the list online? In-Reply-To: <22405.9772.835666.532808@turnbull.sk.tsukuba.ac.jp> References: <22404.38827.967688.645267@turnbull.sk.tsukuba.ac.jp> <22405.9772.835666.532808@turnbull.sk.tsukuba.ac.jp> Message-ID: On Wed, 13 Jul 2016, Stephen J. Turnbull wrote: > Lucio Chiappetti writes: > > Anyhow, getting a self-refreshing html page is just a matter of adding a > > tag to the > > Sure, but if the page itself is static (as in a conventional mailing > list archive), that won't help. The archive host has to be prepared > to feed *new* pages, not refresh the old one, when accessed. Might be not that different (although perhaps is an overkill). There is no much difference in refreshing a page with a click of the user, and having the browser requesting a refresh with a meta-equiv-refresh if the underlying page has changed. I do use the trick with some of my pages, some are CGI scripts which auto-refresh, but in other cases the page can be modified by a crontab script (I say overkill because if the meta-equiv-refresh asks for a refresh every minute, and the crontab updates the page every 15-30 min most of the refresh will be void) Consider a standard mailman thread archive like e.g. https://listmgr.nrao.edu/pipermail/fitsbits/2016-July/thread.html If somebody will make a new post, and I reload the archive page, I will see the new message (I use this trick to verify a message was archived after I sent it). If one could MODIFY the standard format of the archive page in mailman to prepend the meta-equiv-refresh (and I do not know how easy is that. I've never personalised any of the mailman HTML pages although I know for some is possible, maybe one has to patch code) ... that would do the trick. -- ------------------------------------------------------------------------ Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ Do not like Firefox >=29 ? Get Pale Moon ! http://www.palemoon.org From jimpop at gmail.com Wed Jul 13 11:39:27 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Wed, 13 Jul 2016 11:39:27 -0400 Subject: [Mailman-Users] Filtering out Digest replies In-Reply-To: <22405.41139.585014.823624@turnbull.sk.tsukuba.ac.jp> References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> <22405.41139.585014.823624@turnbull.sk.tsukuba.ac.jp> Message-ID: On Tue, Jul 12, 2016 at 10:00 PM, Stephen J. Turnbull wrote: > Whose interest in this task is waxing? I'm not going to say that > user-supported software whose core developers have moved > on can't work (eg, qmail), but it's rare. And this particular thread > requires a programmer to hack on it. Are there volunteers? Is the issue really lack of people who can commit? Every time I look at launchpad I'm amazed at the number of active participants. > If not, the way forward is Mailman 3. No one doubts that. The timing for that is what is in question. Considering LTS releases, MM2.1 could be in some level of production until 2019. Someone from the MM team will have to deal with CVEs, etc., and I guess everybody is presuming that will still be Mark. What I doubt we will see is a mass migration to MM3, people just don't normally do that until in-house milestones (new infrastructure, hardware crashed and all data is lost, etc.) -Jim P. From barry at python.org Wed Jul 13 12:01:22 2016 From: barry at python.org (Barry Warsaw) Date: Wed, 13 Jul 2016 12:01:22 -0400 Subject: [Mailman-Users] Command line access to Mailman 3 (was Re: Filtering out Digest replies) References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> Message-ID: <20160713120122.2569def3@anarchist.wooz.org> On Jul 12, 2016, at 04:04 PM, Stephen J. Turnbull wrote: >Thomas Gramstad writes: > > > There is also the issue of listadmin, the script for command line > > processing of list moderation requests. I'm not sure this script > > is being updated currently, and so probably does not work with > > Mailman 3(?). > >I don't know if it's been integrated yet, but mailmanclient has a nice >command interpreter that a GSoC student built for us. Even if your >particular use case isn't supported yet, it will be easy to do so. > >I think you'll also find Postorius much more efficient than the >current web interface. That may not be enough since you say managing >moderation with the current interface is out of the question, but >since moderation is an activity that needs human input, and UI changes >(ie, use of command line) were enough to make it feasible, Postorius >is something you should look at before deciding to stay with a product >after end-of-line. Mailman 3 has a very rich REST API which can control and administer the core system. In fact, this is exactly how Postorius and HyperKitty work, via mailmanclient, the official Python bindings for the REST API. Being HTTP+JSON, you can in fact talk to Core's REST API using any language you want (even curl for example). However, it's also important to understand that Core's REST API is an administrative API with full access and no authentication (other than Basic AUTH). It is intended to be exposed on localhost only. It's long been discussed to create an "authenticating proxy" which could be exposed on any public IP, and which would allow site admins, list admins, moderators, and users to script the Core, performing any operations that their authorization level permits. Andrew Stuart wrote a project called mailmania (available on GitLab) which implements one take on this. At Pycon 2016, the Mailman sprinters discussed how to move forward on an official proxy, taking inspiration from mailmania. I think we fleshed out a good approach which will be much richer than any MM2 scripting facility, and could be one of the killer apps for MM3 (including IMHO HyperKitty's ability to post from the web, and Postorius's vastly better U/I). We even have name for the project, Lemme and a project page: https://gitlab.com/mailman/lemme/tree/master Several of us are going to start working on this after the MM3.1 release goes out (hopefully in the next month or so). It will take work in the Core as well as work on Lemme, so we invite anybody interested in helping out to join us over in mailman-developers. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From barry at python.org Wed Jul 13 12:16:38 2016 From: barry at python.org (Barry Warsaw) Date: Wed, 13 Jul 2016 12:16:38 -0400 Subject: [Mailman-Users] Mailman 2's future (was Re: Filtering out Digest replies) References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> <5785435C.7010904@msapiro.net> Message-ID: <20160713121638.6373e141@anarchist.wooz.org> On Jul 12, 2016, at 12:22 PM, Mark Sapiro wrote: >It depends on how you define "end of life". Granted there will be MM 2.1 >lists in use for a very long time. There may still even be Mailman 2.0 >lists in active use. > >The real question is not how long there will be users, but how long will >Mailman 2.1 be actively supported and maintained, and whether it makes >sense for new installations to use a package with little or no further >development in sight vs. one with an active and growing development and >support community. Like all FLOSS software, future development and support is highly dependent on finding volunteers interested enough to donate their time to work on it. It's rare to be paid to work on FLOSS, and I can only say that *I* am not paid to work on Mailman. Mark is my hero, for long ago having taken over the task of maintaining Mailman 2.1 and allowing me to concentrate on Mailman 3. I greatly appreciate Steve and all of you who continue to dedicate your time to help each other, solve problems, and keep the Mailman community thriving. I have no interest or time to devote to Mailman 2. The code is 20 years old, and like Python 2, I find it very hard to get motivated to wade into it. Mark knows way more about it than I remember at this point anyway. I am spending my free time trying to make Mailman 3 a compelling and stable upgrade path, with code that's a joy to work in, an architecture that is clean, flexible, and robust, and a universe of tools and subprojects that bring the Mailman we love forward to modern practices, and which integrate better with all the other outlets people have for online communication. Just like with Python 2, Mailman 2.1 will continue to be actively and happily used for many years to come. If and when Mark decides to spend more time on Mailman 3 (\o/) others in this community can rise to the challenge of continuing to support Mailman 2. That's what a volunteer community is all about. There is lots of fun stuff to do, and I call on you to find areas of interest to get involved in. Almost anything you *want* to do *needs* to be done, and we developers are a nice bunch of people, so please join us! Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From guest2 at sgeinc.com Wed Jul 13 12:49:54 2016 From: guest2 at sgeinc.com (Richard Shetron) Date: Wed, 13 Jul 2016 12:49:54 -0400 Subject: [Mailman-Users] Mailman 2's future (was Re: Filtering out Digest replies) In-Reply-To: <20160713121638.6373e141@anarchist.wooz.org> References: <964dd691-d5da-37a7-80ff-c0a519d9fc0e@msapiro.net> <22404.38544.449461.937531@turnbull.sk.tsukuba.ac.jp> <5785435C.7010904@msapiro.net> <20160713121638.6373e141@anarchist.wooz.org> Message-ID: On 7/13/2016 12:16 PM, Barry Warsaw wrote: > On Jul 12, 2016, at 12:22 PM, Mark Sapiro wrote: [snip end of life comments] One thing that makes end of life either easier to handle or harder is: 1) Documentation of the changes and the new system. 2) Conversion aids. At least a program to check a prior system and report all the problems in converting to the new system. Best is a program that can do a full conversion from the old system to the new one with the minimal operator intervention. Yes, I've done that, I worked for a company for 10 years and one of the standard things was converting new customers to our system, exporting data for those going away, and upgrading those on older versions to the newest version. 3) Documentation. I say this twice to emphasis it! From mailinglist at samsi.us Tue Jul 12 15:59:10 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Tue, 12 Jul 2016 12:59:10 -0700 Subject: [Mailman-Users] MailMan won't send list emails Message-ID: Hi there, I?ve been working on this for 1 day and getting frustrated. Everything appears to be setup correctly (lists can be created, list emails are received, I can see emails received in the list mailbox. MailMan sends out notification emails to owners and subscribers. Confirmation email is sent out and processed via web page. The only thing left is sending out received emails. I don?t know where to begin troubleshooting this. Thanks, Caesar. From mailinglist at samsi.us Tue Jul 12 18:55:53 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Tue, 12 Jul 2016 15:55:53 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> Message-ID: <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> [Adding information] Postfix /etc/postfix/main.cf configuration: virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, hash:/var/lib/mailman/data/virtual-mailman alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases relay_domains = mail.samsi.us mailman_destination_recipient_limit = 1 transport_maps = hash:/etc/postfix/transport smtpd_reject_unlisted_sender = no /var/lib/mailman/data/virtual-mailman: test at yugi.us test /etc/aliases: # /etc/aliases mailer-daemon: postmaster postmaster: root nobody: root hostmaster: root usenet: root news: root webmaster: root www: root ftp: root abuse: root noc: root security: root clamav: root monit: root /var/lib/mailman/data/aliases: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE # unless you know what you're doing, and can keep the two files properly # in sync. If you screw it up, you're on your own. # The ultimate loop stopper address mailman-loop: /var/lib/mailman/data/owner-bounces.mbox # STANZA START: mailman # CREATED: Tue Jul 12 12:31:00 2016 mailman: "|/var/lib/mailman/mail/mailman post mailman" mailman-admin: "|/var/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/var/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/var/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/var/lib/mailman/mail/mailman join mailman" mailman-leave: "|/var/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/var/lib/mailman/mail/mailman owner mailman" mailman-request: "|/var/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/var/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman # STANZA START: test # CREATED: Tue Jul 12 12:31:00 2016 test: "|/var/lib/mailman/mail/mailman post test" test-admin: "|/var/lib/mailman/mail/mailman admin test" test-bounces: "|/var/lib/mailman/mail/mailman bounces test" test-confirm: "|/var/lib/mailman/mail/mailman confirm test" test-join: "|/var/lib/mailman/mail/mailman join test" test-leave: "|/var/lib/mailman/mail/mailman leave test" test-owner: "|/var/lib/mailman/mail/mailman owner test" test-request: "|/var/lib/mailman/mail/mailman request test" test-subscribe: "|/var/lib/mailman/mail/mailman subscribe test" test-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe test" # STANZA END: test /etc/postfix/transport: mail.samsi.us mailman: /etc/postfix/master.cf mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} > On Jul 12, 2016, at 1:10 PM, Caesar Samsi wrote: > > [resending, sent it before confirmation was completed earlier] > > Hi there, > > I?ve been working on this for 1 day and getting frustrated. > > Everything appears to be setup correctly (lists can be created, list emails are received, I can see emails received in the list mailbox. > > MailMan sends out notification emails to owners and subscribers. Confirmation email is sent out and processed via web page. > > The only thing left is sending out received emails. > > I don?t know where to begin troubleshooting this. > > Thanks, Caesar. > From mark at msapiro.net Wed Jul 13 13:39:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 10:39:46 -0700 Subject: [Mailman-Users] Problems with Mail Delivery - was: Mailman-Users Digest, Vol 149, Issue 16 In-Reply-To: References: Message-ID: <57867CE2.9030806@msapiro.net> On 07/13/2016 04:00 AM, Gines Granados Bayona wrote: Please do not 'reply' to digests or if replying to a digest, provide a meaningful Subject:. > Hello, well to everybody, thank you very much Mark Sapiro mark at msapiro.net, > i do the steps and it has worked effectively, but It weirdest other error > has occurred, I now send email that is outside the local network on > Internet but lan I can not send email giving errors like that attached, > what do I lacked configure now? ... > Jul 13 12:43:29 2016 (8111) All recipients refused: {'ginesgb@******.net': > (550, '5.1.1 : Recipient address rejected: User unknown > in local recipient table')}, msgid: > > Jul 13 12:43:29 2016 (8111) delivery to ginesgb@******.net failed with code > 550: 5.1.1 : Recipient address rejected: User unknown > in local recipient table This is a Postfix configuration issue. Your local MTA can't deliver to this local recipient. We may be able to help, but in order to do so, we need more information. Is 'ginesgb' a user on this server with a mailbox on this server, or just elsewhere on your LAN? What is the output from 'postconf -n'? > 2016-07-12 21:22 GMT+02:00 : > >> Send Mailman-Users mailing list submissions to >> mailman-users at python.org ... >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Mailman-Users digest..." And please NEVER quote an entire digest in your reply, And legal disclaimers such as attached to your mail are not appropriate for mail to a publicly archived mailman list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Jul 13 13:55:07 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 10:55:07 -0700 Subject: [Mailman-Users] Chinese characters spam filter? In-Reply-To: <5786284F.5010407@poem.co.jp> References: <4861d0d7-f708-3f47-d1a3-f38e1178d3df@msapiro.net> <57fdeb97-88aa-e4b8-f5e8-6a12af87172c@msapiro.net> <57804DB4.8030906@poem.co.jp> <22404.38471.848834.276379@turnbull.sk.tsukuba.ac.jp> <57853B54.1050608@msapiro.net> <5785C055.9000905@poem.co.jp> <5786284F.5010407@poem.co.jp> Message-ID: <5786807B.7040206@msapiro.net> On 07/13/2016 04:38 AM, Yasuhito FUTATSUKI wrote: > >> I think it is better to hold string attributes of mm_cfg and mlist class >> as Unicode than site_language code or list's preferred language code >> encoded (but I know it is so trouble to do so). > And then on pattern matching on message pipeline is done with Unicode > rather than list's prefered language. I have been working on a change to do exactly that. I.e. collect the headers for matching with header_filter_rules as unicode and match the patterns as unicode. This is very difficult to do on a list whose preferred_language character set doesn't support the characters in the header_filter_rules patterns, e.g., trying to match Chinese characters in Subject: headers on an English language list. The major issue is when the character set of the form is say us-ascii and one enters non-ascii as a pattern, it is up to the browser to decide how to encode that. In at least one case with Firefox, characters which are in the windows-1252 character set are encoded as that and others as XML numeric references. I can easily deal with converting the XML numeric references to unicodes, but I don't know in what charset the other characters are encoded. Yes, I know that everything should be unicode and utf-8 encoded regardless of language, but that isn't going to happen in MM 2.1. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Jul 13 15:28:30 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 12:28:30 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> Message-ID: <5786965E.3030906@msapiro.net> On 07/12/2016 03:55 PM, Caesar Samsi wrote: > [Adding information] > > Postfix /etc/postfix/main.cf configuration: > > virtual_alias_maps = > mysql:/etc/postfix/mysql_virtual_alias_maps.cf, > mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, > hash:/var/lib/mailman/data/virtual-mailman > > alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases > relay_domains = mail.samsi.us > mailman_destination_recipient_limit = 1 > transport_maps = hash:/etc/postfix/transport > smtpd_reject_unlisted_sender = no > > /var/lib/mailman/data/virtual-mailman: > > test at yugi.us test I don't know where this comes from. > /etc/aliases: ... > /var/lib/mailman/data/aliases: ... > aliases look OK, but... > /etc/postfix/transport: > > mail.samsi.us mailman: > > /etc/postfix/master.cf > > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} You are using postfix-to-mailman.py for all mail to the mail.samsi.us domain. See and decide whether you want to use postfix-to-mailman.py or Postfix-Mailman integration. Once you have decided that, if you are still having problems, please provide the contents of mm_cfg.py and the Postfix log entries for a message sent to a mailman list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mailinglist at samsi.us Wed Jul 13 20:35:25 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Wed, 13 Jul 2016 17:35:25 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <5786965E.3030906@msapiro.net> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> Message-ID: Hi Mark, Thank you for rendering aid. Caesar. > On Jul 13, 2016, at 12:28 PM, Mark Sapiro wrote: > > > I don't know where this comes from. > > >> /etc/aliases: - Caesar: I?ve removed it from the configuration > ... >> /var/lib/mailman/data/aliases: Caesar: This is generated by bin/genaliases, what should I do with this? > ... >> > > > aliases look OK, but... > > >> /etc/postfix/transport: >> >> mail.samsi.us mailman: >> >> /etc/postfix/master.cf >> >> mailman unix - n n - - pipe >> flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py >> ${nexthop} ${user} > > > You are using postfix-to-mailman.py for all mail to the mail.samsi.us > domain. > > See and decide whether you want to > use postfix-to-mailman.py or Postfix-Mailman integration. Caesar: I?d like to use the official Postfix-Mailman integration > > Once you have decided that, if you are still having problems, please > provide the contents of mm_cfg.py and the Postfix log entries for a > message sent to a mailman list. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://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: https://mail.python.org/mailman/options/mailman-users/mailinglist%40samsi.us mm_cfg.py attached. Log entries for list message (list address: test at yugi.us) Jul 11 17:06:14 mail postfix/cleanup[7937]: 2737340147: message-id= Jul 11 17:06:14 mail postfix/qmgr[7604]: 2737340147: from=, size=2232, nrcpt=1 (queue active) Jul 11 17:06:14 mail postfix/smtpd[7933]: disconnect from localhost[::1] Jul 11 17:06:17 mail postfix/smtpd[7944]: connect from localhost[127.0.0.1] Jul 11 17:06:17 mail postfix/smtpd[7944]: 9634C40148: client=localhost[127.0.0.1] Jul 11 17:06:17 mail postfix/cleanup[7937]: 9634C40148: message-id= Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: from=, size=2873, nrcpt=1 (queue active) Jul 11 17:06:17 mail amavis[7745]: (07745-03) Passed CLEAN {RelayedInternal}, LOCAL [::1]:55664 -> , Queue-ID: 2737340147, Message-ID: , mail_id: 5M0RPAagfqDZ, Hits: 0.274, size: 2232, queued_as: 9634C40148, 3472 ms Jul 11 17:06:17 mail postfix/smtp[7939]: 2737340147: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=3.6, delays=0.1/0.04/0.02/3.5, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 9634C40148) Jul 11 17:06:17 mail postfix/qmgr[7604]: 2737340147: removed Jul 11 17:06:17 mail dovecot: lda(caesar at samsi.us): msgid=: saved mail to INBOX Jul 11 17:06:17 mail postfix/pipe[7945]: 9634C40148: to=, relay=dovecot, delay=0.18, delays=0.03/0.03/0/0.13, dsn=2.0.0, status=sent (delivered via dovecot service) Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: removed From mark at msapiro.net Wed Jul 13 21:47:50 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 18:47:50 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> Message-ID: <5786EF46.4070102@msapiro.net> On 07/13/2016 05:35 PM, Caesar Samsi wrote: > Hi Mark, > > Thank you for rendering aid. > > Caesar. > >> On Jul 13, 2016, at 12:28 PM, Mark Sapiro > > wrote: >> >> >> I don't know where this comes from. >> >> >>> /etc/aliases: - *Caesar*: I?ve removed it from the configuration My remark was about the contents of /var/lib/mailman/data/virtual-mailman, not /etc/aliases. You probably do want /etc/aliases in your Postfix config. >>> /var/lib/mailman/data/aliases: *Caesar*: This is generated by >>> bin/genaliases, what should I do with this? See below. >>> /etc/postfix/transport: >>> >>> mail.samsi.us mailman: You will want to remove /etc/postfix/transport from transport_maps in main.cf. >>> /etc/postfix/master.cf >>> >>> mailman unix - n n - - pipe >>> flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py >>> ${nexthop} ${user} The above in master.cf will be unnecessary, but leaving it won't matter if you don't reference the mailman transport in transport_maps. >> You are using postfix-to-mailman.py for all mail to the mail.samsi.us >> >> domain. >> >> See and decide whether you want to >> use postfix-to-mailman.py or Postfix-Mailman integration. *Caesar*: >> I?d like to use the official Postfix-Mailman integration OK. ... > mm_cfg.py attached. > > > > Log entries for list message (list address: test at yugi.us) > > Jul 11 17:06:14 mail postfix/cleanup[7937]: 2737340147: > message-id= > Jul 11 17:06:14 mail postfix/qmgr[7604]: 2737340147: > from=, size=2232, > nrcpt=1 (queue active) > Jul 11 17:06:14 mail postfix/smtpd[7933]: disconnect from localhost[::1] > Jul 11 17:06:17 mail postfix/smtpd[7944]: connect from localhost[127.0.0.1] > Jul 11 17:06:17 mail postfix/smtpd[7944]: 9634C40148: > client=localhost[127.0.0.1] > Jul 11 17:06:17 mail postfix/cleanup[7937]: 9634C40148: > message-id= > Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: > from=, size=2873, > nrcpt=1 (queue active) > Jul 11 17:06:17 mail amavis[7745]: (07745-03) Passed CLEAN > {RelayedInternal}, LOCAL [::1]:55664 -> , Queue-ID: 2737340147, Message-ID: > , mail_id: 5M0RPAagfqDZ, Hits: > 0.274, size: 2232, queued_as: 9634C40148, 3472 ms > Jul 11 17:06:17 mail postfix/smtp[7939]: 2737340147: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=3.6, > delays=0.1/0.04/0.02/3.5, dsn=2.0.0, status=sent (250 2.0.0 from > MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 9634C40148) > Jul 11 17:06:17 mail postfix/qmgr[7604]: 2737340147: removed > Jul 11 17:06:17 mail dovecot: lda(caesar at samsi.us): > msgid=: saved mail to INBOX > Jul 11 17:06:17 mail postfix/pipe[7945]: 9634C40148: to=, relay=dovecot, delay=0.18, > delays=0.03/0.03/0/0.13, dsn=2.0.0, status=sent (delivered via dovecot > service) > Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: removed > All these messages are from a message from Mailman to caesar at samsi.us which was apparently delivered appropriately. Are you able to send mail to test at yugi.us and have it delivered to Mailman? If not, what are the log messages related to that? Re: mm_cfg.py It all looks OK. I'm only quoting what I'm commenting about. > #------------------------------------------------------------- > # Default domain for email addresses of newly created MLs > DEFAULT_EMAIL_HOST = 'yugi.us' > #------------------------------------------------------------- > # Default host for web interface of newly created MLs > DEFAULT_URL_HOST = 'mail.samsi.us' > #------------------------------------------------------------- > # Required when setting any of its arguments. > #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) The above is good. > MTA='Postfix' > SMTPHOST = 'localhost' > SMTPPORT = 25 The above are good although only MTA='Postfix' is not a default. > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us'] This is good if yugi.us is a Postfix virtual alias domain. It also explains the test at yugi.us test entry in /var/lib/mailman/data/virtual-mailman but it doesn't explain why there aren't 9 more entries like test-admin at yugi.us test-admin test-bounces at yugi.us test-bounces ... See the manual at , and for information on configuring Postfix, and if you continue to have trouble, post the output of 'postconf -n' and the relevant Postfix log entries. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mailinglist at samsi.us Thu Jul 14 00:18:28 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Wed, 13 Jul 2016 21:18:28 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> Message-ID: <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> [including list] The log for an inbound email to test at yugi.us list Jul 13 20:48:09 mail postfix/smtpd[10666]: connect from macpro[192.168.1.253] Jul 13 20:48:09 mail postfix/smtpd[10666]: Anonymous TLS connection established from macpro[192.168.1.253]: TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Jul 13 20:48:09 mail postfix/smtpd[10666]: E31B13FFF3: client=macpro[192.168.1.253], sasl_method=PLAIN, sasl_username=caesar at samsi.us Jul 13 20:48:09 mail postfix/cleanup[10656]: E31B13FFF3: message-id=> Jul 13 20:48:09 mail postfix/qmgr[10476]: E31B13FFF3: from=>, size=316, nrcpt=1 (queue active) Jul 13 20:48:10 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1] Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1] Jul 13 20:48:11 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1] Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1] Jul 13 20:48:12 mail postfix/smtpd[10687]: connect from localhost[127.0.0.1] Jul 13 20:48:12 mail postfix/smtpd[10687]: A44093FFF4: client=localhost[127.0.0.1] Jul 13 20:48:12 mail postfix/cleanup[10656]: A44093FFF4: message-id=> Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: from=>, size=933, nrcpt=1 (queue active) Jul 13 20:48:12 mail amavis[9530]: (09530-14) Passed CLEAN {RelayedInternal}, LOCAL [192.168.1.253]:65462 > -> >, Queue-ID: E31B13FFF3, Message-ID: >, mail_id: lnzQpKxIXYKy, Hits: -0.002, size: 316, queued_as: A44093FFF4, 2809 ms Jul 13 20:48:12 mail postfix/smtp[10658]: E31B13FFF3: to=>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.9, delays=0.03/0.01/0.02/2.8, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as A44093FFF4) Jul 13 20:48:12 mail postfix/qmgr[10476]: E31B13FFF3: removed Jul 13 20:48:12 mail dovecot: lda(test at yugi.us ): msgid=>: saved mail to INBOX Jul 13 20:48:12 mail postfix/pipe[10664]: A44093FFF4: to=>, relay=dovecot, delay=0.18, delays=0.03/0.01/0/0.14, dsn=2.0.0, status=sent (delivered via dovecot service) Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: removed Postfix config: alias_maps = hash:/etc/aliases,hash:/var/lib/mailman/data/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix content_filter = amavis:[127.0.0.1]:10024 disable_vrfy_command = yes dovecot_destination_recipient_limit = 1 enable_original_recipient = no header_checks = regexp:/etc/postfix/header_checks inet_interfaces = all mailbox_size_limit = 0 mailman_destination_recipient_limit = 1 maximal_backoff_time = 8000s maximal_queue_lifetime = 7d minimal_backoff_time = 1000s mydestination = myhostname = mail.samsi.us mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mynetworks_style = host myorigin = /etc/hostname readme_directory = no recipient_delimiter = + relay_domains = mail.samsi.us smtp_helo_timeout = 60s smtpd_banner = $myhostname ESMTP $mail_name smtpd_delay_reject = yes smtpd_hard_error_limit = 12 smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, reject_unknown_helo_hostname, reject_non_fqdn_hostname, reject_invalid_hostname smtpd_recipient_limit = 16 smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_invalid_hostname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_rbl_client sbl.spamhaus.org , reject_rbl_client cbl.abuseat.org , reject_rbl_client dul.dnsbl.sorbs.net smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_soft_error_limit = 3 smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_exclude_ciphers = aNULL, eNULL, EXPORT, DES, RC4, MD5, PSK, aECDH, EDH-DSS-DES-CBC3-SHA, EDH-RSA-DES-CDC3-SHA, KRB5-DE5, CBC3-SHA smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_loglevel = 1 smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3 smtpd_tls_received_header = yes smtpd_tls_security_level = may smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 450 virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, hash:/var/lib/mailman/data/virtual-mailman virtual_gid_maps = static:8 virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf virtual_transport = dovecot virtual_uid_maps = static:150 > On Jul 13, 2016, at 7:53 PM, Mark Sapiro > wrote: > > On 07/13/2016 07:29 PM, Caesar Samsi wrote: > > > > You are going backwards. Please see my reply to your list mail at > > > > You need /var/lib/mailman/data/aliases and /etc/aliases in alias_maps > > You don't want transport_maps. > > Please don't post excerpts of your Postfix config. As I've asked before, > post the output from 'postconf -n', and post to the list. > > -- > Mark Sapiro > The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >> /etc/postfix/main.cf looks like (i.e. alias_map has been deleted, >> /etc/aliases and /var/lib/mailman/data/aliases is also deleted). >> >> virtual_alias_maps = >> mysql:/etc/postfix/mysql_virtual_alias_maps.cf, >> mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, >> hash:/var/lib/mailman/data/virtual-mailman >> >> relay_domains = mail.samsi.us > >> mailman_destination_recipient_limit = 1 >> transport_maps = hash:/etc/postfix/transport From mark at msapiro.net Thu Jul 14 00:56:10 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Jul 2016 21:56:10 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> Message-ID: <57871B6A.6030200@msapiro.net> On 07/13/2016 09:18 PM, Caesar Samsi wrote: > [including list] > > The log for an inbound email to test at yugi.us list > > Jul 13 20:48:09 mail postfix/smtpd[10666]: connect from macpro[192.168.1.253] > Jul 13 20:48:09 mail postfix/smtpd[10666]: Anonymous TLS connection established from macpro[192.168.1.253]: TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) > Jul 13 20:48:09 mail postfix/smtpd[10666]: E31B13FFF3: client=macpro[192.168.1.253], sasl_method=PLAIN, sasl_username=caesar at samsi.us > Jul 13 20:48:09 mail postfix/cleanup[10656]: E31B13FFF3: message-id= > Jul 13 20:48:09 mail postfix/qmgr[10476]: E31B13FFF3: from=, size=316, nrcpt=1 (queue active) > Jul 13 20:48:10 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1] > Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1] > Jul 13 20:48:11 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1] > Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1] > Jul 13 20:48:12 mail postfix/smtpd[10687]: connect from localhost[127.0.0.1] > Jul 13 20:48:12 mail postfix/smtpd[10687]: A44093FFF4: client=localhost[127.0.0.1] > Jul 13 20:48:12 mail postfix/cleanup[10656]: A44093FFF4: message-id= > Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: from=, size=933, nrcpt=1 (queue active) > Jul 13 20:48:12 mail amavis[9530]: (09530-14) Passed CLEAN {RelayedInternal}, LOCAL [192.168.1.253]:65462 -> , Queue-ID: E31B13FFF3, Message-ID: , mail_id: lnzQpKxIXYKy, Hits: -0.002, size: 316, queued_as: A44093FFF4, 2809 ms > Jul 13 20:48:12 mail postfix/smtp[10658]: E31B13FFF3: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=2.9, delays=0.03/0.01/0.02/2.8, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as A44093FFF4) > Jul 13 20:48:12 mail postfix/qmgr[10476]: E31B13FFF3: removed > Jul 13 20:48:12 mail dovecot: lda(test at yugi.us): msgid=: saved mail to INBOX > Jul 13 20:48:12 mail postfix/pipe[10664]: A44093FFF4: to=, relay=dovecot, delay=0.18, delays=0.03/0.01/0/0.14, dsn=2.0.0, status=sent (delivered via dovecot service) > Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: removed Dovecot delivery does not look at aliases. > Postfix config: > ... > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, > mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, > hash:/var/lib/mailman/data/virtual-mailman Adding virtual_alias_domains = yugi.us may help if yugi.us is not a virtual_mailbox_domain, but it may not and if it does help, it may break delivery to non-mailman addresses @yugi.us. If yugi.us is a virtual_mailbox_domain, i.e. is in mysql:/etc/postfix/mysql_virtual_domains_maps.cf and can't be removed, you may need to use the method at to generate transport maps to the local: transport, or you could possibly use some other domain which is not a virtual_mailbox_domain for your list mail. Note that all of this is because of using the Dovecot LDA as virtual_transport. The default Postfix virtual transport will use virtual_alias_maps for virtual_mailbox_domains. > virtual_gid_maps = static:8 > virtual_mailbox_base = /var/vmail > virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, > mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf > virtual_transport = dovecot > virtual_uid_maps = static:150 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mailinglist at samsi.us Thu Jul 14 12:35:27 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Thu, 14 Jul 2016 09:35:27 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <57871B6A.6030200@msapiro.net> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> Message-ID: yugi at us is currently a virtual mailbox. It can be removed though, should I? > On Jul 13, 2016, at 9:56 PM, Mark Sapiro wrote: > > On 07/13/2016 09:18 PM, Caesar Samsi wrote: >> [including list] >> >> The log for an inbound email to test at yugi.us list >> >> Jul 13 20:48:09 mail postfix/smtpd[10666]: connect from macpro[192.168.1.253] >> Jul 13 20:48:09 mail postfix/smtpd[10666]: Anonymous TLS connection established from macpro[192.168.1.253]: TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) >> Jul 13 20:48:09 mail postfix/smtpd[10666]: E31B13FFF3: client=macpro[192.168.1.253], sasl_method=PLAIN, sasl_username=caesar at samsi.us >> Jul 13 20:48:09 mail postfix/cleanup[10656]: E31B13FFF3: message-id= >> Jul 13 20:48:09 mail postfix/qmgr[10476]: E31B13FFF3: from=, size=316, nrcpt=1 (queue active) >> Jul 13 20:48:10 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1] >> Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1] >> Jul 13 20:48:11 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1] >> Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1] >> Jul 13 20:48:12 mail postfix/smtpd[10687]: connect from localhost[127.0.0.1] >> Jul 13 20:48:12 mail postfix/smtpd[10687]: A44093FFF4: client=localhost[127.0.0.1] >> Jul 13 20:48:12 mail postfix/cleanup[10656]: A44093FFF4: message-id= >> Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: from=, size=933, nrcpt=1 (queue active) >> Jul 13 20:48:12 mail amavis[9530]: (09530-14) Passed CLEAN {RelayedInternal}, LOCAL [192.168.1.253]:65462 -> , Queue-ID: E31B13FFF3, Message-ID: , mail_id: lnzQpKxIXYKy, Hits: -0.002, size: 316, queued_as: A44093FFF4, 2809 ms >> Jul 13 20:48:12 mail postfix/smtp[10658]: E31B13FFF3: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=2.9, delays=0.03/0.01/0.02/2.8, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as A44093FFF4) >> Jul 13 20:48:12 mail postfix/qmgr[10476]: E31B13FFF3: removed >> Jul 13 20:48:12 mail dovecot: lda(test at yugi.us): msgid=: saved mail to INBOX >> Jul 13 20:48:12 mail postfix/pipe[10664]: A44093FFF4: to=, relay=dovecot, delay=0.18, delays=0.03/0.01/0/0.14, dsn=2.0.0, status=sent (delivered via dovecot service) >> Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: removed > > > Dovecot delivery does not look at aliases. > >> Postfix config: >> > ... >> virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, >> mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, >> hash:/var/lib/mailman/data/virtual-mailman > > Adding > > virtual_alias_domains = yugi.us > > may help if yugi.us is not a virtual_mailbox_domain, but it may not and > if it does help, it may break delivery to non-mailman addresses @yugi.us. > > If yugi.us is a virtual_mailbox_domain, i.e. is in > mysql:/etc/postfix/mysql_virtual_domains_maps.cf and can't be removed, > you may need to use the method at to > generate transport maps to the local: transport, or you could possibly > use some other domain which is not a virtual_mailbox_domain for your > list mail. > > Note that all of this is because of using the Dovecot LDA as > virtual_transport. The default Postfix virtual transport will use > virtual_alias_maps for virtual_mailbox_domains. > > >> virtual_gid_maps = static:8 >> virtual_mailbox_base = /var/vmail >> virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf >> virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, >> mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf >> virtual_transport = dovecot >> virtual_uid_maps = static:150 > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From ginesgb at gmail.com Thu Jul 14 07:49:00 2016 From: ginesgb at gmail.com (Gines Granados Bayona) Date: Thu, 14 Jul 2016 13:49:00 +0200 Subject: [Mailman-Users] Problems with Mail Delivery Message-ID: Hello, good to everyone, I sent the requested information and thanks very much mark at msapiro.net. I have two users , one local and one external The two are different in multiple subdomain, one of them a local subdomain example. rancid. email.company.com email.company.com In local in this case would be rancid. email.company.com, have registered this machine with this name and have made the installation mailman with postfix, and have observed the log, it tries to send email both local and external domain account but do not get sent email. User ginesgb is a user of an external server email.company.com and the other user is local. I send you the information you are requesting me, and plus a diagram, Greeting and thank you very much From jason at fayre.me Thu Jul 14 15:07:10 2016 From: jason at fayre.me (Jason Fayre) Date: Thu, 14 Jul 2016 15:07:10 -0400 Subject: [Mailman-Users] searchable archive options for cpanel server Message-ID: <095601d1de02$ed357720$c7a06560$@fayre.me> Hi, I really wish I didn't need to ask this, but alas, I do. We have a server running cPanel that hosts around 200 mailing lists. We really want to have searchable archives. If I install the mailman htdig patches, cPanel won't support us. Other than not using cPanel, what are other folks doing:? I know we have the option of using mailarchive.org, but we would like to keep the archives internal if possible. Any suggestions would be appreciated! From mark at msapiro.net Thu Jul 14 15:30:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 Jul 2016 12:30:12 -0700 Subject: [Mailman-Users] searchable archive options for cpanel server In-Reply-To: <095601d1de02$ed357720$c7a06560$@fayre.me> References: <095601d1de02$ed357720$c7a06560$@fayre.me> Message-ID: <5787E844.3030402@msapiro.net> On 07/14/2016 12:07 PM, Jason Fayre wrote: > > We have a server running cPanel that hosts around 200 mailing lists. We > really want to have searchable archives. If I install the mailman htdig > patches, cPanel won't support us. And what Mailman support do you currently get from cPanel that you'd be giving up? Or do you mean that if you patch any piece, they won't support anything including stuff you haven't touched? > Other than not using cPanel, what are other folks doing:? I know we have the > option of using mailarchive.org, but we would like to keep the archives > internal if possible. If by 'internal' you mean private as opposed to public you are fairly limited. For public archives, you can use the site: and inurl: Google search options, e.g. add site:mail.python.org inurl:mailman-users to your Google search terms to search this list. See . You can install local search engines such as htdig on your server without the htdig integration patches. The search form would be a non-Mailman web page rather than being integrated with Mailman's archive pages, but you wouldn't need to patch Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dandrews at visi.com Thu Jul 14 16:32:07 2016 From: dandrews at visi.com (David Andrews) Date: Thu, 14 Jul 2016 15:32:07 -0500 Subject: [Mailman-Users] searchable archive options for cPanel server In-Reply-To: <5787E844.3030402@msapiro.net> References: <095601d1de02$ed357720$c7a06560$@fayre.me> <5787E844.3030402@msapiro.net> Message-ID: At 02:30 PM 7/14/2016, Mark Sapiro wrote: >On 07/14/2016 12:07 PM, Jason Fayre wrote: > > > > We have a server running cPanel that hosts around 200 mailing lists. We > > really want to have searchable archives. If I install the mailman htdig > > patches, cPanel won't support us. > > >And what Mailman support do you currently get from cPanel that you'd be >giving up? Or do you mean that if you patch any piece, they won't >support anything including stuff you haven't touched? He means all cPanel support, not just Mailman! From mark at msapiro.net Thu Jul 14 18:51:11 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 Jul 2016 15:51:11 -0700 Subject: [Mailman-Users] Problems with Mail Delivery In-Reply-To: References: Message-ID: <5788175F.20805@msapiro.net> On 07/14/2016 04:49 AM, Gines Granados Bayona wrote: > I have two users , one local and one external > The two are different in multiple subdomain, one of them a local subdomain > example. > rancid.email.company.com email.company.com > > > > In local in this case would be rancid.email.company.com, have registered > this machine with this name and have made the installation mailman with > postfix, and have observed the log, it tries to send email both local and > external domain account but do not get sent email. > > User ginesgb is a user of an external server email.company.com and the > other user is local. You have to teach Postfix on rancid.email.company.com to relay mail for users not local on rancid.email.company.com to email.company.com. This is a Postfix configuration issue beyond the scope of this list. Alternatively, You can tell Mailman to deliver all outgoing mail to the Postfix on email.company.com by setting SMTPHOST = 'email.company.com' in mm_cfg.py on the Mailman host. One other thing is in the postconf -n you sent in the post I rejected because of it's disclaimer language, you show recipient_delimiter = - There are various things in Mailman that want recipient_delimiter = + See and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 14 19:00:08 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 Jul 2016 16:00:08 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> Message-ID: <57881978.4010606@msapiro.net> On 07/14/2016 09:35 AM, Caesar Samsi wrote: > yugi at us is currently a virtual mailbox. It can be removed though, should I? Yes, and in Postfix main.cf, add virtual_alias_domains = yugi.us and ensure you have hash:/var/lib/mailman/data/aliases in alias_maps and hash:/var/lib/mailman/data/virtual-mailman in virtual_alias_maps and in mm_cfg.py MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us'] -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 14 22:40:32 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 Jul 2016 19:40:32 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> <57881978.4010606@msapiro.net> Message-ID: <57884D20.1020302@msapiro.net> On 07/14/2016 04:47 PM, Caesar Samsi wrote: > > Done the above and attempted to send to test at yugi.us, results are weird: > > RETURNED EMAIL: > > This is the mail system at host mail.samsi.us. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > : Host or domain name not found. Name service error for name=mail > type=AAAA: Host not found > Reporting-MTA: dns; mail.samsi.us > X-Postfix-Queue-ID: 03B813FFFD > X-Postfix-Sender: rfc822; caesar at samsi.us > Arrival-Date: Thu, 14 Jul 2016 16:39:29 -0700 (PDT) > > Final-Recipient: rfc822; test at mail > Original-Recipient: rfc822;test at yugi.us > Action: failed > Status: 5.4.4 > Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error > for name=mail type=AAAA: Host not found > > From: Caesar Samsi > Date: July 14, 2016 at 4:39:25 PM PDT > To: test at yugi.us > Subject: test > > > test > > POSTFIX LOG (not sure why yugi.us is converted to mail) Possibly because virtual_alias_maps maps 'test at yugi.us' to 'test' and postfix defaults append_at_myorigin to yes and myorigin in /etc/hostname is 'mail' You could try adding VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' in mm_cfg.py and running Mailman's 'bin/genaliases'. That may help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mailinglist at samsi.us Thu Jul 14 19:47:24 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Thu, 14 Jul 2016 16:47:24 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <57881978.4010606@msapiro.net> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> <57881978.4010606@msapiro.net> Message-ID: > On Jul 14, 2016, at 4:00 PM, Mark Sapiro wrote: > > On 07/14/2016 09:35 AM, Caesar Samsi wrote: >> yugi at us is currently a virtual mailbox. It can be removed though, should I? > > > Yes, and in Postfix main.cf, add > > virtual_alias_domains = yugi.us > > and ensure you have hash:/var/lib/mailman/data/aliases in alias_maps and > hash:/var/lib/mailman/data/virtual-mailman in virtual_alias_maps > > and in mm_cfg.py > > MTA = 'Postfix' > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us'] > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Done the above and attempted to send to test at yugi.us , results are weird: RETURNED EMAIL: This is the mail system at host mail.samsi.us . I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system : Host or domain name not found. Name service error for name=mail type=AAAA: Host not found Reporting-MTA: dns; mail.samsi.us X-Postfix-Queue-ID: 03B813FFFD X-Postfix-Sender: rfc822; caesar at samsi.us Arrival-Date: Thu, 14 Jul 2016 16:39:29 -0700 (PDT) Final-Recipient: rfc822; test at mail Original-Recipient: rfc822;test at yugi.us Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=mail type=AAAA: Host not found From: Caesar Samsi > Date: July 14, 2016 at 4:39:25 PM PDT To: test at yugi.us Subject: test test POSTFIX LOG (not sure why yugi.us is converted to mail) Jul 14 16:39:29 mail postfix/qmgr[25985]: 03B813FFFD: from=, size=715, nrcpt=1 (queue active) Jul 14 16:39:29 mail amavis[25725]: (25725-01) Passed CLEAN {RelayedOutbound}, LOCAL [192.168.1.253]:58481 -> , Queue-ID: 87D173FFFC, Message-ID: <2A803142-28A7-4639-BE54-454800EA7FA8 at samsi.us>, mail_id: Be3nxwAFFqzO, Hits: 0.728, size: 306, queued_as: 03B813FFFD, 2489 ms Jul 14 16:39:29 mail postfix/smtp[26005]: 87D173FFFC: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=2.6, delays=0.07/0.04/0.04/2.5, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 03B813FFFD) Jul 14 16:39:29 mail postfix/qmgr[25985]: 87D173FFFC: removed Jul 14 16:39:29 mail postfix/smtp[26011]: 03B813FFFD: to=, relay=none, delay=0.09, delays=0.04/0.04/0.02/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name=mail type=AAAA: Host not found) Jul 14 16:39:29 mail postfix/cleanup[26003]: 243913FFFC: message-id=<20160714233929.243913FFFC at mail.samsi.us> Jul 14 16:39:29 mail postfix/qmgr[25985]: 243913FFFC: from=<>, size=2619, nrcpt=1 (queue active) Jul 14 16:39:29 mail postfix/bounce[26012]: 03B813FFFD: sender non-delivery notification: 243913FFFC Jul 14 16:39:29 mail postfix/qmgr[25985]: 03B813FFFD: removed mm_cfg.py: # -*- python -*- # Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA # 02110-1301 USA """This is the module which takes your site-specific settings. From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example.""" ####################################################### # Here's where we get the distributed defaults. # from Defaults import * ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # #------------------------------------------------------------- # The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'yugi.us' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'mail.samsi.us' #------------------------------------------------------------- # Required when setting any of its arguments. #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'en' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.Exim4.Debian or # /usr/share/mailman/postfix-to-mailman.py) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. MTA='Postfix' SMTPHOST = 'localhost' SMTPPORT = 25 #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us'] POSTFIX (postconf -n) alias_maps = hash:/etc/aliases,hash:/var/lib/mailman/data/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix content_filter = amavis:[127.0.0.1]:10024 disable_vrfy_command = yes dovecot_destination_recipient_limit = 1 enable_original_recipient = no header_checks = regexp:/etc/postfix/header_checks inet_interfaces = all mailbox_size_limit = 0 mailman_destination_recipient_limit = 1 maximal_backoff_time = 8000s maximal_queue_lifetime = 7d minimal_backoff_time = 1000s mydestination = myhostname = mail.samsi.us mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mynetworks_style = host myorigin = /etc/hostname readme_directory = no recipient_delimiter = + relay_domains = mail.samsi.us smtp_helo_timeout = 60s smtpd_banner = $myhostname ESMTP $mail_name smtpd_delay_reject = yes smtpd_hard_error_limit = 12 smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, reject_unknown_helo_hostname, reject_non_fqdn_hostname, reject_invalid_hostname smtpd_recipient_limit = 16 smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_invalid_hostname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_rbl_client sbl.spamhaus.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client dul.dnsbl.sorbs.net smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_soft_error_limit = 3 smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_exclude_ciphers = aNULL, eNULL, EXPORT, DES, RC4, MD5, PSK, aECDH, EDH-DSS-DES-CBC3-SHA, EDH-RSA-DES-CDC3-SHA, KRB5-DE5, CBC3-SHA smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_loglevel = 1 smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3 smtpd_tls_received_header = yes smtpd_tls_security_level = may smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 450 virtual_alias_domains = yugi.us virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, hash:/var/lib/mailman/data/virtual-mailman virtual_gid_maps = static:8 virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf virtual_transport = dovecot virtual_uid_maps = static:150 From VxMr at pge.com Fri Jul 15 12:34:18 2016 From: VxMr at pge.com (Montanez, Victor) Date: Fri, 15 Jul 2016 16:34:18 +0000 Subject: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action Message-ID: Can the list owners send a command via email to unsubscribe users of a list that will NOT cause a confirmation email to be generated to the subscribers? We want to send an email to mailman to remove subscribers without requiring confirmation from the subscribed users. All settings I have tried still generate a confirmation email and subscriber interaction is required. Thanks in advance From mark at msapiro.net Fri Jul 15 13:55:54 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 10:55:54 -0700 Subject: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action In-Reply-To: References: Message-ID: <578923AA.2080505@msapiro.net> On 07/15/2016 09:34 AM, Montanez, Victor wrote: > Can the list owners send a command via email to unsubscribe users of > a list that will NOT cause a confirmation email to be generated to > the subscribers? Only if the admin knows the user's list password. If so, the admin can send the command unsubscribe users_password address=user at example.com to the list's -request address, but it must be the user's list password. No other password will work. A possible alternative is to set the list's Privacy options... -> Subscription rules -> unsubscribe_policy to yes and send unsubscribe address=user at example.com to the list's -request address. This will result in the unsubscribe (all unsubscribes) being held for admin approval, but the admin can't approve the held unsubscribe by email, so tha probably won't help. > We want to send an email to mailman to remove subscribers without > requiring confirmation from the subscribed users. All settings I have > tried still generate a confirmation email and subscriber interaction > is required. You could consider patching Mailman/Commands/cmd_unsubscribe.py to accept the list admin password or some other secret as an alternate to the user's password. I think that's the only way. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From VxMr at pge.com Fri Jul 15 14:08:32 2016 From: VxMr at pge.com (Montanez, Victor) Date: Fri, 15 Jul 2016 18:08:32 +0000 Subject: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action In-Reply-To: <578923AA.2080505@msapiro.net> References: <578923AA.2080505@msapiro.net> Message-ID: Hello Mark, For the possible alternative you mention below: If we do set up the unsubscribe policy to "yes" and in the "unsubscribe MODERATORPASSWD address=user at example" command we include the moderator/owner password would that accomplish the removal of the user without confirmation? ************* A possible alternative is to set the list's Privacy options... -> Subscription rules -> unsubscribe_policy to yes and send unsubscribe address=user at example.com to the list's -request address. This will result in the unsubscribe (all unsubscribes) being held for admin approval, but the admin can't approve the held unsubscribe by email, so tha probably won't help. *********** -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+vxmr=pge.com at python.org] On Behalf Of Mark Sapiro Sent: Friday, July 15, 2016 10:56 AM To: mailman-users at python.org Subject: Re: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action This is an EXTERNAL EMAIL. Stop and think before clicking links or opening attachments. ************************************* On 07/15/2016 09:34 AM, Montanez, Victor wrote: > Can the list owners send a command via email to unsubscribe users of a > list that will NOT cause a confirmation email to be generated to the > subscribers? Only if the admin knows the user's list password. If so, the admin can send the command unsubscribe users_password address=user at example.com to the list's -request address, but it must be the user's list password. No other password will work. A possible alternative is to set the list's Privacy options... -> Subscription rules -> unsubscribe_policy to yes and send unsubscribe address=user at example.com to the list's -request address. This will result in the unsubscribe (all unsubscribes) being held for admin approval, but the admin can't approve the held unsubscribe by email, so tha probably won't help. > We want to send an email to mailman to remove subscribers without > requiring confirmation from the subscribed users. All settings I have > tried still generate a confirmation email and subscriber interaction > is required. You could consider patching Mailman/Commands/cmd_unsubscribe.py to accept the list admin password or some other secret as an alternate to the user's password. I think that's the only way. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_mailman_listinfo_mailman-2Dusers&d=CwICAg&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=CNBJ5WQxVRyGeDTLL7hLtA&m=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog&s=AubQGks4ZJkjdlyBIYqG4nLXuMXQcG7k8pCkHT4kf3M&e= Mailman FAQ: https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.list.org_x_AgA3&d=CwICAg&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=CNBJ5WQxVRyGeDTLL7hLtA&m=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog&s=-9PsRNCXE-lpFiSN5nauFUClTOMrDOxFfjn6soHHCo4&e= Security Policy: https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.list.org_x_QIA9&d=CwICAg&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=CNBJ5WQxVRyGeDTLL7hLtA&m=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog&s=pms8W_zjLSJyKbyvxovKZ-i6g8aajS3ZyPz6AiZRE5c&e= Searchable Archives: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mail-2Darchive.com_mailman-2Dusers-2540python.org_&d=CwICAg&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=CNBJ5WQxVRyGeDTLL7hLtA&m=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog&s=L0ghPUhHtLQiGgA9nMI9gC2O0J_VmJR1alZO-gJ_vEo&e= Unsubscribe: https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.python.org_mailman_options_mailman-2Dusers_vxmr-2540pge.com&d=CwICAg&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=CNBJ5WQxVRyGeDTLL7hLtA&m=S71mkh92Tx-4_18SmPaB3jGVR259jGrWUejyLX2YJog&s=dzAvYA05U9p7gK5ayq91KnbwWOwUdybtZcJreMbNt5E&e= From raj at mischievous.us Fri Jul 15 16:45:55 2016 From: raj at mischievous.us (Richard Johnson) Date: Fri, 15 Jul 2016 13:45:55 -0700 Subject: [Mailman-Users] DMARC problems Message-ID: I've been running a number of mailing lists for quite a while and never noticed any problems until I setup one which has some yahoo and hotmail addresses on it. Now I have to deal with the DMARC problem. :( Looking at: https://wiki.list.org/DEV/DMARC I see it says: > In 2.1.16 a from_is_list feature was implemented which if enabled by a site configuration option would offer a list admin the ability to either: > > ? Rewrite (Munge) the From: header with the posters name 'via the list' and the list's address and merge the poster's address into Reply-To: or > ? Wrap the message as a message/rfc822 sub-part in a MIME format outer message with From: and Reply-To: as above. I'm running 2.1.17 and the only thing I see which seems related to this is the "anonymous list" option under General Options. Is this what's being referred to here, or is there some other "site configuration" (i.e., per-site configuration?) method somewhere? /raj From mark at msapiro.net Fri Jul 15 17:37:23 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 14:37:23 -0700 Subject: [Mailman-Users] DMARC problems In-Reply-To: References: Message-ID: <57895793.6010204@msapiro.net> On 07/15/2016 01:45 PM, Richard Johnson wrote: > >> In 2.1.16 a from_is_list feature was implemented ... > I'm running 2.1.17 and the only thing I see which seems related to this is the "anonymous list" option under General Options. Is this what's being referred to here, or is there some other "site configuration" (i.e., per-site configuration?) method somewhere? You really should upgrade. There have been ongoing changes in this area through 2.1.22. See . However, to answer your question, in 2.1.16 and 2.1.17 the from_is_list feature had to be enabled by putting ALLOW_FROM_IS_LIST = Yes 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 Fri Jul 15 17:41:14 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 14:41:14 -0700 Subject: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action In-Reply-To: References: <578923AA.2080505@msapiro.net> Message-ID: <5789587A.10101@msapiro.net> On 07/15/2016 11:08 AM, Montanez, Victor wrote: > Hello Mark, > > For the possible alternative you mention below: > > If we do set up the unsubscribe policy to "yes" and in the "unsubscribe MODERATORPASSWD address=user at example" command we include the moderator/owner password would that accomplish the removal of the user without confirmation? No. The only password that has any meaning in that command is the user's list password. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From VxMr at pge.com Fri Jul 15 17:59:17 2016 From: VxMr at pge.com (Montanez, Victor) Date: Fri, 15 Jul 2016 21:59:17 +0000 Subject: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action In-Reply-To: <5789587A.10101@msapiro.net> References: <578923AA.2080505@msapiro.net> <5789587A.10101@msapiro.net> Message-ID: Thank you for the confirmation Mark. -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, July 15, 2016 2:41 PM To: Montanez, Victor; mailman-users at python.org Subject: Re: [Mailman-Users] Mailman 2.1.2 unsubscribe without confirmation action This is an EXTERNAL EMAIL. Stop and think before clicking links or opening attachments. ************************************* On 07/15/2016 11:08 AM, Montanez, Victor wrote: > Hello Mark, > > For the possible alternative you mention below: > > If we do set up the unsubscribe policy to "yes" and in the "unsubscribe MODERATORPASSWD address=user at example" command we include the moderator/owner password would that accomplish the removal of the user without confirmation? No. The only password that has any meaning in that command is the user's list password. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From raj at mischievous.us Fri Jul 15 18:15:06 2016 From: raj at mischievous.us (Richard Johnson) Date: Fri, 15 Jul 2016 15:15:06 -0700 Subject: [Mailman-Users] DMARC problems In-Reply-To: <57895793.6010204@msapiro.net> References: <57895793.6010204@msapiro.net> Message-ID: <66AC2320-63AE-4EDC-9F6C-3B6454EE3657@mischievous.us> I have now upgraded to 2.1.22. Thanks! /raj > On Jul 15, 2016, at 2:37 PM, Mark Sapiro wrote: > > On 07/15/2016 01:45 PM, Richard Johnson wrote: >> >>> In 2.1.16 a from_is_list feature was implemented ... > >> I'm running 2.1.17 and the only thing I see which seems related to this is the "anonymous list" option under General Options. Is this what's being referred to here, or is there some other "site configuration" (i.e., per-site configuration?) method somewhere? > > > You really should upgrade. There have been ongoing changes in this area > through 2.1.22. See > . > However, to answer your question, in 2.1.16 and 2.1.17 the from_is_list > feature had to be enabled by putting > > ALLOW_FROM_IS_LIST = Yes > > in mm_cfg.py. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://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: https://mail.python.org/mailman/options/mailman-users/raj%40mischievous.us From mailinglist at samsi.us Fri Jul 15 19:16:11 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Fri, 15 Jul 2016 16:16:11 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <57895EEC.1080501@msapiro.net> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> <57881978.4010606@msapiro.net> <489C64D0-3B95-4941-8C2E-A96A9DD9C7F1@samsi.us> <57895EEC.1080501@msapiro.net> Message-ID: <100E01F0-6CF3-4B11-8D10-0CF111FE0859@samsi.us> Sorry, fixed below ... > On Jul 15, 2016, at 3:08 PM, Mark Sapiro wrote: > > On 07/15/2016 11:03 AM, Caesar Samsi wrote: >> Results below, it seems to still translate yugi.us to mail >> >> POSTFIX_MAILMAN_LOCAL_DOMAIN = 'localhost' > > > No! > > VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' > > and then run Mailman's bin/genaliases and verify that the entries in > /var/lib/mailman/data/virtual-mailman are like > > test at yugi.us test at localhost > ... > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Result: : Host or domain name not found. Name service error for name=localhost type=AAAA: Host not found Reporting-MTA: dns; mail.samsi.us X-Postfix-Queue-ID: 27A383FFFD X-Postfix-Sender: rfc822; caesar at samsi.us Arrival-Date: Fri, 15 Jul 2016 16:11:39 -0700 (PDT) Final-Recipient: rfc822; test at localhost Original-Recipient: rfc822;test at yugi.us Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=localhost type=AAAA: Host not found From: Caesar Samsi > Subject: test Date: July 15, 2016 at 4:11:35 PM PDT To: test at yugi.us test mm_cfg.py ======== # -*- python -*- # Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA # 02110-1301 USA """This is the module which takes your site-specific settings. From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example.""" ####################################################### # Here's where we get the distributed defaults. # from Defaults import * ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # #------------------------------------------------------------- # The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'yugi.us' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'mail.samsi.us' #------------------------------------------------------------- # Required when setting any of its arguments. #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'en' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.Exim4.Debian or # /usr/share/mailman/postfix-to-mailman.py) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. MTA='Postfix' SMTPHOST = 'localhost' SMTPPORT = 25 #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us'] VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' virtual-mailman ============ # This file is generated by Mailman, and is kept in sync with the binary hash # file virtual-mailman.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you # know what you're doing, and can keep the two files properly in sync. If you # screw it up, you're on your own. # # Note that you should already have this virtual domain set up properly in # your Postfix installation. See README.POSTFIX for details. # LOOP ADDRESSES START mailman-loop at yugi.us mailman-loop at localhost # LOOP ADDRESSES END # STANZA START: test # CREATED: Fri Jul 15 16:09:03 2016 test at yugi.us test at localhost test-admin at yugi.us test-admin at localhost test-bounces at yugi.us test-bounces at localhost test-confirm at yugi.us test-confirm at localhost test-join at yugi.us test-join at localhost test-leave at yugi.us test-leave at localhost test-owner at yugi.us test-owner at localhost test-request at yugi.us test-request at localhost test-subscribe at yugi.us test-subscribe at localhost test-unsubscribe at yugi.us test-unsubscribe at localhost # STANZA END: test From mark at msapiro.net Fri Jul 15 19:49:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 16:49:46 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <100E01F0-6CF3-4B11-8D10-0CF111FE0859@samsi.us> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> <57881978.4010606@msapiro.net> <489C64D0-3B95-4941-8C2E-A96A9DD9C7F1@samsi.us> <57895EEC.1080501@msapiro.net> <100E01F0-6CF3-4B11-8D10-0CF111FE0859@samsi.us> Message-ID: <5789769A.8050408@msapiro.net> On 07/15/2016 04:16 PM, Caesar Samsi wrote: > Sorry, fixed below ... ... > Result: > > : Host or domain name not found. Name service error for > name=localhost type=AAAA: Host not found You need localhost in mydestination in Postfix (it's probably there by default) and 127.0.0.1 localhost in /etc/hosts. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 15 20:00:10 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 17:00:10 -0700 Subject: [Mailman-Users] DMARC problems In-Reply-To: <66AC2320-63AE-4EDC-9F6C-3B6454EE3657@mischievous.us> References: <57895793.6010204@msapiro.net> <66AC2320-63AE-4EDC-9F6C-3B6454EE3657@mischievous.us> Message-ID: <5789790A.9060007@msapiro.net> On 07/15/2016 03:15 PM, Richard Johnson wrote: > I have now upgraded to 2.1.22. Thanks! And in 2.1.22, dmarc_moderation_action is generally preferable to from_is_list because it is only applied to those post that need it. See Privacy options... -> Sender filters -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mailinglist at samsi.us Fri Jul 15 20:12:01 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Fri, 15 Jul 2016 17:12:01 -0700 Subject: [Mailman-Users] MailMan won't send list emails In-Reply-To: <5789769A.8050408@msapiro.net> References: <12F7BE03-6A6F-477D-83A5-574977634E38@samsi.us> <1DDF63D8-C4DF-4906-A512-F07B3DC93234@samsi.us> <5786965E.3030906@msapiro.net> <538BC868-C28E-47B4-B494-FE4A0EFEEF6F@samsi.us> <5786FEBC.9040704@msapiro.net> <76301960-C6AE-4E20-A1E7-32BBC4567F30@samsi.us> <57871B6A.6030200@msapiro.net> <57881978.4010606@msapiro.net> <489C64D0-3B95-4941-8C2E-A96A9DD9C7F1@samsi.us> <57895EEC.1080501@msapiro.net> <100E01F0-6CF3-4B11-8D10-0CF111FE0859@samsi.us> <5789769A.8050408@msapiro.net> Message-ID: It is ALIVE !!! :-) Now on to creating more lists. Many Thanks Mark! > On Jul 15, 2016, at 4:49 PM, Mark Sapiro wrote: > > On 07/15/2016 04:16 PM, Caesar Samsi wrote: >> Sorry, fixed below ... > ... >> Result: >> >> : Host or domain name not found. Name service error for >> name=localhost type=AAAA: Host not found > > > You need localhost in mydestination in Postfix (it's probably there by > default) and > > 127.0.0.1 localhost > > in /etc/hosts. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From raj at mischievous.us Fri Jul 15 20:22:58 2016 From: raj at mischievous.us (Richard Johnson) Date: Fri, 15 Jul 2016 17:22:58 -0700 Subject: [Mailman-Users] DMARC problems In-Reply-To: <5789790A.9060007@msapiro.net> References: <57895793.6010204@msapiro.net> <66AC2320-63AE-4EDC-9F6C-3B6454EE3657@mischievous.us> <5789790A.9060007@msapiro.net> Message-ID: <222D1C14-413F-4FB8-8B7F-6529B394F074@mischievous.us> This is described as: > Action to take when anyone posts to the list from a domain with a DMARC Reject/Quarantine Policy. but the problem I'm getting is: https://help.yahoo.com/kb/postmaster/SLN7253.html which seems to be caused by the "From" address not matching the domain name wince the message was sent. I think in order to satisfy this, I need to simply apply "from_is_list"="Munge From". When I apply this along with "reply_goes_to_list"="This list", then the original sender's address appears in the "CC" list, which is ok, since most people just hit "reply" and not "reply all". I created a test list and played with it, looking at the SMTP interaction to verify that yahoo seems to think this is fine. /raj > On Jul 15, 2016, at 5:00 PM, Mark Sapiro wrote: > > On 07/15/2016 03:15 PM, Richard Johnson wrote: >> I have now upgraded to 2.1.22. Thanks! > > > And in 2.1.22, dmarc_moderation_action is generally preferable to > from_is_list because it is only applied to those post that need it. > > See Privacy options... -> Sender filters > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 15 21:31:47 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2016 18:31:47 -0700 Subject: [Mailman-Users] DMARC problems In-Reply-To: <222D1C14-413F-4FB8-8B7F-6529B394F074@mischievous.us> References: <57895793.6010204@msapiro.net> <66AC2320-63AE-4EDC-9F6C-3B6454EE3657@mischievous.us> <5789790A.9060007@msapiro.net> <222D1C14-413F-4FB8-8B7F-6529B394F074@mischievous.us> Message-ID: <57898E83.4050607@msapiro.net> On 07/15/2016 05:22 PM, Richard Johnson wrote: > This is described as: > >> Action to take when anyone posts to the list from a domain with a >> DMARC Reject/Quarantine Policy. > > but the problem I'm getting is: > > https://help.yahoo.com/kb/postmaster/SLN7253.html > > which seems to be caused by the "From" address not matching the > domain name wince the message was sent. That link discusses mail rejected by Yahoo which may or may not have anything to do with DMARC. The typical DMARC issue is mail From: a yahoo.com user is bounced by multiple recipient ISPs including, but not limited to Yahoo. > I think in order to satisfy > this, I need to simply apply "from_is_list"="Munge From". When I > apply this along with "reply_goes_to_list"="This list", then the > original sender's address appears in the "CC" list, which is ok, > since most people just hit "reply" and not "reply all". I created a > test list and played with it, looking at the SMTP interaction to > verify that yahoo seems to think this is fine. I think you'll find that setting from_is_list to No and dmarc_moderation_action to Munge From and possibly also setting dmarc_quarantine_moderation_action to Yes will also work, but will only apply the Munge From action to posts From: domains such as yahoo.com that publish DMARC p=reject policies and optionally domains that publish p=quarantine. As far as the original poster's address in Cc: is concerned, we try to make Munge From result in mail which will be dealt with by MUA reply and reply all the same as unmunged mail. Thus, if reply_goes_to_list is Poster, we put the original poster's address in Reply-To: so with compliant MUAs at least, 'reply' goes to the OP and 'reply-all' goes to the OP and the list address in To:. For reply_goes_to_list = This list, we put the OP's address in Cc: rather than Reply-To: so 'reply' will go to only the list, but 'reply all' will go to the list and the OP. In all cases, we want the OP's address somewhere in visible headers. Here are our goals (from comments in the handler that does this): # We need to do some things with the original From: if we've munged # it for DMARC mitigation. We have goals for this process which are # not completely compatible, so we do the best we can. Our goals are: # 1) as long as the list is not anonymous, the original From: address # should be obviously exposed, i.e. not just in a header that MUAs # don't display. # 2) the original From: address should not be in a comment or display # name in the new From: because it is claimed that multiple domains # in any fields in From: are indicative of spamminess. This means # it should be in Reply-To: or Cc:. # 3) the behavior of an MUA doing a 'reply' or 'reply all' should be # consistent regardless of whether or not the From: is munged. # Goal 3) implies sometimes the original From: should be in Reply-To: # and sometimes in Cc:, and even so, this goal won't be achieved in # all cases with all MUAs. In cases of conflict, the above ordering of # goals is priority order. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From g.aloitus at gmail.com Sat Jul 16 10:17:34 2016 From: g.aloitus at gmail.com (Teijo) Date: Sat, 16 Jul 2016 17:17:34 +0300 Subject: [Mailman-Users] From http to https Message-ID: <4d26720a-e023-a1f1-1af7-62cad51908df@gmail.com> Hello, I have Mailman 2.1.22 installed. Web pages are at addresses starting with http, and I'd like to move to https so that all content would be updated to use https. No need to change domain name. Is there any documentation for this (unfortunately I did not find)? Best, Teijo From mark at msapiro.net Sat Jul 16 11:06:31 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 16 Jul 2016 08:06:31 -0700 Subject: [Mailman-Users] From http to https In-Reply-To: <4d26720a-e023-a1f1-1af7-62cad51908df@gmail.com> References: <4d26720a-e023-a1f1-1af7-62cad51908df@gmail.com> Message-ID: <578A4D77.5040803@msapiro.net> On 07/16/2016 07:17 AM, Teijo wrote: > > I have Mailman 2.1.22 installed. Web pages are at addresses starting > with http, and I'd like to move to https so that all content would be > updated to use https. No need to change domain name. > > Is there any documentation for this (unfortunately I did not find)? See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From g.aloitus at gmail.com Sat Jul 16 18:27:07 2016 From: g.aloitus at gmail.com (Teijo) Date: Sun, 17 Jul 2016 01:27:07 +0300 Subject: [Mailman-Users] From http to https In-Reply-To: <578A4D77.5040803@msapiro.net> References: <4d26720a-e023-a1f1-1af7-62cad51908df@gmail.com> <578A4D77.5040803@msapiro.net> Message-ID: <229ca06c-97af-e67d-42b3-e7fad5e300d9@gmail.com> This was just what I needed, thank you! 16.7.2016, 18:06, Mark Sapiro kirjoitti: > On 07/16/2016 07:17 AM, Teijo wrote: >> I have Mailman 2.1.22 installed. Web pages are at addresses starting >> with http, and I'd like to move to https so that all content would be >> updated to use https. No need to change domain name. >> >> Is there any documentation for this (unfortunately I did not find)? > > See . > From odhiambo at gmail.com Mon Jul 18 06:17:02 2016 From: odhiambo at gmail.com (Odhiambo Washington) Date: Mon, 18 Jul 2016 13:17:02 +0300 Subject: [Mailman-Users] Error while searching the archives Message-ID: Hi everyone, I have a strange problem here. When I try a search on my list archives, I see this on the browser: Bug in Mailman version 2.1.22 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. And in the error log I see the details here ->: http://gw.kictanet.or.ke/~wash/error.txt Kindly advise what the problem could be. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From housley at vigilsec.com Mon Jul 18 03:57:20 2016 From: housley at vigilsec.com (Russ Housley) Date: Mon, 18 Jul 2016 03:57:20 -0400 Subject: [Mailman-Users] Support for Internationalized Domain Names and Email Addresses In-Reply-To: References: Message-ID: In August 2010, the IETF published the specifications for Internationalized Domain Names (IDNs) as RFCs 5890 through 5894. In February 2012, the IETF published the specifications for Email Address Internationalization (EAI) as RFC 6530. As far as I can tell, Mailman will not let me include an email address that uses IDN or EAI as a mail list recipient. Has anyone figure out how to use either one of these? Thanks in advance, Russ From mark at msapiro.net Mon Jul 18 20:36:29 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 18 Jul 2016 17:36:29 -0700 Subject: [Mailman-Users] Error while searching the archives In-Reply-To: References: Message-ID: <578D760D.5050408@msapiro.net> On 07/18/2016 03:17 AM, Odhiambo Washington wrote: > > I have a strange problem here. When I try a search on my list archives, I > see this on the browser: > > Bug in Mailman version 2.1.22 ... > And in the error log I see the details here ->: > http://gw.kictanet.or.ke/~wash/error.txt The traceback is > admin(46841): Traceback (most recent call last): > admin(46841): File "/usr/local/mailman/scripts/driver", line 117, in run_main > admin(46841): main() > admin(46841): File "/usr/local/mailman/Mailman/Cgi/mmsearch.py", line 213, in main > admin(46841): child = Popen(cmd, stdin=PIPE, stdout=PIPE) > admin(46841): File "/usr/local/lib/python2.7/subprocess.py", line 710, in __init__ > admin(46841): errread, errwrite) > admin(46841): File "/usr/local/lib/python2.7/subprocess.py", line 1335, in _execute_child > admin(46841): raise child_exception > admin(46841): OSError: [Errno 2] No such file or directory which says Popen can't execute cmd because of the Errno2, No such file or directory. cmd is whatever you have configured for HTDIG_HTSEARCH_PATH in mm_cfg.py. The default in Defaults.py is HTDIG_HTSEARCH_PATH = '/usr/local/bin/htsearch' Does HTDIG_HTSEARCH_PATH contain a path to the htdig htsearch program in your installation? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From odhiambo at gmail.com Tue Jul 19 04:56:36 2016 From: odhiambo at gmail.com (Odhiambo Washington) Date: Tue, 19 Jul 2016 11:56:36 +0300 Subject: [Mailman-Users] Error while searching the archives In-Reply-To: <578D760D.5050408@msapiro.net> References: <578D760D.5050408@msapiro.net> Message-ID: On 19 July 2016 at 03:36, Mark Sapiro wrote: > On 07/18/2016 03:17 AM, Odhiambo Washington wrote: > >> >> I have a strange problem here. When I try a search on my list archives, I >> see this on the browser: >> >> Bug in Mailman version 2.1.22 >> > ... > >> And in the error log I see the details here ->: >> http://gw.kictanet.or.ke/~wash/error.txt >> > > > The traceback is > > admin(46841): Traceback (most recent call last): >> admin(46841): File "/usr/local/mailman/scripts/driver", line 117, in >> run_main >> admin(46841): main() >> admin(46841): File "/usr/local/mailman/Mailman/Cgi/mmsearch.py", line >> 213, in main >> admin(46841): child = Popen(cmd, stdin=PIPE, stdout=PIPE) >> admin(46841): File "/usr/local/lib/python2.7/subprocess.py", line 710, >> in __init__ >> admin(46841): errread, errwrite) >> admin(46841): File "/usr/local/lib/python2.7/subprocess.py", line 1335, >> in _execute_child >> admin(46841): raise child_exception >> admin(46841): OSError: [Errno 2] No such file or directory >> > > which says Popen can't execute cmd because of the Errno2, No such file or > directory. > > cmd is whatever you have configured for HTDIG_HTSEARCH_PATH in mm_cfg.py. > The default in Defaults.py is > > HTDIG_HTSEARCH_PATH = '/usr/local/bin/htsearch' > > Does HTDIG_HTSEARCH_PATH contain a path to the htdig htsearch program in > your installation? In mm_cfg.py, I have: HTDIG_HTSEARCH_PATH = '/usr/local/www/cgi-bin/htsearch' I tried running it: root at gw:/usr/home/wash # /usr/local/www/cgi-bin/htsearch Enter value for words: walu Content-type: text/html htsearch error

ht://Dig error

htsearch detected an error. Please report this to the webmaster of this site by sending an e-mail to: unconfigured at htdig.searchengine.maintainer The error message is:

Unable to read word database file
'/usr/local/share/htdig/database/db.words.db'
Did you run htdig?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From mark at msapiro.net Tue Jul 19 14:38:10 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 11:38:10 -0700 Subject: [Mailman-Users] Error while searching the archives In-Reply-To: References: <578D760D.5050408@msapiro.net> Message-ID: On 07/19/2016 01:56 AM, Odhiambo Washington wrote: > > In mm_cfg.py, I have: > > HTDIG_HTSEARCH_PATH = '/usr/local/www/cgi-bin/htsearch' > > I tried running it: > > root at gw:/usr/home/wash # /usr/local/www/cgi-bin/htsearch > Enter value for words: walu > Content-type: text/html > > htsearch error > >

ht://Dig error

>

htsearch detected an error. Please report this to the > webmaster of this site by sending an e-mail to: > unconfigured at htdig.searchengine.maintainer > The error message is:

> 
> Unable to read word database file
> '/usr/local/share/htdig/database/db.words.db'
> Did you run htdig?
>
> That's good as far as it goes. Making it actually work from the command line is more complicated than that. It expects environment variables and POST data from the search form. Has this ever worked? If so, what did you do just prior to its stopping working? Have you made any changes and not restarted Mailman? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From MGraves at acog.org Mon Jul 18 12:59:02 2016 From: MGraves at acog.org (Mark Graves) Date: Mon, 18 Jul 2016 16:59:02 +0000 Subject: [Mailman-Users] Problems with Membership List and Extraneous Characters in URL Message-ID: I'm running Mailman version 2.1.21. On the web interface Membership Management/Membership List, if I use the Find member and get too many results to show on one screen, the lettered links at the top do not work correctly. The problem is an extraneous U. Here's an example: https://listserv.acog.org/mailman/admin/coding/u'https://listserv.acog.org/mailman/admin/coding/members?letter=b&findmember=acog.org' and here's the source from the link on the page: B   Is this a bug? I found someone else complaining about this in 2003, but nothing since. Any ideas? From odhiambo at gmail.com Tue Jul 19 14:58:26 2016 From: odhiambo at gmail.com (Odhiambo Washington) Date: Tue, 19 Jul 2016 21:58:26 +0300 Subject: [Mailman-Users] Error while searching the archives In-Reply-To: References: <578D760D.5050408@msapiro.net> Message-ID: On 19 July 2016 at 21:38, Mark Sapiro wrote: > On 07/19/2016 01:56 AM, Odhiambo Washington wrote: > > > > In mm_cfg.py, I have: > > > > HTDIG_HTSEARCH_PATH = '/usr/local/www/cgi-bin/htsearch' > > > > I tried running it: > > > > root at gw:/usr/home/wash # /usr/local/www/cgi-bin/htsearch > > Enter value for words: walu > > Content-type: text/html > > > > htsearch error > > > >

ht://Dig error

> >

htsearch detected an error. Please report this to the > > webmaster of this site by sending an e-mail to: > > unconfigured at htdig.searchengine.maintainer > > The error message is:

> > 
> > Unable to read word database file
> > '/usr/local/share/htdig/database/db.words.db'
> > Did you run htdig?
> >
> > > > > That's good as far as it goes. Making it actually work from the command > line is more complicated than that. It expects environment variables and > POST data from the search form. > > Has this ever worked? If so, what did you do just prior to its stopping > working? Have you made any changes and not restarted Mailman? > > I think it worked before. Can't tell for sure. The only change I have made recently is to have my URLs use https. I have just tried to run it again and I see this in the browser: ht://Dig error htsearch detected an error. Please report this to the webmaster of this site by sending an e-mail to: mailman at lists.kictanet.or.ke The error message is: Unable to read word database file '/usr/local/mailman/archives/private/kictanet/htdig/db.words.db' Did you run htdig? root at gw:/usr/home/wash # ls -al /usr/local/mailman/archives/private/kictanet/htdig/ total 770718 drwxrws--- 2 root mailman 512 Mar 1 02:19 . drwxrwsr-x 142 root mailman 7680 Jul 19 21:54 .. -rw-rw-r-- 1 mailman mailman 24576 Mar 1 02:19 db.docdb -rw-rw-r-- 1 mailman mailman 24576 Mar 1 02:19 db.docs.index -rw-rw-r-- 1 mailman mailman 24576 Mar 1 02:19 db.excerpts -rw-r--r-- 1 root mailman 3918 May 29 2013 kictanet.conf -rw-rw-r-- 1 root mailman 2228224 Mar 1 02:24 root2word.db -rw-rw-r-- 1 root mailman 0 Mar 2 02:19 rundig_last_run -rw-rw-r-- 1 root mailman 90112 Mar 1 02:24 synonyms.db -rw-rw-r-- 1 root mailman 786374656 Mar 1 02:24 word2root.db -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." From mark at msapiro.net Tue Jul 19 15:32:15 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Jul 2016 12:32:15 -0700 Subject: [Mailman-Users] Problems with Membership List and Extraneous Characters in URL In-Reply-To: References: Message-ID: On 07/18/2016 09:59 AM, Mark Graves wrote: > > and here's the source from the link on the page: > > B   > > Is this a bug? I found someone else complaining about this in 2003, but nothing since. It is a bug, just reported and fixed. See and . Thank you for the report. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From perry at piermont.com Tue Jul 19 17:10:05 2016 From: perry at piermont.com (Perry E. Metzger) Date: Tue, 19 Jul 2016 17:10:05 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? Message-ID: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> https://httpoxy.org/ seems to impact any python program (among many others) that runs under cgi. Does it cause trouble for mailman? What is a reasonable mitigation? Perry -- Perry E. Metzger perry at piermont.com From jimpop at gmail.com Tue Jul 19 17:25:00 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Tue, 19 Jul 2016 17:25:00 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> Message-ID: On Tue, Jul 19, 2016 at 5:10 PM, Perry E. Metzger wrote: > https://httpoxy.org/ seems to impact any python program (among many > others) that runs under cgi. Does it cause trouble for mailman? What > is a reasonable mitigation? If I understand the issue correctly (and admittedly It's kinda a new issue) this only affects proxied HTTP transactions, not HTTPS ones. Most mailman installations should be running HTTPS in order to protect user data, if not now is a good time to do so. It's worth pointing out that if you are using nginx with mailman that this only affects you if you are using fastcgi. It does not seem to affect you if you are using nginx+uwsgi+mailman. -Jim P. From MGraves at acog.org Tue Jul 19 16:23:45 2016 From: MGraves at acog.org (Mark Graves) Date: Tue, 19 Jul 2016 20:23:45 +0000 Subject: [Mailman-Users] Problems with Membership List and Extraneous Characters in URL In-Reply-To: References: Message-ID: Thank you for the fix. I applied the changes to my admin.py and it is now working properly. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+mgraves=acog.org at python.org] On Behalf Of Mark Sapiro Sent: Tuesday, July 19, 2016 3:32 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Problems with Membership List and Extraneous Characters in URL On 07/18/2016 09:59 AM, Mark Graves wrote: > > and here's the source from the link on the page: > > href="u'https://listserv.acog.org/mailman/admin/coding/members?letter= > b&findmember=acog.org'">B   > > Is this a bug? I found someone else complaining about this in 2003, but nothing since. It is a bug, just reported and fixed. See and . Thank you for the report. From stephen at xemacs.org Wed Jul 20 03:13:19 2016 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 20 Jul 2016 16:13:19 +0900 Subject: [Mailman-Users] Support for Internationalized Domain Names and Email Addresses In-Reply-To: References: Message-ID: <22415.9359.615402.895109@turnbull.sk.tsukuba.ac.jp> Russ Housley writes: > As far as I can tell, Mailman will not let me include an email > address that uses IDN or EAI as a mail list recipient. Has anyone > figure out how to use either one of these? It's up to Mark, but I doubt this will be done in a Mailman 2 release, it's a bit tricky and seems likely to require invasive changes to get display on web pages right and so on. Please file an RFE for Mailman 3, though. For now, the algorithms are widely implemented in MUAs and language libraries. If you can't find a program to do it yourself (eg, on PyPI or Sourceforge), you could always scrape the address out of the off-the-wire headers using "view original" (or whatever feature your MUA offers) on mail from those addresses. (As always in email header fields, it's somehow encoded in ASCII -- the MUA has to convert to viewable form.) Sorry I can't be of more direct help today, it's "remove alligators before draining swamp" time at $DAYJOB. Steve From lesleyb at herlug.org.uk Wed Jul 20 05:52:57 2016 From: lesleyb at herlug.org.uk ('lesleyb') Date: Wed, 20 Jul 2016 10:52:57 +0100 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> Message-ID: <20160720095257.GA7658@pgcroft.net> On Tue, Jul 19, 2016 at 05:25:00PM -0400, Jim Popovitch wrote: > On Tue, Jul 19, 2016 at 5:10 PM, Perry E. Metzger wrote: > > https://httpoxy.org/ seems to impact any python program (among many > > others) that runs under cgi. Does it cause trouble for mailman? What > > is a reasonable mitigation? > > If I understand the issue correctly (and admittedly It's kinda a new > issue) this only affects proxied HTTP transactions, not HTTPS ones. > Most mailman installations should be running HTTPS in order to protect > user data, if not now is a good time to do so. I wouldn't say it's new, it was first detected in 2001[1] > > It's worth pointing out that if you are using nginx with mailman that > this only affects you if you are using fastcgi. It does not seem to > affect you if you are using nginx+uwsgi+mailman. > For anyone concerned, I suggest you take a look at [2] to decide what to do. The exploit involves HTTP_PROXY and the fix does depend on what you're using at the server end. Almost all work on the basis of unsetting any Proxy: header as early as possible in request processing. Good luck Lesley [1] https://httpoxy.org/#history [2] https://httpoxy.org/#fix-now > -Jim P. > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://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: https://mail.python.org/mailman/options/mailman-users/lesleyb%40herlug.org.uk From housley at vigilsec.com Wed Jul 20 13:51:46 2016 From: housley at vigilsec.com (Russ Housley) Date: Wed, 20 Jul 2016 13:51:46 -0400 Subject: [Mailman-Users] Support for Internationalized Domain Names and Email Addresses In-Reply-To: <22415.9359.615402.895109@turnbull.sk.tsukuba.ac.jp> References: <22415.9359.615402.895109@turnbull.sk.tsukuba.ac.jp> Message-ID: <5EC98434-2235-4970-90C3-30C27293C47C@vigilsec.com> Steve: >> As far as I can tell, Mailman will not let me include an email >> address that uses IDN or EAI as a mail list recipient. Has anyone >> figure out how to use either one of these? > > It's up to Mark, but I doubt this will be done in a Mailman 2 release, > it's a bit tricky and seems likely to require invasive changes to get > display on web pages right and so on. Please file an RFE for Mailman > 3, though. > > For now, the algorithms are widely implemented in MUAs and language > libraries. If you can't find a program to do it yourself (eg, on PyPI > or Sourceforge), you could always scrape the address out of the > off-the-wire headers using "view original" (or whatever feature your > MUA offers) on mail from those addresses. (As always in email header > fields, it's somehow encoded in ASCII -- the MUA has to convert to > viewable form.) > > Sorry I can't be of more direct help today, it's "remove alligators > before draining swamp" time at $DAYJOB. Thanks for these thoughts while you are extremely busy. My add addresses that include IDN or EAI have not worked. Subscriptions are rejected. Russ From mark at msapiro.net Wed Jul 20 14:32:35 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 Jul 2016 11:32:35 -0700 Subject: [Mailman-Users] Support for Internationalized Domain Names and Email Addresses In-Reply-To: <5EC98434-2235-4970-90C3-30C27293C47C@vigilsec.com> References: <22415.9359.615402.895109@turnbull.sk.tsukuba.ac.jp> <5EC98434-2235-4970-90C3-30C27293C47C@vigilsec.com> Message-ID: <9a89aca4-1238-b2e7-fc87-c940f1cdf938@msapiro.net> On 07/20/2016 10:51 AM, Russ Housley wrote: > > My add addresses that include IDN or EAI have not worked. Subscriptions are rejected. This is going to be tricky. Several things need to be considered. First, Modifications to the ValidateEmail() function in Mailman/Utils.py may be required. This will depend on how the address is to be represented in Mailman. If Mailman's internal representation is to be the "on the wire" encoded address, this may not be required. There will also probably need to be changes to the MemberAdaptor (default Mailman/OldStyleMemberships.py) in the various methods that test membership add membership and set/retrieve various attributes, depending on exactly how these addresses are to be represented internally in Mailman. I haven't researched exactly what's involved in IDN and EAI encodings, so if Mailman's internal representation is going to be what the address looks like "on the wire", there MAY not need to be changes in this area. There also need to be changes in the web UI to allow mass subscribing such addresses and properly displaying them. This raises the issue of what to do if an address contains a character not representable in Mailman's character set for the list's language. (This is simpler in MM 3 because everything is Unicode and UTF-8.) In short, it is possible (I don't know for sure) that we could store addresses internally in their "on the wire" encoded form, and changes to ValidateEmail() and the MemberAdaptor may not be required or may be very simple. The hard part will be translating between the "on the wire" form and the display form in the web UI. This definitely needs to be addressed in Mailman 3. As far as Mailman 2.1 is concerned, I probably won't try to do it, but if someone wants to try to implement this in a fork of the bzr branch at , I will definitely consider a merge request. For Mailman 3, it would be good to file an issue at so we have something to pin it to. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Jul 20 15:02:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 Jul 2016 12:02:13 -0700 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> Message-ID: <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> On 07/19/2016 02:10 PM, Perry E. Metzger wrote: > https://httpoxy.org/ seems to impact any python program (among many > others) that runs under cgi. Does it cause trouble for mailman? What > is a reasonable mitigation? I am not an expert on httpoxy at all, but quoting from "httpoxy is a vulnerability for server-side web applications. If you?re not deploying code, you don?t need to worry." Mailman's web UI serves end user HTML pages. It does not deploy code. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From turnbull.stephen.fw at u.tsukuba.ac.jp Thu Jul 21 03:39:42 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Thu, 21 Jul 2016 16:39:42 +0900 Subject: [Mailman-Users] Support for Internationalized Domain Names and Email Addresses In-Reply-To: <5EC98434-2235-4970-90C3-30C27293C47C@vigilsec.com> References: <22415.9359.615402.895109@turnbull.sk.tsukuba.ac.jp> <5EC98434-2235-4970-90C3-30C27293C47C@vigilsec.com> Message-ID: <22416.31806.82014.329875@turnbull.sk.tsukuba.ac.jp> Russ Housley writes: > My add addresses that include IDN or EAI have not worked. > Subscriptions are rejected. If you are using the wire-format of IDN addresses, ie, after being encoded to A-labels (ASCII characters in the IDN form), then it should work: those are valid mailboxes as ASCII. If you're using EAI, lists are (generally speaking) problematic. EAI requires the SMTPUTF8 extension to SMTP in *all* relays involved. Are you sure all your subscribers are SMTPUTF8-capable? (That's a real question, I can easily imagine you're in a situation where you do know.) If not, an EAI address will likely DOS those that aren't. Note that it's not unlikely in most contexts that some of them forward to systems which don't support SMTPUTF8. What can Mailman do? Unfortunately, implementing EAI in Mailman is going to require a lot of thought for Mailman development and for site administrators, since enabling SMTPUTF8 in the MTA means that EAI subscribers will likely *send* messages from their EAI addresses. That means that those messages will *hard bounce* at recipient sites (or their secondary MXes) that do not support SMTPUTF8, and you'll be DMARCing[1] those subscribers into oblivion -- they simply won't receive that mail, and maybe they even get unsubscribed (I suppose that the bounce will have a special status code which Mailman can recognize, though). Unless Mailman's host MTA is smart enough to DTRT (but what's that?) with the EAI address and resend. But I don't want to think about what resending means for things like DMARC,[2] and IIRC the EAI RFC did a lot of handwaving about intermediate sites -- and assumed they were pure "next hop" forwarders, not mailing lists, in that discussion. Mailman also is installed at a lot of sites where the default encoding is not UTF-8. This probably isn't a problem (it may even be a non-problem), but it needs consideration in dealing with web interface and error messages. I also worry about whether the big poorly administered domains like AOL and Yahoo![3] will treat such addresses as a spam signal. So far *all* of the mail I've received with raw UTF-8 in the header has been spam. (I'm not judging EAI users, of course, I'm simply remarking on a particular sample with distressing implications if it turns out to be at all representative.) Footnotes: [1] The analogy is quite exact -- certain sender addresses cause innocent subscribers to bounce the post. [2] Theoretically there are a couple of proposed protocols that might help, but we have no idea whether there will be any uptake of them. The past behavior of Yahoo!, Hotmail, and AOL suggests pessimism is in order. [3] Usually not the technicians' fault, but rather management that prefers losing mail to delivering spam ever. From turnbull.stephen.fw at u.tsukuba.ac.jp Thu Jul 21 04:03:29 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Thu, 21 Jul 2016 17:03:29 +0900 Subject: [Mailman-Users] DMARC problems In-Reply-To: <57898E83.4050607@msapiro.net> References: <57895793.6010204@msapiro.net> <66AC2320-63AE-4EDC-9F6C-3B6454EE3657@mischievous.us> <5789790A.9060007@msapiro.net> <222D1C14-413F-4FB8-8B7F-6529B394F074@mischievous.us> <57898E83.4050607@msapiro.net> Message-ID: <22416.33233.745654.578673@turnbull.sk.tsukuba.ac.jp> (catching up on mail) Mark Sapiro writes: > possibly also setting dmarc_quarantine_moderation_action to Yes If you use the dmarc_* settings, I recommend doing this. "p=quarantine" is not very common as far as I know, but (1) sites like GMail[1] do not promote "quarantine" to "safe", so mail *will* end up in Spam folders, and (2) experience shows that many users ignore their Spam folders for extended periods. It's not worth the minor beautification of the From address to have any mail end up in Spam folders. Steve Footnotes: [1] Which takes "reject" as advice rather than a command, and often promotes From mismatches to the Spam folder rather than simply deleting them, based on lack of spam-like or phishing content. From perry at piermont.com Fri Jul 22 11:55:32 2016 From: perry at piermont.com (Perry E. Metzger) Date: Fri, 22 Jul 2016 11:55:32 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> Message-ID: <20160722115532.69264ce8@jabberwock.cb.piermont.com> On Wed, 20 Jul 2016 12:02:13 -0700 Mark Sapiro wrote: > On 07/19/2016 02:10 PM, Perry E. Metzger wrote: > > https://httpoxy.org/ seems to impact any python program (among > > many others) that runs under cgi. Does it cause trouble for > > mailman? What is a reasonable mitigation? > > > I am not an expert on httpoxy at all, but quoting from > > > "httpoxy is a vulnerability for server-side web applications. If > you?re not deploying code, you don?t need to worry." > > Mailman's web UI serves end user HTML pages. It does not deploy > code. > Er, it uses CGI scripts, doesn't it? That's what it means to "deploy code" in this context. Perry -- Perry E. Metzger perry at piermont.com From perry at piermont.com Fri Jul 22 11:57:30 2016 From: perry at piermont.com (Perry E. Metzger) Date: Fri, 22 Jul 2016 11:57:30 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> Message-ID: <20160722115730.2c259310@jabberwock.cb.piermont.com> On Tue, 19 Jul 2016 17:25:00 -0400 Jim Popovitch wrote: > On Tue, Jul 19, 2016 at 5:10 PM, Perry E. Metzger > wrote: > > https://httpoxy.org/ seems to impact any python program (among > > many others) that runs under cgi. Does it cause trouble for > > mailman? What is a reasonable mitigation? > > If I understand the issue correctly (and admittedly It's kinda a new > issue) this only affects proxied HTTP transactions, not HTTPS ones. That is incorrect, so far as I can tell. Perry -- Perry E. Metzger perry at piermont.com From jimpop at gmail.com Fri Jul 22 12:04:25 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Fri, 22 Jul 2016 12:04:25 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160722115730.2c259310@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <20160722115730.2c259310@jabberwock.cb.piermont.com> Message-ID: On Fri, Jul 22, 2016 at 11:57 AM, Perry E. Metzger wrote: > On Tue, 19 Jul 2016 17:25:00 -0400 Jim Popovitch > wrote: >> On Tue, Jul 19, 2016 at 5:10 PM, Perry E. Metzger >> wrote: >> > https://httpoxy.org/ seems to impact any python program (among >> > many others) that runs under cgi. Does it cause trouble for >> > mailman? What is a reasonable mitigation? >> >> If I understand the issue correctly (and admittedly It's kinda a new >> issue) this only affects proxied HTTP transactions, not HTTPS ones. > > That is incorrect, so far as I can tell. According to httpoxy.org, HTTPS is not affected by HTTP_PROXY statements. "And, of course, another defense-in-depth strategy that works is to use HTTPS for internal requests, not just for securing your site?s connections to the outside world. Those aren?t affected by HTTP_PROXY." Of course, that's if you are using a very complicated split-mailman setup (web on one system, other parts on other hosts), If not, then what in your httpd.conf is would be proxying? And if nothing is proxying, then why haven't you already disabled proxy statements? Are you running anything else on the mailman server, PHP, etc? -Jim P. From mark at msapiro.net Fri Jul 22 12:48:34 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 22 Jul 2016 09:48:34 -0700 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160722115532.69264ce8@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> Message-ID: <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> On 07/22/2016 08:55 AM, Perry E. Metzger wrote: > On Wed, 20 Jul 2016 12:02:13 -0700 Mark Sapiro >> >> I am not an expert on httpoxy at all, but quoting from >> >> >> "httpoxy is a vulnerability for server-side web applications. If >> you?re not deploying code, you don?t need to worry." >> >> Mailman's web UI serves end user HTML pages. It does not deploy >> code. >> > > Er, it uses CGI scripts, doesn't it? That's what it means to "deploy > code" in this context. That's not the way I read it, but if you think that's the case, then you've already decided that Mailman 2.1 is vulnerable depending on the specific web server configuration. GNU Mailman has no control over how you set up your web server to serve Mailman's CGI output, so your question should be "is my web server configuration vulnerable?". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From perry at piermont.com Fri Jul 22 21:39:50 2016 From: perry at piermont.com (Perry E. Metzger) Date: Fri, 22 Jul 2016 21:39:50 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> Message-ID: <20160722213950.5d0cd520@jabberwock.cb.piermont.com> On Fri, 22 Jul 2016 09:48:34 -0700 Mark Sapiro wrote: > On 07/22/2016 08:55 AM, Perry E. Metzger wrote: > > On Wed, 20 Jul 2016 12:02:13 -0700 Mark Sapiro > > > >> > >> I am not an expert on httpoxy at all, but quoting from > >> > >> > >> "httpoxy is a vulnerability for server-side web applications. If > >> you?re not deploying code, you don?t need to worry." > >> > >> Mailman's web UI serves end user HTML pages. It does not deploy > >> code. > >> > > > > Er, it uses CGI scripts, doesn't it? That's what it means to > > "deploy code" in this context. > > > That's not the way I read it, It works by an attacker inserting an http_proxy header into the headers which it presents to the web server, which are then passed in the HTTP_PROXY environment variable to the CGI script. I think that there aren't many ways to read this. > but if you think that's the case, then > you've already decided that Mailman 2.1 is vulnerable depending on > the specific web server configuration. I don't know. I don't know if Mailman uses any of the vulnerable routines that might cause HTTP_PROXY being set to cause trouble. > GNU Mailman has no control > over how you set up your web server to serve Mailman's CGI output, > so your question should be "is my web server configuration > vulnerable?". Not entirely, no. You could defend Mailman by interposing code on the http server of course. Perry -- Perry E. Metzger perry at piermont.com From mark at msapiro.net Fri Jul 22 22:59:45 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 22 Jul 2016 19:59:45 -0700 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160722213950.5d0cd520@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> <20160722213950.5d0cd520@jabberwock.cb.piermont.com> Message-ID: <1e3a50cd-9df3-28b9-8024-8be30daa8198@msapiro.net> On 7/22/16 6:39 PM, Perry E. Metzger wrote: > > It works by an attacker inserting an http_proxy header into the > headers which it presents to the web server, which are then passed in > the HTTP_PROXY environment variable to the CGI script. I think that > there aren't many ways to read this. And Mailman 2.1's CGIs will do absolutely nothing with an HTTP_PROXY environment variable. They won't look for it even if it's there. They look at things like query strings and POST data to determine what to do and then they write HTML to stdout. > I don't know. I don't know if Mailman uses any of the vulnerable > routines that might cause HTTP_PROXY being set to cause trouble. Mailman 2.1 uses the Python cgi module and uses only cgi.FieldStorage() to retrieve POST data and query fragments. It uses nothing other than writes to stdout to send any kind of output. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From turnbull.stephen.fw at u.tsukuba.ac.jp Sat Jul 23 03:36:30 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Sat, 23 Jul 2016 16:36:30 +0900 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160722213950.5d0cd520@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> <20160722213950.5d0cd520@jabberwock.cb.piermont.com> Message-ID: <22419.7806.355604.747772@turnbull.sk.tsukuba.ac.jp> Perry E. Metzger writes: > > > Er, it uses CGI scripts, doesn't it? That's what it means to > > > "deploy code" in this context. I can think of several alternative interpretations (such as browser-side Javascript, which was my first take when I read those words -- I haven't looked at the actual documentation). In this case, it seems to mean "deploying an HTTP client (that makes outgoing HTTP requests) in your CGI script". > It works by an attacker inserting an http_proxy header into the > headers which it presents to the web server, which are then passed > in the HTTP_PROXY environment variable to the CGI script. I think > that there aren't many ways to read this. Erm, here's what the site says: What can happen if my web application is vulnerable? If a vulnerable HTTP client makes an outgoing HTTP connection, while running in a server-side CGI application, Note the *in a server-side CGI*. AFAICS, we're done: we're safe. Mailman (as we distribute it) doesn't make *outgoing* HTTP connections, it sends responses to incoming requests. BTW, the Mailman 3 bundled Django applications Postorius and HyperKitty are also apparently safe from this vulnerability even though they make outgoing HTTP connections to the Mailman core, since they are WSGI applications: wsgi, for example, is not vulnerable, because os.environ is not polluted by CGI data (from http://httpoxy.org) Note that the above analysis is completely superficial: it depends on the correctness of the statements by the authors of httpoxy.org. I have not looked at the code. The belt and suspenders approach would be to remove that variable from the environment at the entry to any Mailman CGI. Of course if something in Mailman or its dependencies depends on correct setting of that variable it will occasion a bug. > > GNU Mailman has no control over how you set up your web server to > > serve Mailman's CGI output, so your question should be "is my web > > server configuration vulnerable?". > > Not entirely, no. You could defend Mailman by interposing code on the > http server of course. I don't understand. If you mean between Mailman and the HTTP server, that's site configuration and Mark's question applies. If you mean in Mailman itself (and the Python modules it calls), I guess you mean the "belt and suspenders" approach? (In fact the RightThang to do there would be to remove all envvars that Mailman itself doesn't depend on, with the same risk of bugs, of course.) Steve From jackhill at duke.edu Fri Jul 22 13:08:50 2016 From: jackhill at duke.edu (Jack Hill) Date: Fri, 22 Jul 2016 13:08:50 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> Message-ID: On Fri, 22 Jul 2016, Mark Sapiro wrote: > That's not the way I read it, but if you think that's the case, then > you've already decided that Mailman 2.1 is vulnerable depending on the > specific web server configuration. GNU Mailman has no control over how > you set up your web server to serve Mailman's CGI output, so your > question should be "is my web server configuration vulnerable?". As I understand it, even with a potentially vulnerable httpd configuration (i.e. one that uses the HTTP Proxy: header to set the HTTP_PROXY environment variable for CGI scripts) the CGI application needs to make outgoing HTTP requests, and check the HTTP_PROXY env var to see if it should use a proxy to do so to be affected by httpoxy. I'm not aware of Mailman 2.1 doing this. If that is correct, then httpoxy shouldn't cause problems for us. Best, Jack From perry at piermont.com Sat Jul 23 11:19:37 2016 From: perry at piermont.com (Perry E. Metzger) Date: Sat, 23 Jul 2016 11:19:37 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <1e3a50cd-9df3-28b9-8024-8be30daa8198@msapiro.net> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> <20160722213950.5d0cd520@jabberwock.cb.piermont.com> <1e3a50cd-9df3-28b9-8024-8be30daa8198@msapiro.net> Message-ID: <20160723111937.130b31cf@jabberwock.cb.piermont.com> On Fri, 22 Jul 2016 19:59:45 -0700 Mark Sapiro wrote: > And Mailman 2.1's CGIs will do absolutely nothing with an HTTP_PROXY > environment variable. They won't look for it even if it's there. > They look at things like query strings and POST data to determine > what to do and then they write HTML to stdout. Well, there are implicit things that use HTTP_PROXY. If mailman makes any http requests itself, or calls anything that does, it might cause trouble that it is in the environment. I take it that this is *not* the case? (The problem is not that cgi scripts explicitly look at HTTP_PROXY, it is that many things *implicitly* look at it.) Perry -- Perry E. Metzger perry at piermont.com From perry at piermont.com Sat Jul 23 11:23:25 2016 From: perry at piermont.com (Perry E. Metzger) Date: Sat, 23 Jul 2016 11:23:25 -0400 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <22419.7806.355604.747772@turnbull.sk.tsukuba.ac.jp> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> <20160722213950.5d0cd520@jabberwock.cb.piermont.com> <22419.7806.355604.747772@turnbull.sk.tsukuba.ac.jp> Message-ID: <20160723112325.11a5e958@jabberwock.cb.piermont.com> On Sat, 23 Jul 2016 16:36:30 +0900 "Stephen J. Turnbull" wrote: > > It works by an attacker inserting an http_proxy header into the > > headers which it presents to the web server, which are then > > passed in the HTTP_PROXY environment variable to the CGI script. > > I think that there aren't many ways to read this. > > Erm, here's what the site says: > > What can happen if my web application is vulnerable? > If a vulnerable HTTP client makes an outgoing HTTP connection, > while running in a server-side CGI application, > > Note the *in a server-side CGI*. AFAICS, we're done: we're safe. You're misinterpreting. The issue is that some server side systems also use web APIs of various kinds. > Mailman (as we distribute it) doesn't make *outgoing* HTTP > connections, it sends responses to incoming requests. So that makes it invulnerable, yes. > BTW, the Mailman 3 bundled Django applications Postorius and > HyperKitty are also apparently safe from this vulnerability even > though they make outgoing HTTP connections to the Mailman core, > since they are WSGI applications: > > wsgi, for example, is not vulnerable, because os.environ is not > polluted by CGI data > (from http://httpoxy.org) Well, actually, if you read more, apps using wsgiref.handlers.CGIHandler are (apparently) vulnerable, unless I'm misreading. > > > GNU Mailman has no control over how you set up your web server > > > to serve Mailman's CGI output, so your question should be "is > > > my web server configuration vulnerable?". > > > > Not entirely, no. You could defend Mailman by interposing code > > on the http server of course. > > I don't understand. If you mean between Mailman and the HTTP > server, that's site configuration and Mark's question applies. If > you mean in Mailman itself (and the Python modules it calls), I > guess you mean the "belt and suspenders" approach? (In fact the > RightThang to do there would be to remove all envvars that Mailman > itself doesn't depend on, with the same risk of bugs, of course.) What I meant was that you can do things on the web server side like altering your handling of http_proxy (which is what I did on my web servers as soon as this came out). I would agree that nuking any environment variable that you don't know that you need is probably a good idea in general. It increases safety. Perry -- Perry E. Metzger perry at piermont.com From luscheina at yahoo.de Sat Jul 23 11:30:34 2016 From: luscheina at yahoo.de (Christian F Buser) Date: Sat, 23 Jul 2016 17:30:34 +0200 Subject: [Mailman-Users] Yahoo policy on list messages Message-ID: <57938D9A.803@yahoo.de> I have received several bounce notices for subscribers of my list with the following contents: Action: failed Final-Recipient:rfc822;ekxxxxxka at yahoo.com Status: 5.0.0 Remote-MTA: dns; mta7.am0.yahoodns.net Diagnostic-Code: smtp; 554 5.7.9 Message not accepted for policy reasons. Seehttps://help.yahoo.com/kb/postmaster/SLN7253.html Action: failed Final-Recipient:rfc822;mail at xxxxx-xxxx.info Status: 5.0.0 Remote-MTA: dns; mxcluster1.one.com Diagnostic-Code: smtp; 550 5.7.1 The messages violates the DMARC policy of yahoo.com (eb9fcd83-501a-11e6-b513-b82a72d854f0) Action: failed Final-Recipient:rfc822;mxxxxxw at yahoo.de Status: 5.0.0 Remote-MTA: dns; mx-eu.mail.am0.yahoodns.net Diagnostic-Code: smtp; 554 5.7.9 Message not accepted for policy reasons. Seehttps://help.yahoo.com/kb/postmaster/SLN7253.html I asked my provider for help about this, and he wrote back: "from what I can see from the text files you sent me, it's a matter of the mailing list configuration. The sender ( From: ) needs to be set as the mailing list address and not as the original sender (eg, ekxxxxxka at yahoo.com) Read here: https://help.yahoo.com/kb/postmaster/SLN7253.html - but all mailing lists I know usually have the original sender's name in the From-field... So what am I doing wrong here? My list runs on the cPanel 56.0.28 version of Mailman 2.1.20 Thank you, Christian -- Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) Hilfe f?r Strassenkinder in Ghana: http://www.chance-for-children.org From mark at msapiro.net Sat Jul 23 11:33:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 Jul 2016 08:33:12 -0700 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160723111937.130b31cf@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> <20160722213950.5d0cd520@jabberwock.cb.piermont.com> <1e3a50cd-9df3-28b9-8024-8be30daa8198@msapiro.net> <20160723111937.130b31cf@jabberwock.cb.piermont.com> Message-ID: <73cc01e0-031b-0bc0-b0c3-0fb797c31380@msapiro.net> On 7/23/16 8:19 AM, Perry E. Metzger wrote: > > Well, there are implicit things that use HTTP_PROXY. If mailman makes > any http requests itself, or calls anything that does, it might cause > trouble that it is in the environment. I take it that this is *not* > the case? Yes. That is not the case. In more than one post in this thread it has been affirmed that no Mailman 2.1 CGI issues any kind of HTTP request. They only write HTML to stdout. You can find the code at if you wish to verify this for yourself. And, as also has been posted more than once, Mailman 3's web UI components, Postorius and HyperKitty, are Django WSGI applications, not CGIs at all. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Jul 23 11:41:59 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 Jul 2016 08:41:59 -0700 Subject: [Mailman-Users] Yahoo policy on list messages In-Reply-To: <57938D9A.803@yahoo.de> References: <57938D9A.803@yahoo.de> Message-ID: <1dca66be-7248-4703-fd56-f932c41d3c03@msapiro.net> On 7/23/16 8:30 AM, Christian F Buser via Mailman-Users wrote: > I have received several bounce notices for subscribers of my list with > the following contents: ... > > - but all mailing lists I know usually have the original sender's name > in the From-field... > > So what am I doing wrong here? > > My list runs on the cPanel 56.0.28 version of Mailman 2.1.20 You need to go to Mailman's Privacy options... -> Sender filters page and set dmarc_moderation_action = Munge From dmarc_quarantine_moderation_action = Yes See and for more information. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From turnbull.stephen.fw at u.tsukuba.ac.jp Sat Jul 23 18:26:00 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Sun, 24 Jul 2016 07:26:00 +0900 Subject: [Mailman-Users] Yahoo policy on list messages In-Reply-To: <57938D9A.803@yahoo.de> References: <57938D9A.803@yahoo.de> Message-ID: <22419.61176.712223.879063@turnbull.sk.tsukuba.ac.jp> Christian F Buser via Mailman-Users writes: > "from what I can see from the text files you sent me, it's a matter of > the mailing list configuration. > The sender ( From: ) needs to be set as the mailing list address and not > as the original sender (eg, ekxxxxxka at yahoo.com) Your provider, and Yahoo!, are advocating violating the standards that *define* the Internet. Putting the list's name in From means that the list is claiming responsibility for the content of the message. > - but all mailing lists I know usually have the original sender's name > in the From-field... That is correct usage according to the definition of the From field. > So what am I doing wrong here? According to the standards that define the Internet, *you* are doing nothing wrong (except maybe you shouldn't be accepting posts from Yahoo! email addresses[1]). Yahoo! screwed up by leaking millions of users' address books to spammers and phishers. DMARC is the only effective way to protect the people *in* those address books from spam and phishing messages apparently sent by their friends who use Yahoo! for email, but Yahoo! is completely unapologetic about the collateral damage to both mailing lists and to many small businesses. I tell my friends that friends don't let friends use Yahoo! accounts -- both for reasons of social conscience and because there are a lot of ways that Yahoo!-originated mail can end up in the bitbucket.[2] So bow in the direction of the nearest root nameserver, apologize to the Higher Powers of the Internet, and set dmarc_moderation_action to "Munge From". This will put the mailing list's address in From, along with the user's address in the "display name", for those posters whose email providers abuse DMARC the same way that Yahoo! does, and only those posters. Footnotes: [1] I'm not entirely joking. For example, that is the official policy of my employer, the Japanese Ministry of Education, because of the mess AOL and Yahoo! created in April 2014 in this way. Ironically enough, the Japanese affiliate is one of the few in the Yahoo! family that (still) does NOT cause this problem. [2] Of the popular freemail providers, GMail and Hotmail do not have this problem (yet, they say they won't, but nobody can be 100% sure they'll never leak a few million address books to the black hats :-( ). You can can check your local providers by looking up the TXT record for the _dmarc subdomain of the domain, and checking if it contains "p=reject". For example: $ host -t TXT _dmarc.yahoo.de v=DMARC1\; p=reject\; pct=100\; rua=mailto:dmarc_y_rua at yahoo.com\; Your posts will bounce or be silently discarded at many subscribers to many mailing lists. From turnbull.stephen.fw at u.tsukuba.ac.jp Sat Jul 23 18:26:30 2016 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Sun, 24 Jul 2016 07:26:30 +0900 Subject: [Mailman-Users] Is mailman vulnerable to the httpoxy bug? In-Reply-To: <20160723112325.11a5e958@jabberwock.cb.piermont.com> References: <20160719171005.0b72e1ec@jabberwock.cb.piermont.com> <5ad26b95-2213-9234-975c-2a42c41a4246@msapiro.net> <20160722115532.69264ce8@jabberwock.cb.piermont.com> <99da666f-9294-8fa5-e269-599b5e32c144@msapiro.net> <20160722213950.5d0cd520@jabberwock.cb.piermont.com> <22419.7806.355604.747772@turnbull.sk.tsukuba.ac.jp> <20160723112325.11a5e958@jabberwock.cb.piermont.com> Message-ID: <22419.61206.843980.708453@turnbull.sk.tsukuba.ac.jp> Perry E. Metzger writes: > > Note the *in a server-side CGI*. AFAICS, we're done: we're safe. > > You're misinterpreting. The issue is that some server side systems > also use web APIs of various kinds. > > > Mailman (as we distribute it) doesn't make *outgoing* HTTP > > connections, it sends responses to incoming requests. > > So that makes it invulnerable, yes. Note that in my post, my three sentences above were one paragraph. So I wasn't misinterpreting after all. I know you're trying to help, but this is just FUD. The same is true for the WGSI applications. "Pure" WSGI applications like Postorius and HyperKitty don't use CGIhandler. > What I meant was that you can do things on the web server side like > altering your handling of http_proxy (which is what I did on my web > servers as soon as this came out). Sure, but that is covered by Mark's point that it's the rest of the webserver configuration that site admins should worry about. If you want to do people a favor, explain the necessary configuration magic for the webservers you use. That will protect them, both Mailman from the vanishing probability that there's something in Mailman that makes HTTP requests that we don't know about, as well as any other CGI applications that they happen to run. From mailman at webzebra.net Tue Jul 26 14:19:19 2016 From: mailman at webzebra.net (Nicolas) Date: Tue, 26 Jul 2016 20:19:19 +0200 Subject: [Mailman-Users] delay between delivery to mailman post command and sending out to list Message-ID: <61BB530F-CEF3-49DB-837C-AFBF4A526C69@webzebra.net> Hi, I?m running Mailman version 2.1.14 on an Ubuntu 12.04.5 LTS build, with Postfix MTA. I recently noticed up to one hour delays between Postfix delivering messages to command "/var/lib/mailman/mail/mailman post [listname]", and Mailman effectively sending out the message to list members (as evidenced in Postfix log file, email headers, and Mailman logs). The delays are consistent in that each posted message, to any list and with any number of subscriptions (between 1 and 250), is delayed by at least 20 minutes. The Mailman "post" log file /var/log/mailman/post does not indicate the message being posted, until the message is finally being sent out up to one hour after the post. However, the list?s archives, as well as the list?s digest.mbox file, DO contain the posted message immediately after posting, confirming that Mailman did instantly receive the message from Postfix. Similarly, email notifications to admin (new list, memberships, ?) suffer from the same delays. There are no errors found in the qrunner, mischief, or smtp log files that give pointers as to why this happens. The system is not under any load to speak of, and Postfix is running fine otherwise, delivering mail to local users and remote recipients instantly. The mail queue is virtually empty. Would running separate, verbose instances of qrunner possibly give me any insight, and how should I go about this? Any input is appreciated. Regards, Nicolas From mark at msapiro.net Wed Jul 27 09:47:41 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 Jul 2016 06:47:41 -0700 Subject: [Mailman-Users] delay between delivery to mailman post command and sending out to list In-Reply-To: <61BB530F-CEF3-49DB-837C-AFBF4A526C69@webzebra.net> References: <61BB530F-CEF3-49DB-837C-AFBF4A526C69@webzebra.net> Message-ID: On 07/26/2016 11:19 AM, Nicolas wrote: > > The Mailman "post" log file /var/log/mailman/post does not indicate the message being posted, until the message is finally being sent out up to one hour after the post. This is expected. It's not written until the message is sent. > However, the list?s archives, as well as the list?s digest.mbox file, DO contain the posted message immediately after posting, confirming that Mailman did instantly receive the message from Postfix. Mailman's 'out' queue is backlogged. (I really need to write a FAQ on this ). You can tell because of the above and there will be several files in Mailman's qfiles/out directory and the entries in Mailman's 'smtp' log will be continuous, i.e. the timestamps of each entry will be x seconds after the previous one where x is the "completed in n.nnn seconds" value. > Would running separate, verbose instances of qrunner possibly give me any insight, and how should I go about this? Any input is appreciated. Multiple, sliced OutgoingRunner processes might help, but the real issue is it takes too long for Mailman to deliver to Postfix due to Postfix configuration. In my production installation with full VERP, Mailman delivers to about 20 or more recipients per second. See , although a lot of that is outdated, but do note all the stuff on disable_dns_lookups. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From martin.stein at attac.de Thu Jul 28 08:14:34 2016 From: martin.stein at attac.de (Martin Stein) Date: Thu, 28 Jul 2016 14:14:34 +0200 Subject: [Mailman-Users] Sending mails to all list administrators Message-ID: <5799F72A.3000408@attac.de> Hi, I'm looking for an easy way, as site administrator, to send a message to all list administrators. Is there any possibility to set up a autogenerated list with all list administrators of the site or another smooth solution? Regards, Martin -- Martin Stein Attac Deutschland Webteam Attac Deutschland M?nchener Str. 48 60329 Frankfurt am Main Mail: martin.stein at attac.de From mark at msapiro.net Thu Jul 28 10:02:02 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 Jul 2016 07:02:02 -0700 Subject: [Mailman-Users] Sending mails to all list administrators In-Reply-To: <5799F72A.3000408@attac.de> References: <5799F72A.3000408@attac.de> Message-ID: On 07/28/2016 05:14 AM, Martin Stein wrote: > Hi, > > I'm looking for an easy way, as site administrator, to send a message to > all list administrators. Is there any possibility to set up a > autogenerated list with all list administrators of the site or another > smooth solution? You can create the list and then populate/maintain it with bin/list-owners [-m] | bin/sync_members [options] -f - LISTNAME see 'bin/list-owners --help' and 'bin/sync_members --help' for more info on options. You can run the above pipe via cron to automatically maintain the list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From phirayam at fredhutch.org Thu Jul 28 12:23:22 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Thu, 28 Jul 2016 16:23:22 +0000 Subject: [Mailman-Users] Sending mails to all list administrators In-Reply-To: <5799F72A.3000408@attac.de> References: <5799F72A.3000408@attac.de> Message-ID: <34935_1469723012_579A3183_34935_1247_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A373@adama.fhcrc.org> I suppose you could generate a list of people to send by doing something like: /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed 's/,/\r/g'|sed 's/ //g'|sort|uniq And that use that to send your email. Maybe combine it with xargs to do something like: /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed 's/,/\r/g'|sed 's/ //g'|sort|uniq | xargs -I {} mail -s 'subject' {} < message.txt At least, I think that last might work. :) -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phirayam at fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+phirayam=fredhutch.org at python.org] On Behalf Of Martin Stein Sent: Thursday, July 28, 2016 5:15 AM To: mailman-users at python.org Subject: [Mailman-Users] Sending mails to all list administrators Hi, I'm looking for an easy way, as site administrator, to send a message to all list administrators. Is there any possibility to set up a autogenerated list with all list administrators of the site or another smooth solution? Regards, Martin -- Martin Stein Attac Deutschland Webteam Attac Deutschland M?nchener Str. 48 60329 Frankfurt am Main Mail: martin.stein at attac.de ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://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: https://mail.python.org/mailman/options/mailman-users/phirayam%40fredhutch.org From mark at msapiro.net Thu Jul 28 12:44:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 Jul 2016 09:44:53 -0700 Subject: [Mailman-Users] Sending mails to all list administrators In-Reply-To: <34935_1469723012_579A3183_34935_1247_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A373@adama.fhcrc.org> References: <5799F72A.3000408@attac.de> <34935_1469723012_579A3183_34935_1247_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A373@adama.fhcrc.org> Message-ID: <1310bb4e-399c-417c-7b47-8e3013459c53@msapiro.net> On 07/28/2016 09:23 AM, Hirayama, Pat wrote: > I suppose you could generate a list of people to send by doing something like: > > /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed 's/,/\r/g'|sed 's/ //g'|sort|uniq You can produce the same result with /usr/lib/mailman/bin/list_owners without the post processing. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cmupythia at cmu.edu Thu Jul 28 12:35:33 2016 From: cmupythia at cmu.edu (Gretchen R Beck) Date: Thu, 28 Jul 2016 16:35:33 +0000 Subject: [Mailman-Users] Sending mails to all list administrators In-Reply-To: <34935_1469723012_579A3183_34935_1247_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A373@adama.fhcrc.org> References: <5799F72A.3000408@attac.de>, <34935_1469723012_579A3183_34935_1247_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A373@adama.fhcrc.org> Message-ID: <1469723697733.80083@cmu.edu> Or, even easier to generate the list: /usr/mailman/bin/list_lists | awk '{print $1 "-owner@"}' ________________________________________ From: Mailman-Users on behalf of Hirayama, Pat Sent: Thursday, July 28, 2016 12:23 PM To: Martin Stein; mailman-users at python.org Subject: Re: [Mailman-Users] Sending mails to all list administrators I suppose you could generate a list of people to send by doing something like: /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed 's/,/\r/g'|sed 's/ //g'|sort|uniq And that use that to send your email. Maybe combine it with xargs to do something like: /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed 's/,/\r/g'|sed 's/ //g'|sort|uniq | xargs -I {} mail -s 'subject' {} < message.txt At least, I think that last might work. :) -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phirayam at fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+phirayam=fredhutch.org at python.org] On Behalf Of Martin Stein Sent: Thursday, July 28, 2016 5:15 AM To: mailman-users at python.org Subject: [Mailman-Users] Sending mails to all list administrators Hi, I'm looking for an easy way, as site administrator, to send a message to all list administrators. Is there any possibility to set up a autogenerated list with all list administrators of the site or another smooth solution? Regards, Martin -- Martin Stein Attac Deutschland Webteam Attac Deutschland M?nchener Str. 48 60329 Frankfurt am Main Mail: martin.stein at attac.de ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://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: https://mail.python.org/mailman/options/mailman-users/phirayam%40fredhutch.org ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://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: https://mail.python.org/mailman/options/mailman-users/cmupythia%40cmu.edu From phirayam at fredhutch.org Thu Jul 28 12:55:11 2016 From: phirayam at fredhutch.org (Hirayama, Pat) Date: Thu, 28 Jul 2016 16:55:11 +0000 Subject: [Mailman-Users] Sending mails to all list administrators In-Reply-To: <1310bb4e-399c-417c-7b47-8e3013459c53@msapiro.net> References: <5799F72A.3000408@attac.de> <34935_1469723012_579A3183_34935_1247_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A373@adama.fhcrc.org> <1310bb4e-399c-417c-7b47-8e3013459c53@msapiro.net> Message-ID: <34935_1469724922_579A38F9_34935_2599_1_AE5F7147890F3544BFCDB1594A4329C9E6C7A4CA@adama.fhcrc.org> Thanks, Mark! -p -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+phirayam=fredhutch.org at python.org] On Behalf Of Mark Sapiro Sent: Thursday, July 28, 2016 9:45 AM To: mailman-users at python.org Subject: Re: [Mailman-Users] Sending mails to all list administrators On 07/28/2016 09:23 AM, Hirayama, Pat wrote: > I suppose you could generate a list of people to send by doing something like: > > /usr/lib/mailman/bin/list_admins --all | sed 's/.*Owners: //'|sed 's/,/\r/g'|sed 's/ //g'|sort|uniq You can produce the same result with /usr/lib/mailman/bin/list_owners without the post processing. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://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: https://mail.python.org/mailman/options/mailman-users/phirayam%40fredhutch.org From mailman at webzebra.net Thu Jul 28 13:22:38 2016 From: mailman at webzebra.net (Nicolas) Date: Thu, 28 Jul 2016 19:22:38 +0200 Subject: [Mailman-Users] delay between delivery to mailman post command and sending out to list In-Reply-To: References: <61BB530F-CEF3-49DB-837C-AFBF4A526C69@webzebra.net> Message-ID: <327B0623-25FD-4F41-8B9A-A1500532737F@webzebra.net> > On 27 Jul 2016, at 15:47, Mark Sapiro wrote: > > On 07/26/2016 11:19 AM, Nicolas wrote: >> > > >> Would running separate, verbose instances of qrunner possibly give me any insight, and how should I go about this? Any input is appreciated. > > > Multiple, sliced OutgoingRunner processes might help, but the real issue > is it takes too long for Mailman to deliver to Postfix due to Postfix > configuration. In my production installation with full VERP, Mailman > delivers to about 20 or more recipients per second. > > See , although a lot of that is > outdated, but do note all the stuff on disable_dns_lookups. After deleting a subscribed email address with a non-existing domain from a list without automatic bounce processing configured, for which Mailman obsessively retried delivery every minute while ignoring all the other queued posts, I see up to 50 deliveries per second. Just to confirm (probably ad nauseam for the regulars out here) that a separate Postfix instance with dns lookups disabled (+ automatic bounce processing) is the way to go. Thanks, Nicolas From mailinglist at samsi.us Sat Jul 30 21:19:04 2016 From: mailinglist at samsi.us (Caesar Samsi) Date: Sat, 30 Jul 2016 18:19:04 -0700 Subject: [Mailman-Users] Is there a way to maintain a global Terms of Use / Acceptable Use Policy ? Message-ID: <9D882833-0B83-4064-8968-635F46C978E0@samsi.us> Hi There, I see General List Information which is specific to the list, but wanting a global page to use for when there are a large number of lists. Thanks you, Caesar. From mark at msapiro.net Sat Jul 30 23:14:25 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 30 Jul 2016 20:14:25 -0700 Subject: [Mailman-Users] Is there a way to maintain a global Terms of Use / Acceptable Use Policy ? In-Reply-To: <9D882833-0B83-4064-8968-635F46C978E0@samsi.us> References: <9D882833-0B83-4064-8968-635F46C978E0@samsi.us> Message-ID: On 07/30/2016 06:19 PM, Caesar Samsi wrote: > > I see General List Information which is specific to the list, but wanting a global page to use for when there are a large number of lists. If you want something to appear on the listinfo page of every list, you can make a sitewide edited version of the listinfo.html template. See . You can copy $prefix/templates/en/listinfo.html to $prefix/templates/site/en/listinfo.html and add your information or add some javascript or whatever to load it from a URL or file. Note that this will only work for all lists which don't have a list specific or domain specific version of the listinfo.html template as those will override the site template. E.g., if there is a list specific template created by the list admin Edit the public HTML pages and text files -> General list information page function, that will take priority, but if there isn't one and someone later makes one, the site template will be the starting point. If you also want to use the %(info)s replacement in msg_header, msg_footer, digest_header, digest_footer, there is no global place for that information. You might consider putting something like info = """Some multi-line block of text for info. And more... """ into a file, say /path/to/info.txt and running #!/bin/bash for list in `/path/to/mailman/bin/list_lists --bare`; do /path/to/mailman/bin/config_list -i /path/to/info.txt $list done to set info for all lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan