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

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: MM2 -> MM3 Migration

by Odhiambo Washington

On Fri, Dec 30, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/29/22 23:17, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> The default without the since= option is to import only those messages > >> from the mbox which are newer than the newest message in the existing > >> archive which is exactly what you want. > >> > > > > So I ended up using this and I can see the list metrics indicating that > the > > last post was on 29Dec22, but > > I don't seem to be able to see those posts in the archives. > > > If Postorius list metrics show the last post was 29 Dec, that was a post > to the MM3 list and if it was archived, then running hyperkitty_import > without a since= option will not import any messages older than that. > Is there a way to delete the whole archive and re-import afresh? I checked the django-admin options for hyperkitty and did not see any such option. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

[MM3-users] Re: Internal Server Error: /archives/api/mailman/archive OperationalError at /archives/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1")

by Mark Sapiro

8 months

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

by Mark Sapiro

On 1/27/23 23:53, Odhiambo Washington wrote: > > I have reread what you wrote now and I'm beginning to get the hang of this > method. > My observation is that it can only be _obvious_ to someone very familiar > with Python config > to decipher that *additional* settings *that can be augmented or overridden > in /etc/mailman3/settings.py* can be obtained from: > /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed > these two lines in > the sample settings given in /etc/mailman3/settings.py: > > from mailman_web.settings.base import *from > mailman_web.settings.mailman import * This is how it was always done in Mailman 2.1 and how it should have been done in Mailman 3's Django web UI from the start, but wasn't. MM 2.1 had mm_cfg.py which had ``` from Defaults import * ################################################## # Put YOUR site-specific settings below this line. ``` > [At first instance, it is not obvious that mailman_web.settings.base and > mailman_web.settings.mailman are > actually paths in Python - which magically translates to > mailman_web/settings/base.py and mailman_web/settings/mailman.py] This is very basic Python. > Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. > > For example, my mind all along has been tuned to having a settings_local.py > for overriding the settings.py. > However, with this particular documentation, it would appear that > everything is intended to just go into /etc/mailman3/settings.py. In that method you had the defaults in settings.py which at the end imported settings_local.py. This method has defaults in /PATH-TO/mailman_web/settings/{base|mailman}.py and those are imported at the beginning of settings.py which then has overrides. This is preferable because it allows things in settings.py like ``` HAYSTACK_CONNECTIONS['default']['PATH'] = 'some path' ``` to just override that one thing rather than having to redefine all of HAYSTACK_CONNECTIONS or import it from settings in settings_local.py. > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, > that those two "import *" _DO establish a base set of settings that can be > augmented or overridden in /etc/mailman3/settings.py_ > and that those settings are in what file(s) ? Again, this is very basic Python, but if you submit a merge request to update https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, we'll certainly consider 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, 3 months

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 11 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Thu, Dec 29, 2022 at 3:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 11:37, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 21:46, Odhiambo Washington wrote: > >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >>>> > >>>> I see from another post that you've decided against using Twitter, but > >>>> to answer the question, Twitter does not require adding anything to > >>>> SOCIALACCOUNT_PROVIDERS. > >>>> > >>> > >>> I tried it and ended up with: > >>> > >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server > Error: > >>> /accounts/twitter/login/ > >>> Traceback (most recent call last): > >> ... > >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > >>> query does not exist. > >> > >> > >> Do you have > >> > >> 'allauth.socialaccount.providers.twitter', > >> > >> in INSTALLED_APPS? > >> > > > > Here is what I have in settings_local.py: > > > > INSTALLED_APPS = ( > > 'hyperkitty', > > 'postorius', > > 'django_mailman3', > > # Uncomment the next line to enable the admin: > > 'django.contrib.admin', > > # Uncomment the next line to enable admin documentation: > > 'django.contrib.admindocs', > > 'django.contrib.auth', > > 'django.contrib.contenttypes', > > 'django.contrib.sessions', > > 'django.contrib.sites', > > 'django.contrib.messages', > > 'django.contrib.staticfiles', > > 'rest_framework', > > 'django_gravatar', > > 'compressor', > > 'haystack', > > 'django_extensions', > > 'django_q', > > 'allauth', > > 'allauth.account', > > 'allauth.socialaccount', > > #'django_mailman3.lib.auth.fedora', > > #'allauth.socialaccount.providers.openid', > > 'allauth.socialaccount.providers.github', > > #'allauth.socialaccount.providers.gitlab', > > 'allauth.socialaccount.providers.google', > > 'allauth.socialaccount.providers.facebook', > > 'allauth.socialaccount.providers.twitter', > > #'allauth.socialaccount.providers.stackexchange', > > ) > > > Did you add an app at https://site.name/admin/socialaccount/socialapp/ > with twitter as a provider? See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… Exactly, and I have entered all the credentials from the "OAuth 2.0 Client ID and Client Secret" of the twitter developer portal. https://webmail.kictanet.or.ke/~wash/twitter-oauth.png I have checked my settings_local.py several times trying to find out why the entry is ignored. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Tue, Jan 31, 2023 at 9:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:43, Mark Sapiro wrote: > > > > add another section header > > > > Regular Expression Tables > > ------------------------- > > > > and change that text to > > > > Regular Expression tables are less efficient than hash tables, but they > > remove the additional dependency of having ``postmap`` command available > > to Mailman. If you want to use ``regexp`` or Regular Expression tables, > > then add the following to Postfix's ``main.cf`` file > > > This is now done. > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > That is now quite clear, but I still have one question and this is cosmetic (because Postfix isn't my MTA of choice. You can ignore it if it feels like spoon-feeding a Postfix admin. In the section: ``` https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… ``` .. the Postfix admin had to figure out whether they are using hash or regex tables and modify accordingly, right? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Jered Floyd

Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home from another episode of turkey overconsumption. I confess that I am not a python expert - once I create a new list, what’s the easiest way to inspect the object state? --Jered > On Nov 25, 2023, at 18:28, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/25/23 8:01 AM, Jered Floyd wrote: > >> This suggests that new lists in 3.3.9 may be getting mlist.dmarc_addresses set to None rather than an empty list (which seems to be expected). > > > How did you create this list? > > I have tried and when I create a new list it has mlist.dmarc_addresses set to an empty list. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 5 months

[MM3-users] Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years

[MM3-users] Re: Apple Mail encoding again

by David Newman

On 4/14/22 10:45 AM, Mark Sapiro wrote: > On 4/14/22 10:18, David Newman wrote: >> On 4/14/22 9:50 AM, Mark Sapiro wrote: >>> >>> It could accept a defective message or one with specific defects, but >>> this is problematic for further processing. For example, at least one >>> MUA, Thunderbird, renders such a message with an empty body. >> >> That's not my experience. Mailman 3 accepted without complaint a >> PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to >> list subscribers with the message body intact. > > > Yes, and that's what we expect, but MM 3 does not accept the defective > message, and T-bird does not render the body of such a message. I.e., if > such a message composed by Apple Mail 15 is sent via a non-Mailman > channel to a T-bird user, the user can't read it. Sorry, I misspoke. The Apple Mail sender used S/MIME signing, not PGP signing. In Thunderbird, I was able to read an S/MIME-signed message the user sent directly to me complaining about the 501 bounce. Thunderbird said the signature was invalid due to the use of an untrusted CA, but I could read the message body. dn

4 years

Search results for query "sapiro"