From michael.capelle at charter.net Fri Jul 1 05:25:49 2011 From: michael.capelle at charter.net (Michael Capelle) Date: Thu, 30 Jun 2011 22:25:49 -0500 Subject: [Mailman-Users] a question about archiving. Message-ID: Hello. is there a way to search by topic in mailman? if not, will this be implemented? From dap1 at bellsouth.net Fri Jul 1 17:27:19 2011 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 01 Jul 2011 11:27:19 -0400 Subject: [Mailman-Users] mailpasswds error Message-ID: <4E0DE757.4060401@bellsouth.net> I am still struggling to get my monthly password reminder working. I had to change the site list from 'mailman' to 'dapmm' in order to create acceptable site mailbox names for my ISP. However, now when I run 'mailpasswds -l I get this error: Site list is missing: dapmm Obviously I am still missing a piece of the puzzle. The only change I made was "MAILMAN_SITE_LIST='dapmm'" to mm_cfg.py. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Fri Jul 1 17:56:16 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 01 Jul 2011 08:56:16 -0700 Subject: [Mailman-Users] mailpasswds error In-Reply-To: <4E0DE757.4060401@bellsouth.net> References: <4E0DE757.4060401@bellsouth.net> Message-ID: <4E0DEE20.9070106@msapiro.net> On 7/1/2011 8:27 AM, Dennis Putnam wrote: > I am still struggling to get my monthly password reminder working. I had > to change the site list from 'mailman' to 'dapmm' in order to create > acceptable site mailbox names for my ISP. However, now when I run > 'mailpasswds -l I get this error: > > Site list is missing: dapmm > > Obviously I am still missing a piece of the puzzle. The only change I > made was "MAILMAN_SITE_LIST='dapmm'" to mm_cfg.py. Apparently you also neglected to restart Mailman or you would have gotten the same error there. You have changed the name of the site list, but you haven't created a list with the new name. Your old 'mailman' list is no longer the site list. You can delete it and create a new 'dapmm' site list or rename the 'mailman' list to 'dapmm' per , or if for some reason you want to keep the 'mailman' list, that's OK, but you must have a site list and it's name is now 'dapmm', so you need to create it. Then, restart Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dap1 at bellsouth.net Fri Jul 1 19:12:12 2011 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 01 Jul 2011 13:12:12 -0400 Subject: [Mailman-Users] mailpasswds error In-Reply-To: <4E0DEE20.9070106@msapiro.net> References: <4E0DE757.4060401@bellsouth.net> <4E0DEE20.9070106@msapiro.net> Message-ID: <4E0DFFEC.4020108@bellsouth.net> Thanks for the reply. As usual, nothing is that simple. I tried to create the list 'dapmm' and got this: Jul 01 13:06:07 2011 admin(7032): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(7032): [----- Mailman Version: 2.1.13 -----] admin(7032): [----- Traceback ------] admin(7032): Traceback (most recent call last): admin(7032): File "/usr/lib/mailman/scripts/driver", line 112, in run_main admin(7032): main() admin(7032): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 56, in main admin(7032): process_request(doc, cgidata) admin(7032): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 191, in process_request admin(7032): urlhost=hostname) admin(7032): TypeError: Create() got an unexpected keyword argument 'urlhost' admin(7032): [----- Python Information -----] admin(7032): sys.version = 2.6.5 (r265:79063, May 20 2011, 13:23:49) [GCC 4.4.3] admin(7032): sys.executable = /usr/bin/python admin(7032): sys.prefix = /usr admin(7032): sys.exec_prefix = /usr admin(7032): sys.path = /usr admin(7032): sys.platform = linux2 admin(7032): [----- Environment Variables -----] I didn't include all the environment stuff because of the data it contains but if a specific variable is needed, let me know and I will post it. On 7/1/2011 11:56 AM, Mark Sapiro wrote: > On 7/1/2011 8:27 AM, Dennis Putnam wrote: >> I am still struggling to get my monthly password reminder working. I had >> to change the site list from 'mailman' to 'dapmm' in order to create >> acceptable site mailbox names for my ISP. However, now when I run >> 'mailpasswds -l I get this error: >> >> Site list is missing: dapmm >> >> Obviously I am still missing a piece of the puzzle. The only change I >> made was "MAILMAN_SITE_LIST='dapmm'" to mm_cfg.py. > > Apparently you also neglected to restart Mailman or you would have > gotten the same error there. > > You have changed the name of the site list, but you haven't created a > list with the new name. Your old 'mailman' list is no longer the site > list. You can delete it and create a new 'dapmm' site list or rename the > 'mailman' list to 'dapmm' per , or if for > some reason you want to keep the 'mailman' list, that's OK, but you must > have a site list and it's name is now 'dapmm', so you need to create it. > > Then, restart Mailman. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Fri Jul 1 21:15:43 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 1 Jul 2011 12:15:43 -0700 Subject: [Mailman-Users] mailpasswds error In-Reply-To: <4E0DFFEC.4020108@bellsouth.net> Message-ID: Dennis Putnam wrote: > >Thanks for the reply. As usual, nothing is that simple. I tried to >create the list 'dapmm' and got this: > >Jul 01 13:06:07 2011 admin(7032): >@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >admin(7032): [----- Mailman Version: 2.1.13 -----] >admin(7032): [----- Traceback ------] >admin(7032): Traceback (most recent call last): >admin(7032): File "/usr/lib/mailman/scripts/driver", line 112, in run_main >admin(7032): main() >admin(7032): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 56, >in main >admin(7032): process_request(doc, cgidata) >admin(7032): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 191, >in process_request >admin(7032): urlhost=hostname) >admin(7032): TypeError: Create() got an unexpected keyword argument >'urlhost' It appears that your /usr/lib/mailman/Mailman/Cgi/create.py script is from Mailman 2.1.14 and your base Mailman version including /usr/lib/mailman/Mailman/MailList.py is 2.1.13. These are not compatible. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dap1 at bellsouth.net Fri Jul 1 21:30:20 2011 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 01 Jul 2011 15:30:20 -0400 Subject: [Mailman-Users] mailpasswds error In-Reply-To: References: Message-ID: <4E0E204C.4080508@bellsouth.net> Thanks. Mandrivia strikes again. I guess I need figure out how to upgrade to 2.1.14. On 7/1/2011 3:15 PM, Mark Sapiro wrote: > Dennis Putnam wrote: >> Thanks for the reply. As usual, nothing is that simple. I tried to >> create the list 'dapmm' and got this: >> >> Jul 01 13:06:07 2011 admin(7032): >> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> admin(7032): [----- Mailman Version: 2.1.13 -----] >> admin(7032): [----- Traceback ------] >> admin(7032): Traceback (most recent call last): >> admin(7032): File "/usr/lib/mailman/scripts/driver", line 112, in run_main >> admin(7032): main() >> admin(7032): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 56, >> in main >> admin(7032): process_request(doc, cgidata) >> admin(7032): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 191, >> in process_request >> admin(7032): urlhost=hostname) >> admin(7032): TypeError: Create() got an unexpected keyword argument >> 'urlhost' > > It appears that your /usr/lib/mailman/Mailman/Cgi/create.py script is > from Mailman 2.1.14 and your base Mailman version including > /usr/lib/mailman/Mailman/MailList.py is 2.1.13. These are not > compatible. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Fri Jul 1 21:47:52 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 1 Jul 2011 12:47:52 -0700 Subject: [Mailman-Users] mailpasswds error In-Reply-To: <4E0E204C.4080508@bellsouth.net> Message-ID: Dennis Putnam wrote: > >Thanks. Mandrivia strikes again. I guess I need figure out how to >upgrade to 2.1.14. You could try bin/newlist. That might work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dap1 at bellsouth.net Fri Jul 1 21:57:59 2011 From: dap1 at bellsouth.net (Dennis Putnam) Date: Fri, 01 Jul 2011 15:57:59 -0400 Subject: [Mailman-Users] mailpasswds error In-Reply-To: References: Message-ID: <4E0E26C7.5030200@bellsouth.net> It turns out the RPM for 2.1.14 is not available yet for 2010. However, I reinstalled 2.1.13 and created the new list. Now I am on to the next layer of the onion. # ./config_list -i file dapmm real_name attribute not changed! It must differ from the list's name by case only. On 7/1/2011 3:47 PM, Mark Sapiro wrote: > Dennis Putnam wrote: >> Thanks. Mandrivia strikes again. I guess I need figure out how to >> upgrade to 2.1.14. > > You could try bin/newlist. That might work. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Sat Jul 2 06:17:04 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 1 Jul 2011 21:17:04 -0700 Subject: [Mailman-Users] a question about archiving. In-Reply-To: Message-ID: Michael Capelle wrote: >Hello. >is there a way to search by topic in mailman? >if not, will this be implemented? See the FAQ at for information about making archives searchable. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rfox at irex.org Fri Jul 1 21:52:27 2011 From: rfox at irex.org (rfox) Date: Fri, 1 Jul 2011 12:52:27 -0700 (PDT) Subject: [Mailman-Users] Pending messages queue empty Message-ID: <31976331.post@talk.nabble.com> Hi, I am encountering a strange issue with our listserv which I hope someone can shed some light on. The administrator/moderator of the list gets a message saying that there is a post pending approval. However, when he logs inand clicks "Tend to pending moderator requests" there is nothing there. Basically we keep getting "pending" notices but the queue is empty. It had been working and no settings were changed. We're running Mailman 2.1.14 Thanks for any insight you may have. -- View this message in context: http://old.nabble.com/Pending-messages-queue-empty-tp31976331p31976331.html Sent from the Mailman - Users mailing list archive at Nabble.com. From mark at msapiro.net Sat Jul 2 16:59:31 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 2 Jul 2011 07:59:31 -0700 Subject: [Mailman-Users] Pending messages queue empty In-Reply-To: <31976331.post@talk.nabble.com> Message-ID: rfox wrote: > >I am encountering a strange issue with our listserv Please see . >which I hope someone can >shed some light on. The administrator/moderator of the list gets a message >saying that there is a post pending approval. However, when he logs inand >clicks "Tend to pending moderator requests" there is nothing there. >Basically we keep getting "pending" notices but the queue is empty. It had >been working and no settings were changed. See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dap1 at bellsouth.net Wed Jul 6 00:44:42 2011 From: dap1 at bellsouth.net (Dennis Putnam) Date: Tue, 05 Jul 2011 18:44:42 -0400 Subject: [Mailman-Users] mailpasswds error In-Reply-To: References: Message-ID: <4E1393DA.8030708@bellsouth.net> My ISP occasionally, for unknown reasons, blocks email from python.org and apparently sometimes to python.org. Since I did not get a reply and I cannot find this in the archives, I am sending this again. If this is a double post, my apologies in advance. It turns out the RPM for 2.1.14 is not available yet for 2010. However, I reinstalled 2.1.13 and created the new list. Now I am on to the next layer of the onion. # ./config_list -i file dapmm real_name attribute not changed! It must differ from the list's name by case only. On 7/1/2011 3:47 PM, Mark Sapiro wrote: > Dennis Putnam wrote: >> Thanks. Mandrivia strikes again. I guess I need figure out how to >> upgrade to 2.1.14. > > You could try bin/newlist. That might work. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Wed Jul 6 02:49:02 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 5 Jul 2011 17:49:02 -0700 Subject: [Mailman-Users] mailpasswds error In-Reply-To: <4E1393DA.8030708@bellsouth.net> Message-ID: Dennis Putnam wrote: > >My ISP occasionally, for unknown reasons, blocks email from python.org >and apparently sometimes to python.org. Since I did not get a reply and >I cannot find this in the archives, I am sending this again. If this is >a double post, my apologies in advance. This entire thread including the prior post of the following begins at . I don't know why you couldn't find it. >It turns out the RPM for 2.1.14 is not available yet for 2010. However, >I reinstalled 2.1.13 and created the new list. Now I am on to the next >layer of the onion. > ># ./config_list -i file dapmm >real_name attribute not > changed! It must differ from the list's name by case > only. So you are trying to configure the new site list 'dapmm' using the configuration in 'file'. Presumably 'file' is the output from something like bin/config_list -o file mailman and contains a line like real_name = 'Mailman' Either remove that line or change it to something like real_name = 'DAPmm' where the value differs only in case from 'dapmm'. However, you really don't need to do anything because config_list already applied all the other changes. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rfox at irex.org Wed Jul 6 14:39:33 2011 From: rfox at irex.org (rfox) Date: Wed, 6 Jul 2011 05:39:33 -0700 (PDT) Subject: [Mailman-Users] Pending messages queue empty In-Reply-To: References: <31976331.post@talk.nabble.com> Message-ID: <32004573.post@talk.nabble.com> Got it, mailman is not listserv. Thank you for the correction. Any specific help for my issue? Mark Sapiro-3 wrote: > > rfox wrote: >> >>I am encountering a strange issue with our listserv > > > Please see . > > >>which I hope someone can >>shed some light on. The administrator/moderator of the list gets a message >>saying that there is a post pending approval. However, when he logs inand >>clicks "Tend to pending moderator requests" there is nothing there. >>Basically we keep getting "pending" notices but the queue is empty. It had >>been working and no settings were changed. > > > See the FAQ at . > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com > > -- View this message in context: http://old.nabble.com/Pending-messages-queue-empty-tp31976331p32004573.html Sent from the Mailman - Users mailing list archive at Nabble.com. From mailman-admin at uni-konstanz.de Wed Jul 6 14:43:57 2011 From: mailman-admin at uni-konstanz.de (Mailman Admin) Date: Wed, 06 Jul 2011 14:43:57 +0200 Subject: [Mailman-Users] Pending messages queue empty In-Reply-To: <32004573.post@talk.nabble.com> References: <31976331.post@talk.nabble.com> <32004573.post@talk.nabble.com> Message-ID: <4E14588D.8010206@uni-konstanz.de> Hi On 07/06/2011 02:39 PM, rfox wrote: > > Got it, mailman is not listserv. Thank you for the correction. > > Any specific help for my issue? > Did you read the following? > Mark Sapiro-3 wrote: >> >> >> See the FAQ at . >> Bye Christian Mack From khamilton at umem.org Tue Jul 5 22:23:22 2011 From: khamilton at umem.org (kphamilton) Date: Tue, 5 Jul 2011 13:23:22 -0700 (PDT) Subject: [Mailman-Users] Mailman MySQL backend migration question Message-ID: <32000121.post@talk.nabble.com> Hello, I am attempting to migrate from using Mailman's flat file to store information about members towards a MySQL database backend instead. I have successfully configured it so that when I add a new member or change a member, it changes appropriately with the database table. The problem is that I have 1500+ people who already exist within the flat file and have preferences stored in that file. I need to migrate the data from the flat file to the mySQL database so that all of the preferences are preserved. I have looked a little bit into .json files and importing the information in that manner, but I have not found a solution that works for me. Does anyone have any advice for me on this one? Thanks in advance! -Kevin -- View this message in context: http://old.nabble.com/Mailman-MySQL-backend-migration-question-tp32000121p32000121.html Sent from the Mailman - Users mailing list archive at Nabble.com. From mark at msapiro.net Wed Jul 6 14:46:00 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 06 Jul 2011 05:46:00 -0700 Subject: [Mailman-Users] Pending messages queue empty In-Reply-To: <32004573.post@talk.nabble.com> References: <31976331.post@talk.nabble.com> <32004573.post@talk.nabble.com> Message-ID: <615a5ab1-598e-47ad-a080-0d6f9eda555e@email.android.com> rfox wrote: >Any specific help for my issue? Did you see this FAQ? >Mark Sapiro-3 wrote: >> >> See the FAQ at . -- Mark Sapiro Sent from my Android phone with K-9 Mail. Please excuse my brevity. From mark at msapiro.net Thu Jul 7 03:43:06 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Jul 2011 18:43:06 -0700 Subject: [Mailman-Users] Mailman MySQL backend migration question In-Reply-To: <32000121.post@talk.nabble.com> Message-ID: kphamilton wrote: > >I am attempting to migrate from using Mailman's flat file to store >information about members towards a MySQL database backend instead. I have >successfully configured it so that when I add a new member or change a >member, it changes appropriately with the database table. The problem is >that I have 1500+ people who already exist within the flat file and have >preferences stored in that file. I need to migrate the data from the flat >file to the mySQL database so that all of the preferences are preserved. I am guessing that by 'flat file' you mean membership data as stored in the list object by the default OldStyleMemberships.py member adaptor. >I have looked a little bit into .json files and importing the information in >that manner, but I have not found a solution that works for me. > >Does anyone have any advice for me on this one? Again, assuming you have done this in the 'normal' way and have implemented a replacement MemberAdaptor such as one of the MysqlMemberships.py MemberAdaptors from or , I suggest you create a withlist script similar to the following outline. ------------------------------------------------------------ from Mailman import mm_cfg from Mailman import OldStyleMemberships as OSM def move_members(mlist): if not mlist.Locked(): mlist.Lock() for member in OSM.getMembers(mlist): if mlist.isMember(member): continue cpmember = OSM.getMemberCPAddress(mlist, member) digest = OSM.getMemberOption(mlist, member, mm_cfg.Digests) password = OSM.getMemberPassword(mlist, member) language = OSM.getMemberLanguage(mlist, member) realname = OSM.getMemberName(mlist, member) mlist.addNewMember(cpmember, digest=digest, password=password, language=language, realname=realname) mlist.setDeliveryStatus(member, OSM.getDeliveryStatus(mlist, member)) for flag in (mm_cfg.DontReceiveOwnPosts, mm_cfg.AcknowledgePosts, mm_cfg.DisableMime, mm_cfg.ConcealSubscription, mm_cfg.SuppressPasswordReminder, mm_cfg.ReceiveNonmatchingTopics, mm_cfg.Moderate, mm_cfg.DontReceiveDuplicates, ): mlist.setMemberOption(member, flag, OSM.getMemberOption(mlist, member, flag)) mlist.setMemberTopics(member, OSM.getMemberTopics(mlist, member)) OSM.removeMember(mlist, member) mlist.Save() mlist.Unlock() ------------------------------------------------------------ The above intentionally does not move bounce_info, but could if desired. The OSM.removeMember(mlist, member) is optional and assumes that none of this data is used. If you don't do it, the list's config.pck will still retain all this information which unnecessarily increases its size an potentially causes confusion The script isn't too robust. Probably at a minimum, everything from for member ... through mlist.Save() should be in a try: finally: with the mlist.Unlock() in the finally:. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 7 03:55:43 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Jul 2011 18:55:43 -0700 Subject: [Mailman-Users] Mailman MySQL backend migration question In-Reply-To: Message-ID: Mark Sapiro wrote: > >------------------------------------------------------------ >from Mailman import mm_cfg >from Mailman import OldStyleMemberships as OSM > >def move_members(mlist): > if not mlist.Locked(): > mlist.Lock() > for member in OSM.getMembers(mlist): > if mlist.isMember(member): > continue > cpmember = OSM.getMemberCPAddress(mlist, member) > digest = OSM.getMemberOption(mlist, member, mm_cfg.Digests) > password = OSM.getMemberPassword(mlist, member) > language = OSM.getMemberLanguage(mlist, member) > realname = OSM.getMemberName(mlist, member) > mlist.addNewMember(cpmember, digest=digest, password=password, > language=language, realname=realname) > mlist.setDeliveryStatus(member, > OSM.getDeliveryStatus(mlist, member)) > for flag in (mm_cfg.DontReceiveOwnPosts, > mm_cfg.AcknowledgePosts, > mm_cfg.DisableMime, > mm_cfg.ConcealSubscription, > mm_cfg.SuppressPasswordReminder, > mm_cfg.ReceiveNonmatchingTopics, > mm_cfg.Moderate, > mm_cfg.DontReceiveDuplicates, > ): > mlist.setMemberOption(member, flag, > OSM.getMemberOption(mlist, member, flag)) > mlist.setMemberTopics(member, > OSM.getMemberTopics(mlist, member)) > OSM.removeMember(mlist, member) > mlist.Save() > mlist.Unlock() >------------------------------------------------------------ I forgot to note that the above was untested and without warranty. In particular, the last two lines mlist.Save() mlist.Unlock() should only be indented 4 spaces, not 8 as in mlist.Save() mlist.Unlock() That change will at least give it a chance of processing more than one old member before dying. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khamilton at umem.org Thu Jul 7 04:13:35 2011 From: khamilton at umem.org (kphamilton) Date: Wed, 6 Jul 2011 19:13:35 -0700 (PDT) Subject: [Mailman-Users] Mailman MySQL backend migration question In-Reply-To: References: <32000121.post@talk.nabble.com> Message-ID: <32009929.post@talk.nabble.com> I have actually accomplished this! Woohoo! I did upgrade as you said to MysqlMemberships.py. I accomplished the rest in a different manner than you suggested, so I will share if others attempt this. I used export in the /bin folder to export all list data in xml format. I then wrote a python script that parsed through the xml file for each list and added appropriate members to the appropriate MySQL table. This proved to be fairly tricky as some of the attributes in the tables are not actually what are used to store the information (mostly dealing with the preferences). While there are fields in the tables for preferences like nomail, ack, plain, etc, these are unused fields. The field that controls most of the preferences is user_options. Thanks to a few tutorials (I am at home now so I do not have any URLs from work), I was able to decipher the values required to save preferences. Although I used a different strategy, I thank you Mark Sapiro for your attempted help. You actually did help me on this project because you were the poster in a lot of the tutorials I referenced throughout the process. Thanks again! -Kevin Mark Sapiro-3 wrote: > > Mark Sapiro wrote: >> >>------------------------------------------------------------ >>from Mailman import mm_cfg >>from Mailman import OldStyleMemberships as OSM >> >>def move_members(mlist): >> if not mlist.Locked(): >> mlist.Lock() >> for member in OSM.getMembers(mlist): >> if mlist.isMember(member): >> continue >> cpmember = OSM.getMemberCPAddress(mlist, member) >> digest = OSM.getMemberOption(mlist, member, mm_cfg.Digests) >> password = OSM.getMemberPassword(mlist, member) >> language = OSM.getMemberLanguage(mlist, member) >> realname = OSM.getMemberName(mlist, member) >> mlist.addNewMember(cpmember, digest=digest, password=password, >> language=language, realname=realname) >> mlist.setDeliveryStatus(member, >> OSM.getDeliveryStatus(mlist, member)) >> for flag in (mm_cfg.DontReceiveOwnPosts, >> mm_cfg.AcknowledgePosts, >> mm_cfg.DisableMime, >> mm_cfg.ConcealSubscription, >> mm_cfg.SuppressPasswordReminder, >> mm_cfg.ReceiveNonmatchingTopics, >> mm_cfg.Moderate, >> mm_cfg.DontReceiveDuplicates, >> ): >> mlist.setMemberOption(member, flag, >> OSM.getMemberOption(mlist, member, flag)) >> mlist.setMemberTopics(member, >> OSM.getMemberTopics(mlist, member)) >> OSM.removeMember(mlist, member) >> mlist.Save() >> mlist.Unlock() >>------------------------------------------------------------ > > > I forgot to note that the above was untested and without warranty. In > particular, the last two lines > > mlist.Save() > mlist.Unlock() > > should only be indented 4 spaces, not 8 as in > > mlist.Save() > mlist.Unlock() > > That change will at least give it a chance of processing more than one > old member before dying. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com > > -- View this message in context: http://old.nabble.com/Mailman-MySQL-backend-migration-question-tp32000121p32009929.html Sent from the Mailman - Users mailing list archive at Nabble.com. From egon at frerich.eu Wed Jul 6 20:37:35 2011 From: egon at frerich.eu (Egon Frerich) Date: Wed, 06 Jul 2011 20:37:35 +0200 Subject: [Mailman-Users] mails to lists are passed erroneously to cyrus Message-ID: <4E14AB6F.3040109@frerich.eu> My Postfix is on an host without a real Internet hostname. So the domain name in my main.cf is a fake: myhostname = Cup.freu.ih mydestination = Cup, $myhostname, localhost.$mydomain, $mydomain, localhost Mailman-lists are managed with a real domain name. In main.cf I say: virtual_alias_domains = schwach.de virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman mailman_destination_recipient_limit = 1 transport_maps = hash:/etc/postfix/transport I put 'virtual-mailman' into alias_maps too: alias_maps = hash:/var/lib/mailman/data/virtual-mailman, hash:/etc/aliases transport contains: schwach.de mailman: In master.cf there is an entry: mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} The list is called 'v'. If I send a mail to v at schwach.de via my local email account mailman delivers the mail to the list members. But if I send this mail via an external email account then the mail is handled by cyrus and I get this message: verify_user(user.fetchmail) failed: Mailbox does not exist Why is the email handled by cyrus? Thanks for any help. Egon Frerich -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature URL: From listown at nanniandjack.com Wed Jul 6 19:53:01 2011 From: listown at nanniandjack.com (Jack G F Hill) Date: Wed, 06 Jul 2011 13:53:01 -0400 Subject: [Mailman-Users] Monthly mailing of password hints Message-ID: <4E14A0FD.9010008@nanniandjack.com> We encountered a situation that felt like an error, but probably is not... User is set to NoMail while he moves from one place (and one ISP) to another... no current (working) email address... The system continues to try sending password reminders, which bounce and cause the hosting owner to be concerned about mail errors... Ought mailman (2.1.14) continue sending out password reminders to a "NoMail" subscriber? Is there a setting I can get to to stop the reminders until he returns? I couldn't find it if such a switch exists for list admins... -- Jack Hill, W4KH - BoatAnchors Listowner/Archiver listown at nanniandjack.com "Plus ca change, plus c'est la meme chose" "Il n'y a que les idiots qui ne changent jamais d'idee" From mark at msapiro.net Thu Jul 7 08:11:46 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 06 Jul 2011 23:11:46 -0700 Subject: [Mailman-Users] mails to lists are passed erroneously to cyrus In-Reply-To: <4E14AB6F.3040109@frerich.eu> References: <4E14AB6F.3040109@frerich.eu> Message-ID: <4E154E22.6070709@msapiro.net> On 7/6/2011 11:37 AM, Egon Frerich wrote: > > If I send a mail to v at schwach.de via my local email account mailman > delivers the mail to the list members. > > But if I send this mail via an external email account then the mail is > handled by cyrus and I get this message: > > verify_user(user.fetchmail) failed: Mailbox does not exist > > Why is the email handled by cyrus? Presumably because the MX for the schwach.de domain in DNS is mail.schwach.de whose IP address is 87.230.26.25 and this is not the IP address of your Postfix/Mailman machine. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 7 08:15:34 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 06 Jul 2011 23:15:34 -0700 Subject: [Mailman-Users] Monthly mailing of password hints In-Reply-To: <4E14A0FD.9010008@nanniandjack.com> References: <4E14A0FD.9010008@nanniandjack.com> Message-ID: <4E154F06.3000107@msapiro.net> On 7/6/2011 10:53 AM, Jack G F Hill wrote: > We encountered a situation that felt like an error, but probably is not... > > User is set to NoMail while he moves from one place (and one ISP) to > another... no current (working) email address... > > The system continues to try sending password reminders, which bounce and > cause the hosting owner to be concerned about mail errors... > > Ought mailman (2.1.14) continue sending out password reminders to a > "NoMail" subscriber? Yes. "NoMail" only controls delivery of list messages/digests, not password reminders. > Is there a setting I can get to to stop the reminders until he returns? > I couldn't find it if such a switch exists for list admins... In the Membership Management... -> Membership List pages, click this members email address which will take you to the user's options page where you can change the "Get password reminder email for this list?" setting to No. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From egon at frerich.eu Thu Jul 7 09:39:10 2011 From: egon at frerich.eu (Egon Frerich) Date: Thu, 07 Jul 2011 09:39:10 +0200 Subject: [Mailman-Users] mails to lists are passed erroneously to cyrus In-Reply-To: <4E154E22.6070709@msapiro.net> References: <4E14AB6F.3040109@frerich.eu> <4E154E22.6070709@msapiro.net> Message-ID: <4E15629E.4080005@frerich.eu> Am 07.07.2011 08:11, schrieb Mark Sapiro: > On 7/6/2011 11:37 AM, Egon Frerich wrote: >> >> If I send a mail to v at schwach.de via my local email account mailman >> delivers the mail to the list members. >> >> But if I send this mail via an external email account then the mail is >> handled by cyrus and I get this message: >> >> verify_user(user.fetchmail) failed: Mailbox does not exist >> >> Why is the email handled by cyrus? > > > Presumably because the MX for the schwach.de domain in DNS is > mail.schwach.de whose IP address is 87.230.26.25 and this is not the IP > address of your Postfix/Mailman machine. > Thank you. But can you explain the matter a little more. schwach.de is hosted by an ISP. The ISP collects the mails with its mail server. My machine fetches the mails via POP3. So my machine gets the mails. Postfix should control that mails from the domain schwach.de are passed to mailman, from other domains are passed to cyrus. Is not this controlle by the file /etc/postfix/transport ? Egon Frerich -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature URL: From glen at prideaux.id.au Thu Jul 7 15:55:24 2011 From: glen at prideaux.id.au (Glen Prideaux) Date: Thu, 7 Jul 2011 21:55:24 +0800 Subject: [Mailman-Users] mails to lists are passed erroneously to cyrus In-Reply-To: References: Message-ID: <2D1CB832-8173-4033-8C4E-39B70B4659BF@prideaux.id.au> >> Presumably because the MX for the schwach.de domain in DNS is >> mail.schwach.de whose IP address is 87.230.26.25 and this is not the IP >> address of your Postfix/Mailman machine. >> > > Thank you. But can you explain the matter a little more. > > schwach.de is hosted by an ISP. The ISP collects the mails with its mail > server. My machine fetches the mails via POP3. So my machine gets the > mails. Postfix should control that mails from the domain schwach.de are > passed to mailman, from other domains are passed to cyrus. Is not this > controlle by the file /etc/postfix/transport ? > > Egon Frerich It's a bit hard to be sure from your explanation, but this is what I think is happening. When you send mail from your machine to v at schwach.de, your machine deals with the mail correctly and it goes straight to mailman. This suggests that if the message gets to your machine it should be correctly handled. But when you send from another machine, it works like this: source machine does a DNS lookup for the MX for schwach.de and finds mail.schwach.de->87.230.26.25 source machine talks to mail.schwach.de, "I have a message for v at schwach.de" mail.schwach.de does not know about the list you have set up on your server so replies "Mailbox does not exist". Thus the message never gets to your server. The error message does not come from your server, it comes from your ISP's server at mail.schwach.de. In order to fix this, you need to arrange with your ISP for it to recognise v at mail.schwach.de as a valid address, perhaps as an alias for your regular mail account. It may be simpler to register an Internet domain name for your server (perhaps using a service like no-ip.com if you don't have a static IP address) and have the mail delivered directly to your server and not go through your ISP's mail host at all. Glen From mark at msapiro.net Thu Jul 7 17:07:12 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 Jul 2011 08:07:12 -0700 Subject: [Mailman-Users] mails to lists are passed erroneously to cyrus In-Reply-To: <4E14AB6F.3040109@frerich.eu> References: <4E14AB6F.3040109@frerich.eu> Message-ID: <4E15CBA0.30304@msapiro.net> My earlier reply may have been a bit hasty, and I'm not sure if Glen Prideaux's reply has the correct reason or not (I have tried sending a test mail, but so far, mail.schwach.de has not accepted my server's connection. Anyway, if Glen is correct, you not only need v at schwach.de to be deliverable at mail.schwach.de, but also addresses like v-bounces at schwach.de, v-confirm at schwach.de, v-request at schwach.de, v-owner at schwach.de, etc. In any case, there are problems with your postfix setup and I want some information. Egon Frerich wrote: > My Postfix is on an host without a real Internet hostname. So the domain > name in my main.cf is a fake: > > myhostname = Cup.freu.ih > mydestination = Cup, $myhostname, localhost.$mydomain, $mydomain, localhost > > Mailman-lists are managed with a real domain name. In main.cf I say: > > virtual_alias_domains = schwach.de > virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman The above two lines are irrelevant. > mailman_destination_recipient_limit = 1 > transport_maps = hash:/etc/postfix/transport > > I put 'virtual-mailman' into alias_maps too: > > alias_maps = hash:/var/lib/mailman/data/virtual-mailman, hash:/etc/aliases Fortunately, this too is irrelevant because it is wrong. I would like to know why you did this because I have seen at least two other recent reports on this list of this being done, and if there is some documentation that says to do it, I'd like to see it corrected. What should be in alias_maps is hash:/var/lib/mailman/data/aliases, but not in your case because ... > transport contains: > > schwach.de mailman: > > In master.cf there is an entry: > > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} You are using postfix-to-mailman.py to deliver all mail to the schwach.de domain to Mailman so the alias_maps, virtual_alias_maps and virtual_alias_domains entries for this domain are not required or used. > The list is called 'v'. > > If I send a mail to v@ via my local email account mailman > delivers the mail to the list members. > > But if I send this mail via an external email account then the mail is > handled by cyrus and I get this message: > > verify_user(user.fetchmail) failed: Mailbox does not exist > > Why is the email handled by cyrus? It looks to me, based on your followup clarification and the above that fetchmail retrieves the mail from mail.schwach.de and delivers it, to your local Postfix, but it first does user verification of some kind which fails. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 7 18:56:18 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Jul 2011 09:56:18 -0700 Subject: [Mailman-Users] Mailman MySQL backend migration question In-Reply-To: <32009929.post@talk.nabble.com> Message-ID: kphamilton wrote: > >I have actually accomplished this! Woohoo! I did upgrade as you said to >MysqlMemberships.py. > >I accomplished the rest in a different manner than you suggested, so I will >share if others attempt this. > >I used export in the /bin folder to export all list data in xml format. But you must have somehow disabled the use of MysqlMemberships.py as the MemberAdaptor for the running of bin/export.py or you would have only gotten those members and settings that were already in the MySQL database since bin/export.py uses the list's MemberAdaptor methods to retrieve these things. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khamilton at umem.org Thu Jul 7 19:02:42 2011 From: khamilton at umem.org (kphamilton) Date: Thu, 7 Jul 2011 10:02:42 -0700 (PDT) Subject: [Mailman-Users] Mailman MySQL backend migration question In-Reply-To: References: <32000121.post@talk.nabble.com> <32009929.post@talk.nabble.com> Message-ID: <32014980.post@talk.nabble.com> I used the bin/export before I added the extend.py to any of the lists and it retrieved all of the necessary information. Mark Sapiro-3 wrote: > > kphamilton wrote: >> >>I have actually accomplished this! Woohoo! I did upgrade as you said to >>MysqlMemberships.py. >> >>I accomplished the rest in a different manner than you suggested, so I will >>share if others attempt this. >> >>I used export in the /bin folder to export all list data in xml format. > > > But you must have somehow disabled the use of MysqlMemberships.py as > the MemberAdaptor for the running of bin/export.py or you would have > only gotten those members and settings that were already in the MySQL > database since bin/export.py uses the list's MemberAdaptor methods to > retrieve these things. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com > > -- View this message in context: http://old.nabble.com/Mailman-MySQL-backend-migration-question-tp32000121p32014980.html Sent from the Mailman - Users mailing list archive at Nabble.com. From dap1 at bellsouth.net Thu Jul 7 19:44:52 2011 From: dap1 at bellsouth.net (Dennis Putnam) Date: Thu, 07 Jul 2011 13:44:52 -0400 Subject: [Mailman-Users] mailpasswds error In-Reply-To: References: Message-ID: <4E15F094.8060204@bellsouth.net> Thanks for the reply. I ran the test message and what I got back was nothing like what you suggested. It was simply the message, in tact, as if it was a simple relay. There was nothing in the bounce log either. Obviously there is still something wrong but where do I go from here? On 7/6/2011 8:28 PM, Mark Sapiro wrote: > Dennis Putnam wrote: >> Thanks for the reply, however I'm a little confused by it. I did indeed >> run 'config_list -o file mailman' first. Are you saying that the import >> was already done and the '-i' command is unnecessary? > > No. I'm saying that when you ran 'bin/config_list -i file dapmm' all > the settings in 'file' were successfully applied except for the one > > real_name = ' Mailman' > > setting which you didn't want anyway. > > >> There is nothing >> in the Wiki article that indicated that your suggested edit is necessary. > > I'll update the wiki as soon as the licensing innue that prevents me > from doing so at the moment is resolved. > > >> In any case I've sent the password reminder messages and they were all >> processed by Postfix as before. I guess now I have to see if anything >> comes back although I know already that the message to my own address >> should have arrived by now. I did verify that 'dapmm-bounces' was the >> 'From:' address on the outgoing messages. > > Did you verify the the outgoing MTA relayed the message(s)? > > >> Will I screw anything up if I send a test message to 'dapmm-bounces' and >> what should I expect as result? > > No. Assuming Bounce processing -> > bounce_unrecognized_goes_to_list_owner is Yes, an ordinary email test > message to dapmm-bounces that doesn't look like a DSN should be > forwarded to the owner address(es) of the dapmm list. In any case, > there should be a message like > > Jul 05 10:46:31 2011 (23530) dapmm: bounce message w/no discernable > addresses: > > and if forwarding, one like > > Jul 05 10:46:31 2011 (23530) dapmm: forwarding unrecognized, > message-id: > > in Mailman's bounce log. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Thu Jul 7 19:51:58 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Jul 2011 10:51:58 -0700 Subject: [Mailman-Users] Mailman MySQL backend migration question In-Reply-To: <32014980.post@talk.nabble.com> Message-ID: kphamilton wrote: > >I used the bin/export before I added the extend.py to any of the lists and it >retrieved all of the necessary information. OK. That makes sense. BTW, just for curiousity, I actually tried a partial test on the withlist suggestion I posted, and I found problems. In case anyone finds this in the archives and wants to try it, here's a script that will be a little closer to working. ------------------------------------------------------------ from Mailman import mm_cfg from Mailman.OldStyleMemberships import OldStyleMemberships def move_members(mlist): OSM = OldStyleMemberships(mlist) if not mlist.Locked(): mlist.Lock() for member in OSM.getMembers(): if mlist.isMember(member): continue cpmember = OSM.getMemberCPAddress(member) digest = OSM.getMemberOption(member, mm_cfg.Digests) password = OSM.getMemberPassword(member) language = OSM.getMemberLanguage(member) realname = OSM.getMemberName(member) mlist.addNewMember(cpmember, digest=digest, password=password, language=language, realname=realname) mlist.setDeliveryStatus(member, OSM.getDeliveryStatus(member)) for flag in (mm_cfg.DontReceiveOwnPosts, mm_cfg.AcknowledgePosts, mm_cfg.DisableMime, mm_cfg.ConcealSubscription, mm_cfg.SuppressPasswordReminder, mm_cfg.ReceiveNonmatchingTopics, mm_cfg.Moderate, mm_cfg.DontReceiveDuplicates, ): mlist.setMemberOption(member, flag, OSM.getMemberOption(member, flag)) mlist.setMemberTopics(member, OSM.getMemberTopics(member)) OSM.removeMember(member) mlist.Save() mlist.Unlock() ------------------------------------------------------------ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Jul 7 20:31:37 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 07 Jul 2011 11:31:37 -0700 Subject: [Mailman-Users] mailpasswds error In-Reply-To: <4E15F094.8060204@bellsouth.net> References: <4E15F094.8060204@bellsouth.net> Message-ID: <4E15FB89.1000602@msapiro.net> On 7/7/2011 10:44 AM, Dennis Putnam wrote: > Thanks for the reply. I ran the test message and what I got back was > nothing like what you suggested. It was simply the message, in tact, as > if it was a simple relay. There was nothing in the bounce log either. > Obviously there is still something wrong but where do I go from here? It's probably OK. I forgot that site list bounces are handled differently. The message, whether an actual DSN or not is simply relayed to the owner of the site list with envelope from and Errors-To: and maybe Sender: headers containing the sitelist-loop address. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From listown at nanniandjack.com Thu Jul 7 22:15:55 2011 From: listown at nanniandjack.com (Jack G F Hill) Date: Thu, 07 Jul 2011 16:15:55 -0400 Subject: [Mailman-Users] Monthly mailing of password hints In-Reply-To: <4E154F06.3000107@msapiro.net> References: <4E14A0FD.9010008@nanniandjack.com> <4E154F06.3000107@msapiro.net> Message-ID: <4E1613FB.2050603@nanniandjack.com> Thanks Mark... It was the path to individual member pages for changing settings that I somehow missed... -- Jack Hill, W4KH - BoatAnchors Listowner/Archiver listown at nanniandjack.com "Plus ca change, plus c'est la meme chose" "Il n'y a que les idiots qui ne changent jamais d'idee" On 07/07/2011 02:15 AM, Mark Sapiro wrote: > On 7/6/2011 10:53 AM, Jack G F Hill wrote: > >> Is there a setting I can get to to stop the reminders until he returns? >> I couldn't find it if such a switch exists for list admins... >> > > In the Membership Management... -> Membership List pages, click this > members email address which will take you to the user's options page > where you can change the "Get password reminder email for this list?" > setting to No. > From ken at sunward.org Sun Jul 10 02:45:57 2011 From: ken at sunward.org (Ken Winter) Date: Sat, 9 Jul 2011 20:45:57 -0400 Subject: [Mailman-Users] Rerouting "announce" replies to "talk" automatically Message-ID: <0192F8DB3DDF4879BF4858DAE36DBD3F@KenIBM> I'm trying to set up "announce" and "talk" lists for a neighborhood group. Let's say the addresses of these are announce at my.group and talk at my.group. As usual, "announce" is to be a one-way, no-reply list. I want replies addressed to "announce" to be automatically rerouted to "talk". Following the advice at http://wiki.list.org/pages/viewpage.action?pageId=4030685, I have set these under the announce at my.group General Options: 1. "first_strip_reply_to": Yes 2. "reply_goes_to_list": Explicit address 3. "reply_to_address": talk at my.group 4. "include_list_post_header": No Everything works fine, except when the recipient of an announce message hits reply-to-all. Then the "To:" line of the mail client is populated as talk at my.group; announce at my.group. So the reply goes back to the "announce" list as well as to "talk". Is there any way to set up the "announce" list so that reply-to-all does not include announce at my.group, or is that purely controlled by the mail client? (List members are not techies, and I have no control over the type and settings of the email clients they use.) If I can't stop the reply-to-all from going back to "announce", is there any way to set up "announce" so it recognizes these replies and automatically discards them? (It will not work to just reject emails from list members, since all of them are authorized to send messages to the list.) ~ Thanks in advance ~ Ken From mark at msapiro.net Sun Jul 10 03:35:21 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 9 Jul 2011 18:35:21 -0700 Subject: [Mailman-Users] Rerouting "announce" replies to "talk" automatically In-Reply-To: <0192F8DB3DDF4879BF4858DAE36DBD3F@KenIBM> Message-ID: Ken Winter wrote: > >1. "first_strip_reply_to": Yes > >2. "reply_goes_to_list": Explicit address > >3. "reply_to_address": talk at my.group > >4. "include_list_post_header": No > >Everything works fine, except when the recipient of an announce message hits >reply-to-all. Then the "To:" line of the mail client is populated as >talk at my.group; announce at my.group. So the reply goes back to the "announce" >list as well as to "talk". Is there any way to set up the "announce" list >so that reply-to-all does not include announce at my.group, or is that purely >controlled by the mail client? (List members are not techies, and I have no >control over the type and settings of the email clients they use.) Your settings are pretty much the best you can do. The explicit Reply-To: will override the From: as the reply address, but reply-all will generally include the To: which is the announce list, and may even, depending on the mail client, include the From: >If I can't stop the reply-to-all from going back to "announce", is there any >way to set up "announce" so it recognizes these replies and automatically >discards them? (It will not work to just reject emails from list members, >since all of them are authorized to send messages to the list.) Yes. On the announce list, set up a Privacy options... -> Spam filters -> header_filter_rules rule with an action of Discard and the following regexp ^(To:|Cc:).*[ <]talk at my\.group([, >]|$) This will match any To: or Cc: header containing the talk at my.group address and will thus discard any post received by the announce list that was also addressed to the talk list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ken at sunward.org Sun Jul 10 05:34:27 2011 From: ken at sunward.org (Ken Winter) Date: Sat, 9 Jul 2011 23:34:27 -0400 Subject: [Mailman-Users] Rerouting "announce" replies to "talk" automatically In-Reply-To: Message-ID: Thank you, Mark!! ~ It worked! I set up your spam rule, set it to "Reject" matching messages, then tried to reply-to-all to an "announce" message. I've never been so happy to receive a response saying "Message rejected by filter rule match"! And my reply was delivered to the "talk" list with no problem. Then I set the anti-spam action to "Discard". Now Mailman smoothly reroutes the reply-to-all to "talk" and silently discards the one addressed to "announce", exactly as desired. One more nice thing: "Announce" is a moderated list (for messages from all members). But the spam-filter trick doesn't even bother the moderator with a "post requires approval" when the post is an unwanted reply. Perfect. ~ Thanks again ~ Ken > -----Original Message----- > From: Mark Sapiro [mailto:mark at msapiro.net] > Sent: Saturday, July 09, 2011 9:35 PM > To: ken at sunward.org; Mailman Users List > Subject: Re: [Mailman-Users] Rerouting "announce" replies to "talk" > automatically > > Ken Winter wrote: > > > >1. "first_strip_reply_to": Yes > > > >2. "reply_goes_to_list": Explicit address > > > >3. "reply_to_address": talk at my.group > > > >4. "include_list_post_header": No > > > >Everything works fine, except when the recipient of an announce message > hits > >reply-to-all. Then the "To:" line of the mail client is populated as > >talk at my.group; announce at my.group. So the reply goes back to the > "announce" > >list as well as to "talk". Is there any way to set up the "announce" > list > >so that reply-to-all does not include announce at my.group, or is that > purely > >controlled by the mail client? (List members are not techies, and I have > no > >control over the type and settings of the email clients they use.) > > > Your settings are pretty much the best you can do. The explicit > Reply-To: will override the From: as the reply address, but reply-all > will generally include the To: which is the announce list, and may > even, depending on the mail client, include the From: > > > >If I can't stop the reply-to-all from going back to "announce", is there > any > >way to set up "announce" so it recognizes these replies and automatically > >discards them? (It will not work to just reject emails from list > members, > >since all of them are authorized to send messages to the list.) > > > Yes. On the announce list, set up a Privacy options... -> Spam filters > -> header_filter_rules rule with an action of Discard and the > following regexp > > ^(To:|Cc:).*[ <]talk at my\.group([, >]|$) > > This will match any To: or Cc: header containing the talk at my.group > address and will thus discard any post received by the announce list > that was also addressed to the talk list. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From ken at sunward.org Sun Jul 10 22:36:44 2011 From: ken at sunward.org (Ken Winter) Date: Sun, 10 Jul 2011 16:36:44 -0400 Subject: [Mailman-Users] Moderator forwarding from "announce" list to "talk" list Message-ID: Here's a second question about how to set up "announce" and "talk" lists for a neighborhood group. (For the first question and answer, see http://www.mail-archive.com/mailman-users at python.org/msg59493.html.) Let's say the addresses of these are announce at my.group and talk at my.group. The "announce" list is moderated. Frequently, the moderator's reason for rejecting a post is that it is an expression of opinions rather than factual information, and as such is appropriate to the "talk" list rather than the "announce" list. So the goal here is to enable the moderator to reroute the message from "announce" to "talk". Many of my users - and those who send the most inappropriate posts - are not technically savvy and not easily educated, and I have no control over their email clients or how they are configured, so a scheme that minimizes the demands on them is essential here. Here is the only way I have found to forward messages within Mailman: On the "Posting Held for Approval" form, enter: * Action: Reject * Additionally, forward this message to: talk at my.group (check the check-box) * If you reject this post, please explain (optional): This method presents these problems: 1. The "From:" address of the forwarded message, when it arrives at talk at my.group, is announce-bounces at my.group, rather than the original sender. So replies to the "talk" message will go back to announce-bounces at my.group (which sends a useless "Uncaught bounce notification" message back to the moderator), whereas the need to go back to the sender. So the question here is: How to set the "From:" (or "Reply-To:") address of the forwarded message to the address of the original sender? 2. When the forwarded message shows up in a "talk" member's mailbox, its Subject: line is always "Forward of moderated message". Every word of that headline is going to be meaningless to my non-techy users! The need here is to put the original sender's original headline in the "Subject:" line of the forwarded message. 3. In Outlook (2002), the body shows up as an attachment; either the header or the footer shows up as the message body. My non-techy users have barely mastered opening attachments, even when the body of the message refers to them; they're never going to find the body if it's hidden in an attachment. Gmail presents the message OK. These are the only two clients I've tried. 4. If the first three problems can't be solved, a fallback possibility would be just to reject the message from announce, and put into the rejection message the suggestion that the user resend the message to talk at my.group. This would work much better for my non-tech users if their original message were attached to the rejection message, so they could just open the attachment and forward it to the suggested address. This would at least spare them from having to search in their "sent items" folder for the message to resend. In short: The requirement here is to get inappropriate messages to "announce" forwarded to "talk" in such a way that the original sender's address and subject line appear in the "From:" and "Subject:" fields, respectively - and to do this in a way that minimizes the skills required of my user community. ~ Thanks in advance ~ Ken From mark at msapiro.net Mon Jul 11 00:02:32 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 10 Jul 2011 15:02:32 -0700 Subject: [Mailman-Users] Moderator forwarding from "announce" list to "talk"list In-Reply-To: Message-ID: Ken Winter wrote: > >In short: The requirement here is to get inappropriate messages to >"announce" forwarded to "talk" in such a way that the original sender's >address and subject line appear in the "From:" and "Subject:" fields, >respectively - and to do this in a way that minimizes the skills required of >my user community. This is anywhere from trivial (albeit a bit cumbersome) to nearly impossible depending on your MUA (mail client). The forwarding process actually wraps the original message as a message/rfc822 body of the forwarded message. Another way of looking at this is it attaches the original message to an empty message to the recipient. If you forward the held message to yourself, some MUAs will allow you to open the original message, edit the To: header from 'announce' to 'talk' and resend the edited original to the talk list. Other MUAs may allow saving the message to a file which can the be edited down to the original message with the To: header changed and then resent to the talk list. Another way to get the original message is from the notice to the admin of the held message if admin_immed_notify is Yes. Assuming you don't have shell access to the Mailman server, all of this depends on your having some way to resend (some MUAs call it 'bounce') a message. Without that, there is no way short of modifying Mailman source code to forward a held message in the way you would want. If you do have shell access to the Mailman server you could use a combination of sed and mailman's command line tools in a shell script to do get the held message, edit it, post it to the talk list and discard the original. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Steven.Jones at vuw.ac.nz Mon Jul 11 09:33:31 2011 From: Steven.Jones at vuw.ac.nz (Steven Jones) Date: Mon, 11 Jul 2011 07:33:31 +0000 Subject: [Mailman-Users] Is there a Command to extract the lists owners? Message-ID: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> I need to email each list owner to let them know the server will be off line while I upgrade it, so I need their email addresses. regards From odhiambo at gmail.com Mon Jul 11 11:15:29 2011 From: odhiambo at gmail.com (Odhiambo Washington) Date: Mon, 11 Jul 2011 12:15:29 +0300 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> References: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> Message-ID: On Mon, Jul 11, 2011 at 10:33, Steven Jones wrote: > I need to email each list owner to let them know the server will be off > line while I upgrade it, so I need their email addresses. > A poor man's way: You just need to know the listname and append -owner to it, like mailman-users-owner. ./bin/list_lists | grep -v '^[0-9]' | awk '{print $1"-owner@$domain"}' Replace $domain with a sane value. If there are several different domains on this site, then wait for someone else to advise:) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email. From s.watkins at nhm.ac.uk Mon Jul 11 11:27:46 2011 From: s.watkins at nhm.ac.uk (Steff Watkins) Date: Mon, 11 Jul 2011 10:27:46 +0100 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> References: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> Message-ID: <8A17F10FEBA5C841956578C5AD9027D301AF38C9@HOMER.nhm.ac.uk> > I need to email each list owner to let them know the server > will be off line while I upgrade it, so I need their email addresses. > > regards Hi, bin/list_owners will give you a list of the email addresses of all your lists owners, one email addres at a time. If you add the -m option, you also get all the moderators email addresses also. Simples! :) Steff ----- From odhiambo at gmail.com Mon Jul 11 11:36:41 2011 From: odhiambo at gmail.com (Odhiambo Washington) Date: Mon, 11 Jul 2011 12:36:41 +0300 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: <8A17F10FEBA5C841956578C5AD9027D301AF38C9@HOMER.nhm.ac.uk> References: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> <8A17F10FEBA5C841956578C5AD9027D301AF38C9@HOMER.nhm.ac.uk> Message-ID: On Mon, Jul 11, 2011 at 12:27, Steff Watkins wrote: > > I need to email each list owner to let them know the server > > will be off line while I upgrade it, so I need their email addresses. > > > > regards > > Hi, > > bin/list_owners will give you a list of the email addresses of all your > lists owners, one email addres at a time. If you add the -m option, you > also get all the moderators email addresses also. > > Simples! :) > > Steff > > Perhaps it would be nice if this command also listed the listname against the owners? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email. From s.watkins at nhm.ac.uk Mon Jul 11 12:00:44 2011 From: s.watkins at nhm.ac.uk (Steff Watkins) Date: Mon, 11 Jul 2011 11:00:44 +0100 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: References: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> <8A17F10FEBA5C841956578C5AD9027D301AF38C9@HOMER.nhm.ac.uk> Message-ID: <8A17F10FEBA5C841956578C5AD9027D301BAF67D@HOMER.nhm.ac.uk> > -----Original Message----- > From: Odhiambo Washington [mailto:odhiambo at gmail.com] > Sent: Monday, July 11, 2011 10:37 AM > To: Steff Watkins > Cc: Mailman Users List > Subject: Re: [Mailman-Users] Is there a Command to extract > the lists owners? > > > > On Mon, Jul 11, 2011 at 12:27, Steff Watkins > wrote: > > > > I need to email each list owner to let them know the server > > will be off line while I upgrade it, so I need their > email addresses. > > > > regards > > Perhaps it would be nice if this command also listed the > listname against the owners? It does. Use the -w option. This stuff is really easy to find out about. Just trying running the command with an option of '--help' . If the command doesn't recognise the option it will usually complain and stop working so no damage done there. However if the command (and I'm talking generally about unixy sort of commands, not just Mailman in particular).. If the command does recognise the '--help' option it wil... give you help! The '-h' option is usually good for this as well. If you're really tetchy about supplying unknown options to random binaries then do the operation as a standard or restricted user. Then you minimise the potential for any damage you might do. Simples! :) Steff ----- From bsfinkel at anl.gov Mon Jul 11 15:59:35 2011 From: bsfinkel at anl.gov (Barry Finkel) Date: Mon, 11 Jul 2011 08:59:35 -0500 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> References: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> Message-ID: <4E1B01C7.3010902@anl.gov> On 07/11/11 02:33, Steven Jones wrote: > I need to email each list owner to let them know the server will be off line > while I upgrade it, so I need their email addresses. I have a Mailman list named mailman-list-owners just for this purpose. I have a cron that is run every two hours to keep the membership current. mailman# cat sync_owners.exec #!/bin/csh # shell script to synchronize the mailman-list-owners subscribers # When (how often) do we run this script? # 11May09 0248PM Barry Finkel # Synchronize silently: # file is stdin (-f -) # no Welcome message (-w=no) # no goodby message (-g=no) # no digest mode (-d=no) # no admin notify (-a=no) /usr/lib/mailman/bin/list_owners | \ /usr/lib/mailman/bin/sync_members -f - -w=no -g=no -d=no -a=no \ mailman-list-owners mailman# When I see a new owner, I send him/her e-mail pointing to our internal wiki where I have information for Mailman list owners. -- ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 240, Room 5.B.8 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From kwise at novell.com Mon Jul 11 20:38:47 2011 From: kwise at novell.com (KC Wise) Date: Mon, 11 Jul 2011 12:38:47 -0600 Subject: [Mailman-Users] Different Domains on Single Mailman Server In-Reply-To: <4E1B01C7.3010902@anl.gov> References: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> <4E1B01C7.3010902@anl.gov> Message-ID: <4E1AEED7020000C90006C854@novprvoes0310.provo.novell.com> Inherited a few mailman servers. I was wanting to know if I can combine them into a single server/instance. My issue is that they are not subdomains they are completely different domain names for example: something.org lists.somethingelse.com lists.different2.com Just wanted to make sure that something like this will work before I proceed. Thanks for your time, KC Wise From mark at msapiro.net Tue Jul 12 03:22:52 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2011 18:22:52 -0700 Subject: [Mailman-Users] Different Domains on Single Mailman Server In-Reply-To: <4E1AEED7020000C90006C854@novprvoes0310.provo.novell.com> Message-ID: KC Wise wrote: > >Inherited a few mailman servers. I was wanting to know if I can combine >them into a single server/instance. >My issue is that they are not subdomains they are completely different >domain names for example: >something.org >lists.somethingelse.com >lists.different2.com > >Just wanted to make sure that something like this will work before I >proceed. It will work with standard GNU Mailman in a single instance if all list names are globally unique. If you have need of lists with the same name in different domains, there are some unofficial sets of patches available, or you can run multiple Mailman instances on the one server, but you can expect some minor grief in getting it to work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jul 12 03:27:20 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2011 18:27:20 -0700 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: Message-ID: Odhiambo Washington wrote: > >A poor man's way: You just need to know the listname and append -owner to >it, like mailman-users-owner. > >./bin/list_lists | grep -v '^[0-9]' | awk '{print $1"-owner@$domain"}' Or ./bin/list_lists --bare | awk '{print $1"-owner@$domain"}' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jul 12 03:33:32 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Jul 2011 18:33:32 -0700 Subject: [Mailman-Users] Is there a Command to extract the lists owners? In-Reply-To: <833D8E48405E064EBC54C84EC6B36E402F0C9EF4@STAWINCOX10MBX1.staff.vuw.ac.nz> Message-ID: Steven Jones wrote: >I need to email each list owner to let them know the server will be off line while I upgrade it, so I need their email addresses. There are two commands. bin/list_owners has already been mentioned and there is also bin/list_admins for a somewhat different output format. Give either command with the --help option for details. Also see the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rosenbaumlm at ornl.gov Tue Jul 12 16:09:42 2011 From: rosenbaumlm at ornl.gov (Rosenbaum, Larry M.) Date: Tue, 12 Jul 2011 10:09:42 -0400 Subject: [Mailman-Users] Different Domains on Single Mailman Server In-Reply-To: References: <4E1AEED7020000C90006C854@novprvoes0310.provo.novell.com> Message-ID: > From: mailman-users-bounces+rosenbaumlm=ornl.gov at python.org > [mailto:mailman-users-bounces+rosenbaumlm=ornl.gov at python.org] On Behalf > Of Mark Sapiro > > KC Wise wrote: > > > >Inherited a few mailman servers. I was wanting to know if I can combine > >them into a single server/instance. > >My issue is that they are not subdomains they are completely different > >domain names for example: > >something.org > >lists . somethingelse . com > >lists . different2 . com > > > >Just wanted to make sure that something like this will work before I > >proceed. > > > It will work with standard GNU Mailman in a single instance if all list > names are globally unique. If you have need of lists with the same Could you point me to the documentation on implementing virtual domains where the list names are globally unique? Thanks, Larry From ltymowski at gmail.com Tue Jul 12 16:28:47 2011 From: ltymowski at gmail.com (Luke Tymowski) Date: Tue, 12 Jul 2011 08:28:47 -0600 Subject: [Mailman-Users] Mail to some lists works, bounces for others Message-ID: Hello, We have a number of mailing lists that are member-only. On most of the lists, users can post successfully. But on others, even though people attempting to post are members, or in one case the list owner, their mail is rejected. "550 5.1.1 Recipient address rejected: User unknown" There are no lock files for a particular list. The only files in /var/lib/mailman/locks are master-qrunner and master-qrunner.mailman.2502 (The dates on those two files are more than 24 hours into the future - is that normal?) The /var/lib/mailman/data/aliases shows the relevant aliases for that particular list. Mailman version: 2.1.13 OS: Ubuntu 10.04.2 MTA: Postfix 2.7.0 thanks, Luke From mark at msapiro.net Tue Jul 12 19:36:12 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2011 10:36:12 -0700 Subject: [Mailman-Users] Different Domains on Single Mailman Server In-Reply-To: Message-ID: Rosenbaum, Larry M. wrote: > >Could you point me to the documentation on implementing virtual domains where the list names are globally unique? This involves both Mailman and the MTA. It may or may not involve the web server depending on whether the web server's Mailman related directives are global or per domain. The Mailman side is relatively simple. See the section headed ##### # Virtual domains ##### in Defaults.py. Basically you just need an add_virtualhost('web_host', 'email_host') line in mm_cfg.py for each virtual host. For the Postfix MTA see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Jul 12 19:44:22 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2011 10:44:22 -0700 Subject: [Mailman-Users] Mail to some lists works, bounces for others In-Reply-To: Message-ID: Luke Tymowski wrote: > >We have a number of mailing lists that are member-only. On most of the lists, users can post successfully. > >But on others, even though people attempting to post are members, or in one case the list owner, their mail is rejected. >"550 5.1.1 Recipient address rejected: User unknown" > >There are no lock files for a particular list. Locks are not relevant to this issue as Mailman never sees the attempted posts. >The only files in /var/lib/mailman/locks are master-qrunner and master-qrunner.mailman.2502 >(The dates on those two files are more than 24 hours into the future - is that normal?) Yes, the timestamps on the master-qrunner locks are in the future. That is the time at which the lock expires. >The /var/lib/mailman/data/aliases shows the relevant aliases for that particular list. And has the /var/lib/mailman/data/aliases.db file been updated since those aliases were added? In fact does Postfix even use those aliases? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ltymowski at gmail.com Tue Jul 12 21:23:02 2011 From: ltymowski at gmail.com (Luke Tymowski) Date: Tue, 12 Jul 2011 13:23:02 -0600 Subject: [Mailman-Users] Mail to some lists works, bounces for others In-Reply-To: References: Message-ID: Hello, > And has the /var/lib/mailman/data/aliases.db file been updated since > those aliases were added? What confused me was that these are all lists that have been around for the last 6-7 years. I moved the lists to a new server 2 weeks ago. Most of the lists worked just fine. So, yes, the aliases.db exists and was regenerated when I moved the lists to the new server. > In fact does Postfix even use those aliases? Well, most of the lists worked, but some didn't. I'd think if Postfix didn't know about those aliases, none of the lists would work (it's the only place where the list handlers are kept). I fixed the issue by editing /etc/mailman/mm_cfg and changing: MTA=none to MTA='Postfix' Then running /var/lib/mailman/bin/genaliases Mailman/Postfix were installed from apt-get. Luke From mark at msapiro.net Wed Jul 13 01:24:07 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 12 Jul 2011 16:24:07 -0700 Subject: [Mailman-Users] Mail to some lists works, bounces for others In-Reply-To: Message-ID: Luke Tymowski wrote: > >I fixed the issue by editing /etc/mailman/mm_cfg and changing: >MTA=none >to >MTA='Postfix' > >Then running /var/lib/mailman/bin/genaliases > >Mailman/Postfix were installed from apt-get. So there was some problem with the aliases. Either they weren't in /var/lib/mailman/data/aliases or /var/lib/mailman/data/aliases.db was not properly synced with /var/lib/mailman/data/aliases, because, assuming virtual mappings are not involved, that's the only thing that would be affected by the things above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From s.watkins at nhm.ac.uk Wed Jul 13 11:38:12 2011 From: s.watkins at nhm.ac.uk (Steff Watkins) Date: Wed, 13 Jul 2011 10:38:12 +0100 Subject: [Mailman-Users] Mail to some lists works, bounces for others In-Reply-To: References: Message-ID: <8A17F10FEBA5C841956578C5AD9027D301BAF8C8@HOMER.nhm.ac.uk> > -----Original Message----- > From: mailman-users-bounces+s.watkins=nhm.ac.uk at python.org > [mailto:mailman-users-bounces+s.watkins=nhm.ac.uk at python.org] > On Behalf Of Luke Tymowski > Sent: Tuesday, July 12, 2011 8:23 PM > Subject: Re: [Mailman-Users] Mail to some lists works, > bounces for others > > Hello, > .... > What confused me was that these are all lists that have been around > for the last 6-7 years. > > I moved the lists to a new server 2 weeks ago. > Most of the lists worked just fine. > .... > Mailman/Postfix were installed from apt-get. So Mailman on the new server has been installed using apt-get. Then you moved your list files/directories from the old server to the new server? My Sysadmin-sense[tm] is tingling. I get the feeling that either the permissions of some of the files/directories are not correct or, and this is a biggie when moving servers, the "ownership" of those files/directories may no longer be correct. Are there any warnings about access permissions showing up in the systems logfiles? Try running the bin/check_perms scripts to check that your files and directories have the right permissions. Alternatively, login to your Mailman server, change to the mailman directory and try something like: ls -lR | grep -v MAILMAN-UNAME | less replacing MAILMAN-UNAME with your Mailman username (probably 'mailman' but not guaranteed). Check an eye open for any files that have ended up in there that are not owned by your mailman software. Good luck, Steff ----- From pennguin at mac.com Fri Jul 15 16:08:04 2011 From: pennguin at mac.com (Rob) Date: Fri, 15 Jul 2011 10:08:04 -0400 Subject: [Mailman-Users] Message approval by mail Message-ID: <016FC82B-7802-4F69-ADEB-05AEC897FFCE@mac.com> I am trying to use the option to approve moderated messages using the 'reply' feature but it doesn't seem to work for me. I add the Approved: header to my reply as the first line in the body, but the message simply arrives back in my inbox unmodified, and the moderated message stays in the queue until I approve it with the web interface. Running v2.1.14 Thanks, -Rob An example of an outgoing 'approval' message is below: Return-Path: Received: from murder ([unix socket]) by acvr.org (Cyrus v2.3.8-OS X Server 10.5: 9G7013y) with LMTPA; Fri, 15 Jul 2011 10:03:46 -0400 X-Sieve: CMU Sieve 2.3 Received: from xserve.petrad.com (localhost [127.0.0.1]) by acvr.org (Postfix) with ESMTP id DE73783962E for ; Fri, 15 Jul 2011 10:03:46 -0400 (EDT) X-Original-To: xservetestlist-owner at acvr.org Delivered-To: xservetestlist-owner at acvr.org Received: from [192.168.42.17] (office.petrad.com [173.12.22.82]) by acvr.org (Postfix) with ESMTP id A6DE7839623 for ; Fri, 15 Jul 2011 10:03:45 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Xservetestlist post from mclear at petrad.com requires approval From: "Robert C. McLear, ACVR Treasurer" In-Reply-To: Date: Fri, 15 Jul 2011 10:03:45 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: To: xservetestlist-owner at acvr.org X-Mailer: Apple Mail (2.1084) Errors-To: mailman-bounces at acvr.org Sender: mailman-bounces at acvr.org Approved:******** On Jul 15, 2011, at 10:02 AM, xservetestlist-owner at acvr.org wrote: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: Xservetestlist at acvr.org > From: mclear at petrad.com > Subject: test > Reason: Post to moderated list > > At your convenience, visit: > > http://www.acvr.org/mailman/admindb/xservetestlist > > to approve or deny the request. > > From: Robert McLear > Date: July 15, 2011 10:02:02 AM EDT > To: xservetestlist at acvr.org > Subject: test > > > test > > > > From: xservetestlist-request at acvr.org > Date: July 15, 2011 10:02:09 AM EDT > Subject: confirm dda15190a0e5ffa59d0894b92f7a9efface6b70b > > > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. Do this if the message is > spam. If you reply to this message and include an Approved: header > with the list password in it, the message will be approved for posting > to the list. The Approved: header can also appear in the first line > of the body of the reply. From mark at msapiro.net Fri Jul 15 18:19:52 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2011 09:19:52 -0700 Subject: [Mailman-Users] Message approval by mail In-Reply-To: <016FC82B-7802-4F69-ADEB-05AEC897FFCE@mac.com> Message-ID: Rob wrote: >I am trying to use the option to approve moderated messages using the 'reply' feature but it doesn't seem to work for me. I add the Approved: header to my reply as the first line in the body, but the message simply arrives back in my inbox unmodified, and the moderated message stays in the queue until I approve it with the web interface. Running v2.1.14 > >Thanks, > >-Rob > >An example of an outgoing 'approval' message is below: > >Return-Path: >Received: from murder ([unix socket]) > by acvr.org (Cyrus v2.3.8-OS X Server 10.5: 9G7013y) with LMTPA; > Fri, 15 Jul 2011 10:03:46 -0400 >X-Sieve: CMU Sieve 2.3 >Received: from xserve.petrad.com (localhost [127.0.0.1]) > by acvr.org (Postfix) with ESMTP id DE73783962E > for ; Fri, 15 Jul 2011 10:03:46 -0400 (EDT) >X-Original-To: xservetestlist-owner at acvr.org >Delivered-To: xservetestlist-owner at acvr.org >Received: from [192.168.42.17] (office.petrad.com [173.12.22.82]) > by acvr.org (Postfix) with ESMTP id A6DE7839623 > for ; > Fri, 15 Jul 2011 10:03:45 -0400 (EDT) >Content-Type: text/plain; charset=us-ascii >Mime-Version: 1.0 (Apple Message framework v1084) >Subject: Xservetestlist post from mclear at petrad.com requires approval >From: "Robert C. McLear, ACVR Treasurer" >In-Reply-To: >Date: Fri, 15 Jul 2011 10:03:45 -0400 >Content-Transfer-Encoding: 7bit >Message-Id: >References: >To: xservetestlist-owner at acvr.org >X-Mailer: Apple Mail (2.1084) >Errors-To: mailman-bounces at acvr.org >Sender: mailman-bounces at acvr.org > >Approved:******** Your problem is you are replying to the held message notice itself so your reply is sent to xservetestlist-owner at acvr.org with Subject: Xservetestlist post from mclear at petrad.com requires approval. That reply is just sent back to the list owner. The message to which you replied is a multipart message with 3 parts. The part below is an attached message/rfc822 part. >> From: xservetestlist-request at acvr.org >> Date: July 15, 2011 10:02:09 AM EDT >> Subject: confirm dda15190a0e5ffa59d0894b92f7a9efface6b70b >> >> >> If you reply to this message, keeping the Subject: header intact, >> Mailman will discard the held message. Do this if the message is >> spam. If you reply to this message and include an Approved: header >> with the list password in it, the message will be approved for posting >> to the list. The Approved: header can also appear in the first line >> of the body of the reply. You need to reply to the above attached message. Depending on your MUA, you may be able to open this as a separate message and reply to it. If you can't do this, you have to just compose a message To: xservetestlist-request at acvr.org with Subject: confirm dda15190a0e5ffa59d0894b92f7a9efface6b70b containing the Approved: ... line to accept the post or without the Approved: ... line to discard it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pennguin at mac.com Fri Jul 15 18:28:12 2011 From: pennguin at mac.com (Rob) Date: Fri, 15 Jul 2011 12:28:12 -0400 Subject: [Mailman-Users] Message approval by mail In-Reply-To: References: Message-ID: > > >>> From: xservetestlist-request at acvr.org >>> Date: July 15, 2011 10:02:09 AM EDT >>> Subject: confirm dda15190a0e5ffa59d0894b92f7a9efface6b70b >>> >>> >>> If you reply to this message, keeping the Subject: header intact, >>> Mailman will discard the held message. Do this if the message is >>> spam. If you reply to this message and include an Approved: header >>> with the list password in it, the message will be approved for posting >>> to the list. The Approved: header can also appear in the first line >>> of the body of the reply. > > > You need to reply to the above attached message. Depending on your MUA, > you may be able to open this as a separate message and reply to it. If > you can't do this, you have to just compose a message > > To: xservetestlist-request at acvr.org > > with > > Subject: confirm dda15190a0e5ffa59d0894b92f7a9efface6b70b > > containing the Approved: ... line to accept the post or without the > Approved: ... line to discard it. OK, now I understand. Apple Mail just displays the entire message together, not as separate parts. I can't reply directly but clicking the list-email address and just copy/pasting the subject works just as well. Thanks! -Rob From pennguin at mac.com Fri Jul 15 22:48:31 2011 From: pennguin at mac.com (Rob) Date: Fri, 15 Jul 2011 16:48:31 -0400 Subject: [Mailman-Users] Migrating content to a new list Message-ID: Hi, We have just created a new list in Mailman 2.1.14 to handle a specific set of discussions that were previously taking place on another list hosted on the same server. The membership of the new list is much broader than the old list, so many of its members have had no exposure to the recent discussions. Is there a way that I can use the archives of 'oldlist' and send out the past month's worth of discussions to 'newlist' so that the members are all up to date on the recent conversations? It's not feasible to just make the archives public because not all of the content is pertinent to all the members of 'newlist'. Thanks, -Rob From mark at msapiro.net Sat Jul 16 00:41:41 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Jul 2011 15:41:41 -0700 Subject: [Mailman-Users] Migrating content to a new list In-Reply-To: References: Message-ID: <4E20C225.8050106@msapiro.net> On 7/15/2011 1:48 PM, Rob wrote: > > We have just created a new list in Mailman 2.1.14 to handle a > specific set of discussions that were previously taking place on > another list hosted on the same server. The membership of the new > list is much broader than the old list, so many of its members have > had no exposure to the recent discussions. Is there a way that I can > use the archives of 'oldlist' and send out the past month's worth of > discussions to 'newlist' so that the members are all up to date on > the recent conversations? > > It's not feasible to just make the archives public because not all of > the content is pertinent to all the members of 'newlist'. I think there are two ways to handle this. Both involve making a copy of archives/private/oldlist.mbox/oldlist.mbox and editing it (or perhaps opening it with mutt or similar) and deleting those messages you don't want available on newlist. So you end up with a mailbox with only those posts you want available to newlist. Then, if there haven't yet been any posts to newlist, just save that mailbox as archives/private/newlist.mbox/newlist.mbox making sure it's group is the mailman group, and run 'bin/arch --wipe newlist' to seed the newlist archive with the old posts. Or, if there have been posts to newlist, combine the mailbox with archives/private/newlist.mbox/newlist.mbox and run 'bin/arch --wipe newlist' to add those posts to the newlist archive. If you want the newlist members to receive the posts by email, you can instead remail (bounce in mutt terms) the messages in the mailbox to newlist which will send them to the members and archive them. Before doing that, you might want to set oldlist in Privacy options... -> Recipient filters -> acceptable_aliases of newlist so the bounced posts won't be held. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From karitlaine at yahoo.com Fri Jul 15 20:47:12 2011 From: karitlaine at yahoo.com (Kari Laine) Date: Fri, 15 Jul 2011 11:47:12 -0700 (PDT) Subject: [Mailman-Users] mails go missing Message-ID: <1310755632.91728.YahooMailClassic@web120419.mail.ne1.yahoo.com> Hi, this is my first post to this list. I am GoDaddy customer. I am setting site at http://opensourceug.net where you can test the lists. Problem is that when I register to a list I don't always get a confirmation mail. Sometimes I get it sometimes not. If I try to register several times it some times like wakes up and I get several at the same time. I am at the hold to godaddy support at this time.? Any ideas? Is is just GoDaddy .... Best RegardsKari Laine From mark at msapiro.net Sat Jul 16 18:27:53 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 16 Jul 2011 09:27:53 -0700 Subject: [Mailman-Users] mails go missing In-Reply-To: <1310755632.91728.YahooMailClassic@web120419.mail.ne1.yahoo.com> References: <1310755632.91728.YahooMailClassic@web120419.mail.ne1.yahoo.com> Message-ID: <4E21BC09.1010005@msapiro.net> On 7/15/2011 11:47 AM, Kari Laine wrote: > Hi, this is my first post to this list. I am GoDaddy customer. I am > setting site at http://opensourceug.net where you can test the > lists. And it appears that this mailman installation may be cPanel. If so, see the FAQ at . > Problem is that when I register to a list I don't always get a > confirmation mail. Sometimes I get it sometimes not. If I try to > register several times it some times like wakes up and I get several > at the same time. I am at the hold to godaddy support at this time. > Any ideas? Is is just GoDaddy .... Best RegardsKari Laine In order to even begin to diagnose this, you need access to both Mailman's logs and the MTA's (probably exim if it is cPanel) logs on the host server. In addition to the above, you may find the FAQs at and to be relevant. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dandrews at visi.com Sat Jul 16 23:20:23 2011 From: dandrews at visi.com (David Andrews) Date: Sat, 16 Jul 2011 16:20:23 -0500 Subject: [Mailman-Users] Odd Subscriptions Message-ID: Hi: Has anyone seen anything like this and what does it mean. I run a server with about 150 public mailman lists on it, and just got about 300 new subscriptions to various public lists, from the same domain at the same time. It is "apot.com" and the form is firstname dot lastname at apot.com and the first and last names are all different but believable. Is this like the zeusmail.com subscriptions a while back, I got a bunch, but never knew what they were about. Dave From Ralf.Hildebrandt at charite.de Sun Jul 17 19:21:23 2011 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Sun, 17 Jul 2011 19:21:23 +0200 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: References: Message-ID: <20110717172123.GF5720@charite.de> * David Andrews : > Hi: > > Has anyone seen anything like this and what does it mean. I run a > server with about 150 public mailman lists on it, and just got about > 300 new subscriptions to various public lists, from the same domain > at the same time. It is "apot.com" and the form is firstname dot > lastname at apot.com and the first and last names are all different > but believable. Is this like the zeusmail.com subscriptions a while > back, I got a bunch, but never knew what they were about. Kill them all. Happened here with apotmail.com as well. -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From Ralf.Hildebrandt at charite.de Sun Jul 17 19:22:00 2011 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Sun, 17 Jul 2011 19:22:00 +0200 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: References: Message-ID: <20110717172200.GG5720@charite.de> * David Andrews : > Hi: > > Has anyone seen anything like this and what does it mean. I run a > server with about 150 public mailman lists on it, and just got about > 300 new subscriptions to various public lists, from the same domain > at the same time. It is "apot.com" and the form is firstname dot > lastname at apot.com and the first and last names are all different > but believable. Is this like the zeusmail.com subscriptions a while > back, I got a bunch, but never knew what they were about. >From 209.190.19.68 ? -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From mark at msapiro.net Sun Jul 17 19:35:57 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 Jul 2011 10:35:57 -0700 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: References: Message-ID: <4E231D7D.1020608@msapiro.net> On 7/16/2011 2:20 PM, David Andrews wrote: > > Has anyone seen anything like this and what does it mean. I run a > server with about 150 public mailman lists on it, and just got about 300 > new subscriptions to various public lists, from the same domain at the > same time. It is "apot.com" and the form is firstname dot lastname at > apot.com and the first and last names are all different but believable. > Is this like the zeusmail.com subscriptions a while back, I got a bunch, > but never knew what they were about. It's answerpot archiving your lists. In my case, they sent an email to the owner of one list about a week before with links to opt-in immediately or opt-out with the no response default being opt-in after a week with no response. I didn't respond, set the list's subscribe police to approve and waited. The interesting thing is I have a few advertised lists, some active, and the only one they targeted was effectively dormant. All the lists have private archives. I eventually got a couple of subscription requests from addresses similar to what you describe at apotmail.com. I discarded the requests and added ^.*[@.]apotmail\.com$ to the ban list of all my lists. Perhaps I'll change that to ^.*[@.]apot(mail)?\.com$ based on what you saw. Interestingly, the names answerpot.com, apotmail.com and mail.apotmail.com all map to the same IP while apot.com maps to a different IP which is apparently a reseller - "The domain apot.com is for sale. To purchase, call BuyDomains.com". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Ralf.Hildebrandt at charite.de Sun Jul 17 19:38:01 2011 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Sun, 17 Jul 2011 19:38:01 +0200 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: <4E231D7D.1020608@msapiro.net> References: <4E231D7D.1020608@msapiro.net> Message-ID: <20110717173801.GC7135@charite.de> * Mark Sapiro : > It's answerpot archiving your lists. Aha. > In my case, they sent an email to the owner of one list about a week > before with links to opt-in immediately or opt-out with the no response > default being opt-in after a week with no response. I didn't respond, > set the list's subscribe police to approve and waited. > > The interesting thing is I have a few advertised lists, some active, and > the only one they targeted was effectively dormant. All the lists have > private archives. > > I eventually got a couple of subscription requests from addresses > similar to what you describe at apotmail.com. I discarded the requests > and added > > ^.*[@.]apotmail\.com$ > > to the ban list of all my lists. Perhaps I'll change that to > > ^.*[@.]apot(mail)?\.com$ > > based on what you saw. Would be cool if you could do that on mail.python.org as well! -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From mark at msapiro.net Sun Jul 17 20:53:39 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 Jul 2011 11:53:39 -0700 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: <20110717173801.GC7135@charite.de> References: <4E231D7D.1020608@msapiro.net> <20110717173801.GC7135@charite.de> Message-ID: <4E232FB3.4070107@msapiro.net> On 7/17/2011 10:38 AM, Ralf Hildebrandt wrote: > * Mark Sapiro : >> I eventually got a couple of subscription requests from addresses >> similar to what you describe at apotmail.com. I discarded the requests >> and added >> >> ^.*[@.]apotmail\.com$ >> >> to the ban list of all my lists. Perhaps I'll change that to >> >> ^.*[@.]apot(mail)?\.com$ >> >> based on what you saw. > > Would be cool if you could do that on mail.python.org as well! I think you can do it much more easily than I. I could only do it on mail.python.org one list at a time via the web interface. There is a script at (and mirrored at ) which can be saved in Mailman's bin/ directory and then run via bin/withlist -a -r add_banned -- '^.*[@.]apot(mail)?\.com$' to add that re to the ban_list of all lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jul 17 21:09:37 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 Jul 2011 12:09:37 -0700 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: <4E231D7D.1020608@msapiro.net> Message-ID: Mark Sapiro wrote: > >I eventually got a couple of subscription requests from addresses >similar to what you describe at apotmail.com. I discarded the requests >and added > >^.*[@.]apotmail\.com$ > >to the ban list of all my lists. When I wrote the amove, I hadn't seen my mmdsr report from yesterday. Yesterday (actually, today, July 17, 04:44 -0000) I had 6 banned subscription requests (2 each on 3 lists) from First.last at apotmail.com addresses. This time, there was no advance email. Their getting bolder and even less scrupulous. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Ralf.Hildebrandt at charite.de Sun Jul 17 21:14:05 2011 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Sun, 17 Jul 2011 21:14:05 +0200 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: References: <4E231D7D.1020608@msapiro.net> Message-ID: <20110717191405.GG7135@charite.de> > When I wrote the amove, I hadn't seen my mmdsr report from yesterday. > Yesterday (actually, today, July 17, 04:44 -0000) I had 6 banned > subscription requests (2 each on 3 lists) from First.last at apotmail.com > addresses. This time, there was no advance email. Their getting bolder > and even less scrupulous. Yeah, same on python.org -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From adam-mailman at amyl.org.uk Sun Jul 17 21:21:06 2011 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Sun, 17 Jul 2011 20:21:06 +0100 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: <4E232FB3.4070107@msapiro.net> References: <4E231D7D.1020608@msapiro.net> <20110717173801.GC7135@charite.de> <4E232FB3.4070107@msapiro.net> Message-ID: <20110717192106.GU4223@hendricks.amyl.org.uk> On Sun, Jul 17, 2011 at 11:53:39AM -0700, Mark Sapiro wrote: > bin/withlist -a -r add_banned -- '^.*[@.]apot(mail)?\.com$' Thanks for the heads-up. Only hit one of the five sets of lists I maintain, but still killed off. -- "Jim Hacker: What appalling cynicism." "Sir Humphrey: We call it diplomacy, Minister." From pennguin at mac.com Sun Jul 17 21:27:27 2011 From: pennguin at mac.com (Rob) Date: Sun, 17 Jul 2011 15:27:27 -0400 Subject: [Mailman-Users] Migrating content to a new list In-Reply-To: <4E20C225.8050106@msapiro.net> References: <4E20C225.8050106@msapiro.net> Message-ID: <2A10413B-4EB7-48AA-A69D-D39AEB6026D3@mac.com> On Jul 15, 2011, at 6:41 PM, Mark Sapiro wrote: > > On 7/15/2011 1:48 PM, Rob wrote: > > > I think there are two ways to handle this. Both involve making a copy of > archives/private/oldlist.mbox/oldlist.mbox and editing it (or perhaps > opening it with mutt or similar) and deleting those messages you don't > want available on newlist. So you end up with a mailbox with only those > posts you want available to newlist. > > Then, if there haven't yet been any posts to newlist, just save that > mailbox as archives/private/newlist.mbox/newlist.mbox making sure it's > group is the mailman group, and run 'bin/arch --wipe newlist' to seed > the newlist archive with the old posts. Or, if there have been posts to > newlist, combine the mailbox with > archives/private/newlist.mbox/newlist.mbox and run 'bin/arch --wipe > newlist' to add those posts to the newlist archive. Mark, That worked, thanks. -Rob From mark at msapiro.net Sun Jul 17 22:41:06 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 Jul 2011 13:41:06 -0700 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: Message-ID: David Andrews wrote: > >So, at the risk of seeming stupid, what is it that they are trying to >do, or doing. Are they collecting addresses for spam, or what? If I >don't ask, I won't learn. As I said in my original reply, "It's answerpot archiving your lists." They are subscribing to your lists in order to collect list posts for their archive. See their web site for more info. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jul 17 23:25:26 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 17 Jul 2011 14:25:26 -0700 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: Message-ID: David Andrews wrote: > >Is there any reason >to not let them do this? I think they are unscrupulous. I think that no one should archive any list without an affirmative opt-in request from the list owner. Further, my lists which answerpot has attempted to archive all have private archives. For someone to attempt to subscribe to such a list for the purpose of publicly archiving list posts is just plain wrong. >My sponsoring organization is involved in a >lot of public education kinds of things, and want to get the word >out. Is there a negative, or spam risk, or something to letting them >archive? You'd have to look at their existing archives and decide for yourself. It appears that they hide email addresses, but I don't know how thoroughly. The main thing for me is I consider them to be unscrupulous for not requiring positive opt-in and for attempting to archive lists whose archives are not public. I would not want to support their practices and their ad revenue with my list's content, even if that content were otherwise publicly archived.. >And ... finally, why do they need multiple subscribes to >the same list? Who knows? Maybe to increase the chances that at least one of the subscribe attempts will succeed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dandrews at visi.com Sun Jul 17 22:21:30 2011 From: dandrews at visi.com (David Andrews) Date: Sun, 17 Jul 2011 15:21:30 -0500 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: References: <4E231D7D.1020608@msapiro.net> Message-ID: At 02:09 PM 7/17/2011, Mark Sapiro wrote: >Mark Sapiro wrote: > > > >I eventually got a couple of subscription requests from addresses > >similar to what you describe at apotmail.com. I discarded the requests > >and added > > > >^.*[@.]apotmail\.com$ > > > >to the ban list of all my lists. > > >When I wrote the amove, I hadn't seen my mmdsr report from yesterday. >Yesterday (actually, today, July 17, 04:44 -0000) I had 6 banned >subscription requests (2 each on 3 lists) from First.last at apotmail.com >addresses. This time, there was no advance email. Their getting bolder >and even less scrupulous. So, at the risk of seeming stupid, what is it that they are trying to do, or doing. Are they collecting addresses for spam, or what? If I don't ask, I won't learn. Dave >-- >Mark Sapiro The highway is for gamblers, >San Francisco Bay Area, California better use your sense - B. Dylan From dandrews at visi.com Sun Jul 17 23:02:59 2011 From: dandrews at visi.com (David Andrews) Date: Sun, 17 Jul 2011 16:02:59 -0500 Subject: [Mailman-Users] Odd Subscriptions In-Reply-To: References: Message-ID: At 03:41 PM 7/17/2011, Mark Sapiro wrote: >David Andrews wrote: > > > >So, at the risk of seeming stupid, what is it that they are trying to > >do, or doing. Are they collecting addresses for spam, or what? If I > >don't ask, I won't learn. > > >As I said in my original reply, "It's answerpot >archiving your lists." They are subscribing to your lists in order to >collect list posts for their archive. See their web site for more info. You did say that and I just didn't check it out. Is there any reason to not let them do this? My sponsoring organization is involved in a lot of public education kinds of things, and want to get the word out. Is there a negative, or spam risk, or something to letting them archive? And ... finally, why do they need multiple subscribes to the same list? Sorry if I am asking to many questions -- I know you aren't their representative or defender. Dave From vm3112870680488272v at vmail.inf.h-brs.de Wed Jul 20 10:53:23 2011 From: vm3112870680488272v at vmail.inf.h-brs.de (Steffen Kaiser) Date: Wed, 20 Jul 2011 10:53:23 +0200 (CEST) Subject: [Mailman-Users] access scrubbed attachments of private lists without password? Message-ID: Dear all, is it possible to access scrubbed attachments of private lists without a password? Regards, -- Steffen Kaiser From mark at msapiro.net Wed Jul 20 16:53:59 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 Jul 2011 07:53:59 -0700 Subject: [Mailman-Users] access scrubbed attachments of private lists without password? In-Reply-To: References: Message-ID: <4E26EC07.3050107@msapiro.net> On 7/20/2011 1:53 AM, Steffen Kaiser wrote: > > is it possible to access scrubbed attachments of private lists without a > password? No. Scrubbed attachments are stored in the list's archive file hierarchy and have to be accessed as anything else in the list's archives. If the archive is private, this requires a password. Also, in general, it seems to me that if a list's archives are private, it would not be a good idea to make attachments to list posts publicly accessible. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vm3112870680488272v at vmail.inf.h-brs.de Fri Jul 22 16:23:11 2011 From: vm3112870680488272v at vmail.inf.h-brs.de (Steffen Kaiser) Date: Fri, 22 Jul 2011 16:23:11 +0200 (CEST) Subject: [Mailman-Users] access scrubbed attachments of private lists without password? In-Reply-To: References: Message-ID: On Thu, 21 Jul 2011, Mark Sapiro wrote: >On 7/20/2011 1:53 AM, Steffen Kaiser wrote: >> >> is it possible to access scrubbed attachments of private lists without a >> password? > > >No. Scrubbed attachments are stored in the list's archive file hierarchy >and have to be accessed as anything else in the list's archives. If the >archive is private, this requires a password. > >Also, in general, it seems to me that if a list's archives are private, >it would not be a good idea to make attachments to list posts publicly >accessible. That depends on the view :-) MIMEDefang (www.mimedefang.org) has a feature to replace attachments with links. The URLs are using a SHA1-based hash of the content of the file. The idea is: if someone gained access to the message, s/he would have access to the attachment, if it had not been removed. The URL is obscured in such a way, that one would need the content of the file to guess the URL to it. No need to protect the attachment any further. Or one could think of the SHA1-based URL as the password to the file. Such URL could look like: https://example.com/mailman/private/list/attachments/20110719/5d9da8c3/sha1hash.pdf or one uses: sha1hash/sanitisedFilename.pdf or something like that. Of course, I do not know how the Mailman password stuff works in detail, so one could place appropriate links into https://host/pipermail/list/ or yet another base path. Kind regards, -- Steffen Kaiser From gigahertz at fettabernett.de Fri Jul 22 13:32:26 2011 From: gigahertz at fettabernett.de (gigahertz at fettabernett.de) Date: Fri, 22 Jul 2011 13:32:26 +0200 Subject: [Mailman-Users] Problem with Mailman+Postfix Message-ID: <4E295FCA.1020309@fettabernett.de> Hi there. I?m using Postfix + Dovevot + Mailman on Debian Lenny with ISPConfig3 Setup. I?ve installed Mailman seperate from ISPConfig via apt-get, administrating lists works fine but there is one problem: Postfix does not accept incoming mails to the mailing list. mail.info: Jul 22 10:53:13 atom-29 postfix/smtpd[12620]: NOQUEUE: reject: RCPT from mailout-de.gmx.net[213.165.64.22]: 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table; from= to= proto=SMTP helo= main.cf of Postfix: # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = /usr/share/doc/postfix # TLS parameters smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_use_tls = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. myhostname = atom-29.ip-projects.de alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases myorigin = /etc/mailname mydestination = atom-29.ip-projects.de, localhost, localhost.localdomain relayhost = mynetworks = 127.0.0.0/8 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all html_directory = /usr/share/doc/postfix/html virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /var/vmail virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination smtpd_tls_security_level = may transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf relay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cf relay_recipient_maps = mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps smtpd_sender_restrictions = check_sender_access mysql:/etc/postfix/mysql-virtual_sender.cf smtpd_client_restrictions = check_client_access mysql:/etc/postfix/mysql-virtual_client.cf maildrop_destination_concurrency_limit = 1 maildrop_destination_recipient_limit = 1 virtual_transport = dovecot header_checks = regexp:/etc/postfix/header_checks mime_header_checks = regexp:/etc/postfix/mime_header_checks nested_header_checks = regexp:/etc/postfix/nested_header_checks body_checks = regexp:/etc/postfix/body_checks dovecot_destination_recipient_limit = 1 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth content_filter = amavis:[127.0.0.1]:10024 receive_override_options = no_address_mappings message_size_limit = 0 #Mailman owner_request_special = no What am I doing wrong? From mark at msapiro.net Fri Jul 22 20:41:44 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 22 Jul 2011 11:41:44 -0700 Subject: [Mailman-Users] Problem with Mailman+Postfix In-Reply-To: <4E295FCA.1020309@fettabernett.de> References: <4E295FCA.1020309@fettabernett.de> Message-ID: <4E29C468.6040901@msapiro.net> On 7/22/2011 4:32 AM, gigahertz at fettabernett.de wrote: > Hi there. > I?m using Postfix + Dovevot + Mailman on Debian Lenny with ISPConfig3 > Setup. > I?ve installed Mailman seperate from ISPConfig via apt-get, > administrating lists works fine but there is one problem: Postfix does > not accept incoming mails to the mailing list. > > mail.info: > Jul 22 10:53:13 atom-29 postfix/smtpd[12620]: NOQUEUE: reject: RCPT from > mailout-de.gmx.net[213.165.64.22]: 550 5.1.1 : Recipient > address rejected: User unknown in virtual mailbox table; > from= to= proto=SMTP helo= > > main.cf of Postfix: [...] > alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases > alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases [...] > virtual_alias_domains = > virtual_alias_maps = > proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, > mysql:/etc/postfix/mysql-virtual_email2email.cf > virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf > virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf [...] > > What am I doing wrong? 'postconf -n' is generally more useful than main.cf. It appears the problem is that your list domain is a virtual mailbox domain, but you have no virtual mapping for the list addresses. If that is indeed the problem, you need to add hash:/var/lib/mailman/data/virtual-mailman to virtual_alias_maps in main.cf. You also need to put your list domaian (xyz.net) in POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py as in POSTFIX_STYLE_VIRTUAL_DOMAINS = ['xyz.net'] and run Mailman's bin/genaliases to generate virtual-mailman. Also, you should not have hash:/var/lib/mailman/data/aliases because it will cause Postfix's newaliases command to rebuild hash:/var/lib/mailman/data/aliases.db which may adversely affect the owner:group of this file. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From michael.capelle at charter.net Sat Jul 23 18:29:16 2011 From: michael.capelle at charter.net (Michael Capelle) Date: Sat, 23 Jul 2011 11:29:16 -0500 Subject: [Mailman-Users] upgrading Mailman. Message-ID: <8C8A036A921C4959A0D629DE12589AED@michael849cd7d> Hello. I am trying to upgrade mailman, I am using Debian 5-04. I have mailman version 2.1.11. Do i need to use a dependency to update? thanks. Mike. From michael.capelle at charter.net Sun Jul 24 01:17:52 2011 From: michael.capelle at charter.net (Michael Capelle) Date: Sat, 23 Jul 2011 18:17:52 -0500 Subject: [Mailman-Users] upgrading Mailman. References: <8C8A036A921C4959A0D629DE12589AED@michael849cd7d> Message-ID: <5A72613502AA48E3A10DB3CB304A9403@michael849cd7d> I need to add, we are not using 5.0.4, we are using 5.0.8. Is there any dependencies we need to download? we have 2.1.11, and we want to upgrade to 2.1.15, we are using debian 5.0.8. thanks. ----- Original Message ----- From: "Michael Capelle" To: Cc: Sent: Saturday, July 23, 2011 11:29 AM Subject: [Mailman-Users] upgrading Mailman. > Hello. > I am trying to upgrade mailman, I am using Debian 5-04. I have mailman > version 2.1.11. Do i need to use a dependency to update? > thanks. > Mike. > > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/michael.capelle%40charter.net > From mark at msapiro.net Sun Jul 24 03:35:31 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 Jul 2011 18:35:31 -0700 Subject: [Mailman-Users] upgrading Mailman. In-Reply-To: <5A72613502AA48E3A10DB3CB304A9403@michael849cd7d> Message-ID: Michael Capelle wrote: >I need to add, we are not using 5.0.4, we are using 5.0.8. Is there any >dependencies we need to download? >we have 2.1.11, and we want to upgrade to 2.1.15, we are using debian 5.0.8. I believe Mailman 2.1.11 (1:2.1.11-11+lenny1) is the latest Debian packaged release for Debian 5. If you want to install from source, you will need python and python-dev - Python 2.6.x is recommended for current Mailman, but Python 2.5.x (not 2.5) should be OK, see and . Whatever MTA and web server you currently have is OK. I don't know where you plan to get Mailman 2.1.15. The latest release is 2.1.14-1, although 2.1.15 should be released this summer, but there is currently no target date. Others on this list or a Debian/Ubuntu list/forum may have more information on installing from source on Debian. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From maria at shadlen.org Mon Jul 25 06:53:47 2011 From: maria at shadlen.org (Maria Mckinley) Date: Sun, 24 Jul 2011 21:53:47 -0700 Subject: [Mailman-Users] upgrade question Message-ID: <4E2CF6DB.9030302@shadlen.org> Hi there, I have upgraded my mail server by the following steps: 1. make a copy of the old hard drive 2. upgrade the new one (while isolated) while the old one is still running 3. once the new one is working isolate both 4. then rsync data from the old to the new. 5. bring the new one on line. However, mailman is missing some stuff that happened while I was upgrading the new machine, so I must be rsyncing the wrong directory. I thought it should be /var/lib/mailman/, but I think this must not be the directory that mailman is using anymore. This is on a debian squeeze machine. thanks, maria From adam-mailman at amyl.org.uk Mon Jul 25 16:46:32 2011 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Mon, 25 Jul 2011 15:46:32 +0100 Subject: [Mailman-Users] upgrade question In-Reply-To: <4E2CF6DB.9030302@shadlen.org> References: <4E2CF6DB.9030302@shadlen.org> Message-ID: <20110725144632.GG4223@hendricks.amyl.org.uk> On Sun, Jul 24, 2011 at 09:53:47PM -0700, Maria Mckinley wrote: > However, mailman is missing some stuff that happened while I was > upgrading the new machine, so I must be rsyncing the wrong directory. I > thought it should be /var/lib/mailman/, but I think this must not be the > directory that mailman is using anymore. This is on a debian squeeze > machine. This may have been more suitable for the pkg-mailman-hackers list, but that aside -- /etc/mailman and /usr/lib/mailman and /etc/{init.d,default} also have bits and pieces, along with, probably, things in your MTA's config, and perhaps anti-spam software directory, and maybe any other MDAs / LDAs. -- "Remember, the plural of 'moron' is 'focus group'." -- James A Wolf From mark at msapiro.net Mon Jul 25 16:40:44 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 Jul 2011 07:40:44 -0700 Subject: [Mailman-Users] upgrade question In-Reply-To: <4E2CF6DB.9030302@shadlen.org> Message-ID: Maria Mckinley wrote: > >However, mailman is missing some stuff that happened while I was >upgrading the new machine, so I must be rsyncing the wrong directory. I >thought it should be /var/lib/mailman/, but I think this must not be the >directory that mailman is using anymore. This is on a debian squeeze >machine. This is really a Debian packaging question, but in addition to /var/lib/mailman, there are probably things in /usr/lib/mailman and maybe /etc/mailman. You could try 'locate mailman'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adam-mailman at amyl.org.uk Mon Jul 25 17:58:17 2011 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Mon, 25 Jul 2011 16:58:17 +0100 Subject: [Mailman-Users] upgrade question In-Reply-To: References: <4E2CF6DB.9030302@shadlen.org> Message-ID: <20110725155817.GH4223@hendricks.amyl.org.uk> On Mon, Jul 25, 2011 at 07:40:44AM -0700, Mark Sapiro wrote: > You could try 'locate mailman'. And/or 'dpkg -L mailman' -- "There seems to be something wrong with our bloody ships today" -- David, Vice-Admiral Beatty (re: the Battle of the Jutland) From maria at shadlen.org Mon Jul 25 23:31:01 2011 From: maria at shadlen.org (Maria Mckinley) Date: Mon, 25 Jul 2011 14:31:01 -0700 Subject: [Mailman-Users] upgrade question In-Reply-To: <20110725155817.GH4223@hendricks.amyl.org.uk> References: <4E2CF6DB.9030302@shadlen.org> <20110725155817.GH4223@hendricks.amyl.org.uk> Message-ID: <4E2DE095.9050403@shadlen.org> On 7/25/11 8:58 AM, Adam McGreggor wrote: > On Mon, Jul 25, 2011 at 07:40:44AM -0700, Mark Sapiro wrote: >> You could try 'locate mailman'. > > And/or 'dpkg -L mailman' > Thanks for everyone's help. Turns out I had copied the correct directory, but the mboxes needed to be rebuilt. But, there are some subscribers that were added between the builds, and they seem to still be lost. Does anyone know what file has the subscriber lists? thanks, maria From mark at msapiro.net Tue Jul 26 02:05:13 2011 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 Jul 2011 17:05:13 -0700 Subject: [Mailman-Users] upgrade question In-Reply-To: <4E2DE095.9050403@shadlen.org> References: <4E2CF6DB.9030302@shadlen.org> <20110725155817.GH4223@hendricks.amyl.org.uk> <4E2DE095.9050403@shadlen.org> Message-ID: <4E2E04B9.6090701@msapiro.net> On 7/25/2011 2:31 PM, Maria Mckinley wrote: > > Thanks for everyone's help. Turns out I had copied the correct > directory, but the mboxes needed to be rebuilt. But, there are some > subscribers that were added between the builds, and they seem to still > be lost. Does anyone know what file has the subscriber lists? I'm not sure what you're referring to as mboxes, but the configuration, subscriber list, etc. for the LISTNAME list are all saved as a Python pickle of the list object in the file /var/lib/mailman/lists/LISTNAME/config.pck. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From kowalskM at cs.moravian.edu Tue Jul 26 17:33:17 2011 From: kowalskM at cs.moravian.edu (myron) Date: Tue, 26 Jul 2011 11:33:17 -0400 Subject: [Mailman-Users] moving mailman to another server Message-ID: I'm moving mailman from Solaris to Ubuntu 10.04. The latest it installed on Ubuntu was ii mailman 1:2.1.13-1ubuntu0.2 Everything seems to work fine on a test list (xxx) except that it won't build any archives. This is from the log/mailman/error Jul 26 11:21:57 2011 (1132) Archive file access failure: /var/lib/mailman/archives/private/xxx.mbox/xxx.mbox [Errno 13] Permission denied: '/var/lib/mailman/archives/private/xxx.mbox/ xxx.mbox' Jul 26 11:21:57 2011 (1132) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/xxx.mbox/xxx.mbox' Jul 26 11:21:57 2011 (1132) Traceback (most recent call last): File "/var/lib/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/var/lib/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 198, in ArchiveMail self.__archive_to_mbox(msg) File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 167, in __archive_to_mbox mbox = self.__archive_file(afn) File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 155, in __archive_file return Mailbox.Mailbox(open(afn, 'a+')) IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/ private/xxx.mbox/xxx.mbox' These are the permissions setup by mailman on the archive directories. /var/lib/mailman/archives# ll total 16 drwxrwsr-x 4 root list 4096 2011-07-20 10:38 ./ drwxrwsr-x 9 root list 4096 2011-07-25 13:49 ../ drwxrws--- 8 root www-data 4096 2011-07-25 14:56 private/ drwxrwsr-x 2 root list 4096 2011-07-25 14:56 public/ It doesn't seem to like the root:www-data permission setup. --myron ================================= Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College myron at cs.moravian.edu From mark at msapiro.net Wed Jul 27 04:35:55 2011 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 26 Jul 2011 19:35:55 -0700 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: References: Message-ID: <4E2F798B.2050301@msapiro.net> On 7/26/2011 8:33 AM, myron wrote: > > These are the permissions setup by mailman on the archive > directories. > > /var/lib/mailman/archives# ll total 16 drwxrwsr-x 4 root list > 4096 2011-07-20 10:38 ./ drwxrwsr-x 9 root list 4096 2011-07-25 > 13:49 ../ drwxrws--- 8 root www-data 4096 2011-07-25 14:56 private/ > drwxrwsr-x 2 root list 4096 2011-07-25 14:56 public/ > > It doesn't seem to like the root:www-data permission setup. Exactly. archives/private should be owner:group www-data:list, not root:www-data. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From maria at shadlen.org Wed Jul 27 21:20:21 2011 From: maria at shadlen.org (Maria Mckinley) Date: Wed, 27 Jul 2011 12:20:21 -0700 Subject: [Mailman-Users] upgrade question In-Reply-To: <4E2E04B9.6090701@msapiro.net> References: <4E2CF6DB.9030302@shadlen.org> <20110725155817.GH4223@hendricks.amyl.org.uk> <4E2DE095.9050403@shadlen.org> <4E2E04B9.6090701@msapiro.net> Message-ID: <4E3064F5.3030902@shadlen.org> On 7/25/11 5:05 PM, Mark Sapiro wrote: > On 7/25/2011 2:31 PM, Maria Mckinley wrote: >> >> Thanks for everyone's help. Turns out I had copied the correct >> directory, but the mboxes needed to be rebuilt. But, there are some >> subscribers that were added between the builds, and they seem to still >> be lost. Does anyone know what file has the subscriber lists? > > > I'm not sure what you're referring to as mboxes, but the configuration, > subscriber list, etc. for the LISTNAME list are all saved as a Python > pickle of the list object in the file > /var/lib/mailman/lists/LISTNAME/config.pck. > Yes, thanks, that was it. Not sure why that didn't get copied over. cheers, maria From kowalskM at cs.moravian.edu Wed Jul 27 21:22:39 2011 From: kowalskM at cs.moravian.edu (myron) Date: Wed, 27 Jul 2011 15:22:39 -0400 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: <4E2F798B.2050301@msapiro.net> References: <4E2F798B.2050301@msapiro.net> Message-ID: <84E82371-8675-4019-8E78-8F5472FDAEB4@cs.moravian.edu> On Jul 26, 2011, at 10:35 PM, Mark Sapiro wrote: > On 7/26/2011 8:33 AM, myron wrote: >> >> These are the permissions setup by mailman on the archive >> directories. >> >> /var/lib/mailman/archives# ll total 16 drwxrwsr-x 4 root list >> 4096 2011-07-20 10:38 ./ drwxrwsr-x 9 root list 4096 2011-07-25 >> 13:49 ../ drwxrws--- 8 root www-data 4096 2011-07-25 14:56 private/ >> drwxrwsr-x 2 root list 4096 2011-07-25 14:56 public/ >> >> It doesn't seem to like the root:www-data permission setup. > > > Exactly. archives/private should be owner:group www-data:list, not > root:www-data. > I'm going to assume you meant list:www-data because I have a user list and group www-data not vice versa. > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From mark at msapiro.net Thu Jul 28 00:55:59 2011 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 27 Jul 2011 15:55:59 -0700 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: <84E82371-8675-4019-8E78-8F5472FDAEB4@cs.moravian.edu> Message-ID: myron wrote: >On Jul 26, 2011, at 10:35 PM, Mark Sapiro wrote: > >> On 7/26/2011 8:33 AM, myron wrote: >>> >>> These are the permissions setup by mailman on the archive >>> directories. >>> >>> /var/lib/mailman/archives# ll >>> total 16 >>> drwxrwsr-x 4 root list 4096 2011-07-20 10:38 ./ >>> drwxrwsr-x 9 root list 4096 2011-07-25 13:49 ../ >>> drwxrws--- 8 root www-data 4096 2011-07-25 14:56 private/ >>> drwxrwsr-x 2 root list 4096 2011-07-25 14:56 public/ >>> >>> It doesn't seem to like the root:www-data permission setup. >> >> >> Exactly. archives/private should be owner:group www-data:list, not >> root:www-data. >> > >I'm going to assume you meant list:www-data because I have a user list >and group www-data not vice versa. No. I meant exactly what I wrote. See the FAQ at and the installation manual at for further information. If you don't have a 'list' group, how come it is the group of /var/lib/mailman, /var/lib/mailman/archives and /var/lib/mailman/archives/public? If you don't have a 'www-data' user, then that should be whatever the user is that your web server runs Mailman's CGIs as. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dunkel at calamus.net Thu Jul 28 15:29:11 2011 From: dunkel at calamus.net (Ulf Dunkel) Date: Thu, 28 Jul 2011 15:29:11 +0200 Subject: [Mailman-Users] Mailman aliases: various places on new server? Message-ID: <4E316427.6000402@calamus.net> Hi Mark, once again, I also had to move my Mailman lists to a new server. Now that I am almost done, I wonder about this: When I run /usr/lib/mailman/bin/genaliases, I see that in /etc/mailman/ the relevant files are updated: - aliases - aliases.db - virtual-mailman - virtual-mailman.db But Postfix won't react on alias changes until I copy at least the aliases* files into /var/lib/mailman/data/. I didn't set up Mailman on the new machine, but my ISP did. In various documentations on the web I see various places for all this stuff. Is there any place where the genaliases output should be written to by default? ---Ulf Dunkel From dunkel at calamus.net Thu Jul 28 15:23:55 2011 From: dunkel at calamus.net (Ulf Dunkel) Date: Thu, 28 Jul 2011 15:23:55 +0200 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: References: Message-ID: <4E3162EB.2020606@calamus.net> Hi Myron. ~mailman/bin/check_perms is your friend, really. When you're done fixing all permissions, run ~mailman/bin/unshunt I am almost done with the same stuff - once again. ---Ulf Dunkel From mark at msapiro.net Thu Jul 28 15:58:12 2011 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 Jul 2011 06:58:12 -0700 Subject: [Mailman-Users] Mailman aliases: various places on new server? In-Reply-To: <4E316427.6000402@calamus.net> Message-ID: Ulf Dunkel wrote: > >When I run /usr/lib/mailman/bin/genaliases, I see that in /etc/mailman/ >the relevant files are updated: > >- aliases >- aliases.db >- virtual-mailman >- virtual-mailman.db > >But Postfix won't react on alias changes until I copy at least the >aliases* files into /var/lib/mailman/data/. > >I didn't set up Mailman on the new machine, but my ISP did. In various >documentations on the web I see various places for all this stuff. Is >there any place where the genaliases output should be written to by default? In standard GNU Mailman genaliases and list creation/deletion with MTA = 'Postfix' writes/updates aliases* and virtual-mailman* in $var-prefix/data/ where var-prefix is set by configure when Mailman is configured. This can be overridden in mm_cfg.py by setting DATA_DIR = '/etc/mailman' or anything else as desired. It appears your ISP is using some packaged Mailman (possibly Debian or RedHat), but has not properly configured Postfix to look for Mailman's aliases and virtual maps in the place where the package puts them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dunkel at calamus.net Thu Jul 28 17:51:22 2011 From: dunkel at calamus.net (Ulf Dunkel) Date: Thu, 28 Jul 2011 17:51:22 +0200 Subject: [Mailman-Users] Mailman aliases: various places on new server? In-Reply-To: References: Message-ID: <4E31857A.5000508@calamus.net> Hi Mark. > It appears your ISP is using some packaged Mailman (possibly Debian or > RedHat), but has not properly configured Postfix to look for Mailman's > aliases and virtual maps in the place where the package puts them. It's a VM with CentOS and I guess he simply picked the package from Yum. I have now fixed the relevant entry in /etc/postfix/main.cf: ----- snip ----- alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases ----- snap ----- Thank you for your comment, as always. ---Ulf Dunkel From barry at list.org Thu Jul 28 20:56:06 2011 From: barry at list.org (Barry Warsaw) Date: Thu, 28 Jul 2011 14:56:06 -0400 Subject: [Mailman-Users] wiki.list.org license has been renewed Message-ID: <20110728145606.116e0b49@resist.wooz.org> I think I've managed to get our Confluence license renewed, so those of you with write privileges to wiki.list.org should be able to save pages again. If not, please let me know. I haven't heard much about the Moin conversion lately, but hopefully that will happen before the next time our license runs out. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From barry at list.org Fri Jul 29 01:34:31 2011 From: barry at list.org (Barry Warsaw) Date: Thu, 28 Jul 2011 19:34:31 -0400 Subject: [Mailman-Users] [Mailman-Announce] wiki.list.org license has been renewed In-Reply-To: <4E31EF5D.7050509@bjdean.id.au> References: <20110728145606.116e0b49@resist.wooz.org> <4E31EF5D.7050509@bjdean.id.au> Message-ID: <20110728193431.5d0df560@resist.wooz.org> On Jul 29, 2011, at 09:23 AM, Bradley Dean wrote: >On 29/07/11 04:56, Barry Warsaw wrote: >> I haven't heard much about the Moin conversion lately, but hopefully that will >> happen before the next time our license runs out. > >Still working through it - sorry it's taking longer than hoped but the confluence XML is, well, interesting: > > * http://lists.bjdean.id.au/pipermail/mmwiki/2011q3/000067.html > * http://lists.bjdean.id.au/pipermail/mmwiki/2011q3/000068.html > * http://moinmo.in/ConfluenceConverter/DevelopmentNotes/TransformProcess#Confluence_Dump_XML > >We've also had a little less input from members of the assembled team. Now that I think I've got the XML structure pinned down I'll get stuck in to the content extraction and transformation. Thanks for the update! -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From dunkel at calamus.net Fri Jul 29 13:52:02 2011 From: dunkel at calamus.net (Ulf Dunkel) Date: Fri, 29 Jul 2011 13:52:02 +0200 Subject: [Mailman-Users] Any quantity restrictions in who email command? Message-ID: <4E329EE2.4060702@calamus.net> Hi Mark. I try to grab the members from various of my mailing lists via the email interface, but two of them with more than 1,000 users each won't let Mailman reply on my "who " email to the relevant -request at mydomain account. Are there any quantity restrictions I have overseen (or forgotten)? Thanks in advance for your reply, ---Ulf Dunkel From bjdean at bjdean.id.au Fri Jul 29 01:23:09 2011 From: bjdean at bjdean.id.au (Bradley Dean) Date: Fri, 29 Jul 2011 09:23:09 +1000 Subject: [Mailman-Users] [Mailman-Announce] wiki.list.org license has been renewed In-Reply-To: <20110728145606.116e0b49@resist.wooz.org> References: <20110728145606.116e0b49@resist.wooz.org> Message-ID: <4E31EF5D.7050509@bjdean.id.au> Hi folks, On 29/07/11 04:56, Barry Warsaw wrote: > I haven't heard much about the Moin conversion lately, but hopefully that will > happen before the next time our license runs out. Still working through it - sorry it's taking longer than hoped but the confluence XML is, well, interesting: * http://lists.bjdean.id.au/pipermail/mmwiki/2011q3/000067.html * http://lists.bjdean.id.au/pipermail/mmwiki/2011q3/000068.html * http://moinmo.in/ConfluenceConverter/DevelopmentNotes/TransformProcess#Confluence_Dump_XML We've also had a little less input from members of the assembled team. Now that I think I've got the XML structure pinned down I'll get stuck in to the content extraction and transformation. Cheerio, Brad -- Bradley Dean Email: bjdean at bjdean.id.au Skype: skype at bjdean.id.au Mobile(Aus): +61-413014395 WWW: http://bjdean.id.au/ From kowalskM at cs.moravian.edu Thu Jul 28 17:19:28 2011 From: kowalskM at cs.moravian.edu (myron) Date: Thu, 28 Jul 2011 11:19:28 -0400 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: <4E3162EB.2020606@calamus.net> References: <4E3162EB.2020606@calamus.net> Message-ID: <0E38CAE4-F88D-4F00-A0AF-03D1536AAFE6@cs.moravian.edu> On Jul 28, 2011, at 9:23 AM, Ulf Dunkel wrote: > Hi Myron. > > ~mailman/bin/check_perms is your friend, really. Mark was right about the owner:group setting. Looks like I was combining fact with fiction. I was making a lot of assumptions about what's on my system. Easy when you're not familiar with the OS. I think it's working now. When I run bin/check_perms I get 10 listed problems--all links. I looked at some of the links and they are right. I assume the rest are too. However, when I create a newlist, it is made with the same wrong permissions, but running bin/check_perms doesn't report it. So, I'm guessing that all I need to do is set www-data:list on the list whenever I create a new list. > > When you're done fixing all permissions, run > > ~mailman/bin/unshunt > > > I am almost done with the same stuff - once again. > > ---Ulf Dunkel > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-users/myron%40cs.moravian.edu From lorenzo at coronati.com Thu Jul 28 17:41:50 2011 From: lorenzo at coronati.com (Lorenzo Coronati) Date: Thu, 28 Jul 2011 17:41:50 +0200 Subject: [Mailman-Users] mailman problem with exim Message-ID: <4E31833E.5020708@coronati.com> hi all I'm trying to make mailman work with exim (on a centos server) but I'm facing a problem: when a subscriber posts a message, it isn't forwarded to the other subscribers, and no error message is sent back to the sender this is what I find in the /var/log/exim/main.log: 2011-07-28 09:01:50 1QmKbO-0004h7-NS <= lorenzo at coronati.com H=adsl-ull-193-191.49-151.net24.it ([192.168.0.207]) [151.49.191.193] P=esmtpa A=plain_login:lorenzo at coronati.com S=644 id=4E310960.6050509 at coronati.com T="provo io" 2011-07-28 09:01:50 1QmKbO-0004h7-NS Failed to find group "" from expanded string "${lookup mysql{select users.gid from users,domains where localpart = '${quote_mysql:$local_part}' and domain = '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}" for the address_pipe transport 2011-07-28 09:01:50 1QmKbO-0004h7-NS == |/usr/local/mailman/mail/mailman post mailinglistaips R=system_aliases T=address_pipe defer (-28): Failed to find group "" from expanded string "${lookup mysql{select users.gid from users,domains where localpart = '${quote_mysql:$local_part}' and domain = '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}" for the address_pipe transport what I understand is that exim (which is configured to manage the email addresses stored in a mysql database) tries to expand the mailing list looking for subscribers via sql, instead of letting mailman to do this am I right? and then, what do I have to do to fix this? thanks in advance lorenzo From mark at msapiro.net Fri Jul 29 16:27:10 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Jul 2011 07:27:10 -0700 Subject: [Mailman-Users] Any quantity restrictions in who email command? In-Reply-To: <4E329EE2.4060702@calamus.net> Message-ID: Ulf Dunkel wrote: > >I try to grab the members from various of my mailing lists via the email >interface, but two of them with more than 1,000 users each won't let >Mailman reply on my "who " email to the relevant >-request at mydomain account. > >Are there any quantity restrictions I have overseen (or forgotten)? There are no built-in limits. Is there anything in Mailman's logs, particularly error and qrunner? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 29 16:29:50 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Jul 2011 07:29:50 -0700 Subject: [Mailman-Users] mailman problem with exim In-Reply-To: <4E31833E.5020708@coronati.com> Message-ID: Lorenzo Coronati wrote: > >what I understand is that exim (which is configured to manage the email >addresses stored in a mysql database) tries to expand the mailing list >looking for subscribers via sql, instead of letting mailman to do this >am I right? >and then, what do I have to do to fix this? See for the recommended way to configure Exim with Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jul 29 16:43:00 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Jul 2011 07:43:00 -0700 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: <0E38CAE4-F88D-4F00-A0AF-03D1536AAFE6@cs.moravian.edu> Message-ID: myron wrote: > >I think it's working now. When I run bin/check_perms I get 10 listed >problems--all links. >I looked at some of the links and they are right. I assume the rest >are too. > >However, when I create a newlist, it is made with the same wrong >permissions, but running >bin/check_perms doesn't report it. So, I'm guessing that all I need to >do is set www-data:list >on the list whenever I create a new list. Exactly which directories/files get incorrect owner:group? What exactly is the incorrect owner:group? Is the superordinate directory group 'list' and SETGID? Note that in general the owner is irrelevant but the group should always be 'list'. The only place owner matters is on the single directory /var/lib/mailman/archives/private and only if it is not o+x. See the FAQ at and the installation manual at for further information. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adam-mailman at amyl.org.uk Fri Jul 29 17:06:14 2011 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Fri, 29 Jul 2011 16:06:14 +0100 Subject: [Mailman-Users] mailman problem with exim In-Reply-To: References: <4E31833E.5020708@coronati.com> Message-ID: <20110729150614.GO4223@hendricks.amyl.org.uk> On Fri, Jul 29, 2011 at 07:29:50AM -0700, Mark Sapiro wrote: > Lorenzo Coronati wrote: > > > >what I understand is that exim (which is configured to manage the email > >addresses stored in a mysql database) tries to expand the mailing list > >looking for subscribers via sql, instead of letting mailman to do this > >am I right? > >and then, what do I have to do to fix this? > > > See for the recommended way > to configure Exim with Mailman. And make sure your routers are ordered the way you wish them to have precedence (read from the top) -- "Bernard: It's another of those irregular verbs. I hold confidential briefings, you leak, he's been charged under section 2A of the Official Secrets Act." From kowalskM at cs.moravian.edu Fri Jul 29 17:02:33 2011 From: kowalskM at cs.moravian.edu (myron) Date: Fri, 29 Jul 2011 11:02:33 -0400 Subject: [Mailman-Users] moving mailman to another server In-Reply-To: References: Message-ID: <51B0D077-FD45-4307-8931-9EAAA21F01A7@cs.moravian.edu> On Jul 29, 2011, at 10:43 AM, Mark Sapiro wrote: > myron wrote: >> >> I think it's working now. When I run bin/check_perms I get 10 listed >> problems--all links. >> I looked at some of the links and they are right. I assume the rest >> are too. >> >> However, when I create a newlist, it is made with the same wrong >> permissions, but running >> bin/check_perms doesn't report it. So, I'm guessing that all I need >> to >> do is set www-data:list >> on the list whenever I create a new list. > > > Exactly which directories/files get incorrect owner:group? What > exactly > is the incorrect owner:group? Is the superordinate directory group > 'list' and SETGID? root at errol:/var/lib/mailman/archives# ll drwxrws--- 14 www-data list 4096 2011-07-29 10:48 private/ drwxrwsr-x 2 root list 4096 2011-07-29 10:48 public/ > > Note that in general the owner is irrelevant but the group should > always be 'list'. The only place owner matters is on the single > directory /var/lib/mailman/archives/private and only if it is not o+x. > See the FAQ at and the installation > manual at for further > information. And it works. I tested it this time instead of just assuming. The archives appear for both aaa and xxx lists. Thanks. drwxrws--- 14 www-data list 4096 2011-07-29 10:48 ./ drwxrwsr-x 4 root list 4096 2011-07-20 10:38 ../ drwxrwsr-x 2 root list 4096 2011-07-29 10:48 aaa/ drwxrwsr-x 2 root list 4096 2011-07-29 10:48 aaa.mbox/ drwxrwsr-x 2 www-data list 4096 2011-07-20 10:39 mailman/ drwxrwsr-x 2 www-data list 4096 2011-07-20 10:39 mailman.mbox/ drwxrwsr-x 6 www-data list 4096 2011-07-28 03:27 xxx/ drwxrwsr-x 2 www-data list 4096 2011-07-27 15:34 xxx.mbox/ > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-users/myron%40cs.moravian.edu From lorenzo at coronati.com Fri Jul 29 17:52:00 2011 From: lorenzo at coronati.com (Lorenzo Coronati) Date: Fri, 29 Jul 2011 17:52:00 +0200 Subject: [Mailman-Users] mailman problem with exim In-Reply-To: References: Message-ID: <4E32D720.90209@coronati.com> On 29/07/2011 16:29, Mark Sapiro wrote: > Lorenzo Coronati wrote: >> what I understand is that exim (which is configured to manage the email >> addresses stored in a mysql database) tries to expand the mailing list >> looking for subscribers via sql, instead of letting mailman to do this >> am I right? >> and then, what do I have to do to fix this? > > See for the recommended way > to configure Exim with Mailman. > Thanks Mark, I've read that page and followed the examples, but still I can't make things work. I wonder if all instructions I've found are based on the assumption that exim works with real unix users... Lorenzo From mark at msapiro.net Fri Jul 29 23:42:07 2011 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Jul 2011 14:42:07 -0700 Subject: [Mailman-Users] mailman problem with exim In-Reply-To: <4E32D720.90209@coronati.com> Message-ID: Lorenzo Coronati wrote: > >Thanks Mark, >I've read that page and followed the examples, but still I can't make >things work. >I wonder if all instructions I've found are based on the assumption that >exim works with real unix users... >Lorenzo Check your exim logs. If your list mail is not using the "mailman_router" router, you need to move that router closer to the front of the routers section, at least ahead of the router it is using. The "mailman_router" router uses the "mailman_transport" transport, not the "address_pipe" transport in the messages in your OP. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lorenzo at coronati.com Sat Jul 30 09:20:30 2011 From: lorenzo at coronati.com (Lorenzo Coronati) Date: Sat, 30 Jul 2011 09:20:30 +0200 Subject: [Mailman-Users] mailman problem with exim In-Reply-To: References: Message-ID: <4E33B0BE.6030706@coronati.com> On 29/07/2011 23:42, Mark Sapiro wrote: > > Check your exim logs. If your list mail is not using the > "mailman_router" router, you need to move that router closer to the > front of the routers section, at least ahead of the router it is > using. The "mailman_router" router uses the "mailman_transport" > transport, not the "address_pipe" transport in the messages in your OP. > Hi Mark, the router is the first of the list; I paste it here: mailman_router: driver = accept domains = +mm_domains require_files = MAILMAN_LISTCHK local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm+* : -join : -leave : \ -owner : -request : -admin headers_remove = X-Spam-Score:X-Spam-Report transport = mailman_transport and the transport follows: mailman_transport: driver = pipe command = MAILMAN_WRAP \ '${if def:local_part_suffix \ {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \ {post}}' \ $local_part current_directory = MAILMAN_HOME home_directory = MAILMAN_HOME user = MAILMAN_USER group = MAILMAN_GROUP I copied both from one of the many tutorials on the web, and adjusted only the variables in capitals... Thanks again for your support Lorenzo From dunkel at calamus.net Sat Jul 30 10:45:51 2011 From: dunkel at calamus.net (Ulf Dunkel) Date: Sat, 30 Jul 2011 10:45:51 +0200 Subject: [Mailman-Users] Any quantity restrictions in who email command? In-Reply-To: References: Message-ID: <4E33C4BF.4050707@calamus.net> Am 29.07.2011 16:27, schrieb Mark Sapiro: > Ulf Dunkel wrote: >> >> I try to grab the members from various of my mailing lists via the email >> interface, but two of them with more than 1,000 users each won't let >> Mailman reply on my "who" email to the relevant >> -request at mydomain account. >> >> Are there any quantity restrictions I have overseen (or forgotten)? > > > There are no built-in limits. Is there anything in Mailman's logs, > particularly error and qrunner? My fault - the replies were simply dropped into my Junk folder where I found them this morning. Don't know why Thunderbird did this. :-) ---Ulf Dunkel From mark at msapiro.net Sat Jul 30 15:57:25 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 30 Jul 2011 06:57:25 -0700 Subject: [Mailman-Users] mailman problem with exim In-Reply-To: <4E33B0BE.6030706@coronati.com> Message-ID: Lorenzo Coronati wrote: > >mailman_router: > driver = accept > domains = +mm_domains What is your definition of mm_domains? > require_files = MAILMAN_LISTCHK What are your defininitions of MAILMAN_LISTCHK, MAILMAN_HOME, MAILMAN_USER and MAILMAN_GROUP > local_part_suffix_optional > local_part_suffix = -bounces : -bounces+* : \ > -confirm+* : -join : -leave : \ > -owner : -request : -admin The list above should probably also include -confirm, -subscribe and -unsubscribe. > headers_remove = X-Spam-Score:X-Spam-Report > transport = mailman_transport > > >and the transport follows: > >mailman_transport: > driver = pipe > command = MAILMAN_WRAP \ > '${if def:local_part_suffix \ > {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \ > {post}}' \ > $local_part > current_directory = MAILMAN_HOME > home_directory = MAILMAN_HOME > user = MAILMAN_USER > group = MAILMAN_GROUP > > >I copied both from one of the many tutorials on the web, and adjusted >only the variables in capitals... There should be domainlist mm_domains=aips.it or maybe domainlist mm_domains=aips.it:other.list.domain:... in your configuration. Your OP showed your list mail was using the transport 'address_pipe', not 'mailman_transport'. If your mailman_router is first and you are still seeing the same errors with the address_pipe transport, some condition in your mailman_router is not being met. Either, your mm_domains domain list does not include your list domain(s) or your MAILMAN_LISTCHK macro doesn't expand to the correct /path/to/lists/LISTNAME/config.pck. Note that if you installed Mailman from a RedHat/CentOS rpm, most examples on the web won't work because the mail wrapper mail/mailman and the lists/ directory are not in the same MM_HOME directory. I.e. the wrapper is /usr/lib/mailman/mail/mailman and the list directory is /var/lib/mailman/lists/. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From bill at flanagan-consulting.com Sun Jul 31 14:39:22 2011 From: bill at flanagan-consulting.com (W. Flanagan) Date: Sun, 31 Jul 2011 08:39:22 -0400 Subject: [Mailman-Users] Setting MIME as default for new Non-Digest subscribers In-Reply-To: References: Message-ID: <4E354CFA.7010406@flanagan-consulting.com> Hi, This question from Jan 2005 is still a problem. All the addresses I load into mailman end up with a check in the "plain" box when listed under membership management. I seem to recall (from years ago) a config choice for new non-digest subscribers to force plain format, but it's not in the 2.1.14 version. The current admin manual does not address (that I can find) what effect the plain check box has on non-digest subscribers. If there is no effect, perhaps I can contribute some text to explain what happens--when I know. Bill > >QUESTIONS: > >In order to avoid having to manually change this option for each > >existing subscriber, is there a way to force all existing subscribers to > >receive MIME in Non-Digest mode? > > > >If not, is there a way to force all NEW subscribers to be enrolled with > >MIME as their default? > > > >Also, is there a way to "lock" the MIME switch on, so that users who try > >to change their option to plain text will be prevented from doing so? > > > Your questions are not relevant to what you are doing. To send MIME > format messages to non-digest subscribers you just post that format to > the list and either turn off content filtering or adjust the content > filtering to pass what you want. -- Flanagan Consulting *In Converged Networking* *We Have the Experience* 3800 Concorde Parkway, Suite 1500, Chantilly, Virginia USA Ph: +1.703.242.8381 Fx: +1.703.242.8391 www.Flanagan-Consulting.com /Flanagan Consulting is a Service Mark of W. A. Flanagan, Inc. / /"Beware of false knowledge; it is more dangerous than ignorance." / --George Bernard Shaw From tom.browder at gmail.com Sat Jul 30 15:24:46 2011 From: tom.browder at gmail.com (Tom Browder) Date: Sat, 30 Jul 2011 08:24:46 -0500 Subject: [Mailman-Users] Mailman error: Forbidden: You don't have permission to access /pipermail/grads/ on this server Message-ID: I'm testing a new installation of postfix and mailman on a remote server (Ubuntu 10.04 LTS, 64-bit) with two active virtual hosts. Each host is accessed via a switch to https (TLS). I installed mailman (and postfix) via my package manager. I've established four lists, two for each server, and I can send and receive mail successfully so far. However, I, as a list user, cannot get access to the archives for a list. When I try to look at the archives through the link on the Welcome message I get the following: Forbidden You don't have permission to access /pipermail/grads/ on this server. I tried changing the example line in the mailman.conf file from: Alias /pipermail/ /var/lib/mailman/archives/public/ to ScriptAlias /pipermail/ /var/lib/mailman/archives/public/ but that didn't change anything so I changed it back. I have searched this list for "pipermail" but see no similar problem. I'm sure I've missed a note somewhere but I'm not sure how to proceed. The mailman docs talk about permissions and the mailman user but Ubuntu installs all mailman files with root:list ownership which seems to work for all else. All the directories under /var/lib/mailman have these permissions: drwxrwsr-x 4 root list Thanks for your help. Best regards, -Tom Thomas M. Browder, Jr. Niceville, Florida USA From tom.browder at gmail.com Sat Jul 30 17:41:37 2011 From: tom.browder at gmail.com (Tom Browder) Date: Sat, 30 Jul 2011 10:41:37 -0500 Subject: [Mailman-Users] Error when e-mailing a list: User unknown in virtual alias table Message-ID: I get this message when posting to my new lists: Delivery to the following recipient failed permanently: news at mydomain.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table (state 14). The Mailman docs (specifically /etc/mailman/postfix-to-mailman.py) says that I don't have to set up virtual aliases: # -join, -leave, -subscribe and -unsubscribe addresses. It will # recognize a list as soon as the list is created, there is no need to # add _any_ aliases for any list. It recognizes mail to postmaster, but is that really true? Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA From mark at msapiro.net Sun Jul 31 19:57:46 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 Jul 2011 10:57:46 -0700 Subject: [Mailman-Users] Setting MIME as default for new Non-Digestsubscribers In-Reply-To: <4E354CFA.7010406@flanagan-consulting.com> Message-ID: W. Flanagan wrote: > >This question from Jan 2005 is still a problem. All the addresses I >load into mailman end up with a check in the "plain" box when listed >under membership management. I seem to recall (from years ago) a config >choice for new non-digest subscribers to force plain format, but it's >not in the 2.1.14 version. > >The current admin manual does not address (that I can find) what effect >the plain check box has on non-digest subscribers. If there is no >effect, perhaps I can contribute some text to explain what happens--when >I know. The plain/MIME setting only affects digests. It has no effect whatsoever on non-digest subscribers. The actual option bit exists for all subscribers and is controlled for new subscribers by the Digest options -> mime_is_default_digest setting, but it only actually affects the format of the digest for digest subscribers. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jul 31 20:08:54 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 Jul 2011 11:08:54 -0700 Subject: [Mailman-Users] Mailman error: Forbidden: You don't have permissionto access /pipermail/grads/ on this server In-Reply-To: Message-ID: Tom Browder wrote: > >However, I, as a list user, cannot get access to the archives for a >list. When I try to look at the archives through the link on the >Welcome message I get the following: > > Forbidden > > You don't have permission to access /pipermail/grads/ on this server. > >I tried changing the example line in the mailman.conf file from: > > Alias /pipermail/ /var/lib/mailman/archives/public/ > >to > > ScriptAlias /pipermail/ /var/lib/mailman/archives/public/ > >but that didn't change anything so I changed it back. Good. >I have searched this list for "pipermail" but see no similar problem. > >I'm sure I've missed a note somewhere but I'm not sure how to proceed. > The mailman docs talk about permissions and the mailman user but >Ubuntu installs all mailman files with root:list ownership which seems >to work for all else. All the directories under /var/lib/mailman have >these permissions: > > drwxrwsr-x 4 root list If that includes /var/lib/mailman/archives/private, then that's OK. Otherwise note that /var/lib/mailman/archives/private must be o+x or must have user:group xxx:list where xxx is the user that the web server uses to access files. If this is not the problem, make sure the directory /var/lib/mailman/archives/public has Options +FollowSymlinks in your web server config. I.e for Apache, put Options +FollowSymLinks Order allow,deny Allow from all immediately after Alias /pipermail/ /var/lib/mailman/archives/public/ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Jul 31 20:19:50 2011 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 Jul 2011 11:19:50 -0700 Subject: [Mailman-Users] Error when e-mailing a list: User unknown invirtual alias table In-Reply-To: Message-ID: Tom Browder wrote: >I get this message when posting to my new lists: > >Delivery to the following recipient failed permanently: > > news at mydomain.org > >Technical details of permanent failure: >Google tried to deliver your message, but it was rejected by the >recipient domain. We recommend contacting the other email provider for >further information about the cause of this error. The error that the >other server returned was: 550 550 5.1.1 : >Recipient address rejected: User unknown in virtual alias table (state >14). > >The Mailman docs (specifically /etc/mailman/postfix-to-mailman.py) >says that I don't have to set up virtual aliases: postfix-to-mailman.py is not a part of standard GNU mailman. It is part of the Debian/Ubuntu Mailman package, but whether it is properly installed by default is a Debian/Ubuntu packaging question. ># -join, -leave, -subscribe and -unsubscribe addresses. It will ># recognize a list as soon as the list is created, there is no need to ># add _any_ aliases for any list. It recognizes mail to postmaster, > >but is that really true? It is if Postfix is properly configured to use a 'mailman' transport that invokes postfix-to-mailman.py for all mail to the Mailman list domain. It is clear from the above error message that 'mydomain.org' is a virtual alias domain in Postfix and is not mapped to a 'mailman' transport. You can either configure Postfix to use postfix-to-mailman.py per the documentation which may or may not be provided by Debian/Ubuntu or configure Postfix/Mailman integration per . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From reks at iiap.res.in Sun Jul 31 22:27:10 2011 From: reks at iiap.res.in (Rekhesh Mohan) Date: Mon, 1 Aug 2011 01:57:10 +0530 Subject: [Mailman-Users] mailman on freeBSD 8.2: getgrgid error Message-ID: <201108010157.10387.reks@iiap.res.in> Hi folks, I've been fiddling with mailman 2.1.14 (from freebsd ports) on free BSD 8.2. Everything seems to be fine so far except for the web based stuff. I get the following error when I try to access the page: http://this.great.site/mailman/listinfo --------------- Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Failure to find group name for GID 80. Mailman expected the CGI wrapper to be executed as group "www", but the system's web server executed the wrapper as GID 80 for which the name could not be found. Try adding GID 80 to your system as "www", or tweak your web server to run the wrapper as group "www". ---------------- This system has a www user and gid is 80 (group = www). In the first attempt, I let freebsd choose its own configure-arguments and later I tried it myself. Error remained the same. AFAIK, src/common.c is checking the GID with getgid() followed by getgrgid(). Now, my machine uses blowfish instead of md5 for passwd. getgid() is returning 80 - which is fine since i have gid(www) = 80 on my system. However, getgrgid(gid) returns null :-| I gave up my fight at that point and decided to ask for help :) I tried to figure out the behaviour of these functions with a small test code: getgrgid() returns gr_passwd = * for blowfish, and gr_passwd = x for md5. Is that an issue with mailman or am I making mistakes somewhere else in the installation? My apache config is given below (I followed the steps in installation doc.) Thanks in advance..! ------------------------- ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" Alias /pipermail/ "/usr/local/mailman/archives/public/" Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all RedirectMatch ^/mailman[/]*$ http://this.great.site/mailman/listinfo/ -------------------------