From dlongnecker at comcast.net Fri May 1 16:14:54 2015 From: dlongnecker at comcast.net (Dennis Longnecker) Date: Fri, 1 May 2015 07:14:54 -0700 Subject: [Mailman-Users] Mailman and dmark help -- please Message-ID: <03d101d08419$335ff580$9a1fe080$@comcast.net> I have a mailing list setup for our boy scout troop. The site is running mailman version version 2.1.18-1. I looking at various lists, I believe I have as much set as I can. (Details for from_is_list) = Munge From I really -- really want the list set so when someone gets an e-mail from the list they can see who sent it and when they click reply it goes to the original sender. When I have the remove sender option, etc. People don't know who the e-mail came from or how to directly reply. I was reading about some DNS DMARC settings, but frankly it really confused me. What I have observed: E-mail from MSN to list Comcast Users = DOn't Get it AOL Users = Don't Get it Yahoo Users = Don't Get it users with arvixe accounts = Do Get it. E-mail from GMAIL to list Comcast Users = DOn't Get it AOL Users = Don't Get it Yahoo Users = Don't Get it users with arvixe accounts = Do Get it. E-mail from Comcast to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Do Get it outlook.com = Do Get it users with arvixe accounts = Do Get it. E-mail from AOL to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Dont Get it outlook.com = Dont Get it users with arvixe accounts = Do Get it. E-mail from Outlook to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Dont Get it outlook.com = Dont Get it users with arvixe accounts = Do Get it. E-mail from Yahoo to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Do Get it outlook.com = Do Get it users with arvixe accounts = Do Get it. Any sugestions? My site is troop101-wa.org if looking at its DNS records could help. Dennis From himbeere at meine-oma.de Fri May 1 13:19:58 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Fri, 01 May 2015 13:19:58 +0200 Subject: [Mailman-Users] mailman 3.0 and exim Message-ID: <19077190.QKGnMlDpdU@rather> Hello. Just installed mailman3 on one of my testsystems. There is only exim installed. No postfix. When i try to create a new list i get error 500 from nginx. The logfile says: sh: /usr/sbin/postmap: No such file or directory sh: /usr/sbin/postmap: No such file or directory Traceback (most recent call last): File "/usr/lib64/python3.4/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/mailman/database/transaction.py", line 57, in wrapper rtn = function(*args, **kws) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/mailman/rest/wsgiapp.py", line 65, in __call__ environ, start_response) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/falcon/api.py", line 182, in __call__ responder(req, resp, **params) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/mailman/rest/lists.py", line 207, in on_post mlist = create_list(**validator(request)) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/mailman/app/lifecycle.py", line 81, in create_list call_name(config.mta.incoming).create(mlist) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/mailman/mta/postfix.py", line 69, in create self.regenerate() File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- packages/mailman/mta/postfix.py", line 104, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /home/mailman/mailman- bundler/var/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /home/mailman/mailman- bundler/var/data/postfix_domains, 127, Key has expired [01/May/2015 04:14:48] "POST /mailman3/lists/new/ HTTP/1.0" 200 2716 Why is mailman looking for the postmap command? How can i prevent this from happening? thanks and cheers t. From himbeere at meine-oma.de Fri May 1 20:13:14 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Fri, 01 May 2015 20:13:14 +0200 Subject: [Mailman-Users] mailman 3.0 and exim In-Reply-To: <19077190.QKGnMlDpdU@rather> References: <19077190.QKGnMlDpdU@rather> Message-ID: <2295431.EUAHqlSApz@rather> On Friday 01 May 2015 13:19:58 Thomas Stein wrote: > Hello. In $home_mailman/var/etc/mailman.cfg i have this setting: [mta] # For all Exim4 installations. incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver # Typical single host with MTA and Mailman configuration. # Adjust to your system's configuration. # Exim happily works with the "localhost" alias rather than IP address. lmtp_host: localhost smtp_host: localhost # Mailman should not be run as root. # Use any convenient port > 1024. 8024 is a convention, but can be # changed if there is a conflict with other software using that port. lmtp_port: 8024 # smtp_port rarely needs to be set. smtp_port: 25 # Exim4-specific configuration parameter defaults. Currently empty. configuration: python:mailman.config.exim4 So i guess mailman should be aware of my exim setup. thanks for any hints. cheers t. > Just installed mailman3 on one of my testsystems. There is only exim > installed. No postfix. When i try to create a new list i get error 500 from > nginx. The logfile says: > > sh: /usr/sbin/postmap: No such file or directory > sh: /usr/sbin/postmap: No such file or directory > Traceback (most recent call last): > File "/usr/lib64/python3.4/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/mailman/database/transaction.py", line 57, in wrapper > rtn = function(*args, **kws) > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/mailman/rest/wsgiapp.py", line 65, in __call__ > environ, start_response) > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/falcon/api.py", line 182, in __call__ > responder(req, resp, **params) > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/mailman/rest/lists.py", line 207, in on_post > mlist = create_list(**validator(request)) > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/mailman/app/lifecycle.py", line 81, in create_list > call_name(config.mta.incoming).create(mlist) > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/mailman/mta/postfix.py", line 69, in create > self.regenerate() > File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site- > packages/mailman/mta/postfix.py", line 104, in regenerate > raise RuntimeError(NL.join(errors)) > RuntimeError: command failure: /usr/sbin/postmap /home/mailman/mailman- > bundler/var/data/postfix_lmtp, 127, Key has expired > command failure: /usr/sbin/postmap /home/mailman/mailman- > bundler/var/data/postfix_domains, 127, Key has expired > [01/May/2015 04:14:48] "POST /mailman3/lists/new/ HTTP/1.0" 200 2716 > > Why is mailman looking for the postmap command? How can i prevent this from > happening? > > thanks and cheers > t. From ournet.biz at gmail.com Sat May 2 18:07:00 2015 From: ournet.biz at gmail.com (EyeLand) Date: Sat, 2 May 2015 19:07:00 +0300 Subject: [Mailman-Users] Conceal the member's address Message-ID: Hello, on ?General Options - Default options for new members joining this list. - Conceal the member's address? http://i11.pixs.ru:/storage/9/6/1/1JPG_2435911_17190961.jpg I deactivate check box, but on letter I not see the subscriber email http://i11.pixs.ru:/storage/9/6/2/2JPG_7009327_17190962.jpg, can you consult? Thank you. From barry at list.org Sat May 2 18:14:45 2015 From: barry at list.org (Barry Warsaw) Date: Sat, 2 May 2015 12:14:45 -0400 Subject: [Mailman-Users] mailman 3.0 and exim In-Reply-To: <2295431.EUAHqlSApz@rather> References: <19077190.QKGnMlDpdU@rather> <2295431.EUAHqlSApz@rather> Message-ID: <20150502121445.44c97647@anarchist.wooz.org> On May 01, 2015, at 08:13 PM, Thomas Stein wrote: >In $home_mailman/var/etc/mailman.cfg i have this setting: Did you restart Mailman after changing this configuration? Make sure `mailman info` confirms you're using the configuration file you think you are. Make sure `mailman conf` confirms the settings. Cheers, -Barry From mark at msapiro.net Sat May 2 18:45:54 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 09:45:54 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: Message-ID: <5544FF42.9040207@msapiro.net> On 05/02/2015 09:07 AM, EyeLand wrote: > Hello, on ?General Options - Default options for new members joining this > list. - Conceal the member's address? > http://i11.pixs.ru:/storage/9/6/1/1JPG_2435911_17190961.jpg > I deactivate check box, but on letter I not see the subscriber email > http://i11.pixs.ru:/storage/9/6/2/2JPG_7009327_17190962.jpg, can you > consult? Thank you. I am unable to see your screen shots - i11.pixs.ru doesn't resolve in my local DNS and if I look up the A records in ns1.nameself.com and use the IP, I get 403 or 404 errors. In any case, unchecking the box only affects the default setting for new members. Changing the boxes on ?General Options - Default options for new members joining this list." has no effect on existing members. Further, that specific option is the "hide" checkbox on the Membership Management... -> Membership List pages which is also the "Conceal yourself from subscriber list?" setting on the user's options page, and the only thing that controls is the presence or absence of that member on the roster (e.g. http://example.com/mailman/roster/listname). Also, since Mailman 2.1.10 all members are shown on the roster regardless of user option if you are authenticated as the list admin or moderator or site admin. Since I can't see your screen shots, I don't know what you mean by "letter", so if the above doesn't answer your question, please give some detail, possibly by copying/pasting text, so we know what the issue is. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Sat May 2 19:08:47 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Sat, 02 May 2015 19:08:47 +0200 Subject: [Mailman-Users] mailman 3.0 and exim In-Reply-To: <20150502121445.44c97647@anarchist.wooz.org> References: <19077190.QKGnMlDpdU@rather> <2295431.EUAHqlSApz@rather> <20150502121445.44c97647@anarchist.wooz.org> Message-ID: <3787580.hrlQMVLEj2@rather> On Saturday 02 May 2015 12:14:45 Barry Warsaw wrote: > On May 01, 2015, at 08:13 PM, Thomas Stein wrote: > >In $home_mailman/var/etc/mailman.cfg i have this setting: > Did you restart Mailman after changing this configuration? > > Make sure `mailman info` confirms you're using the configuration file you > think you are. > > Make sure `mailman conf` confirms the settings. Thanks. After using the right configfile everything works. ciao t. > Cheers, > -Barry > ------------------------------------------------------ > 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/himbeere%40meine-oma. > de From himbeere at meine-oma.de Sat May 2 19:13:30 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Sat, 02 May 2015 19:13:30 +0200 Subject: [Mailman-Users] mailman 3.0 /archives throws error Message-ID: <1823045.BsY6bSZbfd@rather> Hello. Still struggling with mailman3 a little bit. :-) When i try to access /archives i get this error: FilterError at /archives/ module.js:340 throw err; ^ Error: Cannot find module '../lib/less/fs' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object. (/usr/bin/lessc:4:10) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) Request Method: GET Request URL: http://127.0.0.1:8000/archives/ Django Version: 1.7.7 Exception Type: FilterError Exception Value: module.js:340 throw err; nodejs-less is installed (i guess). Does this error come from nodejs-less? Thanks and Ciao t. From ournet.biz at gmail.com Sat May 2 19:23:34 2015 From: ournet.biz at gmail.com (EyeLand) Date: Sat, 2 May 2015 20:23:34 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <5544FF42.9040207@msapiro.net> References: <5544FF42.9040207@msapiro.net> Message-ID: 2015-05-02 19:45 GMT+03:00 Mark Sapiro : > On 05/02/2015 09:07 AM, EyeLand wrote: > > Hello, on ?General Options - Default options for new members joining this > > list. - Conceal the member's address? > > http://i11.pixs.ru:/storage/9/6/1/1JPG_2435911_17190961.jpg > > I deactivate check box, but on letter I not see the subscriber email > > http://i11.pixs.ru:/storage/9/6/2/2JPG_7009327_17190962.jpg, can you > > consult? Thank you. > > > I am unable to see your screen shots - i11.pixs.ru doesn't resolve in my > local DNS and if I look up the A records in ns1.nameself.com and use the > IP, I get 403 or 404 errors. > > In any case, unchecking the box only affects the default setting for new > members. Changing the boxes on ?General Options - Default options for > new members joining this list." has no effect on existing members. > > Further, that specific option is the "hide" checkbox on the Membership > Management... -> Membership List pages which is also the "Conceal > yourself from subscriber list?" setting on the user's options page, and > the only thing that controls is the presence or absence of that member > on the roster (e.g. http://example.com/mailman/roster/listname). > > Also, since Mailman 2.1.10 all members are shown on the roster > regardless of user option if you are authenticated as the list admin or > moderator or site admin. > > Since I can't see your screen shots, I don't know what you mean by > "letter", so if the above doesn't answer your question, please give some > detail, possibly by copying/pasting text, so we know what the issue is. > > -- > 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/ournet.biz%40gmail.com > Not accurately described the problem, I want to display the subscribers email on received letter, look screanshots: https://img-fotki.yandex.ru/get/17840/20871157.78/0_c4066_ebf55cbe_orig https://img-fotki.yandex.ru/get/6846/20871157.78/0_c4067_14e67d7a_orig From lac at openend.se Sat May 2 19:54:58 2015 From: lac at openend.se (Laura Creighton) Date: Sat, 02 May 2015 19:54:58 +0200 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: Message from Mark Sapiro of "Sat, 02 May 2015 09:45:54 -0700." <5544FF42.9040207@msapiro.net> References: <5544FF42.9040207@msapiro.net> Message-ID: <201505021754.t42HswkL028134@fido.openend.se> I can see his screenshots. Reposted here: http://www2.openend.se/~lac/EyeLand/EyeLand.ss1.jpg http://www2.openend.se/~lac/EyeLand/EyeLand.ss2.jpg Let me know if you can see the ones he put up on img-fotki.yandex.ru , If not, I can keep doing this. Though I am having dinner soon ... Laura From mark at msapiro.net Sat May 2 20:03:36 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 11:03:36 -0700 Subject: [Mailman-Users] mailman 3.0 /archives throws error In-Reply-To: <1823045.BsY6bSZbfd@rather> References: <1823045.BsY6bSZbfd@rather> Message-ID: <55451178.1000103@msapiro.net> On 05/02/2015 10:13 AM, Thomas Stein wrote: > > nodejs-less is installed (i guess). Does this error come from nodejs-less? There have been observed conflicts with node-less in some platforms. If you type a bare 'lessc' command you should get a 'help like' response. If you get an unknown command, you may need to install node-less. If you get no response, see the bit in about symlinking 'node' to 'nodejs'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat May 2 20:07:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 11:07:16 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <201505021754.t42HswkL028134@fido.openend.se> References: <5544FF42.9040207@msapiro.net> <201505021754.t42HswkL028134@fido.openend.se> Message-ID: <55451254.9030106@msapiro.net> On 05/02/2015 10:54 AM, Laura Creighton wrote: > I can see his screenshots. Reposted here: > http://www2.openend.se/~lac/EyeLand/EyeLand.ss1.jpg > http://www2.openend.se/~lac/EyeLand/EyeLand.ss2.jpg > > Let me know if you can see the ones he put up on img-fotki.yandex.ru , > If not, I can keep doing this. Though I am having dinner soon ... I can see the second set (although I can't read Russian). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Sat May 2 20:10:01 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 03 May 2015 03:10:01 +0900 Subject: [Mailman-Users] Mailman and dmark help -- please In-Reply-To: <03d101d08419$335ff580$9a1fe080$@comcast.net> References: <03d101d08419$335ff580$9a1fe080$@comcast.net> Message-ID: <87oam2onpi.fsf@uwakimon.sk.tsukuba.ac.jp> Dennis Longnecker writes: > I really -- really want the list set so when someone gets an e-mail > from the list they can see who sent it and when they click reply it > goes to the original sender. Given your user base, the only way to accomplish this is to set your list so that there is *no* header text inserted in the message body, there is *no* footer text appended to the message body, and no list tag or serial number prepended to the Subject field. Then the AOL and Yahoo! DMARC policies won't matter, because the DKIM signatures will continue to verify. From munging can't quite do what you want, IIRC, and Wrapping will definitely cause serious problems for some subscribers and be ugly for all. > AOL Users = Don't Get it I don't know why they don't get any mail, but I suspect that AOL has decided your list is a spam source. You'll have to ask AOL about that. However, mxtoolbox.com says you're not on any blacklists: http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a198.58.94.90&run=toolpage# > E-mail from MSN to list > Comcast Users = DOn't Get it > AOL Users = Don't Get it > Yahoo Users = Don't Get it > users with arvixe accounts = Do Get it. I have no clue about this one. Perhaps it has something to do with the DNS issue described at the very end, but I would think that would mean each recipient would either get all mail or get none. > E-mail from GMAIL to list > Comcast Users = DOn't Get it > AOL Users = Don't Get it > Yahoo Users = Don't Get it > users with arvixe accounts = Do Get it. This has nothing to do with DMARC, as gmail.com has a p=none policy. > E-mail from Comcast to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Do Get it > outlook.com = Do Get it > users with arvixe accounts = Do Get it. This is the expected outcome, comcast.net also has p=none. > E-mail from AOL to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Dont Get it > outlook.com = Dont Get it > users with arvixe accounts = Do Get it. This is semi-expected; I'm surprised that Comcast doesn't respect AOL's p=reject policy. > E-mail from Outlook to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Dont Get it > outlook.com = Dont Get it > users with arvixe accounts = Do Get it. This has nothing to do with DMARC, as gmail.com has a p=none policy. > E-mail from Yahoo to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Do Get it > outlook.com = Do Get it > users with arvixe accounts = Do Get it. This is semi-expected; I'm surprised that Comcast doesn't respect Yahoo!'s p=reject policy. > Any sugestions? My site is troop101-wa.org if looking at its DNS > records could help. Your MX record says to send mail to troop101-wa.org, but the A record says the IP address is 198.58.94.90, and the reverse lookup on the IP resolves to stats.puffin.arvixe.com. I don't know if this is a problem that could cause mail failure or not. You could try changing the MX record to stats.puffin.arvixe.com. From ournet.biz at gmail.com Sat May 2 20:22:14 2015 From: ournet.biz at gmail.com (EyeLand) Date: Sat, 2 May 2015 21:22:14 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <55451254.9030106@msapiro.net> References: <5544FF42.9040207@msapiro.net> <201505021754.t42HswkL028134@fido.openend.se> <55451254.9030106@msapiro.net> Message-ID: 2015-05-02 21:07 GMT+03:00 Mark Sapiro : > On 05/02/2015 10:54 AM, Laura Creighton wrote: > > I can see his screenshots. Reposted here: > > http://www2.openend.se/~lac/EyeLand/EyeLand.ss1.jpg > > http://www2.openend.se/~lac/EyeLand/EyeLand.ss2.jpg > > > > Let me know if you can see the ones he put up on img-fotki.yandex.ru , > > If not, I can keep doing this. Though I am having dinner soon ... > > > I can see the second set (although I can't read Russian). > > -- > 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/ournet.biz%40gmail.com > I translate https://img-fotki.yandex.ru/get/4520/20871157.78/0_c4068_961468d8_orig From mark at msapiro.net Sat May 2 20:23:32 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 11:23:32 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> Message-ID: <55451624.8010500@msapiro.net> On 05/02/2015 10:23 AM, EyeLand wrote: > Not accurately described the problem, I want to display the subscribers > email on received letter, look screanshots: > > https://img-fotki.yandex.ru/get/17840/20871157.78/0_c4066_ebf55cbe_orig > https://img-fotki.yandex.ru/get/6846/20871157.78/0_c4067_14e67d7a_orig The setting on ?General Options - Default options for new members joining this list. - Conceal the member's address? as I explained has nothing to do with this. I can't read the Russian. I do not know in which header you want the member's email, but I'm guessing you want it in To:. If so, this is called Full Personalization. If you do not see the 'personalize' settings on the admin Non-digest options page, see the FAQ . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Sat May 2 20:40:30 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Sat, 02 May 2015 20:40:30 +0200 Subject: [Mailman-Users] mailman 3.0 /archives throws error In-Reply-To: <55451178.1000103@msapiro.net> References: <1823045.BsY6bSZbfd@rather> <55451178.1000103@msapiro.net> Message-ID: <3369058.IGAyzYol26@rather> On Saturday 02 May 2015 11:03:36 Mark Sapiro wrote: > On 05/02/2015 10:13 AM, Thomas Stein wrote: > > nodejs-less is installed (i guess). Does this error come from nodejs-less? > > There have been observed conflicts with node-less in some platforms. If > you type a bare 'lessc' command you should get a 'help like' response. > If you get an unknown command, you may need to install node-less. If you > get no response, see the bit in about > symlinking 'node' to 'nodejs'. Thanks for the link. I reinstalled less with "npm install -g less". After that the error is gone. thanks again and ciao t. From mark at msapiro.net Sat May 2 20:41:55 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 11:41:55 -0700 Subject: [Mailman-Users] Mailman and dmark help -- please In-Reply-To: <03d101d08419$335ff580$9a1fe080$@comcast.net> References: <03d101d08419$335ff580$9a1fe080$@comcast.net> Message-ID: <55451A73.1020301@msapiro.net> Sent previously, but inadvertently to the OP only. Much overlap with Stephen's reply. On 05/01/2015 07:14 AM, Dennis Longnecker wrote: > I have a mailing list setup for our boy scout troop. The site is running > mailman version version 2.1.18-1. I looking at various lists, I believe I > have as much set as I can. > > (Details for from_is_list) = Munge From While it doesn't really say so, from_is_list should be considered deprecated. Use Privacy options... -> Sender filters -> dmarc_moderation_action instead for a less generally disruptive approach. > I really -- really want the list set so when someone gets an e-mail from the > list they can see who sent it and when they click reply it goes to the > original sender. When I have the remove sender option, etc. People don't > know who the e-mail came from or how to directly reply. What remove sender option? Have you set anonymous_list = Yes? > I was reading about some DNS DMARC settings, but frankly it really confused > me. What I have observed: > > E-mail from MSN to list > Comcast Users = DOn't Get it > AOL Users = Don't Get it > Yahoo Users = Don't Get it > users with arvixe accounts = Do Get it. This isn't DMARC. msn.com doesn't publish a DMARC policy. > E-mail from GMAIL to list > Comcast Users = DOn't Get it > AOL Users = Don't Get it > Yahoo Users = Don't Get it > users with arvixe accounts = Do Get it. This isn't DMARC. gmail.com publishes a DMARC p=none policy. > E-mail from Comcast to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Do Get it > outlook.com = Do Get it > users with arvixe accounts = Do Get it. This isn't DMARC. comcast.net publishes a DMARC p=none policy. Also, only AOL doesn't like it. > E-mail from AOL to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Dont Get it > outlook.com = Dont Get it > users with arvixe accounts = Do Get it. aol.com publishes DMARC p=reject. Comcast honors that policy, so whatever DMARC mitigation policy is in effect seems to be working in this case. > E-mail from Outlook to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Dont Get it > outlook.com = Dont Get it > users with arvixe accounts = Do Get it. This isn't DMARC. outlook.com publishes a DMARC p=none policy. > E-mail from Yahoo to list > Comcast Users = DO Get it > AOL Users = Don't Get it > Yahoo Users = Do Get it > outlook.com = Do Get it > users with arvixe accounts = Do Get it. See AOL above. The same things apply to yahoo.com. > Any sugestions? My site is troop101-wa.org if looking at its DNS records > could help. I see you do have an SPF record which is good in general, but won't help with DMARC. You might also consider DKIM signing your outgoing mail which also will help in general but not with DMARC. You clearly have deliverability issues, but they don't seem to be DMARC related. Also, simple From: munging for DMARC should preserve the From: display name or list member's 'real name' in the resulting From: John Doe via list header and put the original From: data in Reply-To: so with an RFC compliant MUA, 'reply' will go to the original From: and 'reply all' will go to the original From: and the list. What are your settings for General Options -> from_is_list anonymous_list first_strip_reply_to reply_goes_to_list reply_to_address For your deliverability, you need to see the server's outgoing MTA logs to see if any of the undelivered mail is rejected at SMTP time and why and also look at Mailman's bounce log to see if mail is otherwise bouncing. You probably have to get your hosting provider to do this if you can. See . Also see for some general information on deliverability. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Sat May 2 21:56:53 2015 From: ournet.biz at gmail.com (EyeLand) Date: Sat, 2 May 2015 22:56:53 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <55451624.8010500@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> Message-ID: 2015-05-02 21:23 GMT+03:00 Mark Sapiro : > On 05/02/2015 10:23 AM, EyeLand wrote: > > > Not accurately described the problem, I want to display the subscribers > > email on received letter, look screanshots: > > > > https://img-fotki.yandex.ru/get/17840/20871157.78/0_c4066_ebf55cbe_orig > > https://img-fotki.yandex.ru/get/6846/20871157.78/0_c4067_14e67d7a_orig > > > The setting on ?General Options - Default options for new members > joining this list. - Conceal the member's address? as I explained has > nothing to do with this. > > I can't read the Russian. I do not know in which header you want the > member's email, but I'm guessing you want it in To:. If so, this is > called Full Personalization. If you do not see the 'personalize' > settings on the admin Non-digest options page, see the FAQ > . > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > I want when subscriber receive mail from mailing list on ?To? was ? user_mail at examble.com? not ?test at list.ournet.biz? From mark at msapiro.net Sat May 2 22:15:25 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 13:15:25 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> Message-ID: <5545305D.4030203@msapiro.net> On 05/02/2015 12:56 PM, EyeLand wrote: > > > 2015-05-02 21:23 GMT+03:00 Mark Sapiro : > > > I can't read the Russian. I do not know in which header you want the > member's email, but I'm guessing you want it in To:. If so, this is > called Full Personalization. If you do not see the 'personalize' > settings on the admin Non-digest options page, see the FAQ > . > > I want when subscriber receive mail from mailing list on ?To? was > ?user_mail at examble.com ? not > ?test at list.ournet.biz ? Yes, and what I said in the above paragraph is how to do that. I.e., Go to the list admin Non-digest options page, and set personalize to Full Personalization. If you do not see the personalize settings on that page, you need to set OWNERS_CAN_ENABLE_PERSONALIZATION = Yes in mm_cfg.py as it says in the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Sat May 2 22:31:17 2015 From: ournet.biz at gmail.com (EyeLand) Date: Sat, 2 May 2015 23:31:17 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <5545305D.4030203@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> Message-ID: 2015-05-02 23:15 GMT+03:00 Mark Sapiro : > On 05/02/2015 12:56 PM, EyeLand wrote: > > > > > > 2015-05-02 21:23 GMT+03:00 Mark Sapiro : > > > > > > I can't read the Russian. I do not know in which header you want the > > member's email, but I'm guessing you want it in To:. If so, this is > > called Full Personalization. If you do not see the 'personalize' > > settings on the admin Non-digest options page, see the FAQ > > . > > > > I want when subscriber receive mail from mailing list on ?To? was > > ?user_mail at examble.com ? not > > ?test at list.ournet.biz ? > > > Yes, and what I said in the above paragraph is how to do that. I.e., Go > to the list admin Non-digest options page, and set personalize to Full > Personalization. If you do not see the personalize settings on that > page, you need to set > > OWNERS_CAN_ENABLE_PERSONALIZATION = Yes > > in mm_cfg.py as it says in the FAQ at . > > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > - Non-digest options page https://img-fotki.yandex.ru/get/17848/20871157.78/0_c4069_fc0260f1_orig - On Debian when I can find file $prefix/Mailman/Defaults.py, $prefix/Mailman/mm_cfg.py ? From mark at msapiro.net Sat May 2 23:32:21 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 02 May 2015 14:32:21 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> Message-ID: <55454265.6010402@msapiro.net> On 05/02/2015 01:31 PM, EyeLand wrote: > - On Debian when I can find file $prefix/Mailman/Defaults.py, > $prefix/Mailman/mm_cfg.py ? As far as I know, in the Debian package, $prefix is /var/lib/mailman, but there may also be a symlink from /usr/lib/mailman/Mailman to /var/lib/mailman/Mailman. If that doesn't help, try locate mm_cfg.py or sudo find / -name mm_cfg.py -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Sun May 3 12:24:43 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Sun, 03 May 2015 12:24:43 +0200 Subject: [Mailman-Users] mailloop exim lmtp Message-ID: <1743836.q4BaZKxO8a@rather> Hola. After having mailman3 installation behind me a first test post seems to lead to a kind of mailloop. mailman smtp.log says: May 03 10:17:37 2015 (24469) <20150503080846.24473.69262 at misc.domain> smtp to goodnews at misc.domain for 1 recips, completed in 0.014857053756713867 seconds May 03 10:17:37 2015 (24469) <20150503080846.24473.69262 at misc.domain> post to goodnews at misc.domain from goodnews-owner at misc.domain, 19631 bytes, 1 failures May 03 10:17:37 2015 (24469) <20150503080846.24473.69262 at misc.domain> delivery to goodnews-owner at misc.domain failed with code 444, [Errno 97] Address family not supported by protocol May 03 10:17:37 2015 (24469) <20150503080846.24473.31080 at misc.domain> low level smtp error: [Errno 97] Address family not supported by protocol May 03 10:17:37 2015 (24469) <20150503080846.24473.31080 at misc.domain> smtp to goodnews at misc.domain for 1 recips, completed in 0.022059917449951172 seconds May 03 10:17:37 2015 (24469) <20150503080846.24473.31080 at misc.domain> post to goodnews at misc.domain from goodnews-owner at misc.domain, 31458 bytes, 1 failures May 03 10:17:37 2015 (24469) <20150503080846.24473.31080 at misc.domain> delivery to goodnews-owner at misc.domain failed with code 444, [Errno 97] Address family not supported by protocol May 03 10:17:37 2015 (24469) <20150503080846.24473.49233 at misc.domain> low level smtp error: [Errno 97] Address family not supported by protocol May 03 10:17:37 2015 (24469) <20150503080846.24473.49233 at misc.domain> smtp to goodnews at misc.domain for 1 recips, completed in 0.014764547348022461 seconds May 03 10:17:37 2015 (24469) <20150503080846.24473.49233 at misc.domain> post to goodnews at misc.domain from goodnews-owner at misc.domain, 19614 bytes, 1 failures May 03 10:17:37 2015 (24469) <20150503080846.24473.49233 at misc.domain> delivery to goodnews-owner at misc.domain failed with code 444, [Errno 97] Address family not supported by protocol May 03 10:17:38 2015 (24469) <20150503080847.24473.74610 at misc.domain> low level smtp error: [Errno 97] Address family not supported by protocol May 03 10:17:38 2015 (24469) <20150503080847.24473.74610 at misc.domain> smtp to goodnews at misc.domain for 1 recips, completed in 0.01850271224975586 seconds May 03 10:17:38 2015 (24469) <20150503080847.24473.74610 at misc.domain> post to goodnews at misc.domain from goodnews-owner at misc.domain, 21954 bytes, 1 failures May 03 10:17:38 2015 (24469) <20150503080847.24473.74610 at misc.domain> delivery to goodnews-owner at misc.domain failed with code 444, [Errno 97] Address family not supported by protocol Exim gives no error. Just a loop between goodnews-bounces and goodnews. What did i wrong this time? :-) thanks and ciao t. From ournet.biz at gmail.com Sun May 3 13:04:47 2015 From: ournet.biz at gmail.com (EyeLand) Date: Sun, 3 May 2015 14:04:47 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <55454265.6010402@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> Message-ID: 2015-05-03 0:32 GMT+03:00 Mark Sapiro : > On 05/02/2015 01:31 PM, EyeLand wrote: > > > - On Debian when I can find file $prefix/Mailman/Defaults.py, > > $prefix/Mailman/mm_cfg.py ? > > > As far as I know, in the Debian package, $prefix is /var/lib/mailman, > but there may also be a symlink from /usr/lib/mailman/Mailman to > /var/lib/mailman/Mailman. > > If that doesn't help, try > > locate mm_cfg.py > > or > > sudo find / -name mm_cfg.py > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > root at vps1:~# locate mm_cfg.py /etc/mailman/mm_cfg.py /etc/mailman/mm_cfg.py~ /usr/lib/mailman/Mailman/mm_cfg.py /usr/lib/mailman/Mailman/mm_cfg.py.dist /usr/lib/mailman/Mailman/mm_cfg.pyc /usr/local/ispconfig/server/conf/mm_cfg.py.master /usr/share/doc/mailman/examples/mm_cfg.py.gz root at vps1:~# sudo find / -name mm_cfg.py /usr/lib/mailman/Mailman/mm_cfg.py /etc/mailman/mm_cfg.py on file /usr/lib/mailman/Mailman/mm_cfg.py https://gist.githubusercontent.com/eyeland/e33c20045867b262d1a2/raw/1bdb433403594c4f1ab2e6c6e12007c8881fefaa/gistfile1.txt I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES From lac at openend.se Sun May 3 14:35:43 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 03 May 2015 14:35:43 +0200 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: Message from EyeLand of "Sun, 03 May 2015 14:04:47 +0300." References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> Message-ID: <201505031235.t43CZhBn031755@fido.openend.se> In a message of Sun, 03 May 2015 14:04:47 +0300, EyeLand writes: >root at vps1:~# sudo find / -name mm_cfg.py >/usr/lib/mailman/Mailman/mm_cfg.py >/etc/mailman/mm_cfg.py > >on file /usr/lib/mailman/Mailman/mm_cfg.py >https://gist.githubusercontent.com/eyeland/e33c20045867b262d1a2/raw/1bdb433403594c4f1ab2e6c6e12007c8881fefaa/gistfile1.txt >I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES on your machine live in /usr/lib/mailman/Mailman/Defaults.py But _never_ _ever_ edit Defaults.py You want to edit /usr/lib/mailman/Mailman/mm_cfg.py and put the values you want changed _there_. Ok? Then you need to go to the list Admin Non-digest options page and set Personalize to Full Personalization. Then you need to restart mailman. And then, we hope, you can come back and tell us that it worked. :) Laura From stephen at xemacs.org Sun May 3 14:41:27 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 03 May 2015 21:41:27 +0900 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> Message-ID: <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> EyeLand writes: > I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES Defaults are set in /usr/lib/mailman/Mailman/Defaults.py on my Debian system. You should not change that file, any changes will be overwritten the next time you upgrade. Instead, add those variables and their new settings to mm_cfg.py From stephen at xemacs.org Sun May 3 14:48:02 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 03 May 2015 21:48:02 +0900 Subject: [Mailman-Users] mailloop exim lmtp In-Reply-To: <1743836.q4BaZKxO8a@rather> References: <1743836.q4BaZKxO8a@rather> Message-ID: <87oam16d4t.fsf@uwakimon.sk.tsukuba.ac.jp> Thomas Stein writes: > Exim gives no error. Just a loop between goodnews-bounces and goodnews. What > did i wrong this time? :-) It appears that Exim can't send mail at all, and so first the error happens in the mailing list, then it tries to send the error information to the list-owner, but that fails the same way ("address faimily not supported by protocol"). Can't say more without seeing your configs. Can you send any mail at all on that host? From lac at openend.se Sun May 3 15:17:25 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 03 May 2015 15:17:25 +0200 Subject: [Mailman-Users] /etc/mailman/mm_cfg.py (was EyeLand's problem) In-Reply-To: Message from EyeLand of "Sun, 03 May 2015 14:04:47 +0300." References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> Message-ID: <201505031317.t43DHPcS000773@fido.openend.se> In poking around debian systems to see if I could shed any light on EyeLand's problem, I ended up with a question. On all the machines I can ssh to, I have an /etc/mailman/mm_cfg.py as well as a /usr/lib (or /var/lib) /mailman/Mailman/mm_cfg.py, and the second is a symbolic link to the first. Why do we have an /etc/mailmand/mm_cfg.py at all? Just curious, Laura From himbeere at meine-oma.de Sun May 3 15:25:12 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Sun, 03 May 2015 15:25:12 +0200 Subject: [Mailman-Users] mailloop exim lmtp In-Reply-To: <87oam16d4t.fsf@uwakimon.sk.tsukuba.ac.jp> References: <1743836.q4BaZKxO8a@rather> <87oam16d4t.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <2440627.IAU8V9vmZD@rather> On Sunday 03 May 2015 21:48:02 Stephen J. Turnbull wrote: > Thomas Stein writes: > > Exim gives no error. Just a loop between goodnews-bounces and goodnews. > > What did i wrong this time? :-) > > It appears that Exim can't send mail at all, and so first the error > happens in the mailing list, then it tries to send the error > information to the list-owner, but that fails the same way ("address > faimily not supported by protocol"). > > Can't say more without seeing your configs. > Can you send any mail at all on that host? Yes. No problems. Here a test via command line. Mailing list is called "more". misc ~ # exim -v more at misc.domain.de From: himbeere at domain.de To: more at misc.domain.de Subject: Test This is a test. LOG: MAIN <= root at misc.domain.de U=root P=local S=362 misc ~ # delivering 1Yoroo-0007Vh-Hd Connecting to localhost [127.0.0.1]:8024 ... connected SMTP<< 220 misc.domain.de Python LMTP runner 1.0 SMTP>> LHLO misc.domain.de SMTP<< 250 misc.domain.de SMTP>> MAIL FROM: SMTP<< 250 OK SMTP>> RCPT TO: SMTP<< 250 OK SMTP>> DATA SMTP<< 354 End data with . SMTP>> writing message and terminating "." SMTP<< 250 Ok SMTP>> QUIT LOG: MAIN => more at misc.domain.de R=mailman3_router T=mailman3_transport H=localhost [127.0.0.1] C="250 Ok" LOG: MAIN Completed So the mail is with mailman now. Mailman smtp.log still the same: May 03 13:13:14 2015 (24469) <20150503111313.24473.30074 at misc.g.de> low level smtp error: [Errno 97] Address family not supported by protocol May 03 13:13:14 2015 (24469) <20150503111313.24473.30074 at misc.g.de> smtp to more at misc.domain.de for 1 recips, completed in 0.0038123130798339844 seconds May 03 13:13:14 2015 (24469) <20150503111313.24473.30074 at misc.g.de> post to more at misc.domain.de from more-bounces at misc.domain.de, 831 bytes, 1 failures May 03 13:13:14 2015 (24469) <20150503111313.24473.30074 at misc.g.de> delivery to himbeere at domain.de failed with code 444, [Errno 97] Address family not supported by protocol May 03 13:13:14 2015 (24469) <20150503111313.24473.98555 at misc.g.de> low level smtp error: [Errno 97] Address family not supported by protocol It seems mailman is unable to send mail. Sending mail as user mailman on the commandline works. Strange. thanks and ciao t. From mark at msapiro.net Sun May 3 16:50:08 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 03 May 2015 07:50:08 -0700 Subject: [Mailman-Users] mailloop exim lmtp In-Reply-To: <2440627.IAU8V9vmZD@rather> References: <1743836.q4BaZKxO8a@rather> <87oam16d4t.fsf@uwakimon.sk.tsukuba.ac.jp> <2440627.IAU8V9vmZD@rather> Message-ID: <554635A0.5030403@msapiro.net> On 05/03/2015 06:25 AM, Thomas Stein wrote: > > It seems mailman is unable to send mail. Sending mail as user mailman on the > commandline works. Strange. These kinds of problems often result because mailman sends via SMTP to (by default) 'localhost' and there is a conflict because for example, the MTA is configured to accept mail from an IPv4 local host (127.0.0.1/n) and not from an IPv6 local host (::1), but 'localhost' is defined in /etc/hosts as the 'wrong' one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun May 3 17:00:36 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 03 May 2015 08:00:36 -0700 Subject: [Mailman-Users] /etc/mailman/mm_cfg.py (was EyeLand's problem) In-Reply-To: <201505031317.t43DHPcS000773@fido.openend.se> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <201505031317.t43DHPcS000773@fido.openend.se> Message-ID: <55463814.9060308@msapiro.net> On 05/03/2015 06:17 AM, Laura Creighton wrote: > In poking around debian systems to see if I could shed any light on > EyeLand's problem, I ended up with a question. On all the machines > I can ssh to, I have an /etc/mailman/mm_cfg.py as well as a > /usr/lib (or /var/lib) /mailman/Mailman/mm_cfg.py, and the second is > a symbolic link to the first. Why do we have an /etc/mailmand/mm_cfg.py > at all? In a word (or acronym), FHS. Actually, AFAIK, the Red Hat (hence CentOS) Mailman package is the only one that does it right. See and the mailman-developers post linked therefrom. Debian (hence Ubuntu) puts things in the FHS recommended places, but everything not in /var/lib/mailman/ is symlinked from there so Mailman itself still thinks everything is in /var/lib/mailman/. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Sun May 3 17:30:45 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Sun, 03 May 2015 17:30:45 +0200 Subject: [Mailman-Users] mailloop exim lmtp In-Reply-To: <554635A0.5030403@msapiro.net> References: <1743836.q4BaZKxO8a@rather> <2440627.IAU8V9vmZD@rather> <554635A0.5030403@msapiro.net> Message-ID: <2038476.kf6PmJ9NCc@rather> On Sunday 03 May 2015 07:50:08 Mark Sapiro wrote: > On 05/03/2015 06:25 AM, Thomas Stein wrote: > > It seems mailman is unable to send mail. Sending mail as user mailman on > > the commandline works. Strange. > > These kinds of problems often result because mailman sends via SMTP to > (by default) 'localhost' and there is a conflict because for example, > the MTA is configured to accept mail from an IPv4 local host > (127.0.0.1/n) and not from an IPv6 local host (::1), but 'localhost' is > defined in /etc/hosts as the 'wrong' one. Thanks for your answer. Changed localhost to 127.0.0.1 in mailman.cfg and now the error is gone. But the mail loop still is in action. It works even better now. :-) I guess i have to keep digging. thanks again and cheers t. From stephen at xemacs.org Mon May 4 02:15:34 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 04 May 2015 09:15:34 +0900 Subject: [Mailman-Users] /etc/mailman/mm_cfg.py In-Reply-To: <55463814.9060308@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <201505031317.t43DHPcS000773@fido.openend.se> <55463814.9060308@msapiro.net> Message-ID: <87mw1l5hax.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > On 05/03/2015 06:17 AM, Laura Creighton wrote: > > On all the machines I can ssh to, I have an > > /etc/mailman/mm_cfg.py as well as a /usr/lib (or /var/lib) > > /mailman/Mailman/mm_cfg.py, and the second is a symbolic link to > > the first. Why do we have an /etc/mailmand/mm_cfg.py at all? > > In a word (or acronym), FHS. > > > Actually, AFAIK, the Red Hat (hence CentOS) Mailman package is the only > one that does it right. I don't understand what you mean by "right". John Dennis's distinction that mm_cfg.py is "executable" and others aren't is bogus AFAICS; there are lots of apparently data-only files that are actually interpreted code (PDF being one of the more powerful and dangerous). What matters here is exceptional treatment of this one file by the PMS. In the case of Red Hat, they cannot simply unpack the archive into place (in practice, noboby does that any more, but that's a different issue); they have to either avoid copying over mm_cfg.py or preserve it and restore it. In Debian, you can just unpack the archive, but then you need to remove the distributed mm_cfg.py and restore the symlink. AFAICS these procedures are basically equivalent, except that both the PMS and the sysadmin have to know something special about Mailman in the Red Hat scheme. Note that in the Debian scheme you can be an old Mailman hand and edit /var/lib/mailman/Mailman/mm_cfg.py, or Debian admins who don't know much about the history of Mailman can just go to the FHS place in /etc/mailman and find mm_cfg.py there. That's an advantage to the Debian scheme AFAICS. Another (minor) advantage is that in the Debian scheme the PMS doesn't have to do anything special to protect the "real" mm_cfg.py, it just never automatically edits anything under /etc. From mark at msapiro.net Mon May 4 03:59:36 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 03 May 2015 18:59:36 -0700 Subject: [Mailman-Users] /etc/mailman/mm_cfg.py In-Reply-To: <87mw1l5hax.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <201505031317.t43DHPcS000773@fido.openend.se> <55463814.9060308@msapiro.net> <87mw1l5hax.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <5546D288.5050406@msapiro.net> On 05/03/2015 05:15 PM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > > Actually, AFAIK, the Red Hat (hence CentOS) Mailman package is the only > > one that does it right. > > I don't understand what you mean by "right". I actually meant 'right' in a much more limited sense. Also, I had actually forgotten John Dennis' whole mm_cfg.py thing and it's 'exceptional' treatment in Red Hat. I agree with what you've said here. I only meant that for the most part Red Hat puts the files where they belong under FHS and teaches Mailman to look for them there. Debian also puts the files where they belong, including putting mm_cfg.py in /etc/mailman/ which I agree is the right place, but Mailman still thinks all the files are in /var/lib/mailman and those that aren't, which is a bunch, are symlinked from there including a symlink from /var/lib/mailman/Mailman to /usr/lib/mailman/Mailman and then a second one from /usr/lib/mailman/Mailman/mm_cfg.py to /etc/mailman/mm_cfg.py. While this all works, and it is arguably better than patching Mailman in ways that make it more difficult to upgrade from source should you want to, it just seems somehow unclean to me, and that's all I meant to say. Does it right was really not the correct characterization, particularly since I'm reminded of Red Hat's mm_cfg.py handling. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Mon May 4 05:40:17 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 04 May 2015 12:40:17 +0900 Subject: [Mailman-Users] /etc/mailman/mm_cfg.py In-Reply-To: <5546D288.5050406@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <201505031317.t43DHPcS000773@fido.openend.se> <55463814.9060308@msapiro.net> <87mw1l5hax.fsf@uwakimon.sk.tsukuba.ac.jp> <5546D288.5050406@msapiro.net> Message-ID: <87egmx57tq.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > Debian also puts the files where they belong, including putting > mm_cfg.py in /etc/mailman/ which I agree is the right place, but Mailman > still thinks all the files are in /var/lib/mailman Ah, OK, I see what you mean. Except IIRC Mailman proper knows the absolute paths to where its list data is. The problem is that the scripts in bin expect relative paths, so the admin wants to cd to /var/lib/mailman and operate from there, thus the link to bin for the admin's convenience, and the scripts in bin expect Mailman to be at ../Mailman, so a link to Mailman is needed too. > While this all works, and it is arguably better than patching > Mailman in ways that make it more difficult to upgrade from source > should you want to, That is a PITA, so let's not even think about anybody doing that! :-) > it just seems somehow unclean to me, and that's all I meant to say. Indeed, I agree with that. I don't see any way to avoid uncleanness, though, given "dynamic linking" (here, importing) of "shared" modules, and the occasional dependency on minor-version-specific idiosyncracies. This particular ugliness is especially useful to admins (although we might want to make sure we reduce or avoid it in Mailman 3)? From eric at phoenixsecure.com Sun May 3 23:54:54 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Sun, 3 May 2015 21:54:54 +0000 Subject: [Mailman-Users] Syslog in Mailman Message-ID: <99ae7f84117e4b768ca6867a394785fc@PhoenixSrv01.phoenixsecure.com> Hi, I have Mailman installed on my Debian and I don't get any message in my syslog server from Mailman. I have exim4 on the same server and I get syslog from it. I have generated some stuff in mailman, like creating a list etc and I see the message in /var/log/mailman/ bounce,error,smtp etc. so I know the message are getting in the log files. Just no syslog. Any idea? I am using Mailman 2.1.18 on Debian 8. Thanks. [cid:45762505-9551-43f5-9158-58708DA84162.jpg] [cid:logo-new.jpg] Eric Lamer CEO Phoenix Secure Inc. [cid:phone.png] 514-914-5599 [cid:printer_and_fax.png] 514-800-2556 [cid:mail_32.png] eric at phoenixsecure.com [cid:button-facebook.png] [cid:button-linkedin.png] [cid:button-twitter.png] [cid:button-youtube.png] [cid:button-google.png] [cid:C44700B8-0227-4717-A5D5-7935D46B0F9D.jpg] From mark at msapiro.net Mon May 4 08:41:15 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 03 May 2015 23:41:15 -0700 Subject: [Mailman-Users] Syslog in Mailman In-Reply-To: <99ae7f84117e4b768ca6867a394785fc@PhoenixSrv01.phoenixsecure.com> References: <99ae7f84117e4b768ca6867a394785fc@PhoenixSrv01.phoenixsecure.com> Message-ID: <5547148B.2070402@msapiro.net> On 05/03/2015 02:54 PM, Eric Lamer wrote: > > I have Mailman installed on my Debian and I don't get any message in my syslog server from Mailman. I have exim4 on the same server and I get syslog from it. Mailman has its own logging facility. It calls it syslog, but it is Mailman's own logging, not the system syslog. > I have generated some stuff in mailman, like creating a list etc and I see the message in /var/log/mailman/ bounce,error,smtp etc. so I know the message are getting in the log files. Just no syslog. Exactly. Mailman logs to it's own files which in a Debian package are in /var/log/mailman. That's the only logging Mailman does. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Mon May 4 09:54:45 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Mon, 04 May 2015 09:54:45 +0200 Subject: [Mailman-Users] python error when try to save a setting Message-ID: <554725C5.6010605@meine-oma.de> Hello. When i try to save a setting --schnipp-- Settings / Message Acceptance Default action to take when a member posts to the list ---> Accept --schnapp-- via pistorius i get: UnboundLocalError at /mailman3/lists/hoppla.domain/settings/message_acceptance local variable 'HTTPError' referenced before assignment Request Method: POST Request URL: http://127.0.0.1:8000/mailman3/lists/hoppla.misc.meine-oma.de/settings/message_acceptance Django Version: 1.7.8 Exception Type: UnboundLocalError Exception Value: local variable 'HTTPError' referenced before assignment Exception Location: /var/www/mailman/eggs/postorius-1.0.1-py2.7.egg/postorius/views/list.py in list_settings, line 787 Python Executable: /var/www/mailman/venv/bin/python2.7 Python Version: 2.7.9 Python Path: ['/var/www/mailman/eggs/Django-1.7.8-py2.7.egg', '/var/www/mailman/eggs/postorius-1.0.1-py2.7.egg', '/var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg', '/var/www/mailman/eggs/Whoosh-2.7.0-py2.7.egg', '/var/www/mailman/eggs/mock-1.0.1-py2.7.egg', '/var/www/mailman/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/var/www/mailman/eggs/djangorecipe-1.11-py2.7.egg', '/var/www/mailman/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/var/www/mailman/venv/lib/python2.7/site-packages', '/var/www/mailman/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/lockfile-0.10.2-py2.7.egg', '/var/www/mailman/eggs/django_extensions-1.5.2-py2.7.egg', '/var/www/mailman/eggs/django_haystack-2.3.1-py2.7.egg', '/var/www/mailman/eggs/enum34-1.0.4-py2.7.egg', '/var/www/mailman/eggs/networkx-1.9.1-py2.7.egg', '/var/www/mailman/eggs/python_dateutil-1.5-py2.7.egg', '/var/www/mailman/eggs/mailmanclient-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_browserid-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_compressor-1.5-py2.7.egg', '/var/www/mailman/eggs/django_paintstore-0.2-py2.7.egg', '/var/www/mailman/eggs/pytz-2015.2-py2.7.egg', '/var/www/mailman/eggs/robot_detection-0.3-py2.7.egg', '/var/www/mailman/eggs/cssmin-0.2.0-py2.7.egg', '/var/www/mailman/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/var/www/mailman/eggs/djangorestframework-3.1.1-py2.7.egg', '/var/www/mailman/eggs/python_social_auth-0.2.7-py2.7.egg', '/var/www/mailman/eggs/django_gravatar2-1.3.0-py2.7.egg', '/var/www/mailman/eggs/six-1.9.0-py2.7.egg', '/var/www/mailman/eggs/decorator-3.4.2-py2.7.egg', '/var/www/mailman/eggs/httplib2-0.9.1-py2.7.egg', '/var/www/mailman/eggs/requests-2.6.2-py2.7.egg', '/var/www/mailman/eggs/django_appconf-1.0.1-py2.7.egg', '/var/www/mailman/eggs/PyJWT-1.1.0-py2.7.egg', '/var/www/mailman/eggs/requests_oauthlib-0.4.2-py2.7.egg', '/var/www/mailman/eggs/oauthlib-0.7.2-py2.7.egg', '/var/www/mailman/eggs/python_openid-2.2.5-py2.7.egg', '/var/www/mailman', '/var/www/mailman/bin', '/var/www/mailman/venv/lib64/python27.zip', '/var/www/mailman/venv/lib64/python2.7', '/var/www/mailman/venv/lib64/python2.7/plat-linux2', '/var/www/mailman/venv/lib64/python2.7/lib-tk', '/var/www/mailman/venv/lib64/python2.7/lib-old', '/var/www/mailman/venv/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7/plat-linux2'] How can i repair this? Thanks and cheers t. From himbeere at meine-oma.de Mon May 4 10:01:57 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Mon, 04 May 2015 10:01:57 +0200 Subject: [Mailman-Users] mailloop exim lmtp In-Reply-To: <2038476.kf6PmJ9NCc@rather> References: <1743836.q4BaZKxO8a@rather> <2440627.IAU8V9vmZD@rather> <554635A0.5030403@msapiro.net> <2038476.kf6PmJ9NCc@rather> Message-ID: <55472775.1050709@meine-oma.de> Am 03.05.15 um 17:30 schrieb Thomas Stein: > On Sunday 03 May 2015 07:50:08 Mark Sapiro wrote: >> On 05/03/2015 06:25 AM, Thomas Stein wrote: >> > It seems mailman is unable to send mail. Sending mail as user mailman on >> > the commandline works. Strange. >> >> These kinds of problems often result because mailman sends via SMTP to >> (by default) 'localhost' and there is a conflict because for example, >> the MTA is configured to accept mail from an IPv4 local host >> (127.0.0.1/n) and not from an IPv6 local host (::1), but 'localhost' is >> defined in /etc/hosts as the 'wrong' one. > > Thanks for your answer. Changed localhost to 127.0.0.1 in mailman.cfg and now > the error is gone. But the mail loop still is in action. It works even better > now. :-) I guess i have to keep digging. After i restarted the virtual machine the mail loop is gone. It was probably a ipv4/ipv6 issue. Can i disable somewhere ipv6 in mailman? thanks and cheers t. From himbeere at meine-oma.de Mon May 4 10:34:08 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Mon, 04 May 2015 10:34:08 +0200 Subject: [Mailman-Users] error when trying to register via hyperkitty Message-ID: <55472F00.80207@meine-oma.de> Hello. When i try to signup via hyperkitty i get: KeyError at /archives/accounts/register/ 'email' Request Method: POST Request URL: http://127.0.0.1:8000/archives/accounts/register/?next=/archives/ Django Version: 1.7.8 Exception Type: KeyError Exception Value: 'email' Exception Location: /var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg/hyperkitty/views/forms.py in clean_username, line 57 Python Executable: /var/www/mailman/venv/bin/python2.7 Python Version: 2.7.9 Python Path: ['/var/www/mailman/eggs/Django-1.7.8-py2.7.egg', '/var/www/mailman/eggs/postorius-1.0.1-py2.7.egg', '/var/www/mailman/eggs/HyperKitty-1.0.0-py2.7.egg', '/var/www/mailman/eggs/Whoosh-2.7.0-py2.7.egg', '/var/www/mailman/eggs/mock-1.0.1-py2.7.egg', '/var/www/mailman/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/var/www/mailman/eggs/djangorecipe-1.11-py2.7.egg', '/var/www/mailman/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/var/www/mailman/venv/lib/python2.7/site-packages', '/var/www/mailman/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/lockfile-0.10.2-py2.7.egg', '/var/www/mailman/eggs/django_extensions-1.5.2-py2.7.egg', '/var/www/mailman/eggs/django_haystack-2.3.1-py2.7.egg', '/var/www/mailman/eggs/enum34-1.0.4-py2.7.egg', '/var/www/mailman/eggs/networkx-1.9.1-py2.7.egg', '/var/www/mailman/eggs/python_dateutil-1.5-py2.7.egg', '/var/www/mailman/eggs/mailmanclient-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_browserid-1.0.0-py2.7.egg', '/var/www/mailman/eggs/django_compressor-1.5-py2.7.egg', '/var/www/mailman/eggs/django_paintstore-0.2-py2.7.egg', '/var/www/mailman/eggs/pytz-2015.2-py2.7.egg', '/var/www/mailman/eggs/robot_detection-0.3-py2.7.egg', '/var/www/mailman/eggs/cssmin-0.2.0-py2.7.egg', '/var/www/mailman/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/var/www/mailman/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/var/www/mailman/eggs/djangorestframework-3.1.1-py2.7.egg', '/var/www/mailman/eggs/python_social_auth-0.2.7-py2.7.egg', '/var/www/mailman/eggs/django_gravatar2-1.3.0-py2.7.egg', '/var/www/mailman/eggs/six-1.9.0-py2.7.egg', '/var/www/mailman/eggs/decorator-3.4.2-py2.7.egg', '/var/www/mailman/eggs/httplib2-0.9.1-py2.7.egg', '/var/www/mailman/eggs/requests-2.6.2-py2.7.egg', '/var/www/mailman/eggs/django_appconf-1.0.1-py2.7.egg', '/var/www/mailman/eggs/PyJWT-1.1.0-py2.7.egg', '/var/www/mailman/eggs/requests_oauthlib-0.4.2-py2.7.egg', '/var/www/mailman/eggs/oauthlib-0.7.2-py2.7.egg', '/var/www/mailman/eggs/python_openid-2.2.5-py2.7.egg', '/var/www/mailman', '/var/www/mailman/bin', '/var/www/mailman/venv/lib64/python27.zip', '/var/www/mailman/venv/lib64/python2.7', '/var/www/mailman/venv/lib64/python2.7/plat-linux2', '/var/www/mailman/venv/lib64/python2.7/lib-tk', '/var/www/mailman/venv/lib64/python2.7/lib-old', '/var/www/mailman/venv/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7/plat-linux2'] I used no special characters for username and email. Any ideas? ciao t. From lac at openend.se Mon May 4 11:05:23 2015 From: lac at openend.se (Laura Creighton) Date: Mon, 04 May 2015 11:05:23 +0200 Subject: [Mailman-Users] Syslog in Mailman In-Reply-To: Message from Eric Lamer of "Sun, 03 May 2015 21:54:54 -0000." <99ae7f84117e4b768ca6867a394785fc@PhoenixSrv01.phoenixsecure.com> References: <99ae7f84117e4b768ca6867a394785fc@PhoenixSrv01.phoenixsecure.com> Message-ID: <201505040905.t4495NrP004156@fido.openend.se> In a message of Sun, 03 May 2015 21:54:54 -0000, Eric Lamer writes: >Hi, > > I have Mailman installed on my Debian and I don't get any message in my syslog server from Mailman. I have exim4 on the same server and I get syslog from it. > > I have generated some stuff in mailman, like creating a list etc and I see the message in /var/log/mailman/ bounce,error,smtp etc. so I know the message are getting in the log files. Just no syslog. > > Any idea? I've seen this. My fix was to reinstall the debian package rsyslog. But there are multiple reasons why this could be happening, and this is only one of them. Laura From lac at openend.se Mon May 4 11:07:59 2015 From: lac at openend.se (Laura Creighton) Date: Mon, 04 May 2015 11:07:59 +0200 Subject: [Mailman-Users] Syslog in Mailman In-Reply-To: Message from Laura Creighton of "Mon, 04 May 2015 11:05:23 +0200." <201505040905.t4495NrP004156@fido.openend.se> References: <99ae7f84117e4b768ca6867a394785fc@PhoenixSrv01.phoenixsecure.com><201505040905.t4495NrP004156@fido.openend.se> Message-ID: <201505040907.t4497x5W004247@fido.openend.se> In a message of Mon, 04 May 2015 11:05:23 +0200, Laura Creighton writes: >In a message of Sun, 03 May 2015 21:54:54 -0000, Eric Lamer writes: >>Hi, >> >> I have Mailman installed on my Debian and I don't get any message in my syslog server from Mailman. I have exim4 on the same server and I get syslog from it. >> >> I have generated some stuff in mailman, like creating a list etc and I see the message in /var/log/mailman/ bounce,error,smtp etc. so I know the message are getting in the log files. Just no syslog. >> >> Any idea? > >I've seen this. My fix was to reinstall the debian package rsyslog. >But there are multiple reasons why this could be happening, and this is >only one of them. > >Laura Aha, I misread the earlier mail. I thought the problem was that nothing was getting written to debians syslog, which isn't a mailman problem, but, ah one I know about. Amazing how your mind grabs the solution you are familiar with even when the problem doesn't fit. At any rate, sorry about that. Treat as an OUT_OF_CAFFINE error or something. Laura From mark at msapiro.net Mon May 4 18:45:18 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 04 May 2015 09:45:18 -0700 Subject: [Mailman-Users] python error when try to save a setting In-Reply-To: <554725C5.6010605@meine-oma.de> References: <554725C5.6010605@meine-oma.de> Message-ID: <5547A21E.3020409@msapiro.net> It is still best to post Mailman 3 related things to mailman-developers at python.org. Most of the people working closely on MM 3 (especially Postorius and HyperKitty) read that list much more regularly than this one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon May 4 18:46:22 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 04 May 2015 09:46:22 -0700 Subject: [Mailman-Users] error when trying to register via hyperkitty In-Reply-To: <55472F00.80207@meine-oma.de> References: <55472F00.80207@meine-oma.de> Message-ID: <5547A25E.5090907@msapiro.net> It is still best to post Mailman 3 related things to mailman-developers at python.org. Most of the people working closely on MM 3 (especially Postorius and HyperKitty) read that list much more regularly than this one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon May 4 20:56:00 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 04 May 2015 11:56:00 -0700 Subject: [Mailman-Users] mailloop exim lmtp In-Reply-To: <55472775.1050709@meine-oma.de> References: <1743836.q4BaZKxO8a@rather> <2440627.IAU8V9vmZD@rather> <554635A0.5030403@msapiro.net> <2038476.kf6PmJ9NCc@rather> <55472775.1050709@meine-oma.de> Message-ID: <5547C0C0.6070602@msapiro.net> On 05/04/2015 01:01 AM, Thomas Stein wrote: > > After i restarted the virtual machine the mail loop is gone. It was > probably a ipv4/ipv6 issue. Can i disable somewhere ipv6 in mailman? Mailman is connecting to the host defined as smtp_host in the [mta] section of your config. The default is 'localhost'. If this causes mailman to try to connect to the MTA at an IPv6 address, it's because localhost is defined as an IPv6 address in /etc/hosts. So you can a) change the definition of smtp_host in your Mailman config to a literal IPv4 address, or b) change the definition of 'localhost' in /etc/hosts to an IPv4 address, or c) change the definition of smtp_host in your Mailman config to whatever name is already defined in /etc/hosts as an IPv4 local host. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Bill.Costa at unh.edu Mon May 4 23:02:17 2015 From: Bill.Costa at unh.edu (Bill.Costa at unh.edu) Date: Mon, 4 May 2015 17:02:17 -0400 (EDT) Subject: [Mailman-Users] Mystery of the site-wide mailing list... Message-ID: I'm migrating our site from ListProc to Mailman and am in the process of wrapping my head around the Mailman way of doing things. For almost 20 years we have had the established email address list.admin at unh.edu as *the* way to contact your friendly local neighborhood mailing list site administrator. ListProc, as part of the list configuration, made it easy to specify this already established address as the single contact point for the site admin for all automatically generated emails. With Mailman I am seeing the convention of using the site-wide mailing list's owner address for contacting the site admin, both in messages for list owners... > From: mailman-owner at lists.unh.edu > To: joe list owner > Subject: Your new mailing list: my.list > > The mailing list `my.list' has just been created for you. The > following is some basic information about your mailing list. : : > Please address all questions to mailman-owner at lists.unh.edu. ...and in messages sent to subscribers.... > From: mailman-owner at lists.unh.edu > To: mary list subscriber > Subject: lists.unh.edu mailing list memberships reminder > > This is a reminder, sent out once a month, about your lists.unh.edu > mailing list memberships. : : > If you have questions, problems, comments, etc, send them to > mailman-owner at lists.unh.edu. Thanks! But if you go to the top-level listinfo web page, you see the suggestion: > If you are having trouble using the lists, please contact > mailman at lists.unh.edu. This address in particular does the user no good since, if configured as suggested, the site-wide mailing list does not accept non-subscriber postings. > From: mailman-owner at lists.unh.edu > To: fred random user > Subject: How do I... > > Your message has been rejected, probably because you are not > subscribed to the mailing list and the list's policy is to > prohibit non-members from posting to it. If you think that > your messages are being rejected in error, contact the mailing > list owner at mailman-owner at lists.unh.edu. I searched the archives for more information about the role of the site-wide mailing list, and found this thread that is related to my issue. It is unanswered as far as I can tell. https://www.mail-archive.com/mailman-users%40python.org/msg25082.html So here is what I want to do. Any place that mailman would direct the user to the site administrator, I would like it to use our long established address for that function, and not mailman-owner, and certainly not the mailman list posting address if that is not what it is suppose to be used for. At this point the only thing I can find that is relevant is changing the name of the site-wide list, but then I would still get the auto-generated email address of "list.admin-owner at lists.unh.edu" which is not desirable, and I would have to open up postings to the world to the site-wise list which does not seem to be the recommended practice. Any help or suggestions would be welcomed. ...BC -- =====================================[ Bill.Costa at unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]== From mark at msapiro.net Tue May 5 01:57:44 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 04 May 2015 16:57:44 -0700 Subject: [Mailman-Users] Mystery of the site-wide mailing list... In-Reply-To: References: Message-ID: <55480778.6050801@msapiro.net> There is a file, sitelist.cfg, in the misc/ directory in the source distribution that gets put in the data/ directory in an installed Mailman. This is intended to be used as input to config_list to configure the site list appropriately. However, some of its settings are not appropriate. Here's how I use and recommend the site list. 1) the members of the list are the site admins. 2) generic_nonmember_action is Accept. This has two good effects. The 'help' address exposed on listinfo and admin overviews works and delivers to an appropriate place, and output from Mailman crons sent to the 'mailman' user actually gets delivered to an appropriate place. Now, you want to use a different address and this can be done but requires some changes. For the address in listinfo, around line 122 in Mailman/Cgi/listinfo.py change siteowner = Utils.get_site_email() to siteowner = 'list.admin at unh.edu' For the admin overview, around line 297 in Mailman/Cgi/admin.py change mailman_owner = Utils.get_site_email() to mailman_owner = 'list.admin at unh.edu' To change the password reminder From: header and the address in the If you have questions, problems, comments, etc, send them to %(owner)s. Thanks! paragraph, at about line 197 in cron/mailpasswds, change siteowner = Utils.get_site_email(host, 'owner') to siteowner = 'list.admin at unh.edu' To change the new list notification From: header and Please address all questions to %(siteowner)s. paragraph, at about line 2646 in bin/newlist, change siteowner = Utils.get_site_email(mlist.host_name, 'owner') to siteowner = 'list.admin at unh.edu' and at about line 243 in Mailman/Cgi/create.py, change siteowner = Utils.get_site_email(mlist.host_name, 'owner') to siteowner = 'list.admin at unh.edu' All the above can also be accomplished by changing the get_site_email() function in Mailman/Utils.py, but that isn't a good idea as the function is used elsewhere. Also, the address in the body of password reminders and new list mail can be changed by creating edited cronpass.txt and newlist.txt templates (see ), but without changing the code, the From: will still be the sitelist-owner address. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at list.org Tue May 5 02:07:57 2015 From: barry at list.org (Barry Warsaw) Date: Mon, 4 May 2015 20:07:57 -0400 Subject: [Mailman-Users] Please consider donating to the GNU Mailman project Message-ID: <20150504200757.546be47a@anarchist.wooz.org> I should have included this in our release announcement. I'd like to remind everyone that GNU Mailman has a directed donation fund set up at the Free Software Foundation. Please consider donating! http://wiki.list.org/x/4816967 This year, we used a portion of our fund to sponsor Abhilash coming to PyCon 2015. Abhilash has been a core developer since his participation in GSoC, and has proven himself to be indispensable across a wide range of the project. We were beyond happy to be able to meet him in person and work with him over the course of the sprints, and we reached the 3.0 release in large part because of his participation at the sprints. Your donations can help with future sprints, user testing, hosting, and more. We're a small team of volunteers and every dollar can help. A portion of your donation also goes to the Free Software Foundation, so you can help two great organizations with one donation. 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 Bill.Costa at unh.edu Tue May 5 15:24:34 2015 From: Bill.Costa at unh.edu (Bill.Costa at unh.edu) Date: Tue, 5 May 2015 09:24:34 -0400 (EDT) Subject: [Mailman-Users] Mystery of the site-wide mailing list... In-Reply-To: <55480778.6050801@msapiro.net> References: <55480778.6050801@msapiro.net> Message-ID: Mark Sapiro recently posted, in part... > Here's how I use and recommend the site list. > > 1) the members of the list are the site admins. > 2) generic_nonmember_action is Accept. Left to my own devices, this is what I would have done, but it seemed to go against the 'official' recommendation. Hearing from an experienced site admin that this is a good practice is a big help.2 > Now, you want to use a different address and this can be done but > requires some changes. While I want to keep the installation as vanilla as possible, I'm not averse to a few well placed hacks. I really appreciate your pointing out the precise locations where these changes need to be applied. > Also, the address in the body of password reminders and new > list mail can be changed ... but without changing the code, > the From: will still be the sitelist-owner address. We can certainly live with that. I noticed there are .py source files and .pyc files which I guessed and confirmed are compiled versions of the source. According to this doc: http://wiki.list.org/DOC/My%20change%20to%20a%20source%20module%20is%20inneffective%3B%20When%20do%20I%20need%20to%20restart%20Mailman%3F?highlight=%28compile%29 or https://tinyurl.com/obxff58 It looks like all I need to do is make the changes to the source and restart Mailman, and we should be all set; new compiled versions will be automatically created as needed. Slick. Thanks so much for site-wide list recommendation and the roadmap for making the site contact customization. ...BC -- =====================================[ Bill.Costa at unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]== From Bill.Costa at unh.edu Tue May 5 15:40:22 2015 From: Bill.Costa at unh.edu (Bill.Costa at unh.edu) Date: Tue, 5 May 2015 09:40:22 -0400 (EDT) Subject: [Mailman-Users] Possible problems using a site-wide list auto-responder? Message-ID: I couldn't seem to find any docs, FAQs or postings on this topic. The auto-responder feature built into Mailman looks like it would be perfect for the site-wide list as a way of letting users know when somebody will be looking at their questions (normal business hours) and to point them to self-help documentation. But since the site-wide list is used for various automated tasks, are there any downsides or cautions in using this feature? I was thinking of turning it on both for the posting address as well as the -owner address. ...BC -- =====================================[ Bill.Costa at unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]== From mark at tafn.org.uk Mon May 4 14:46:55 2015 From: mark at tafn.org.uk (Mark) Date: Mon, 4 May 2015 13:46:55 +0100 Subject: [Mailman-Users] removing your lists from the main lists Message-ID: <77AAAD39A6554695B85198D3C7520C3B@PC> Hi new user i run a mailman lists for a blind group and wondered is there a way of not having the lists listed on the main mailman pageonly this group is for members only and are getting people out side the group trying to post messages to our groups Many thanks Mark. From mark at tafn.org.uk Mon May 4 14:48:32 2015 From: mark at tafn.org.uk (Mark) Date: Mon, 4 May 2015 13:48:32 +0100 Subject: [Mailman-Users] upgrading mailman Message-ID: Hi my linode needs upgrading and i have been told if i upgrade it will break my mailman does any one know if this right mark. From mark at msapiro.net Tue May 5 18:15:43 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 05 May 2015 09:15:43 -0700 Subject: [Mailman-Users] Mystery of the site-wide mailing list... In-Reply-To: References: <55480778.6050801@msapiro.net> Message-ID: <5548ECAF.2060806@msapiro.net> On 05/05/2015 06:24 AM, Bill.Costa at unh.edu wrote: > > I noticed there are .py source files and .pyc files which I > guessed and confirmed are compiled versions of the source. > According to this doc: > > http://wiki.list.org/DOC/My%20change%20to%20a%20source%20module%20is%20inneffective%3B%20When%20do%20I%20need%20to%20restart%20Mailman%3F?highlight=%28compile%29 > > > or https://tinyurl.com/obxff58 If you look at the navigation links on the wiki pages there is a TinyURL link - in the default theme it is in the left sidebar in the middle of the second group in the "Wiki" section. Clicking this link will give a message, "A short link to this page is http://wiki.list.org/x/17891729" in the case of the above page. This is perhaps a bit easier than creating a tinyurl.com link. > It looks like all I need to do is make the changes to the source > and restart Mailman, and we should be all set; new compiled > versions will be automatically created as needed. Slick. Yes, Python will do the right thing. If the .py is newer than the .pyc, it will use the .py and if it has permission, rewrite the .pyc for the next time. > Thanks so much for site-wide list recommendation and the roadmap > for making the site contact customization. You're welcome. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Tue May 5 18:39:57 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 06 May 2015 01:39:57 +0900 Subject: [Mailman-Users] Possible problems using a site-wide list auto-responder? In-Reply-To: References: Message-ID: <87vbg73rmq.fsf@uwakimon.sk.tsukuba.ac.jp> Bill.Costa at unh.edu writes: > The auto-responder feature built into Mailman looks like it would > be perfect for the site-wide list as a way of letting users know > when somebody will be looking at their questions (normal business > hours) and to point them to self-help documentation. Autoresponders are dangerous since they can be used to send mail to anybody simply by forging their address in From (which is trivial to do if you have any knowledge of how mail works). > But since the site-wide list is used for various automated tasks, > are there any downsides or cautions in using this feature? I was > thinking of turning it on both for the posting address as well as > the -owner address. If users are posting fairly frequently, autoresponses can get annoying quite quickly, although you can specify an interval such that within that interval only one autoresponse will be sent, and then the autoresponses are suppressed for that period. However, for the use you describe, I think it would be appreciated as long as the self-help documentation is well-crafted, easy to access, and kept up to date. There is also an "ack" feature for posts, which is per-subscriber. I don't know how customizable the ack message is, but the advantage is that the subscriber controls whether she gets those messages or not. And in your case you may not want ordinary users to be subscribed to that list (but there may be a workaround for that). From mark at msapiro.net Tue May 5 19:06:24 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 05 May 2015 10:06:24 -0700 Subject: [Mailman-Users] Possible problems using a site-wide list auto-responder? In-Reply-To: References: Message-ID: <5548F890.4050105@msapiro.net> On 05/05/2015 06:40 AM, Bill.Costa at unh.edu wrote: > > The auto-responder feature built into Mailman looks like it would > be perfect for the site-wide list as a way of letting users know > when somebody will be looking at their questions (normal business > hours) and to point them to self-help documentation. But since > the site-wide list is used for various automated tasks, are there > any downsides or cautions in using this feature? I was thinking > of turning it on both for the posting address as well as the > -owner address. There should no problem at all using it for the posting address or the -owner address. There are various notices from the list to the owner, e.g. bounce notifications, posts requiring moderation, etc. that are actually sent to the -owner address before being resent from there to the owners/moderators. You don't want auto responses to those, but that's covered in that the auto responder won't reply to messages with Precedence: bulk, junk or list, and all Mailman generated notices are sent with Precedence: bulk or list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue May 5 19:12:59 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 05 May 2015 10:12:59 -0700 Subject: [Mailman-Users] removing your lists from the main lists In-Reply-To: <77AAAD39A6554695B85198D3C7520C3B@PC> References: <77AAAD39A6554695B85198D3C7520C3B@PC> Message-ID: <5548FA1B.2080501@msapiro.net> On 05/04/2015 05:46 AM, Mark wrote: > Hi new user i run a mailman lists for a blind group and wondered is there a way of not having the lists listed on the main mailman pageonly this group is for members only and are getting people out side the group trying to post messages to our groups In the list's web admin interface, set Privacy options... -> Subscription rules -> advertised to No. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue May 5 19:22:40 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 05 May 2015 10:22:40 -0700 Subject: [Mailman-Users] upgrading mailman In-Reply-To: References: Message-ID: <5548FC60.6040203@msapiro.net> On 05/04/2015 05:48 AM, Mark wrote: > Hi my linode needs upgrading and i have been told if i upgrade it will break my mailman does any one know if this right It probably depends on exactly how you installed Mailman (package, source, ??) and if you have any patches to your Mailman. If you do everything as recommended, i.e. never change Defaults.py but make your changes in mm_cfg.py; don't edit templates but create site/domain/list specific versions via the web admin UI or as described in the FAQ at , an upgrade shouldn't break Mailman, but you also need to be aware of what an upgrade might do to the Mailman related things in the web server and MTA. Backup!!! -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From drew.tenenholz at isid.org Tue May 5 21:22:28 2015 From: drew.tenenholz at isid.org (Drew Tenenholz) Date: Tue, 5 May 2015 15:22:28 -0400 Subject: [Mailman-Users] Help with ONE broken list (Mailman 2.1.9) Message-ID: Hi all -- I'm hoping you can make some suggestions on hot to get a broken list working again. Here's the basic details. Mailman 2.1.9 RHEL 5.x I have root access to the VM running our lists. The problem was caused by an IT Dept. standard RHEL update on April 21. Somehow, this update managed to revert some file back to an earlier state, breaking just ONE of my lists. This was a list I migrated from a different mailman server on March 31 (v2.1.14 installed from source on Mac OS X - so not the Apple distribution). All of the other lists which were in place before March 31 are just fine. For certain, /var/lib/mailman/data/aliases was replaced with an earlier version (I can't tell you how long it took to find this out....), and the newest aliases from the migration were removed. So, I replaced them, and restarted both mailman and postfix, but no joy. Now, I've been struggling through trying to get the rest of the configuration to work. Here are some sample problems: 1) http://list.name.tld/mailman/admin/list-name/general page will not load, giving the "Oops, we've hit a bug" mailman/python error. Oddly enough, I can manually type in the correct URL for things like the list members or language options and those pages DO load. 2) I've probably broken a lot of common sense rules, but I've replaced the /var/lib/mailman/lists/list-name/config.pck file with the one I used during the migration. That not only doesn't fix the list, it seems to reset the list admin password (which i can now fix with change_pw), the URL (which I can fix with bin/withlist -l -r fix_url list-name -v). but, as I said, the list is still showing all the problems as before. 3) For unknown reasons, /bin/config_list -o will not complete. So, I got the IT folks to actually restore a snapshot of the machine to a DIFFERENT VM, and frustratingly enough, that version of the list seems to work fine. I can even copy over the config.pck from the damaged list into this April 4 snapshot, and it WORKS! (Grrr....) I can also export the configuration from this newly restored and munged setup back onto the production machine, and it FAILS. On the production machine, bin/check_db and bin/check_perms both run without reporting any problems. If it makes any difference at all, this list is set to run with RUSSIAN CYRILLIC (KOI8-R) as the default language, so when I export the members list with full names, all I get are ???. I'd prefer to not only have the working list, but working archives, and the correct subscriber list as of the date things started to go worky. Then, I hope to restore all of the shunted messages that were clogging up the entire system most of which were pending messages for the damaged list, and clear out that queue. If you have gotten this far: 1) THANK YOU. 2) As you can see, this is a VERY ACTIVE mailman install. It probably sends 500,000 mails/day to 70,000 subscribers on 12-15 lists, and also has to handle 50-100 confirmation requests/day with people constantly adding/removing themselves. Sort of like trying to sip out of a fire hose.... Thinks in Advance, Drew Tenenholz From drew.tenenholz at isid.org Tue May 5 21:51:26 2015 From: drew.tenenholz at isid.org (drew.tenenholz at isid.org) Date: Tue, 05 May 2015 15:51:26 -0400 Subject: [Mailman-Users] Help with ONE broken list (Mailman 2.1.9) P.S. In-Reply-To: References: Message-ID: <20150505155126.Horde.vCiKMWDWbMH6gB66qoyYDQ1@agamemnon.swishmail.com> P.S. If this error message helps, here is something that doesn't work on the production machine but is fine on the development one: root# ./config_list -v -i /path_to_file/config_from_previous_date list-name Traceback (most recent call last): File "./config_list", line 362, in ? main() File "./config_list", line 357, in main do_input(listname, infile, checkonly, verbose) File "./config_list", line 258, in do_input guibyprop = getPropertyMap(mlist) File "./config_list", line 230, in getPropertyMap for element in gui.GetConfigInfo(mlist, category, subcat): File "/usr/lib/mailman/Mailman/Gui/Privacy.py", line 162, in GetConfigInfo if mlist.dmarc_quarantine_moderation_action: File "/usr/lib/mailman/Mailman/MailList.py", line 146, in __getattr__ raise AttributeError, name AttributeError: dmarc_quarantine_moderation_action -- Drew From mark at msapiro.net Wed May 6 00:09:48 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 05 May 2015 15:09:48 -0700 Subject: [Mailman-Users] Help with ONE broken list (Mailman 2.1.9) P.S. In-Reply-To: <20150505155126.Horde.vCiKMWDWbMH6gB66qoyYDQ1@agamemnon.swishmail.com> References: <20150505155126.Horde.vCiKMWDWbMH6gB66qoyYDQ1@agamemnon.swishmail.com> Message-ID: <55493FAC.6090502@msapiro.net> On 05/05/2015 12:51 PM, drew.tenenholz at isid.org wrote: > P.S. > > If this error message helps, here is something that doesn't work on the > production machine but is fine on the development one: > > root# ./config_list -v -i /path_to_file/config_from_previous_date list-name > Traceback (most recent call last): > File "./config_list", line 362, in ? > main() > File "./config_list", line 357, in main > do_input(listname, infile, checkonly, verbose) > File "./config_list", line 258, in do_input > guibyprop = getPropertyMap(mlist) > File "./config_list", line 230, in getPropertyMap > for element in gui.GetConfigInfo(mlist, category, subcat): > File "/usr/lib/mailman/Mailman/Gui/Privacy.py", line 162, in > GetConfigInfo > if mlist.dmarc_quarantine_moderation_action: > File "/usr/lib/mailman/Mailman/MailList.py", line 146, in __getattr__ > raise AttributeError, name > AttributeError: dmarc_quarantine_moderation_action I'm a bit confused, but I think I understand. You say this is Mailman 2.1.9, but the above traceback says /usr/lib/mailman/Mailman/Gui/Privacy.py defines a list attribute dmarc_quarantine_moderation_action which didn't exist before 2.1.18. My best guess is something backported the DMARC mitigations into your Mailman 2.1.9 and also included code in Mailman/versions.py to update older lists, but whether or not a list gets updated by this process depends on the list's data_version being less than the DATA_FILE_VERSION defined in Mailman/Version.py. So, still guessing but, the backport incremented DATA_FILE_VERSION so all the existing lists got updated except the list that came from the 2.1.14 Mailman that already had a data_version >= the new DATA_FILE_VERSION. To fix this, do the following: bin/withlist -l problem_list_name (responses from withlist ending with prompt) >>> m.data_version = 1 >>> m.Save() >>> <- control-D here to exit If I am correct, that will fix the problem, and If it is something else, no harm will be done. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fsantiago at garden-life.org Wed May 6 03:45:32 2015 From: fsantiago at garden-life.org (Fabian Santiago) Date: Tue, 5 May 2015 21:45:32 -0400 Subject: [Mailman-Users] Newer mailman version for cos 6.6 Message-ID: <3561691663525349330@unknownmsgid> Does anyone out there know where to find an rpm for a newer if not the most current version of mailman that'll run in cos 6.6? I'm looking for something newer than what's in the official repo. Sincerely, Fabian Santiago Sent from my iPhone From mark at tafn.org.uk Wed May 6 18:55:49 2015 From: mark at tafn.org.uk (Mark) Date: Wed, 6 May 2015 17:55:49 +0100 Subject: [Mailman-Users] Archive problem Message-ID: Good after noon, i have a Archived list but if i go to my Archives it ses no messages have been posted yet this is not troo only they are being posted can any one help the list is set to private Archive many thanks mark. From mark at msapiro.net Wed May 6 19:21:04 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 06 May 2015 10:21:04 -0700 Subject: [Mailman-Users] Archive problem In-Reply-To: References: Message-ID: <554A4D80.2040601@msapiro.net> On 05/06/2015 09:55 AM, Mark wrote: > Good after noon, > i have a Archived list but if i go to my Archives it ses no messages have been posted yet > this is not troo only they are being posted can any one help > the list is set to private Archive Are messages being posted and delivered to the list? If so, is Mailman's ArchRunner running on the server - i.e. does ps -fwwA|grep [A]rchRunner show something like mailman 14297 14295 0 May01 ? 00:00:45 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s If ArchRunner is running, what's in Mailman's error log on the server. If not, try stopping and starting Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From eric at phoenixsecure.com Wed May 6 19:33:21 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Wed, 6 May 2015 17:33:21 +0000 Subject: [Mailman-Users] Mailman on CentOs Message-ID: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> ?Hi, Can I install Mailman on CentOs 6.5? Thanks. [cid:45762505-9551-43f5-9158-58708DA84162.jpg] [cid:logo-new.jpg] Eric Lamer CEO Phoenix Secure Inc. [cid:phone.png] 514-914-5599 [cid:printer_and_fax.png] 514-800-2556 [cid:mail_32.png] eric at phoenixsecure.com [cid:button-facebook.png] [cid:button-linkedin.png] [cid:button-twitter.png] [cid:button-youtube.png] [cid:button-google.png] [cid:C44700B8-0227-4717-A5D5-7935D46B0F9D.jpg] From mark at msapiro.net Thu May 7 19:09:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 10:09:06 -0700 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> Message-ID: <554B9C32.1030700@msapiro.net> On 05/06/2015 10:33 AM, Eric Lamer wrote: > > Can I install Mailman on CentOs 6.5? There's no technical reason why not. I run my production 'head of the branch' Mailman on CentOS 5.0 (soon to be replaced with an Ubuntu 14.04 box). I think the Python that comes with CentOS 6.5 is Python 2.6.6 which should be OK. In my case, I have Python 2.7.9 installed along side the CentOS 5.0 default Python 2.4.3 (you can't just upgrade Python on RHEL/CentOS -it breaks things). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From drew.tenenholz at isid.org Thu May 7 19:11:07 2015 From: drew.tenenholz at isid.org (Drew Tenenholz) Date: Thu, 7 May 2015 13:11:07 -0400 Subject: [Mailman-Users] Help with ONE broken list (Mailman 2.1.9) - part 2 In-Reply-To: <55493FAC.6090502@msapiro.net> References: <20150505155126.Horde.vCiKMWDWbMH6gB66qoyYDQ1@agamemnon.swishmail.com> <55493FAC.6090502@msapiro.net> Message-ID: At 3:09 PM -0700 5/5/15, Mark Sapiro wrote: >I'm a bit confused, but I think I understand. You say this is Mailman >2.1.9, but the above traceback says >/usr/lib/mailman/Mailman/Gui/Privacy.py defines a list attribute >dmarc_quarantine_moderation_action which didn't exist before 2.1.18. > >My best guess is something backported the DMARC mitigations into your >Mailman 2.1.9 and also included code in Mailman/versions.py to update >older lists, but whether or not a list gets updated by this process >depends on the list's data_version being less than the DATA_FILE_VERSION >defined in Mailman/Version.py. > >So, still guessing but, the backport incremented DATA_FILE_VERSION so >all the existing lists got updated except the list that came from the >2.1.14 Mailman that already had a data_version >= the new DATA_FILE_VERSION. > >To fix this, do the following: > >bin/withlist -l problem_list_name >(responses from withlist ending with prompt) >>>> m.data_version = 1 >>>> m.Save() > >>> <- control-D here to exit > >If I am correct, that will fix the problem, and If it is something else, >no harm will be done. Mark -- Thanks for the suggestion. I did try it, and it actually did make things worse, though I've been able to get back to the previous (yet still broken) state. It appears to me that something within /lib/mailman/lists/problem-list/config.pck is the problem child. I'd be happy to remove and re-create the list with good settings. But I _must_ have the subscribers including their bounce status, digest-status, the real-names they've entered through the Mailman confirmation page, etc.etc. Is there a way to do this in Mailman 2.1.9? (Remembering that I have a working version of the list on a restored snapshot of the server, where everthing actually does work.) I say this based on the results of applying the change Mark suggested, and recovering from the troubles it caused. Sorry to include all the gory details below, and thanks to anyone who is brave enough to read to the end.... Thanks Again, Drew Tenenholz Before applying the change Mark suggested, I thought I'd at least capture what /Mailman.Versions.py actually says: [root]# more /usr/lib/mailman/Mailman/Version.py # Copyright (C) 1998-2006 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. # Mailman version VERSION = "2.1.9" # And as a hex number in the manner of PY_VERSION_HEX ALPHA = 0xa BETA = 0xb GAMMA = 0xc # release candidates RC = GAMMA FINAL = 0xf MAJOR_REV = 2 MINOR_REV = 1 MICRO_REV = 9 REL_LEVEL = FINAL # at most 15 beta releases! REL_SERIAL = 0 HEX_VERSION = ((MAJOR_REV << 24) | (MINOR_REV << 16) | (MICRO_REV << 8) | (REL_LEVEL << 4) | (REL_SERIAL << 0)) # config.pck schema version number DATA_FILE_VERSION = 97 # qfile/*.db schema version number QFILE_SCHEMA_VERSION = 3 # version number for the lists//pending.db file schema PENDING_FILE_SCHEMA_VERSION = 2 # version number for the lists//request.db file schema REQUESTS_FILE_SCHEMA_VERSION = 1 After applying the change to the one list, I got this: [root]# bin/withlist -l problem-list {enter m.data_version change here....} Loading list promed-rus (locked) Traceback (most recent call last): File "./withlist", line 297, in ? main() File "./withlist", line 275, in main r = do_list(listname, args, func) File "./withlist", line 194, in do_list m = MailList.MailList(listname, lock=LOCK) File "/usr/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/usr/lib/mailman/Mailman/MailList.py", line 165, in Lock self.Load() File "/usr/lib/mailman/Mailman/MailList.py", line 670, in Load self.CheckVersion(dict) File "/usr/lib/mailman/Mailman/MailList.py", line 723, in CheckVersion Update(self, stored_state) File "/usr/lib/mailman/Mailman/versions.py", line 51, in Update UpdateOldVars(l, stored_state) File "/usr/lib/mailman/Mailman/versions.py", line 264, in UpdateOldVars elif l.data_version <= 10 and l.posters: File "/usr/lib/mailman/Mailman/MailList.py", line 146, in __getattr__ raise AttributeError, name AttributeError: posters Furthermore, even the simple URL http://list.server.tld/mailman/listinfo threw a Python error, and bin/list_lists errored as well: [root]# bin/list_lists Traceback (most recent call last): File "./list_lists", line 122, in ? main() File "./list_lists", line 94, in main mlist = MailList.MailList(n, lock=0) File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/usr/lib/mailman/Mailman/MailList.py", line 670, in Load self.CheckVersion(dict) File "/usr/lib/mailman/Mailman/MailList.py", line 723, in CheckVersion Update(self, stored_state) File "/usr/lib/mailman/Mailman/versions.py", line 51, in Update UpdateOldVars(l, stored_state) File "/usr/lib/mailman/Mailman/versions.py", line 264, in UpdateOldVars elif l.data_version <= 10 and l.posters: File "/usr/lib/mailman/Mailman/MailList.py", line 146, in __getattr__ raise AttributeError, name AttributeError: posters So, I decided to try and get back to a working state by deleting the problem list with bin/rmlist problem-list. THIS WORKED. Then, I re-created the list with the same name, knowing that the archives would be re-linked, but of course, the settings would need to be imported. What I then did was to diff the settings from the broken list (which I can get them from the restored snapshot of the server before it was updated) with the current settings for a different, completely working list. I saw only two sections that were different, and to my surprise, the WORKING list has the dmarc references and the BROKEN list does not. So, I inserted two sections (below) into the output of config_list -o of the BROKEN list. # Several protocols now in wide use attempt to ensure that use of the # domain in the author's address (ie, in the From: header field) is # authorized by that domain. These protocols may be incompatible with # common list features such as footers, causing participating email # services to bounce list traffic merely because of the address in the # From: field. This has resulted in members being unsubscribed despite # being perfectly able to receive mail. # # The following actions are applied to all list messages when selected # here. To apply these actions only to messages where the domain in the # From: header is determined to use such a protocol, see the # dmarc_moderation_action settings under Privacy options... -> Sender # filters. Settings: # # No Do nothing special. This is appropriate for anonymous lists. It is # appropriate for dedicated announcement lists, unless the From: address # of authorized posters might be in a domain with a DMARC or similar # policy. It is also appropriate if you choose to use # dmarc_moderation_action other than Accept for this list. Munge From # This action replaces the poster's address in the From: header with the # list's posting address and adds the poster's address to the addresses # in the original Reply-To: header. Wrap Message Just wrap the message # in an outer message with the From: header containing the list's # posting address and with the original From: address added to the # addresses in the original Reply-To: header and with Content-Type: # message/rfc822. This is effectively a one message MIME format digest. # # The transformations for anonymous_list are applied before any of these # actions. It is not useful to apply actions other than No to an # anonymous list, and if you do so, the result may be surprising. The # Reply-To: header munging actions below interact with these actions as # follows: # first_strip_reply_to = Yes will remove all the incoming # Reply-To: addresses but will still add the poster's address to # Reply-To: for all three settings of reply_goes_to_list which # respectively will result in just the poster's address, the poster's # address and the list posting address or the poster's address and the # explicit reply_to_address in the outgoing Reply-To: header. If # first_strip_reply_to = No the poster's address in the original From: # header, if not already included in the Reply-To:, will be added to any # existing Reply-To: address(es). These actions, whether selected here # or via # dmarc_moderation_action, do not apply to messages in digests or # archives or sent to usenet via the Mail<->News gateways. If # dmarc_moderation_action applies to this message with an action other # than Accept, that action rather than this is applied # # legal values are: # 0 = "No" # 1 = "Munge From" # 2 = "Wrap Message" from_is_list = 0 and # Munge From -- applies the from_is_list Munge From # transformation to these messages. # # Wrap Message -- applies the from_is_list Wrap Message # transformation to these messages. # # Reject -- this automatically rejects the message by sending a bounce # notice to the post's author. The text of the bounce notice can be configured by # you. # # Discard -- this simply discards the message, with no notice sent to # the post's author. # # # This setting takes precedence over the from_is_list setting if the # message is From: an affected domain and the setting is other than # Accept. # # legal values are: # 0 = "Accept" # 1 = "Munge From" # 2 = "Wrap Message" # 3 = "Reject" # 4 = "Discard" dmarc_moderation_action = 0 # No -- this applies dmarc_moderation_action to only those posts From: a # domain with DMARC p=reject. This is appropriate if you are concerned # about bounced messages, but want to apply dmarc_moderation_action to # as few messages as possible. Yes -- this applies # dmarc_moderation_action to posts From: a domain with DMARC p=reject or # p=quarantine. If a message is From: a domain with DMARC p=quarantine # and dmarc_moderation_action is not applied (this set to No) the # message will likely not bounce, but will be delivered to recipients' # spam folders or other hard to find places. # # legal values are: # 0 = "No" # 1 = "Yes" dmarc_quarantine_moderation_action = True # Text to include in any rejection # notice to be sent to anyone who posts to this list from a domain with # a DMARC Reject/Quarantine Policy. dmarc_moderation_notice = '' I then used bin/config_list -v -i /path-to-folder/updated_settings problem-list -v and got a result with NO ERRORS! (minor Hooray here!) When I try to access the list, the http://mailman.server.tld/mailman/admin/promed-mod/general page loads just fine and the list would seem to have the appearance of working. But, of course, the subscriber list and their individual settings are completely missing. (not a surprise, once I thought about it.) So, I did a slightly rude restoration of the list members by overwriting /var/lib/mailman/lists/broken-list/config.pck with a copy of the same file from before the damage occurred. I made sure mailman was stopped, and manually corrected file permissions before restarting mailman. And, just like that, my problems have been restored, along with the subscribers. So, it would appear that something within /lib/mailman/lists/problem-list/config.pck is the problem child. I'd be happy to remove and re-create the list with good settings. But I _must_ have the subscribers including their bounce status, digest-status, the real-names they've entered through the Mailman confirmation page, etc.etc. Is there a way to do this in Mailman 2.1.9? (Remembering that I have a working version of the list on a restored snapshot of the server, where everything actually does work.) Thanks Again, Drew Tenenholz From mark at msapiro.net Thu May 7 19:31:29 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 10:31:29 -0700 Subject: [Mailman-Users] Help with ONE broken list (Mailman 2.1.9) - part 2 In-Reply-To: References: <20150505155126.Horde.vCiKMWDWbMH6gB66qoyYDQ1@agamemnon.swishmail.com> <55493FAC.6090502@msapiro.net> Message-ID: <554BA171.7020501@msapiro.net> On 05/07/2015 10:11 AM, Drew Tenenholz wrote: > > Thanks for the suggestion. I did try it, and it actually did make things worse, though I've been able to get back to the previous (yet still broken) state. My mistake. I thought setting data_version to 1 would be OK and it was simpler than having you look things up. Sorry ... ... > # config.pck schema version number > DATA_FILE_VERSION = 97 OK. > After applying the change to the one list, I got this: > > [root]# bin/withlist -l problem-list > {enter m.data_version change here....} > > Loading list promed-rus (locked) > Traceback (most recent call last): > File "./withlist", line 297, in ? > main() > File "./withlist", line 275, in main > r = do_list(listname, args, func) > File "./withlist", line 194, in do_list > m = MailList.MailList(listname, lock=LOCK) > File "/usr/lib/mailman/Mailman/MailList.py", line 128, in __init__ > self.Lock() > File "/usr/lib/mailman/Mailman/MailList.py", line 165, in Lock > self.Load() > File "/usr/lib/mailman/Mailman/MailList.py", line 670, in Load > self.CheckVersion(dict) > File "/usr/lib/mailman/Mailman/MailList.py", line 723, in CheckVersion > Update(self, stored_state) > File "/usr/lib/mailman/Mailman/versions.py", line 51, in Update > UpdateOldVars(l, stored_state) > File "/usr/lib/mailman/Mailman/versions.py", line 264, in UpdateOldVars > elif l.data_version <= 10 and l.posters: > File "/usr/lib/mailman/Mailman/MailList.py", line 146, in __getattr__ > raise AttributeError, name > AttributeError: posters As I said, I thought it would be OK, but you get this if data_version is <= 10. So you need to set it bigger than that. Actually, in your case, anything between 11 and 96 will do, but set it to 96. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From himbeere at meine-oma.de Thu May 7 20:33:55 2015 From: himbeere at meine-oma.de (Thomas Stein) Date: Thu, 07 May 2015 20:33:55 +0200 Subject: [Mailman-Users] subscribe page Message-ID: <1753769.gdvUnK3MZx@rather> Hello. I am trying to find the setting in postorius to allow a user to subscribe to a mailing list on its own. All i see is "You have to log in to subscribe to this list." thanks for any hints. cheers t. From addw at phcomp.co.uk Fri May 8 00:18:29 2015 From: addw at phcomp.co.uk (Alain Williams) Date: Thu, 7 May 2015 23:18:29 +0100 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <554B9C32.1030700@msapiro.net> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> Message-ID: <20150507221829.GD23728@phcomp.co.uk> On Thu, May 07, 2015 at 10:09:06AM -0700, Mark Sapiro wrote: > On 05/06/2015 10:33 AM, Eric Lamer wrote: > > > > Can I install Mailman on CentOs 6.5? > > > There's no technical reason why not. There is an RPM, so: yum install mailman -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include From mark at msapiro.net Fri May 8 01:10:09 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 16:10:09 -0700 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <20150507221829.GD23728@phcomp.co.uk> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> Message-ID: <554BF0D1.6090005@msapiro.net> On 05/07/2015 03:18 PM, Alain Williams wrote: > On Thu, May 07, 2015 at 10:09:06AM -0700, Mark Sapiro wrote: >> On 05/06/2015 10:33 AM, Eric Lamer wrote: >>> >>> Can I install Mailman on CentOs 6.5? >> >> >> There's no technical reason why not. > > There is an RPM, so: > > yum install mailman I assumed, perhaps erroneously, that he was asking about installing the current version (2.1.20) from source rather than the Red Hat/CentOS package version (2.1.12 - 6 years old?) that yum will install. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From addw at phcomp.co.uk Fri May 8 01:25:56 2015 From: addw at phcomp.co.uk (Alain Williams) Date: Fri, 8 May 2015 00:25:56 +0100 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <554BF0D1.6090005@msapiro.net> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> Message-ID: <20150507232556.GE23728@phcomp.co.uk> On Thu, May 07, 2015 at 04:10:09PM -0700, Mark Sapiro wrote: > On 05/07/2015 03:18 PM, Alain Williams wrote: > > On Thu, May 07, 2015 at 10:09:06AM -0700, Mark Sapiro wrote: > >> On 05/06/2015 10:33 AM, Eric Lamer wrote: > >>> > >>> Can I install Mailman on CentOs 6.5? > >> > >> > >> There's no technical reason why not. > > > > There is an RPM, so: > > > > yum install mailman > > > I assumed, perhaps erroneously, that he was asking about installing the > current version (2.1.20) from source rather than the Red Hat/CentOS > package version (2.1.12 - 6 years old?) that yum will install. It is not hard to do. In fact it is what I do (ie not use the RPM version) this is because I have the same list name in different domains. Unpack and run something like: ./configure --prefix=/usr/local/mailman/example.org --with-var-prefix=/var/spool/mailman/example.org --with-cgi-gid=apache --with-mailhost=lists.example.org --with-urlhost=lists.example.org I will shortly try to install MM3 on CentOS 7 ... the biggest issue looks to be that it does not have a version of python that is new enough - so the first thing to fix. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include From eric at phoenixsecure.com Fri May 8 03:01:48 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 01:01:48 +0000 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <20150507232556.GE23728@phcomp.co.uk> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> Message-ID: <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> I tried to upgrade to version 2.1.20 or 2.1.18 and I have a lot of problems, io error etc. EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+eric=phoenixsecure.com at python.org] On Behalf Of Alain Williams Sent: Thursday, May 7, 2015 7:26 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Mailman on CentOs On Thu, May 07, 2015 at 04:10:09PM -0700, Mark Sapiro wrote: > On 05/07/2015 03:18 PM, Alain Williams wrote: > > On Thu, May 07, 2015 at 10:09:06AM -0700, Mark Sapiro wrote: > >> On 05/06/2015 10:33 AM, Eric Lamer wrote: > >>> > >>> Can I install Mailman on CentOs 6.5? > >> > >> > >> There's no technical reason why not. > > > > There is an RPM, so: > > > > yum install mailman > > > I assumed, perhaps erroneously, that he was asking about installing > the current version (2.1.20) from source rather than the Red > Hat/CentOS package version (2.1.12 - 6 years old?) that yum will install. It is not hard to do. In fact it is what I do (ie not use the RPM version) this is because I have the same list name in different domains. Unpack and run something like: ./configure --prefix=/usr/local/mailman/example.org --with-var-prefix=/var/spool/mailman/example.org --with-cgi-gid=apache --with-mailhost=lists.example.org --with-urlhost=lists.example.org I will shortly try to install MM3 on CentOS 7 ... the biggest issue looks to be that it does not have a version of python that is new enough - so the first thing to fix. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include ------------------------------------------------------ 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/eric%40phoenixsecure.com From mark at msapiro.net Fri May 8 03:23:32 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 18:23:32 -0700 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> Message-ID: <554C1014.3080808@msapiro.net> On 05/07/2015 06:01 PM, Eric Lamer wrote: > I tried to upgrade to version 2.1.20 or 2.1.18 and I have a lot of problems, io error etc. We'd be happy to help if you post tracebacks or mailman error log messages. Lot's of i/o error issues are permissions, and Mailman's bin/check_perms -f run as root will fix most of them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From eric at phoenixsecure.com Fri May 8 03:26:46 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 01:26:46 +0000 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <554C1014.3080808@msapiro.net> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> Message-ID: I will reinstall a brand new CentOs 6.5 then install Mailman, should I install directly version 2.1.20 or should I use yum first then upgrade? EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+eric=phoenixsecure.com at python.org] On Behalf Of Mark Sapiro Sent: Thursday, May 7, 2015 9:24 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Mailman on CentOs On 05/07/2015 06:01 PM, Eric Lamer wrote: > I tried to upgrade to version 2.1.20 or 2.1.18 and I have a lot of problems, io error etc. We'd be happy to help if you post tracebacks or mailman error log messages. Lot's of i/o error issues are permissions, and Mailman's bin/check_perms -f run as root will fix most of them. -- 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/eric%40phoenixsecure.com From cpz at tuunq.com Fri May 8 03:31:13 2015 From: cpz at tuunq.com (Carl Zwanzig) Date: Thu, 07 May 2015 18:31:13 -0700 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> Message-ID: <554C11E1.3030501@tuunq.com> On 5/7/2015 6:26 PM, Eric Lamer wrote: > I will reinstall a brand new CentOs 6.5 then install Mailman, should I > install directly version 2.1.20 or should I use yum first then upgrade? Install centos 6.5, run yum update & reboot (you'll end up at 6.6), install mailman directly from *source*. Do not install mailman from yum first. z! From mark at msapiro.net Fri May 8 04:04:32 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 19:04:32 -0700 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> Message-ID: <554C19B0.8050709@msapiro.net> On 05/07/2015 06:26 PM, Eric Lamer wrote: > I will reinstall a brand new CentOs 6.5 then install Mailman, should I install directly version 2.1.20 or should I use yum first then upgrade? Install directly from 2.1.20 following (also in the tarball). If you install the RHEL/CentOS package, you have to deal with things being spread all over. See . This makes an upgrade from source difficult at best. The only reason to do it is if you run with SELinux enabled. That causes difficulty if you don't do it the Red Hat way. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From eric at phoenixsecure.com Fri May 8 04:48:21 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 02:48:21 +0000 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <554C19B0.8050709@msapiro.net> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> Message-ID: <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> What parameters should I use for the configure? EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Thursday, May 7, 2015 10:05 PM To: Eric Lamer; Subject: Re: [Mailman-Users] Mailman on CentOs On 05/07/2015 06:26 PM, Eric Lamer wrote: > I will reinstall a brand new CentOs 6.5 then install Mailman, should I install directly version 2.1.20 or should I use yum first then upgrade? Install directly from 2.1.20 following (also in the tarball). If you install the RHEL/CentOS package, you have to deal with things being spread all over. See . This makes an upgrade from source difficult at best. The only reason to do it is if you run with SELinux enabled. That causes difficulty if you don't do it the Red Hat way. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri May 8 05:28:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 20:28:34 -0700 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> Message-ID: <554C2D62.9060607@msapiro.net> On 05/07/2015 07:48 PM, Eric Lamer wrote: > What parameters should I use for the configure? I recommend --prefix=/usr/lib/mailman --with-var-prefix=/var/lib/mailman The above are optional. Without them everything installs in /usr/local/mailman which is also OK, but I prefer to separate the mutable and immutable data and the above are more consistent with FHS. Then for CentOS with Postfix --with-cgi-gid=apache --with-mail-gid=mailman --with-mailhost=Your.primary.email.domain --with-urlhost=Your.primary.web.domain and if you aren't going to use the system's default Python --with-python=/path/to/pythonx.y -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dlongnecker at comcast.net Fri May 8 07:05:00 2015 From: dlongnecker at comcast.net (Dennis Longnecker) Date: Thu, 7 May 2015 22:05:00 -0700 Subject: [Mailman-Users] Mailman and dmark help -- please Message-ID: <010a01d0894c$895eb6f0$9c1c24d0$@comcast.net> Thanks for the assistance on this. It appears from the responses, there is nothing wrong with my mailman setup. I have noticed I am getting a bunch of these e-mails. This is all so confusing...just want to scouts in the troop to be able to send and receive e-mail from the mailing list. Any suggestions on how to fix this? This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: xxx at gmail.com SMTP error from remote mail server after end of data: host productio-tcloadba-tkyjfaz4ap1l-328615543.us-west-2.elb.amazonaws.com [54.214.243.124]: 550 5.7.1 [JR] Blocked. See https://console.mailchannels.net/insights/bounce?auid=arvixe&sender=scouts-b ounces%40troop101-wa.org&txid=530e9876 xxx at yahoo.com SMTP error from remote mail server after end of data: host productio-tcloadba-tkyjfaz4ap1l-328615543.us-west-2.elb.amazonaws.com [54.214.243.124]: 550 5.7.1 [JR] Blocked. See https://console.mailchannels.net/insights/bounce?auid=arvixe&sender=scouts-b ounces%40troop101-wa.org&txid=530e9876 xxx at hotmail.com SMTP error from remote mail server after end of data: host productio-tcloadba-tkyjfaz4ap1l-328615543.us-west-2.elb.amazonaws.com [54.214.243.124]: 550 5.7.1 [JR] Blocked. See https://console.mailchannels.net/insights/bounce?auid=arvixe&sender=scouts-b ounces%40troop101-wa.org&txid=530e9876 xxx at wahzoo2.com SMTP error from remote mail server after end of data: host productio-tcloadba-tkyjfaz4ap1l-328615543.us-west-2.elb.amazonaws.com [54.214.243.124]: 550 5.7.1 [JR] Blocked. See https://console.mailchannels.net/insights/bounce?auid=arvixe&sender=scouts-b ounces%40troop101-wa.org&txid=530e9876 xxx at eri-intl.com -----Original Message----- From: Dennis Longnecker [mailto:dlongnecker at comcast.net] Sent: Friday, May 01, 2015 7:15 AM To: 'mailman-users at python.org' Subject: Mailman and dmark help -- please I have a mailing list setup for our boy scout troop. The site is running mailman version version 2.1.18-1. I looking at various lists, I believe I have as much set as I can. (Details for from_is_list) = Munge From I really -- really want the list set so when someone gets an e-mail from the list they can see who sent it and when they click reply it goes to the original sender. When I have the remove sender option, etc. People don't know who the e-mail came from or how to directly reply. I was reading about some DNS DMARC settings, but frankly it really confused me. What I have observed: E-mail from MSN to list Comcast Users = DOn't Get it AOL Users = Don't Get it Yahoo Users = Don't Get it users with arvixe accounts = Do Get it. E-mail from GMAIL to list Comcast Users = DOn't Get it AOL Users = Don't Get it Yahoo Users = Don't Get it users with arvixe accounts = Do Get it. E-mail from Comcast to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Do Get it outlook.com = Do Get it users with arvixe accounts = Do Get it. E-mail from AOL to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Dont Get it outlook.com = Dont Get it users with arvixe accounts = Do Get it. E-mail from Outlook to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Dont Get it outlook.com = Dont Get it users with arvixe accounts = Do Get it. E-mail from Yahoo to list Comcast Users = DO Get it AOL Users = Don't Get it Yahoo Users = Do Get it outlook.com = Do Get it users with arvixe accounts = Do Get it. Any sugestions? My site is troop101-wa.org if looking at its DNS records could help. Dennis From mark at msapiro.net Fri May 8 07:45:09 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 May 2015 22:45:09 -0700 Subject: [Mailman-Users] Mailman and dmark help -- please In-Reply-To: <010a01d0894c$895eb6f0$9c1c24d0$@comcast.net> References: <010a01d0894c$895eb6f0$9c1c24d0$@comcast.net> Message-ID: <554C4D65.9090805@msapiro.net> On 05/07/2015 10:05 PM, Dennis Longnecker wrote: > Thanks for the assistance on this. It appears from the responses, there is > nothing wrong with my mailman setup. I have noticed I am getting a bunch > of these e-mails. This is all so confusing...just want to scouts in the > troop to be able to send and receive e-mail from the mailing list. Any > suggestions on how to fix this? > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > xxx at gmail.com > SMTP error from remote mail server after end of data: > host > productio-tcloadba-tkyjfaz4ap1l-328615543.us-west-2.elb.amazonaws.com > [54.214.243.124]: > 550 5.7.1 [JR] Blocked. See > https://console.mailchannels.net/insights/bounce?auid=arvixe&sender=scouts-b > ounces%40troop101-wa.org&txid=530e9876 It's hard to say for sure, but it looks to me like your outbound mail is being relayed through a mail server at Amazon Web Services, possibly by US-West and for some reason that server is not accepting these messages. It don't think it has anything to do with DMARC, but it might. I think it's more likely some kind of rate limiting or they just don't like the server that's sending to them. I think you will have to involve your hosting provider in diagnosing and fixing this issue. It may be some configuration in their outgoing mail that is the problem or something else, but without a whole lot more info than is in those bounce messages, I can't say. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dap1 at bellsouth.net Fri May 8 13:01:27 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 08 May 2015 07:01:27 -0400 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> Message-ID: <554C9787.2050806@bellsouth.net> On 5/7/2015 9:26 PM, Eric Lamer wrote: > I will reinstall a brand new CentOs 6.5 then install Mailman, should I install directly version 2.1.20 or should I use yum first then upgrade? > > > > > > > > EricLamer > CEO > Phoenix Secure Inc. > 514-914-5599 > 514-800-2556 > eric at phoenixsecure.com > > > > > > > > -----Original Message----- > From: Mailman-Users [mailto:mailman-users-bounces+eric=phoenixsecure.com at python.org] On Behalf Of Mark Sapiro > Sent: Thursday, May 7, 2015 9:24 PM > To: mailman-users at python.org > Subject: Re: [Mailman-Users] Mailman on CentOs > > On 05/07/2015 06:01 PM, Eric Lamer wrote: >> I tried to upgrade to version 2.1.20 or 2.1.18 and I have a lot of problems, io error etc. > > We'd be happy to help if you post tracebacks or mailman error log messages. > > Lot's of i/o error issues are permissions, and Mailman's bin/check_perms -f run as root will fix most of them. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > If you are going to install a fresh CentOS why are you not using the latest version (7)? That will solve all your problems because the CentOS 7 repos have the later version of mailman. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From eric at phoenixsecure.com Fri May 8 15:33:50 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 13:33:50 +0000 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <554C2D62.9060607@msapiro.net> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> Message-ID: <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> Ok I installed a fresh copy of mailman 2.1.20, now I have this error Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Mailman Version: 2.1.20 -----] [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Traceback ------] [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Traceback (most recent call last): [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] immediate=1) [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] self.__get_f() [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] 1) [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Python Information -----] This is the permission I have [root at list httpd]# ls -la /var/lib/mailman/ total 36 drwxrwsr-x. 9 root mailman 4096 May 8 06:33 . drwxr-xr-x. 33 root root 4096 May 8 06:32 .. drwxrwsr-x. 4 root mailman 4096 May 8 06:33 archives drwxrwsr-x. 2 root mailman 4096 May 8 09:24 data drwxrwsr-x. 3 root mailman 4096 May 8 09:22 lists drwxrwsr-x. 2 root mailman 4096 May 8 09:30 locks drwxrwsr-x. 2 root mailman 4096 May 8 09:24 logs drwxrwsr-x. 11 root mailman 4096 May 8 09:24 qfiles drwxrwsr-x. 2 root mailman 4096 May 8 06:33 spam -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Thursday, May 7, 2015 11:29 PM To: Eric Lamer; mailman-users at python.org Subject: Re: [Mailman-Users] Mailman on CentOs On 05/07/2015 07:48 PM, Eric Lamer wrote: > What parameters should I use for the configure? I recommend --prefix=/usr/lib/mailman --with-var-prefix=/var/lib/mailman The above are optional. Without them everything installs in /usr/local/mailman which is also OK, but I prefer to separate the mutable and immutable data and the above are more consistent with FHS. Then for CentOS with Postfix --with-cgi-gid=apache --with-mail-gid=mailman --with-mailhost=Your.primary.email.domain --with-urlhost=Your.primary.web.domain and if you aren't going to use the system's default Python --with-python=/path/to/pythonx.y -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Ralf.Hildebrandt at charite.de Fri May 8 15:40:47 2015 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Fri, 8 May 2015 15:40:47 +0200 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> References: <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> Message-ID: <20150508134047.GM12003@charite.de> * Eric Lamer : > Ok I installed a fresh copy of mailman 2.1.20, now I have this error > > Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Mailman Version: 2.1.20 -----] > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Traceback ------] > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Traceback (most recent call last): > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] immediate=1) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] self.__get_f() > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] 1) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' Mailman is running as user ??? an cannot write to /var/lib/mailman/logs/error -- Ralf Hildebrandt Charite Universit?tsmedizin Berlin ralf.hildebrandt at charite.de Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 From eric at phoenixsecure.com Fri May 8 16:41:13 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 14:41:13 +0000 Subject: [Mailman-Users] [SPAM] - Re: Mailman on CentOs - Sender is forged (SPF Fail) In-Reply-To: <20150508134047.GM12003@charite.de> References: <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com>, <20150508134047.GM12003@charite.de> Message-ID: <1431096073957.14273@phoenixsecure.com> Mailman is running as user Mailman Apache is running as user Apache What I suspect is the httpd could now write to the error log. EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com ________________________________________ From: Ralf Hildebrandt Sent: May-08-15 9:40 AM To: Eric Lamer Cc: Mark Sapiro; mailman-users at python.org Subject: [SPAM] - Re: [Mailman-Users] Mailman on CentOs - Sender is forged (SPF Fail) * Eric Lamer : > Ok I installed a fresh copy of mailman 2.1.20, now I have this error > > Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Mailman Version: 2.1.20 -----] > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Traceback ------] > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Traceback (most recent call last): > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] immediate=1) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] self.__get_f() > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] 1) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' Mailman is running as user ??? an cannot write to /var/lib/mailman/logs/error -- Ralf Hildebrandt Charite Universit?tsmedizin Berlin ralf.hildebrandt at charite.de Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 From eric at phoenixsecure.com Fri May 8 17:32:59 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 15:32:59 +0000 Subject: [Mailman-Users] [SPAM] - Re: Mailman on CentOs - Sender is forged (SPF Fail) In-Reply-To: <20150508134047.GM12003@charite.de> References: <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> <20150508134047.GM12003@charite.de> Message-ID: <1c188a722e084a93b2f8f6216d22c064@PhoenixSrv01.phoenixsecure.com> Hi, Is it normal that /var/www/html/mailman does not exist? [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Mailman Version: 2.1.20 -----] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Traceback ------] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Traceback (most recent call last): [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] immediate=1) [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] self.__get_f() [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] 1) [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Python Information -----] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.version = 2.6.6 (r266:84292, Jan 22 2014, 09:42:36) [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.executable = /usr/bin/python [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.prefix = /usr [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.exec_prefix = /usr [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python26.zip', '/usr/lib64/python2.6/', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib/python2.6/site-packages'] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.platform = linux2 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Environment Variables -----] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_COOKIE: mailman+admin=28020000006945c14a55732800000065316232653636666133383561616563316138343762663435616335306536333632376633393265 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_SOFTWARE: Apache/2.2.15 (CentOS) [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSCRIPT_NAME: /mailman/listinfo [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_SIGNATURE:
Apache/2.2.15 (CentOS) Server at list.sipro.com Port 80
[Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREQUEST_METHOD: GET [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_INFO: /mailman [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PROTOCOL: HTTP/1.1 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tQUERY_STRING: [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_CONNECTION: keep-alive [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_NAME: list.sipro.com [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREMOTE_ADDR: 192.168.2.2 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_TRANSLATED: /var/www/html/mailman [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PORT: 80 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_ADDR: 172.16.4.225 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tDOCUMENT_ROOT: /var/www/html [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPYTHONPATH: /usr/lib/mailman [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/listinfo [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_ADMIN: root at localhost [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_DNT: 1 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_HOST: list.sipro.com [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREQUEST_URI: /mailman/listinfo/mailman [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tGATEWAY_INTERFACE: CGI/1.1 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREMOTE_PORT: 64030 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT_LANGUAGE: en-GB,en;q=0.8,en-US;q=0.6,fr;q=0.4 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT_ENCODING: gzip, deflate, sdch [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File does not exist: /var/www/html/favicon.ico, referer: http://list.sipro.com/mailman/listinfo/mailman -----Original Message----- From: Ralf Hildebrandt [mailto:Ralf.Hildebrandt at charite.de] Sent: Friday, May 8, 2015 9:41 AM To: Eric Lamer Cc: Mark Sapiro; mailman-users at python.org Subject: [SPAM] - Re: [Mailman-Users] Mailman on CentOs - Sender is forged (SPF Fail) * Eric Lamer : > Ok I installed a fresh copy of mailman 2.1.20, now I have this error > > Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Mailman > Version: 2.1.20 -----] [Fri May 08 09:25:51 2015] [error] [client > 192.168.2.70] [----- Traceback ------] [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Traceback (most recent call last): > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] immediate=1) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] self.__get_f() > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] 1) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) > [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' Mailman is running as user ??? an cannot write to /var/lib/mailman/logs/error -- Ralf Hildebrandt Charite Universit?tsmedizin Berlin ralf.hildebrandt at charite.de Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 From dap1 at bellsouth.net Fri May 8 17:40:28 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 08 May 2015 11:40:28 -0400 Subject: [Mailman-Users] [SPAM] - Re: Mailman on CentOs - Sender is forged (SPF Fail) In-Reply-To: <1c188a722e084a93b2f8f6216d22c064@PhoenixSrv01.phoenixsecure.com> References: <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> <20150508134047.GM12003@charite.de> <1c188a722e084a93b2f8f6216d22c064@PhoenixSrv01.phoenixsecure.com> Message-ID: <554CD8EC.3030805@bellsouth.net> On 5/8/2015 11:32 AM, Eric Lamer wrote: > Hi, > > Is it normal that /var/www/html/mailman does not exist? > > > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Mailman Version: 2.1.20 -----] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Traceback ------] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Traceback (most recent call last): > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] immediate=1) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] self.__get_f() > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] 1) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' > > > > > > EricLamer > CEO > Phoenix Secure Inc. > 514-914-5599 > 514-800-2556 > eric at phoenixsecure.com > > > > > > > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Python Information -----] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.version = 2.6.6 (r266:84292, Jan 22 2014, 09:42:36) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.executable = /usr/bin/python > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.prefix = /usr > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.exec_prefix = /usr > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python26.zip', '/usr/lib64/python2.6/', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib/python2.6/site-packages'] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.platform = linux2 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Environment Variables -----] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_COOKIE: mailman+admin=28020000006945c14a55732800000065316232653636666133383561616563316138343762663435616335306536333632376633393265 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_SOFTWARE: Apache/2.2.15 (CentOS) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSCRIPT_NAME: /mailman/listinfo > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_SIGNATURE:
Apache/2.2.15 (CentOS) Server at list.sipro.com Port 80
> [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREQUEST_METHOD: GET > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_INFO: /mailman > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PROTOCOL: HTTP/1.1 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tQUERY_STRING: > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_CONNECTION: keep-alive > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_NAME: list.sipro.com > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREMOTE_ADDR: 192.168.2.2 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_TRANSLATED: /var/www/html/mailman > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PORT: 80 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_ADDR: 172.16.4.225 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tDOCUMENT_ROOT: /var/www/html > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPYTHONPATH: /usr/lib/mailman > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/listinfo > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_ADMIN: root at localhost > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_DNT: 1 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_HOST: list.sipro.com > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREQUEST_URI: /mailman/listinfo/mailman > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tGATEWAY_INTERFACE: CGI/1.1 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tREMOTE_PORT: 64030 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT_LANGUAGE: en-GB,en;q=0.8,en-US;q=0.6,fr;q=0.4 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT_ENCODING: gzip, deflate, sdch > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File does not exist: /var/www/html/favicon.ico, referer: http://list.sipro.com/mailman/listinfo/mailman > > -----Original Message----- > From: Ralf Hildebrandt [mailto:Ralf.Hildebrandt at charite.de] > Sent: Friday, May 8, 2015 9:41 AM > To: Eric Lamer > Cc: Mark Sapiro; mailman-users at python.org > Subject: [SPAM] - Re: [Mailman-Users] Mailman on CentOs - Sender is forged (SPF Fail) > > * Eric Lamer : >> Ok I installed a fresh copy of mailman 2.1.20, now I have this error >> >> Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- Mailman >> Version: 2.1.20 -----] [Fri May 08 09:25:51 2015] [error] [client >> 192.168.2.70] [----- Traceback ------] [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Traceback (most recent call last): >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] immediate=1) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] self.__get_f() >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] 1) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' > Mailman is running as user ??? an cannot write to /var/lib/mailman/logs/error > > -- > Ralf Hildebrandt Charite Universit?tsmedizin Berlin > ralf.hildebrandt at charite.de Campus Benjamin Franklin > http://www.charite.de Hindenburgdamm 30, 12203 Berlin > Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 Yes. The httpd config file redirects it to /usr/lib/mailman. The data is in /var/lib/mailman. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From eric at phoenixsecure.com Fri May 8 17:48:11 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Fri, 8 May 2015 15:48:11 +0000 Subject: [Mailman-Users] [SPAM] - Re: Mailman on CentOs - Sender is forged (SPF Fail) In-Reply-To: <554CD8EC.3030805@bellsouth.net> References: <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> <20150508134047.GM12003@charite.de> <1c188a722e084a93b2f8f6216d22c064@PhoenixSrv01.phoenixsecure.com> <554CD8EC.3030805@bellsouth.net> Message-ID: Ok I disabled SELinux and it is working. Any idea why SELinux would prevent mailman to write to log? EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+eric=phoenixsecure.com at python.org] On Behalf Of Dennis Putnam Sent: Friday, May 8, 2015 11:40 AM To: mailman-users at python.org Subject: Re: [Mailman-Users] [SPAM] - Re: Mailman on CentOs - Sender is forged (SPF Fail) On 5/8/2015 11:32 AM, Eric Lamer wrote: > Hi, > > Is it normal that /var/www/html/mailman does not exist? > > > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- > Mailman Version: 2.1.20 -----] [Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] [----- Traceback ------] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Traceback (most recent call last): > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] immediate=1) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] self.__get_f() > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] 1) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' > > > > > > EricLamer > CEO > Phoenix Secure Inc. > 514-914-5599 > 514-800-2556 > eric at phoenixsecure.com > > > > > > > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- Python Information -----] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.version = 2.6.6 (r266:84292, Jan 22 2014, 09:42:36) > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [GCC 4.4.7 > 20120313 (Red Hat 4.4.7-4)] [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.executable = /usr/bin/python > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.prefix = /usr > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.exec_prefix = /usr > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python26.zip', '/usr/lib64/python2.6/', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib/python2.6/site-packages'] > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] sys.platform = linux2 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] [----- > Environment Variables -----] [Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] \tHTTP_COOKIE: > mailman+admin=28020000006945c14a55732800000065316232653636666133383561 > 616563316138343762663435616335306536333632376633393265 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tSERVER_SOFTWARE: Apache/2.2.15 (CentOS) [Fri May 08 11:27:01 2015] > [error] [client 192.168.2.70] \tSCRIPT_NAME: /mailman/listinfo [Fri > May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tSERVER_SIGNATURE:
Apache/2.2.15 (CentOS) Server at > list.sipro.com Port 80
[Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] [Fri May 08 11:27:01 2015] [error] [client > 192.168.2.70] \tREQUEST_METHOD: GET [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tPATH_INFO: /mailman [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tSERVER_PROTOCOL: HTTP/1.1 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] \tQUERY_STRING: > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tHTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.3; Win64; x64) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 > Safari/537.36 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tHTTP_CONNECTION: keep-alive [Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] \tSERVER_NAME: list.sipro.com [Fri May 08 > 11:27:01 2015] [error] [client 192.168.2.70] \tREMOTE_ADDR: > 192.168.2.2 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tPATH_TRANSLATED: /var/www/html/mailman [Fri May 08 11:27:01 2015] > [error] [client 192.168.2.70] \tSERVER_PORT: 80 [Fri May 08 11:27:01 > 2015] [error] [client 192.168.2.70] \tSERVER_ADDR: 172.16.4.225 [Fri > May 08 11:27:01 2015] [error] [client 192.168.2.70] \tDOCUMENT_ROOT: > /var/www/html [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tPYTHONPATH: /usr/lib/mailman [Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] \tSCRIPT_FILENAME: > /usr/lib/mailman/cgi-bin/listinfo [Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] \tSERVER_ADMIN: root at localhost [Fri May 08 > 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_DNT: 1 [Fri May 08 > 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_HOST: > list.sipro.com [Fri May 08 11:27:01 2015] [error] [client > 192.168.2.70] \tREQUEST_URI: /mailman/listinfo/mailman [Fri May 08 > 11:27:01 2015] [error] [client 192.168.2.70] \tHTTP_ACCEPT: > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q > =0.8 [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tGATEWAY_INTERFACE: CGI/1.1 [Fri May 08 11:27:01 2015] [error] > [client 192.168.2.70] \tREMOTE_PORT: 64030 [Fri May 08 11:27:01 2015] > [error] [client 192.168.2.70] \tHTTP_ACCEPT_LANGUAGE: > en-GB,en;q=0.8,en-US;q=0.6,fr;q=0.4 > [Fri May 08 11:27:01 2015] [error] [client 192.168.2.70] > \tHTTP_ACCEPT_ENCODING: gzip, deflate, sdch [Fri May 08 11:27:01 2015] > [error] [client 192.168.2.70] File does not exist: > /var/www/html/favicon.ico, referer: > http://list.sipro.com/mailman/listinfo/mailman > > -----Original Message----- > From: Ralf Hildebrandt [mailto:Ralf.Hildebrandt at charite.de] > Sent: Friday, May 8, 2015 9:41 AM > To: Eric Lamer > Cc: Mark Sapiro; mailman-users at python.org > Subject: [SPAM] - Re: [Mailman-Users] Mailman on CentOs - Sender is > forged (SPF Fail) > > * Eric Lamer : >> Ok I installed a fresh copy of mailman 2.1.20, now I have this error >> >> Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] [----- >> Mailman >> Version: 2.1.20 -----] [Fri May 08 09:25:51 2015] [error] [client >> 192.168.2.70] [----- Traceback ------] [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Traceback (most recent call last): >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/scripts/driver", line 85, in run_main >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] immediate=1) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] Logger.__init__(self, category, nofail, immediate) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] self.__get_f() >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] 1) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] File "/usr/lib64/python2.6/codecs.py", line 881, in open >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] file = __builtin__.open(filename, mode, buffering) >> [Fri May 08 09:25:51 2015] [error] [client 192.168.2.70] IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' > Mailman is running as user ??? an cannot write to > /var/lib/mailman/logs/error > > -- > Ralf Hildebrandt Charite Universit?tsmedizin Berlin > ralf.hildebrandt at charite.de Campus Benjamin Franklin > http://www.charite.de Hindenburgdamm 30, 12203 Berlin > Gesch?ftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 Yes. The httpd config file redirects it to /usr/lib/mailman. The data is in /var/lib/mailman. From mark at msapiro.net Fri May 8 19:27:46 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 08 May 2015 10:27:46 -0700 Subject: [Mailman-Users] Mailman on CentOs - Sender is forged (SPF Fail) In-Reply-To: References: <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C19B0.8050709@msapiro.net> <3d60d90d04c5416490c6aabec59f45ee@PhoenixSrv01.phoenixsecure.com> <554C2D62.9060607@msapiro.net> <343492fbe9174fe3badaa24a35e19561@PhoenixSrv01.phoenixsecure.com> <20150508134047.GM12003@charite.de> <1c188a722e084a93b2f8f6216d22c064@PhoenixSrv01.phoenixsecure.com> <554CD8EC.3030805@bellsouth.net> Message-ID: <554CF212.3060703@msapiro.net> On 05/08/2015 08:48 AM, Eric Lamer wrote: > Ok I disabled SELinux and it is working. > > Any idea why SELinux would prevent mailman to write to log? Yes. When you do a straight install of Mailman from source, it doesn't put everything in FHS compliant places. In particular, the logs in your case are in /var/lib/mailman/logs, not in /var/log/mailman where FHS and your SELinux security policy expects them to be. If you don't care about SELinux, just leave it disabled. If you want to use it, it will be difficult. You could try moving things to the locations indicated at . Much stuff will already be there if you configured as I suggested, but some things need to move. If you create any new 'mailman' directories, (e.g. /var/lock/mailman,/var/log/mailman, /var/spool/mailman, /etc/mailman) be sure they are group 'mailman' and SETGID and then create symlinks from the old places to the new ones. You can also look in Defaults.py at the sections labeled # Useful directories # Directories used by the qrunner subsystem # Other useful files and override some of those settings in mm_cfg.py. If you do this, you might think that for the queue fils it would be sufficiewnt to just put QUEUE_DIR = '/var/spool/mailman' in mm_cfg.py, but other things were set in Defaults.py based on the 'old' QUEUE_DIR, so you also need to put all the things like INQUEUE_DIR = os.path.join(QUEUE_DIR, 'in') in mm_cfg.py after the QUEUE_DIR setting. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pshute at nuw.org.au Sun May 10 00:03:29 2015 From: pshute at nuw.org.au (Peter Shute) Date: Sun, 10 May 2015 08:03:29 +1000 Subject: [Mailman-Users] Allowing images to be sent to a list References: Message-ID: <6E235443-268A-4D22-8BAE-6993DB3EFACD@nuw.org.au> We're experimenting with allowing images to be sent to our list, but the images are being scrubbed. Please see below for the results of a recent test. What settings should I check to prevent the images being scrubbed? Is it something to do with convert_html_to_plaintext being set to yes? I don't want to experiment with that unnecessarily because this is a live list, and I don't have a non production list to play with. Peter Shute Sent from my iPad Begin forwarded message: From: Peter Shute > Date: 10 May 2015 7:53:41 am AEST To: New birding-aus > Subject: [Birding-Aus] Test 3 Testing if images can be sent to the list. -------------- next part -------------- A non-text attachment was scrubbed... Name: FullSizeRender.jpg Type: image/jpeg Size: 8488 bytes Desc: FullSizeRender.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL:

Birding-Aus mailing list
Birding-Aus at birding-aus.org
To change settings or unsubscribe visit:
http://birding-aus.org/mailman/listinfo/birding-aus_birding-aus.org From lists at damorris.com Sun May 10 00:34:58 2015 From: lists at damorris.com (adam morris) Date: Sun, 10 May 2015 08:34:58 +1000 Subject: [Mailman-Users] user not receiving messages. Message-ID: <554E8B92.1060203@damorris.com> Hi all, I have a user subscribed to a list with two addresses. He can send to the list from both addresses but can only receive from one. I have unsubscribed him and resubscribed with the same result. Neither of us have done anything to his settings after he has been subscribed. Should I contact my hosting provider? -- Adam Morris email: adam at damorris.com From mark at msapiro.net Sun May 10 02:26:19 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 09 May 2015 17:26:19 -0700 Subject: [Mailman-Users] Allowing images to be sent to a list In-Reply-To: <6E235443-268A-4D22-8BAE-6993DB3EFACD@nuw.org.au> References: <6E235443-268A-4D22-8BAE-6993DB3EFACD@nuw.org.au> Message-ID: <554EA5AB.6030201@msapiro.net> On 05/09/2015 03:03 PM, Peter Shute wrote: > We're experimenting with allowing images to be sent to our list, but the images are being scrubbed. Please see below for the results of a recent test. What settings should I check to prevent the images being scrubbed? If images are scrubbed from individual messages and MIME format digests, in the list's admin interface set Non-digest options -> scrub_nondigest to No. If images are scrubbed only from the pipermail archive and plain format digests, that is normal as these are plain text only be definition. > Is it something to do with convert_html_to_plaintext being set to yes? No. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun May 10 02:38:20 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 09 May 2015 17:38:20 -0700 Subject: [Mailman-Users] user not receiving messages. In-Reply-To: <554E8B92.1060203@damorris.com> References: <554E8B92.1060203@damorris.com> Message-ID: <554EA87C.4010807@msapiro.net> On 05/09/2015 03:34 PM, adam morris wrote: > > I have a user subscribed to a list with two addresses. > He can send to the list from both addresses but can only receive from one. What are his subscription options for the address he doesn't receive? Do both addresses forward to the same mailbox that filters dups? Is mailman recording any bounces for the non-delivered address? > Should I contact my hosting provider? Probably not. You could ask them the check their outgoing mail logs to verify that messages are being sent to both addresses, but if both addressses are set in Mailman to receive mail and bounce processing is enabled for the list and there are no bounces, it is almost certain that what they will find is the mail is being sent to both addresses and being delivered to the downstream MX servers and nothing more. It is possible that one of these ISPs is simply treating the list mail as 'obvious spam' and discarding it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun May 10 03:46:11 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 09 May 2015 18:46:11 -0700 Subject: [Mailman-Users] user not receiving messages. In-Reply-To: <554EA9BE.6010502@damorris.com> References: <554E8B92.1060203@damorris.com> <554EA87C.4010807@msapiro.net> <554EA9BE.6010502@damorris.com> Message-ID: <554EB863.4070703@msapiro.net> On 05/09/2015 05:43 PM, adam morris wrote: > > no bounces for the non receiving address. OK > Not sure about dups, This would be at his end. If you send him a message off list to both his addresses, does he receive both. If yes, try sending To: yourself with Bcc: to both his address and see if he receives both. If not, that would rule out Mailman. If so, it could be his ISP, but that's unlikely if he never receives any list message, even in his spam folder. It could also be that he has some filtering rules in his own mail client the do something with the list messages To: the one address. Also, ask him if he never receives any messages or maybe just not some. For example if the not receiving address is @gmail.com and the posts he doesn't receive are only ones he sends from that address, see . > I'm a beginner at mailman, I just subscribe users > to this list and don't change any options, so both of his addresses > would be set up the same. Just to be sure, look at both his addresses in the web admin Membership Management... -> Membership List. Are both the 'nomail' and 'digest' boxes unchecked for both his addresses? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pshute at nuw.org.au Sun May 10 06:40:35 2015 From: pshute at nuw.org.au (Peter Shute) Date: Sun, 10 May 2015 14:40:35 +1000 Subject: [Mailman-Users] Allowing images to be sent to a list In-Reply-To: <554EA5AB.6030201@msapiro.net> References: <6E235443-268A-4D22-8BAE-6993DB3EFACD@nuw.org.au> <554EA5AB.6030201@msapiro.net> Message-ID: <6FB760BC-0DDB-4105-8CF2-8DF44FE13AAA@nuw.org.au> Yes, it was the scrub_nondigest setting, which we experimented with a long time ago and forgot about. Thanks, Peter Shute Sent from my iPad > On 10 May 2015, at 10:26 am, Mark Sapiro wrote: > >> On 05/09/2015 03:03 PM, Peter Shute wrote: >> We're experimenting with allowing images to be sent to our list, but the images are being scrubbed. Please see below for the results of a recent test. What settings should I check to prevent the images being scrubbed? > > > If images are scrubbed from individual messages and MIME format digests, > in the list's admin interface set Non-digest options -> scrub_nondigest > to No. > > If images are scrubbed only from the pipermail archive and plain format > digests, that is normal as these are plain text only be definition. > > >> Is it something to do with convert_html_to_plaintext being set to yes? > > > No. > > -- > 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/pshute%40nuw.org.au From steve at pearwood.info Sun May 10 07:51:54 2015 From: steve at pearwood.info (Steven D'Aprano) Date: Sun, 10 May 2015 15:51:54 +1000 Subject: [Mailman-Users] Bounces being detected as spam/virus sending rate In-Reply-To: <553865BA.90006@msapiro.net> References: <20150423022806.GP5663@ando.pearwood.info> <553865BA.90006@msapiro.net> Message-ID: <20150510055154.GG5663@ando.pearwood.info> On Wed, Apr 22, 2015 at 08:23:38PM -0700, Mark Sapiro wrote: > On 04/22/2015 07:28 PM, Steven D'Aprano wrote: > > > > > > I receive unhandled bounce notifications (no more than a handful of > > those, which I then manually remove) and see notifications of addresses > > that are removed for excessive bouncing, again no more than a handful at > > a time. How can I see a list of members set to No Mail for bouncing? > > > bin/list_members --nomail=bybounce LISTNAME Thanks Mark. According to that, there are currently 12 bouncing members. But when I run the more detail script below, I get 30 bouncing members. What's the difference between the two? (Oh, and for the record, there's only two Hotmail, and one each AOL and Yahoo, addresses in the 30.) > To see more detail get the script at > , copy it to > Mailman's bin/ directory and run > > bin/withlist -a -r get_bounce_info > > > > Can you suggest anything I can do to avoid triggering the ISP's system? > > (A hard question, I know, since we don't know precisely what triggers > > it in the first place.) Thanks for the feedback. I look forward to many frustrating conversations. I currently get Uncaught bounce notifications, and process them by hand as they come in. I also see unsubscribes. Is there a way I can be notified of *caught* bounce notifications? -- Steve From camelia.botez at weizmann.ac.il Sun May 10 08:28:45 2015 From: camelia.botez at weizmann.ac.il (Camelia Botez) Date: Sun, 10 May 2015 06:28:45 +0000 Subject: [Mailman-Users] mail doesn't return Message-ID: <74B33B2DD6D2A148967C7ECBEBF842CF0113105358@IBWMBX02> I have a mailing list with a couple of wrong e-mail addresses . When I send a message to this mailing list I see in /var/log/maillog of the mailman server that those addresses get user unknown and the messages is not sent , but I don't get back an error mail with user unknown From bsfinkel at att.net Sun May 10 18:06:15 2015 From: bsfinkel at att.net (Barry S. Finkel) Date: Sun, 10 May 2015 11:06:15 -0500 Subject: [Mailman-Users] mail doesn't return In-Reply-To: <74B33B2DD6D2A148967C7ECBEBF842CF0113105358@IBWMBX02> References: <74B33B2DD6D2A148967C7ECBEBF842CF0113105358@IBWMBX02> Message-ID: <554F81F7.1020400@att.net> On 5/10/2015 1:28 AM, Camelia Botez wrote: > I have a mailing list with a couple of wrong e-mail addresses . > When I send a message to this mailing list I see in /var/log/maillog > of the mailman server that those addresses get user unknown and > the messages is not sent , but I don't get back an error mail > with user unknown Check the bounce values for the list. IIRC, the default value is 5, so each bounce (max one per day) is counted against a subscriber. All bounces are processed by the Mailman bounce process, and only when a subscriber "achieves" a bounce score at or above the set maximum is the rejection mail sent to the list owner. When I ran a Mailman server, I checked the bounce scores on all lists daily so that I would be able to see which subscribers had bounces, as many of our lists were re-built automatically from external sources. I used scripts developed by Mark Sapiro, and he referenced them in a posting earlier today or yesterday. --Barry Finkel From mark at msapiro.net Sun May 10 19:16:05 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 10 May 2015 10:16:05 -0700 Subject: [Mailman-Users] Bounces being detected as spam/virus sending rate In-Reply-To: <20150510055154.GG5663@ando.pearwood.info> References: <20150423022806.GP5663@ando.pearwood.info> <553865BA.90006@msapiro.net> <20150510055154.GG5663@ando.pearwood.info> Message-ID: <554F9255.2030109@msapiro.net> On 05/09/2015 10:51 PM, Steven D'Aprano wrote: > > Thanks Mark. According to that, there are currently 12 bouncing members. > But when I run the more detail script below, I get 30 bouncing members. > What's the difference between the two? bin/list_members --nomail=bybounce lists those members whose delivery is currently disabled by bounce processing because their bounce score reached threshold. These are members that haven't yet been removed, but will be after they've received and not responded to bounce_you_are_disabled_warnings warning notifications. These will show in the get_bounce_info output with current score >= bounce_score_threshold last bounce date in the recent past email notices left < bounce_you_are_disabled_warnings last notice date in the recent past confirmation cookie = a hex string The other 18 are either stale or currently bouncing but not yet disabled. They will all have current score < bounce_score_threshold email notices left = bounce_you_are_disabled_warnings last notice date = (1970, 1, 1) confirmation cookie = None The difference between stale and current is whether last bounce date is older than today - bounce_info_stale_after days. > I currently get Uncaught bounce notifications, and process them by hand > as they come in. Please send them to me or post them here so we can improve the heuristic bounce recognition. You may sanitize them by munging email addresses to a form like user at example.com, list-bounces at example.com, etc. and if the original list post is included, you may replace it with a note, but otherwise we would like the exact headers and MTA boilerplate from the notice. > I also see unsubscribes. Is there a way I can be > notified of *caught* bounce notifications? If you set bounce_notify_owner_on_disable to Yes, you will get a notice including the actual bounce DSN when the member's delivery is first disabled by bounce. Beginning in Mailman 2.1.19, you can set bounce_notify_owner_on_bounce_increment to Yes to receive a similar notice every time a member's bounce score is incremented, i.e., for at most one bounce per member per day. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun May 10 20:05:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 10 May 2015 11:05:16 -0700 Subject: [Mailman-Users] mail doesn't return In-Reply-To: <74B33B2DD6D2A148967C7ECBEBF842CF0113105358@IBWMBX02> References: <74B33B2DD6D2A148967C7ECBEBF842CF0113105358@IBWMBX02> Message-ID: <554F9DDC.2030604@msapiro.net> On 05/09/2015 11:28 PM, Camelia Botez wrote: > I have a mailing list with a couple of wrong e-mail addresses . > When I send a message to this mailing list I see in /var/log/maillog of the mailman server that those addresses get user unknown and the messages is not sent , but I don't get back an error mail with user unknown If you see that error in /var/log/maillog, it indicates the MTA accepted the message from Mailman at SMTP time and should have returned a non-delivery notification to the envelope sender which is the list's -bounces address and that in turn should be recorded by Mailman as a bounce assuming the list's Bounce processing -> bounce_processing setting is Yes (See Barry Finkel's reply in this thread). In my (Postfix MTA) log I will see things like: May 6 09:45:41 sbh16 postfix/smtp[9314]: D42FD6900F9: to=, relay=mailin-04.mx.aol.com[64.12.88.131]:25, delay=7.6, delays=5.4/0.11/0.51/1.6, dsn=5.2.1, status=bounced (host mailin-04.mx.aol.com[64.12.88.131] said: 521 5.2.1 : AOL will not accept delivery of this message. (in reply to end of DATA command)) Following the queue-id D42FD6900F9, I see May 6 09:45:41 sbh16 postfix/bounce[9342]: D42FD6900F9: sender non-delivery notification: 95BFB6900E2 and following that queue-id, I see May 6 09:45:41 sbh16 postfix/local[9343]: 95BFB6900E2: to=, orig_to=, relay=local, delay=0.35, delays=0.01/0.01/0/0.34, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces gpc-talk) saying the bounce DSN was delivered to Mailman. Is bounce_processing set to Yes for this list? If not, bounces are just ignored. If so, bounces should be recorded in Mailman's bounce log. In any case, read the Bounce processing section of the list's admin UI for more on available settings and how bounce processing works in Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From eric at phoenixsecure.com Sun May 10 19:45:10 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Sun, 10 May 2015 17:45:10 +0000 Subject: [Mailman-Users] Problem after switching servers Message-ID: <37415f79a6224fa493142e47f1c61a85@PhoenixSrv01.phoenixsecure.com> Hi, I had mailman installed on a debian server with version 2.1.18. I installed a new server with Centos 6.6 and mailman 2.1.20 I transferred all my lists and archives. When I access the web server and click on a list it try to go to http://list.aaa.com/cgi-bin/mailman/listinfo/g711.1ac instead of http://list.aaa.com/mailman/listinfo/g711.1ac so my old server had cgi-bin in the url and my new server does not. How can I fix this? So I need to remove the cgi-bin from the url on my new server. Thanks. [cid:45762505-9551-43f5-9158-58708DA84162.jpg] [cid:logo-new.jpg] Eric Lamer CEO Phoenix Secure Inc. [cid:phone.png] 514-914-5599 [cid:printer_and_fax.png] 514-800-2556 [cid:mail_32.png] eric at phoenixsecure.com [cid:button-facebook.png] [cid:button-linkedin.png] [cid:button-twitter.png] [cid:button-youtube.png] [cid:button-google.png] [cid:C44700B8-0227-4717-A5D5-7935D46B0F9D.jpg] From mark at msapiro.net Mon May 11 08:26:51 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 10 May 2015 23:26:51 -0700 Subject: [Mailman-Users] Problem after switching servers In-Reply-To: <37415f79a6224fa493142e47f1c61a85@PhoenixSrv01.phoenixsecure.com> References: <37415f79a6224fa493142e47f1c61a85@PhoenixSrv01.phoenixsecure.com> Message-ID: <55504BAB.20404@msapiro.net> On 05/10/2015 10:45 AM, Eric Lamer wrote: > > When I access the web > server and click on a list it try to go to > http://list.aaa.com/cgi-bin/mailman/listinfo/g711.1ac instead of > http://list.aaa.com/mailman/listinfo/g711.1ac so my old server had > cgi-bin in the url and my new server does not. How can I fix this? Put DEFAULT_URL_PATTERN = 'http://%s/mailman/' in mm_cfg.py and run Mailman's bin/withlist -a -l -r fix_url See the FAQ at for more info. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Mon May 11 20:58:19 2015 From: danil at smirnov.la (Danil Smirnov) Date: Mon, 11 May 2015 21:58:19 +0300 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: <554C9787.2050806@bellsouth.net> References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C9787.2050806@bellsouth.net> Message-ID: 2015-05-08 14:01 GMT+03:00 Dennis Putnam : > > If you are going to install a fresh CentOS why are you not using the > latest version (7)? That will solve all your problems because the CentOS > 7 repos have the later version of mailman. Hi Dennis! Could you be more specific? I don't see last Mailman version on my newly installed Centos 7 box - just 2.1.15 one. What repo do you use? Many thanks in advance, Danil From dap1 at bellsouth.net Mon May 11 21:11:42 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Mon, 11 May 2015 15:11:42 -0400 Subject: [Mailman-Users] Mailman on CentOs In-Reply-To: References: <68b12fe266454498bd341b5e891e7d8d@PhoenixSrv01.phoenixsecure.com> <554B9C32.1030700@msapiro.net> <20150507221829.GD23728@phcomp.co.uk> <554BF0D1.6090005@msapiro.net> <20150507232556.GE23728@phcomp.co.uk> <4cb46366afec423a9b22b2010e610c21@PhoenixSrv01.phoenixsecure.com> <554C1014.3080808@msapiro.net> <554C9787.2050806@bellsouth.net> Message-ID: <5550FEEE.3040400@bellsouth.net> Hi Danil, Sorry, I thought that was the version you were looking for. The version from the CentOS 6 repos was older but maybe they upgraded it since I migrated about 2 months ago. On 5/11/2015 2:58 PM, Danil Smirnov wrote: > 2015-05-08 14:01 GMT+03:00 Dennis Putnam : >> If you are going to install a fresh CentOS why are you not using the >> latest version (7)? That will solve all your problems because the CentOS >> 7 repos have the later version of mailman. > Hi Dennis! > > Could you be more specific? > I don't see last Mailman version on my newly installed Centos 7 box - > just 2.1.15 one. > What repo do you use? > > Many thanks in advance, > Danil > ------------------------------------------------------ > 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/dap1%40bellsouth.net > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From gaja.php at gmail.com Tue May 12 17:29:04 2015 From: gaja.php at gmail.com (Selva Gaja) Date: Tue, 12 May 2015 20:59:04 +0530 Subject: [Mailman-Users] Integrate Mailman from PHP Message-ID: Hi All, I am a PHP(Server Side Script Language) Developer. I want to integrate Mailman from PHP. Is there any API to get Mailman List? How to connect Mailman from PHP? Thanks in Advance. -- Thanks and Regards, Selva Gajendran.S From eric at phoenixsecure.com Tue May 12 04:38:58 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Tue, 12 May 2015 02:38:58 +0000 Subject: [Mailman-Users] Problem with Postfix Message-ID: Hi, When I am sending mail to my mailman server I get this error: Remote Server returned '< #5.3.0 x-unix; Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mailman", but the system's mail server executed the mail script as group "nobody". Try tweaking the mail server to run the script as group "mailman", or re-run configure, providing the command line option `--with-mail-gid=nobody'.>' Any idea how to fix it? Thanks. [cid:45762505-9551-43f5-9158-58708DA84162.jpg] [cid:logo-new.jpg] Eric Lamer CEO Phoenix Secure Inc. [cid:phone.png] 514-914-5599 [cid:printer_and_fax.png] 514-800-2556 [cid:mail_32.png] eric at phoenixsecure.com [cid:button-facebook.png] [cid:button-linkedin.png] [cid:button-twitter.png] [cid:button-youtube.png] [cid:button-google.png] [cid:C44700B8-0227-4717-A5D5-7935D46B0F9D.jpg] From mark at msapiro.net Tue May 12 18:37:54 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 May 2015 09:37:54 -0700 Subject: [Mailman-Users] Problem with Postfix In-Reply-To: References: Message-ID: <55522C62.6010903@msapiro.net> On 05/11/2015 07:38 PM, Eric Lamer wrote: > Hi, > > When I am sending mail to my mailman server I get this error: > > > Remote Server returned '< #5.3.0 x-unix; Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mailman", but the system's mail server executed the mail script as group "nobody". Try tweaking the mail server to run the script as group "mailman", or re-run configure, providing the command line option `--with-mail-gid=nobody'.>' > Any idea how to fix it? See the FAQ at . Note that with Postfix, the pipe to the mail wrapper will be executed as the user that owns the aliases.db file in which the alias is found. If you have Mailman/Postfix integration configured this will be /path/to/mailman/data/aliases.db which chould be owned by 'mailman'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue May 12 18:55:24 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 May 2015 09:55:24 -0700 Subject: [Mailman-Users] Integrate Mailman from PHP In-Reply-To: References: Message-ID: <5552307C.3070602@msapiro.net> On 05/12/2015 08:29 AM, Selva Gaja wrote: > > I am a PHP(Server Side Script Language) Developer. I want to integrate > Mailman from PHP. > > Is there any API to get Mailman List? > How to connect Mailman from PHP? For Mailman 2.1.x, see the FAQ at . Mailman 3 has a RESTful http API for communicating with the core engine, so you can build your own web UI more easily. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From eric at phoenixsecure.com Tue May 12 19:23:40 2015 From: eric at phoenixsecure.com (Eric Lamer) Date: Tue, 12 May 2015 17:23:40 +0000 Subject: [Mailman-Users] Mailman 3 Message-ID: <4b2a2bfff8674df5995fc3bb987fe7c0@PhoenixSrv01.phoenixsecure.com> Hi, Some questions about Mailman 3.0 1- Is it stable enough to use in production? 2- Can you copy lists and archives from Mailman 2.x to Mailman 3.0? Thanks. EricLamer CEO Phoenix Secure Inc. 514-914-5599 514-800-2556 eric at phoenixsecure.com From mark at msapiro.net Tue May 12 23:03:26 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 May 2015 14:03:26 -0700 Subject: [Mailman-Users] Mailman 3 In-Reply-To: <4b2a2bfff8674df5995fc3bb987fe7c0@PhoenixSrv01.phoenixsecure.com> References: <4b2a2bfff8674df5995fc3bb987fe7c0@PhoenixSrv01.phoenixsecure.com> Message-ID: <55526A9E.90201@msapiro.net> On 05/12/2015 10:23 AM, Eric Lamer wrote: > > Some questions about Mailman 3.0 > > 1- Is it stable enough to use in production? We think so ;). Most of the issues we've seen since the initial release are with installation, not operation. > 2- Can you copy lists and archives from Mailman 2.x to Mailman 3.0? Not yet. Eventually we will have a clear path for migrating 2.1.x lists, but for now you should be looking at MM 3 for new lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Bill.Costa at unh.edu Wed May 13 03:56:37 2015 From: Bill.Costa at unh.edu (Bill.Costa at unh.edu) Date: Tue, 12 May 2015 21:56:37 -0400 (EDT) Subject: [Mailman-Users] Mailman 3 In-Reply-To: <55526A9E.90201@msapiro.net> References: <4b2a2bfff8674df5995fc3bb987fe7c0@PhoenixSrv01.phoenixsecure.com> <55526A9E.90201@msapiro.net> Message-ID: > ... for now you should be looking at MM 3 for new lists. I'm working on a migration from ListProc (LP) to Mailman. I installed the latest v2 without any problems; the installation instructions were easy to follow. But with v3 just coming out of beta, it would seem to make more sense to jump from LP to Mailman v3, rather than put our list owners and subscribers through two migrations. Also HyperKitty looks like it would be a real win for us. > Most of the issues we've seen since the initial release are > with installation, not operation. I installed Python v3 yesterday with no problems. But I am finding the Mailman v3 install instructions a bit hard to follow. If I run into brick wall, is this the appropriate forum for any questions I may have? ...BC -- =====================================[ Bill.Costa at unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]== From mark at msapiro.net Wed May 13 04:52:40 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 May 2015 19:52:40 -0700 Subject: [Mailman-Users] Mailman 3 In-Reply-To: References: <4b2a2bfff8674df5995fc3bb987fe7c0@PhoenixSrv01.phoenixsecure.com> <55526A9E.90201@msapiro.net> Message-ID: <5552BC78.70703@msapiro.net> On 05/12/2015 06:56 PM, Bill.Costa at unh.edu wrote: > > I installed Python v3 yesterday with no problems. But I am > finding the Mailman v3 install instructions a bit hard to follow. > If I run into brick wall, is this the appropriate forum for any > questions I may have? For now, mailman-developers at python.org is probably a better place, simply because those in the best position to help hang out there more than here. We hope to have a mailman3-users at mailman3.org list up (on Mailman 3 of course) soon. We are in the process of getting a VM to run it on. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Wed May 13 06:42:47 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 13 May 2015 13:42:47 +0900 Subject: [Mailman-Users] Mailman 3 In-Reply-To: <5552BC78.70703@msapiro.net> References: <4b2a2bfff8674df5995fc3bb987fe7c0@PhoenixSrv01.phoenixsecure.com> <55526A9E.90201@msapiro.net> <5552BC78.70703@msapiro.net> Message-ID: <87617x2im0.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > On 05/12/2015 06:56 PM, Bill.Costa at unh.edu wrote: > > > > I installed Python v3 yesterday with no problems. But I am > > finding the Mailman v3 install instructions a bit hard to follow. > > If I run into brick wall, is this the appropriate forum for any > > questions I may have? > > For now, mailman-developers at python.org is probably a better place, You might also try #mailman at Freenode IRC, especially as GSoC starts to ramp up. All our projects are focused on Mailman 3. Of course there's always the risk that nobody will be on when you are, but if you're a little lucky you could get online help very quickly. From renaud.courvoisier at ecole-art-aix.fr Wed May 13 10:38:20 2015 From: renaud.courvoisier at ecole-art-aix.fr (renaud courvoisier) Date: Wed, 13 May 2015 10:38:20 +0200 Subject: [Mailman-Users] Issue since 2.1.13-5 to 2.1.13-6 update Message-ID: <55530D7C.5070100@ecole-art-aix.fr> Hi, since I've updated from 2.1.13-5 to 2.1.13-6 the language option keep chinese (taiwan) event if I uncheck it. That's really annoying because the listing of all my lists is in chinese, even if the prefered language is french which is ok in any other part of mailman. How can I change this ? By the way, I'm searching where to set up html template capabilities for the mails generated by mailman (and because the system in based on Squeeze I can't change my version of mailman for the moment). I saw the different things in this list and in mailman docs, I know that I've to put the fingers in python, but where ? Thanks for your solutions. -- *Renaud Courvoisier* *?cole Sup?rieure d'Art d'Aix-en-Provence* rue ?mile Tavan - 13100 Aix-en-Provence www.ecole-art-aix.fr / www.esaaix.fr <3D%22http://www.esaaix.fr/%22> From stephen at xemacs.org Wed May 13 11:27:39 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 13 May 2015 18:27:39 +0900 Subject: [Mailman-Users] Issue since 2.1.13-5 to 2.1.13-6 update In-Reply-To: <55530D7C.5070100@ecole-art-aix.fr> References: <55530D7C.5070100@ecole-art-aix.fr> Message-ID: <8738303jzo.fsf@uwakimon.sk.tsukuba.ac.jp> renaud courvoisier writes: > Hi, > since I've updated from 2.1.13-5 to 2.1.13-6 the language option keep > chinese (taiwan) event if I uncheck it. 2.1.13 is very old, and the "-5" is not part of the Mailman version. You may be able to get better help from your OS distributor than from us. Try setting DEFAULT_SERVER_LANGUAGE = 'fr' in mm_cfg.py. > By the way, I'm searching where to set up html template capabilities for > the mails generated by mailman What do you mean by "html template capabilities for mail"? From sm at noisynotes.com Wed May 13 15:15:20 2015 From: sm at noisynotes.com (Steve Matzura) Date: Wed, 13 May 2015 09:15:20 -0400 Subject: [Mailman-Users] Trying to get mail working Message-ID: <8ij6la5jfg22v4i889betlm3mb1qb339ns@4ax.com> I have charge of a very mixed system--current OS (Fedora 20--OK 21's out but I just haven't upgraded yet), current (or nearly so) Mailman (2.1.18-1), Postfix 2.10 with a configuration file sfrom something a lot older which I've run through the upgrade-configuration procedure, and old Dovecot (1.0.15). Is there anything I can do to test each of these components individually, then add a second component and test the three pairs, then all three together? I am nobody's definitioin of an expert in any of these three components, so am having a lot of trouble making them work together, so I thought maybe there might be some test procedure that might straighten me out. Thanks in advance. From stephen at xemacs.org Wed May 13 16:19:45 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 13 May 2015 23:19:45 +0900 Subject: [Mailman-Users] Trying to get mail working In-Reply-To: <8ij6la5jfg22v4i889betlm3mb1qb339ns@4ax.com> References: <8ij6la5jfg22v4i889betlm3mb1qb339ns@4ax.com> Message-ID: <87zj581rwe.fsf@uwakimon.sk.tsukuba.ac.jp> Steve Matzura writes: > I have charge of a very mixed system--current OS (Fedora 20--OK 21's > out but I just haven't upgraded yet), current (or nearly so) Mailman > (2.1.18-1), Postfix 2.10 with a configuration file sfrom something a > lot older which I've run through the upgrade-configuration procedure, > and old Dovecot (1.0.15). Is there anything I can do to test each of > these components individually, Dovecot and Mailman should be mostly independent of each other, while both depend crucially on Postfix. The first thing to do is to find the log files for each application, and test that mail works for all combinations of inside and outside the system (and often "outside" has to be divided into "your domain" and "the rest of the Internet"), to and from. If Dovecot isn't working, you still should be able to see mail flowing in the Postfix logs, and possibly learn something about its status using the mailq tool. Next work on being able to read and perhaps submit mail via Dovecot. Finally, do the Mailman configuration. Testing Dovecot or Mailman in the absence of a working Postfix is going to be hard for you, I guess. It's not impossible, but it requires some knowledge of internals of each program, and a fair amount of confidence with Unix tools like pipes and netcat. Much easier to learn to read Postfix's logs to determine when the problem is with one of the (non- ;-) cooperating applications, and when it's Postfix. It would help if you describe the symptoms, although perhaps the best thing we can do is direct you to a Postfix or Dovecot channel. HTH Steve From mark at msapiro.net Wed May 13 17:20:49 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 May 2015 08:20:49 -0700 Subject: [Mailman-Users] Trying to get mail working In-Reply-To: <87zj581rwe.fsf@uwakimon.sk.tsukuba.ac.jp> References: <8ij6la5jfg22v4i889betlm3mb1qb339ns@4ax.com> <87zj581rwe.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <55536BD1.90004@msapiro.net> On 05/13/2015 07:19 AM, Stephen J. Turnbull wrote: > > Dovecot and Mailman should be mostly independent of each other, while > both depend crucially on Postfix. The situation which makes them "mostly independent" rather than "completely independent" is if Postfix is configured in a way that tries to use Dovecot as the LDA for mail to Mailman. Normally, Mailman relies on aliases in Postfix to properly deliver mail to Mailman, and only Postfix's "local" LDA uses aliases; Dovecot doesn't. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sm at noisynotes.com Thu May 14 15:26:47 2015 From: sm at noisynotes.com (Steve Matzura) Date: Thu, 14 May 2015 09:26:47 -0400 Subject: [Mailman-Users] Trying to get mail working In-Reply-To: <87zj581rwe.fsf@uwakimon.sk.tsukuba.ac.jp> References: <8ij6la5jfg22v4i889betlm3mb1qb339ns@4ax.com> <87zj581rwe.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On Wed, 13 May 2015 23:19:45 +0900, Steve Turnbull wrote: >Dovecot and Mailman should be mostly independent of each other, while >both depend crucially on Postfix. The first thing to do is to find >the log files for each application, and test that mail works for all >combinations of inside and outside the system (and often "outside" has >to be divided into "your domain" and "the rest of the Internet"), to >and from. If Dovecot isn't working, you still should be able to see >mail flowing in the Postfix logs, and possibly learn something about >its status using the mailq tool. Next work on being able to read and >perhaps submit mail via Dovecot. Finally, do the Mailman >configuration. Thanks. That sounds like an excellent starting point. >Testing Dovecot or Mailman in the absence of a working Postfix is >going to be hard for you, I guess. It's not impossible, but it >requires some knowledge of internals of each program, and a fair >amount of confidence with Unix tools like pipes and netcat. Much >easier to learn to read Postfix's logs to determine when the problem >is with one of the (non- ;-) cooperating applications, and when it's >Postfix. Tools are not a problem, but program internals? Nah, not I, said the sys admin (LOL). At least I know now what the focal point is of the three. >It would help if you describe the symptoms, although perhaps the best >thing we can do is direct you to a Postfix or Dovecot channel. No symptoms to report, as I've not begun testing in a serious and methodical way ... until now, because I was clueless as to where to begin. I'll work with the above and reply with more details as they are revealed if things don't work. From billc_lists at greenbuilder.com Fri May 15 06:32:00 2015 From: billc_lists at greenbuilder.com (Bill Christensen) Date: Thu, 14 May 2015 23:32:00 -0500 Subject: [Mailman-Users] Migrating a list to a new email address Message-ID: <555576C0.1060708@greenbuilder.com> Hi all, I have a long running list with thousands of subscribers that needs to move to a new set of email addresses. The existing list is announce-only, so doesn't get a whole lot of traffic - typically at most a few outgoing emails a year. But some time back a bot started sending spam registrations via hits to the web server in the form /mailman/subscribe.cgi/bwbnewsletter?email=@&fullname=&pw=123456789&pw-conf=123456789&language=en&digest=0&email-button=Subscribe. I long ago routed real users to an alternative signup, but the spam keeps coming, unrelenting, and are now anywhere between 1k and 10k per day. I'm thinking that the best way to deal with this is to move everything, including the archives, to a newly created list on the same domain name. The alternative signup method i've set up works, so if i set the new list to "Advertise this list..." = NO in Privacy, I'm hoping the spammers won't figure out that the new mailman list exists. I could also set it up as a closed list if that's possible since the new registrations will be entered manually in bulk, though I don't see any settings which disallow all subscriptions. So I'd like confirmation on how to move a list to a new address under the same domain. I figure I need to: 1) take a backup copy of the .mbox file in /archives/private 2) take a copy of the current subscriber list (already done using the list_members command) 3) create the new list, aliases, etc and associated email addresses 4) remove /archives/private/.mbox 5) rename .mbox to .mbox 5b) do I need to replace all instances of with everywhere they occur in the .mbox file? Would doing so cause any problems? 6) rebuild the archives 7) test the new list 8) bulk subscribe the subscriber list to 9) delete the old list Did I miss anything? Thanks in advance. From mark at msapiro.net Fri May 15 07:21:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 May 2015 22:21:06 -0700 Subject: [Mailman-Users] Migrating a list to a new email address In-Reply-To: <555576C0.1060708@greenbuilder.com> References: <555576C0.1060708@greenbuilder.com> Message-ID: <55558242.3080706@msapiro.net> On 05/14/2015 09:32 PM, Bill Christensen wrote: > > I'm thinking that the best way to deal with this is to move everything, > including the archives, to a newly created list on the same domain > name. The alternative signup method i've set up works, so if i set the > new list to "Advertise this list..." = NO in Privacy, I'm hoping the > spammers won't figure out that the new mailman list exists. I could > also set it up as a closed list if that's possible since the new > registrations will be entered manually in bulk, though I don't see any > settings which disallow all subscriptions. Privacy options... -> Subscription rules -> subscribe_policy st to Require approval and then discard all requests. > So I'd like confirmation on how to move a list to a new address under > the same domain. I figure I need to: > > 1) take a backup copy of the .mbox file in /archives/private > > 2) take a copy of the current subscriber list (already done using the > list_members command) > > 3) create the new list, aliases, etc and associated email addresses > > 4) remove /archives/private/.mbox > > 5) rename .mbox to .mbox > > 5b) do I need to replace all instances of with > everywhere they occur in the .mbox file? Would doing so > cause any problems? 5b) No. You don't need to edit the old .mbox file in any way. Of course, if there are say URLs in the bodies of messages (other than scrubbed attachment links) that point to the old list, you may want to fix those. You can do all the above (1-5) in one step with the script at . See the FAQ at which mentions this and a few other methods. > 6) rebuild the archives See the note in the second half of that FAQ about scrub_nondigest. Similar info is in the script's -h/--help output. The archives will be moved with the -a/--archives option to the script. The reason you may want to rebuild the archives are the "more information about this list" links still point to the old list name and likewise, links to scrubbed attachments if any. > 7) test the new list > > 8) bulk subscribe the subscriber list to Already done with the -m/--members option to the list. > 9) delete the old list > > Did I miss anything? If you have and pending requests, a digest mbox or list specific templates, you may want to move those, but the -e/--extra_files option to the script will do that. It also takes care of alias generation for the new list if you use Mailman/Postfix integration. Otherwise, you may need to update aliases manually. In short, the whole process is 1) Install the clone_list script in mailman's bin/ directory. 2) bin/clone_list -m -a -e old_list_name new_list_name (there are also options to change subject_prefix, list owner and list password, but they default to keeping current values.) 2a) maybe bin/arch --wipe new_list_name (or maybe 3a) 3) Test 4) bin/rmlist old_list_name -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dean.collins at insightplanners.com Fri May 15 15:53:47 2015 From: dean.collins at insightplanners.com (Dean Collins) Date: Fri, 15 May 2015 06:53:47 -0700 Subject: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 Message-ID: <009a01d08f16$9108a620$b319f260$@insightplanners.com> Hello, everyone. Will "config_list -I" work to import settings from version 2.1.12-18 to 2.1.15-17? Thanks! Dean From regis92130 at gmail.com Thu May 14 14:29:25 2015 From: regis92130 at gmail.com (Regis) Date: Thu, 14 May 2015 14:29:25 +0200 Subject: [Mailman-Users] Where are the wrong email adresses ? Message-ID: <55549525.8010700@gmail.com> Hello everybody, I have just sent my first mailing with mailman. I kwow that a lot of email adresses are wrong but, in the admin panel, i can't see them neither in the Membership Management list nor in the Bounce Processing... Please could you tell me where can i see and manage these wrong email adresses ? Thanks a lot ! From mark at msapiro.net Fri May 15 18:16:55 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 May 2015 09:16:55 -0700 Subject: [Mailman-Users] Where are the wrong email adresses ? In-Reply-To: <55549525.8010700@gmail.com> References: <55549525.8010700@gmail.com> Message-ID: <55561BF7.8070607@msapiro.net> On 05/14/2015 05:29 AM, Regis wrote: > > Please could you tell me where can i see and manage these wrong email > adresses ? Bounces from invalid addresses are returned to a special LISTNAME-bounces address where they are either ignored or automatically processed by Mailman according to settings in the Bounce processing admin UI. If Bounce processing -> bounce_processing is set to Yes for the list, the bounces will be processed automatically according to the remaining settings. Each bounce is logged in Mailman's bounce log and you can see the addresses there, but not the actual bounce DSN. If bounce_notify_owner_on_disable is Yes, the notice to the list owner will contain a copy of the DSN that caused the disable (i.e., increased the score to bounce_score_threshold). If you have Mailman 2.1.19 or newer, you can also set bounce_notify_owner_on_bounce_increment to Yes to receive a nitice with a copy of the DSN that incremented the score, i.e., the first bounce of the day. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri May 15 18:41:12 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 May 2015 09:41:12 -0700 Subject: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 In-Reply-To: <009a01d08f16$9108a620$b319f260$@insightplanners.com> References: <009a01d08f16$9108a620$b319f260$@insightplanners.com> Message-ID: <555621A8.20803@msapiro.net> On 05/15/2015 06:53 AM, Dean Collins wrote: > Hello, everyone. Will "config_list -I" work to import settings from version 2.1.12-18 to 2.1.15-17? Yes it will, but if you're actually moving a list as opposed to just using its settings, you can just move the lists/LISTNAME/config.pck file and that works too as long as it's an upgrade (from older Mailman to newer). Mailman detects that the config.pck is old and upgrades it automatically. Actually, some downgrades will work too, but it's trickier and depends on the exact from and to versions. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dean.collins at insightplanners.com Fri May 15 21:28:48 2015 From: dean.collins at insightplanners.com (Dean Collins) Date: Fri, 15 May 2015 12:28:48 -0700 Subject: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 In-Reply-To: <555621A8.20803@msapiro.net> References: <009a01d08f16$9108a620$b319f260$@insightplanners.com> <555621A8.20803@msapiro.net> Message-ID: <01b501d08f45$5df6b8b0$19e42a10$@insightplanners.com> This is Mailman 2.1.15-17, qmail, CentOS 7. I've got a new server and set up a test list, say, mylist at mydomain.com. Subscribers include me at mydomain.com (the same domain the list is on) and various addresses from other domains/servers (a couple of servers I run, plus Gmail and AT&T.) Mail sent to mylist at mydomain.com from any subscriber gets archived -- and distributed to me at mydomain.com. But none of the other subscribers receive the list mail. Non-list, regular mail works fine. Using me at mydomain.com I can send to anyone (and they receive it) and receive from anyone. I know less about mail than just about anything else in the world, so any suggestions as to what might be wrong would be appreciated. Thanks! Dean From dap1 at bellsouth.net Fri May 15 21:51:27 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 15 May 2015 15:51:27 -0400 Subject: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 In-Reply-To: <01b501d08f45$5df6b8b0$19e42a10$@insightplanners.com> References: <009a01d08f16$9108a620$b319f260$@insightplanners.com> <555621A8.20803@msapiro.net> <01b501d08f45$5df6b8b0$19e42a10$@insightplanners.com> Message-ID: <55564E3F.60702@bellsouth.net> On 5/15/2015 3:28 PM, Dean Collins wrote: > This is Mailman 2.1.15-17, qmail, CentOS 7. > > I've got a new server and set up a test list, say, mylist at mydomain.com. > > Subscribers include me at mydomain.com (the same domain the list is on) and > various addresses from other domains/servers (a couple of servers I run, > plus Gmail and AT&T.) > > Mail sent to mylist at mydomain.com from any subscriber gets archived -- and > distributed to me at mydomain.com. But none of the other subscribers receive > the list mail. > > Non-list, regular mail works fine. Using me at mydomain.com I can send to > anyone (and they receive it) and receive from anyone. > > I know less about mail than just about anything else in the world, so any > suggestions as to what might be wrong would be appreciated. Thanks! > > Dean > > What outgoing SMTP server are you trying to use? If smtp.att.yahoo.com your problem is in the postfix config, not mailman. ATT is so heavily restricted it is nearly impossible to set up. I use MailJet as my outgoing server for mailman instead. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Fri May 15 21:58:49 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 May 2015 12:58:49 -0700 Subject: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 In-Reply-To: <01b501d08f45$5df6b8b0$19e42a10$@insightplanners.com> References: <009a01d08f16$9108a620$b319f260$@insightplanners.com> <555621A8.20803@msapiro.net> <01b501d08f45$5df6b8b0$19e42a10$@insightplanners.com> Message-ID: <55564FF9.8010309@msapiro.net> On 05/15/2015 12:28 PM, Dean Collins wrote: > > Subscribers include me at mydomain.com (the same domain the list is on) and > various addresses from other domains/servers (a couple of servers I run, > plus Gmail and AT&T.) > > Mail sent to mylist at mydomain.com from any subscriber gets archived -- and > distributed to me at mydomain.com. But none of the other subscribers receive > the list mail. In order to be sure about anything, I'd need to see some logs like Mailman's smtp-failure log and the MTA logs, except I don't know anything about qmail. However, based on past experience I can say the following. 1) Mailman is delivering to the local MTA (qmail) and the mail is being delivered to local addresses but not being sent to remote domains. 2) Other locally generated mail is being sent to remote domains. When this happens it is probably an IPv4 vs. IPv6 issue. Here's one scenario. It may not be exactly this in your case, but you should be able to translate. The MTA has an idea of what addresses constitute the local network and will relay mail from those addresses to the outside. This includes say the IPv4 local host, something like 127.0.0.1, but not the IPv6 local host ::1. Mailman, by default, delivers to 'localhost'. 'localhost' in turn is defined as the IPv6 ::1 address. Thus Mailman's mail comes to the MTA from ::1 which is not in the MTA's notion of the local network, so the MTA refuses to relay the mail. This can be fixed in multiple ways. You can add the IPv6 local host to the MTA's local network. You can change /etc/hosts to associate 127.0.0.1 rather than ::1 with 'localhost'. You can set SMTPHOST in mm_cfg.py to something that will work. E.g., SMTPHOST = '127.0.0.1' Note that since I haven't seen your logs, the above scenario may be off. Perhaps it would be that Mailman is sending via the IPv4 loopback and qmail wants IPv6, but the idea is the same. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From billc_lists at greenbuilder.com Sat May 16 03:51:42 2015 From: billc_lists at greenbuilder.com (Bill Christensen) Date: Fri, 15 May 2015 20:51:42 -0500 Subject: [Mailman-Users] Migrating a list to a new email address In-Reply-To: <55558242.3080706@msapiro.net> References: <555576C0.1060708@greenbuilder.com> <55558242.3080706@msapiro.net> Message-ID: <5556A2AE.3080500@greenbuilder.com> Excellent. I didn't know about the clone_list script. On 5/15/15 12:21 AM, Mark Sapiro wrote: > Privacy options... -> Subscription rules -> subscribe_policy st to > Require approval and then discard all requests. when you say "discard all requests", is there a way to do that automatically? Without email notices to the owner address? From mark at msapiro.net Sat May 16 05:26:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 May 2015 20:26:16 -0700 Subject: [Mailman-Users] Migrating a list to a new email address In-Reply-To: <5556A2AE.3080500@greenbuilder.com> References: <555576C0.1060708@greenbuilder.com> <55558242.3080706@msapiro.net> <5556A2AE.3080500@greenbuilder.com> Message-ID: <5556B8D8.7070905@msapiro.net> On 05/15/2015 06:51 PM, Bill Christensen wrote: > > On 5/15/15 12:21 AM, Mark Sapiro wrote: >> Privacy options... -> Subscription rules -> subscribe_policy st to >> Require approval and then discard all requests. > when you say "discard all requests", is there a way to do that > automatically? Without email notices to the owner address? Not really. If you set General Options -> admin_immed_notify to No, there will be only one summary notice per day, and not the one per request and you could modify Mailman's crontab to not run checkdbs or run it less frequently than daily, but the requests will still be there. There is no automatic discard, but it wouldn't be hard to create a script that discards all outstanding subscription requests for a list (or all lists) and run it daily just before checkdbs runs so checkdbs would have nothing to report. In fact, if you wanted to be really crude and ignore all requests for a list you could just remove the lists/listname/request.pck file. This would effectively discard all requests. You have to be carful because you don't want to do this if there are held messages because then the message files would be orphaned, but something like (adjust list, prefix and var_prefix to suit #! /bin/sh list=LISTNAME prefix=/usr/lib/mailman var_prefix=/var/lib/mailman ls $var_prefix/data/heldmsg-$list-* | xargs $prefix/bin/discard rm $var_prefix/lists/$list/request.pck would discard all held messages and then discard the remaining subscribe (and unsubscribe if unsubscribe_policy is Yes) requests. You could add this to the crontab to run just before checkdbs, or add $prefix/cron/checkdbs to the end of it and run it instead of checkdbs. That all assumes you might have other lists you want to treat normally. There are other things you can do as well, but, looking at your original post, I see I didn't fully register the situation. If your Mailman is at least 2.1.16, all you need to do is set SUBSCRIBE_FORM_SECRET = 'Some string unique to your site" in mm_cfg.py, and that attack will no longer work. Doing that requires that for the subscribe to be successful, the URL must contain a token which was generated by the listinfo subscribe form at least 5 seconds and no more than an hour before submission. The token contains a hash of the secret, the requesting IP, the list name and the time which means if a bot is going to subscribe, it has to first retrieve the listinfo page to get the token and then wait 5 seconds (which can be configured to be longer by setting SUBSCRIBE_FORM_MIN_TIME in mm_cfg.py) and then submit the request with the token. I don't think the bots have figured it out yet. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ericardosantos at gmail.com Sun May 17 03:55:25 2015 From: ericardosantos at gmail.com (Ricardo Santos) Date: Sat, 16 May 2015 21:55:25 -0400 Subject: [Mailman-Users] help with error on start Message-ID: I installed mailman and have those message: /usr/lib/mailman/bin/check_db --all --verbose Traceback (most recent call last): File "/usr/lib/mailman/bin/check_db", line 61, in from Mailman.MailList import MailList File "/usr/lib/mailman/Mailman/MailList.py", line 51, in from Mailman.Archiver import Archiver File "/usr/lib/mailman/Mailman/Archiver/__init__.py", line 17, in from Archiver import * File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 37, in from Mailman.i18n import _ File "/usr/lib/mailman/Mailman/i18n.py", line 36, in _ctype_charset = _get_ctype_charset() File "/usr/lib/mailman/Mailman/i18n.py", line 31, in _get_ctype_charset old = locale.setlocale(locale.LC_CTYPE, '') File "/usr/lib/python2.6/locale.py", line 513, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting Service is stopped. It can not start anyway. Some help please? From mark at msapiro.net Sun May 17 17:54:55 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 May 2015 08:54:55 -0700 Subject: [Mailman-Users] help with error on start In-Reply-To: References: Message-ID: <5558B9CF.9010800@msapiro.net> On 05/16/2015 06:55 PM, Ricardo Santos wrote: > I installed mailman and have those message: > > /usr/lib/mailman/bin/check_db --all --verbose > > Traceback (most recent call last): ... > File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 37, in > > from Mailman.i18n import _ > > File "/usr/lib/mailman/Mailman/i18n.py", line 36, in > > _ctype_charset = _get_ctype_charset() Something is wrong here. The Mailman/i18n.py distributed by the GNU Mailman project does not anything like the above line. How did you install Mailman? Where did /usr/lib/mailman/Mailman/i18n.py come from? If this is a 'package', see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From billc_lists at greenbuilder.com Sun May 17 22:58:30 2015 From: billc_lists at greenbuilder.com (Bill Christensen) Date: Sun, 17 May 2015 15:58:30 -0500 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " Message-ID: Mark, Adding the line SUBSCRIBE_FORM_SECRET = 'Some string unique to your site" in mm_cfg.py definitely made a huge difference to the spam registration problem I was having. Looks like I may not need to migrate the list to a new address after all. One more problem to solve. I'm using Gmail for all our email addresses, and pulling the mail into Mailman using Fetchmail. It's been working fine for years. One of my more important lists recently started getting this in the Fetchmail console: post script, list not found: fetchmail: Error writing to MDA: Broken pipe and the Mailman error log says: gate_news(12061): IOError : [Errno 13] Permission denied: '/opt/local/var/mailman/locks/gate_news.lock..12061.0' post(12068): post script, list not found: Mailman mischief log says: Hostile listname: In the smtp-failure log I'm seeing Message size exceeds fixed limit In General Options => Maximum length in kilobytes (KB) of a message body. Use 0 for no limit. I have '0'. I've run the check permissions script ( with -f), it changes nothing. It appears that there are 5 messages waiting for delivery, though I don't see them in any of the queues. This appears to have started around the time that I upgraded from Mailman 2.1.17 (or so) to 2.1.20 That list is also not archiving properly, so it clearly has problems All the other lists on the server are working fine as far as I can tell. Any ideas as to what's wrong? From pshute at nuw.org.au Mon May 18 01:04:53 2015 From: pshute at nuw.org.au (Peter Shute) Date: Mon, 18 May 2015 09:04:53 +1000 Subject: [Mailman-Users] Could Mailman cope with extra Mime sections intended for Apple Watches? Message-ID: This isn't something that's happening right now, and I doubt it will, but you never know. Apple is playing with mail formats intended to display as a message summary on an Apple Watch, but show the full message on a larger device. Apparently it's a legal format, but lots of mail clients are getting it wrong, and I'm wondering what Mailman would do with a message like that. I don't fully understand the problem, but it seems that reply notifications sent to people participating in discussions in the "Apple Support Comunities" (discussions.apple.com)have recently changed format. Previously they had an html part and a plain text part. Now they have an additional second html part containing the message summary. Mail clients are supposed to go through the Mime sections and select the most suitable one to display. It appears that most are selecting the html summary and not looking any further, so people don't see the full message. It appears that Exchange is even removing the other bits. It hasn't been suggested that Apple will try to do the same thing with user generated email, but who knows? If they do, will Mailman pass all three Mime sections through? It's being discussed here, and someone has posted a sample of the format: https://discussions.apple.com/thread/7039218?start=15&tstart=0 Peter Shute From mark at msapiro.net Mon May 18 01:26:15 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 May 2015 16:26:15 -0700 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " In-Reply-To: References: Message-ID: <55592397.9030006@msapiro.net> On 05/17/2015 01:58 PM, Bill Christensen wrote: > Mark, > > Adding the line > > SUBSCRIBE_FORM_SECRET = 'Some string unique to your site" > > in mm_cfg.py definitely made a huge difference to the spam registration > problem I was having. Looks like I may not need to migrate the list to a > new address after all. > > > One more problem to solve. > > I'm using Gmail for all our email addresses, and pulling the mail into > Mailman using Fetchmail. It's been working fine for years. > > One of my more important lists recently started getting this in the > Fetchmail console: > > post script, list not found: > > fetchmail: Error writing to MDA: Broken pipe > > and the Mailman error log says: > > gate_news(12061): IOError : [Errno 13] Permission denied: > '/opt/local/var/mailman/locks/gate_news.lock..12061.0' This is probably not related. Do you even have any lists with Mail<->News gateways -> gateway_to_mail = Yes?. Mailman's cron/gate_news runs by default every five minutes and does use this lock to prevent concurrent updates. I would also expect to see entries like 'Could not acquire gate_news lock' in the fromusenet log. If this is a one-time occurrence, It was just a glitch. Maybe someone manually ran cron/gate_news as a user not in Mailman's group. If you get these every 5 minutes, there is a permissions issue, probably with the user running this cron not being mailman, because if the locks directory were not group mailman and group writable, lots more would be broken. > post(12068): post script, list not found: The post script invoked by /path/to/mailman/mail/mailman post in your fetchmail script says doesn't exist. > Mailman mischief log says: > > Hostile listname: This is consistent with the 'post script' report and says that contains one or more characters not in the Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The default setting only allows letters, digits, '-', '+', '_', '.' and '='. Does contain characters outside this set or whatever set you've specified? > In the smtp-failure log I'm seeing > > Message size exceeds fixed limit > > In General Options => Maximum length in kilobytes (KB) of a message body. > Use 0 for no limit. I have '0'. These two things are unrelated. The message in smtp-failure says Mailman attempted to send a message which was larger than the MTA would accept. In Postfix for example, this is the main.cf parameter message_size_limit. > I've run the check permissions script ( with -f), it changes nothing. It > appears that there are 5 messages waiting for delivery, though I don't see > them in any of the queues. If Mailman is retrying the smtp-failure, the message would be in Mailman's 'retry' queue until Mailman eventually gives up. Or, they could be still in the gmail inbox since fetchmail probably wouldn't delete them as it couldn't deliver them. > This appears to have started around the time that I upgraded from Mailman > 2.1.17 (or so) to 2.1.20 > > That list is also not archiving properly, so it clearly has problems The listname problem would mess up a lot, but it looks like there would be nothing to archive since nothing for that list is getting posted. > All the other lists on the server are working fine as far as I can tell. > > Any ideas as to what's wrong? First, what's the list name? Once you fix that issue, that may be all, or there may be shunted messages in Mailman's shunt queue to be unshunted. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon May 18 01:59:18 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 May 2015 16:59:18 -0700 Subject: [Mailman-Users] Could Mailman cope with extra Mime sections intended for Apple Watches? In-Reply-To: References: Message-ID: <55592B56.1040107@msapiro.net> On 05/17/2015 04:04 PM, Peter Shute wrote: > This isn't something that's happening right now, and I doubt it will, > but you never know. Apple is playing with mail formats intended to > display as a message summary on an Apple Watch, but show the full > message on a larger device. Apparently it's a legal format, but lots > of mail clients are getting it wrong, and I'm wondering what Mailman > would do with a message like that. Process it in conformance with the MIME RFCs and the list's content filtering. > It's being discussed here, and someone has posted a sample of the > format: > https://discussions.apple.com/thread/7039218?start=15&tstart=0 I looked at that, and it appears the structure of the message is as follows multipart/mixed multipart/alternative text/plain plain text version text/html html 'summary' text/html html version This is arguably non-conformant. multipart/alternative parts are supposed to contain sub-parts which are alternative representations of the message arranged in increasing order of complexity, and MUAs are supposed to render the most complex (supposedly closest to the original) that they understand. The summary part is not a more faithful representation of the complete message than even the text/plain part, so it doesn't belong there. What mailman will do depends on content filtering as follows: filter_content = No or filter_content = Yes and both text/html and text/plain accepted (in pass_mime_types) and both collapse_alternatives and convert_html_to_plaintext = No In these cases the message will be delivered as received, except if filter_content is Yes, the multipart/mixed outer part with only one multipart/alternative sub-part may be collapsed to just the multipart alternative part. As above but collapse_alternatives = Yes In this case all the alternatives other that the first (text/plain) will be removed. This is essentially the same whether or not there is a summary part. if collapse_alternatives = No and convert_html_to_plaintext = Yes All three parts will remain and all will be converted to text/plain and it will be up to the MUA to pick one which should be the text/plain conversion of the full message HTML part. There are other possibilities such as text/html not accepted in which case only the original text/plain part will remain. In short, Mailman will do the right thing, but Apple watch users probably won't like the result in some cases. Apple is notorious for playing fast and loose with email. I don't know if it's still the case, but at one point, Apple mail would let you drag and drop pictures into a plain text email so it would look to Apple mail users as some text [picture] more text [picture] etc. with a MIME structure like multipart/mixed text/plain image/jpeg text/plain image/jpeg text/plain and Apple mail would render what the sender saw and every other MUA would see a text/plain message with 4 attachments. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Mon May 18 05:44:24 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 18 May 2015 12:44:24 +0900 Subject: [Mailman-Users] Could Mailman cope with extra Mime sections intended for Apple Watches? In-Reply-To: <55592B56.1040107@msapiro.net> References: <55592B56.1040107@msapiro.net> Message-ID: <87pp5yzh0n.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > On 05/17/2015 04:04 PM, Peter Shute wrote: > > This isn't something that's happening right now, and I doubt it > > will, but you never know. Apple is playing with mail formats > > intended to display as a message summary on an Apple Watch, but > > show the full message on a larger device. Apparently it's a legal > > format, The MIME is legal. (More below.) The HTML may be legal, but it's deprecated (no DOCTYPE, no HTML element, etc). However, it's a very stupid format. Apple should just define and register an Apple-Watch-Summary header field and put it there. > > but lots of mail clients are getting it wrong, Too bad for them. What they are supposed to do work down the list of alternative types, and pick the last one they can handle. Presumably the Watch looks at the last text/html part, says to itself "Way too big!" and backs up to the tiny text/html part. > > and I'm wondering what Mailman would do with a message like that. > > Process it in conformance with the MIME RFCs and the list's content > filtering. AFAIK, Mailman doesn't read any content in the body (except maybe in spam filtering? but I think not even there), and filters only on MIME Content-Type and filename extensions in "name" parameters. > I looked at that, and it appears the structure of the message is as follows > > multipart/mixed > multipart/alternative > text/plain > plain text version > text/html > html 'summary' > text/html > html version Agree. > This is arguably non-conformant. multipart/alternative parts are > supposed to contain sub-parts which are alternative representations of > the message arranged in increasing order of complexity, Agree, with s/arguably// (nobody in their right mind who isn't an Apple Watch developer would argue this is conformant) and s/complexity/faithfulness/ per RFC 2046. Apple Watch fans might argue for s/complexity/preference/ (another term used in RFC 2046), but the interpretation that "whatever the author wants goes" is perverse in the presence of the word "faithfulness". > and MUAs are supposed to render the most complex (supposedly > closest to the original) that they understand. No, s/most complex/last/. Apple is being perverted here: they're relying on the letter of the law to "hide" the Watch summary from real MIME-conformant MUAs, and then having the Watch implement a non-conformant algorithm (there's nothing that says a conformant MUA can select on anything but MIME type). > In short, Mailman will do the right thing, but Apple watch users > probably won't like the result in some cases. Agreed. > > Apple is notorious for playing fast and loose with email. I don't know > if it's still the case, but at one point, Apple mail would let you drag > and drop pictures into a plain text email so it would look to Apple mail > users as > > some text > [picture] > more text > [picture] > etc. > > with a MIME structure like > > multipart/mixed > text/plain > image/jpeg > text/plain > image/jpeg > text/plain > > and Apple mail would render what the sender saw and every other MUA > would see a text/plain message with 4 attachments. > I've never had a problem with that structure, as long as disposition=inline (which is default for text/* for most MUAs). Even on a TTY, all MIME-capable Emacs MUAs will display that as Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. [Save attachment][Display attachment using external program] Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. [Save attachment][Display attachment using external program] Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. I know that there are GUI MUAs that can't handle it, but MIME did envision that structure leading to an inline presentation of the images (and audio or video or application/*, for that matter) if the terminal is capable. What pisses *me* off about Apple-generated email is their habit of hiding attachments inside of text/html parts as elements. (I consider my MUA to be broken because it doesn't display them even when I ask for the full MIME structure, but it's annoying that they aren't available when displaying the text/plain MIME part.) AFAICT, instead of multipart/alternative text/plain multipart/mixed text/html # containing CID references image/jpeg # with CID what should work fine is multipart/mixed multipart/alternative text/plain text/html # containing CID references image/jpeg # with CID or something like that. From billc_lists at greenbuilder.com Mon May 18 07:14:43 2015 From: billc_lists at greenbuilder.com (Bill Christensen) Date: Mon, 18 May 2015 00:14:43 -0500 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " In-Reply-To: <55592397.9030006@msapiro.net> References: <55592397.9030006@msapiro.net> Message-ID: On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro wrote: > On 05/17/2015 01:58 PM, Bill Christensen wrote: > > > > I'm using Gmail for all our email addresses, and pulling the mail into > > Mailman using Fetchmail. It's been working fine for years. > > > > One of my more important lists recently started getting this in the > > Fetchmail console: > > > > post script, list not found: > > > > fetchmail: Error writing to MDA: Broken pipe > > > > and the Mailman error log says: > > > > gate_news(12061): IOError : [Errno 13] Permission denied: > > '/opt/local/var/mailman/locks/gate_news.lock..12061.0' > > This is probably not related. Do you even have any lists with > Mail<->News gateways -> gateway_to_mail = Yes?. > Mailman's cron/gate_news runs by default every five minutes and does use > this lock to prevent concurrent updates. I would also expect to see > entries like 'Could not acquire gate_news lock' in the fromusenet log. > No news gateways. > > If this is a one-time occurrence, It was just a glitch. Maybe someone > manually ran cron/gate_news as a user not in Mailman's group. If you get > these every 5 minutes, there is a permissions issue, probably with the > user running this cron not being mailman, because if the locks directory > were not group mailman and group writable, lots more would be broken. > Yes, definitely every 5 minutes. > > > post(12068): post script, list not found: > > The post script invoked by > > /path/to/mailman/mail/mailman post > > in your fetchmail script says doesn't exist. > > > Mailman mischief log says: > > > > Hostile listname: > > This is consistent with the 'post script' report and says that > contains one or more characters not in the > Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The > default setting only allows letters, digits, '-', '+', '_', '.' and '='. > > Does contain characters outside this set or whatever set > you've specified? > Nope, it's four uppercase letters. No spaces, no punctuation. > > > In the smtp-failure log I'm seeing > > > > Message size exceeds fixed limit > > > > In General Options => Maximum length in kilobytes (KB) of a message body. > > Use 0 for no limit. I have '0'. > > > These two things are unrelated. The message in smtp-failure says Mailman > attempted to send a message which was larger than the MTA would accept. > In Postfix for example, this is the main.cf parameter message_size_limit. > Ok. I checked the messages waiting in Gmail. They're all small enough, no worrisome attachments or anything. I tried marking the oldest as read just in case it was jamming up the works, but the others are still in a logjam. > > > > I've run the check permissions script ( with -f), it changes nothing. It > > appears that there are 5 messages waiting for delivery, though I don't > see > > them in any of the queues. > > > If Mailman is retrying the smtp-failure, the message would be in > Mailman's 'retry' queue until Mailman eventually gives up. Or, they > could be still in the gmail inbox since fetchmail probably wouldn't > delete them as it couldn't deliver them. > Yes, there are still 5 messages waiting in Gmail. Fetchmail apparently hasn't marked them as read as it can't put them anywhere. > > > > This appears to have started around the time that I upgraded from Mailman > > 2.1.17 (or so) to 2.1.20 > > > > That list is also not archiving properly, so it clearly has problems > > > The listname problem would mess up a lot, but it looks like there would > be nothing to archive since nothing for that list is getting posted. > Makes sense. > > > > All the other lists on the server are working fine as far as I can tell. > > > > Any ideas as to what's wrong? > > > First, what's the list name? Once you fix that issue, that may be all, > or there may be shunted messages in Mailman's shunt queue to be unshunted. > As far as I can tell, the list name is correct. I checked bin/list_lists /etc/aliases /etc/postfix/virtual /etc/fetchmailrc and ran sudo newaliases it was lower case in a few places, so I changed those to upper case to match, just in case. then stopped/started Mailman. No change. I decided to take a chance and used your clone_list script to make a copy, moved the original archives to a backup location, then removed the original list and cloned back from the copy to the original name. Ran check_perms -f and checked them manually as well. All looks correct. And yet, it's still throwing the same errors. One improvement - after correcting permissions manually on .mbox/.mbox I can get to the archives again. They were -rw-rw-r-- 1 root staff and I set them to -rwxrwxr-x 1 root staff to match other working lists with public archives. Then I looked at mailman/lists/. The list in question was owned by my user, not root like the rest of them (possibly a result of clone list? the only two with that user were this list and the clone I had made earlier). Changed that to match the rest. Ownership of the enclosed files has me confused. All have the following files config.pck config.pck.last pending.pck request.pck some lists have some files with owner = _www, other files with owner = _mailman and still others lists have files with owner = my user . They're not consistent and I'm not really sure what they're all supposed to be, so I'd appreciate it if you'd enlighten me. Some also have 'en' directories, and I'm similarly unsure of what the correct owners are for those and their enclosed files - but I'm pretty sure they're probably not supposed to be my user. Next steps? From ericardosantos at gmail.com Mon May 18 14:32:08 2015 From: ericardosantos at gmail.com (Ricardo Santos) Date: Mon, 18 May 2015 08:32:08 -0400 Subject: [Mailman-Users] help with error on start In-Reply-To: <5558B9CF.9010800@msapiro.net> References: <5558B9CF.9010800@msapiro.net> Message-ID: Thanks Mark for you answer. I installed from a tutorial with this command (Centos 6.6) > yum --enablerepo=remi install mailman (Ver 3:2.1.12-18.el6 ) 2015-05-17 11:54 GMT-04:00 Mark Sapiro : > On 05/16/2015 06:55 PM, Ricardo Santos wrote: > > I installed mailman and have those message: > > > > /usr/lib/mailman/bin/check_db --all --verbose > > > > Traceback (most recent call last): > ... > > File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 37, in > > > > > from Mailman.i18n import _ > > > > File "/usr/lib/mailman/Mailman/i18n.py", line 36, in > > > > _ctype_charset = _get_ctype_charset() > > > Something is wrong here. The Mailman/i18n.py distributed by the GNU > Mailman project does not anything like the above line. > > How did you install Mailman? Where did /usr/lib/mailman/Mailman/i18n.py > come from? If this is a 'package', see . > > -- > 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/ericardosantos%40gmail.com > From dean.collins at insightplanners.com Mon May 18 19:42:35 2015 From: dean.collins at insightplanners.com (Dean Collins) Date: Mon, 18 May 2015 10:42:35 -0700 Subject: [Mailman-Users] Mail delivered locally but not to remote domains Message-ID: <016801d09192$068952a0$139bf7e0$@insightplanners.com> Sorry for not changing the subject last time. This is a server using the Plesk 12 control panel. The answer was: "Ensure that 'localhost' IP addresses is white listed in Plesk. Go to Tools & Settings > Mail Server Settings > White list To verity it open Tools & Settings > Mail Settings > White List and check whether it contain the following addresses: '::1/128' and '127.0.0.1'." Their knowledgebase article is at http://kb.odin.com/en/123649. Thank you! Dean -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+dean.collins=insightplanners.com at python.org] On Behalf Of Mark Sapiro Sent: Friday, May 15, 2015 12:59 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 On 05/15/2015 12:28 PM, Dean Collins wrote: > > Subscribers include me at mydomain.com (the same domain the list is on) > and various addresses from other domains/servers (a couple of servers > I run, plus Gmail and AT&T.) > > Mail sent to mylist at mydomain.com from any subscriber gets archived -- > and distributed to me at mydomain.com. But none of the other subscribers > receive the list mail. In order to be sure about anything, I'd need to see some logs like Mailman's smtp-failure log and the MTA logs, except I don't know anything about qmail. However, based on past experience I can say the following. 1) Mailman is delivering to the local MTA (qmail) and the mail is being delivered to local addresses but not being sent to remote domains. 2) Other locally generated mail is being sent to remote domains. When this happens it is probably an IPv4 vs. IPv6 issue. Here's one scenario. It may not be exactly this in your case, but you should be able to translate. The MTA has an idea of what addresses constitute the local network and will relay mail from those addresses to the outside. This includes say the IPv4 local host, something like 127.0.0.1, but not the IPv6 local host ::1. Mailman, by default, delivers to 'localhost'. 'localhost' in turn is defined as the IPv6 ::1 address. Thus Mailman's mail comes to the MTA from ::1 which is not in the MTA's notion of the local network, so the MTA refuses to relay the mail. This can be fixed in multiple ways. You can add the IPv6 local host to the MTA's local network. You can change /etc/hosts to associate 127.0.0.1 rather than ::1 with 'localhost'. You can set SMTPHOST in mm_cfg.py to something that will work. E.g., SMTPHOST = '127.0.0.1' Note that since I haven't seen your logs, the above scenario may be off. Perhaps it would be that Mailman is sending via the IPv4 loopback and qmail wants IPv6, but the idea is the same. -- 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/dean.collins%40insight planners.com From pshute at nuw.org.au Tue May 19 00:51:43 2015 From: pshute at nuw.org.au (Peter Shute) Date: Tue, 19 May 2015 08:51:43 +1000 Subject: [Mailman-Users] Could Mailman cope with extra Mime sections intended for Apple Watches? In-Reply-To: <55592B56.1040107@msapiro.net> References: <55592B56.1040107@msapiro.net> Message-ID: Thanks to you both for your input on this. It'll be interesting to see whether they persist with this mail format. Peter Shute > -----Original Message----- > From: Mailman-Users > [mailto:mailman-users-bounces+pshute=nuw.org.au at python.org] > On Behalf Of Mark Sapiro > Sent: Monday, 18 May 2015 9:59 AM > To: mailman-users at python.org > Subject: Re: [Mailman-Users] Could Mailman cope with extra > Mime sections intended for Apple Watches? > This is arguably non-conformant. multipart/alternative parts > are supposed to contain sub-parts which are alternative > representations of the message arranged in increasing order > of complexity, and MUAs are supposed to render the most > complex (supposedly closest to the original) that they > understand. The summary part is not a more faithful > representation of the complete message than even the > text/plain part, so it doesn't belong there. From mark at msapiro.net Tue May 19 06:07:08 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 18 May 2015 21:07:08 -0700 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " In-Reply-To: References: <55592397.9030006@msapiro.net> Message-ID: <555AB6EC.9070202@msapiro.net> On 05/17/2015 10:14 PM, Bill Christensen wrote: > On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro wrote: > >> If this is a one-time occurrence, It was just a glitch. Maybe someone >> manually ran cron/gate_news as a user not in Mailman's group. If you get >> these every 5 minutes, there is a permissions issue, probably with the >> user running this cron not being mailman, because if the locks directory >> were not group mailman and group writable, lots more would be broken. >> > > Yes, definitely every 5 minutes. There is a permissions issue on the locks directory. If you do ls -la /opt/local/var/mailman/locks/ you should see something similar to drwxrwsr-x 2 root mailman 4096 May 18 20:11 . drwxrwsr-x 9 root mailman 4096 May 10 2008 .. -rw-rw-r-- 2 mailman mailman 62 May 19 2015 master-qrunner -rw-rw-r-- 2 mailman mailman 62 May 19 2015 master-qrunner.host.pid There may or may not be other files, but the two master-qrunner files should be there and everything should be mailman's group (owner is not important) and both . and .. should have permissions as shown. If all this is correct, then either cron/gate_news is not running as the Mailman user (where is its crontab and what's in it?) or there may be some SELinux, apparmor or other security policy issue. >>> post(12068): post script, list not found: >> >> The post script invoked by >> >> /path/to/mailman/mail/mailman post >> >> in your fetchmail script says doesn't exist. >> >>> Mailman mischief log says: >>> >>> Hostile listname: >> >> This is consistent with the 'post script' report and says that >> contains one or more characters not in the >> Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The >> default setting only allows letters, digits, '-', '+', '_', '.' and '='. >> >> Does contain characters outside this set or whatever set >> you've specified? >> > > Nope, it's four uppercase letters. No spaces, no punctuation. List names are always all lower-case. The list may have a real_name attribute which is mixed case but it must differ only in case from the list's internal name. The name in the pipe to 'mailman/mail/mailman post ' command MUST be all lower case. > I checked the messages waiting in Gmail. They're all small enough, no > worrisome attachments or anything. I tried marking the oldest as read just > in case it was jamming up the works, but the others are still in a logjam. Because fetchmail can't deliver to the list until you fix the listname you pass to the 'mailman' wrapper if that's the issue. > Yes, there are still 5 messages waiting in Gmail. Fetchmail apparently > hasn't marked them as read as it can't put them anywhere. Yes. > As far as I can tell, the list name is correct. I checked > > bin/list_lists > > /etc/aliases > /etc/postfix/virtual > /etc/fetchmailrc > and ran sudo newaliases > > it was lower case in a few places, so I changed those to upper case to > match, just in case. That was the reverse of what you should have done. Hopefilly, the name of the list's directory in the /opt/local/var/mailman/lists/ directory is all lower case. It must also be all lower case in fetchmailrc and in the commands in /etc/aliases. I.e. an alias could be LISTNAME: '|/path/to/mailman/mail/mailman post listname' LISTNAME-admin: '|/path/to/mailman/mail/mailman admin listname' But it should match /etc/postfix/virtual, but it's best if it's all lower case. But then if fetchmail is delivering directly to /path/to/mailman/mail/mailman, none of the postfix stuff matters as it isn't used. > then stopped/started Mailman. No change. > > I decided to take a chance and used your clone_list script to make a copy, > moved the original archives to a backup location, then removed the original > list and cloned back from the copy to the original name. > > Ran check_perms -f and checked them manually as well. All looks correct. > > And yet, it's still throwing the same errors. > > One improvement - after correcting permissions manually on > .mbox/.mbox I can get to the archives again. They were > -rw-rw-r-- 1 root staff > and I set them to > -rwxrwxr-x 1 root staff > to match other working lists with public archives. It's a file. +x is not necessary on files. archives/private/.mbox should be drwxrwsr-x (note the SETGID), but no x of the file is needed (it's not executable). And I hope is all lower case. Also, it appears that Mailman's group is 'staff', not 'mailman' so everywhere I refer to it as 'mailman', read 'staff' > > Then I looked at mailman/lists/. The list in question was owned by my > user, not root like the rest of them (possibly a result of clone list? the > only two with that user were this list and the clone I had made earlier). > Changed that to match the rest. > > Ownership of the enclosed files has me confused. All have the following > files > > config.pck > > config.pck.last > > pending.pck > > request.pck > > some lists have some files with owner = _www, other files with owner = > _mailman and still others lists have files with owner = my user . They're > not consistent and I'm not really sure what they're all supposed to be, so > I'd appreciate it if you'd enlighten me. It doesn't matter. It is only the group that's important. The owner will reflect the user/process that created it, but in Mailman all the directories are SETGID and thus, things are created with the group of the containing directory, and permissions are by group. There are a couple of places where owner might matter. These are the owner of the aliases.db file with mailman's aliases and the owner of the archives/private/ directory itself if that directory is not o+x, but everywhere else, owner doesn't matter. But if _mailman is an owner, that says to me FreeBSD or maybe Darwin, and I would have thought Mailman's group would also be _mailman, not staff. > Some also have 'en' directories, and I'm similarly unsure of what the > correct owners are for those and their enclosed files - but I'm pretty sure > they're probably not supposed to be my user. The en/ directories contain list specific templates, and again, the owner doesn't matter as long as everything is in Mailman's group. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue May 19 06:30:12 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 18 May 2015 21:30:12 -0700 Subject: [Mailman-Users] help with error on start In-Reply-To: References: <5558B9CF.9010800@msapiro.net> Message-ID: <555ABC54.5020302@msapiro.net> On 05/18/2015 05:32 AM, Ricardo Santos wrote: > Thanks Mark for you answer. I installed from a tutorial with this command > (Centos 6.6) > >> yum --enablerepo=remi install mailman (Ver 3:2.1.12-18.el6 ) OK, but the /usr/lib/mailman/Mailman/i18n.py file in your installed Mailman doesn't look like the one distributed by GNU Mailman nor does it look like the one from RHEL 5 that I happen to have. So either something went wrong with your package install, or you will have to pursue this with Red Hat/Centos. Or, you could try downliading i18n.py from and replacing yours with that. That will probably get you past the current issue, but there may be other things wrong. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue May 19 07:54:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 18 May 2015 22:54:34 -0700 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " In-Reply-To: References: <55592397.9030006@msapiro.net> Message-ID: <555AD01A.8030609@msapiro.net> On 05/17/2015 10:14 PM, Bill Christensen wrote: > On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro wrote: > >> On 05/17/2015 01:58 PM, Bill Christensen wrote: >>> In the smtp-failure log I'm seeing >>> >>> Message size exceeds fixed limit >>> >>> In General Options => Maximum length in kilobytes (KB) of a message body. >>> Use 0 for no limit. I have '0'. >> >> >> These two things are unrelated. The message in smtp-failure says Mailman >> attempted to send a message which was larger than the MTA would accept. >> In Postfix for example, this is the main.cf parameter message_size_limit. >> > > Ok. > > I checked the messages waiting in Gmail. They're all small enough, no > worrisome attachments or anything. I tried marking the oldest as read just > in case it was jamming up the works, but the others are still in a logjam. The Message size exceeds fixed limit errors have nothing to do with the list messages that are not getting posted. They are messages being sent from Mailman to the MTA (Postfix ?) that are bigger than Postfix's message_size_limit. You'll have to look at the Postfix log for more info. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From billc_lists at greenbuilder.com Wed May 20 04:19:47 2015 From: billc_lists at greenbuilder.com (Bill Christensen) Date: Tue, 19 May 2015 21:19:47 -0500 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " In-Reply-To: <555AB6EC.9070202@msapiro.net> References: <55592397.9030006@msapiro.net> <555AB6EC.9070202@msapiro.net> Message-ID: Great! I fixed the list name uppercase problem and enough of the permissions and group assignments to get things running again last night. I still need to comb through and make sure that everything that's supposed to be is in the Mailman group, but that'll happen soon and the other major lists we run continue to work as intended. Thanks for your help! On Mon, May 18, 2015 at 11:07 PM, Mark Sapiro wrote: > On 05/17/2015 10:14 PM, Bill Christensen wrote: > > On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro wrote: > > > > >> If this is a one-time occurrence, It was just a glitch. Maybe someone > >> manually ran cron/gate_news as a user not in Mailman's group. If you get > >> these every 5 minutes, there is a permissions issue, probably with the > >> user running this cron not being mailman, because if the locks directory > >> were not group mailman and group writable, lots more would be broken. > >> > > > > Yes, definitely every 5 minutes. > > > There is a permissions issue on the locks directory. If you do > > ls -la /opt/local/var/mailman/locks/ > > you should see something similar to > > drwxrwsr-x 2 root mailman 4096 May 18 20:11 . > drwxrwsr-x 9 root mailman 4096 May 10 2008 .. > -rw-rw-r-- 2 mailman mailman 62 May 19 2015 master-qrunner > -rw-rw-r-- 2 mailman mailman 62 May 19 2015 master-qrunner.host.pid > > There may or may not be other files, but the two master-qrunner files > should be there and everything should be mailman's group (owner is not > important) and both . and .. should have permissions as shown. > > If all this is correct, then either cron/gate_news is not running as the > Mailman user (where is its crontab and what's in it?) or there may be > some SELinux, apparmor or other security policy issue. > > > > >>> post(12068): post script, list not found: > >> > >> The post script invoked by > >> > >> /path/to/mailman/mail/mailman post > >> > >> in your fetchmail script says doesn't exist. > >> > >>> Mailman mischief log says: > >>> > >>> Hostile listname: > >> > >> This is consistent with the 'post script' report and says that > >> contains one or more characters not in the > >> Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The > >> default setting only allows letters, digits, '-', '+', '_', '.' and '='. > >> > >> Does contain characters outside this set or whatever set > >> you've specified? > >> > > > > Nope, it's four uppercase letters. No spaces, no punctuation. > > > List names are always all lower-case. The list may have a real_name > attribute which is mixed case but it must differ only in case from the > list's internal name. > > The name in the pipe to 'mailman/mail/mailman post ' command > MUST be all lower case. > > > > I checked the messages waiting in Gmail. They're all small enough, no > > worrisome attachments or anything. I tried marking the oldest as read > just > > in case it was jamming up the works, but the others are still in a > logjam. > > > Because fetchmail can't deliver to the list until you fix the listname > you pass to the 'mailman' wrapper if that's the issue. > > > > Yes, there are still 5 messages waiting in Gmail. Fetchmail apparently > > hasn't marked them as read as it can't put them anywhere. > > > Yes. > > > > > As far as I can tell, the list name is correct. I checked > > > > bin/list_lists > > > > /etc/aliases > > /etc/postfix/virtual > > /etc/fetchmailrc > > and ran sudo newaliases > > > > it was lower case in a few places, so I changed those to upper case to > > match, just in case. > > > That was the reverse of what you should have done. Hopefilly, the name > of the list's directory in the /opt/local/var/mailman/lists/ directory > is all lower case. > > It must also be all lower case in fetchmailrc and in the commands in > /etc/aliases. > > I.e. an alias could be > > LISTNAME: '|/path/to/mailman/mail/mailman post listname' > LISTNAME-admin: '|/path/to/mailman/mail/mailman admin listname' > > But it should match /etc/postfix/virtual, but it's best if it's all > lower case. > > But then if fetchmail is delivering directly to > /path/to/mailman/mail/mailman, none of the postfix stuff matters as it > isn't used. > > > > then stopped/started Mailman. No change. > > > > I decided to take a chance and used your clone_list script to make a > copy, > > moved the original archives to a backup location, then removed the > original > > list and cloned back from the copy to the original name. > > > > Ran check_perms -f and checked them manually as well. All looks correct. > > > > And yet, it's still throwing the same errors. > > > > One improvement - after correcting permissions manually on > > .mbox/.mbox I can get to the archives again. They > were > > -rw-rw-r-- 1 root staff > > and I set them to > > -rwxrwxr-x 1 root staff > > to match other working lists with public archives. > > It's a file. +x is not necessary on files. > archives/private/.mbox should be drwxrwsr-x (note the SETGID), > but no x of the file is needed (it's not executable). And I hope > is all lower case. > > Also, it appears that Mailman's group is 'staff', not 'mailman' so > everywhere I refer to it as 'mailman', read 'staff' > > > > > Then I looked at mailman/lists/. The list in question was owned by my > > user, not root like the rest of them (possibly a result of clone list? > the > > only two with that user were this list and the clone I had made earlier). > > Changed that to match the rest. > > > > Ownership of the enclosed files has me confused. All have the following > > files > > > > config.pck > > > > config.pck.last > > > > pending.pck > > > > request.pck > > > > some lists have some files with owner = _www, other files with owner = > > _mailman and still others lists have files with owner = my user . > They're > > not consistent and I'm not really sure what they're all supposed to be, > so > > I'd appreciate it if you'd enlighten me. > > > It doesn't matter. It is only the group that's important. The owner will > reflect the user/process that created it, but in Mailman all the > directories are SETGID and thus, things are created with the group of > the containing directory, and permissions are by group. There are a > couple of places where owner might matter. These are the owner of the > aliases.db file with mailman's aliases and the owner of the > archives/private/ directory itself if that directory is not o+x, but > everywhere else, owner doesn't matter. > > But if _mailman is an owner, that says to me FreeBSD or maybe Darwin, > and I would have thought Mailman's group would also be _mailman, not staff. > > > > Some also have 'en' directories, and I'm similarly unsure of what the > > correct owners are for those and their enclosed files - but I'm pretty > sure > > they're probably not supposed to be my user. > > > The en/ directories contain list specific templates, and again, the > owner doesn't matter as long as everything is in Mailman's group. > > -- > 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/billc_lists%40greenbuilder.com > From mark at msapiro.net Wed May 20 04:44:42 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 May 2015 19:44:42 -0700 Subject: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: " In-Reply-To: References: <55592397.9030006@msapiro.net> <555AB6EC.9070202@msapiro.net> Message-ID: <555BF51A.7020409@msapiro.net> On 05/19/2015 07:19 PM, Bill Christensen wrote: > Great! I fixed the list name uppercase problem and enough of the > permissions and group assignments to get things running again last night. > > I still need to comb through and make sure that everything that's supposed > to be is in the Mailman group, but that'll happen soon and the other major > lists we run continue to work as intended. I know you said in your original post that you'd "run the check permissions script ( with -f), it changes nothing." Did you run it as root? It should fix most things with ownership and permission. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cczdao at unix.ccc.nottingham.ac.uk Wed May 20 15:38:01 2015 From: cczdao at unix.ccc.nottingham.ac.uk (David Osborne) Date: Wed, 20 May 2015 14:38:01 +0100 Subject: [Mailman-Users] Migrating a list to a new email address In-Reply-To: <555576C0.1060708@greenbuilder.com> References: <555576C0.1060708@greenbuilder.com> Message-ID: <555C8E39.5090800@unix.ccc.nottingham.ac.uk> On 15/05/15 05:32, Bill Christensen wrote: > I have a long running list with thousands of subscribers that needs to > move to a new set of email addresses. > > The existing list is announce-only, so doesn't get a whole lot of > traffic - typically at most a few outgoing emails a year. But some time > back a bot started sending spam registrations via hits to the web server > in the form > > > /mailman/subscribe.cgi/bwbnewsletter?email=@&fullname=&pw=123456789&pw-conf=123456789&language=en&digest=0&email-button=Subscribe. > > > I long ago routed real users to an alternative signup, but the spam > keeps coming, unrelenting, and are now anywhere between 1k and 10k per day. One of our lists was spammed in a similar way. The approach I took was to configure Apache to allow requests to /mailman/subscribe only when the referring page was on our server: SetEnvIf Referer lists\.my\.domain localreferer Order deny,allow Deny from all Allow from env=localreferer -- David Osborne University of Nottingham, UK This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. From adam-mailman at amyl.org.uk Wed May 20 16:07:35 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Wed, 20 May 2015 15:07:35 +0100 Subject: [Mailman-Users] Migrating a list to a new email address In-Reply-To: <555C8E39.5090800@unix.ccc.nottingham.ac.uk> References: <555576C0.1060708@greenbuilder.com> <555C8E39.5090800@unix.ccc.nottingham.ac.uk> Message-ID: <20150520140734.GB9573@hendricks.amyl.org.uk> On Wed, May 20, 2015 at 02:38:01PM +0100, David Osborne wrote: > On 15/05/15 05:32, Bill Christensen wrote: > >I long ago routed real users to an alternative signup, but the spam > >keeps coming, unrelenting, and are now anywhere between 1k and 10k per day. > > One of our lists was spammed in a similar way. The approach I took > was to configure Apache to allow requests to /mailman/subscribe only > when the referring page was on our server: I've used mod_security/fail2ban in the past, both work as well as might be expected. [?] > This message and any attachment are intended solely for the addressee > and may contain confidential information. If you have received this > message in error, please send it back to me, and immediately delete > it. Hum. -- "Celebrity can be malign in that it becomes a form of idolatry, and people live their lives vicariously through the rich and famous rather than attending to their own lives." -- John Sentamu From brian at emwd.com Wed May 20 15:44:47 2015 From: brian at emwd.com (Brian Carpenter) Date: Wed, 20 May 2015 09:44:47 -0400 Subject: [Mailman-Users] Subscription Spam Message-ID: <0afe01d09303$22f4fc10$68def430$@emwd.com> Hello My Fellow Mailman Users: Subscription spam is starting to become an issue with some of our mailing lists. Am I correct that the SUBSCRIBE_FORM_SECRET setting will help reduce the amount of subscription spam? Are there any other measures that can be done to reduce this type of spam? The pattern is one email address trying to subscribe to all the mailing lists of domain for several days. Banning the address works until a new email address is being used. Brian Carpenter Owner Providing Cloud Services and more for over 15 years. T: 336.755.0685 E: brian at emwd.com www.emwd.com From mark at msapiro.net Thu May 21 01:13:02 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 May 2015 16:13:02 -0700 Subject: [Mailman-Users] Subscription Spam In-Reply-To: <0afe01d09303$22f4fc10$68def430$@emwd.com> References: <0afe01d09303$22f4fc10$68def430$@emwd.com> Message-ID: <555D14FE.2060908@msapiro.net> On 05/20/2015 06:44 AM, Brian Carpenter wrote: > > Subscription spam is starting to become an issue with some of our mailing > lists. Am I correct that the SUBSCRIBE_FORM_SECRET setting will help reduce > the amount of subscription spam? Are there any other measures that can be > done to reduce this type of spam? The pattern is one email address trying to > subscribe to all the mailing lists of domain for several days. Banning the > address works until a new email address is being used. Yes, setting SUBSCRIBE_FORM_SECRET has so far been very effective. Also, see the post at -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From skip.montanaro at gmail.com Thu May 21 03:56:42 2015 From: skip.montanaro at gmail.com (Skip Montanaro) Date: Wed, 20 May 2015 20:56:42 -0500 Subject: [Mailman-Users] Mapping back from pipermail HTML to a specific message in the raw archive? Message-ID: I have a list of spam HTML messages in pipermail archives. I need to clear out their content (no great problem there), but I also want to clean the corresponding messages in the raw mbox file (zap subject, message body, etc, but leave a placeholder message so future archive regeneration doesn't mess up article numbers). Looking at one of these messages (HTML source), I see nothing like a message id which would allow me to unambiguously identify the corresponding raw message. Does something exist? If not, what heuristics have people developed to perform this mapping? Thanks, Skip Montanaro From mark at msapiro.net Thu May 21 04:38:49 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 May 2015 19:38:49 -0700 Subject: [Mailman-Users] Mapping back from pipermail HTML to a specific message in the raw archive? In-Reply-To: References: Message-ID: <555D4539.8000005@msapiro.net> On 05/20/2015 06:56 PM, Skip Montanaro wrote: > I have a list of spam HTML messages in pipermail archives. I need to clear > out their content (no great problem there), but I also want to clean the > corresponding messages in the raw mbox file (zap subject, message body, > etc, but leave a placeholder message so future archive regeneration doesn't > mess up article numbers). Looking at one of these messages (HTML source), I > see nothing like a message id which would allow me to unambiguously > identify the corresponding raw message. Does something exist? If not, what > heuristics have people developed to perform this mapping? The poster's address in the HTML is a link that looks like: > TITLE="Actual_Subject">poster at example.com >
The In-Reply-To fragment is the Message-ID. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From drsmith at fsu.edu Thu May 21 17:47:03 2015 From: drsmith at fsu.edu (Smith, David) Date: Thu, 21 May 2015 15:47:03 +0000 Subject: [Mailman-Users] getting count of users Message-ID: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> Hi folks, I've written a little script to give me output of the following from any or all listservs we manage. Listname, Last Activity, List Creation Date, Anonymous List, Admins I'd like to add a count of users into the mix, but just cannot seem to get my head around it. Here is my script : """Display the last post time for a list or all lists. Save as bin/FSU_listCheck.py Run via bin/withlist -r FSU_listCheck listname or bin/withlist -a -r FSU_listCheck to do all lists. """ import time def FSU_listCheck(mlist): #This process outputs the following : listname, Last Activity, List Creation Date, Anonymous List, Admins print '%s; %s; %s; %s; %s' % ( mlist.real_name, time.strftime('%Y/%m/%d %I:%M %p',time.localtime(mlist.last_post_time)), time.strftime('%Y/%m/%d %I:%M %p',time.localtime(mlist.created_at)), mlist.advertised, mlist.owner ) I am sure it's some sort of mlist.usernames and then maybe using a cmd= 'wc -l' , but I cannot get it to jibe.. any help? Thanks! Dave Smith drsmith at fsu.edu (850)645-8024 Linux Administrators its-unixadmins at fsu.edu (850)644-2591 Information Technology Services Florida State University From drsmith at fsu.edu Thu May 21 19:35:49 2015 From: drsmith at fsu.edu (Smith, David) Date: Thu, 21 May 2015 17:35:49 +0000 Subject: [Mailman-Users] getting count of users In-Reply-To: References: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> Message-ID: <9A6683009E58C8428500D51565BD13541C8B0633@fsu-exch-nwr03.fsu.edu> PERFECT! Thanks Mat .. that was the key .. 'len' I'll remember that one , I just wasn't even thinking about that. I was so ingrained on using 'cmd' .. *sigh Thanks! Dave Smith???????? ???????????????? ?????????????????????????????? drsmith at fsu.edu???????? ?? ??????????????? (850)645-8024 Linux Administrators?? ?????????????? its-unixadmins at fsu.edu?? ?????????? (850)644-2591 Information Technology Services? ???????????Florida State University -----Original Message----- From: mat houser [mailto:mhouser at uwm.edu] Sent: Thursday, May 21, 2015 1:31 PM To: Smith, David Cc: mailman-users at python.org Subject: Re: [Mailman-Users] getting count of users len(mlist.members) should work. -- ------------- mat:houser mhouser at uwm.edu uwm:uits:iam-support ------------- On Thu, 21 May 2015, Smith, David wrote: Hi folks, I've written a little script to give me output of the following from any or all listservs we manage. Listname, Last Activity, List Creation Date, Anonymous List, Admins I'd like to add a count of users into the mix, but just cannot seem to get my head around it. Here is my script : """Display the last post time for a list or all lists. Save as bin/FSU_listCheck.py Run via bin/withlist -r FSU_listCheck listname or bin/withlist -a -r FSU_listCheck to do all lists. """ import time def FSU_listCheck(mlist): #This process outputs the following : listname, Last Activity, List Creation Date, Anonymous List, Admins print '%s; %s; %s; %s; %s' % ( mlist.real_name, time.strftime('%Y/%m/%d %I:%M %p',time.localtime(mlist.last_post_time)), time.strftime('%Y/%m/%d %I:%M %p',time.localtime(mlist.created_at)), mlist.advertised, mlist.owner ) I am sure it's some sort of mlist.usernames and then maybe using a cmd= 'wc -l' , but I cannot get it to jibe.. any help? Thanks! Dave Smith drsmith at fsu.edu (850)645-8024 Linux Administrators its-unixadmins at fsu.edu (850)644-2591 Information Technology Services Florida State University ------------------------------------------------------ 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/mhouser%40uwm.edu From mark at msapiro.net Thu May 21 20:05:54 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 21 May 2015 11:05:54 -0700 Subject: [Mailman-Users] getting count of users In-Reply-To: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> References: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> Message-ID: <555E1E82.2070607@msapiro.net> On 05/21/2015 08:47 AM, Smith, David wrote: > Hi folks, > > I've written a little script to give me output of the following from any or all listservs we manage. I didn't think Listserv(r) was written in Python or had a withlist script ;) See > I am sure it's some sort of mlist.usernames and then maybe using a cmd= 'wc -l' , but I cannot get it to jibe.. any help? The number of list members is len(mlist.getMembers()) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From drsmith at fsu.edu Thu May 21 20:47:52 2015 From: drsmith at fsu.edu (Smith, David) Date: Thu, 21 May 2015 18:47:52 +0000 Subject: [Mailman-Users] getting count of users In-Reply-To: <555E1E82.2070607@msapiro.net> References: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> <555E1E82.2070607@msapiro.net> Message-ID: <9A6683009E58C8428500D51565BD13541C8B075E@fsu-exch-nwr03.fsu.edu> Sorry Mark! :) GNU Mailman will be remembered from now on .. Thanks! Dave Smith???????? ???????????????? ?????????????????????????????? drsmith at fsu.edu???????? ?? ??????????????? (850)645-8024 Linux Administrators?? ?????????????? its-unixadmins at fsu.edu?? ?????????? (850)644-2591 Information Technology Services? ???????????Florida State University -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+drsmith=fsu.edu at python.org] On Behalf Of Mark Sapiro Sent: Thursday, May 21, 2015 2:06 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] getting count of users On 05/21/2015 08:47 AM, Smith, David wrote: > Hi folks, > > I've written a little script to give me output of the following from any or all listservs we manage. I didn't think Listserv(r) was written in Python or had a withlist script ;) See > I am sure it's some sort of mlist.usernames and then maybe using a cmd= 'wc -l' , but I cannot get it to jibe.. any help? The number of list members is len(mlist.getMembers()) -- 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/drsmith%40fsu.edu From mhouser at uwm.edu Thu May 21 19:31:02 2015 From: mhouser at uwm.edu (mat houser) Date: Thu, 21 May 2015 12:31:02 -0500 (CDT) Subject: [Mailman-Users] getting count of users In-Reply-To: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> References: <9A6683009E58C8428500D51565BD13541C8B0510@fsu-exch-nwr03.fsu.edu> Message-ID: len(mlist.members) should work. -- ------------- mat:houser mhouser at uwm.edu uwm:uits:iam-support ------------- On Thu, 21 May 2015, Smith, David wrote: Hi folks, I've written a little script to give me output of the following from any or all listservs we manage. Listname, Last Activity, List Creation Date, Anonymous List, Admins I'd like to add a count of users into the mix, but just cannot seem to get my head around it. Here is my script : """Display the last post time for a list or all lists. Save as bin/FSU_listCheck.py Run via bin/withlist -r FSU_listCheck listname or bin/withlist -a -r FSU_listCheck to do all lists. """ import time def FSU_listCheck(mlist): #This process outputs the following : listname, Last Activity, List Creation Date, Anonymous List, Admins print '%s; %s; %s; %s; %s' % ( mlist.real_name, time.strftime('%Y/%m/%d %I:%M %p',time.localtime(mlist.last_post_time)), time.strftime('%Y/%m/%d %I:%M %p',time.localtime(mlist.created_at)), mlist.advertised, mlist.owner ) I am sure it's some sort of mlist.usernames and then maybe using a cmd= 'wc -l' , but I cannot get it to jibe.. any help? Thanks! Dave Smith drsmith at fsu.edu (850)645-8024 Linux Administrators its-unixadmins at fsu.edu (850)644-2591 Information Technology Services Florida State University ------------------------------------------------------ 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/mhouser%40uwm.edu From hansen at rc.org Sat May 23 23:45:00 2015 From: hansen at rc.org (Allan Hansen) Date: Sat, 23 May 2015 14:45:00 -0700 Subject: [Mailman-Users] DMARC hack Message-ID: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> Hi, I have waited almost a year for AOL and Yahoo to admit that they messed up and to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at me because I won?t let them post. A number now have two subscriptions, one for posting (from GMail) and another for receiving the messages. So against my better judgement, I included this hack in Cleanse.py; 22c22 < from email.Utils import formataddr, parseaddr ? >from email.Utils import formataddr 69,74d68 < < # Added to deal with DMARC issuej < name, addrs = parseaddr(msg.get('from')) < addrs += '.invalid' < del msg['from'] < msg['from'] = formataddr((name, addrs)) \ No newline at end of file I found it in the discussion list. I don?t get compile errors, but Cleanse.pyc is not being updated. I have stopped and restarted Mailman and I have also rebooted, but same non-action. I have not tried ?compileall? and am not eager to, either (permissions, where to invoke, etc). Any suggestions? The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14 Yours, Allan From mark at msapiro.net Sun May 24 01:39:46 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 May 2015 16:39:46 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> Message-ID: <55610FC2.2000202@msapiro.net> On 05/23/2015 02:45 PM, Allan Hansen wrote: > > So against my better judgement, I included this hack in Cleanse.py; > > 22c22 > < from email.Utils import formataddr, parseaddr > ? >>from email.Utils import formataddr > > 69,74d68 > < > < # Added to deal with DMARC issuej > < name, addrs = parseaddr(msg.get('from')) > < addrs += '.invalid' > < del msg['from'] > < msg['from'] = formataddr((name, addrs)) > \ No newline at end of filez- It would help me understand what you did if you would post diff -u Cleanse.py.original Cleanse.py.new So that your patch is not reversed and I can see context, but it looks like you replaced del msg['x-pmrqc'] at the end of Cleanse.py with your added code. If that is what you did, why delete the del msg['x-pmrqc'] line? In any case, I will refrain from discussing the merits of adding .invalid to the domain, but why do it for all domains and not just yahoo.com and aol.com or actually look up the From: domain's DMARC policy and only do it for domains with DMARC p=reject. > I don?t get compile errors, but Cleanse.pyc is not being updated. I have stopped and restarted Mailman and I have also rebooted, but same non-action. I have not tried ?compileall? and am not eager to, either (permissions, where to invoke, etc). Any suggestions? Does your hack do what you expect? Cleanse.pyc will not be updated until Mailman processes at least one post and then only if IncomingRunner can write to Cleanse.pyc. It may be that Cleanse.pyc is in Mailman's group but not owned by the Mailman user and is not group writable. None of this matters. when Python imports the module, it will notice that Cleanse.py is newer than Cleanse.pyc and will load and compile Cleanse.py. Then it will write the byte-compiled result to Cleanse.pyc if it can, but in any case, it will be using the code in Cleanse.py. If there is a problem with permissions, you can compile Cleanse.py with compileall as a user that can write the file, but it won't change the results. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From hansen at rc.org Sun May 24 02:02:36 2015 From: hansen at rc.org (Allan Hansen) Date: Sat, 23 May 2015 17:02:36 -0700 Subject: [Mailman-Users] DMARC hack Message-ID: Never mind - it started working. I just had to leave the house and come back. Mayby the issues at work can be done that way, too. :-) Allan Hi, I have waited almost a year for AOL and Yahoo to admit that they messed up and to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at me because I won?t let them post. A number now have two subscriptions, one for posting (from GMail) and another for receiving the messages. So against my better judgement, I included this hack in Cleanse.py; 22c22 < from email.Utils import formataddr, parseaddr ? > from email.Utils import formataddr 69,74d68 < < # Added to deal with DMARC issuej < name, addrs = parseaddr(msg.get('from')) < addrs += '.invalid' < del msg['from'] < msg['from'] = formataddr((name, addrs)) \ No newline at end of file I found it in the discussion list. I don?t get compile errors, but Cleanse.pyc is not being updated. I have stopped and restarted Mailman and I have also rebooted, but same non-action. I have not tried ?compileall? and am not eager to, either (permissions, where to invoke, etc). Any suggestions? The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14 Yours, Allan From billc_lists at greenbuilder.com Sun May 24 03:10:49 2015 From: billc_lists at greenbuilder.com (Bill Christensen) Date: Sat, 23 May 2015 20:10:49 -0500 Subject: [Mailman-Users] Migrating a list to a new email address In-Reply-To: <20150520140734.GB9573@hendricks.amyl.org.uk> References: <555576C0.1060708@greenbuilder.com> <555C8E39.5090800@unix.ccc.nottingham.ac.uk> <20150520140734.GB9573@hendricks.amyl.org.uk> Message-ID: Mark's fix: If your Mailman is at least 2.1.16, all you need to do is set SUBSCRIBE_FORM_SECRET = 'Some string unique to your site" in mm_cfg.py, and that attack will no longer work. Is working fine. But thanks for the alternative suggestions. I've got a copy of fail2ban ready to install but just haven't had time to configure it yet. On Wed, May 20, 2015 at 9:07 AM, Adam McGreggor wrote: > On Wed, May 20, 2015 at 02:38:01PM +0100, David Osborne wrote: > > On 15/05/15 05:32, Bill Christensen wrote: > > >I long ago routed real users to an alternative signup, but the spam > > >keeps coming, unrelenting, and are now anywhere between 1k and 10k per > day. > > > > One of our lists was spammed in a similar way. The approach I took > > was to configure Apache to allow requests to /mailman/subscribe only > > when the referring page was on our server: > > I've used mod_security/fail2ban in the past, both work as well as > might be expected. > > [?] > > > This message and any attachment are intended solely for the addressee > > and may contain confidential information. If you have received this > > message in error, please send it back to me, and immediately delete > > it. > > Hum. > > > -- > "Celebrity can be malign in that it becomes a form of idolatry, and > people live their lives vicariously through the rich and famous rather > than attending to their own lives." > -- John Sentamu > ------------------------------------------------------ > 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/billc_lists%40greenbuilder.com > From stephen at xemacs.org Sun May 24 15:10:50 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 24 May 2015 22:10:50 +0900 Subject: [Mailman-Users] DMARC hack In-Reply-To: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> Message-ID: <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> Allan Hansen writes: > 69,74d68 > < > < # Added to deal with DMARC issuej > < name, addrs = parseaddr(msg.get('from')) > < addrs += '.invalid' This is known to be a bad idea, as it increases the spam score at many sites (because the author's mail domain doesn't resolve). Subscribers at such sites may have trouble receiving mail, and your list(s) may be tagged as suspicious. I would recommend the From-munging approach: name, addr = parseadder(msg.get('from')) if addr.endswith('aol.com') or addr.endswith('yahoo.com'): # I forget what happens if it's a bare address name = "%s (%s) via list" % (name if name else "Anonymous", addr) addr = del msg['from'] msg['from'] = formataddr((name, addr)) Mark (or you) probably have better code, and in some cases you may want to add the addr to the Reply-To field. > < del msg['from'] > < msg['from'] = formataddr((name, addrs)) > \ No newline at end of file From hansen at rc.org Sun May 24 18:02:02 2015 From: hansen at rc.org (Allan Hansen) Date: Sun, 24 May 2015 09:02:02 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> Stephen, Much appreciated. Checking for aol.com and yahoo.com here alone will not work. I have a bunch of other subscribers that have accounts with providers that are owned by Yahoo (mostly) and AOL, but whose addresses are not of this form. I would have to do this for all addresses, to be safe. If I do this and add the bit about the Reply-To, what would the code look like? Yours, Allan > On May 24, 2015, at 6:10 , Stephen J. Turnbull wrote: > > Allan Hansen writes: > >> 69,74d68 >> < >> < # Added to deal with DMARC issuej >> < name, addrs = parseaddr(msg.get('from')) >> < addrs += '.invalid' > > This is known to be a bad idea, as it increases the spam score at many > sites (because the author's mail domain doesn't resolve). Subscribers > at such sites may have trouble receiving mail, and your list(s) may be > tagged as suspicious. > > I would recommend the From-munging approach: > > name, addr = parseadder(msg.get('from')) > if addr.endswith('aol.com') or addr.endswith('yahoo.com'): > # I forget what happens if it's a bare address > name = "%s (%s) via list" % (name if name else "Anonymous", addr) > addr = > del msg['from'] > msg['from'] = formataddr((name, addr)) > > Mark (or you) probably have better code, and in some cases you may > want to add the addr to the Reply-To field. > >> < del msg['from'] >> < msg['from'] = formataddr((name, addrs)) >> \ No newline at end of file > From andrew at hodgsonfamily.org Sun May 24 20:06:08 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Sun, 24 May 2015 18:06:08 +0000 Subject: [Mailman-Users] DMARC hack In-Reply-To: <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> Message-ID: Allan Hansen wrote: >Stephen, >Much appreciated. >Checking for aol.com and yahoo.com here alone will not work. I have a bunch of other subscribers that have accounts with providers that are owned by Yahoo (mostly) and AOL, but whose addresses are not of this form. >I would have to do this for all addresses, to be safe. Probably a good reason why you can't do this, but is there any way you can upgrade to the latest 2.1.20? It means the code for doing this is already there for you and will work by looking up the relevant domain's DMARC policy in DNS. I use it on all the lists here by default now by munging the From: header and it works when it needs to. Thanks. Andrew. From hansen at rc.org Sun May 24 20:11:30 2015 From: hansen at rc.org (Allan Hansen) Date: Sun, 24 May 2015 11:11:30 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> Message-ID: <1BB16389-F6EA-4D22-854F-14DE254B33D3@rc.org> Hi Stephen, Yes, there is a good reason. I?m using Mailman as it came with the OS X Server and am not prepared to replace it. Also, Mailman no longer comes pre-installed on the Apple platform, so I?m basically stuck. This is why I tried the simplest hack I could find. I have 44 busy lists and I?m weary of messing anything up, as I have basically no time or background to fix it. Yours, Allan > On May 24, 2015, at 11:06 , Andrew Hodgson wrote: > > Allan Hansen wrote: > >> Stephen, > >> Much appreciated. >> Checking for aol.com and yahoo.com here alone will not work. I have a bunch of other subscribers that have accounts with providers that are owned by Yahoo (mostly) and AOL, but whose addresses are not of this form. >> I would have to do this for all addresses, to be safe. > > Probably a good reason why you can't do this, but is there any way you can upgrade to the latest 2.1.20? It means the code for doing this is already there for you and will work by looking up the relevant domain's DMARC policy in DNS. I use it on all the lists here by default now by munging the From: header and it works when it needs to. > > Thanks. > Andrew. From stephen at xemacs.org Sun May 24 20:14:21 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 25 May 2015 03:14:21 +0900 Subject: [Mailman-Users] DMARC hack In-Reply-To: <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> Message-ID: <877frxhmgy.fsf@uwakimon.sk.tsukuba.ac.jp> Allan Hansen writes: > Checking for aol.com and yahoo.com here alone will not work. I have > a bunch of other subscribers that have accounts with providers > that are owned by Yahoo (mostly) and AOL, but whose addresses are > not of this form. Oddly enough, it turns out that they only use DMARC p=reject at their principal domain (aol.com and yahoo.com). You can check for any given domain by prepending _dmarc. and checking the TXT record. For example, for aol.com it would be "host -t TXT _dmarc.aol.com" if you have the host utility for doing DNS lookups. > I would have to do this for all addresses, to be safe. If you're worried about safety and care about conforming to standards, you really should upgrade to at least Mailman 2.1.18-1. That allows you to be nonconformant only for authors whose addresses are in troublesome domains, and handles the reply-to issue as well as possible (making everybody happy isn't quite possible). I'm sure you have good reason for not doing so *right* *now*, but keep it in mind. > If I do this and add the bit about the Reply-To, what would the > code look like? If you do it for all mail, you just delete the "if" line and shift everything left one dedent. name, addr = parseaddr(msg.get('from')) name = "%s (%s) via list" % (name if name else "Anonymous", addr) fromaddr = mlist.GetListEmail() del msg['from'] msg['from'] = formataddr((name, addr)) # reply-to handling goes here I'm not comfortable trying to say what to do about reply-to, because it's quite complicated depending on how you want to handle each of a large number of variations: what to do with a preexisting Reply-To and whether to put the list and/or the from address there. See the Mailman/Handlers/CookHeaders.py file in the Mailman distribution. From mark at msapiro.net Sun May 24 21:56:25 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 24 May 2015 12:56:25 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> Message-ID: <55622CE9.40605@msapiro.net> On 05/24/2015 09:02 AM, Allan Hansen wrote: > Checking for aol.com and yahoo.com here alone will not work. I have a bunch of other subscribers that have > accounts with providers that are owned by Yahoo (mostly) and AOL, but whose addresses are not of this form. > I would have to do this for all addresses, to be safe. You only have to mung those addresses for which the domain publishes a DMARC p=reject policy. This almost certainly does not include aol and yahoo provided 'other' domains. The code in Mailman 2.1.18+ actually does a DNS lookup of the DMARC policy. In all the myriad @python.org list posts, the only domains I see with p=reject are aol.com, yahoo.com and paypal.com. > If I do this and add the bit about the Reply-To, what would the code look like? I'm currently between flights in an airport. When I get a chance, I'll post some code. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From hansen at rc.org Mon May 25 00:19:37 2015 From: hansen at rc.org (Allan Hansen) Date: Sun, 24 May 2015 15:19:37 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <877frxhmgy.fsf@uwakimon.sk.tsukuba.ac.jp> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> <877frxhmgy.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: I wonder why then I got a bunch of issues with btopenworld.com, which apparently is Yahoo based. I just checked btopenworld.com with the ?host? command and as you say, it has no ?reject?: $ host -t TXT _dmarc.btopenworld.com _dmarc.btopenworld.com descriptive text "v=DMARC1\; p=none\; fo=1\; rua=mailto:dmarcagg at btinternet.com, mailto:dmarc_agg at auth.returnpath.net\;" $ host -t TXT _dmarc.yahoo.com _dmarc.yahoo.com descriptive text "v=DMARC1\; p=reject\; sp=none\; pct=100\; rua=mailto:dmarc-yahoo-rua at yahoo-inc.com, mailto:dmarc_y_rua at yahoo.com\;? Here is the reject notice: Final-Recipient: rfc822; subscriber at aol.com Original-Recipient: rfc822;subscriber at aol.com Action: failed Status: 5.2.1 Remote-MTA: dns; mailin-04.mx.aol.com Diagnostic-Code: smtp; 521 5.2.1 : AOL will not accept delivery of this message. Date: May 13, 2015 at 07:52:17 PDT From: To: Subject: subject Reply-To: sender at btopenworld.com And yes, as I just wrote, I have good reasons for keeping this as simple as I possibly can. Upgrading is not simple, I suspect, though I?d love to move to 3.0, as I have a lot of lists, with subscribers on many lists simulteneously. Yours, Allan > On May 24, 2015, at 11:14 , Stephen J. Turnbull wrote: > > Allan Hansen writes: > >> Checking for aol.com and yahoo.com here alone will not work. I have >> a bunch of other subscribers that have accounts with providers >> that are owned by Yahoo (mostly) and AOL, but whose addresses are >> not of this form. > > Oddly enough, it turns out that they only use DMARC p=reject at their > principal domain (aol.com and yahoo.com). You can check for any given > domain by prepending _dmarc. and checking the TXT record. For > example, for aol.com it would be "host -t TXT _dmarc.aol.com" if you > have the host utility for doing DNS lookups. > >> I would have to do this for all addresses, to be safe. > > If you're worried about safety and care about conforming to standards, > you really should upgrade to at least Mailman 2.1.18-1. That allows > you to be nonconformant only for authors whose addresses are in > troublesome domains, and handles the reply-to issue as well as > possible (making everybody happy isn't quite possible). I'm sure you > have good reason for not doing so *right* *now*, but keep it in mind. > >> If I do this and add the bit about the Reply-To, what would the >> code look like? > > If you do it for all mail, you just delete the "if" line and shift > everything left one dedent. > > name, addr = parseaddr(msg.get('from')) > name = "%s (%s) via list" % (name if name else "Anonymous", addr) > fromaddr = mlist.GetListEmail() > del msg['from'] > msg['from'] = formataddr((name, addr)) > # reply-to handling goes here > > I'm not comfortable trying to say what to do about reply-to, because > it's quite complicated depending on how you want to handle each of a > large number of variations: what to do with a preexisting Reply-To and > whether to put the list and/or the from address there. See the > Mailman/Handlers/CookHeaders.py file in the Mailman distribution. > From mark at msapiro.net Mon May 25 02:40:12 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 24 May 2015 17:40:12 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> <877frxhmgy.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <55626F6C.5090601@msapiro.net> On 05/24/2015 03:19 PM, Allan Hansen wrote: > > $ host -t TXT _dmarc.btopenworld.com > _dmarc.btopenworld.com descriptive text "v=DMARC1\; p=none\; fo=1\; rua=mailto:dmarcagg at btinternet.com, mailto:dmarc_agg at auth.returnpath.net\;" The domain publishes DMARC p=none. Thus, no ISP should treat a message From: someone at btopenworld.com any differently than the same message From: someone at elsewhere.com. > Here is the reject notice: > > Final-Recipient: rfc822; subscriber at aol.com > Original-Recipient: rfc822;subscriber at aol.com > Action: failed > Status: 5.2.1 > Remote-MTA: dns; mailin-04.mx.aol.com > Diagnostic-Code: smtp; 521 5.2.1 : AOL will not accept delivery of this > message. I see this exact rejection reliably from AOL. When an AOL user posts to a list, the list post sent back to that user is rejected in this way, even though AOL accepts the same post for delivery to other AOL users. I have experimented with this using my own AOL address to send and reflecting various versions of the message back. I munged a lot of headers including I think Message-Id:, and I always got rejected. I gave up trying to figure out what AOL is looking at, but this reject occurs to list posts from aol.com, even though the From: is munged to the list address. In any case, that's not the reject reason uses for a reject due to DMARC policy. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From regis92130 at gmail.com Sun May 24 12:17:02 2015 From: regis92130 at gmail.com (Regis) Date: Sun, 24 May 2015 12:17:02 +0200 Subject: [Mailman-Users] How to know if all messages were distributed Message-ID: <5561A51E.30600@gmail.com> Hello, I sent my first mailingfew days ago to an important number of subscribers : about 200 000 (!). However, i wonder if the distribution has been complete... Indeed 72 hours after the mailing, i continue to see permanently about 500 messages in the queue of my messaging server (i have a linux centOS VPS with Qmail). But what is strange is that actually some of those messages were really distributed : I am sure because I got return receipt emails for them ! So i am confused on the total distribution of my mailing to all subscribers : is there a possibility so see the number of messages processed or not yet processed directly from the server (logs...) ? THANKS A LOT :-) Regis. From mark at msapiro.net Mon May 25 17:03:07 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 May 2015 08:03:07 -0700 Subject: [Mailman-Users] getting count of users In-Reply-To: References: Message-ID: <556339AB.1080108@msapiro.net> mat houser wrote: > len(mlist.members) should work. This is wrong for two reasons. 1) mlist.members is not defined in the MemberAdaptor API, it is an artifact of OldStyleMemberships.py which is the default MemberAdaptor, but not necessarily the one in use for a particular list, and more importantly, 2) even with OldStyleMemberships.py, the mlist.members dictionary only includes regular members, not digest members. The proper public methods which return lists of all members, regular members and digest members are respectively getMembers, getRegularMemberKeys and getDigestMemberKeys. Thus, as I posted previously, the way to get the total number of members is len(mlist.getMembers()) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon May 25 17:22:02 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 May 2015 08:22:02 -0700 Subject: [Mailman-Users] How to know if all messages were distributed In-Reply-To: <5561A51E.30600@gmail.com> References: <5561A51E.30600@gmail.com> Message-ID: <55633E1A.9040102@msapiro.net> On 05/24/2015 03:17 AM, Regis wrote: > > However, i wonder if the distribution has been complete... > > Indeed 72 hours after the mailing, i continue to see permanently about > 500 messages in the queue of my messaging server (i have a linux centOS > VPS with Qmail). First of all, your question is a Qmail question, not a Mailman question. >From the Mailman standpoint, when you see a message like May 25 03:40:03 2015 (14302) But what is strange is that actually some of those messages were really > distributed : I am sure because I got return receipt emails for them ! > > So i am confused on the total distribution of my mailing to all > subscribers : is there a possibility so see the number of messages > processed or not yet processed directly from the server (logs...) ? Again, this is a Qmail question. What I suspect you're seeing is a result of Mailman delivering non-VERPed, non-personalized messages in chunks of up to SMTP_MAX_RCPTS recipients per SMTP transaction and Qmail experiencing retryable errors on some of the recipients in the chunk and delivering others. But ask someone who knows Qmail if you want a definitive answer. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Mon May 25 17:46:33 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 26 May 2015 00:46:33 +0900 Subject: [Mailman-Users] How to know if all messages were distributed In-Reply-To: <5561A51E.30600@gmail.com> References: <5561A51E.30600@gmail.com> Message-ID: <871ti4hd7q.fsf@uwakimon.sk.tsukuba.ac.jp> Regis writes: > Indeed 72 hours after the mailing, i continue to see permanently about > 500 messages in the queue of my messaging server (i have a linux centOS > VPS with Qmail). Using Qmail is asking for trouble. Dan Bernstein is unquestionably a genius, but his software tends to assume that the world is a saner place than it actually is, and doesn't work and play well with others. I'll assume that you have perfectly good reasons for using Qmail rather than Exim or Postfix that are more commonly used with Mailman, but you should be aware that most of the folks on this list are experienced with Exim, Postfix, and/or Sendmail, and for Qmail-specific issues, or interactions between Qmail and Mailman, you probably need to go to a Qmail channel. First question: *which queue*? Mailman has its queues, which you can examine using ls on the queue directory or mailman/bin/show_qfiles on the individual queued messages. Qmail also has its own queue(s), and if the messages are in the Qmail queues, *it's very unlikely to be a Mailman-related problem*. By design, once a mail server has accepted a message, the mail server is fully responsible for its deliver, or for reporting non-delivery. > But what is strange is that actually some of those messages were > really distributed : I am sure because I got return receipt emails > for them ! You've cross checked the Message-IDs? What do you mean by "return receipt"? Are you sure they are not "bounce" messages, which indicate that mailwas *not* delivered? > So i am confused on the total distribution of my mailing to all > subscribers : is there a possibility so see the number of messages > processed or not yet processed directly from the server (logs...) ? I don't know about where Centos keeps Mailman's logs and queues, but yes, you can look at the logs and queues once you find them. The "post" log tells you what posts Mailman has received, but not their disposition. The "smtp" log tells you what messages have been sent (by message-id and time, and how long it took to process the smtp transaction), but due to the nature of the outgoing runner, there are typically many log messages for each post. Mark may have a script for summing them up to find out how many have actually been delivered. I'm not sure exactly what goes into the smtp-failure log, but I would suppose that would record cases where qmail tells mailman that it can't deliver the message for some reason. I'm not sure if it records tempfails, and for tempfails there's no way for qmail to tell mailman about retries whether they succeed or fail. For the qfiles, most likely you just care about if they're there in "outgoing" or "retry". You might also look in the "shunt" queue directory for "broken" messages that Mailman can't process. From mark at msapiro.net Mon May 25 18:54:01 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 May 2015 09:54:01 -0700 Subject: [Mailman-Users] How to know if all messages were distributed In-Reply-To: <871ti4hd7q.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5561A51E.30600@gmail.com> <871ti4hd7q.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <556353A9.10501@msapiro.net> On 05/25/2015 08:46 AM, Stephen J. Turnbull wrote: > Regis writes: > > > But what is strange is that actually some of those messages were > > really distributed : I am sure because I got return receipt emails > > for them ! > > You've cross checked the Message-IDs? What do you mean by "return > receipt"? Are you sure they are not "bounce" messages, which indicate > that mailwas *not* delivered? I overlooked this in my earlier reply. If you mean that in your post you have requested to be notified when the recipient reads the message, Mailman makes some effort to remove all such requests from message headers before sending the message, so any DSN you received is more likely a bounce, but you shouldn't be seeing those either as they should be delivered to the Mailman's bounce processing. Regis, I would like to see how you are requesting a return receipt. Please send me a message using the same mail client you used to post to the list and requesting a return receipt. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jon at brazoslink.net Mon May 25 18:56:39 2015 From: jon at brazoslink.net (Jon Gardner) Date: Mon, 25 May 2015 11:56:39 -0500 Subject: [Mailman-Users] SMTP-AUTH and Mailman 2.1.18-1 Message-ID: <52B13EF7-9B64-4E52-B88B-5C2FD4A69173@brazoslink.net> I?ve been using the SMTPAUTHDirect.py handler to enable Mailman 2.1.x to use SMTP-AUTH. It?s been working great, until I upgraded my server from Mavericks (Mac OS X 10.9 + Server 3) to Yosemite (Mac OS X 10.10 + Server 4). For some reason, Server 4 isn?t permitting ?plain? authentication at all. I?m still chasing that down, but in the meantime Mailman can?t send anything at all. Is there a way to make the SMTPAUTHDirect.py handler use cram-md5 authentication instead of plain? TIA, Jon From cpz at tuunq.com Mon May 25 19:00:38 2015 From: cpz at tuunq.com (Carl Zwanzig) Date: Mon, 25 May 2015 10:00:38 -0700 Subject: [Mailman-Users] How to know if all messages were distributed In-Reply-To: <556353A9.10501@msapiro.net> References: <5561A51E.30600@gmail.com> <871ti4hd7q.fsf@uwakimon.sk.tsukuba.ac.jp> <556353A9.10501@msapiro.net> Message-ID: <55635536.4010607@tuunq.com> On 5/25/2015 9:54 AM, Mark Sapiro wrote: > I overlooked this in my earlier reply. If you mean that in your post you > have requested to be notified when the recipient reads the message, > Mailman makes some effort to remove all such requests from message > headers before sending the message, so any DSN you received is more > likely a bounce, but you shouldn't be seeing those either as they should > be delivered to the Mailman's bounce processing. And some people will routinely discard or dismiss those requests, too. Return receipt is not a reliable way to tell if someone has read the message unless all of the recipients are willing and they actually get the request. z! From mark at msapiro.net Mon May 25 19:50:19 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 May 2015 10:50:19 -0700 Subject: [Mailman-Users] SMTP-AUTH and Mailman 2.1.18-1 In-Reply-To: <52B13EF7-9B64-4E52-B88B-5C2FD4A69173@brazoslink.net> References: <52B13EF7-9B64-4E52-B88B-5C2FD4A69173@brazoslink.net> Message-ID: <556360DB.3080905@msapiro.net> On 05/25/2015 09:56 AM, Jon Gardner wrote: > I?ve been using the SMTPAUTHDirect.py handler to enable Mailman 2.1.x to use SMTP-AUTH. It?s been working great, until I upgraded my server from Mavericks (Mac OS X 10.9 + Server 3) to Yosemite (Mac OS X 10.10 + Server 4). For some reason, Server 4 isn?t permitting ?plain? authentication at all. I?m still chasing that down, but in the meantime Mailman can?t send anything at all. > > Is there a way to make the SMTPAUTHDirect.py handler use cram-md5 authentication instead of plain? Where did you get this handler? The only similar thing I am aware of is a patch at . While the proper first line of recourse to a third party patch/handler is to the author, if you tell me where this handler came from so I can get a copy, I'll look at how to fix it. However, if your SMTPAUTHDirect.py is just SMTPDirect.py patched as above, it just uses smtplib.connect.login and it seems that that should try all offered authentication methods that it supports which are in order of preference, CRAM_MD5, PLAIN, LOGIN. Thus it would seem either your handler is not just SMTPDirect.py patched as above or perhaps your server is not offering AUTH methods in response to EHLO. You could try settng the connection's debug level as described in the FAQ at to get more info. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From regis92130 at gmail.com Mon May 25 20:26:19 2015 From: regis92130 at gmail.com (Regis) Date: Mon, 25 May 2015 20:26:19 +0200 Subject: [Mailman-Users] How to know if all messages were distributed In-Reply-To: <871ti4hd7q.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5561A51E.30600@gmail.com> <871ti4hd7q.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <5563694B.4060908@gmail.com> Hello, Thanks for your great answer. > I'll assume that you have perfectly good reasons for using Qmail > rather than Exim or Postfix that are more commonly used with Mailman, Actually... no ! That's why I have now set Postfix as messaging server on my VPS from Plesk ;-) > First question: *which queue*? Mailman has its queues, which you can > examine using ls on the queue directory or mailman/bin/show_qfiles on > the individual queued messages. Qmail also has its own queue(s), and > if the messages are in the Qmail queues, *it's very unlikely to be a > Mailman-related problem*. By design, once a mail server has accepted > a message, the mail server is fully responsible for its deliver, or > for reporting non-delivery. It was the Qmail queue, which is visible in Plesk. > You've cross checked the Message-IDs? What do you mean by "return > receipt"? Are you sure they are not "bounce" messages, which indicate > that mailwas *not* delivered? No. It was automatic responses from the messages recipients. > I don't know about where Centos keeps Mailman's logs and queues, > [...] > For the qfiles, most likely you just care about if they're there in > "outgoing" or "retry". You might also look in the "shunt" queue > directory for "broken" messages that Mailman can't process. I had a look to all these logs but difficult to see which messages where sent or not... it doesn't matter i will send a new mailing in few weeks and i hope it will work better with Postfix ;-) Thanks again. Regis. -------- Message original -------- Sujet : [Mailman-Users] How to know if all messages were distributed De : Stephen J. Turnbull Pour : regis92130 at gmail.com Copie ? : mailman-users at python.org Date : Tue, 26 May 2015 00:46:33 +0900 > Regis writes: > > > Indeed 72 hours after the mailing, i continue to see permanently about > > 500 messages in the queue of my messaging server (i have a linux centOS > > VPS with Qmail). > > Using Qmail is asking for trouble. Dan Bernstein is unquestionably a > genius, but his software tends to assume that the world is a saner > place than it actually is, and doesn't work and play well with others. > I'll assume that you have perfectly good reasons for using Qmail > rather than Exim or Postfix that are more commonly used with Mailman, > but you should be aware that most of the folks on this list are > experienced with Exim, Postfix, and/or Sendmail, and for Qmail-specific > issues, or interactions between Qmail and Mailman, you probably need > to go to a Qmail channel. > > First question: *which queue*? Mailman has its queues, which you can > examine using ls on the queue directory or mailman/bin/show_qfiles on > the individual queued messages. Qmail also has its own queue(s), and > if the messages are in the Qmail queues, *it's very unlikely to be a > Mailman-related problem*. By design, once a mail server has accepted > a message, the mail server is fully responsible for its deliver, or > for reporting non-delivery. > > > But what is strange is that actually some of those messages were > > really distributed : I am sure because I got return receipt emails > > for them ! > > You've cross checked the Message-IDs? What do you mean by "return > receipt"? Are you sure they are not "bounce" messages, which indicate > that mailwas *not* delivered? > > > So i am confused on the total distribution of my mailing to all > > subscribers : is there a possibility so see the number of messages > > processed or not yet processed directly from the server (logs...) ? > > I don't know about where Centos keeps Mailman's logs and queues, but > yes, you can look at the logs and queues once you find them. The > "post" log tells you what posts Mailman has received, but not their > disposition. The "smtp" log tells you what messages have been sent > (by message-id and time, and how long it took to process the smtp > transaction), but due to the nature of the outgoing runner, there are > typically many log messages for each post. Mark may have a script for > summing them up to find out how many have actually been delivered. > > I'm not sure exactly what goes into the smtp-failure log, but I would > suppose that would record cases where qmail tells mailman that it > can't deliver the message for some reason. I'm not sure if it records > tempfails, and for tempfails there's no way for qmail to tell mailman > about retries whether they succeed or fail. > > For the qfiles, most likely you just care about if they're there in > "outgoing" or "retry". You might also look in the "shunt" queue > directory for "broken" messages that Mailman can't process. > > From jon at brazoslink.net Mon May 25 21:04:50 2015 From: jon at brazoslink.net (Jon Gardner) Date: Mon, 25 May 2015 14:04:50 -0500 Subject: [Mailman-Users] set help Message-ID: From kamflyer at shaw.ca Mon May 25 17:14:42 2015 From: kamflyer at shaw.ca (Rob Dover) Date: Mon, 25 May 2015 08:14:42 -0700 Subject: [Mailman-Users] One way umbrella list question Message-ID: Greetings. I have an installation (2.1.20) that we use for club communications. All club members are explicitly subscribed to the main [members] list. There are also a couple of smaller lists that we use for executive and committee discussions. I would like all members of the master [members] list to have posting privileges to the smaller lists but limit the emails that mailman sends for the smaller lists to only the smaller lists. In other words if a member of the exec list posts to the exec list, all members of the executive receive a copy but a regular member would be allowed to post to the executive list but ONLY the executive members would get a copy. As I understand an umbrella list all umbrella members would see all postings. Correct? Can this be done? Thanks -Rob? From mark at msapiro.net Tue May 26 14:41:08 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 May 2015 05:41:08 -0700 Subject: [Mailman-Users] One way umbrella list question In-Reply-To: References: Message-ID: <556469E4.4050500@msapiro.net> On 05/25/2015 08:14 AM, Rob Dover wrote: > Greetings. > I have an installation (2.1.20) that we use for club communications. All > club members are explicitly subscribed to the main [members] list. There are > also a couple of smaller lists that we use for executive and committee > discussions. I would like all members of the master [members] list to have > posting privileges to the smaller lists but limit the emails that mailman > sends for the smaller lists to only the smaller lists. You don't want umbrella lists. All you need to do is put @members (or whatever the name of the all-members list is preceded with '@') in the Privacy options... -> Sender filters -> accept_these_nonmembers setting of all the smaller lists. follow the (Details for accept_these_nonmembers) link on the Privacy options... -> Sender filters page for more info. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Tue May 26 16:59:29 2015 From: ournet.biz at gmail.com (EyeLand) Date: Tue, 26 May 2015 17:59:29 +0300 Subject: [Mailman-Users] Default domain email not work Message-ID: Hello, when send mail to default domain email mailman at list.ournet.biz - http://r.ournet.biz/1Hue3k5 I receive error http://r.ournet.biz/1AvMZDz , can you consult how can resolve this issue? Thank you. From mark at msapiro.net Tue May 26 17:32:00 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 May 2015 08:32:00 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <55622CE9.40605@msapiro.net> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <4AC2B035-96E8-49A8-A9D1-1526AAD3D3F7@rc.org> <55622CE9.40605@msapiro.net> Message-ID: <556491F0.4060903@msapiro.net> On 05/24/2015 12:56 PM, Mark Sapiro wrote: > > The code in Mailman 2.1.18+ actually does a DNS lookup of the DMARC > policy. In all the myriad @python.org list posts, the only domains I see > with p=reject are aol.com, yahoo.com and paypal.com. > > >> If I do this and add the bit about the Reply-To, what would the code look like? I have attached two files. Cookheaders.py.txt is a patched version of the 2.1.14 CookHeaders which will mung the From: address for messages with a From: containing @yahoo.com or @aol.com in the same way that current Mailman's Mung From action does it. This would replace your existing Mailman/Handlers/CookHeaders.py, and you also need to remove your changes to Mailman/Handlers/Cleanse.py. Cookheaders.py.patch.txt is just the diff between the 2.1.14 base CookHeaders.py and the attached Cookheaders.py.txt. If you want to base the munging on an actual DNS lookup of DMARC policy, you would need to: Add the IsDMARCProhibited function at lines 1136-1223 at and the import of dns.resolver at lines 74-79 of the same file to your Mailman/Utils.py, Add # Parameters for DMARC DNS lookups. If you are seeing 'DNSException: # Unable to query DMARC policy ...' entries in your error log, you may need # to adjust these. # The time to wait for a response from a name server before timeout. DMARC_RESOLVER_TIMEOUT = seconds(3) # The total time to spend trying to get an answer to the question. DMARC_RESOLVER_LIFETIME = seconds(5) to Mailman/Defaults.py Ensure the dnspython package package is available in Python. This package can be downloaded from dnspython.org or from the CheeseShop or installed with pip. Then you could replace the lines dre = re.compile('@(yahoo\.com|aol\.com)\W', re.IGNORECASE) if dre.search(msg['from']) and not fasttrack: in the attached CookHeaders.py.txt with (all one line, watch out for wrap): if IsDMARCProhibited(mlist, parseaddr(msg.get('from'))[1]) and not fasttrack: -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- --- - 2015-05-26 07:54:48.674119160 -0700 +++ /home/mark/CookHeaders.py 2015-05-26 07:40:33.950461686 -0700 @@ -107,6 +107,35 @@ # sendmail docs, the most authoritative source of this header's semantics. if not msg.has_key('precedence'): msg['Precedence'] = 'list' + # Do we change the from so the list takes ownership of the email + # This re determines whether we do it or not. + dre = re.compile('@(yahoo\.com|aol\.com)\W', re.IGNORECASE) + if dre.search(msg['from']) and not fasttrack: + # Be as robust as possible here. + faddrs = getaddresses(msg.get_all('from', [])) + # Strip the nulls and bad emails. + faddrs = [x for x in faddrs if x[1].find('@') > 0] + if len(faddrs) == 1: + realname, email = o_from = faddrs[0] + else: + # No From: or multiple addresses. Just punt and take + # the get_sender result. + realname = '' + email = msgdata['original_sender'] + o_from = (realname, email) + if not realname: + if mlist.isMember(email): + realname = mlist.getMemberName(email) or email + else: + realname = email + # Remove domain from realname if it looks like an email address + realname = re.sub(r'@([^ .]+\.)+[^ .]+$', '---', realname) + del msg['from'] + msg['From'] = formataddr(('%s via %s' % (realname, mlist.real_name), + mlist.GetListEmail())) + else: + # Use this as a flag + o_from = None # Reply-To: munging. Do not do this if the message is "fast tracked", # meaning it is internally crafted and delivered to a specific user. BAW: # Yuck, I really hate this feature but I've caved under the sheer pressure @@ -115,6 +144,23 @@ # augment it. RFC 2822 allows max one Reply-To: header so collapse them # if we're adding a value, otherwise don't touch it. (Should we collapse # in all cases?) + # MAS: 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. + if not fasttrack: # A convenience function, requires nested scopes. pair is (name, addr) new = [] @@ -132,10 +178,29 @@ # the original Reply-To:'s to the list we're building up. In both # cases we'll zap the existing field because RFC 2822 says max one is # allowed. + o_rt = False if not mlist.first_strip_reply_to: orig = msg.get_all('reply-to', []) for pair in getaddresses(orig): + # There's an original Reply-To: and we're not removing it. add(pair) + o_rt = True + # We also need to put the old From: in Reply-To: in all cases where + # it is not going in Cc:. This is when reply_goes_to_list == 0 and + # either there was no original Reply-To: or we stripped it. + # However, if there was an original Reply-To:, unstripped, and it + # contained the original From: address we need to flag that it's + # there so we don't add the original From: to Cc: + if o_from and mlist.reply_goes_to_list == 0: + if o_rt: + if d.has_key(o_from[1].lower()): + # Original From: address is in original Reply-To:. + # Pretend we added it. + o_from = None + else: + add(o_from) + # Flag that we added it. + o_from = None # Set Reply-To: header to point back to this list. Add this last # because some folks think that some MUAs make it easier to delete # addresses from the right than from the left. @@ -158,16 +223,35 @@ # above code? # Also skip Cc if this is an anonymous list as list posting address # is already in From and Reply-To in this case. - if mlist.personalize == 2 and mlist.reply_goes_to_list <> 1 \ - and not mlist.anonymous_list: + # We do add the Cc in cases where From: header munging is being done + # because even though the list address is in From:, the Reply-To: + # poster will override it. Brain dead MUAs may then address the list + # twice on a 'reply all', but reasonable MUAs should do the right + # thing. We also add the original From: to Cc: if it wasn't added + # to Reply-To: + add_list = (mlist.personalize == 2 and + mlist.reply_goes_to_list <> 1 and + not mlist.anonymous_list) + if add_list or o_from: # Watch out for existing Cc headers, merge, and remove dups. Note # that RFC 2822 says only zero or one Cc header is allowed. new = [] d = {} - for pair in getaddresses(msg.get_all('cc', [])): - add(pair) - i18ndesc = uheader(mlist, mlist.description, 'Cc') - add((str(i18ndesc), mlist.GetListEmail())) + # If we're adding the original From:, add it first. + if o_from: + add(o_from) + # AvoidDuplicates may have set a new Cc: in msgdata.add_header, + # so check that. + if (msgdata.has_key('add_header') and + msgdata['add_header'].has_key('Cc')): + for pair in getaddresses([msgdata['add_header']['Cc']]): + add(pair) + else: + for pair in getaddresses(msg.get_all('cc', [])): + add(pair) + if add_list: + i18ndesc = uheader(mlist, mlist.description, 'Cc') + add((str(i18ndesc), mlist.GetListEmail())) del msg['Cc'] msg['Cc'] = COMMASPACE.join([formataddr(pair) for pair in new]) # Add list-specific headers as defined in RFC 2369 and RFC 2919, but only -------------- next part -------------- # Copyright (C) 1998-2008 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. """Cook a message's Subject header.""" from __future__ import nested_scopes import re from types import UnicodeType from email.Charset import Charset from email.Header import Header, decode_header, make_header from email.Utils import parseaddr, formataddr, getaddresses from email.Errors import HeaderParseError from Mailman import mm_cfg from Mailman import Utils from Mailman.i18n import _ from Mailman.Logging.Syslog import syslog CONTINUATION = ',\n\t' COMMASPACE = ', ' MAXLINELEN = 78 # True/False try: True, False except NameError: True = 1 False = 0 def _isunicode(s): return isinstance(s, UnicodeType) nonascii = re.compile('[^\s!-~]') def uheader(mlist, s, header_name=None, continuation_ws='\t', maxlinelen=None): # Get the charset to encode the string in. Then search if there is any # non-ascii character is in the string. If there is and the charset is # us-ascii then we use iso-8859-1 instead. If the string is ascii only # we use 'us-ascii' if another charset is specified. charset = Utils.GetCharSet(mlist.preferred_language) if nonascii.search(s): # use list charset but ... if charset == 'us-ascii': charset = 'iso-8859-1' else: # there is no nonascii so ... charset = 'us-ascii' return Header(s, charset, maxlinelen, header_name, continuation_ws) def process(mlist, msg, msgdata): # Set the "X-Ack: no" header if noack flag is set. if msgdata.get('noack'): del msg['x-ack'] msg['X-Ack'] = 'no' # Because we're going to modify various important headers in the email # message, we want to save some of the information in the msgdata # dictionary for later. Specifically, the sender header will get waxed, # but we need it for the Acknowledge module later. msgdata['original_sender'] = msg.get_sender() # VirginRunner sets _fasttrack for internally crafted messages. fasttrack = msgdata.get('_fasttrack') if not msgdata.get('isdigest') and not fasttrack: try: prefix_subject(mlist, msg, msgdata) except (UnicodeError, ValueError): # TK: Sometimes subject header is not MIME encoded for 8bit # simply abort prefixing. pass # Mark message so we know we've been here, but leave any existing # X-BeenThere's intact. msg['X-BeenThere'] = mlist.GetListEmail() # Add Precedence: and other useful headers. None of these are standard # and finding information on some of them are fairly difficult. Some are # just common practice, and we'll add more here as they become necessary. # Good places to look are: # # http://www.dsv.su.se/~jpalme/ietf/jp-ietf-home.html # http://www.faqs.org/rfcs/rfc2076.html # # None of these headers are added if they already exist. BAW: some # consider the advertising of this a security breach. I.e. if there are # known exploits in a particular version of Mailman and we know a site is # using such an old version, they may be vulnerable. It's too easy to # edit the code to add a configuration variable to handle this. if not msg.has_key('x-mailman-version'): msg['X-Mailman-Version'] = mm_cfg.VERSION # We set "Precedence: list" because this is the recommendation from the # sendmail docs, the most authoritative source of this header's semantics. if not msg.has_key('precedence'): msg['Precedence'] = 'list' # Do we change the from so the list takes ownership of the email # This re determines whether we do it or not. dre = re.compile('@(yahoo\.com|aol\.com)\W', re.IGNORECASE) if dre.search(msg['from']) and not fasttrack: # Be as robust as possible here. faddrs = getaddresses(msg.get_all('from', [])) # Strip the nulls and bad emails. faddrs = [x for x in faddrs if x[1].find('@') > 0] if len(faddrs) == 1: realname, email = o_from = faddrs[0] else: # No From: or multiple addresses. Just punt and take # the get_sender result. realname = '' email = msgdata['original_sender'] o_from = (realname, email) if not realname: if mlist.isMember(email): realname = mlist.getMemberName(email) or email else: realname = email # Remove domain from realname if it looks like an email address realname = re.sub(r'@([^ .]+\.)+[^ .]+$', '---', realname) del msg['from'] msg['From'] = formataddr(('%s via %s' % (realname, mlist.real_name), mlist.GetListEmail())) else: # Use this as a flag o_from = None # Reply-To: munging. Do not do this if the message is "fast tracked", # meaning it is internally crafted and delivered to a specific user. BAW: # Yuck, I really hate this feature but I've caved under the sheer pressure # of the (very vocal) folks want it. OTOH, RFC 2822 allows Reply-To: to # be a list of addresses, so instead of replacing the original, simply # augment it. RFC 2822 allows max one Reply-To: header so collapse them # if we're adding a value, otherwise don't touch it. (Should we collapse # in all cases?) # MAS: 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. if not fasttrack: # A convenience function, requires nested scopes. pair is (name, addr) new = [] d = {} def add(pair): lcaddr = pair[1].lower() if d.has_key(lcaddr): return d[lcaddr] = pair new.append(pair) # List admin wants an explicit Reply-To: added if mlist.reply_goes_to_list == 2: add(parseaddr(mlist.reply_to_address)) # If we're not first stripping existing Reply-To: then we need to add # the original Reply-To:'s to the list we're building up. In both # cases we'll zap the existing field because RFC 2822 says max one is # allowed. o_rt = False if not mlist.first_strip_reply_to: orig = msg.get_all('reply-to', []) for pair in getaddresses(orig): # There's an original Reply-To: and we're not removing it. add(pair) o_rt = True # We also need to put the old From: in Reply-To: in all cases where # it is not going in Cc:. This is when reply_goes_to_list == 0 and # either there was no original Reply-To: or we stripped it. # However, if there was an original Reply-To:, unstripped, and it # contained the original From: address we need to flag that it's # there so we don't add the original From: to Cc: if o_from and mlist.reply_goes_to_list == 0: if o_rt: if d.has_key(o_from[1].lower()): # Original From: address is in original Reply-To:. # Pretend we added it. o_from = None else: add(o_from) # Flag that we added it. o_from = None # Set Reply-To: header to point back to this list. Add this last # because some folks think that some MUAs make it easier to delete # addresses from the right than from the left. if mlist.reply_goes_to_list == 1: i18ndesc = uheader(mlist, mlist.description, 'Reply-To') add((str(i18ndesc), mlist.GetListEmail())) del msg['reply-to'] # Don't put Reply-To: back if there's nothing to add! if new: # Preserve order msg['Reply-To'] = COMMASPACE.join( [formataddr(pair) for pair in new]) # The To field normally contains the list posting address. However # when messages are fully personalized, that header will get # overwritten with the address of the recipient. We need to get the # posting address in one of the recipient headers or they won't be # able to reply back to the list. It's possible the posting address # was munged into the Reply-To header, but if not, we'll add it to a # Cc header. BAW: should we force it into a Reply-To header in the # above code? # Also skip Cc if this is an anonymous list as list posting address # is already in From and Reply-To in this case. # We do add the Cc in cases where From: header munging is being done # because even though the list address is in From:, the Reply-To: # poster will override it. Brain dead MUAs may then address the list # twice on a 'reply all', but reasonable MUAs should do the right # thing. We also add the original From: to Cc: if it wasn't added # to Reply-To: add_list = (mlist.personalize == 2 and mlist.reply_goes_to_list <> 1 and not mlist.anonymous_list) if add_list or o_from: # Watch out for existing Cc headers, merge, and remove dups. Note # that RFC 2822 says only zero or one Cc header is allowed. new = [] d = {} # If we're adding the original From:, add it first. if o_from: add(o_from) # AvoidDuplicates may have set a new Cc: in msgdata.add_header, # so check that. if (msgdata.has_key('add_header') and msgdata['add_header'].has_key('Cc')): for pair in getaddresses([msgdata['add_header']['Cc']]): add(pair) else: for pair in getaddresses(msg.get_all('cc', [])): add(pair) if add_list: i18ndesc = uheader(mlist, mlist.description, 'Cc') add((str(i18ndesc), mlist.GetListEmail())) del msg['Cc'] msg['Cc'] = COMMASPACE.join([formataddr(pair) for pair in new]) # Add list-specific headers as defined in RFC 2369 and RFC 2919, but only # if the message is being crafted for a specific list (e.g. not for the # password reminders). # # BAW: Some people really hate the List-* headers. It seems that the free # version of Eudora (possibly on for some platforms) does not hide these # headers by default, pissing off their users. Too bad. Fix the MUAs. if msgdata.get('_nolist') or not mlist.include_rfc2369_headers: return # This will act like an email address for purposes of formataddr() listid = '%s.%s' % (mlist.internal_name(), mlist.host_name) cset = Utils.GetCharSet(mlist.preferred_language) if mlist.description: # Don't wrap the header since here we just want to get it properly RFC # 2047 encoded. i18ndesc = uheader(mlist, mlist.description, 'List-Id', maxlinelen=998) listid_h = formataddr((str(i18ndesc), listid)) else: # without desc we need to ensure the MUST brackets listid_h = '<%s>' % listid # We always add a List-ID: header. del msg['list-id'] msg['List-Id'] = listid_h # For internally crafted messages, we also add a (nonstandard), # "X-List-Administrivia: yes" header. For all others (i.e. those coming # from list posts), we add a bunch of other RFC 2369 headers. requestaddr = mlist.GetRequestEmail() subfieldfmt = '<%s>, ' listinfo = mlist.GetScriptURL('listinfo', absolute=1) useropts = mlist.GetScriptURL('options', absolute=1) headers = {} if msgdata.get('reduced_list_headers'): headers['X-List-Administrivia'] = 'yes' else: headers.update({ 'List-Help' : '' % requestaddr, 'List-Unsubscribe': subfieldfmt % (useropts, requestaddr, 'un'), 'List-Subscribe' : subfieldfmt % (listinfo, requestaddr, ''), }) # List-Post: is controlled by a separate attribute if mlist.include_list_post_header: headers['List-Post'] = '' % mlist.GetListEmail() # Add this header if we're archiving if mlist.archive: archiveurl = mlist.GetBaseArchiveURL() if archiveurl.endswith('/'): archiveurl = archiveurl[:-1] headers['List-Archive'] = '<%s>' % archiveurl # First we delete any pre-existing headers because the RFC permits only # one copy of each, and we want to be sure it's ours. for h, v in headers.items(): del msg[h] # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded, but is at least text-MUA friendly. The # adding of 2 is for the colon-space separator. if len(h) + 2 + len(v) > 78: v = CONTINUATION.join(v.split(', ')) msg[h] = v def prefix_subject(mlist, msg, msgdata): # Add the subject prefix unless the message is a digest or is being fast # tracked (e.g. internally crafted, delivered to a single user such as the # list admin). prefix = mlist.subject_prefix.strip() if not prefix: return subject = msg.get('subject', '') # Try to figure out what the continuation_ws is for the header if isinstance(subject, Header): lines = str(subject).splitlines() else: lines = subject.splitlines() ws = '\t' if len(lines) > 1 and lines[1] and lines[1][0] in ' \t': ws = lines[1][0] msgdata['origsubj'] = subject # The subject may be multilingual but we take the first charset as major # one and try to decode. If it is decodable, returned subject is in one # line and cset is properly set. If fail, subject is mime-encoded and # cset is set as us-ascii. See detail for ch_oneline() (CookHeaders one # line function). subject, cset = ch_oneline(subject) # TK: Python interpreter has evolved to be strict on ascii charset code # range. It is safe to use unicode string when manupilating header # contents with re module. It would be best to return unicode in # ch_oneline() but here is temporary solution. subject = unicode(subject, cset) # If the subject_prefix contains '%d', it is replaced with the # mailing list sequential number. Sequential number format allows # '%d' or '%05d' like pattern. prefix_pattern = re.escape(prefix) # unescape '%' :-< prefix_pattern = '%'.join(prefix_pattern.split(r'\%')) p = re.compile('%\d*d') if p.search(prefix, 1): # prefix have number, so we should search prefix w/number in subject. # Also, force new style. prefix_pattern = p.sub(r'\s*\d+\s*', prefix_pattern) old_style = False else: old_style = mm_cfg.OLD_STYLE_PREFIXING subject = re.sub(prefix_pattern, '', subject) rematch = re.match('((RE|AW|SV|VS)(\[\d+\])?:\s*)+', subject, re.I) if rematch: subject = subject[rematch.end():] recolon = 'Re:' else: recolon = '' # At this point, subject may become null if someone post mail with # subject: [subject prefix] if subject.strip() == '': subject = _('(no subject)') cset = Utils.GetCharSet(mlist.preferred_language) subject = unicode(subject, cset) # and substitute %d in prefix with post_id try: prefix = prefix % mlist.post_id except TypeError: pass # If charset is 'us-ascii', try to concatnate as string because there # is some weirdness in Header module (TK) if cset == 'us-ascii': try: if old_style: h = u' '.join([recolon, prefix, subject]) else: if recolon: h = u' '.join([prefix, recolon, subject]) else: h = u' '.join([prefix, subject]) h = h.encode('us-ascii') h = uheader(mlist, h, 'Subject', continuation_ws=ws) del msg['subject'] msg['Subject'] = h ss = u' '.join([recolon, subject]) ss = ss.encode('us-ascii') ss = uheader(mlist, ss, 'Subject', continuation_ws=ws) msgdata['stripped_subject'] = ss return except UnicodeError: pass # Get the header as a Header instance, with proper unicode conversion if old_style: h = uheader(mlist, recolon, 'Subject', continuation_ws=ws) h.append(prefix) else: h = uheader(mlist, prefix, 'Subject', continuation_ws=ws) h.append(recolon) # TK: Subject is concatenated and unicode string. subject = subject.encode(cset, 'replace') h.append(subject, cset) del msg['subject'] msg['Subject'] = h ss = uheader(mlist, recolon, 'Subject', continuation_ws=ws) ss.append(subject, cset) msgdata['stripped_subject'] = ss def ch_oneline(headerstr): # Decode header string in one line and convert into single charset # copied and modified from ToDigest.py and Utils.py # return (string, cset) tuple as check for failure try: d = decode_header(headerstr) # at this point, we should rstrip() every string because some # MUA deliberately add trailing spaces when composing return # message. d = [(s.rstrip(), c) for (s,c) in d] cset = 'us-ascii' for x in d: # search for no-None charset if x[1]: cset = x[1] break h = make_header(d) ustr = h.__unicode__() oneline = u''.join(ustr.splitlines()) return oneline.encode(cset, 'replace'), cset except (LookupError, UnicodeError, ValueError, HeaderParseError): # possibly charset problem. return with undecoded string in one line. return ''.join(headerstr.splitlines()), 'us-ascii' From mark at msapiro.net Tue May 26 17:41:37 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 May 2015 08:41:37 -0700 Subject: [Mailman-Users] Default domain email not work In-Reply-To: References: Message-ID: <55649431.4000501@msapiro.net> On 05/26/2015 07:59 AM, EyeLand wrote: > Hello, when send mail to default domain email mailman at list.ournet.biz - > http://r.ournet.biz/1Hue3k5 I receive error http://r.ournet.biz/1AvMZDz , > can you consult how can resolve this issue? Thank you. This is a Postfix configuration issue on the list.ournet.biz server. We will try to help you resolve this, but may help. In order for us to help wee need to see at least the output from postconf -n on the server, and the contents of Mailman/mm_cfg.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Tue May 26 18:03:48 2015 From: ournet.biz at gmail.com (EyeLand) Date: Tue, 26 May 2015 19:03:48 +0300 Subject: [Mailman-Users] Default domain email not work In-Reply-To: <55649431.4000501@msapiro.net> References: <55649431.4000501@msapiro.net> Message-ID: 2015-05-26 18:41 GMT+03:00 Mark Sapiro : > On 05/26/2015 07:59 AM, EyeLand wrote: > > Hello, when send mail to default domain email mailman at list.ournet.biz - > > http://r.ournet.biz/1Hue3k5 I receive error http://r.ournet.biz/1AvMZDz > , > > can you consult how can resolve this issue? Thank you. > > > This is a Postfix configuration issue on the list.ournet.biz server. We > will try to help you resolve this, but > may help. > > In order for us to help wee need to see at least the output from > > postconf -n > > on the server, and the contents of Mailman/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/ournet.biz%40gmail.com > postconf -n https://gist.githubusercontent.com/eyeland/c28256b0602679d4954d/raw/92e672f70b4a6adb0d6cfe555d04804edda1b090/gistfile1.txt Mailman/mm_cfg.py https://gist.githubusercontent.com/eyeland/b3a2ede982b5db3ab3dc/raw/a18096825a97c6d752f81c6cea68ad221e1c16c9/gistfile1.txt From mark at msapiro.net Tue May 26 18:15:32 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 May 2015 09:15:32 -0700 Subject: [Mailman-Users] Default domain email not work In-Reply-To: References: <55649431.4000501@msapiro.net> Message-ID: <55649C24.2010505@msapiro.net> On 05/26/2015 09:03 AM, EyeLand wrote: > > postconf -n > https://gist.githubusercontent.com/eyeland/c28256b0602679d4954d/raw/92e672f70b4a6adb0d6cfe555d04804edda1b090/gistfile1.txt > Mailman/mm_cfg.py > https://gist.githubusercontent.com/eyeland/b3a2ede982b5db3ab3dc/raw/a18096825a97c6d752f81c6cea68ad221e1c16c9/gistfile1.txt It looks like you are trying to follow the FAQ at . Is there some reason you are doing this instead of just following the Debian docs? What is the content of /var/lib/mailman/data/transport-mailman? What are the Postfix log messages associated with the failed delivery? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Tue May 26 19:00:45 2015 From: ournet.biz at gmail.com (EyeLand) Date: Tue, 26 May 2015 20:00:45 +0300 Subject: [Mailman-Users] Default domain email not work In-Reply-To: <55649C24.2010505@msapiro.net> References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> Message-ID: 2015-05-26 19:15 GMT+03:00 Mark Sapiro : > On 05/26/2015 09:03 AM, EyeLand wrote: > > > > postconf -n > > > https://gist.githubusercontent.com/eyeland/c28256b0602679d4954d/raw/92e672f70b4a6adb0d6cfe555d04804edda1b090/gistfile1.txt > > Mailman/mm_cfg.py > > > https://gist.githubusercontent.com/eyeland/b3a2ede982b5db3ab3dc/raw/a18096825a97c6d752f81c6cea68ad221e1c16c9/gistfile1.txt > > > It looks like you are trying to follow the FAQ at > . Is there some reason you are doing > this instead of just following the Debian docs? > > What is the content of /var/lib/mailman/data/transport-mailman? > > What are the Postfix log messages associated with the failed delivery? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > /var/lib/mailman/data/transport-mailman https://gist.githubusercontent.com/eyeland/8836edc1edef4fb11ece/raw/c950ed0eec1830199da848e991e7b20d4b26a0b8/gistfile1.txt Postfix log messages associated with the failed delivery is on file /var/log/mail.warn ? From mark at msapiro.net Tue May 26 20:12:04 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 May 2015 11:12:04 -0700 Subject: [Mailman-Users] Default domain email not work In-Reply-To: References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> Message-ID: <5564B774.2010101@msapiro.net> On 05/26/2015 10:00 AM, EyeLand wrote: > > /var/lib/mailman/data/transport-mailman > https://gist.githubusercontent.com/eyeland/8836edc1edef4fb11ece/raw/c950ed0eec1830199da848e991e7b20d4b26a0b8/gistfile1.txt I see two issues here: First, entries like mailman at list.mobilier.md local should all be mailman at list.mobilier.md local: I.e., yours are all missing the : after local. See item 3) at and compare that to your /etc/mailman/virtual_to_transport.sh. More importantly, the undeliverable mail is addressed to mailman at list.ournet.biz, but the domain of the mailman list is list.mobilier.md. The methods you are using only create the transport maps for the list's 'host_name' domain so Postfix can't deliver to the list @ a different domain. > Postfix log messages associated with the failed delivery is on file > /var/log/mail.warn ? /var/log/mail.log -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Tue May 26 22:49:14 2015 From: ournet.biz at gmail.com (EyeLand) Date: Tue, 26 May 2015 23:49:14 +0300 Subject: [Mailman-Users] Default domain email not work In-Reply-To: <5564B774.2010101@msapiro.net> References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> <5564B774.2010101@msapiro.net> Message-ID: 2015-05-26 21:12 GMT+03:00 Mark Sapiro : > On 05/26/2015 10:00 AM, EyeLand wrote: > > > > /var/lib/mailman/data/transport-mailman > > > https://gist.githubusercontent.com/eyeland/8836edc1edef4fb11ece/raw/c950ed0eec1830199da848e991e7b20d4b26a0b8/gistfile1.txt > > I see two issues here: > > First, entries like > > mailman at list.mobilier.md local > > should all be > > mailman at list.mobilier.md local: > > I.e., yours are all missing the : after local. See item 3) at > and compare that to your > /etc/mailman/virtual_to_transport.sh. > > More importantly, the undeliverable mail is addressed to > mailman at list.ournet.biz, but the domain of the mailman list is > list.mobilier.md. > > The methods you are using only create the transport maps for the list's > 'host_name' domain so Postfix can't deliver to the list @ a different > domain. > > > Postfix log messages associated with the failed delivery is on file > > /var/log/mail.warn ? > > /var/log/mail.log > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > /var/log/mail.log https://gist.githubusercontent.com/eyeland/84ca2edc3f07ca507a8d/raw/aae9c95eb3dd0830726a4cf1632ef6c38dc4a507/gistfile1.txt the main server domain is vps1.ournet.biz, secondary domains are test2.ournet.biz, list.ournet.biz, list.mobilier.md From mark at msapiro.net Wed May 27 00:23:00 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 May 2015 15:23:00 -0700 Subject: [Mailman-Users] Default domain email not work In-Reply-To: References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> <5564B774.2010101@msapiro.net> Message-ID: <5564F244.7080309@msapiro.net> On 05/26/2015 01:49 PM, EyeLand wrote: > > /var/log/mail.log > https://gist.githubusercontent.com/eyeland/84ca2edc3f07ca507a8d/raw/aae9c95eb3dd0830726a4cf1632ef6c38dc4a507/gistfile1.txt I see things like the following in the log. May 26 14:44:30 vps1 postfix/local[12807]: 4B7BD80F0C: to=, relay=local, delay=0.37, delays=0.26/0.03/0/0.08, dsn=2.0.0, status=sent (delivered to command: /var/lib/mailman/mail/mailman post mailman) This is a message To: mailman at vps1.ournet.biz which is delivered directly to mailman via the 'mailman' alias because vps1.ournet.biz is a local domain in Postfix, i.e., its in mydestination in Postfix. May 26 14:44:50 vps1 postfix/smtpd[12792]: NOQUEUE: reject: RCPT from forward15o.cmail.yandex.net[37.9.109.212]: 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table; from= to= proto=ESMTP helo= This is a message to mailman at list.ournet.biz which is rejected because list.ournet.biz is not a Postfix local domain and the address mailman at list.ournet.biz is not mapped to the local transport in transport maps nor is it mapped to the local mailman address via virtual alias maps May 26 14:45:25 vps1 postfix/local[12807]: 6460280F0C: to=, orig_to=, relay=local, delay=0.13, delays=0.05/0/0/0.07, dsn=2.0.0, status=sent (delivered to command: /var/lib/mailman/mail/mailman post mailman) And this is a message to mailman at list.mobilier.md which is mapped to the local transport via transport maps and is thus accepted. > the main server domain is vps1.ournet.biz, > secondary domains are test2.ournet.biz, > list.ournet.biz, list.mobilier.md You are using transport maps to map list addresses in non-local domains such as list.ournet.biz and list.mobilier.md to Postfix's local transport. The method you are using only generates mappings for the list's host_name domain which in the case of the mailman list is list.mobilier.md. Thus mail to mailman at list.mobilier.md is properly delivered to Mailman, but mail to mailman at list.ournet.biz is not deliverable because the address is not in transport maps or virtual alias maps and list.ournet.biz is not a local domain. So the question is why are you trying to mail to mailman at list.ournet.biz in the first place. If you really want to be able to mail to mailman@ any of the domains, you could manually replicate the 'mailman' stanza in both data/virtual-mailman and data/transport-mailman changing the list.mobilier.md domain to list.ournet.biz in the replicated stanzas. That should work until you rebuild those files completely with bin/genaliases. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ericardosantos at gmail.com Wed May 27 05:56:29 2015 From: ericardosantos at gmail.com (Ricardo Santos) Date: Tue, 26 May 2015 23:56:29 -0400 Subject: [Mailman-Users] help with error on start In-Reply-To: <555ABC54.5020302@msapiro.net> References: <5558B9CF.9010800@msapiro.net> <555ABC54.5020302@msapiro.net> Message-ID: Download from "http://ftp.gnu.org/gnu/mailman/mailman-2.1.20.tgz" but have error again: # /var/lib/mailman/bin/newlist Traceback (most recent call last): File "/var/lib/mailman/bin/newlist", line 108, in from Mailman import MailList File "/var/lib/mailman/Mailman/MailList.py", line 45, in from Mailman import Utils File "/var/lib/mailman/Mailman/Utils.py", line 75, in import dns.resolver File "/usr/lib/python2.6/site-packages/dns/resolver.py", line 35, in import dns.message File "/usr/lib/python2.6/site-packages/dns/message.py", line 191 print('id %d' % self.id, file=s) ^ SyntaxError: invalid syntax 2015-05-19 0:30 GMT-04:00 Mark Sapiro : > On 05/18/2015 05:32 AM, Ricardo Santos wrote: > > Thanks Mark for you answer. I installed from a tutorial with this command > > (Centos 6.6) > > > >> yum --enablerepo=remi install mailman (Ver 3:2.1.12-18.el6 ) > > > OK, but the /usr/lib/mailman/Mailman/i18n.py file in your installed > Mailman doesn't look like the one distributed by GNU Mailman nor does it > look like the one from RHEL 5 that I happen to have. > > So either something went wrong with your package install, or you will > have to pursue this with Red Hat/Centos. > > Or, you could try downliading i18n.py from > < > http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/i18n.py > > > and replacing yours with that. That will probably get you past the > current issue, but there may be other things wrong. > > -- > 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/ericardosantos%40gmail.com > From ournet.biz at gmail.com Wed May 27 09:35:49 2015 From: ournet.biz at gmail.com (EyeLand) Date: Wed, 27 May 2015 10:35:49 +0300 Subject: [Mailman-Users] Default domain email not work In-Reply-To: <5564F244.7080309@msapiro.net> References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> <5564B774.2010101@msapiro.net> <5564F244.7080309@msapiro.net> Message-ID: 2015-05-27 1:23 GMT+03:00 Mark Sapiro : > On 05/26/2015 01:49 PM, EyeLand wrote: > > > > /var/log/mail.log > > > https://gist.githubusercontent.com/eyeland/84ca2edc3f07ca507a8d/raw/aae9c95eb3dd0830726a4cf1632ef6c38dc4a507/gistfile1.txt > > > I see things like the following in the log. > > May 26 14:44:30 vps1 postfix/local[12807]: 4B7BD80F0C: > to=, relay=local, delay=0.37, > delays=0.26/0.03/0/0.08, dsn=2.0.0, status=sent (delivered to command: > /var/lib/mailman/mail/mailman post mailman) > > > This is a message To: mailman at vps1.ournet.biz which is delivered > directly to mailman via the 'mailman' alias because vps1.ournet.biz is a > local domain in Postfix, i.e., its in mydestination in Postfix. > > > > May 26 14:44:50 vps1 postfix/smtpd[12792]: NOQUEUE: reject: RCPT from > forward15o.cmail.yandex.net[37.9.109.212]: 550 5.1.1 > : Recipient address rejected: User unknown in > virtual mailbox table; from= > to= proto=ESMTP helo= > > > > This is a message to mailman at list.ournet.biz which is rejected because > list.ournet.biz is not a Postfix local domain and the address > mailman at list.ournet.biz is not mapped to the local transport in > transport maps nor is it mapped to the local mailman address via virtual > alias maps > > > May 26 14:45:25 vps1 postfix/local[12807]: 6460280F0C: > to=, orig_to=, > relay=local, delay=0.13, delays=0.05/0/0/0.07, dsn=2.0.0, status=sent > (delivered to command: /var/lib/mailman/mail/mailman post mailman) > > > And this is a message to mailman at list.mobilier.md which is mapped to the > local transport via transport maps and is thus accepted. > > > > the main server domain is vps1.ournet.biz, > > secondary domains are test2.ournet.biz, > > list.ournet.biz, list.mobilier.md > > > You are using transport maps to map list addresses in non-local domains > such as list.ournet.biz and list.mobilier.md to Postfix's local > transport. The method you are using only generates mappings for the > list's host_name domain which in the case of the mailman list is > list.mobilier.md. Thus mail to mailman at list.mobilier.md is properly > delivered to Mailman, but mail to mailman at list.ournet.biz is not > deliverable because the address is not in transport maps or virtual > alias maps and list.ournet.biz is not a local domain. > > So the question is why are you trying to mail to mailman at list.ournet.biz > in the first place. If you really want to be able to mail to mailman@ > any of the domains, you could manually replicate the 'mailman' stanza in > both data/virtual-mailman and data/transport-mailman changing the > list.mobilier.md domain to list.ournet.biz in the replicated stanzas. > That should work until you rebuild those files completely with > bin/genaliases. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > 1) I want to receive mails to mailman at list.ournet.biz because subscribers view that email on info page http://r.ournet.biz/1Hue3k5 2) today Mailman change file /var/lib/mailman/data/transport-mailman https://gist.githubusercontent.com/eyeland/5f2017044013cd94ffe2/raw/907d4860807af00076acc4e6d3e96fd3ff587e1a/gistfile1.txt and I not see now on file mailman at list.mobilier.md anyway that mail work fine 3) I test again mailman at list.mobilier.md, mailman at vps1.ournet.biz, mailman at list.ournet.biz and mails to mailman at list.mobilier.md and mailman at vps1.ournet.biz was redirect to mailman at vps1.ournet.biz control panel Mailman http://vps1.ournet.biz/cgi-bin/mailman/admin/mailman, but mail sent to mailman at list.ournet.biz generate error https://gist.githubusercontent.com/eyeland/172404219786ce7902fc/raw/5f52e7fb432d332265086e6581a7ed3ec530d1b5/gistfile1.txt 4) I create mailman lists on control panel ISPconfig, maybe the problem is on another place? From mark at msapiro.net Wed May 27 14:20:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 05:20:16 -0700 Subject: [Mailman-Users] help with error on start In-Reply-To: References: <5558B9CF.9010800@msapiro.net> <555ABC54.5020302@msapiro.net> Message-ID: <5565B680.1050106@msapiro.net> On 05/26/2015 08:56 PM, Ricardo Santos wrote: > Download from "http://ftp.gnu.org/gnu/mailman/mailman-2.1.20.tgz" but have > error again: > > # /var/lib/mailman/bin/newlist > > Traceback (most recent call last): > >... > File "/usr/lib/python2.6/site-packages/dns/message.py", line 191 > > print('id %d' % self.id, file=s) > > ^ > > SyntaxError: invalid syntax It appears you have installed a Python 3 versipn of dnspython in Python 2.6 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Mike.Lake at uts.edu.au Wed May 27 03:33:04 2015 From: Mike.Lake at uts.edu.au (Michael Lake) Date: Wed, 27 May 2015 11:33:04 +1000 Subject: [Mailman-Users] Some pages are only partially translated - most still show part of page in English Message-ID: <55651ED0.1030609@uts.edu.au> Hi all I have setup Mailman via a Debian package. It's Mailman version 2.1.15 from Debian 1:2.1.15-1+deb7u1 On the listinfo page if I select from the languages only part of the page is translated. An example below is for Spanish. I thought it might be due to customization of the files in mailman/lists/XXX-announce/en/ but I have removed those and restarted mailman (to clear any caching) and still the pages are only partially translated. I have installed a second mailman on another machine and a clean install with no customization of templates still shows "standard mailman text" as English. /var/lib/mailman/messages/ shows all the .mo and .po files are present. Of course my List Name & Description will only be in English but the standard text should all be translated. The options login page is fully translated. But once logged in the mailing list membership configuration page is also only partially translated. Example for Spanish below. The first line under "Subscribing to XX" is in English, then just one paragraph translated. The "XXX-announce Subscribers" section is translated. Subscribing to XXX-announce --------------------------- Subscribe to XXX-announce by filling out the following form. Se le mandar? un mensaje de correo electr?nico pidiendole una confirmaci?n, para prevenir que otras personas le suscriban sin que usted lo sepa. Esta lista es oculta, lo que singinifica que los suscriptores de la lista solo est?n disponibles para el administrador de la lista. Your email address: Your name (optional): You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. Do not use a valuable password as it will occasionally be emailed back to you in cleartext. If you choose not to enter a password, one will be automatically generated for you, and it will be sent to you once you've confirmed your subscription. You can always request a mail-back of your password when you edit your personal options. Pick a password: Reenter password to confirm: Which language do you prefer to display your messages? XXX-announce Subscribers ------------------------ Para anular su suscripci?n de XXX-announce, consiga un recordatorio de su clave o cambie sus opciones de suscripci?n indique su direcci?n de correo electr?nico con el que est? suscrito: Mike Lake UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. From mark at msapiro.net Wed May 27 14:48:03 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 05:48:03 -0700 Subject: [Mailman-Users] Some pages are only partially translated - most still show part of page in English In-Reply-To: <55651ED0.1030609@uts.edu.au> References: <55651ED0.1030609@uts.edu.au> Message-ID: <5565BD03.4060807@msapiro.net> On 05/26/2015 06:33 PM, Michael Lake wrote: > Hi all > > I have setup Mailman via a Debian package. It's Mailman version 2.1.15 > from Debian 1:2.1.15-1+deb7u1 > > On the listinfo page if I select from the languages only part of the > page is translated. An example below is for Spanish. Al of Mailman's translations are contributed by volunteers. Some are incomplete because they were never fully translated. Others are incomplete because strings were added or changed since the last update of the translation. There were a few updates to the Spanish translation in 2.1.16, but these only addressed errors in existing translated strings and didn't add new ones . If you wish to help improve the Spanish or other translations, we welcome your help. Start at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed May 27 15:44:15 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 06:44:15 -0700 Subject: [Mailman-Users] Default domain email not work In-Reply-To: References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> <5564B774.2010101@msapiro.net> <5564F244.7080309@msapiro.net> Message-ID: <5565CA2F.2090508@msapiro.net> On 05/27/2015 12:35 AM, EyeLand wrote: > > 1) I want to receive mails to mailman at list.ournet.biz > because subscribers view that email on > info page http://r.ournet.biz/1Hue3k5 Yes, I understand. This is a situation that is not straightforward to deal with in installations with lists in multiple virtual domains. The mailman at domain address is displayed on admin and listinfo overviews with a domain based on the 'host' of the URL of the page which means ideally, the 'mailman' address should work in all supported domains, but Mailman's integration with Postfix doesn't do that. Thinking about it, I have decided this is a bug. See . > 2) today Mailman change file /var/lib/mailman/data/transport-mailman > https://gist.githubusercontent.com/eyeland/5f2017044013cd94ffe2/raw/907d4860807af00076acc4e6d3e96fd3ff587e1a/gistfile1.txt > and I not see now on file mailman at list.mobilier.md > anyway that mail work fine It looks like you ran bin/genaliases and before doing so, you changed the host_name attribute of the 'mailman' list so it is no longer either list.ournet.biz or list.mobilier.md. > 3) I test again mailman at list.mobilier.md, mailman at vps1.ournet.biz, > mailman at list.ournet.biz > and mails to mailman at list.mobilier.md > and mailman at vps1.ournet.biz > was redirect to mailman at vps1.ournet.biz > control panel Mailman > http://vps1.ournet.biz/cgi-bin/mailman/admin/mailman, but mail sent to > mailman at list.ournet.biz generate error > https://gist.githubusercontent.com/eyeland/172404219786ce7902fc/raw/5f52e7fb432d332265086e6581a7ed3ec530d1b5/gistfile1.txt The real question here is how is mail to mailman at list.mobilier.md being delivered. I suspect that address is in a virtual mapping somewhere. Your postconf -n shows virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman, proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf Since you apparently ran genaliases and mailman at list.mobilier.md is not in your transport maps, it also isn't in /var/lib/mailman/data/virtual-mailman, but it may still be in /var/lib/mailman/data/virtual-mailman.db because your postfix map command doesn't update it. This then again raises the question of why you are doing all the transport maps stuff at all when the straightforward virtual_alias_maps will apparently work > 4) I create mailman lists on control panel ISPconfig, maybe the problem > is on another place? If you are dealing with control panels, you should take those issues to the people who provide them. I will fix the bug at <> and provide a patch here when I do. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From kamflyer at shaw.ca Wed May 27 15:52:24 2015 From: kamflyer at shaw.ca (Rob Dover) Date: Wed, 27 May 2015 06:52:24 -0700 Subject: [Mailman-Users] One way umbrella list question In-Reply-To: <556469E4.4050500@msapiro.net> References: Message-ID: On 2015-05-26, 5:41 AM, "Mark Sapiro" wrote: >On 05/25/2015 08:14 AM, Rob Dover wrote: >> Greetings. >> I have an installation (2.1.20) that we use for club communications. All >> club members are explicitly subscribed to the main [members] list. >>There are >> also a couple of smaller lists that we use for executive and committee >> discussions. I would like all members of the master [members] list to >>have >> posting privileges to the smaller lists but limit the emails that >>mailman >> sends for the smaller lists to only the smaller lists. > > >You don't want umbrella lists. All you need to do is put @members (or >whatever the name of the all-members list is preceded with '@') in the >Privacy options... -> Sender filters -> accept_these_nonmembers setting >of all the smaller lists. follow the (Details for >accept_these_nonmembers) link on the Privacy options... -> Sender >filters page for more info. > >-- >Mark Sapiro The highway is for gamblers, >San Francisco Bay Area, California better use your sense - B. Dylan > I have @members in the Sender filters -> accept_these_nonmembers but am still getting "Post by non-member to a members-only list? despite the poster address being in the master list. Is there another setting somewhere else? This is a private list, would that make any difference? Thanks From mark at msapiro.net Wed May 27 16:11:08 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 07:11:08 -0700 Subject: [Mailman-Users] One way umbrella list question In-Reply-To: References: Message-ID: <5565D07C.30902@msapiro.net> On 05/27/2015 06:52 AM, Rob Dover wrote: > > I have @members in the Sender filters -> accept_these_nonmembers but am > still getting "Post by non-member to a members-only list? despite the > poster address being in the master list. Is there another setting > somewhere else? This is a private list, would that make any difference? > Thanks The only requirement is to put @name_of_master_list (the actual name of the list, not literally 'name_of_master_list' or 'members' unless that is the list's name) on one line with no leading or embedded spaces in accept_these_nonmembers of each of the smaller lists. If that's what you are doing, and you have access, what's in Mailman's 'error' log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ournet.biz at gmail.com Wed May 27 17:09:08 2015 From: ournet.biz at gmail.com (EyeLand) Date: Wed, 27 May 2015 18:09:08 +0300 Subject: [Mailman-Users] Default domain email not work In-Reply-To: <5565CA2F.2090508@msapiro.net> References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> <5564B774.2010101@msapiro.net> <5564F244.7080309@msapiro.net> <5565CA2F.2090508@msapiro.net> Message-ID: 2015-05-27 16:44 GMT+03:00 Mark Sapiro : > On 05/27/2015 12:35 AM, EyeLand wrote: > > > > 1) I want to receive mails to mailman at list.ournet.biz > > because subscribers view that email on > > info page http://r.ournet.biz/1Hue3k5 > > > Yes, I understand. This is a situation that is not straightforward to > deal with in installations with lists in multiple virtual domains. The > mailman at domain address is displayed on admin and listinfo overviews with > a domain based on the 'host' of the URL of the page which means ideally, > the 'mailman' address should work in all supported domains, but > Mailman's integration with Postfix doesn't do that. > > Thinking about it, I have decided this is a bug. See > . > > > > 2) today Mailman change file /var/lib/mailman/data/transport-mailman > > > https://gist.githubusercontent.com/eyeland/5f2017044013cd94ffe2/raw/907d4860807af00076acc4e6d3e96fd3ff587e1a/gistfile1.txt > > and I not see now on file mailman at list.mobilier.md > > anyway that mail work fine > > It looks like you ran bin/genaliases and before doing so, you changed > the host_name attribute of the 'mailman' list so it is no longer either > list.ournet.biz or list.mobilier.md. > > > > 3) I test again mailman at list.mobilier.md, mailman at vps1.ournet.biz, > > mailman at list.ournet.biz > > and mails to mailman at list.mobilier.md > > and mailman at vps1.ournet.biz > > was redirect to mailman at vps1.ournet.biz > > control panel Mailman > > http://vps1.ournet.biz/cgi-bin/mailman/admin/mailman, but mail sent to > > mailman at list.ournet.biz generate error > > > https://gist.githubusercontent.com/eyeland/172404219786ce7902fc/raw/5f52e7fb432d332265086e6581a7ed3ec530d1b5/gistfile1.txt > > > The real question here is how is mail to mailman at list.mobilier.md being > delivered. I suspect that address is in a virtual mapping somewhere. > Your postconf -n shows > > virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman, > proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, > proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf > > Since you apparently ran genaliases and mailman at list.mobilier.md is not > in your transport maps, it also isn't in > /var/lib/mailman/data/virtual-mailman, but it may still be in > /var/lib/mailman/data/virtual-mailman.db because your postfix map > command doesn't update it. > > This then again raises the question of why you are doing all the > transport maps stuff at all when the straightforward virtual_alias_maps > will apparently work > > > > 4) I create mailman lists on control panel ISPconfig, maybe the problem > > is on another place? > > > If you are dealing with control panels, you should take those issues to > the people who provide them. > > I will fix the bug at > <> and provide a patch > here when I do. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > Maybe these files help for solve the bug /var/lib/mailman/data/virtual-mailman https://gist.githubusercontent.com/eyeland/c4095804712e4af3f892/raw/88c951b3a0bdda63253e45bc1fd0af6cc7c59615/gistfile1.txt /etc/postfix/mysql-virtual_forwardings.cf https://gist.githubusercontent.com/eyeland/3e8f1ff2c848a6d78783/raw/ee9cd2539cc9641ac2bc66b0b578188129e38c65/gistfile1.txt /etc/postfix/mysql-virtual_email2email.cf https://gist.githubusercontent.com/eyeland/b483b0c0246fe8c2e3bd/raw/ed3ead3b056588ee8415ed03103741d90fa5e01a/gistfile1.txt that is right on file /var/lib/mailman/data/virtual-mailman.db I found mailman at list.mobilier.md From mark at msapiro.net Wed May 27 17:38:29 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 08:38:29 -0700 Subject: [Mailman-Users] Default domain email not work In-Reply-To: References: <55649431.4000501@msapiro.net> <55649C24.2010505@msapiro.net> <5564B774.2010101@msapiro.net> <5564F244.7080309@msapiro.net> <5565CA2F.2090508@msapiro.net> Message-ID: <5565E4F5.5020601@msapiro.net> On 05/27/2015 08:09 AM, EyeLand wrote: > > Maybe these files help for solve the bug > > /var/lib/mailman/data/virtual-mailman > https://gist.githubusercontent.com/eyeland/c4095804712e4af3f892/raw/88c951b3a0bdda63253e45bc1fd0af6cc7c59615/gistfile1.txt The bug is fixed. The attached patch to Mailman/MTA/Postfix.py will fix it. If you apply that patch and rerun bin/genaliases, it will add entries for the mailman at list.ournet.biz and mailman at list.mobilier.md addresses to data/virtual-mailman. > that is right on file /var/lib/mailman/data/virtual-mailman.db I found > mailman at list.mobilier.md So again, standard Mailman-Postfix integration without transport maps does appear to work in your case. That means you can remove POSTFIX_MAP_CMD = '/etc/mailman/virtual_to_transport.sh' from mm_cfg.py and change transport_maps = hash:/var/lib/mailman/data/transport-mailman, proxy:mysql:/etc/postfix/mysql-virtual_transports.cf in postfix/main.cf to just transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf and thus simplify your Postfix config and make it more standard, although it will continue to work as you have it. Also the mm_cfg.py you posted previously does not contain the lines add_virtualhost('list.ournet.biz', 'list.ournet.biz') add_virtualhost('list.mobilier.md', 'list.mobilier.md') and it should. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- === modified file 'Mailman/MTA/Postfix.py' --- Mailman/MTA/Postfix.py 2014-01-09 18:44:08 +0000 +++ Mailman/MTA/Postfix.py 2015-05-27 14:41:26 +0000 @@ -127,10 +127,13 @@ # Set up the mailman-loop address loopaddr = Utils.get_site_email(mlist.host_name, extra='loop') loopdest = Utils.ParseEmail(loopaddr)[0] + # And the site list posting address. + siteaddr = Utils.get_site_email(mlist.host_name) + sitedest = Utils.ParseEmail(siteaddr)[0] if mm_cfg.VIRTUAL_MAILMAN_LOCAL_DOMAIN: loopdest += '@' + mm_cfg.VIRTUAL_MAILMAN_LOCAL_DOMAIN # Seek to the end of the text file, but if it's empty write the standard - # disclaimer, and the loop catch address. + # disclaimer, and the loop catch address and site address. fp.seek(0, 2) if not fp.tell(): print >> fp, """\ @@ -145,7 +148,13 @@ # LOOP ADDRESSES START %s\t%s # LOOP ADDRESSES END -""" % (loopaddr, loopdest) + +# We also add the site list address in each virtual domain as that address +# is exposed on admin and listinfo overviews. +# SITE ADDRESSES START +%s\t%s +# SITE ADDRESSES END +""" % (loopaddr, loopdest, siteaddr, sitedest) # The text file entries get a little extra info print >> fp, '# STANZA START:', listname print >> fp, '# CREATED:', time.ctime(time.time()) @@ -168,6 +177,8 @@ def _check_for_virtual_loopaddr(mlist, filename): loopaddr = Utils.get_site_email(mlist.host_name, extra='loop') loopdest = Utils.ParseEmail(loopaddr)[0] + siteaddr = Utils.get_site_email(mlist.host_name) + sitedest = Utils.ParseEmail(siteaddr)[0] infp = open(filename) omask = os.umask(007) try: @@ -200,6 +211,32 @@ else: # This isn't our loop address, so spit it out and continue outfp.write(line) + # Now do it all again for the site list address. It must follow the + # loop addresses. + while True: + line = infp.readline() + if not line: + break + outfp.write(line) + if line.startswith('# SITE ADDRESSES START'): + break + # Now see if our domain has already been written + while True: + line = infp.readline() + if not line: + break + if line.startswith('# SITE ADDRESSES END'): + # It hasn't + print >> outfp, '%s\t%s' % (siteaddr, sitedest) + outfp.write(line) + break + elif line.startswith(siteaddr): + # We just found it + outfp.write(line) + break + else: + # This isn't our loop address, so spit it out and continue + outfp.write(line) outfp.writelines(infp.readlines()) finally: infp.close() From ournet.biz at gmail.com Wed May 27 18:36:14 2015 From: ournet.biz at gmail.com (EyeLand) Date: Wed, 27 May 2015 19:36:14 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: 2015-05-03 15:41 GMT+03:00 Stephen J. Turnbull : > EyeLand writes: > > > I not see OWNERS_CAN_ENABLE_PERSONALIZATION and > VERP_PERSONALIZED_DELIVERIES > > Defaults are set in /usr/lib/mailman/Mailman/Defaults.py on my Debian > system. You should not change that file, any changes will be > overwritten the next time you upgrade. Instead, add those variables > and their new settings to mm_cfg.py > I not have file mm_cfg.py, but I have files mm_cfg.pyc and mm_cfg.py.dist, where I need to insert variables? From mark at msapiro.net Wed May 27 18:51:38 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 11:51:38 -0500 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On May 27, 2015 11:36:14 AM CDT, EyeLand wrote: > >I not have file mm_cfg.py, but I have files mm_cfg.pyc and >mm_cfg.py.dist, >where I need to insert variables? Where did this come from. https://gist.githubusercontent.com/eyeland/b3a2ede982b5db3ab3dc/raw/a18096825a97c6d752f81c6cea68ad221e1c16c9/gistfile1.txt -- Mark Sapiro Sent from my Android phone with K-9 Mail. [Unpaid endorsement] From ournet.biz at gmail.com Wed May 27 19:13:13 2015 From: ournet.biz at gmail.com (EyeLand) Date: Wed, 27 May 2015 20:13:13 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: 2015-05-27 19:51 GMT+03:00 Mark Sapiro : > On May 27, 2015 11:36:14 AM CDT, EyeLand wrote: > > > >I not have file mm_cfg.py, but I have files mm_cfg.pyc and > >mm_cfg.py.dist, > >where I need to insert variables? > > > Where did this come from. > > > https://gist.githubusercontent.com/eyeland/b3a2ede982b5db3ab3dc/raw/a18096825a97c6d752f81c6cea68ad221e1c16c9/gistfile1.txt > > > -- > Mark Sapiro > Sent from my Android phone with K-9 Mail. [Unpaid endorsement] > file is from /etc/mailman/mm_cfg.py, there I need to insert next variables? OWNERS_CAN_ENABLE_PERSONALIZATION = Yes VERP_PERSONALIZED_DELIVERIES = Yes From mark at msapiro.net Wed May 27 19:45:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 12:45:06 -0500 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> On May 27, 2015 12:13:13 PM CDT, EyeLand wrote: > >file is from /etc/mailman/mm_cfg.py, there I need to insert next >variables? > >OWNERS_CAN_ENABLE_PERSONALIZATION = Yes >VERP_PERSONALIZED_DELIVERIES = Yes Yes. You will probably also see a symlink to that file from /var/lib/Mailman/mm_cfg.py. -- Mark Sapiro Sent from my Android phone with K-9 Mail. [Unpaid endorsement] From ournet.biz at gmail.com Wed May 27 19:55:13 2015 From: ournet.biz at gmail.com (EyeLand) Date: Wed, 27 May 2015 20:55:13 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> Message-ID: 2015-05-27 20:45 GMT+03:00 Mark Sapiro : > On May 27, 2015 12:13:13 PM CDT, EyeLand wrote: > > > >file is from /etc/mailman/mm_cfg.py, there I need to insert next > >variables? > > > >OWNERS_CAN_ENABLE_PERSONALIZATION = Yes > >VERP_PERSONALIZED_DELIVERIES = Yes > > > Yes. > > You will probably also see a symlink to that file from > /var/lib/Mailman/mm_cfg.py. > > > -- > Mark Sapiro > Sent from my Android phone with K-9 Mail. [Unpaid endorsement] > After that I need to delete (comment) from /usr/lib/mailman/Mailman/Defaults.py next variables? # Set this variable to Yes to allow list owners to set the "personalized" # flags on their mailing lists. Turning these on tells Mailman to send # separate email messages to each user instead of batching them together for # delivery to the MTA. This gives each member a more personalized message, # but can have a heavy impact on the performance of your system. OWNERS_CAN_ENABLE_PERSONALIZATION = No and # Another good opportunity is when regular delivery is personalized. Here # again, we're already incurring the performance hit for addressing each # individual recipient. Set this to Yes to enable VERPs on all personalized # regular deliveries (personalized digests aren't supported yet). VERP_PERSONALIZED_DELIVERIES = No From mark at msapiro.net Wed May 27 23:21:48 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 May 2015 16:21:48 -0500 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> Message-ID: <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> On May 27, 2015 12:55:13 PM CDT, EyeLand wrote: > >After that I need to delete (comment) from >/usr/lib/mailman/Mailman/Defaults.py next variables? NO! NEVER edit Defaults.py! Anything in mm_cfg.py overrides the corresponding setting in Defaults.py. See . -- Mark Sapiro Sent from my Android phone with K-9 Mail. [Unpaid endorsement] From ournet.biz at gmail.com Thu May 28 10:50:39 2015 From: ournet.biz at gmail.com (EyeLand) Date: Thu, 28 May 2015 11:50:39 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> Message-ID: 2015-05-28 0:21 GMT+03:00 Mark Sapiro : > On May 27, 2015 12:55:13 PM CDT, EyeLand wrote: > > > >After that I need to delete (comment) from > >/usr/lib/mailman/Mailman/Defaults.py next variables? > > > NO! NEVER edit Defaults.py! > > Anything in mm_cfg.py overrides the corresponding setting in Defaults.py. > > See . > > > -- > Mark Sapiro > Sent from my Android phone with K-9 Mail. [Unpaid endorsement] > I setup on /etc/mailman/mm_cfg.py variables and I view subscriber email on each mail OWNERS_CAN_ENABLE_PERSONALIZATION = Yes VERP_PERSONALIZED_DELIVERIES = Yes after I click on Full personalisation on http://list.ournet.biz/cgi-bin/mailman/admin/test/nondigest and I test to insert next variables on mail, top and futer user_address user_delivered_to user_password user_name user_optionsurl but they are not convert and I receive on subscriber email simple text user_address user_delivered_to user_password user_name user_optionsurl From lac at openend.se Thu May 28 11:11:15 2015 From: lac at openend.se (Laura Creighton) Date: Thu, 28 May 2015 11:11:15 +0200 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: Message from EyeLand of "Thu, 28 May 2015 11:50:39 +0300." References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> Message-ID: <201505280911.t4S9BFK8013009@fido.openend.se> Did you remember to restart mailman after you made these changes? You need to restart qrunner for the change to actually take effect. Laura From ournet.biz at gmail.com Thu May 28 11:27:50 2015 From: ournet.biz at gmail.com (EyeLand) Date: Thu, 28 May 2015 12:27:50 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <201505280911.t4S9BFK8013009@fido.openend.se> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> <201505280911.t4S9BFK8013009@fido.openend.se> Message-ID: 2015-05-28 12:11 GMT+03:00 Laura Creighton : > Did you remember to restart mailman after you made these changes? > You need to restart qrunner for the change to actually take effect. > I write on console service mailman restart service amavis restart service postfix restart From mark at msapiro.net Thu May 28 13:46:01 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 May 2015 04:46:01 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> Message-ID: <5566FFF9.5030202@msapiro.net> On 05/28/2015 01:50 AM, EyeLand wrote: > > I setup on /etc/mailman/mm_cfg.py variables and I view subscriber email > on each mail > > OWNERS_CAN_ENABLE_PERSONALIZATION = Yes > VERP_PERSONALIZED_DELIVERIES = Yes > > after I click on Full personalisation on > http://list.ournet.biz/cgi-bin/mailman/admin/test/nondigest and I test > to insert next variables on mail, top and futer > > user_address > user_delivered_to > user_password > user_name > user_optionsurl > > but they are not convert and I receive on subscriber email simple text > > user_address > user_delivered_to > user_password > user_name > user_optionsurl You need to put, e.g., %(user_address)s in msg_header and msg_footer, not just user_address. If this does not explain the issue, please post the exact contents of msg_header and msg_footer and an exampl of the email received from the list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Thu May 28 14:07:48 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 28 May 2015 21:07:48 +0900 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> Message-ID: <87egm0vraj.fsf@uwakimon.sk.tsukuba.ac.jp> EyeLand writes: > insert next variables on mail, top and futer > > user_address > user_delivered_to > user_password > user_name > user_optionsurl > > but they are not convert and I receive on subscriber email simple text > > user_address > user_delivered_to > user_password > user_name > user_optionsurl Syntax error? Try $(user_address)s $(user_delivered_to)s $(user_password)s $(user_name)s $(user_optionsurl)s and restart. From hansen at rc.org Thu May 28 17:25:58 2015 From: hansen at rc.org (Allan Hansen) Date: Thu, 28 May 2015 08:25:58 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <54A83550-EBB9-4E0F-A8D4-48BBA7894B7A@rc.org> Hi Stephen, You?re right. AOL does not accept these messages with ?invalid? at the end. You?re recommending this: name, addr = parseadder(msg.get('from')) if addr.endswith('aol.com') or addr.endswith('yahoo.com'): # I forget what happens if it's a bare address name = "%s (%s) via list" % (name if name else "Anonymous", addr) addr = del msg['from?] msg['from'] = formataddr((name, addrs)) Can I copy this code directly into the file? Is valid syntax? (I have 40+ lists) Yours, Allan > On May 24, 2015, at 6:10 , Stephen J. Turnbull wrote: > > Allan Hansen writes: > >> 69,74d68 >> < >> < # Added to deal with DMARC issuej >> < name, addrs = parseaddr(msg.get('from')) >> < addrs += '.invalid' > > This is known to be a bad idea, as it increases the spam score at many > sites (because the author's mail domain doesn't resolve). Subscribers > at such sites may have trouble receiving mail, and your list(s) may be > tagged as suspicious. > > I would recommend the From-munging approach: > > name, addr = parseadder(msg.get('from')) > if addr.endswith('aol.com') or addr.endswith('yahoo.com'): > # I forget what happens if it's a bare address > name = "%s (%s) via list" % (name if name else "Anonymous", addr) > addr = > del msg['from'] > msg['from'] = formataddr((name, addr)) > > Mark (or you) probably have better code, and in some cases you may > want to add the addr to the Reply-To field. > >> < del msg['from'] >> < msg['from'] = formataddr((name, addrs)) >> \ No newline at end of file > From ournet.biz at gmail.com Thu May 28 18:05:25 2015 From: ournet.biz at gmail.com (EyeLand) Date: Thu, 28 May 2015 19:05:25 +0300 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <87egm0vraj.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5544FF42.9040207@msapiro.net> <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> <87egm0vraj.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: 2015-05-28 15:07 GMT+03:00 Stephen J. Turnbull : > Syntax error? Try > > $(user_address)s > $(user_delivered_to)s > $(user_password)s > $(user_name)s > $(user_optionsurl)s > > and restart. > Not work, look mail source: https://gist.githubusercontent.com/eyeland/d6fc6ff64d4228ad8a6d/raw/aeb852b4bde72a99424a50ab9f0e78e526b683e0/gistfile1.txt From mark at msapiro.net Thu May 28 23:28:27 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 May 2015 14:28:27 -0700 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: References: <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> <87egm0vraj.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <5567887B.9040109@msapiro.net> On 05/28/2015 09:05 AM, EyeLand wrote: > 2015-05-28 15:07 GMT+03:00 Stephen J. Turnbull >: > > Syntax error? Try > > $(user_address)s > $(user_delivered_to)s > $(user_password)s > $(user_name)s > $(user_optionsurl)s > > and restart. > > > > Not work, look mail source: > https://gist.githubusercontent.com/eyeland/d6fc6ff64d4228ad8a6d/raw/aeb852b4bde72a99424a50ab9f0e78e526b683e0/gistfile1.txt Thats because they should be %(user_address)s, etc., not $(user_address)s. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu May 28 23:31:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 May 2015 14:31:16 -0700 Subject: [Mailman-Users] DMARC hack In-Reply-To: <54A83550-EBB9-4E0F-A8D4-48BBA7894B7A@rc.org> References: <4D3112EB-BFF0-41C1-AFF7-485D2BBCA0EF@rc.org> <87egm6glyd.fsf@uwakimon.sk.tsukuba.ac.jp> <54A83550-EBB9-4E0F-A8D4-48BBA7894B7A@rc.org> Message-ID: <55678924.4000805@msapiro.net> On 05/28/2015 08:25 AM, Allan Hansen wrote: > Hi Stephen, > > You?re right. AOL does not accept these messages with ?invalid? at the end. > > You?re recommending this: > > name, addr = parseadder(msg.get('from')) > if addr.endswith('aol.com') or addr.endswith('yahoo.com'): > # I forget what happens if it's a bare address > name = "%s (%s) via list" % (name if name else "Anonymous", addr) > addr = > del msg['from?] > msg['from'] = formataddr((name, addrs)) > > Can I copy this code directly into the file? > Is valid syntax? (I have 40+ lists) No, it is meant to be replaced with the actual list posting address, but is there some reasone you don't want to do what I posted at ? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cybergram at eastlink.ca Thu May 28 23:17:15 2015 From: cybergram at eastlink.ca (Nancy C) Date: Thu, 28 May 2015 18:17:15 -0300 Subject: [Mailman-Users] Question about confirming each email for one subscriber Message-ID: <000201d0998b$ac024c40$0406e4c0$@eastlink.ca> Hi We have a member who is very computer / email illiterate & continually sends emails that should not get through to the group as a whole. Is there a setting that could be made so her emails always come to the listkeepers first? Thank you for any help :) Nancy From bryan at skiblack.com Fri May 29 03:28:50 2015 From: bryan at skiblack.com (Bryan Blackwell) Date: Thu, 28 May 2015 21:28:50 -0400 Subject: [Mailman-Users] Question about confirming each email for one subscriber In-Reply-To: <000201d0998b$ac024c40$0406e4c0$@eastlink.ca> References: <000201d0998b$ac024c40$0406e4c0$@eastlink.ca> Message-ID: <142CC3C0-C191-4108-A707-845C0E4EE5B6@skiblack.com> Easy to do - check the "mod" (for "moderate") box next to their name on the member list, and set the list so moderated messages are held for review under Privacy options... > Sender filters > member_moderation_action. --Bryan > On May 28, 2015, at 5:17 PM, Nancy C wrote: > > Hi > > > > We have a member who is very computer / email illiterate & continually sends > emails that should not get through > > to the group as a whole. > > > > Is there a setting that could be made so her emails always come to the > listkeepers first? > > > > Thank you for any help :) > > > > Nancy > > ------------------------------------------------------ > 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/bryan%40skiblack.com From akgul at bilkent.edu.tr Fri May 29 11:42:45 2015 From: akgul at bilkent.edu.tr (Mustafa Akgul) Date: Fri, 29 May 2015 12:42:45 +0300 Subject: [Mailman-Users] debian jessie - apache2.4. Message-ID: <20150529124245.202afbd2.akgul@bilkent.edu.tr> I have debian jessie running apache2 2.4.10-10 , mailman 1:2.1.18-2 and postfix 2.11.3-1 I have difficulty i mailman-apache interface. I was running on debian7 and apache2.2 nicely. I took mailman, apache.conf, modified allow,deny setting http://filiz.inet-tr.org.tr/cgi-bin/mailman/listinfo ask what to do with listinfo http://filiz.inet-tr.org.tr/cgi-bin/mailman/admindb/edu-net I got The requested URL /cgi-bin/mailman/admindb/edu-net was not found on this server mailman.conf in apache sites-enabled is: ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/ AllowOverride None Options ExecCGI # AddHandler cgi-script .cgi Require all granted Options FollowSymlinks AllowOverride None Require all granted AllowOverride None Require all granted ServerName liste.inet-tr.org.tr ServerAlias filiz.inet-tr.org.tr DocumentRoot /var/www/web ErrorLog /var/log/apache2/liste-error.log CustomLog /var/log/apache2/liste-access.log combined Options FollowSymLinks AllowOverride None ---- Any suggestion ? Best regards -- Mustafa Akgul From stephen at xemacs.org Fri May 29 13:05:25 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Fri, 29 May 2015 20:05:25 +0900 Subject: [Mailman-Users] Conceal the member's address In-Reply-To: <5567887B.9040109@msapiro.net> References: <55451624.8010500@msapiro.net> <5545305D.4030203@msapiro.net> <55454265.6010402@msapiro.net> <87pp6h6dfs.fsf@uwakimon.sk.tsukuba.ac.jp> <3E8F385C-8377-4B3F-99DF-E00DA090B5BC@msapiro.net> <028AA5C3-7640-4E48-897A-E236C1662BCD@msapiro.net> <87egm0vraj.fsf@uwakimon.sk.tsukuba.ac.jp> <5567887B.9040109@msapiro.net> Message-ID: <878uc7ve2y.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > Thats because they should be %(user_address)s, etc., not $(user_address)s. Oops, sorry about that. Too much shell programming (and I don't use % formatting anymore, I almost always use .format). From mail at casi.pw Fri May 29 01:49:08 2015 From: mail at casi.pw (casi.pw) Date: Fri, 29 May 2015 01:49:08 +0200 Subject: [Mailman-Users] Mailman 3: Uncaught runner exception: 'ascii' codec can't encode character Message-ID: <5567A974.2010009@casi.pw> Hello, I'm trying to run mailman 3 in production on a shared server. Mailman gets its mail from exim via LMTP. First it appeared to work fine, but I got a problem: According to my mailman.log, mails with special characters (in this case "?", but also Germanic umlauts as "?") in their bodies are shunted and not delivered. (Mails with special characters only in their subjects but not in their bodies are not affected by this error.) ---- May 29 01:17:26 2015 (2332) ACCEPT: <5567XXXX.5040XXX at XXXX.net> May 29 01:17:27 2015 (2317) Uncaught runner exception: 'ascii' codec can't encode character '\u20ac' in position 1: ordinal not in range(128) May 29 01:17:27 2015 (2317) Traceback (most recent call last): File "/home/casi/mailman3/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 165, in _one_iteration self._process_one_file(msg, msgdata) File "/home/casi/mailman3/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 258, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/casi/mailman3/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 41, in _dispose process(mlist, msg, msgdata, pipeline) File "/home/casi/mailman3/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/pipelines.py", line 62, in process handler.process(mlist, msg, msgdata) File "/home/casi/mailman3/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/handlers/to_digest.py", line 54, in process mbox.add(msg) File "/package/host/localhost/python-3.4/lib/python3.4/mailbox.py", line 601, in add self._toc[self._next_key] = self._append_message(message) File "/package/host/localhost/python-3.4/lib/python3.4/mailbox.py", line 752, in _append_message offsets = self._install_message(message) File "/package/host/localhost/python-3.4/lib/python3.4/mailbox.py", line 824, in _install_message self._dump_message(message, self._file, self._mangle_from_) File "/package/host/localhost/python-3.4/lib/python3.4/mailbox.py", line 214, in _dump_message gen.flatten(message) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 112, in flatten self._write(msg) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 178, in _write self._dispatch(msg) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 211, in _dispatch meth(msg) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 433, in _handle_text super(BytesGenerator,self)._handle_text(msg) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 246, in _handle_text self._write_lines(payload) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 158, in _write_lines self.write(laststripped) File "/package/host/localhost/python-3.4/lib/python3.4/email/generator.py", line 407, in write self._fp.write(s.encode('ascii', 'surrogateescape')) UnicodeEncodeError: 'ascii' codec can't encode character '\u20ac' in position 1: ordinal not in range(128) May 29 01:17:27 2015 (2317) SHUNTING: 1432855047.4798193+1fe1f94488b77c19d5521cb8cbcda48f52828752 ---- Deleting the list's digest.mmdf file had no effect. "mailman unshunt" created a new, empty digest.mmdf file, but the mails where shunted again. Is there any solution for this issue? Best regards, casi From tcora at skylands.ibmwr.org Fri May 29 02:59:44 2015 From: tcora at skylands.ibmwr.org (Tom Coradeschi) Date: Thu, 28 May 2015 20:59:44 -0400 Subject: [Mailman-Users] Question about confirming each email for one subscriber In-Reply-To: <000201d0998b$ac024c40$0406e4c0$@eastlink.ca> References: <000201d0998b$ac024c40$0406e4c0$@eastlink.ca> Message-ID: <4D4F014D-7E7D-4B49-9423-B3F28CEC9FC3@skylands.ibmwr.org> > On 28 May 2015, at 5:17 PM, Nancy C wrote: > > Hi > > > > We have a member who is very computer / email illiterate & continually sends > emails that should not get through > > to the group as a whole. > > > > Is there a setting that could be made so her emails always come to the > listkeepers first? Sure: Put that user?s account in moderation. ? tom coradeschi tcora at skylands.ibmwr.org From barry at list.org Fri May 29 15:18:09 2015 From: barry at list.org (Barry Warsaw) Date: Fri, 29 May 2015 09:18:09 -0400 Subject: [Mailman-Users] Mailman 3: Uncaught runner exception: 'ascii' codec can't encode character In-Reply-To: <5567A974.2010009@casi.pw> References: <5567A974.2010009@casi.pw> Message-ID: <20150529091809.40189e14@anarchist.wooz.org> On May 29, 2015, at 01:49 AM, casi.pw wrote: >I'm trying to run mailman 3 in production on a shared server. Mailman >gets its mail from exim via LMTP. First it appeared to work fine, but I >got a problem: > >According to my mailman.log, mails with special characters (in this case >"?", but also Germanic umlauts as "?") in their bodies are shunted and >not delivered. (Mails with special characters only in their subjects but >not in their bodies are not affected by this error.) This looks like a legitimate bug. Would you mind reporting it at: https://gitlab.com/mailman/mailman Cheers, -Barry From exim4debian at gmail.com Fri May 29 16:02:38 2015 From: exim4debian at gmail.com (James Nightly) Date: Fri, 29 May 2015 07:02:38 -0700 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... Message-ID: How can I configure mailman on Debian to reject messages with X-Spam-Score over 8? We are getting bombarded with spam, messages are tagged by Spamassasin, but for some reason Exim4 still sends these to Mailman. Debian 8 (Jessie) Exim version 4.84 Mailman 1:2.1.18-2 SpamAssassin version 3.4.0, running on Perl version 5.20.2 From adam-mailman at amyl.org.uk Fri May 29 17:12:11 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Fri, 29 May 2015 16:12:11 +0100 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... In-Reply-To: References: Message-ID: <20150529151211.GO9573@hendricks.amyl.org.uk> On Fri, May 29, 2015 at 07:02:38AM -0700, James Nightly wrote: > How can I configure mailman on Debian to reject messages with > X-Spam-Score over 8? We are getting bombarded with spam, messages are > tagged by Spamassasin, but for some reason Exim4 still sends these to > Mailman. Drop/Discard/Reject mails at SMTP time, before they hit Mailman? -- "The power of accurate observation is often called cynicism by those who do not have it." -- George Bernard Shaw From skip.montanaro at gmail.com Fri May 29 17:43:20 2015 From: skip.montanaro at gmail.com (Skip Montanaro) Date: Fri, 29 May 2015 10:43:20 -0500 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... In-Reply-To: <20150529151211.GO9573@hendricks.amyl.org.uk> References: <20150529151211.GO9573@hendricks.amyl.org.uk> Message-ID: On Fri, May 29, 2015 at 10:12 AM, Adam McGreggor wrote: > > Drop/Discard/Reject mails at SMTP time, before they hit Mailman? Right, but it seems like James is saying Exim4 isn't doing that. I poked around the MM config for the chicago at python.org mailing list, but for the life of me couldn't find the setting where it holds messages with X-Spam-Score with spam or unsure values. (We use SpamBayes on mail.python.org.) I know it's there somewhere, but I can never find such nuggets. Mail.python.org has a very mature Postfix setup. It's all magic to me (well, except for the SpamBayes part), but I think publishing a small document about the configuration might be worthwhile. Skip Montanaro From stephen at xemacs.org Fri May 29 18:24:37 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 30 May 2015 01:24:37 +0900 Subject: [Mailman-Users] Mailman 3: Uncaught runner exception: 'ascii' codec can't encode character In-Reply-To: <20150529091809.40189e14@anarchist.wooz.org> References: <5567A974.2010009@casi.pw> <20150529091809.40189e14@anarchist.wooz.org> Message-ID: <874mmvuzay.fsf@uwakimon.sk.tsukuba.ac.jp> Barry Warsaw writes: > On May 29, 2015, at 01:49 AM, casi.pw wrote: > >According to my mailman.log, mails with special characters (in this case > >"?", but also Germanic umlauts as "?") in their bodies are shunted and > >not delivered. > > This looks like a legitimate bug. It doesn't just look like one, it *is* one. Mailman should *never* need to shunt because of a Unicode error. If it's a design bug, it's that Mailman isn't aware of 8-bit Content-Transfer-Encoding. It might be that a dain-bramaged MUA or MTA isn't setting that header, though, and in that case you might want to Discard, Reject, or Hold rather than deliver (depends on how "Father Knows Best" you want to be about it). You shouldn't need to shunt because of body problems though. Steve From adam-mailman at amyl.org.uk Fri May 29 18:28:05 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Fri, 29 May 2015 17:28:05 +0100 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... In-Reply-To: References: <20150529151211.GO9573@hendricks.amyl.org.uk> Message-ID: <20150529162805.GP9573@hendricks.amyl.org.uk> On Fri, May 29, 2015 at 10:43:20AM -0500, Skip Montanaro wrote: > On Fri, May 29, 2015 at 10:12 AM, Adam McGreggor > wrote: > > > > Drop/Discard/Reject mails at SMTP time, before they hit Mailman? > > Right, but it seems like James is saying Exim4 isn't doing that. If the mails are being scored (which was mentioned), then I would be inclined to deal with those before they're accepted -- let alone before they get to Exim's handling (routing) for Mailman. > I poked around the MM config for the chicago at python.org mailing list, > but for the life of me couldn't find the setting where it holds > messages with X-Spam-Score with spam or unsure values. (We use > SpamBayes on mail.python.org.) I know it's there somewhere, but I can > never find such nuggets. I have a couple of ACLS (for check_message): the 'magic' I use is condition = ${if >{$spam_score_int}{60}{1}{0}} (A SpamAssassin score >6) For drop/discard/reject, maybe see https://lists.exim.org/lurker/message/20090116.101052.18c04deb.en.html In my view (but "your mailsystem, your rules"), "high" scored Spam shouldn't be accepted; so score it, and deal with it at SMTP time; deal with the others once accepted. -- War is Peace Freedom is Slavery Ignorance is Strength 1984 From stephen at xemacs.org Fri May 29 18:28:23 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 30 May 2015 01:28:23 +0900 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... In-Reply-To: References: Message-ID: <87382fuz4o.fsf@uwakimon.sk.tsukuba.ac.jp> James Nightly writes: > How can I configure mailman on Debian to reject messages with > X-Spam-Score over 8? We are getting bombarded with spam, messages are > tagged by Spamassasin, but for some reason Exim4 still sends these to > Mailman. "Evaluating" numbers by regexp is finicky, but there's a SpamAssassin setting that makes it provide a header with as many stars as the message got spam points. Then you just filter on r"^X-Spam-Stars: \*\*\*\*\*\*\*\*" (where you need to substitute the real header name for "X-Spam-Stars", of course). From adam at amyl.org.uk Fri May 29 18:32:54 2015 From: adam at amyl.org.uk (Adam McGreggor) Date: Fri, 29 May 2015 17:32:54 +0100 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... In-Reply-To: <20150529162805.GP9573@hendricks.amyl.org.uk> References: <20150529151211.GO9573@hendricks.amyl.org.uk> <20150529162805.GP9573@hendricks.amyl.org.uk> Message-ID: <20150529163254.GQ9573@hendricks.amyl.org.uk> On Fri, May 29, 2015 at 05:28:05PM +0100, Adam McGreggor wrote: > I have a couple of ACLS (for check_message): the 'magic' I use is > > condition = ${if >{$spam_score_int}{60}{1}{0}} http://www.exim.org/exim-html-current/doc/html/spec_html/ch-content_scanning_at_acl_time.html is still the place I go to, if needed? -- "If we let people see that kind of thing, there would never again be any war." (US spokesman, on news film of Iraqi soldiers killed by helicopter gunfire) From mark at msapiro.net Sat May 30 03:39:10 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 May 2015 18:39:10 -0700 Subject: [Mailman-Users] X-Spam-Score: 22.4 and still sent out to the list... In-Reply-To: <87382fuz4o.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87382fuz4o.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <556914BE.4070308@msapiro.net> On 05/29/2015 09:28 AM, Stephen J. Turnbull wrote: > James Nightly writes: > > > How can I configure mailman on Debian to reject messages with > > X-Spam-Score over 8? We are getting bombarded with spam, messages are > > tagged by Spamassasin, but for some reason Exim4 still sends these to > > Mailman. > > "Evaluating" numbers by regexp is finicky, but there's a SpamAssassin > setting that makes it provide a header with as many stars as the > message got spam points. Then you just filter on r"^X-Spam-Stars: > \*\*\*\*\*\*\*\*" (where you need to substitute the real header name > for "X-Spam-Stars", of course). Right, and while it is still best to do this ahead of Mailman, Mailman's Privacy options... -> Spam filters -> header_filter_rules is the place to do it in Mailman. (and that's where chicago at python.org does it bases on x-spam-status:). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From akgul at bilkent.edu.tr Sat May 30 21:52:15 2015 From: akgul at bilkent.edu.tr (Mustafa Akgul) Date: Sat, 30 May 2015 22:52:15 +0300 Subject: [Mailman-Users] jessie, apache2.4 solved Message-ID: I had problem in web interface of mailman, error was "cgi-bin/mailman/admindb/listname was undefined" it turned out that mod.cgi was not loaded. adding mod.cgi yo mods-enabled solved the problem. Regards Mustafa Akgul From m.kozlowski at mini.pw.edu.pl Sun May 31 07:41:05 2015 From: m.kozlowski at mini.pw.edu.pl (Marek Kozlowski) Date: Sun, 31 May 2015 07:41:05 +0200 Subject: [Mailman-Users] Mailman: postfix and/or apache on remote machines? Message-ID: <556A9EF1.7050000@mini.pw.edu.pl> :-) I'm afraid documentation doesn't say it clearly: I'm thinking of running web server and mail server on separate virtual machines (separate hosts). I'd like to install mailman on one of those hosts or on a separate VM. Does mailman require postfix and apache on the same host (as mailman)? Can it use a remote mail or a remote web server? Configuration doesn't provide such examples but doesn't say clearly it is impossible... Best regards, Marek From mark at msapiro.net Sun May 31 10:20:58 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 May 2015 01:20:58 -0700 Subject: [Mailman-Users] Mailman: postfix and/or apache on remote machines? In-Reply-To: <556A9EF1.7050000@mini.pw.edu.pl> References: <556A9EF1.7050000@mini.pw.edu.pl> Message-ID: <556AC46A.6050102@msapiro.net> On 05/30/2015 10:41 PM, Marek Kozlowski wrote: > > I'm afraid documentation doesn't say it clearly: There's a FAQ at which says a bit about it. > I'm thinking of running web server and mail server on separate virtual > machines (separate hosts). I'd like to install mailman on one of those > hosts or on a separate VM. Does mailman require postfix and apache on > the same host (as mailman)? Can it use a remote mail or a remote web > server? Configuration doesn't provide such examples but doesn't say > clearly it is impossible... While it is possible to have the incoming mail server and Mailman on separate machines by using, e.g., fetchmail or NFS shared files to get the mail to Mailman, it is better to have at least a minimal MTA on the Mailman host, although mail can be relayed to it from a 'main' mail server. The outgoing MTA that Mailman sends to is configured via SMTPHOST and SMTPPORT in mm_cfg.py and can be anywhere that Mailman can talk to via SMTP, although if it is a 'smarthost' relay, you may need to patch Mailman to do authentication if it is not in a local network. Mailman and the web server can be on different hosts if they share files via NFS or if the main web server acts as a proxy for a limited web server on the Mailman host. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From heller at deepsoft.com Sun May 31 16:39:16 2015 From: heller at deepsoft.com (Robert Heller) Date: Sun, 31 May 2015 10:39:16 -0400 Subject: [Mailman-Users] Mailman crash/error question Message-ID: <201505311439.t4VEdGVQ002171@sharky2.deepsoft.com> Recently the moderator of a mailing list I host got a Mailman error. And this is what was in Mailman's error log: May 29 21:55:21 2015 admin(16001): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(16001): [----- Mailman Version: 2.1.16 -----] admin(16001): [----- Traceback ------] admin(16001): Traceback (most recent call last): admin(16001): File "/usr/lib/mailman/scripts/driver", line 117, in run_main admin(16001): main() admin(16001): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 203, in main admin(16001): process_form(mlist, doc, cgidata) admin(16001): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 785, in process_form admin(16001): if id not in senderactions[sender]['message_ids']: admin(16001): KeyError: 'message_ids' admin(16001): [----- Python Information -----] admin(16001): sys.version = 2.4.3 (#1, Jan 9 2013, 06:47:03) [GCC 4.1.2 20080704 (Red Hat 4.1.2-54)] admin(16001): sys.executable = /usr/bin/python admin(16001): sys.prefix = /usr admin(16001): sys.exec_prefix = /usr admin(16001): sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python24.zip', '/usr/lib64/python2.4/', '/usr/lib64/python2.4/plat-linux2', '/usr/lib64/python2.4/lib-tk', '/usr/lib64/python2.4/lib-dynload', '/usr/lib/python2.4/site-packages'] admin(16001): sys.platform = linux2 admin(16001): [----- Environment Variables -----] admin(16001): HTTP_COOKIE: wendell-townsfolk+moderator=28020000006976186955732800000037663266333937633233343834636466636163626230326138666637653834613966616561613230 This is on a CentOS 5.11 system (64bit), with Mailman 2.1.16 that I built as an RPM from the sources. Is this something I need to worry about? Or is it likely to have been caused by an illformed spam message? -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller at deepsoft.com -- Webhosting Services From stephen at xemacs.org Sun May 31 18:01:18 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 01 Jun 2015 01:01:18 +0900 Subject: [Mailman-Users] Mailman crash/error question In-Reply-To: <201505311439.t4VEdGVQ002171@sharky2.deepsoft.com> References: <201505311439.t4VEdGVQ002171@sharky2.deepsoft.com> Message-ID: <87iob8u46p.fsf@uwakimon.sk.tsukuba.ac.jp> Robert Heller writes: > admin(16001): if id not in senderactions[sender]['message_ids']: > admin(16001): KeyError: 'message_ids' > Is this something I need to worry about? Or is it likely to have > been caused by an illformed spam message? I'm not familiar with that particular part of the code, but despite the key 'message_ids' I don't think this has anything to do with the well-formedness of the message. It looks to me like line 760 of Mailman/Cgi/admindb.py is getting skipped because none of the relevant variables are present in the CGI data received. I don't know why that would be. (Don't worry about the code reference if you're not prepared to look at it yourself, I just wanted to save Mark the time since I did look it up.) Steve From mark at msapiro.net Sun May 31 20:18:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 May 2015 11:18:34 -0700 Subject: [Mailman-Users] Mailman crash/error question In-Reply-To: <201505311439.t4VEdGVQ002171@sharky2.deepsoft.com> References: <201505311439.t4VEdGVQ002171@sharky2.deepsoft.com> Message-ID: <556B507A.30200@msapiro.net> On 05/31/2015 07:39 AM, Robert Heller wrote: > Recently the moderator of a mailing list I host got a Mailman error. And this > is what was in Mailman's error log: > > May 29 21:55:21 2015 admin(16001): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > admin(16001): [----- Mailman Version: 2.1.16 -----] > admin(16001): [----- Traceback ------] > admin(16001): Traceback (most recent call last): > admin(16001): File "/usr/lib/mailman/scripts/driver", line 117, in run_main > admin(16001): main() > admin(16001): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 203, in main > admin(16001): process_form(mlist, doc, cgidata) > admin(16001): File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 785, in process_form > admin(16001): if id not in senderactions[sender]['message_ids']: > admin(16001): KeyError: 'message_ids' > admin(16001): [----- Python Information -----] > admin(16001): sys.version = 2.4.3 (#1, Jan 9 2013, 06:47:03) > [GCC 4.1.2 20080704 (Red Hat 4.1.2-54)] > admin(16001): sys.executable = /usr/bin/python > admin(16001): sys.prefix = /usr > admin(16001): sys.exec_prefix = /usr > admin(16001): sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python24.zip', '/usr/lib64/python2.4/', '/usr/lib64/python2.4/plat-linux2', '/usr/lib64/python2.4/lib-tk', '/usr/lib64/python2.4/lib-dynload', '/usr/lib/python2.4/site-packages'] > admin(16001): sys.platform = linux2 > admin(16001): [----- Environment Variables -----] > admin(16001): HTTP_COOKIE: wendell-townsfolk+moderator=28020000006976186955732800000037663266333937633233343834636466636163626230326138666637653834613966616561613230 > > This is on a CentOS 5.11 system (64bit), with Mailman 2.1.16 that I built as > an RPM from the sources. > > Is this something I need to worry about? Or is it likely to have been caused > by an illformed spam message? and on 05/31/2015 09:01 AM, Stephen J. Turnbull wrote: > (Don't worry about the code reference if you're not prepared to look > at it yourself, I just wanted to save Mark the time since I did look > it up.) Thanks ;) This occurred when a moderator (already authenticated) submitted an admindb form for the wendell-townsfolk list, and the post data from the form was incomplete. This probably occurred because for some reason, the http transaction between the moderator's web browser and the web server on the Mailman host got interrupted mid stream, or possibly the moderator went to an admindb URL with some kind of query fragment, but insufficient data. If there weren't more in the [----- Environment Variables -----] section in the error log, that leans towards the interruption scenario. If there were, I might be able to say more if I saw them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan