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

[MM3-users] Re: Trouble Installing Mailman3

by Mark Sapiro

On 6/3/25 08:22, Henry Hartley via Mailman-users wrote: > > (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary > Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) > ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) > ERROR: No matching distribution found for wheel > > The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I don't understand why this is occurring. All those packages exist in pypi.org https://pypi.org/project/wheel/ https://pypi.org/project/mailman/ https://pypi.org/project/psycopg2-binary/ Also, pypi.org has a valid ssl certificate signed by GlobalSign nv-sa If I create and activate a new virtualenv named zzz, and do ``` (zzz) mark@msapiro:~$ pip -v install wheel mailman psycopg2-binary ``` I get a successful installation. I am guessing that there is something in your local network that's redirecting connects to pypi.org to somewhere else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/9/25 5:02 AM, Flo via Mailman-users wrote: > Hi, > > I added a new site in Django: lists.example.com > > Usually I click on 'view site' and I can add a Domain in Postorios. In > this case I get an error message and I need to add a Domain in Django. > Then I can go to 'view site'. > > I can create a mailing list there. However when I send an email to be > subscribed, I get the following in mailman.log (and nothing else happens): > > > Oct 09 13:46:24 2025 (110452) deque: do_confirm_verify > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailman/model/domain.py", line > 177, in __getitem__ > raise KeyError(mail_host) > KeyError: 'lists.example.com' It appears you don't have a domain in Mailman core with mail_host = 'lists.example.com'. Do you see one in Postorius' domains view? If not, perhaps you need to add it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: Unknown templates being used

by Mark Sapiro

On 2/14/21 1:47 PM, Tom Stoddard wrote: > > On 2/14/2021 1:31 PM, Mark Sapiro wrote: >> >> I.e., we know it should be a template, but it currently isn't. > > That's fine but it doesn't explain why I have received messages that > were built by a template for some subscription requests. In other words, > why is there a template being used in some instances and on others a > "mailman notify command" is being used? The notice sent at the time the request is generated is built from a template. The `mailman notify` command is intended to be run periodically via cron set up by the site admins to send a summary of then outstanding requests to the list admins. You should receive the initial notice built from a template of each request as it is generated as long as the list is sent to send immediate notices. The notice sent by `mailman notify` is a summary of all requests outstanding at that time. If all the requests have been handled by the time `mailman notify` is run, it won't send you anything. > Are there different methods for people to use to request a subscription? Yes, but that's not the explanation for your question. Subscription can be requested via a web UI or via email to the list-join or list-subscribe address or via a join or subscribe command sent to the list-request address, but all methods result in the same notices to the admin. > By the way, Brian at EMWD has been extremely helpful to me already and, > as he stated, he informed me that this is an issue with Mailman 3 so I > thought I'd try getting the answer directly from this group. I agree and appreciate that Brian is very supportive. In my initial reply, it was not clear to me that Brian had referred you here which is the only reason I pointed out that he was your primary line of support. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > Hi Team, > > Today, I found an error message like "Multiple rows were found > for one_or_none()" when a hold message is approved for a list. Until > yesterday the mails were accepted and delivered fine. We have seen this issue before. See <https://gitlab.com/mailman/mailman/-/issues/657>. There are also multiple threads on it in the archive, e.g., <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. We don't know how it happens, but the issue is that the `listarchiver` table in the database has multiple `mhonarc` entries for the same `mailing_list_id`. You can see the problem with the query select * from listarchiver where name = 'mhonarc'; There will be two entries with the same `mailing_list_id` and deleting one of them will fix this and you can run `mailman unshunt` to reprocess the shunted messages. The above referenced issue contains a script that can be run to remove the extra entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/9/20 6:39 PM, matthew(a)alberti.us wrote: > > For core, the connection string seems to accept a tailing > "?charset=utf8&use_unicode=1" per > https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So > for core, maybe just updating the connection string to include > "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the > recommend encoding... maybe that should be updated? I'm in the process of doing that update. > Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is > recommended, and it needs to be explicitly identified in the database > settings for BOTH core and web, and probably somehow at database creation > time? It's not as critical for core because barring things like 4-byte utf-8 unicode graphics in list configurations, core doesn't store anything like that in its tables. The major issue is with HyperKitty where messages have emojis and other 4-byte utf-8 encodings in message subjects and bodies. -- 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: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/21/23 17:30, Thomas Ward wrote: > > MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). > > If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 09:08, Wikinaut wrote: >>> In the Postorius held messages view, click on the message's subject to >> open a dialog showing the messages content > > Dear Mark, sorry: > How should I know this? Well, the subject of the message in the held messages view looks like a link. Maybe click it once to see what it does. > I'd rather prefer to have these both changes: > > i) relabel the existing one od three buttons from "accept" to "accept once" ; and > ii) add a fourth button "accept all messages from this sender (i.e. add to white list)" That wouldn't include options like "discard further posts from this user", "reject further posts from this user" and perhaps other possibilities. If I were going to do anything, it would probably be adding a line above the list of held messages saying something like "Click the message's subject for more options." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/26/22 21:29, Jan Eden via Mailman-users wrote: > > Replicating this setup on the server solved the KeyError problem, > everything works now! I just wonder why these uwsgi parameters need to > be passed explicitly when using a file socket, but not with a http > socket. You are doing more than just switching from a tcp socket to a unix socket. You are also switching from communicating with uwsgi via http protocol to uwsgi protocol. > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > files when using the virtualenv installation instructions > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, not mailman-web. If you want, you could put mailman-hyperkitty.cfg in /etc/mailman3/ by putting ``` configuration: /etc/mailman3/mailman-hyperkitty.cfg ``` in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. -- 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: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Mark Sapiro

On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: > I noticed some unusual behavior in Mailman3 stable release on PyPI and > such. Namely, there are instances where replies are being processed and > the prefix tags are simply being **lost** and dropped by Mailman3, > instead of being properly prepended where they're supposed to go. > > Is this a known bug or does it need its own bug in the gitlab tracker? Are you sure you are looking at messages from the list and not messages received by direct To:, CC: or BCC:? I have never seen an issue where list posts would sometimes have the subject prefix prepended and sometimes not. If you are seeing this, we would ideally like to see a thread in the hyperkitty archive where some of the messages have the prefix in the message view and some don't, or at least see some of the raw Subject: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/17/24 16:57, Mark wrote: > > I can see the French text for the "Password Reset Email" in the > django.po file. And running the compilemessages command reports the > "django.po" for French is okay and up to date. Should I be recompiling > the ".mo" file? No, It's fine. The issue is the language context for this message has nothing to do with any Mailman list's preferred language. Again, see https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… If all the lists on your server are French, you could set LANGUAGE_CODE = 'fr' in your Django settings. Otherwise, the user's browser has to include an Accept-Language: header specifying French as the most preferred language in it's request. Also note the ordering of SessionMiddleware, LocaleMiddleware and CommonMiddleware in the above doc. I have recently updated the various places where we suggest or supply MIDDLEWARE settings, but you may find that your settings have LocaleMiddleware after CommonMiddleware and you should fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Search results for query "sapiro"