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

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by tlhackque

On 12-Jul-17 12:39, Mark Sapiro wrote: > > Also, with respect to Mailman 2.1, if you want the scrubber to preserve > file names and extensions, set the following in mm_cfg.py > > SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False > SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True > > and if you want scrubbed HTML to not be HTML escaped so it renders > rather than looking like raw html, set > > ARCHIVE_HTML_SANITIZER = 3 > > but note this comment from Defaults.py > >> # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this >> # is very dangerous because it essentially means anybody can send an HTML >> # email to your site containing evil JavaScript or web bugs, or other >> # nasty things, and folks viewing your archives will be susceptible. You >> # should only consider this option if you do heavy moderation of your list >> # postings. > > This is an issue with HyperKitty as it appears this is what HyperKitty > does and there's no way to turn it off. > This warning seems a bit dated, though it's not completely wrong. It comes from the days when HTML was new, browsers were fragile, and javascript treated with suspicion. And virus/spam scanners for email were non-existent. Today, it's a very rare website that doesn't rely on javascript (Postorious and Hyperkitty use JS). Browsers, while they still have bugs, are much more defensive. And there are plenty of truly evil sites that they have to defend against. It is certainly true that archived e-mail can turn your site into an unknowing distributor of malware: FLASH bugs, documents with embedded buffer overflows, cross-site scripting and the other many ills of the day. Wikis deal with this frequently. However, in these cases, your mailing list has distributed the same bits to your subscribers - a community that you probably care more about than a random visitor to your (open) archive. I wouldn't run a list - public or private - where the traffic doesn't go through SPAM and virus filtering before Mailman sees it. (SpamAssassin and ClamAV are good open-source solutions.) And once you've done that (and Mailman 3's optional DMARC), most of these attacks are defanged/mitigated. This is essentially automated moderation - to a point. Note that all the Djano authentication schemes packaged with Mailman (facebook, google, etc) rely on javascript and are sites littered with what the comment refers to as "webbugs" - Google Analytics, tracking cookies, browser fingerprinting, 0 size images (the original webbug). They make money (and have become mainstream) using technologies that were considered anti-social when that warning was written. (Personally, I still think of them as anti-social, but the public has chosen to pay for services with privacy...) While some may elect to stick with the highly restrictive policies of "plain text only", this limits the information content and applicability of the the platform. Whether this is acceptable depends on the community that you serve. Mailman can be an effective mechanism to deliver rich media on a "push" basis. And that's "rich" by 1980 standards (bold, well-formatted tables, an attached agenda or document package); not even "rich" by today's (sleeping cat videos...). I think that Mailman has to be able to handle today's rich media with a reasonable degree of safety and convenience. Including in the archives. I thought that was one of the goals for Mailman Version 3... I also think that the advice quoted above should be modified to better reflect these realities. Mailman isn't the only tool available to protect users from evil content, and aggressively filtering to plaintext is a very blunt instrument. Including anti-spam, anti-virus, DNS blacklisting, DKIM/DMARC tests in the delivery pipeline (most of which can be/is done before Mailman touches a post) should be strongly recommended. Checks for headers indicating checked-by local (anti-spam/anti-virus) agents should be available in the Mailman rulesets (and require some cooperation from the MTA to ensure that they can't be passed through from outside.) There is nothing wrong with running a plain text only site, if it serves your community. But if Mailman wants to be relevant in today's environment, it has to adapt to rich content as more than an unwelcome guest. (As I have :0)

7 years, 10 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Thu, Sep 30, 2021 at 4:09 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Thu, Sep 30, 2021, at 2:20 AM, Odhiambo Washington wrote: > > On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > >> > >> > >> > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> > >> wrote: > >> > > >> > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > > >> >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: > >> >>> 1. Confirmation emails to Users has wrong domain name (example.com > !) > >> >>> <https://docs.mailman3.org/en/latest/faq.html#id1> > >> >>> < > >> >> > >> > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > >> >>> > >> >>> > >> >>> This happens when your reverse (SSL) proxy isn’t setting up the > correct > >> >>> headers when proxying requests. Fix this by setting the right > >> >>> proxy_set_header directives: > >> >> ... > >> >>> How is this supposed to be mitigated in Apache when using WSGI? > >> >>> > >> >>> My config: > >> >>> > >> >>> WSGIDaemonProcess hyperkitty threads=25 > python-path=/usr/local/mailman > >> >>> user=mailman group=mailman > >> >>> WSGIPythonHome "/usr/local" > >> >>> WSGIProcessGroup hyperkitty > >> >> > >> >> > >> >> You are using mod_wsgi and not proxying at all, so this is not > relevant > >> >> in your case. > >> >> > >> >> Are you actually seeing this issue? If so, it might be related to > >> >> > >> >> > >> > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > >> >> > >> > > >> > My issue is related to this, but the documentation referred to is not > for > >> > the faint-hearted! > >> > I can't make head or tails of it. > >> > >> Click on “Domain” in Postorius from the top bar, which should take you > to > >> the Domains page. > >> > >> For your domain (in the “Mail Host” column), see the corresponding “Web > >> Host” column, it should look something like: > >> > >> lists.mailman3.org (lists.mailman3.org) > >> (Edit) > >> SITE_ID = 1 > >> > > > > Mine looks different, slightly. But there is no example.com at all. > > > > [image: Abhilash.png] > > > > > > > >> > >> on a new-ish version of Postorius. > >> > > > > I have the newest versions of everything, having installed only > yesterday. > > > > > >> > >> If it doesn’t show the right values and instead shows “example.com” for > >> you, click on the “Edit” link, which will take > >> you to a page that will allow you to edit both the values. > >> > > > > It shows the right values, but with "SITE_ID = 2". In my > settings_local.py > > I have SITE_ID = 1. > > I suppose the example.com is the one tied to SITE_ID = 1 and that is > what I > > have in my settings_local.py. > > That is most likely what is happening. > > > Should I edit my settings_local.py? > > Yes, please update it to have SITE_ID = 2 to correspond to the site you > want and restart. I did this, but there is still a problem: The hyperkitty URL still shows example.com. Maybe I need to re-import the database to clear this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 7 months

[MM3-users] Re: E-mail every minute: "Cron <www-data@sharky5> ..."

by Odhiambo Washington

On Sun, Jul 7, 2024 at 8:43 PM Robert Heller <heller(a)deepsoft.com> wrote: > At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > > > > On Sun, Jul 7, 2024 at 7:16Ã¢Â€Â¯PM Robert Heller <heller(a)deepsoft.com> > wrote: > > > > > At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington < > odhiambo(a)gmail.com> > > > wrote: > > > > > > > > > > > On Sun, Jul 7, 2024 at 4:12ÃƒÂƒÃ‚Â¢ÃƒÂ‚Ã¢Â‚Â¬ÃƒÂ‚Ã‚Â¯PM Robert > Heller <heller(a)deepsoft.com> > > > wrote: > > > > > > > > > What am I missing? I *think* I have mailman3 *mostly* setup, but > there > > > > > are > > > > > still some configuration things that are missing, but I am not sure > > > how to > > > > > fix > > > > > them (the docs are NOT clear). > > > > > > > > > > > > > Which docs are you relying on? > > > > > > https://docs.mailman3.org/en/latest/config-web.html > > > > > > I presume these are the official docs for mailman3 -- maybe they > aren't? > > > > > > > > > > > How about this - > > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > ?? > > > > > > I'm not using a virtual environment. I'm using all native Debian 12 > > > packages, > > > installed via apt. The virtual environment docs are actually even worse > > > (even > > > more confusing). > > > > > > Worse? :-) > > Even more confusing. Both sets of docs make various assumptions and don't > really explain things properly. Like everywhere where "settings.py" is > mentioned, it really means "/etc/mailman3/mailman-web.py" > No! It means /etc/mailman3/settings.py - literally! > In any case, the virtual environment docs are hard to relate to a "native" > install and are generally hard to follow, since they seem to jump all over > the > place. When one day you'll be able to internalize what a Python virtual environment is, you'll realize that it's VERY convenient. You will actually embrace it from that point onwards. (Spaghetti docs?) And it is hard to replace the various (and not > always consistent) virtual environment paths and settings files to the > "native" > paths. Actually, if you're this inclined to run everything natively, MM3 is perhaps not for you. Why? Because you'll not easily find help here. We focus on the virtual environment only as the standard.. Why? Because no one is willing to deal with ALL the OS-centric packaging out there. Python virtual environment is universal across all the OSes, I can say. > The "official" docs are just not useful to me, since I am not using a > virtual > environment. If a virtual environment is recomended, what is the point of > the > Debian 12 packages? We cannot answer that here. I guess they are meant for people like you who strive under pain :-) With the Python virtual environment, I can install and manage MM3 in almost any *nix OS. > Are they just not meant to be used? Really? Do you mean that I should use > a separate package management system for Mailman3? That > really sucks. > Yes, they are meant to be used. Noone denies that. However, they are not packaged by the Mailman Developers. Did you read one response from Mark Sapiro where he said, and I quote: ``` If you prefer to use the Debian packages, that's fine, but if using the Debian packages, your primary resource for support, documentation, bug reports, etc. should be Debian. See https://wiki.list.org/x/12812344 ``` So yes, go ahead and use the Debian packages. No one is stopping you. -- 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]

10 months, 1 week

[MM3-users] Re: Digests not working correctly

by Joel Lord

Now I'm on one of the lists in digest mode and I can see that it's a mess. Periodic digests are definitely NOT working, so I'll lay that out here. root@host2:/# cat /etc/cron.d/mailman # This goes in /etc/cron.d/mailman # Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory 0 23 * * * lists /usr/local/bin/mailman digests --periodic 0 23 * * * lists /usr/local/bin/mailman notify root@host2:/# grep digests /var/log/cron.log Jun 11 23:00:01 host2 CRON[1632765]: (lists) CMD (/usr/local/bin/mailman digests --periodic) Jun 12 23:00:01 host2 CRON[2177286]: (lists) CMD (/usr/local/bin/mailman digests --periodic) root@host2:/home/members/directory# su - lists lists@host2:~$ /usr/local/bin/mailman digests --periodic lists@host2:~$ ls var/lists/<list>/ digest.mmdf In this case I've got /usr/local/bin/mailman as a symlink to the mailman binary inside the venv's bin directory, just for simplicity. That digest.mmdf file is dated June 9th and clearly ought to have been cleared out on any of the nightly runs between then and today but has not. There are no errors anywhere I can find. How can I try and track this down? -Joel On 6/4/2023 10:15 PM, Joel Lord wrote: > The May 4th digest that went out was _also_ size-triggered, so this may > have nothing to do with periodic digests at all, and possibly my > periodic digests aren't working. I'm not on any of my own lists in > digest mode, I'm slowly extracting diagnostic information out of people > who are. Also, since this is a ~2 month cycle, it's really difficult to > get data points to work with. I'll need to remember to go in and look > when this settles down again (new cycle of activity started last night) > to see if there's anything left pending. > > (venv) root@host2:/home/lists/mailman/venv/bin# pip freeze | grep -i hyper > HyperKitty==1.3.7 > > On 6/4/2023 10:05 PM, Mark Sapiro wrote: >> On 6/4/23 18:35, Joel Lord wrote: >>> >>> The periodic digests do seem to be coming out. I also now have >>> confirmation that the one message in this morning's digest that was >>> from May 4th was also included in the last digest back on May 4th, so >>> it seems that the one message was left behind in the digest queue >>> when the periodic digest was sent. >> >> I don't see how that can happen. The process that sends a digest >> renames the var/lists/<list-id>/digest.mmdf mailbox file in which the >> messages are accumulated to >> var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and >> <issue> are the volume and issue numbers of that digest, and then >> queues a message in the `digest` queue to tell the digest runner to >> create the digest from the messages in that mbox and send it. Thus, it >> leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that >> is created anew when the next post arrives. Further, if there is a >> non-empty digest.mmdf file, its messages should be sent no later than >> the next 11 PM `cron digests`. >> >> >>> There was one earlier message to the list back on May 4th, before the >>> one that got duplicated, but I can't tell if that triggered a >>> size-based digest to be sent: the logs aren't clear enough on that >>> detail for me to tell > >> >> OK >> >> >>> Just to inform things: >>> >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman >>> django-mailman3==1.3.9 >>> mailman==3.3.8 >>> mailman-hyperkitty==1.2.1 >>> mailman-web==0.0.6 >>> mailmanclient==3.3.5 >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper >>> mailman-hyperkitty==1.2.1 >> >> Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is >> up to date as are the others. >> >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post >>> postorius==1.3.8 >>> >>> >> > -- Joel Lord

1 year, 11 months

[MM3-users] Re: psycopg2 error?

by Odhiambo Washington

On Fri, Oct 27, 2023 at 4:38 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/26/23 01:03, Odhiambo Washington wrote: > > > > <CUT> > > root@debian12:/home/wash# systemctl status mailman3.service > > × mailman3.service - GNU Mailing List Manager > > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; > preset: > > enabled) > > Active: failed (Result: exit-code) since Thu 2023-10-26 09:36:41 > EAT; > > 8s ago > > Process: 1893842 ExecStart=/opt/mailman/venv/bin/mailman start > > (code=exited, status=1/FAILURE) > > CPU: 789ms > > > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: dbapi = > > dbapi_meth(**dbapi_args) > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: > > ^^^^^^^^^^^^^^^^^^^^^^^^ > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > > > "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > > line 690, in import_dbapi > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: import psycopg2 > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", > line > > 51, in <module> > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: from > > psycopg2._psycopg import ( # noqa > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: SystemError: > > initialization of _psycopg raised unreported exception > > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Control > > process exited, code=exited, status=1/FAILURE > > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Failed > with > > result 'exit-code'. > > Oct 26 09:36:41 debian12.wash.lan systemd[1]: Failed to start > > mailman3.service - GNU Mailing List Manager. > > </CUT> > > Is your database PostgreSQL or some other? If it's not PostgreSQL, see > the thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > - particularly > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Also see > > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… > where it now says in part "This will install latest release of Mailman > Core, and Python bindings for Postgresql database. If you are using a > different database manager, do not install psycopg2-binary." > So my database is PostgreSQL-15: ``` postgres@debian12:~$ psql psql (15.3 (Debian 15.3-0+deb12u1)) Type "help" for help. postgres=# ``` Below is the output of `mailman info` which for some reason I forgot to attach in the initial post. Maybe it contains something useful? ``` (venv) mailman@debian12:~$ mailman info Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1077, in main with self.make_context(prog_name, args, **extra) as ctx: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 943, in make_context self.parse_args(ctx, args) File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1644, in parse_args rest = super().parse_args(ctx, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1408, in parse_args value, args = param.handle_parse_result(ctx, opts, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 2400, in handle_parse_result value = self.process_value(ctx, value) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 2362, in process_value value = self.callback(ctx, self, value) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/core/initialize.py", line 229, in initialize initialize_2(propagate_logs=propagate_logs) File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/core/initialize.py", line 187, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/database/factory.py", line 57, in create database.initialize() File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/database/base.py", line 117, in initialize self.engine = create_engine( ^^^^^^^^^^^^^^ File "<string>", line 2, in create_engine File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned return fn(*args, **kwargs) # type: ignore[no-any-return] ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/engine/create.py", line 601, in create_engine dbapi = dbapi_meth(**dbapi_args) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi import psycopg2 File "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> from psycopg2._psycopg import ( # noqa SystemError: initialization of _psycopg raised unreported exception ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 6 months

[MM3-users] Re: moving lists to another server

by Odhiambo Washington

On Mon, Nov 20, 2023 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/20/23 00:58, Odhiambo Washington wrote: > > > > What is the command to export the archive as a mbox from the DB? > > I can't figure out which option it is by looking at 'mailman-web -h'. > > Normally you do this on the old server via the HyperKitty web UI which > has download buttons which do things like > > > https://example.com/archives/list/list@example.com/export/list@example.com.… > > or for a partial archive > > > https://example.com/archives/list/list@example.com/export/list@example.com-… > > However, in your case I don't think you have the old installation working > any more so the above won't help. > I had a dump of the old installation actually - both databases. The above has actually helped and I obtained the archive. > > BTW, how will ' mailman addmembers' treat a file containing: > > ``` > > Firstname Lastname <email@address> > > Onlyname <email2@address> > > ``` > > Correctly. It will import email@address with display name = 'Firstname > Lastname' and email2@address with display name = 'Onlyname'. > Super! > > I have opted for the simple way to do this: > > 1. Create the site in Django Admin and create/configure the list in > > Postorius > > 2. Add the members from the file dump, with delivery set to regular. > > 3. Send the members an email informing them that they need to set their > > delivery preferences. > > > > I am stuck on the issue of exporting the archives to mbox file as already > > stated above. > > Perhaps you can export the mbox via the web UI on the old server or > maybe temporarily create a second mailman-web on your server with the > old mailman-web database and use that web UI. That's exactly how I did it and got the archives. > Otherwise, if you have a working mailman-web that can access this > database, you could try > something like > ``` > $ mailman-web shell > > >>> from hyperkitty.lib.compat import get_list_by_name > >>> mlist = get_list_by_name('list_name_only', 'list_domain') > >>> with open('output.mbox', 'wb') as fp: > ... for email in mlist.emails.order_by("archived_date").all(): > ... fp.write(email.as_bytes() + b'\n') > ... > >>> > ``` > I tested the above out of curiosity. It failed. There are 9 lists in the setup, but I am only interested in 1. ``` (venv) mailman@debian12:~$ mailman-web shell Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Type 'copyright', 'credits' or 'license' for more information IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help. In [1]: from hyperkitty.lib.compat import get_list_by_name In [2]: mlist = get_list_by_name('list_name_only', 'list_domain') --------------------------------------------------------------------------- Http404 Traceback (most recent call last) Cell In[2], line 1 ----> 1 mlist = get_list_by_name('list_name_only', 'list_domain') File ~/venv/lib/python3.11/site-packages/hyperkitty/lib/compat.py:37, in get_list_by_name(list_name, domain) 35 matching = list(MailingList.objects.filter(name__startswith=list_name+"@")) 36 if len(matching) == 0: # no candidate found ---> 37 raise Http404("No archived mailinglist by that name") 38 if len(matching) == 1: # only one candidate 39 return matching[0] Http404: No archived mailinglist by that name ``` Was I supposed to substitute something for the real listname of the list I wanted? Another thing - totally unrelated - that surprised me: While using the commented-out block below, I could not click and get anything beyond http://http://list.name/mailman3 as anything to do with /postorius/xxxxx gave "Page not found" error. However, with the second config block that uses the UNIX socket, I am able to access everything ``` #<IfModule mod_proxy.c> # ProxyPreserveHost On # ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3" # ProxyPass "/archives" "http://127.0.0.1:8010/archives" # ProxyPass "/accounts" "http://127.0.0.1:8010/accounts" # ProxyPass "/admin" "http://127.0.0.1:8010/admin" # ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile" # </IfModule> ProxyPassMatch ^/static/ ! ProxyPassMatch ^/favicon.ico ! ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ ``` Why is it that the UNIX socket option worked flawlessly while the other option failed??? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 5 months

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, No luck :( (venv) mailman@new-server ~ (v3.3.9)> *pip freeze | egrep "mailman-web|django-mailman3|django-allauth"* django-allauth==0.59.0 django-mailman3==1.3.11 mailman-web==0.0.8 (venv) mailman@new-server ~ (v3.3.9)> *pip install -U django-allauth==0.58.0* Collecting django-allauth==0.58.0 Downloading django-allauth-0.58.0.tar.gz (861 kB) ---------------------------------------- 861.7/861.7 KB 9.4 MB/s eta 0:00:00 Installing build dependencies ... done Getting requirements to build wheel ... done Installing backend dependencies ... done Preparing metadata (pyproject.toml) ... done Requirement already satisfied: requests-oauthlib>=0.3.0 in ./venv/lib/python3.10/site-packages (from django-allauth==0.58.0) (1.3.1) Requirement already satisfied: Django>=3.2 in ./venv/lib/python3.10/site-packages (from django-allauth==0.58.0) (4.1.13) Requirement already satisfied: pyjwt[crypto]>=1.7 in ./venv/lib/python3.10/site-packages (from django-allauth==0.58.0) (2.8.0) Requirement already satisfied: requests>=2.0.0 in ./venv/lib/python3.10/site-packages (from django-allauth==0.58.0) (2.31.0) Requirement already satisfied: python3-openid>=3.0.8 in ./venv/lib/python3.10/site-packages (from django-allauth==0.58.0) (3.2.0) Requirement already satisfied: asgiref<4,>=3.5.2 in ./venv/lib/python3.10/site-packages (from Django>=3.2->django-allauth==0.58.0) (3.7.2) Requirement already satisfied: sqlparse>=0.2.2 in ./venv/lib/python3.10/site-packages (from Django>=3.2->django-allauth==0.58.0) (0.4.4) Requirement already satisfied: cryptography>=3.4.0 in ./venv/lib/python3.10/site-packages (from pyjwt[crypto]>=1.7->django-allauth==0.58.0) (41.0.7) Requirement already satisfied: defusedxml in ./venv/lib/python3.10/site-packages (from python3-openid>=3.0.8->django-allauth==0.58.0) (0.7.1) Requirement already satisfied: urllib3<3,>=1.21.1 in ./venv/lib/python3.10/site-packages (from requests>=2.0.0->django-allauth==0.58.0) (2.1.0) Requirement already satisfied: charset-normalizer<4,>=2 in ./venv/lib/python3.10/site-packages (from requests>=2.0.0->django-allauth==0.58.0) (3.3.2) Requirement already satisfied: idna<4,>=2.5 in ./venv/lib/python3.10/site-packages (from requests>=2.0.0->django-allauth==0.58.0) (3.6) Requirement already satisfied: certifi>=2017.4.17 in ./venv/lib/python3.10/site-packages (from requests>=2.0.0->django-allauth==0.58.0) (2023.11.17) Requirement already satisfied: oauthlib>=3.0.0 in ./venv/lib/python3.10/site-packages (from requests-oauthlib>=0.3.0->django-allauth==0.58.0) (3.2.2) Requirement already satisfied: typing-extensions>=4 in ./venv/lib/python3.10/site-packages (from asgiref<4,>=3.5.2->Django>=3.2->django-allauth==0.58.0) (4.9.0) Requirement already satisfied: cffi>=1.12 in ./venv/lib/python3.10/site-packages (from cryptography>=3.4.0->pyjwt[crypto]>=1.7->django-allauth==0.58.0) (1.16.0) Requirement already satisfied: pycparser in ./venv/lib/python3.10/site-packages (from cffi>=1.12->cryptography>=3.4.0->pyjwt[crypto]>=1.7->django-allauth==0.58.0) (2.21) Building wheels for collected packages: django-allauth Building wheel for django-allauth (pyproject.toml) ... done Created wheel for django-allauth: filename=django_allauth-0.58.0-py3-none-any.whl size=1157319 sha256=a430c552101d1ad47bc00b16d1c1d6df728afacdd13823927b4cbfb02c35dbfc Stored in directory: /local/mailman/.cache-ubuntu-22.04/pip/wheels/55/0a/79/e199827a18f310906c2a90b0e92b89c41daf21d2a502db6710 Successfully built django-allauth Installing collected packages: django-allauth Attempting uninstall: django-allauth Found existing installation: django-allauth 0.59.0 Uninstalling django-allauth-0.59.0: Successfully uninstalled django-allauth-0.59.0 Successfully installed django-allauth-0.58.0 (venv) mailman@new-server ~ (v3.3.9)> *mailman-web migrate* System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email...Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 257, in query _mysql.connection.query(self, query) MySQLdb.OperationalError: (2013, 'Lost connection to MySQL server during query') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 96, in wrapped res = handle_func(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/migrate.py", line 349, in handle post_migrate_state = executor.migrate( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/migration.py", line 130, in apply operation.database_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/operations/fields.py", line 235, in database_forwards schema_editor.alter_field(from_model, from_field, to_field) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 788, in alter_field self._alter_field( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 858, in _alter_field self.execute(self._delete_unique_sql(model, constraint_name)) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 199, in execute cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/local/mailman/venv/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 257, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (2013, 'Lost connection to MySQL server during query') (venv) mailman@new-server ~ (v3.3.9) [0|1]> *more /etc/mailman3/settings.py* # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * # Settings below supplement or override the defaults. #: Default list of admins who receive the emails from error logging. ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) # Postgresql database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', # TODO: Replace this with the password. 'PASSWORD': '***********', 'HOST': 'localhost', # PORT: set to empty string for default. 'PORT': '3306', # OPTIONS: Extra parameters to use when connecting to the database. #'OPTIONS': { # Set sql_mode to 'STRICT_TRANS_TABLES' for MySQL. See # https://docs.djangoproject.com/en/1.11/ref/ # databases/#setting-sql-mode # 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", # 'charset': 'utf8mb4', #}, } } # 'collectstatic' command will copy all the static files here. # Alias this location from your webserver to `/static` STATIC_ROOT = '/local/mailman/web/static' # enable the 'compress' command. COMPRESS_ENABLED = True # Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/local/mailman/web/logs/mailmanweb.log' #: See https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "127.0.0.1", # "lists.your-domain.org", # Add here all production domains you have. "*" ] #: See https://docs.djangoproject.com/en/dev/ref/settings/#csrf-trusted-origins (venv) mailman@new-server ~ (v3.3.9)> *mysql -umailman3web -p -h localhost mailman3web* Enter password: Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 32 Server version: 10.6.12-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [mailman3web]> show tables; +-------------------------------+ | Tables_in_mailman3web | +-------------------------------+ | account_emailaddress | | account_emailconfirmation | | auth_group | | auth_group_permissions | | auth_permission | | auth_user | | auth_user_groups | | auth_user_user_permissions | | django_admin_log | | django_content_type | | django_mailman3_maildomain | | django_mailman3_profile | | django_migrations | | django_q_ormq | | django_q_schedule | | django_q_task | | django_session | | django_site | | hyperkitty_attachment | | hyperkitty_email | | hyperkitty_favorite | | hyperkitty_lastview | | hyperkitty_mailinglist | | hyperkitty_profile | | hyperkitty_sender | | hyperkitty_tag | | hyperkitty_tagging | | hyperkitty_thread | | hyperkitty_threadcategory | | hyperkitty_vote | | socialaccount_socialaccount | | socialaccount_socialapp | | socialaccount_socialapp_sites | | socialaccount_socialtoken | +-------------------------------+ 34 rows in set (0.000 sec) Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Mon, 18 Dec 2023 at 17:11, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/18/23 6:24 AM, Helio Loureiro wrote: > > Hi, > > > > Indeed it was the configuration. It was placed into > > /etc/mailman3/mailman-web.py. After a I changed to > > /etc/mailman3/settings.py a few things advanced a little bit more. > > > > I had to figure out how to fix mysqlclient installation since there > isn't a > > mention about it and the simple "pip install mysqclient" was breaking > with > > pkg-config issues. But it did work at the end. > > > > Now I can see further messages on mailman3-web than before. > > > > (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate > > System check identified some issues: > > > > WARNINGS: > > account.EmailAddress: (models.W036) MariaDB does not support unique > > constraints with conditions. > > HINT: A constraint won't be created. Silence this warning if you don't > care > > about it. > > account.EmailAddress: (models.W043) MariaDB does not support indexes on > > expressions. > > HINT: An index won't be created. Silence this warning if you don't care > > about it. > > Operations to perform: > > Apply all migrations: account, admin, auth, contenttypes, > > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > > socialaccount > > Running migrations: > > Applying account.0004_alter_emailaddress_drop_unique_email...Traceback > > (most recent call last): > > > I'm not sure why there would be an issue with this migration, but there > is a possible compatibility issue depending on how you installed things. > > django-mailman3<=1.3.11 is not compatible with django-allauth>=0.58. > > In your venv, try > ``` > pip install django-allauth\<0.58 > ``` > > -- > 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 helio(a)loureiro.eng.br >

1 year, 4 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/22 00:00, Odhiambo Washington wrote: > > > > These are my files: > > 1. urls.py > > <CUT > > > from django.conf.urls import include > > from django.urls import re_path > > from django.contrib import admin > > from django.urls import reverse_lazy > > from django.views.generic import RedirectView > > > > urlpatterns = [ > > re_path(r'^$', RedirectView.as_view( > > url=reverse_lazy('list_index'), > > permanent=True)), > > re_path(r'^postorius/', include('postorius.urls')), > > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > > re_path(r'', include('django_mailman3.urls')), > > re_path(r'^accounts/', include('allauth.urls')), > > # Django admin > > re_path(r'^admin/', admin.site.urls), > > re_path(r'^mailman3/', include('postorius.urls')), > > re_path(r'^archives/', include('hyperkitty.urls')), > > ] > > </CUT> > > > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, but > having both is OK. > That urls.py was picked from https://wiki.list.org/DOC/Mailman%203%20installation%20experience. Maybe that page needs some edits/revision now? > 2. apache.conf > > <CUT> > > ... > > Alias /static "/opt/mailman/mm/static" > > <Directory "/opt/mailman/mm/static"> > > Require all granted > > </Directory> > > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > > > This will send every http request to mod_wsgi except for requests to > /static. This is OK if there are no other web sites on this server and > the only http requests are for Django related things. > This is just a virtual host. There are other websites on the server. ... > > I have tested with creating all those commented out aliases and that > ended > > up still giving me /mailman3/mailman3/* which I did not > > like, although everything appeared to work. > > I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" > > and now when I type https://mm3-lists.kictanet.or.ke I end > > up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course > something > > has appended "/mailman3" > > So this has resulted in all URLs having /mailman3/ appended, except for > the > > /archives link. > > > How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > I have uncommented the line "WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py", I don't see any definition for it in urls.py as well. Perhaps that's the issue? When I uncomment /user-profile, I end up with an ugly URL: https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ So instead of aliasing the /user-profile, I have decided to add another definition to urls.py: re_path(r'^user-profile/', include('allauth.urls')), Which I think gives me a cleaner URL: https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ I also had to alias /accounts, which then brings me to: https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I believe is fine because one gets the option to either login or signup. And I think that "/account" and "/user-profile" are synonymous. > Now my question is about what could be adding the /mailman3. Is it > possible > > that I installed something out of the ordinary? > > > It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time > (I now use gunicorn on all the sites I manage), but when I did I think I > had > WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > > and all the URLs were like https://example.com/mm3/mailman3/..., > https://example.com/mm3/archives/..., etc. > I already had gunicorn working too, but I just need to also figure out this mod_wsgi. I will stop bothering about the /mailman3 being appended, as long as it serves the required purpose. Thank you for all the help. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: hello， Discussion on how to subscribe to the mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/16/23 18:55, 朱超 wrote: > > Hi, When I subscribe the email list in Subscription Policy is > > confirm, Some problems happen in here： > > 1.Some mail mua reject send the confirm the message, because the > > length of recipient is too long. for exmaple: > > requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, > > and the mail mua reject to modify about this. > > The default English template says in part: > > Before you can start using GNU Mailman at this site, you must first > confirm that this is your email address. You can do this by replying to > this message. > > Or you should include the following line -- and only the following > line -- in a message to $request_email: > > confirm $token > > I.e. It gives an alternative method if `reply` doesn't work. You can > provide a custom version of this template with different wording if you > think you can improve it. The problem is the reply address, though. Changing the template to suggest only the "confirm $token" in body method doesn't help people who hit R expecting that should work, especially since many "user fiendly" (misspelling intentional) MUAs don't display the address. Avoiding that requires code changes, I guess? > > 2.It is inconvenient for users to use. Many people will > > mistakenly think that after clicking the subscribe button, it > > will be successful, and they will not process the email. > step, you can set Subscription Policy to Open, but then anyone can > maliciously subscribe third parties to the list. *Please* do not do this if your server is exposed to the Internet. There are bots that search for such servers, and sell lists of them to people who want to DOS mailboxes. You may find yourself banned across the Internet. The only real alternative to confirmation is approval by moderators. I believe Mailman 3 offers that alternative as Mailman 2 did, can't check at the moment. > > Regarding the discussion on the subscription method of the > > mailing list, should we consider optimizing the subscription > > method of the mailing list, for example: > > 1. use the method of sending a verification code to subscribe by > > email，When you receive the verification code sent by the > > mailing list and fill it in again, you can subscribe > > successfully。 > > How is this different from the present method. Just wording. I think they are thinking of the "invite" option that was provided in Mailman 2 mass subscribe (again, I think Mailman 3 retains it but I never ever used it so I don't recall for sure). But it doesn't make sense for a user-initiated interaction. > If you want, you can make > a custom template and include something like: > > Alternatively, you can confirm by going to the URL > > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token If I understand the OP's PoV correctly, I think I would change the list information page to say "Send a personal invitation to join the list to [email address here]. If you aren't a subscriber, you can invite yourself." And change the word "confirm" in the confirmation template to "subscribe". > We don't include that in the default template because Mailman core > doesn't know if you even have a web UI or how to access it if you > do. We should fix that, at least if the web interface is Postorius (wishlist, assigned to me): https://gitlab.com/mailman/mailman/-/issues/1055 @mark https://gitlab.com/mailman/mailman/-/issues/901 Maybe we can close this? I'm not sure why it was left open since there's no action proposed for Mailman improvement. > > 2. use the email to send a connection to confirm the > > subscription，People click the link to be redirected to a > > confirmation page to subscribe to the email。 > > See above. Indeed, AFAICS almost everything the OP is suggesting amounts to an identical procedure as far as the Mailman server is concerned, it's just described to the subscriber differently. The one exception is the suggestion to eliminate the confirmation step, and while that is supported, it's quite likely to cause problems for third parties and eventually for the Mailman site unless you have an alternative ground source of truth such as an employee database. Steve

2 years, 3 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Ken Alker

--On Monday, June 26, 2023 8:24 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 12:01 AM, Ken Alker wrote: >> When I view a list via Postorius the "Held Messages" menu item has an >> inverse-red-"2" next to it, as if there are two held messages. There >> are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the >> held messages should be in "pipeline" subdirectory). When I click on >> "Held Messages" I get "Something went wrong" followed by "HTTP Error >> 500: {"title": "500 Internal Server Error"}". How do I fix this? > > The held messages are not in any queue. They are stored in Mailman's > var/messages/ hierarchy. They can be examined with `mailman qfile` Is the var/messages hierarchy also where all the archived emails are stored for future viewing via the web interface? > Also, there is a long thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be > relevant. I have never used the mailman shell before, but based on the referenced thread I learned to do this (note that the thread also taught me how to rewrite it to narrow down to just the list with issues so I didn't delete held messages in other lists, if my case): for verification: venv) mailman@speedy:~/web/logs$ mailman shell -l sbarc-list(a)lists.netlojix.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list >>> requests = IListRequests(m) >>> first = True >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(m.list_id) ... print (f"""\ ... Sender: {data['_mod_sender']} ... Subject: {data['_mod_subject']} ... Date: {data['_mod_hold_date']} ... Reason: {data['_mod_reason']} ... """) ... and then to delete the two messages: (venv) mailman@speedy:~/web/logs$ mailman shell -l sbarc-list(a)lists.netlojix.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list >>> requests = IListRequests(m) >>> first = True >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(m.list_id) ... print(f'request id: {request.id}, deleting') ... requests.delete_request(request.id) ... sbarc-list.lists.netlojix.com request id: 27, deleting request id: 28, deleting >>> The result of this, however, was that the web interface still claimed I had two held messages. I wasn't sure if there was some cron-type "sweeper" process I had to wait to auto-run or if I had to manually do something to create an update. I then realized that the sample script had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered the script (but it didn't spit out that it deleted anything this time) and got an error when I did the commit. So, I figured the messages HAD been delete and the commit wasn't really necessary. When I went back to the web interface, the number of held messages was at 0 and I no longer get the original error when clicking on "Held messages", so my issue is solved. But this does leave me with some educational questions: 1) Did I affect something somehow with my "commit", or was there a job that cleaned things up (if so, what job)? 2) Is the "commit" even necessary (I saw it in someone else's script in the thread)? 3) Is there a way to save a script and then execute it via shell rather than typing it in every time (it appears from the examples that people are typing them in every time, which is super tedious; I didn't paste for fear of doing something damaging, but maybe that would work)? 4) Are the request.id's of the messages dynamic/changing, or are they fixed for life? I thought I'd delete based on exact request.id without looping but I was afraid maybe they were changing over time and that this wouldn't be a good idea. Might be nice to know for the future. Thanks for the guidance! Ken

1 year, 10 months

Search results for query "sapiro"