Search results for "Postorius" - Mailman-users

mailman3-web postorious error "invalid request block size: 14056 (max 4096)...skip"

by Frederik

Until about one month ago, I had mailman3 and mailman3-web successfully running on Debian 12. However, when I access any page such as https://example.com/mailman3/postorius/lists/ now, I just get a 500 server error. /var/log/mailman3/web/mailman-web.log logs this at every request: invalid request block size: 14056 (max 4096)...skip I read somewhere that adding buffer-size = 65536 to uwsgi.ini might help. It indeed makes a difference, but unfortunately I just get another error instead: [pid: 4067215|app: -1|req: -1/1] () {256 vars in 14055 bytes} [Tue Jan 28 18:06:30 2025] => generated 0 bytes in 0 msecs ( 500) 0 headers in 0 bytes (1 switches on core 0) There are no other errors in the logs. I proxy mailman in Apache like this: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost-mailman3/ </IfModule> and mailman3's uwsgi.ini looks like this: [uwsgi] uwsgi-socket = /run/mailman3-web/uwsgi.sock enable-threads = true chdir = /usr/share/mailman3-web wsgi-file = wsgi.py master = true process = 2 threads = 2 uid = www-data gid = www-data env = HOME=/tmp plugins = python3 attach-daemon = python3 manage.py qcluster logto = /var/log/mailman3/web/mailman-web.log buffer-size = 65536 Any idea what could be wrong or how to debug this further? I'm using mailman3-full 3.3.8-2~deb12u2 and mailman3-web 0+20240312-1 packages.

1 year, 7 months

Re: Verification emails 'helo' rejected

by Greg Newby

Thanks for this, Odhiambo. Unfortunately it doesn't address my situation. See below: On Tue, Oct 15, 2024 at 3:21 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Mon, Oct 14, 2024 at 10:43 PM Greg Newby via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Hi friends. >> >> I'm now getting a 500 server error upon signing up a new username on the >> web-based front end. The username is created in the back end, but the >> verification email does not get sent. >> >> This is GNU Mailman 3.3.9 (Tom Sawyer), venv, Ubuntu 24.04LTS, PostgreSQL, >> Postfix >> >> Here are the corresponding logfile entries from mailmanweb.log: >> smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 >> <mail>: >> Helo command rejected: need fully-qualified hostname')} >> >> and from mail.log: >> Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from >> localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need >> fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost >> > >> proto=ESMTP helo=<mail> >> > ^^^^ Note the problem isn't the "From:" address. That is being correctly configured from mailman-web.py and settings.py via the variables below. The problem is it's going "To:" root@localhost. I don't know why this is happening - shouldn't it be going to redacted(a)gmail.com? Also, based on settings below shouldn't this be From: postorius(a)lists.domain.tld not From: root(a)lists.domain.tld? More: > >> lists.domain.tld is the domain for Mailman3. I don't know why it's trying >> to send email from root@. >> >> I've seen places where 'localhost' appears in the Mailman settings >> (settings.py, mailman.cfg, mailman-web.py), and tried changing them to the >> host's FQDN and restarting mailman3 and mailman3-web, but the problem >> persists. >> > > Find and fix these values to what they should be as explained. > > # The sender of emails from Django such as address confirmation requests. > # Set this to a valid email address. > DEFAULT_FROM_EMAIL = 'johndoe(a)domain.name' > > # The sender of error messages from Django. Set this to a valid email > # address. > SERVER_EMAIL = 'johndoe(a)domain.name' > > I use listmaster(a)lists.domain.name in my servers. > In the default files via the venv installation, these were already set properly: EMAILNAME='lists.domain.tld' <-- I set this myself These were default in settings.py and mailman-web.py: DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) SERVER_EMAIL = 'root@{}'.format(EMAILNAME) I set them explicitly to postorius(a)lists.domain.tld and root(a)lists.domain.tld and restarted mailman and mailman web, and this did not change the problem with the server error and mail log entries above. > I am not sure what files on your server contains them in your server. > > And while at it, also fix the site_owner: email in mailman.cfg. > That was already set to my email address, and I do correctly get site emails, such as cron output. Further guidance would be appreciated. ~ Greg

1 year, 11 months

Re: Manage Member(s) Mailman Settings / Display Names

by Jim Ward

I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. 2) The 'Search Members' function appears to be limited to the email address only and does not include display name These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, January 10, 2020 7:05 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attributes (display_name, etc) > > Postorius is a beautiful interface BUT I am evidently not finding how to manage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. -- 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://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 8 months

Re: EMWD/Affinity/Empathy in 2023

by Mark Sapiro

On 1/16/23 07:58, jaboyib556--- via Mailman-users wrote: > > However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? I have had some contact, but not much. As far as I know, they are still in business and offering list hosting including Mailman 3 lists with Affinity and Empathy. They no longer offer support for installation and maintenance of Mailman on other people's servers. When we first were developing Mailman 3, we designed it in a modular fashion with a REST API for the core engine so that users who were so inclined could develop their own web UIs for archiving and list management. We also recognized that we needed to develop our own to make a complete package. Thus, we developed HyperKitty and Postorius for that, but we have always hoped that the community would develop others (hopefully open source and Python based). As far as I know, it was only EMWD that did this and for business reasons, kept it proprietary. -- 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

Re: Email to list owner on list creation only sent when using mailman create --notify command

by Perry Kollmorgen

Ok, thanks for the information. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, 10 June 2024 2:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- 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 pcjkollmorgen(a)hotmail.com

2 years, 3 months

Re: Ann: Mailman Core 3.3.5 is out

by Mark Sapiro

On 9/29/21 9:59 AM, Brett Delmage via Mailman-users wrote: > On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > >> Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I >> would have >> to bypass the Debian installer. Or will there be Debian packages >> available? >> Same question for Postorius 1.3.6 Since Mailman 3.3.4 has been out for over six months and the latest Mailman 3 in even Debian sid is still 3.3.3, I would expect a long wait before these latest releases are available in Debian/Ubuntu. > I am excited to see 3.3.5 with its many updates available. Thanks to all > the contributors. > > I would like to know this too, as I was just about to install parallel > to the Debian package(s). I expect there are many of us. > > Going forward, what is the best way to maintain a stable version of > 3.3.5 with security and defect fixes only, exluding new features? Is > picking and applying individual checkins on gitlab the only way? I would suggest abandoning the Debian packages and installing as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. You should be able to keep all your existing configuration files and the database. You could even keep `list` as the Mailman user if desired. Once you have done this, upgrading via pip from PyPI or even from GitLab is very simple. -- 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

Re: Dump/restore users (with passwords) via API

by Dmitry Makovey

On 09/17/2018 12:39 PM, Abhilash Raj wrote: > On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: >> We are trying to dump/restore users using API calls and it seems >> that API allows us to dump password hashes (a good thing), but then >> API does not allow to insert users back using saved password hashes >> - only cleartext passwords. > > I'd say that is intentional. You don't want people to be setting up > hashes as passwords. > >> Aside from create_user is there any other way to create >> users/change their password? > > Not that I know of, not using the API atleast. You could potentially > use the low level API that inserts records in the database or use SQL > to dump and restore that data. > > What do you use the Core's user/password for? Currently, the user > passwords are basically just a carry-over from Mailman2 and there > shouldn't be any use for it. I have been considering removing that > completely have Postorius do all the authentication/authorization. > > Email based authentication should rely on more reliable identities > like email signatures, intead of having to send cleartext passwords > over email. I think I am asking about the username/password auth for postorious and how to dump/restore it. At present we have no tools for dump/restoring users so that's what we're trying to build. -- Sr System and DevOps Engineer SoM IRT

8 years

Re: old usernames appearing in mailman.log

by Ken Alker

--On Monday, June 26, 2023 5:03 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 10:57 PM, Ken Alker wrote: >> >> I have studied the output, looked at the code lines referenced in the >> Traceback, and I can't figure out the problem (I feel like the sad guy >> on the side of the street with his hood up staring into the engine bay >> with stream pouring out and not knowing what to do next). I did some >> analyses on the log file and determined that there are 71 messages it is >> having problems processing and there are 71 messages "stuck" in >> /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to >> process each message about 20 times). > > > Each time there is a new post, it retries all the messages in the spool/ > directory. > > >> Since upgrading to V3.3.8 I've >> not seen new messages get stuck like this (although it's only been >> running smoothly for 24 hours now and there hasn't been much activity). >> But I'm suspecting there was something awry between the conversion from >> V2 to V3 in February and me installing V3.3.8 that caused this (based on >> message time stamps). It is HIGHLY likely these messages are in the >> archiving spool as a result of me unshunting the shunt queue and that >> they are copies of the messages that got delivered to the subscribers >> when I did that... but are now hung up in the archiving process. > > > Are new messages being archived OK. If so, that is a real mystery. It > says mailman-hyperkitty can talk to hyperkitty and archive new messages, > but it can't talk to hyperkitty when attempting to process a queued > message. Ahhh! I had convinced myself that new messages were being archived, but now that you ask, they ARE NOT. I may have said they were at some point, and I apologize if I did. Now I feel less confused. It appears that archiving stopped when I did the migration from "Debian package layout" to "source layout" and upgraded to V3.3.8. I'll bet I munged a config file or two. I was struggling with what to keep from Debian layout and what to bring over from the source install instructions and I haven't gone back through to clean them up. I had previously figured it could not be a configuration issue since some messages were making it into the archive and some were not, but now that I see NONE are making it, this makes the problem less daunting. >> Following is an excerpt from mailman.log. Note that the "first >> section" (from DOCTYPE at top to 404 at bottom) is repeated four times >> (maybe not identical; but similar) (so I did not include it to save >> room) before the Traceback appears. >> >> Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list >> found >> Jun 25 00:13:04 2023 (386086) ACCEPT: >> <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> >> Jun 25 00:13:04 2023 (386090) HyperKitty failure on >> https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > I just went to that URL and got a 404. This is a serious problem. > https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should > return some documentation of the API. > > https://lists.netlojix.com/archives/api/ does work and returns the > expected information. > > Your urls.py file probably contains in its urlpatterns list > ``` > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ``` > The simplest fix is to add > ``` > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > ``` > to that list. I see many ursl.py files all over the system, but none that appear to be where I'd expect them to be for processing by any executables. Is this a file I should have copied over and edited, or created from scratch and somehow missed? I don't see anything about it in the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html> (although I do see a post from last July from someone stating it got missed in the instructions back then). > Another way to fix this is in your mailman-hyperkitty.cfg, you have > ``` > base_url: https://lists.netlojix.com/hyperkitty > ``` > Change that to > ``` > base_url: https://lists.netlojix.com/archives > ``` Done, and restarted both services, but I'm not seeing a difference when I go to <https://lists.netlojix.com/hyperkitty/api/> (I was getting a "Page not found", and still get that). > but it wouldn't hurt to add the `^postorius/` and `^hyperkitty/` patterns > to urls.py anyway.

3 years, 2 months

Re: Clean-up of non-members

by Odhiambo Washington

On Tue, Dec 24, 2024 at 8:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> I saw that too. Reported > >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > > > > It isn't clear to me what I should do to mitigate the error. > > > Apply this patch: > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - dn = address.display_name or member.user.display_name > + # Non-members may have empty address.display_name and > member.user can > + # be None resulting in AttributeError on member.user.display_name. > + try: > + dn = address.display_name or member.user.display_name > + except AttributeError: > + dn = '' > if email_only or not dn: > print(address.original_email, file=outfp) > else: > ``` > Thank you. Now only if you can help me reconcile the fact that Postorius tells me that I have ``` List Nonmembers (872) ``` ..while the CLI command gives me only 13 addresses. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

Re: Clean-up of non-members

by Odhiambo Washington

On Wed, Dec 25, 2024 at 8:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 23:35, Odhiambo Washington via Mailman-users wrote: > > > > Now only if you can help me reconcile the fact that Postorius tells me > that > > I have > > ``` > > List Nonmembers (872) > > > > ``` > > > > ..while the CLI command gives me only 13 addresses. > > > How are you invoking the `mailman nonmembers` command? I suspect it is > not using the proper mailman.cfg. Does `mailman info` show the correct > mailman.cfg. > ``` (venv) mailman@eu:~$ whoami mailman (venv) mailman@eu:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman:XXXXXXXXX@localhost /mailmansuite?charset=utf8mb4&use_unicode=1 devmode: DISABLED REST root url: https://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC Agnes <agnesa(a)REDACTED.com> Angela M <angelam(a)REDACTED.org> <beatiemaina!!(a)REDACTED.com> <psgimode(a)REDACTED.ke> <jwothaxxx(a)\REDACTED.ke> <lgichdhdh(a)REDACTED.ke> <mrussher(a)REDACTED.org> <mutwiXXj3(a)REDACTED.com> <news@REDACTED> Nesema <xxxxxx(a)kictanet.or.ke> Robert M <xxxxxxo(a)yahoo.com> <telasalma17@ REDACTED > <wambdddddd(a)REDACTED.ke> (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC | wc -l 13 (venv) mailman@eu:~$ ``` It uses the correct config file. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

Mailman-users search results for query "Postorius"