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

[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, 1 month

[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, 1 month

[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, 1 month

[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, 1 month

[MM3-users] Re: mailman import21

by Brian Carpenter

On 10/11/20 11:40 AM, Mark Sapiro wrote: > As I said, (msg|digest)_(header|footer) are MM 2.1 list attributes, not > templates. Those, and I think only those, are converted to > var/templates/lists/listname/lc/ templates by import21. I forgot to say thank you for the above information. That makes sense of what I am seeing with imports. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Member Issue Discovered

by Mark Dadgar

On Oct 20, 2020, at 8:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > Even in mailman 2.1, while a list admin could go to a user's options > page for the list and change things, the "change globally" check boxes > only worked for the user, not for the list admin. That was by design!? As an admin, that was so irritating. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 1 month

[MM3-users] Re: migration from 2.1 - owners and moderators

by Alex Schuilenburg

On 24/10/2020 19:29, Mark Sapiro wrote: > Those are Django tasks and don't affect this. You also need to run > `mailman digests --periodic` to send periodic digests (see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>) > and `mailman notify` to send periodic moderator notices (see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>). Thanks for reminding me I need to upgrade :-) 3.2.1 Does not have "notify" I'll wager that the sporadic notification messages are down to this version, so upgrading just bumped up my todo. -- Alex

5 years, 1 month

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Stephen J. Turnbull

Mark Sapiro writes: > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. Shouldn't Postorius's setup.py be checking for this? Steve

5 years, 1 month

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 5:05 PM, Mark Sapiro wrote: > Why do you keep bringing this up? The current design of Mailman core > does not remove the user when the user unsubscribes from a list, even if > it is their only subscription. We know you don't like this behavior, but > there are reasons for it. > > On the other hand, when a user removes their account, the circumstance > is different and we do remove the user's information in this case > because that's what the user asked for. Just clarifying Mark. I was surprised by your answer that's all. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Torge Riedel

Am 28.10.20 um 20:09 schrieb Mark Sapiro: > What does your systemd mailman.service script contain for ExecReload? ExecReload=/opt/mailman/core/bin/mailman.sh restart > What crons run at the time of the anomalous timestamps? I checked that and came to the idea, that there might by a reboot of the machine at that time. Maybe it is caused by start mailman & postfix at the same time or not in the "correct" order (postfix first, then mailman)? Kind regards Torge

5 years

Search results for query "sapiro"