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

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 6/24/20 7:28 AM, kelly.close(a)lrewater.com wrote: > Hi Mark - could you elaborate on this just a little? One of the things I did try was to include the https:// prefix in my base URL setting and it did not affect the issue. Is there a different way to use an https scheme in the base_url setting than just adding the 's'? I tried every combination I could think of for that setting, restarting both mailman and apache2 between each try I think, but maybe I missed something. ~Kelly I don't know what the issue was in your case, but if it was fixed by changing the Appache config to not redirect http to https for requests from localhost, it should be fixed by just going to https in the first place unless there is some certificate issue at play. The relevant settings for this list are: mailman-hyperkitty.cfg: [general] base_url: https://lists.mailman3.org/archives api_key: xxx settings_local.py: MAILMAN_ARCHIVER_KEY = 'xxx' ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'lists.mailman3.org', 'mail.mailman3.org', 'mailman.iad1.psf.io', 'mail.falconframework.org', '104.239.228.201', ] (I'm sure the above is overkill, but ...) MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1', '::ffff:127.0.0.1', '104.239.228.201', ) ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Problems after Upgrade

by Mark Sapiro

On 10/30/22 12:24, Jeff wrote: > > When I run the command: > > mailman-web compress > > I get the following error: > > traceback (most recent call last): > File "bin/mailman-web", line 8, in <module> > sys.exit(main()) > File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/__init__.py", line 49, in load_command_class > return module.Command() > File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management/base.py", line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > I have not been able to fix this and would appreciate any assistance. This is a bug in Django 4.1. See https://github.com/painless-software/django-probes/issues/24. Downgrading Django<4.1 should avoid 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, 10 months

[MM3-users] Re: Archive search failing on one list

by Mark Sapiro

On 9/23/23 17:51, Mark wrote: > > For example, on searching for the word "Derbyshire" (which is mentioned > in one of the archived messages) the results page displays: > > "Sorry no email could be found for this query." > > The logs show: > > +++++++++++++++++++++++++++++++++++++ > /var/log/mailman3/web/mailman-web.log > +++++++++++++++++++++++++++++++++++++ > > [pid: 1156|app: 0|req: 55/55] 2001:8004:5310:2405:ce66:5ff:41fc:60db () > {76 vars in 1537 bytes} [Sat Sep 23 23:57:43 2023] GET > /mailman3/hyperkitty/search?mlist=LISTNAME-1%40DOMAIN.COM&q=Derbyshire > => generated 13752 bytes in 3188 msecs (HTTP/1.1 200) 5 headers in 164 > bytes (1 switches on core 0) ... > mlist = MailingList.objects.get(name=mlist_name) > File "/usr/lib/python3/dist-packages/django/db/models/manager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line > 406, in get > raise self.model.DoesNotExist( > hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList > matching query does not exist. What does this database query return ``` select * from hyperkitty_mailinglist where name like 'LISTNAME-1(a)DOMAIN.COM'; ``` If it returns a row, does case match for the name in the row and the query? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Mark Sapiro

On 3/14/25 3:55 AM, Stefan Bauer via Mailman-users wrote: > Dear Mark, > > thank you for your time. > > After patching your script according to > https://github.com/maxking/docker-mailman/issues/729#issuecomment-2447542238 > > It fails with > > /opt/mailman/venv/data# /usr/local/bin/UC_fix > /opt/mailman/venv/data/mailman3web.db > Traceback (most recent call last): > File "/usr/local/bin/UC_fix", line 77, in <module> > c.execute("delete from account_emailaddress where email = %s;", > sqlite3.OperationalError: near "%": syntax error That patch still assumes the database is PostgreSQL. You need to replace ``` import psycopg2 ``` with ``` import sqlite3 ``` and ``` db = psycopg2.connect(...) ``` with ``` db = sqlite3.connect(...) ``` but it appears you've done that. It appears that the sqlite3 module doesn't accept the '... %s', value' syntax. See https://docs.python.org/3/library/sqlite3.html You need to change things like ``` c.execute("""update account_emailaddress set "primary" = 't' where email = %s;""", [em1]) ``` to ``` c.execute("""update account_emailaddress set "primary" = 't' where email = %s;""" % em1) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: How to get rid of footer (Mailman3)

by Mark Sapiro

On 2/11/20 11:31 PM, tarmokumar(a)gmail.com wrote: > Hi, I have read multiple posts in this forum that you should be able to get rid of the footer completely but I am unable to. > I have tried: > - adding the footer template to a list and not adding any "Data" to it. Result was a attachment with some "dfgdfgdfgdfg" text in it. Did you add this via Postorius. If so, it would seem to be a Postorius issue. > - adding/creating a blank "list:member:generic:footer" document to /var/templates/site/en, var/templates/lists/LIST.ID/en/ and var/templates/domains/DOMAIN/en/. Result is that the sent e-mail still has the original unsubscribe text in the footer (as an attachment) Did you name the file list:member:generic:footer.txt (with the .txt extension)? Putting a zero-length file of that name in any of those places should work. > - removing all the files from /mailman/src/mailman/templates/en, still no change If you restarted Mailman after doing this, this indicates something (Postorius?) may have set a URI for this template. What do you get from curl -urestadmin:restpass \ http://localhost:8001/3.1/lists/LIST.ID/uris -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: hyperkitty installation: Unclear instructions

by Mark Sapiro

On 1/5/23 15:00, Johannes Rohr wrote: > Dear all, > > I just installed mailman and mailman3-web in virtualenv as described in > https://docs.mailman3.org/en/latest/install/virtualenv.html > > Next I moved on to set up hyperkitty as described in > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html. I > got confused by the instructions: You are confused because you are mixing incompatible ways of installation. Installing mailman-web per https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-… installs both HyperKitty an Postorius as dependencies of mailman-web. > But then, hyperkitty seems to be already have been pulled in by > mailman-web, looking at its dependencies. Yes. > If that's the case, then neither the instructions at > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html nor > those at > https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html > are correct. They are correct, but they are for different methods of installation. > Can someone enlighten me on what the canonical way is of installing and > setting it up in virtualenv? Just follow the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. They are the current recommendation and will result in a complete installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: mass remove pending confirmation

by Mark Sapiro

On 5/22/23 13:46, Jens Günther wrote: > > Since we migrate some lists from mailman2 to 3, there are a lot of new > users/subscribers and an admin made the mistake to not checkbox the 3. > option that the users don't need to verify their address. Are these newly added users since the migration? If you migrate a list with the `mailman import21` the users of the MM 2.1 list will be imported and there won't be confirmations. > Now we have a long list of pending confirmations in different lists. Is > there an easy way in the shell to mass remove these pending > mailaddresses so that we don't have to do that one by one? That would be > awsome. Do you want to remove them or confirm them. If you just remove them, the user's addresses will still be unconfirmed. If you just want to remove them so you can redo the mass subscribes, you could do something like the following in `mailman shell` ``` >>> pendings = getUtility(IPendings) >>> for token, data in pendings.find( token_owner=TokenOwner.subscriber, pend_type='subscription'): ... pendings.confirm(token, expunge=True) ... >>> commit() ``` -- 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: Setting base_url for the domain to use it in the templates.

by Mark Sapiro

On 8/27/24 11:27, Ondřej Brablc via Mailman-users wrote: > The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… shows that when the variable is not set it would come as `base_url: None` on GET request. > > But the my table `domain` does not even have column `base_url`. I have tried adding it `ALTER TABLE domain ADD COLUMN base_url CHARACTER VARYING;` but this did not help. The docs at https://docs.mailman3.org/ include documentation of the heads of the GitLab branches so they may contain documentation of things that are not yet released. When Mailman 3.3.10 is released and you upgrade (or when you upgrade from the head of the GitLab branch), a migration will run automatically to add the base_url column to the domain table. > So I believe this is just some WIP. Some related commits: > > - https://gitlab.com/mailman/mailman/-/commit/a80f6d32252b6cf174f836210bc2157… > - https://gitlab.com/mailman/mailman/-/commit/7c5294fe1245d927cb30c556beb2176… Yes, it is a WIP in that it hasn't yet been released as are all the changes at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Migrating Mailman 3 lists

by Mark Sapiro

On 5/19/20 7:25 PM, Mark Dadgar wrote: > > I get a bunch of these errors because identifiers in postgres are limited to 63 characters and mm3 creates some in sqlite that are longer than that: > > 2020-05-20T02:16:20.574000Z WARNING PostgreSQL warning: identifier "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6b632_uniq" will be truncated to "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6" ... > > etc. > > I killed the job before it finished and have not actually tried running against this database, but my question is this: > > How does mailman3 handle this limitation with postgres if I set up an instance from scratch using postgres? Does it just truncate the identifiers identically, in which case migrating via pgloader should work? Mailman doesn't make those names. Those are names in table index entries. Mailman specifies the columns in a table which are indexed, but the DBM itself manages the index. > For reference my pgloader script looks like: > > load database > from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db > into postgresql://mailman3:XXREDACTEDXX@localhost/mailman > > with include drop, create tables, create indexes, reset sequences, no truncate I'm not sure why this doesn't work. A brief look at the pgloader docs seems to say it should. -- 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: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 12:33 PM, Massimo Zappalà wrote: > Hi Mark, thanks for the reply. > > my /etc/opendkim.conf > AutoRestart Yes > AutoRestartRate 10/1h > UMask 002 > Syslog yes > SyslogSuccess Yes > LogWhy Yes > Canonicalization relaxed/simple > ExternalIgnoreList refile:/etc/opendkim/TrustedHosts > InternalHosts refile:/etc/opendkim/TrustedHosts > KeyTable refile:/etc/opendkim/KeyTable > SigningTable refile:/etc/opendkim/SigningTable > Mode sv > PidFile /var/run/opendkim/opendkim.pid > SignatureAlgorithm rsa-sha256 > UserID opendkim:opendkim > Socket inet:12301@localhost > > > my /etc/opendkim/SigningTable > *(a)catania.linux.it mailselector._domainkey.catania.linux.it Assuminng your list's domain is catania.linux.it, what you need to do to enable DKIM signing of this message is add SenderHeaders List-Post,Sender,From to /etc/opendkim.conf > full email django error > Internal Server Error: /hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Unfortunately, the rest of the detail doesn't help. What we need to see is the raw message. You should be able to find it in Mailman's var/archives/prototype/<list_address/new/ directory, perhaps by timestamp or something in the headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Search results for query "sapiro"