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

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/24/20 4:34 AM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > I am not sure. How can I check that if it is from unshunting ? It is from unshunting if you or someone else manually ran `mailman unshunt`. I was trying to understand how Mailman would be trying to add a message for the digest to a non-existent list. One way I think is if a message to be added was shunted from the digest queue and then unshunted after the list was deleted. This however seems unlikely. Another possibility is mailman was stopped with an entry for the list in the digest queue and started again after deleting the list. This seems more likely. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by Mark Sapiro

On 7/21/22 08:09, skenny(a)scss.tcd.ie wrote: > > I was afraid that by removing the default database that comes with the database container, I'd be losing some vital information that may have been added or changed in the database config since I first got my production server working 2 years ago - changed field values, extra table columns ... ? Does that make any sense? I've a hazy understanding at best of the minutiae of databases, being honest. You should run your Django admin command with the `migrate` argument, however you run that in your container after you import the database to apply any necessary migrations. This should fix any issues with added columns or changed definitions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Audit Logs

by Mark Sapiro

On 1/30/19 11:53 AM, Enrique Terrazas wrote: > Greetings, > I’m wondering if there is an “audit log” of sorts to see who made changes to a specific list. What we’re after is a way of tracking, in case requested, who made additions or deletions of subscribers etc. I can see the DELETE commands in the ./mailman/logs/mailman.log file but it doesn’t specifically state who made the request. It can be inferred from the timestamps. I’m just wondering if there is somewhere else I should be looking for this information. There is a 'subscribe' log, but currently the only events logged there are moderator approvals of unsubscribe requests held because the list's unsubscription_policy is moderate. Please submit an issue at <https://gitlab.com/mailman/mailman/issues/new> requesting logging of the information you'd like to see in this log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error:

by Mark Sapiro

On 11/18/19 9:26 AM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > I got an errormessage via mail to root@[domain-01]. > > The complete text is attached in a utf-8-text-file. > > In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, > 165, 166, 169, 187, 247, 251, 321 ....you can find links to different > domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. You attempted to delete testliste02.[domain-01] via Postorius and Mailman's REST API returned a 500 status. You may find more information in mailman.log. I'm only guessing, but possibly this is because you posted to the URL <https://[domain-02]/mailman3/postorius/lists/testliste02.[domain-01]/delete>. I.e., you were accessing Postorius at https://[domain-02]/mailman3/postorius/ (domain-02) and deleting a domain-01 list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Mark Sapiro

On 7/27/20 6:48 AM, Odhiambo Washington wrote: > So now I have tried to see if there is such option from django-admin, but: > > (venv) [root@gw /opt/mailman/mm]# django-admin --help You must run /opt/mailman/mm/bin/django-admin. If you run these commands in your venv, you run the ones in /opt/mailman/mm/venv/bin which dont have all the pointers to configuration and settings. It's OK to run /opt/mailman/mm/bin/* with your venv active, but if you just give the command name, you get the wring one. You also must have the empty /opt/mailman/mm/__init__py so that imports of /opt/mailman/mm*.py modules will work as I said at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Correcting name spellings in a list

by Mark Sapiro

On 2/24/21 10:13 AM, Peter Adebahr via Mailman-users wrote: > On 2/24/21 6:40 AM, Morris Jones wrote: >> I typo'd some full names in a mailing list. Is there a way to fix it >> without writing SQL? >> > > I understand it is just the name itself, which has been typo'd, not the > mail address: Couldn't you just edit the field "display_name" of table > "address" in the MM3 database? Easy with phpmyadmin or adminer... Of course you can do that if that's where the typo is. The actual display name you see may be the one in the `address` table, or it may be the one in the `user` table depending on whether the subscription is by address or by user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: How to promote non-members to members?

by Mark Sapiro

On 3/15/22 11:16, Quanah Gibson-Mount wrote: > Hello, > > We have a constant issue with confirmation emails for subscribers > getting lost and then the subscriber contacting us because their posts > to the list never show up. Is there a way I can, as an administrator, > do the confirmation on their behalf or in some other way promote them to > being a member from non-member? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… If they don't have an outstanding subscription waiting user confirmation, you can just mass subscribe them. If they do and your Postorius and Mailman core is reasonably up to date, you can find the pending request at Subscription requests -> Pending Confirmation, delete it and then mass subscribe them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: best pratice - set default MM settings and make them update-save

by Mark Sapiro

On 5/16/22 07:16, Stefan Bauer wrote: > > Is there also a way to have this box checked by default or do not request a > verifcation at all? > Could not find any flag in base.py. To have the box checked by default would require a patch to Postorius like this. ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): pre_verified = forms.BooleanField( label=_('Pre Verified'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, users will not have to verify that their ' ``` Not requiring verification at all would require patching Mailman core but would be a bad idea as it could allow someone to subscribe anyone without that person's consent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Is there a way to see all the list's held messages

by Mark Sapiro

On 10/11/22 07:04, bob B via Mailman-users wrote: > I run mailman but do not admin the lists. Is there a way for me to see all the held messages for all the lists? There are various things you can do depending on what you want. Does 'I run mailman' mean you are an admin of the server on which it is installed? If so, you can do this in `mailman shell`, but what do you want to see? I.e., just a summary by list of subject, sender and hold reason or also the message content. Also, the Django superuser has full admin access to all the lists and again depending on what you want, that may suffice. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Search results for query "sapiro"