From mark at msapiro.net Wed May 4 20:57:38 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 05 May 2016 00:57:38 -0000 Subject: [Bug 1578450] [NEW] Mailman should allow setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string. Message-ID: <20160505005738.24503.64205.malonedeb@gac.canonical.com> Public bug reported: If for some reason a site doesn't want to or can't access a DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL, maybe the site is IPv6 only and there is no IPv6 source of the data, the site should be able to set DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string and avoid the attempted retrieval, the failure of which causes other issues. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1578450 Title: Mailman should allow setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1578450/+subscriptions From 1578450 at bugs.launchpad.net Wed May 4 21:27:49 2016 From: 1578450 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 05 May 2016 01:27:49 -0000 Subject: [Bug 1578450] Re: Mailman should allow setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string. References: <20160505005738.24503.64205.malonedeb@gac.canonical.com> Message-ID: <20160505012752.9759.73276.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1578450 Title: Mailman should allow setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1578450/+subscriptions From mark at msapiro.net Fri May 6 17:45:55 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 06 May 2016 21:45:55 -0000 Subject: [Bug 558281] Re: SMTP authentication and TLS support References: <20100408090904.1687.571.launchpad@loganberry.canonical.com> Message-ID: <20160506214556.8658.86037.launchpad@gac.canonical.com> ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.23 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558281 Title: SMTP authentication and TLS support To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558281/+subscriptions From 558281 at bugs.launchpad.net Fri May 6 17:46:19 2016 From: 558281 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 06 May 2016 21:46:19 -0000 Subject: [Bug 558281] Re: SMTP authentication and TLS support References: <20100408090904.1687.571.launchpad@loganberry.canonical.com> Message-ID: <20160506214623.28472.13131.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558281 Title: SMTP authentication and TLS support To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558281/+subscriptions From 1581215 at bugs.launchpad.net Thu May 12 17:03:24 2016 From: 1581215 at bugs.launchpad.net (Jonas Jelten) Date: Thu, 12 May 2016 21:03:24 -0000 Subject: [Bug 1581215] [NEW] dmarc_moderation_action = wrap message sets no date header Message-ID: <20160512210324.21417.38266.malonedeb@wampee.canonical.com> Public bug reported: The "outer" mail does not have any date header set then, the date field in the "forwarded" message is preserved. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1581215 Title: dmarc_moderation_action = wrap message sets no date header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1581215/+subscriptions From mark at msapiro.net Thu May 12 17:50:06 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 12 May 2016 21:50:06 -0000 Subject: [Bug 1581215] Re: dmarc_moderation_action = wrap message sets no date header References: <20160512210324.21417.38266.malonedeb@wampee.canonical.com> Message-ID: <20160512215007.406.89009.malone@chaenomeles.canonical.com> Normally, the outgoing MTA will set a Date: header in the outgoing message, but it seems preferable to copy the Date: header from the original post. I can't tell if that's what you're asking for, but there are only two options that make sense: copy the original Date: or set the current Date:. Unless there is argument to the contrary, I'll go for copying the original. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Milestone: None => 2.1.23 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1581215 Title: dmarc_moderation_action = wrap message sets no date header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1581215/+subscriptions From 1581215 at bugs.launchpad.net Fri May 13 12:27:42 2016 From: 1581215 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 13 May 2016 16:27:42 -0000 Subject: [Bug 1581215] Re: dmarc_moderation_action = wrap message sets no date header References: <20160512210324.21417.38266.malonedeb@wampee.canonical.com> Message-ID: <20160513162744.32688.56778.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1581215 Title: dmarc_moderation_action = wrap message sets no date header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1581215/+subscriptions From mark at msapiro.net Fri May 13 12:28:48 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 13 May 2016 16:28:48 -0000 Subject: [Bug 1581215] Re: dmarc_moderation_action = wrap message sets no date header References: <20160512210324.21417.38266.malonedeb@wampee.canonical.com> Message-ID: <20160513162849.981.90669.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1581215 Title: dmarc_moderation_action = wrap message sets no date header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1581215/+subscriptions From mark at msapiro.net Tue May 17 01:51:09 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 May 2016 05:51:09 -0000 Subject: [Bug 1582532] [NEW] bin/list_lists and both the listinfo and admin CGI overviews can throw MMUnknownListError Message-ID: <20160517055109.10380.65514.malonedeb@gac.canonical.com> Public bug reported: bin/list_lists and the listinfo and the admin CGIs call Utils.list_names() to get the names of all lists. They then instantiate each list to determine if it meets the conditions for listing. It is possible, particularly in installations with a large number of lists, that a list can be deleted after its name is retrieved and before it is instantiated. Instantiation then throws MMUnknownListError. This should be caught in a try: and the list ignored. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582532 Title: bin/list_lists and both the listinfo and admin CGI overviews can throw MMUnknownListError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582532/+subscriptions From carlos at ttk.pte.hu Tue May 17 13:13:08 2016 From: carlos at ttk.pte.hu (carlos) Date: Tue, 17 May 2016 17:13:08 -0000 Subject: [Bug 1582819] [NEW] subject encoding bug Message-ID: <20160517171308.21663.96093.malonedeb@wampee.canonical.com> Public bug reported: When mailman receives a message with =?ISO-8859-2?Q? in it twice, the second =?ISO-8859-2?Q? gets encoded, and looks like this for example: =3F=3D=3D=3FI?==?iso-8859-2?q?SO-8859-2=3FQ=3F Where the position of the newly inserted encoding is between the "I" and "SO" of the original encoding sign ( which is not recognized by the mailman ) ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582819 Title: subject encoding bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582819/+subscriptions From mark at msapiro.net Tue May 17 14:01:43 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 May 2016 18:01:43 -0000 Subject: [Bug 1582819] Re: subject encoding bug References: <20160517171308.21663.96093.malonedeb@wampee.canonical.com> Message-ID: <20160517180143.476.42330.malone@chaenomeles.canonical.com> I am unable to duplicate exactly what you describe, but I do see an issue in that this: Subject: =?ISO-8859-2?Q?Part_=31_?==?ISO-8859-2?Q?Part_=32_?= gets changed to Subject: [List1] =?iso-8859-2?q?Part_1_=3F=3D=3D=3FISO-8859-2=3FQ=3FPart_2?= however the incoming Subject is non-compliant. RFC2047 section 5(1) says in part: Ordinary ASCII text and 'encoded-word's may appear together in the same header field. However, an 'encoded-word' that appears in a header field defined as '*text' MUST be separated from any adjacent 'encoded-word' or 'text' by 'linear-white-space'. If I add a space as in Subject: =?ISO-8859-2?Q?Part_=31_?= =?ISO-8859-2?Q?Part_=32_?= the result is Subject: [List1] =?iso-8859-2?q?Part_1_Part_2?= which is correct. If you see this issue with an RFC 2047 compliant encoded Subject: or other header, pleas provide the exact header that causes the issue. ** Changed in: mailman Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582819 Title: subject encoding bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582819/+subscriptions From mark at msapiro.net Tue May 17 15:10:54 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 May 2016 19:10:54 -0000 Subject: [Bug 1582856] [NEW] Banned Addresses are only logged from AddMember. Message-ID: <20160517191054.941.41287.malonedeb@chaenomeles.canonical.com> Public bug reported: When the AddMember list method is called with a banned address, MembershipIsBanned is raised and the fact is logged. MembershipIsBanned can also be raised by InviteNewMember, ApprovedAddMember, ChangeMemberAddress and ApprovedChangeMemberAddress and should be logged in those cases too. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582856 Title: Banned Addresses are only logged from AddMember. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582856/+subscriptions From mark at msapiro.net Tue May 17 15:12:35 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 May 2016 19:12:35 -0000 Subject: [Bug 1578450] Re: Mailman should allow setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string. References: <20160505005738.24503.64205.malonedeb@gac.canonical.com> Message-ID: <20160517191235.1141.13218.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1578450 Title: Mailman should allow setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or a null string. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1578450/+subscriptions From 1582532 at bugs.launchpad.net Tue May 17 15:33:39 2016 From: 1582532 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 17 May 2016 19:33:39 -0000 Subject: [Bug 1582532] Re: bin/list_lists and both the listinfo and admin CGI overviews can throw MMUnknownListError References: <20160517055109.10380.65514.malonedeb@gac.canonical.com> Message-ID: <20160517193342.2929.50762.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582532 Title: bin/list_lists and both the listinfo and admin CGI overviews can throw MMUnknownListError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582532/+subscriptions From mark at msapiro.net Tue May 17 15:33:52 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 May 2016 19:33:52 -0000 Subject: [Bug 1582532] Re: bin/list_lists and both the listinfo and admin CGI overviews can throw MMUnknownListError References: <20160517055109.10380.65514.malonedeb@gac.canonical.com> Message-ID: <20160517193353.20962.5982.launchpad@wampee.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582532 Title: bin/list_lists and both the listinfo and admin CGI overviews can throw MMUnknownListError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582532/+subscriptions From 1582856 at bugs.launchpad.net Tue May 17 16:47:07 2016 From: 1582856 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 17 May 2016 20:47:07 -0000 Subject: [Bug 1582856] Re: Banned Addresses are only logged from AddMember. References: <20160517191054.941.41287.malonedeb@chaenomeles.canonical.com> Message-ID: <20160517204708.2929.55574.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582856 Title: Banned Addresses are only logged from AddMember. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582856/+subscriptions From mark at msapiro.net Tue May 17 16:47:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 May 2016 20:47:13 -0000 Subject: [Bug 1582856] Re: Banned Addresses are only logged from AddMember. References: <20160517191054.941.41287.malonedeb@chaenomeles.canonical.com> Message-ID: <20160517204715.8295.59649.launchpad@soybean.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582856 Title: Banned Addresses are only logged from AddMember. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582856/+subscriptions From carlos at ttk.pte.hu Tue May 17 19:14:32 2016 From: carlos at ttk.pte.hu (carlos) Date: Tue, 17 May 2016 23:14:32 -0000 Subject: [Bug 1582819] Re: subject encoding bug References: <20160517171308.21663.96093.malonedeb@wampee.canonical.com> Message-ID: <20160517231433.21523.2179.malone@wampee.canonical.com> Fixed the sender software's encoding issues... ** Changed in: mailman Status: Incomplete => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582819 Title: subject encoding bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582819/+subscriptions From mark at msapiro.net Wed May 18 20:31:28 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 19 May 2016 00:31:28 -0000 Subject: [Bug 1583387] [NEW] Allow list admin to edit more templates. Message-ID: <20160519003128.21201.66213.malonedeb@wampee.canonical.com> Public bug reported: A number of .html and .txt templates can be edited via the web admin GUI to create/update list specific versions of them. Any templates can be edited to make list specific, domain specific or sitewide edited versions, but this requires a level of access that many list admins don't have. The templates that can currently be edited via the web admin GUI are: ('listinfo.html', _('General list information page')), ('subscribe.html', _('Subscribe results page')), ('options.html', _('User specific options page')), ('subscribeack.txt', _('Welcome email text file')), ('masthead.txt', _('Digest masthead')), The following would be useful additions to that list: ('postheld.txt', _('User notice of held post')), ('approve.txt', _('User notice of held subscription')), ('refuse.txt', _('Notice of post refused by moderator')), ('invite.txt', _('Invitation to join list')), ('verify.txt', _('Request to confirm subscription')), ('unsub.txt', _('Request to confirm unsubscription')), ('nomoretoday.txt', _('User notice of autoresponse limit')), ('postack.txt', _('User post acknowledgement')), ('disabled.txt', _('Subscription disabled by bounce warning')), ('admlogin.html', _('Admin/moderator login page')), ('private.html', _('Private archive login page')), ('userpass.txt', _('On demand password reminder')), ** Affects: mailman Importance: Wishlist Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1583387 Title: Allow list admin to edit more templates. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1583387/+subscriptions From 1583387 at bugs.launchpad.net Wed May 18 20:41:55 2016 From: 1583387 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 19 May 2016 00:41:55 -0000 Subject: [Bug 1583387] Re: Allow list admin to edit more templates. References: <20160519003128.21201.66213.malonedeb@wampee.canonical.com> Message-ID: <20160519004157.25337.45703.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1583387 Title: Allow list admin to edit more templates. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1583387/+subscriptions From mark at msapiro.net Wed May 18 20:43:35 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 19 May 2016 00:43:35 -0000 Subject: [Bug 1583387] Re: Allow list admin to edit more templates. References: <20160519003128.21201.66213.malonedeb@wampee.canonical.com> Message-ID: <20160519004336.784.94919.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1583387 Title: Allow list admin to edit more templates. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1583387/+subscriptions From carlos at ttk.pte.hu Thu May 19 12:02:40 2016 From: carlos at ttk.pte.hu (carlos) Date: Thu, 19 May 2016 16:02:40 -0000 Subject: [Bug 1582819] Re: subject encoding bug References: <20160517171308.21663.96093.malonedeb@wampee.canonical.com> Message-ID: <20160519160241.8440.16085.malone@soybean.canonical.com> New, fixed subject example sent (from the sent file directly): =?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?= =?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zi?=s Received back from mailman (from the mailfile directly): [Xxx-yyyyyyyy] =?iso-8859-2?q?PIVOT_kutat=E1sfinan_=3D=3FISO-8859?= =?iso-8859-2?q?-2=3FQ=3Fsz=3DEDroz=3DE1si=5Fadatb=3DE1zi=3F=3Ds?= So something is not correct :( ** Changed in: mailman Status: Invalid => New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582819 Title: subject encoding bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582819/+subscriptions From mark at msapiro.net Thu May 19 12:44:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 19 May 2016 16:44:46 -0000 Subject: [Bug 1582819] Re: subject encoding bug References: <20160517171308.21663.96093.malonedeb@wampee.canonical.com> Message-ID: <20160519164446.303.13485.malone@chaenomeles.canonical.com> =?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?= =?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zi?=s is still non-compliant. It is too long: RFC2047 section 2 says in part While there is no limit to the length of a multiple-line header field, each line of a header field that contains one or more 'encoded-word's is limited to 76 characters. but that is not the issue here. The issue is the same as before. The final 's' is not separated from the preceding encoded word by linear white space. If the header were Subject: =?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?= =?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zi?= s Mailman would produce Subject: [List1] =?iso-8859-2?q?PIVOT_kutat=E1sfinansz=EDroz=E1si_adatb=E1?= =?iso-8859-2?q?zi_s?= which is not quite what you want as it decodes to Subject: [List1] PIVOT kutat?sfinansz?roz?si adatb?zi s and you presumably want 'adatb?zis', not 'adatb?zi s'. There are always whitespace issues when mixing encoded words and plain text in one header. The proper encoding of that header is Subject: =?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?= =?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zis?= Granted, various MUAs are more forgiving of the defects, but the Mailman issue is really in the underlying Python email package which insists that the terminating ?= be followed by white space in order that the encoded word be recognized as such. ** Changed in: mailman Status: New => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1582819 Title: subject encoding bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1582819/+subscriptions From rsurette at doleandbailey.com Thu May 26 10:57:39 2016 From: rsurette at doleandbailey.com (Rick Surette) Date: Thu, 26 May 2016 14:57:39 -0000 Subject: [Bug 1586070] [NEW] Non Member Filters Not Working with Special Characters Message-ID: <20160526145739.17845.89269.malonedeb@soybean.canonical.com> Public bug reported: When using the @ symbol to Allow another mailing list to send to that list, any email address from the allowed to send list still gets held for moderation. EX: list2 at mycompany.com has the following in the List of non-member addresses whose postings should be automatically accepted. @list1 at mycompany.com Any member of list1 should now be allowed to send to list2. But, Members from list1 are still getting held for moderation??? Any help would be appreciated. Thank You, Rick Surette ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586070 Title: Non Member Filters Not Working with Special Characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586070/+subscriptions From mark at msapiro.net Thu May 26 11:54:34 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 26 May 2016 15:54:34 -0000 Subject: [Bug 1586070] Re: Non Member Filters Not Working with Special Characters References: <20160526145739.17845.89269.malonedeb@soybean.canonical.com> Message-ID: <20160526155434.17845.65403.malone@soybean.canonical.com> The @listname syntax uses just a list name in the same Mailman installation, not a list posting address. If you have standard GNU Mailman, this should be just '@list1' in this case. Please clarify whether this is the issue or if you have a Mailman which is modified to allow the same name in different virtual hosts by appending '@domain' so that the actual list name is list1 at mycompany.com. ** Changed in: mailman Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586070 Title: Non Member Filters Not Working with Special Characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586070/+subscriptions From rroopstr at gmail.com Thu May 26 15:42:56 2016 From: rroopstr at gmail.com (ruben) Date: Thu, 26 May 2016 19:42:56 -0000 Subject: [Bug 1445764] Re: "The executable /usr/bin/python3.4 does not exist" error when Installing Mailman 3 on Centos 7 References: <20150418121916.32277.67461.malonedeb@gac.canonical.com> Message-ID: <20160526194256.27827.19853.malone@gac.canonical.com> Hi, I am just installing Mailman on CentOs 7 and already installed Python 3.5 and get the exact same output after typing buildout: Installing mailman. The executable python3.4 (from --python=python3.4) does not exist /tmp/tmptaILCi/run: line 2: /root/mailman-bundler/venv-3.4/bin/pip: No such file or directory While: Installing mailman. An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "/root/Python-3.5.0/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1992, in main getattr(buildout, command)(args) File "/root/Python-3.5.0/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 666, in install installed_files = self[part]._call(recipe.install) File "/root/Python-3.5.0/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1407, in _call return f() File "/root/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install self.execute() File "/root/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute run_commands(cmds, self.shell) File "/root/mailman-bundler/eggs/collective.recipe.cmd-0.11-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands check_call('%s %s' % (shell, tmpfile), shell=True) File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command 'sh /tmp/tmptaILCi/run' returned non-zero exit status 127 What to do now? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1445764 Title: "The executable /usr/bin/python3.4 does not exist" error when Installing Mailman 3 on Centos 7 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1445764/+subscriptions From mark at msapiro.net Thu May 26 16:16:04 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 26 May 2016 20:16:04 -0000 Subject: [Bug 1445764] Re: "The executable /usr/bin/python3.4 does not exist" error when Installing Mailman 3 on Centos 7 References: <20150418121916.32277.67461.malonedeb@gac.canonical.com> Message-ID: <20160526201605.17994.77801.malone@soybean.canonical.com> Apparently mailman-bundler is not (yet) compatible with Python 3.5. This is no longer the appropriate place for any mailman3 related issues. Please resubmit this issue at . -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1445764 Title: "The executable /usr/bin/python3.4 does not exist" error when Installing Mailman 3 on Centos 7 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1445764/+subscriptions From rroopstr at gmail.com Thu May 26 16:41:59 2016 From: rroopstr at gmail.com (ruben) Date: Thu, 26 May 2016 20:41:59 -0000 Subject: [Bug 1445764] Re: "The executable /usr/bin/python3.4 does not exist" error when Installing Mailman 3 on Centos 7 References: <20150418121916.32277.67461.malonedeb@gac.canonical.com> <20160526201605.17994.77801.malone@soybean.canonical.com> Message-ID: thank you Mark Rub?n Rivero Capriles http://www.rubenrivero.net (blog global - espa?ol) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) 2016-05-26 16:16 GMT-04:00 Mark Sapiro : > Apparently mailman-bundler is not (yet) compatible with Python 3.5. > > This is no longer the appropriate place for any mailman3 related issues. > Please resubmit this issue at bundler/issues>. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1445764 > > Title: > "The executable /usr/bin/python3.4 does not exist" error when > Installing Mailman 3 on Centos 7 > > Status in GNU Mailman: > Fix Committed > > Bug description: > Short summary: when installing Mailman 3 onto new Centos 7 box using > manual at page > http://mailman-bundler.readthedocs.org/en/latest/ > > after step > > (venv)[root at host mailman-bundler]# pip install zc.buildout > (venv)[root at host mailman-bundler]# buildout > > getting the error: > > --- > Installing mailman. > The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) > does not exist > /tmp/tmpePyrQ3/run: line 2: > /usr/local/src/mailman-bundler/venv-3.4/bin/pip: No such file or directory > While: > Installing mailman. > --- > > Now in details: > > Fresh new CentOS Linux release 7.1.1503 (Core) installed as kvm guest. > > System python package installed: python-2.7.5-16.el7.x86_64 > > Python 3.4.3 was installed by commands: > > [root at host ~]# cd /usr/local/src > [root at host src]# curl -O > https://www.python.org/ftp/python/3.4.3/Python-3.4.3.tgz > [root at host src]# tar -xvzf Python-3.4.3.tgz > [root at host src]# cd /usr/local/src/Python-3.4.3 > [root at host Python-3.4.3]# ./configure --enable-shared > --prefix=/usr/local LDFLAGS="-Wl,-rpath /usr/local/lib" > [root at host Python-3.4.3]# make > [root at host Python-3.4.3]# make altinstall > > Virtualenv was installed from package > python-virtualenv.noarch 0:1.10.1-2.el7 > with dependant python-devel.x86_64 0:2.7.5-16.el7 > > Then everything was don according > http://mailman-bundler.readthedocs.org/en/latest/ > until the error mentioned above occurred. > > When I did > (venv)[root at host mailman-bundler]# ln -s /usr/local/bin/python3.4 > /usr/bin/python3.4 > > I've got another error: > --- > (venv)[root at host mailman-bundler]# buildout > Develop: '/usr/local/src/mailman-bundler/.' > warning: no files found matching '*.in' under directory 'mailman_bundler' > warning: no files found matching '*.in' under directory 'deployment' > warning: no files found matching 'deployment/mailman-web.logrotate.conf' > Updating mailman-web. > Updating main. > Installing mailman. > Running virtualenv with interpreter /usr/bin/python3.4 > Using base prefix '/usr/local' > New python executable in > /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 > Also creating executable in > /usr/local/src/mailman-bundler/venv-3.4/bin/python > Failed to import the site module > Traceback (most recent call last): > File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site.py", > line 67, in > import os > File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/os.py", > line 616, in > from _collections_abc import MutableMapping > ImportError: No module named '_collections_abc' > ERROR: The executable > /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 is not functioning > ERROR: It thinks sys.prefix is '/usr/local/src/mailman-bundler' (should > be '/usr/local/src/mailman-bundler/venv-3.4') > ERROR: virtualenv is not compatible with this system or executable > /tmp/tmpTl6JgC/run: line 2: > /usr/local/src/mailman-bundler/venv-3.4/bin/pip: No such file or directory > While: > Installing mailman. > > An internal error occurred due to a bug in either zc.buildout or in a > recipe being used: > Traceback (most recent call last): > File > "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", > line 1946, in main > getattr(buildout, command)(args) > File > "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", > line 626, in install > installed_files = self[part]._call(recipe.install) > File > "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", > line 1370, in _call > return f() > File > "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", > line 56, in install > self.execute() > File > "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", > line 69, in execute > run_commands(cmds, self.shell) > File > "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", > line 39, in run_commands > check_call('%s %s' % (shell, tmpfile), shell=True) > File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call > raise CalledProcessError(retcode, cmd) > CalledProcessError: Command 'sh /tmp/tmpTl6JgC/run' returned non-zero > exit status 127 > --- > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1445764/+subscriptions > -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1445764 Title: "The executable /usr/bin/python3.4 does not exist" error when Installing Mailman 3 on Centos 7 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1445764/+subscriptions From mark at msapiro.net Fri May 27 14:47:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 27 May 2016 18:47:40 -0000 Subject: [Bug 1586505] [NEW] Scrubber links in archives are in the poster's language rather than the list's preferred_language. Message-ID: <20160527184740.25918.22343.malonedeb@chaenomeles.canonical.com> Public bug reported: The Runner _onefile method inherited by ArchRunner sets the i18n language to that of the message's sender. This is the language context in effect when Scrubber is called to scrub the message to plain text. It should be set to the list's preferred language. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Description changed: The Runner _onefile method inherited by ArchRunner sets the i18n - language to that of the messages sender. This is the language context in - effect when Scrubber is called to scrub the message to plain text. It + language to that of the message's sender. This is the language context + in effect when Scrubber is called to scrub the message to plain text. It should be set to the list's preferred language. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586505 Title: Scrubber links in archives are in the poster's language rather than the list's preferred_language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586505/+subscriptions From 1586505 at bugs.launchpad.net Fri May 27 15:19:23 2016 From: 1586505 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 27 May 2016 19:19:23 -0000 Subject: [Bug 1586505] Re: Scrubber links in archives are in the poster's language rather than the list's preferred_language. References: <20160527184740.25918.22343.malonedeb@chaenomeles.canonical.com> Message-ID: <20160527191925.19961.92992.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586505 Title: Scrubber links in archives are in the poster's language rather than the list's preferred_language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586505/+subscriptions From mark at msapiro.net Fri May 27 15:19:32 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 27 May 2016 19:19:32 -0000 Subject: [Bug 1586505] Re: Scrubber links in archives are in the poster's language rather than the list's preferred_language. References: <20160527184740.25918.22343.malonedeb@chaenomeles.canonical.com> Message-ID: <20160527191933.22246.80176.launchpad@wampee.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586505 Title: Scrubber links in archives are in the poster's language rather than the list's preferred_language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586505/+subscriptions From rsurette at doleandbailey.com Tue May 31 16:47:28 2016 From: rsurette at doleandbailey.com (Rick Surette) Date: Tue, 31 May 2016 20:47:28 -0000 Subject: [Bug 1586070] Re: Non Member Filters Not Working with Special Characters References: <20160526145739.17845.89269.malonedeb@soybean.canonical.com> Message-ID: <20160531204728.27365.11609.malone@gac.canonical.com> Not sure what you mean by "the same mailman installation"?? I am using the standard mailman from Bluehost. We have not modified mailman at all. I may not have explained my situation clearly enough. I will try again. I have a list list1 at mycompany.com with 5 people. It is a members only mailing list. Only those 5 can send to the list. I have another list list2 at mycompany.com with 50 people. There is an option for Allowing non members to send to a list. I do not want to type all 50 email addresses in the allow to send box. There is a help option that stated if you use the @ symbol and a list name, all email addresses on the list will be allowed to send. I tried just @list2 and received the same results. I contacted Bluehost support and was told I needed the whole list name after the @ symbol (@list2 at mycompany.com). Therefore I typed @list2 at mycompany.com as the allowed to send address. These email addresses are getting held for moderation as non members trying to send to a members only list. Thank you again, Rick Surette -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586070 Title: Non Member Filters Not Working with Special Characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586070/+subscriptions From mark at msapiro.net Tue May 31 17:31:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 31 May 2016 21:31:40 -0000 Subject: [Bug 1586070] Re: Non Member Filters Not Working with Special Characters References: <20160526145739.17845.89269.malonedeb@soybean.canonical.com> <20160531204728.27365.11609.malone@gac.canonical.com> Message-ID: <52e593da-c443-2a58-ba64-d26b5df0674f@msapiro.net> You need to use the same listname as in URLs for the web admin UI for the list. I don't know how Bluehost uniquifies list names, but it is likely something like list2-mycompany.com or list2_mycompany.com. I *think* Bluehost uses cPanel Mailman and if this is the case, use @list2_mycompany.com, but in any case use exactly the same listname as in the listname part of URLs for the web UI. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586070 Title: Non Member Filters Not Working with Special Characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586070/+subscriptions From mark at msapiro.net Tue May 31 17:46:01 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 31 May 2016 21:46:01 -0000 Subject: [Bug 1586070] Re: Non Member Filters Not Working with Special Characters References: <20160526145739.17845.89269.malonedeb@soybean.canonical.com> Message-ID: <20160531214602.26607.45478.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Incomplete => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586070 Title: Non Member Filters Not Working with Special Characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586070/+subscriptions From rsurette at doleandbailey.com Tue May 31 18:07:08 2016 From: rsurette at doleandbailey.com (Rick Surette) Date: Tue, 31 May 2016 22:07:08 -0000 Subject: [Bug 1586070] Re: Non Member Filters Not Working with Special Characters References: <20160526145739.17845.89269.malonedeb@soybean.canonical.com> Message-ID: <20160531220708.25887.75344.malone@chaenomeles.canonical.com> cPanel is correct. As well as the url, it is the _ in cPanel. I have changed the lists from list2 at mycompany.com TO list2_mycompany.com I will test and reply with my results. Thank You for your Prompt responses! Rick Surette -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1586070 Title: Non Member Filters Not Working with Special Characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1586070/+subscriptions