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

[MM3-users] Re: Strange password problem

by Mark Sapiro

On 9/22/23 11:39, Eggert Ehmke via Mailman-users wrote: > Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > >> If you set the password with the Django admin changepassword command, >> does it stick? > > Never tried that, how do I do that? In our recommended install, the Django anmin command is `mailman-web` so with your venv active, ``` $ mailman-web changepassword ``` will prompt you for a new password for the current user. If you want to change another user's password, specify that user's username as in ``` $ mailman-web changepassword user ``` >> Can you create another superuser with the Django admin createsuperuser >> command and does that user's password stick? > > Will try that. So I can create another superuser? Does it need a separate > email address? I guess yes ``` $ mailman-web createsuperuser ``` It will prompt for a username, email address and password. The username and email address need to be unique. -- 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: change preferred language of list

by Mark Sapiro

On 6/20/19 5:01 PM, Mark Sapiro wrote: > > There does seem to be an issue. I set the preferred_language of a list > to 'de' and subscribed an address. The address was sent a confirmation > request in German, but upon response, the subsequent "The results of > your email commands" message and the list welcome message were in English. > > The "The results of your email commands" message was in English because > it is built dynamically by the command runner and while the messages are > i18n'd, there is as yet no German message catalog. > > However the list welcome message should have used the German template. > This appears to be a bug. Actually the issue is the welcome message is sent in the user's preferred language, not the list's preferred language, and a newly created user has no preferred language so the language defaults to English. See <https://gitlab.com/mailman/mailman/issues/608>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Header Filter madness

by Mark Sapiro

On 1/11/21 6:14 PM, Brian Carpenter wrote: > > On 1/11/21 8:48 PM, Mark Sapiro wrote: >> On January 11, 2021 5:50:04 PM MST, Brian Carpenter >> <brian_carpenter(a)emwd.com> wrote: >>> I have a client whose header filters seemed to have stop working. No >>> matter what I try, it seems none of their header filters are being >>> applied. Other lists on the same server that use header filters, are >>> working fine. This particular header is the subject header. I can >>> duplicate their problem but only with their list. If I create the exact >>> same header on a test list using the exact same subject line, the >>> header >>> filter does its job (moderate). Just not with this one list. What's in the X-Mailman-Rule-* headers of the post that should be but isn't held? Are there other header filter rules besides the one that doesn't 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, 9 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/25/20 12:12 AM, Alan So wrote: > Mark Sapiro wrote: > >> In the absence of an issue at >> https://gitlab.com/mailman/mailman/-/issues, >> probably never. <hint> > > Is that anyone with a gitlab account can file an issue? If it is appropriate, I can try to file one. Yes, anyone with a gitlab account can file an issue. >> Have you asked Microsoft to fix Outlook to not create these defective >> messages? That's the real solution. > > Yes and I agree. My colleague has actually done so but it is probably not yet escalated to the appropriate tier of support. Here is the comment of my colleague: "I can submit this problem to Microsoft. However, it may take a long time to fix it or not even important enough to be fixed." At least you're trying and that's a good thing even if they don't fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: How to upgrade to 3.10

by Mark Sapiro

On 3/8/26 10:25, Paul Tomblin via Mailman-users wrote: > > > On Sat, Mar 7, 2026, at 11:08 PM, Mark Sapiro wrote: >> >> Do you have the latest Postorius from GitLab? > > I missed that step at first, but now I've done it, I see no change. It still says version 1.3.13, and the Edit Domain page still just has Description, Alias Domain, and Web Host. > > When I was installing it, it said it was this commit: > Resolved https://gitlab.com/mailman/postorius to commit 2c0c3aeb905c82ee4d6724897b89def71c02c1ef > which does appear to be the latest. That should be good. It will say 1.3.13 as the version hasn't been updated in GitLab. Is an old page cached somewhere? Have you tried clearing browser cache or a different browser or depending on browser and platform ctrl+reload or shift+reload. Does your /opt/mailman/venv/lib/py<version>/site-packages/postorius/forms/domain_forms.py match <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/doma…>? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/27/24 08:32, Mark Sapiro wrote: > > More strangeness. I've now done a test on one of the production servers > I manage, and there is no error. Both the production server and the > development server are running the identical Mailman code installed in a > venv, they both have the same version of urllib3 and similar Python > versions, 3.9.16 on the development server and 3.9.10 on the production > server. Both servers are running under Ubuntu 20.04.6. The only other > difference I see is on the production server everything runs as user > mailman and on the development server everything runs as user mark. I have now reinstalled Mailman from scratch on the development server in a Python 3.12.3 venv using the heads of the gitlab branches and getting the current versions of all the dependencies and this installation gets no error. So while I still have an older venv that produces this error, I cannot duplicate the error in a new install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/18/19 2:29 PM, Manos Pitsidianakis wrote: > > Στις 2019-09-18 19:12, Mark Sapiro έγραψε: >> Is only one list affected, and is it all messages from this list or only >> some? > > Just two messages from this certain list. Subsequent messages and other > activity seems to work properly There should be entries in the mailman.log for each shunted message listing the exception with a traceback and the fact that the message was shunted. What are these entries? > Well there is no connection to postfix at all when the runner starts and > the "Cannot connect to SMTP server" log shows up. Otherwise I'd have > seen something in the postfix logs or tcpdumps in localhost. The "Cannot connect to SMTP server" log message should not occur immediately on startup unless there are queued messages. That log message should only occur on an attempt to actually send a message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Why is it VERPing every message?

by Mark Sapiro

On 6/24/26 13:01, Paul Tomblin via Mailman-users wrote: > On Tue, Jun 23, 2026, at 8:48 PM, Mark Sapiro wrote: > >> I don't know what the issue is, but even if you have personalization >> off, try setting `verp_personalized_deliveries: no` in case there's some >> issue there. > > Ok, that's weird. `mailman conf -s mta` said it was already set to no, but I added it to /etc/mailman3/mailman.cfg and now it's sending in big chunks. Which now RoadRunner is rejecting because of too many recipients in one message instead of too many simultaneous connections. Can't win with these idiots, can I? Did you set max_recipients in the mta section of mailman.cfg. That controls the maximum number of recipients of a message. The default is 10. Is that the number of recipients you're seeing in the rejected messages. On the other hand, your MTA might be combining recipients from two or more messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/15/22 10:20, Mark Sapiro wrote: > On 9/15/22 01:22, Kimmo L wrote: >> Hi Mark! >> >> I forwarded the same shunted file to you as well, which i sent to Steve. > > > Thanks. I got it and will look further. This is very strange. The message object in the shunted pickle is missing several important headers. In particular, there is no Message-ID: and no MIME-Version: and no Content-Type: while the body contains subpart headers like ``` Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ``` and ``` Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ``` but no boundaries. This apparently confuses the Python email package so that the get_payload() method returns a list of strings rather than a list of message objects. The question is how did this happen. What does ``` mailman conf -k anonymous_list_keep_headers ``` show, and what is the content of mailman/handlers/cleanse.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

On 1/14/23 11:44, Odhiambo Washington wrote: > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Nothing in those releases per se would affect this. This is Django and >> django-allauth. Perhaps when you updated the Mailman packages, you also >> updated these dependencies. >> > > Which dependencies would those be? Django and django-allauth. > When I upgraded, the command I ran was: > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > mailman-hyperkitty django-mailman3 Do you mean --force-reinstall? pip has no --force option. I *think* --force-reinstall will upgrade dependencies. Depending on your pip version, --upgrade alone may or may not upgrade dependences. Older versions of pip will, but newer versions, at least without --force-upgrade require --upgrade-strategy eager to update dependencies. > And how do I find out what is suppressing the logging for the social > accounts? That's a django-allauth question. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Search results for query "sapiro"