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

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/11/24 11:06 AM, Elias Rudberg wrote: > Hello! > > I am using mailman3 (version 3.3.8) and it mostly works fine, but > sometimes (usually several times every day) the error below appears. > > Any suggestions for what could be done about this? ... > Here is what the error message looks like: > ------------------------------------------- > > [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/postorius/lists/ > > Internal Server Error: /mailman3/postorius/lists/ > > ValueError at /postorius/lists/ > Need 2 values to unpack in for loop; got 1. Can you get the page at /mailman3/postorius/lists/ and /mailman3/postorius/lists/?all-lists If those are OK, look in your web server access logs for `GET /mailman3/postorius/lists/` messages with the same timestamp as those errors. Is there some bogus query fragment on those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 1:55 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: >> >> Unless you want to remove the Ubuntu package and install everything >> with >> pip, you need to just stick with what you have that at least partly >> works and we'll try to determine how to fix the utf8mb4 issue. > > Hi Mark, > > You're a very patient soul. Thank you. > > Yes, I'm resigned to exactly that. The archives when folks send emojis > will break, but that's just life. Mail will get sent. Heck, I guess I > could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to > get rid of the emoji in the worst case... You would need to do that, because once one of the `emoji` messages gets into /var/lib/mailman3/archives/hyperkitty/spool, I think no further messages are archived because mailman_hyperkitty tries to process the queued messages first and throws the exception. But, it's still not clear to me whether you have removed the settings_local.pyc and restarted uWSGI or whatever interfaces to Django. > Once I've migrated my 1500 mailing lists (this weekend) to the server, > I'll think about how to get a new server set up that I can shift to and > I'll install that with pip, since that'll clearly give me something > more supportable. > > Is Ubuntu 20.04 a reasonable platform for that? Yes it is. FWIW, this list runs bleeding edge Mailman 3 on an Ubuntu 14.04 server (yes we should upgrade), the only issue being that we needed to install Python 3.6 (the latest at the time) from source because the native Python 3 was 3.4 -- 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: Django Internal Server Error on held_messages

by Mark Sapiro

On 3/24/22 04:02, Hasan Berkay Çağır via Mailman-users wrote: > Hello, > > We've been running a Mailman3 instance with Debian 10's official package: > > Mailman Core Version: GNU Mailman 3.2.1 (La Villa Strangiato) > Mailman Core API Version: 3.0 > Mailman Core Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] > > For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email: > > """ > Internal Server Error: /postorius/lists/list.example.com/held_messages As Andrew suggests, you will probably find exceptions with tracebacks in Mailman core's mailman.log. This is probably /var/log/mailman/mailman.log in the Debian package. If you find such and you can't determine the problem from them, post one here. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Error while Approving a Post Through Email

by Mark Sapiro

On 12/14/22 01:45, Stephen J. Turnbull wrote: > Alex A.J. writes: > > line 1132, in identify_record > > raise exc.UnknownHashError("hash could not be identified") > > passlib.exc.UnknownHashError: hash could not be identified > > Dec 13 17:01:41 2022 (2677611) SHUNTING: > > 1670931101.6040337+d5806b00b2b9d03f25db396639f66f3a26516178 > > This looks like maybe you have the wrong password? > > Maybe Mark or Abhilash has a more concrete suggestion, I've never used > the Approved header with Mailman 3. I don't have more time to look at this now, but I think it's a bug. This patch ``` --- a/src/mailman/rules/approved.py +++ b/src/mailman/rules/approved.py @@ -140,6 +140,7 @@ class Approved: mpw = mlist.moderator_password else: mpw = mlist.moderator_password.decode('utf-8') + mpw = config.password_context.encrypt(mpw) is_valid, new_hash = config.password_context.verify(password, mpw) if is_valid and new_hash: # Hash algorithm migration. ``` may fix 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

[MM3-users] Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/23/23 08:42, Odhiambo Washington wrote: > On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Thanks both of you. I didn't know Debian11 version is out of date. I will >> try using pip. >> > No. Debian 11 is _not_ out of date. It's just that the preferred and easy > to support installation method is using the virtualenv. The Debian stable mailman packages definitely ARE out of date. bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2. bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would 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, 8 months

[MM3-users] Re: Postfix SMTP REJECT non-subscribers

by Mark Sapiro

On 7/10/24 12:26 AM, Matthew Blissett via Mailman-users wrote: > > With Mailman 2, I have configuration and scripts to reject non-members > from posting to lists _during the SMTP connection_. This is better than > bouncing (no backscatter), better than discarding messages (the user > finds out) and better than moderation (spammy messages aren't forwarded > to external email systems). > > > The configuration and scripts are described here: > https://code.launchpad.net/~jimpop/mailman/check_subscriber > > > Is anything like this built-in to Mailman 3? I cannot find it in Gitlab. No. nothing similar is built in to Mailman 3, but it shouldn't be difficult to implement. It could be done with a milter as in the above implementation, or it could be done by modifying the _handle_RCPT function in mailman/runners/lmtp.py to check if the sender is a member of the recipient list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 12/10/24 07:44, pdw(a)mythic-beasts.com wrote: > > The messages were constantly re-appearing in the "out" queue with different file names (I assume they were going via the retry queue). First check to ensure there are no files in Mailman's var/templates/ directory that are not readable by the Mailman user. That can cause this issue. > After multiple restarts trying to get some debug information, the hard loop seems to have stopped recurring, and the messages are sat in the "shunt" queue. They've not been delivered to recipients, but they are in the hyperkitty archive. The shunted messages should have a SHUNTING entry with an exception and traceback in mailman.log. If there were files unreadable by Mailman in Mailman's var/templates/ directory and you have corrected that, you can move the shunted messages back to their original queue with `mailman unshunt`. -- 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: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Mark Sapiro

On 3/31/25 06:26, Philip Bondi wrote: > My /etc/mailman3/urls.py is empty. > > Should I, like it indicates in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > cp /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py /etc/mailman3/urls.py > chown mailman:mailman /etc/mailman3/urls.py > and add to /etc/mailman3/settings.py > > ROOT_URLCONF = 'urls' You can do all of that, but it's probably unnecessary. What is in /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py? compare it to https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > After completing above, https://systemdatabase.ca/mailman3 still gives > Service Unavailable It appears that https://systemdatabase.ca/postorius works so the issue is almost certainly that your urls.py is missing path('mailman3/', include('postorius.urls')), -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Relay Access Denied

by Mark Sapiro

On 7/22/25 10:25 AM, jkoral(a)luc.edu wrote: > Here is what I have in postfox_lmtp. Do I need to add another line for joetest(a)lists.luc.edu as well? > > joetest(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-bounces(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-confirm(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-join(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-leave(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-owner(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-request(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-subscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-unsubscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 If you want to address the lists @lists.luc.edu, the list names should be, e.g. joetest(a)lists.luc.edu, not joetest(a)listservnew.luc.edu. If you want to be able to use either domain for list mail, that's more involved. If you want this, say so and as I have time I can make suggestions., but I suspect you really only want to use the lists.luc.edu domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Mark Sapiro

On 9/9/25 08:42, M.Ede via Mailman-users wrote: > Hello everyone, > > I use mailman together with mailcow and have configured my mailing list as follows: > - Anonymous list: Yes > - DMARC mitigation action: Replace From: with list address > - DMARC Mitigate unconditionally: Yes > > My problem is that my emails are not being accepted by mailcow (rspamd) with the error > SPOOFED_UNAUTH (50.00) > ... > What am I still doing wrong? Can you help me, which setting is still missing? > What informations are you still missing? I doubt that this has anything to do with the ARC-*, Authentication-Results or DKIM-Signature headers you quote. There are some threads on SPOOFED_UNAUTH in the mailcow community forum, e.g. https://community.mailcow.email/d/403-spoofed-unauth-rspamd and https://community.mailcow.email/d/637-problems-with-emails-keep-getting-rej… Also see https://www.reddit.com/r/mailcow/comments/12lhw8e/whitelist_ip/ These came up in a google search for SPOOFED_UNAUTH. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

Search results for query "sapiro"