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

[MM3-users] Re: Heads Up - Downtime

by Mark Sapiro

On 5/19/23 18:48, Mark Sapiro wrote: > > The move was completed earlier today. Everything is up, but there are > two things that may affect mail delivery. At least some outgoing mail is > not being DKIM signed. I'm puzzled as to why. And, it's a new server > that doesn't have a reputation yet. Everything seems to be functioning well at this point. I fixed the DKIM signing issue and mail is being signed. We are still seeing a few bounces and I'm monitoring that. The last few posts were sent to 323 regular subscribers, six of whom bounced. We were listed in Spamhaus PBL, but that listing was removed yesterday. Still 3 yahoo.com addresses are bounced for being listed in Spamhaus. Maybe Yahoo will refresh its cache at some point. Also, 1 msn.com and 2 outlook.com addresses are bounced for our network being on their block list. This may be due to the Spamhaus listing or maybe not. I'll continue to monitor 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, 6 months

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 6:59 AM, Mark Sapiro wrote: > On 4/25/23 3:02 AM, Andrew Hodgson wrote: >> >> You may find this script useful: >> https://www.msapiro.net/scripts/clean_users.py > > I will modify the script to enable deleting Mailman users with no > memberships even if they aren't Django users and post here when it's done. The script at https://www.msapiro.net/scripts/clean_users.py has been updated. As before, it has settings to control whether Django users are deleted if there is a corresponding Mailman user with no memberships or only if there is no corresponding Mailman user, and whether or not Mailman users with no memberships are deleted. The difference is when deleting Mailman users it will now delete Mailman users with no memberships whether or not there is a corresponding Django user. -- 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

[MM3-users] Re: Imported Digest Settings

by Mark Sapiro

On 2/16/21 4:08 PM, Brian Carpenter wrote: > On 2/16/21 6:13 PM, Mark Sapiro wrote: >> On 2/16/21 2:28 PM, Brian Carpenter wrote: >>> The beginning of my OP stated I was using Mailman 3.3.3. >> Then please get me a copy of the complete raw digest message so I can >> try to find the underlying issue. >> > Not sure how to do that. Do you mean have the list member forward their > garbled digest message to me? Is that what you need? Oops. Sorry for the prior content free reply. Yes the list member needs to forward the garbled digest to you to resend to me or to me directly, but if it's forwarded, it must be forwarded as an attachment, not inline, because inline forwarding will lose the headers I need to see. Alternatively, the list member can view the message source (how to do that depends on the MUA), select it in its entirety, copy and paste it into a message to you or me -- 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: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 10:02, Odhiambo Washington wrote: > On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Thus, putting >> ``` >> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' >> ``` >> in your settings will maintain compatibility with pre 3.2 versions and >> existing tables and this is the correct thing to do. >> > > Thank you very much for the clarification. Also note that for the past year or so, the files postorius/example_project/settings.py:, mailman_web/settings/base.py, hyperkitty/example_project/settings.py and mailman-suite/mailman-suite_project/settings.py have all contained DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' and if you follow https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… you will import mailman_web/settings/base.py and pick this up from mailman-web 0.0.6 and both https://wiki.list.org/x/17892066 and https://wiki.list.org/x/17891998 suggest that your settings.py should be a copy of the mailman-suite settings.py file but with DEBUG = False, the implication being that when that file changes, yours should too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 11:57 AM, Mark Dadgar wrote: > On Jun 9, 2020, at 11:34 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> ./mm3-admin: line 6: 702058 Killed django-admin $@ >>> >>> Now what? >> >> >> Run it as user `list`. > > > Same. It appears that the reference to line 6 is line 6 of your mm3-admin file which is the `django-admin $@` command. So that command is being killed by the OS for some reason, probably out of memory. Try this instead. import pytz import datetime start = datetime.datetime(2020, 1, 1).replace(tzinfo=pytz.UTC) end = datetime.datetime(2020, 2, 1).replace(tzinfo=pytz.UTC) # These are examples. The args are year, month, day. # Pick dates for start and end that overlap the start of this issue. from hyperkitty.models import Email emails = Email.objects.filter(date__range=(start,end)) for email in emails: if email.content.find('\u200b'*5) >= 0: print('Found in ml {}, hash {}'.format( email.mailinglist.name, email.message_id_hash)) This will make a much smaller query set than all the emails and should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/17/2018 10:05 PM, Joe Steeve wrote: > On Tue, 2018-07-17 at 22:04 -0700, Mark Sapiro wrote: >> You would need to stop Mailman core and all Django processes including >> cron jobs and WSGI processes to ensure nothing is accessing the SQLite >> database, update the database section in mailman.cfg and the DATABASES >> settings in your Django settings, use SQLite tools to dump the relevant >> database(s) and PostgreSQL tools to create and load them, and finally >> restart Mailman core and all Django processes. > > Fantastic. I'll give it a shot and update. It occurs to me, it might be trickier than that in that dumping the SQLite database(s) and then loading them into PostgreSQL might result in table/column definitions in PostgreSQL that are inconsistent with the models because of differences in what SQLite and PostgreSQL support. If this is the case, it might be necessary to let Mailman core and Django create (empty) PostgreSQL tables and then just load the data from SQLite. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Can't remove footer(s)

by Mark Sapiro

On 10/11/2018 02:04 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> The templates named list_member_digest_footer.txt and >> list_member_regular_footer.txt (with underscores) were created by >> import21 and set as the URIs for those templates. Had you just copied >> /dev/null (or otherwise made empty) those files and done nothing else, >> that would have done what you wanted, but since you deleted the template >> URIs for the list, the template names are now the default > > How do I make these not default? You can set them via ITemplateManager. > Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? You could except Postorius won't let you set an empty value for a template and deleting a template in Postorius just reverts to using the default - e.g., 'list:member:regular:footer'. What you need to do is copy /dev/null to files in (in your case) /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/ named list:member:digest:footer.txt and list:member:regular:footer.txt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 17:51, Mark wrote: > > > >> On 2024-04-24 03:58, Mark Sapiro wrote: >> >>> What do you get if you do >>> ``` >>> sudo -u mailman curl >>> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… >>> ``` >>> with the template set in Postorius? >> > > ******************* > >> The welcome message is returned. >> >> root@hel:~# sudo -u mailman curl >> https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… >> Test Welcome message for new subscribers.root@hel:~# > > ******************* > > Making progress... > > I edited settings file again, replacing the domain name with the IP > address () > > POSTORIUS_TEMPLATE_BASE_URL = 'http://12.34.56.78' (no SSL) That should be no different than `http://host_name` where host_name's DNS A record is 12.34.56.78. > The URI in the template table now has this. > > http://12.34.56.78/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/list… And if you go there in a browser, what do you get? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Mark Sapiro

On 12/28/22 12:22, Odhiambo Washington wrote: > On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/27/22 22:00, Odhiambo Washington wrote: >>> I worke up to 959 such entries in my mailmanweb.log: >>> >>> ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The >>> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ... >>> >>> What might have been the cause of this? >>> >> >> Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= >> 1.3.5 requires mailman-hyperkitty>=1.2.0. Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a different message so that isn't it. There is an issue with Apache. If you search the archives of this list for the log message you'd find it, but see the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… But why these messages all of a sudden? Did you just change something? -- 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: applying patch 1130

by Mark Sapiro

On 8/21/23 9:00 PM, David Newman wrote: > > On 8/21/23 7:57 PM, Mark Sapiro wrote: >> >> Since !1130 is merged, just `pip install` from the gitlab head. >> ``` >> pip install git+https://gitlab.com/mailman/mailman@head > > > Perhaps something else is needed first? This is on a Debian 12 system > upgraded from 11, with MM3 3.3.8 installed in a venv. > > (venv) mailman@x12:~$ pip install > git+https://gitlab.com/mailman/mailman@head > Collecting git+https://gitlab.com/mailman/mailman@head > Cloning https://gitlab.com/mailman/mailman (to revision head) to > /tmp/pip-req-build-wjge_v67 > Running command git clone --filter=blob:none --quiet > https://gitlab.com/mailman/mailman /tmp/pip-req-build-wjge_v67 > warning: redirecting to https://gitlab.com/mailman/mailman.git/ > WARNING: Did not find branch or tag 'head', assuming revision or ref. > Running command git checkout -q head > error: pathspec 'head' did not match any file(s) known to git > error: subprocess-exited-with-error It worked for me in a virtualenv with pip 23.2.1, but try ``` pip install git+https://gitlab.com/mailman/mailman@master ``` -- 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

Search results for query "sapiro"