Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Problem with list creation

by Stephen J. Turnbull

Mark Sapiro writes: > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > We increased timeout in mailman.cfg This looks like the issue in Shashikanth's post, too: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… They are also creating more than 1000 lists. Do we know why these timeouts are happening? (Search for "list creation times out" returns no results in either core or Postorius issues.)

5 years, 6 months

[MM3-users] Re: Template path

by Seth Seeger

> On Sep 17, 2020, at 12:54 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Something appears to be trying to connect to REST on port 8000 I found this (older) email: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… that does say that the POSTORIUS_TEMPLATE_BASE_URL should be “http://mailman-web:8000” Seth

5 years, 6 months

[MM3-users] Re: Office365 posts shunted (authres.core.SyntaxError)

by Stephen J. Turnbull

Mark Sapiro writes: > I think that's fine. Also, you should look at > <https://gitlab.com/mailman/mailman/-/issues/765>. I agree with Mark. I was pretty sure something like that would work, but I haven't looked at the code in a while, so didn't know exactly where to patch. I'll take a look at it tomorrow, and see if I can spot any edge cases, but that's probably as simple as it looks. Steve

5 years, 6 months

[MM3-users] Re: Unable to remove non-member

by Brian Carpenter

On 9/29/20 12:40 AM, Mark Sapiro wrote: > Is that all it said? The code says it is > > The user could not be removed: <error message> > > Where <error message> is the relevant HTTP error. It says: The user could not be removed: Nothing comes after the colon. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

[MM3-users] Re: Unable to remove non-member

by Brian Carpenter

On 9/29/20 1:18 PM, Mark Sapiro wrote: > I see the issue. when mailmanclient processes the delete request from > Postorius it calls the REST API DELETE method with the URL > lists/<listname>/<role>/<address> and the address is `quoted` with > urllib.parse.quote_plus, co in this case, the URL becomes > lists/<listname>/nonmember/z_email%2Fdomain.org.za(a)domain.org.za > > This is all fine except the REST API doesn't call > urllib.parse.unquote_plus to change the %2F back to slash. This is now > reported at<https://gitlab.com/mailman/mailman/-/issues/774>. Thanks Mark! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Brian Carpenter

On 9/30/20 11:52 AM, Mark Sapiro wrote: >> 2. I would find the postorius UI much easier to cope with if the >> default template was 'populated' into the UI wherever it was non-blank, >> rather than the UI starting off as if no templates were defined at all. Our Affinity admin interface does that: Affinity Template -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:08:58 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Since you are running the command as user `mailman`, the file must be > readable by that user. Is it? > ls -hl members.txt: -rw-rw-r--. 1 mailman mailman 78 Oct 14 16:15 members.txt See file permissions and ownership above. Unless mailman3 expects a certain Selinux context. -- Onyeibo

5 years, 5 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:08:58 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > > Since you are running the command as user `mailman`, the file must be > readable by that user. Is it? > This question inspired me to run mailman3 directly. It worked! However, I had to execute mailman3 from: /usr/libexec/mailman3/mailman rather than: /usr/bin/mailman3 (or just, ... mailman3). What is the recommended way to run mailman3 please?

5 years, 5 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > In my case, the `mailman` command I run invokes a bash file that looks like > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman \ > -C "/opt/mailman/mm/mailman.cfg" \ > $@ IIRC shell scripts have a race condition, although I don't recall the conditions under which it's exploitable. Perhaps SELinux is sensitive to that. I don't really see how we can take responsibility for such issues except to document it as one user's experience.

5 years, 5 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/19/20 10:23 PM, Mark Sapiro wrote: > And the import21 created the user and address records for this user. Does the same thing for a new subscriber as well. So there is no pathway to change a real name that is associated with an email address. None. Zilch. Mailman 2 made this so easy and Mailman 3 made it impossible. I will let someone else file the bug report. You don't really think that this is an issue which means it will be years before it is addressed. So I will save me some time. I will learn to live with it. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

Search results for query "sapiro"