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

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Mark Sapiro

On 08/09/2017 02:35 PM, Abhilash Raj wrote: > Hi, > > On Wed, 9 Aug 2017 13:42:20 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> # Send periodic digests. >>> # I like 03:30 so they go overnight, but since we're 'global' and on UTC, >>> # maybe 07:30 is good. >>> 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > well? It's only that one and whether it's needed or not depends on list configuration. The list has attributes digest_send_periodic and digest_size_threshold. When a post is received it is added to the list's digest mbox, and if that causes the size of the mbox to reach digest_size_threshold K bytes, a digest is sent. Additionally, if digest_send_periodic is true, a digest is sent periodically whether or not it has reached digest_size_threshold. However, the sending of periodic digests depends on cron running something periodically to actually trigger the sending. Note: I've just looked at the code and there seems to be an issue with using 'mailman digests --send' to send the periodic digests. It appears that if a list's digest mbox has any messages, 'mailman digests --send' will send a digest even if digest_send_periodic is false. I've just reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: mailman-web migrate error

by Mark Sapiro

On 11/12/25 12:09, Mark Sapiro wrote: > > This is actually a django-allauth issue. This issue is due to changes in > Django allauth to prevent creating > multiple addresses differing only in case. The problem is if you have > such multiple addresses in your account_emailaddress table, this > migration fails. There is a script at > https://www.msapiro.net/scripts/UC_fix that will fix this. You may need > to adjust the shebang and replace psycopg2 with sqlite3. > > See https://github.com/pennersr/django-allauth/issues/3019 perhaps > starting at > This issue is due to changes in Django allauth to prevent creating > multiple addresses differing only in case. The problem is if you have > such multiple addresses in your account_emailaddress table, this > migration fails. There is a script at > https://www.msapiro.net/scripts/UC_fix that will fix this. You may need > to adjust the shebang. > > See https://github.com/pennersr/django-allauth/issues/3019 perhaps > starting at > https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… That was a bit of a copy/paste messup. It should have said just This is actually a django-allauth issue. This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: remove non members from a list

by Mark Sapiro

On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Thanks. Now it's no showing errors (and nothing at all) but apparently > it does nothing. The non mebers of the list (the few that remains: I've > been deleting one at a time from the web) aparently still are there.. > > Knowing the correct procedure will ease me to try tomorrow with a clean > head. It doesn't report anything, and if you don't commit() or exit with control-D, any changes will be rolled back. What does list(m.nonmembers.members) show before doing the unsubscribe() and commit() and then what after? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/17/21 3:06 PM, dancab(a)caltech.edu wrote: > I don't know why either. The mailman shell command seems to have had no effect either. > > Would it be safe to remove those expired rows directly via MySQL commands? Is the id column keyed or joined to another table where I would also have to delete corresponding rows? Yes it should be fine. Just DELETE FROM file_cache; I'm assuming your MySQL database is shared between your two Mailman servers or that both are accessing the same MySQL server. Is it somehow possible that there are two MySQL databases and Mailman is using one and you are looking at another? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: How to authorise members visibility?

by Mark Sapiro

On 5/25/22 02:50, Pierre Malard via Mailman-users wrote: > Hello, > > My setup: > - Debian 11 > - Mailman3-full v 3.3.3-1 > > My Question: > How to configure the visibility of a list of subscribers to a list? > > I created a list and set "subscriber visibility" to subscribers only. When I log in as such and try to view the list information, I can't see anywhere how to display that list. > It's the same regardless of the setting used for this "subscriber visibility" field (only moderators, only subscribers or anyone). This is a bug in Postorius. See https://gitlab.com/mailman/postorius/-/issues/369 -- 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: Digests not working correctly

by Mark Sapiro

On 6/13/23 10:58, Joel Lord wrote: > I ran the "/usr/local/bin/mailman digests --periodic" again, sadly > without the --verbose, and it kicked out the digests as it ought to have > the first time. Now I have to wait for some list traffic to come in to > "recharge" the digests so I have something to test with again. Even with the --verbose option, it wouldn't have helped much because it worked. What we would really like to see is the output with the --verbose option when it fails. It is a mystery to me why it would sometimes fail and sometimes not with the same digest.mmdf file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Archive date/time vs elapsed time

by Mark Sapiro

On 6/26/23 7:46 PM, Mark wrote: > Hi > > In the archive's "Recent", "Most active" etc displays, the date and > time of each post is shown. > > However, when viewing by "Thread" listing, each post shows the elapsed > time since it was posted ie. the number of days, hours since it was > posted (eg. 1 day, 2 hours). I don't see this. It may have been recently changed. Please visit the archive of this list at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ and if you see the issue there, post a URL of a page on which you see it. -- 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: List Configuration Attribute Descriptions

by Mark Sapiro

On 5/20/24 11:27 AM, steve.bachinsky(a)tena-sda.org wrote: > Where does one obtain a complete and concise description for all of the list configuration attributes? > >>From the documentation, it is shown that the REST "config" interface will provide all of the attribute values associated with a particular list. But how does one find a concise description for all of these attributes? For example, I see that there is a list attribute for "default_nonmember_action" and there are two documentation pages for this attribute, but I can't find a concise description of the attribute and the permitted values. https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/mai… may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/29/24 10:23, Elias Rudberg wrote: > > Does it make sense, that "the template and the view should be corrected" > as suggested there? (The template in question would be pagination.html > but I'm not sure exactly how it should be corrected.) It makes sense, but it may difficult. I think we would need to somehow sanitize the query fragments to ensure they didn't contain `items=`, and if they did, probably just return an http 400 Bad Request. The difficulty is finding all the places in all the views that need this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Disable "confirmation emails"

by Mark Sapiro

On 09/18/2018 01:46 PM, Hagen Bauer wrote: > > even after a lot of google search I could not find a way to disable the > Confirmation Mails like > .... > The results of your email command are provided below. > > - Original message details: > ....... > > Is there a way to do this? I have users who would be irritated and I > dont want them to recieve this Where are you seeing these? There were changes in this area in Mailman core v. 3.2.0 and I think these now should only be sent in response to mail to the -request address that contains a command other than (un)subscribe or confirm. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

Search results for query "sapiro"