From 1609516 at bugs.launchpad.net Fri May 10 00:20:56 2019 From: 1609516 at bugs.launchpad.net (Bug Watch Updater) Date: Fri, 10 May 2019 04:20:56 -0000 Subject: [Bug 1609516] Re: [needs-packaging] GNU Mailman v3 References: <20160803182324.17278.47145.malonedeb@chaenomeles.canonical.com> Message-ID: <155746205845.17538.10385426572315987416.launchpad@loganberry.canonical.com> Launchpad has imported 10 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1363871. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2016-08-03T18:41:46+00:00 kxra wrote: Description of problem: Mailman 3 is really a suite of 5 tools: * The core, which provides the mail delivery engine, the unified user model, moderation and modification of email messages, and interfaces to external archivers; * Postorius, our new Django-based web user interface for users and list administrators; * HyperKitty, our new Django-based web archiver, providing rich access to the historical record of mailing list traffic; * mailman.client, the official Python bindings to the core's REST API; * mailman-bundler, a set of scripts to make it easy to deploy the full suite inside Python virtual environments. What's new about Mailman 3? Well, lots! Some highlights include: * Backed by a relational database; * True support for multiple domains, with no cross-domain mailing list naming restrictions; * One user account to manage all your subscriptions on a site; * The core's functionality exposed through an administrative REST+JSON API; * All passwords hashed by default, and no monthly password reminders! * Users can post to lists via the web interface; * Built-in archive searching! and more. Tons more. URL: https://www.gnu.org/software/mailman/ Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/1 ------------------------------------------------------------------------ On 2016-08-04T07:23:02+00:00 aurelien wrote: I've been working on Mailman3 for a while now, and I have packaged it (and all its dependencies), and I intend on getting it into Fedora. The thing is, there's a loooot of new dependencies that need to be in there too. I haven't tried to push them at the moment because the dependencies have been changing a lot until recently (they still are a bit, but it's low enough now). I intend to work with Jan on that (we haven't talked about this in a while ;-) ) FYI I have a Mailman3 / Postorius / HyperKitty repo here: https://repos.fedorapeople.org/abompard/hyperkitty/ It's for EPEL7, but it should rebuild properly on Fedora (it's even easier because more deps are included). I've started checking which deps are into Fedora and on which version, so I can request reviews or updates on them. That's where I am today. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/3 ------------------------------------------------------------------------ On 2017-05-31T01:07:23+00:00 kxra wrote: Hi, has there been progress on packages being accepted into the main repos? Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/4 ------------------------------------------------------------------------ On 2017-05-31T06:57:03+00:00 aurelien wrote: Yes, there's progress, but there are still some dependencies being packaged and reviewed. If you want to help, please check out https://lstu.fr/abompard-package-review. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/5 ------------------------------------------------------------------------ On 2017-11-16T18:34:25+00:00 bcotton wrote: This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/6 ------------------------------------------------------------------------ On 2017-12-12T10:28:12+00:00 bcotton wrote: Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/7 ------------------------------------------------------------------------ On 2017-12-13T04:17:35+00:00 troycurtisjr wrote: Is the idea here to go to mailman 3.x version and bypass the newer 2.x versions that aren't yet packaged for Fedora? According to the provided link, there don't appear to be any outstanding dep package reviews, so is the mailman3 update happening soon? Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/8 ------------------------------------------------------------------------ On 2018-02-20T15:38:05+00:00 bcotton wrote: This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/9 ------------------------------------------------------------------------ On 2018-04-10T07:38:43+00:00 pzhukov wrote: (In reply to Aurelien Bompard from comment #3) > Yes, there's progress, but there are still some dependencies being packaged > and reviewed. If you want to help, please check out > https://lstu.fr/abompard-package-review. Thanks! Hi Aurelien, Are you planning to go through formal review of the rest of packages? As I can see Core has all deps packaged in Fedora. As Python3 is deprecated we can use generic name (mailman) and not introduce new package. Are you ok with that? Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/10 ------------------------------------------------------------------------ On 2019-05-02T21:12:21+00:00 bcotton wrote: This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1609516/comments/11 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1609516 Title: [needs-packaging] GNU Mailman v3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1609516/+subscriptions From 266754 at bugs.launchpad.net Fri May 17 13:31:38 2019 From: 266754 at bugs.launchpad.net (Siridech Kingsuwan) Date: Fri, 17 May 2019 17:31:38 -0000 Subject: [Bug 266754] Re: Add names to roster References: <20080905194238.1806.75744.launchpad@forster.canonical.com> Message-ID: <155811429919.21246.6312591487812999177.launchpad@chaenomeles.canonical.com> *** This bug is a duplicate of bug 558122 *** https://bugs.launchpad.net/bugs/558122 ** Also affects: ubuntu 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/266754 Title: Add names to roster To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266754/+subscriptions From 1830182 at bugs.launchpad.net Thu May 23 05:25:37 2019 From: 1830182 at bugs.launchpad.net (Isuru Rupasinghe) Date: Thu, 23 May 2019 09:25:37 -0000 Subject: [Bug 1830182] [NEW] mails getting queued "he user you are trying to contact is receiving mail at a rate that 450-4.2.1" Message-ID: <155860353728.15187.5437282079506261362.malonedeb@gac.canonical.com> Public bug reported: Hi Support, 8560E2170B 3716 Thu May 23 00:56:21 mailman-bounces at mail.wso2.org (host ASPMX.L.GOOGLE.com[173.194.204.26] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, please 450-4.2.1 visit 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate f15si5167250qkg.48 - gsmtp (in reply to RCPT TO command)) techops at wso2.com Can you please advice why we are going through this error causing mails to queue. Thanks & Regards, Isuru ** 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/1830182 Title: mails getting queued "he user you are trying to contact is receiving mail at a rate that 450-4.2.1" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions From 1830182 at bugs.launchpad.net Thu May 23 06:09:38 2019 From: 1830182 at bugs.launchpad.net (Isuru Rupasinghe) Date: Thu, 23 May 2019 10:09:38 -0000 Subject: [Bug 1830182] Re: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" References: <155860353728.15187.5437282079506261362.malonedeb@gac.canonical.com> Message-ID: <155860617893.15038.15651809933705824539.launchpad@wampee.canonical.com> ** Summary changed: - mails getting queued "he user you are trying to contact is receiving mail at a rate that 450-4.2.1" + mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.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/1830182 Title: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions From mark at msapiro.net Thu May 23 09:56:26 2019 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 23 May 2019 13:56:26 -0000 Subject: [Bug 1830182] Re: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" References: <155860353728.15187.5437282079506261362.malonedeb@gac.canonical.com> Message-ID: <155861978723.15348.9470470342083666211.malone@wampee.canonical.com> This is not a bug in mailman. This is a problem with the specific user. Google mail is not accepting mail for that user for the reason stated. If this affects multiple users receiving mail from Mailman, and you think it is Mailman sending at too great a rate, why is that happening? Are these list posts or something else. Possibly someone is mail bombing the user by submitting subscription requests to your Mailman lists. ** 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/1830182 Title: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions From 1830182 at bugs.launchpad.net Fri May 24 00:49:07 2019 From: 1830182 at bugs.launchpad.net (Isuru Rupasinghe) Date: Fri, 24 May 2019 04:49:07 -0000 Subject: [Bug 1830182] Re: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" References: <155860353728.15187.5437282079506261362.malonedeb@gac.canonical.com> <155861978723.15348.9470470342083666211.malone@wampee.canonical.com> Message-ID: Hi Mark, Sorry about it, it was one of exim mail service issue i think, i think we sorted it. Thanks & Regards, On Thursday, May 23, 2019, Mark Sapiro wrote: > This is not a bug in mailman. This is a problem with the specific user. > Google mail is not accepting mail for that user for the reason stated. > > If this affects multiple users receiving mail from Mailman, and you > think it is Mailman sending at too great a rate, why is that happening? > Are these list posts or something else. Possibly someone is mail bombing > the user by submitting subscription requests to your Mailman lists. > > ** Changed in: mailman > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1830182 > > Title: > mails getting queued "The user you are trying to contact is receiving > mail at a rate that 450-4.2.1" > > Status in GNU Mailman: > Incomplete > > Bug description: > Hi Support, > > 8560E2170B 3716 Thu May 23 00:56:21 mailman-bounces at mail.wso2.org > (host ASPMX.L.GOOGLE.com[173.194.204.26] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, please 450-4.2.1 visit 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate f15si5167250qkg.48 - gsmtp (in reply to RCPT TO command)) > techops at wso2.com > > > Can you please advice why we are going through this error causing mails to queue. > > Thanks & Regards, > > Isuru > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions > -- *Isuru Rupasinghe* *Systems EngineerWSO2 Inc.: http://wso2.com lean.enterprise.middle-wareOn-Call Number - +94 76 841 4562mobile: +94 77 590 4545* *office: +94 11 214 5345 / +94 11 7**43 5800 ext: 1005739* -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1830182 Title: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions From mark at msapiro.net Fri May 24 13:34:21 2019 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 24 May 2019 17:34:21 -0000 Subject: [Bug 1830182] Re: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" References: <155860353728.15187.5437282079506261362.malonedeb@gac.canonical.com> Message-ID: <155871926331.16532.13591958606150499116.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/1830182 Title: mails getting queued "The user you are trying to contact is receiving mail at a rate that 450-4.2.1" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830182/+subscriptions From 1830663 at bugs.launchpad.net Mon May 27 22:36:22 2019 From: 1830663 at bugs.launchpad.net (griswolf) Date: Tue, 28 May 2019 02:36:22 -0000 Subject: [Bug 1830663] [NEW] admin email interface fails w/ password holding space Message-ID: <155901098287.16454.1472854820296203607.malonedeb@chaenomeles.canonical.com> Public bug reported: The only way to get access to the list of users for my group is via the email interface "who" request. Mailman quite properly allows me to set arbitrary passwords that may have spaces. However the email interface becomes confused when I send who This is just one password address=someone at somewhere.me It seems like the parser should correctly note the "address=" keyword and figure out that everything (space delimited) between "who" and "address" is password. OR it should allow shell-like quoting. ** 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/1830663 Title: admin email interface fails w/ password holding space To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830663/+subscriptions From mark at msapiro.net Tue May 28 20:50:10 2019 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 May 2019 00:50:10 -0000 Subject: [Bug 1830663] Re: admin email interface fails w/ password holding space References: <155901098287.16454.1472854820296203607.malonedeb@chaenomeles.canonical.com> Message-ID: <155909101116.25445.1609100839405977947.malone@gac.canonical.com> The issue is the whole command line is 'parsed' into tokens by CommandRunner using split(). CommandRunner has no knowledge of the syntax of the command. It only knows the first token is the command name and it passes the list of tokens to the command. Thus, the 'who' command gets ['This', 'is', 'just', 'one', 'password', 'address=someone at somewhere.me']. Even if it were to recognize that arg[5] is an 'address=' and assume arg[:5] is the words of the password, it still doesn't know how to reassemble them as there may have been multiple spaces between words. The correct fix would be to teach CommandRunner about quotes and escapes so it could correctly parse 'How\'s this for a password' into one token. This is complex, but I'll work on it. I'm curious though as to why you can't get the roster via the web UI. ** Changed in: mailman Status: New => Confirmed ** 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/1830663 Title: admin email interface fails w/ password holding space To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830663/+subscriptions From 1830663 at bugs.launchpad.net Tue May 28 23:42:06 2019 From: 1830663 at bugs.launchpad.net (griswolf) Date: Wed, 29 May 2019 03:42:06 -0000 Subject: [Bug 1830663] Re: admin email interface fails w/ password holding space References: <155901098287.16454.1472854820296203607.malonedeb@chaenomeles.canonical.com> Message-ID: <155910132701.12481.12693084744640926935.malone@soybean.canonical.com> Thanks. If you can reasonably peel off part of your "work on it" I'd be happy to lay a hand to it. I've been developing in python now for a decade more or less (with intervals when Java was shop-required). Just finished moving my personal library of tools to Python 3, but only aliased "python" to python3 last week. Oh, and I'm retired, so there is free time, albeit not as much as folks with jobs think. What I'd really like is a web interface such as I provide for the dance weekend pages I administer: A button that offers "download as CSV" for the Membership list. Barring that, accessing all 787 list members, one page at a time, scraping the pages into an editor, and then doing what I need to do would be a serious PITA. The "who" command is _exactly_ what I want. So, until now, my work process has been. And: I have no sysadmin access to the list: On that server I'm a pure (admin-level for mailman) user. try it (about annually, so I forget between) realize it failed realize what the problem is change the password grab the info change the password again As you can imagine, this is less than ideal. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1830663 Title: admin email interface fails w/ password holding space To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830663/+subscriptions From mark at msapiro.net Wed May 29 00:50:04 2019 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 May 2019 04:50:04 -0000 Subject: [Bug 1830663] Re: admin email interface fails w/ password holding space References: <155901098287.16454.1472854820296203607.malonedeb@chaenomeles.canonical.com> Message-ID: <155910540492.12854.12165523643450467367.malone@soybean.canonical.com> > Oh, and I'm retired, so there is free time, albeit not as much as folks with jobs think. I'm retired too (27 + years). You've probably heard the line "There are two kinds of retired people - those who are bored stiff and those who can't figure out how they ever had time to go to work." I think we're both in the latter category. > What I'd really like is a web interface such as I provide for the dance weekend pages I administer: A button that offers "download as CSV" for the Membership list. See the script at https://www.msapiro.net/scripts/mailman- subscribers3.py (mirrored at https://fog.ccsf.edu/~msapiro/scripts /mailman-subscribers3.py ) If you have admin access to the list, it will screen scrape the admin membership list and give you what you want. As far as fixing this bug, I have this idea: import re # See https://www.metaltoad.com/blog/regex-quoted-string-escapable-quotes qre = re.compile(r"""((? Message-ID: <155910613181.25407.8556062731454063429.malone@gac.canonical.com> Also, the roster (http(s)://example.com/roster/list_name), as opposed to the admin membership list, is all on one page. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1830663 Title: admin email interface fails w/ password holding space To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830663/+subscriptions From mark at msapiro.net Wed May 29 10:37:45 2019 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 May 2019 14:37:45 -0000 Subject: [Bug 1830663] Re: admin email interface fails w/ password holding space References: <155901098287.16454.1472854820296203607.malonedeb@chaenomeles.canonical.com> Message-ID: <155914066600.24515.18250279945101588647.malone@gac.canonical.com> Because of the ambiguity over a quoted password vs. a password containing quotes, I don't think I can fix this without potentially breaking things. Also, see https://wiki.list.org/x/4030569 for other ways to get a member list. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1830663 Title: admin email interface fails w/ password holding space To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1830663/+subscriptions