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

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/23/21 9:18 AM, Mark Sapiro wrote: > However, that's not the issue. You originally reported and I didn't look > closely enough: > >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > That URL is from a Mailman 2.1 installation. Are you still running > Mailman 2.1? I'm not, but that, and me not looking closely, was the problem. The system doesn't run MM2.1 any more, and no longer has it installed. But I failed to notice the dates on those 'admindb' messages: They were from the day of the upgrade, about 30 minutes before decommissioning MM2.1. And the docs do say explicitly to deal with any pending tasks before doing a cutover. The task-pending message that MM3 sends to list owners and moderators just says generically to check the dashboard, without providing a URL. Can that be modified to provide an explicit URL, something like this? https://lists.example.com/mailman3/lists/listname Thanks again for spotting this. dn

3 years, 9 months

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Odhiambo Washington

PS: I beg you to put your responses below the last one. Makes the hierarchy look better. Now, have you edited your /etc/mailman3/mailman-hyperkitty.cfg and restarted MM3? On Tue, Jul 29, 2025 at 3:18 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > Odhiambo, long time no hear from you. Hope you are doing well. > > The last archived post for that specific list is July 3rd. 2025. We do not > see the one for July 25th. Also, I just noticed something else in the logs, > apparently the server is still having "SSLCertVerificationError" issues > even after updating the DigiCert, CA-Certificate,etc. I must be missing > something else. > > Based on that, looks like the archiving is failing still due to the > "SSLCertVerificationError". > > The spool directory now has 8 *.pck files in it. However, I do not see the > original ones from 7/25 > > ~# ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 14725 Jul 29 08:07 > 1753790859.2498085+320096cb9852779b55a4cbb1e4f9603736ebd78d.pck > -rw-rw---- 1 mailman mailman 15122 Jul 29 08:07 > 1753790859.2437658+7fddf881d592f27be60e32aa5b3c34c7077b9988.pck > -rw-rw---- 1 mailman mailman 6399 Jul 29 08:07 > 1753790859.2370558+ee410eb31691bf2854cca46c64e80e3bf61c3523.pck > -rw-rw---- 1 mailman mailman 26619 Jul 29 08:07 > 1753790859.230345+b2e70f5b65900731895bbee5a3d83401f1500567.pck > -rw-rw---- 1 mailman mailman 15676 Jul 29 08:07 > 1753790859.2225533+82371c8a0202d62eaa046dd3633a23d6837d7a80.pck > -rw-rw---- 1 mailman mailman 98273 Jul 29 08:07 > 1753790859.2136636+8ee9273fbbaf4352d482e69d177e2eb2824078a5.pck > -rw-rw---- 1 mailman mailman 98109 Jul 29 08:07 > 1753790859.2026713+49d82ecd57eda7eaa582ba925449e2343bea5c56.pck > -rw-rw---- 1 mailman mailman 88479 Jul 29 08:07 > 1753790859.191489+162aa89dcac50ca6f5463ce1098c828728af12d1.pck > > > > > ------------------------------ > *From:* Odhiambo Washington <odhiambo(a)gmail.com> > *Sent:* Tuesday, July 29, 2025 7:59 AM > *To:* mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>; Mark > Sapiro <mark(a)msapiro.net> > *Cc:* Willie Castillo <Willie.Castillo(a)caemilusa.com> > *Subject:* Re: [MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails > - Hyperkitty - CERT Issue > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < > Willie.Castillo(a)caemilusa.com> wrote: > > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. > > > While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what > is documented so that the issue doesn't recur: > ``` > [general] > base_url: http://127.0.0.1:8000/archives/ > <https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV…> > api_key: Secret_Hyperkitty_API_Key > ``` > > PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s > questions quoted below: > ``` > Did the new post get archived? If so, why is last post at still July 25, > 2025? If no, why not. The post must go to the archiver to cause the > queue to be processed. > > If the post was archived and the July 25 messages are still queued, > what's in Mailman's mailman.log. There should be error messages and > tracebacks indicating the issue. > ``` > > -- > 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 > <https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht…> > ] > -- 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]

2 months, 2 weeks

[MM3-users] Re: MM3 not starting afte an upgrade

by Gelpi Andrea

Il 23/07/20 23:05, Mark Sapiro ha scritto: > On 7/23/20 4:35 AM, Gelpi Andrea wrote: >> Hi, >> to day in a Debian system I upgraded some packages. >> >> After the MM3 doesn't start anymore. . . . >> Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0) >> Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1] >> Operation not permitted > > > I think you have a stale lock issue and the master is trying to > determine if the process that set it still exists. > > Remove Mailman's var/locks/master.lck* > Thanks Mark, now MM3 star but postorius is not working. The web pagge return: An error occurred while processing your request. I receive an email with: ... Exception Type: KeyError at /postorius/lists/ Exception Value: 'file' Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data Is that related to Django id setting or there is a passphrase mismach some where? How can I check? -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 2 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Alex Schuilenburg

On Fri, 2020-10-02 at 12:00 -0700, Mark Sapiro wrote: > [...]There's much more detail in my reply at< > https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422894486>;, > butyou can fix the ResponseNotReady() issue from the sync_mailman job > byfinding the entries in the hyperkitty_sender table with > invalidaddresses in the address column and deleting them. As per comment https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422958260 , it was not a simple delete, but an insert/update/delete > We can try to address this specific issue in hyperkitty_import, > butthere are in general various mbox defects that we can't detect. > mboxesneed to be checked for unescaped `From ` lines in message > bodies andother defects before importing them. The Mailman 2.1 > bin/cleanarchscript and the new hyperkitty/contrib/check_hk_import > script can helpwith some of this. I ran both on the original archive, cleanarch made no changes and check_hk_import just retported the number of messages. As it turns out, the message was imported, but with the dodgy email as sender which was fixed by the insert/update as per my comment. Hope you have some success with the redacted mbox example. Cheers -- Alex

5 years

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote: > > On 3/13/21 11:14 AM, John Covici wrote: > > > > Now one thing came up while trying to create the database, I got a > > traceback complaining about a revision error because gentoo had a > > slightly different version (3.3.2) instead of 3.3.3 using pip. When I > > upgrade mailman, am I going to have to do something to the database as > > well and why should the database have some kind of reference to the > > mailman version? > > > I don't know why this is an issue. You shouldn't need to do anything > with the database when you upgrade. Please post the full traceback and > error message. Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 7 months

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > > On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >> I've come across mailman-cli docs: > >> > >> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >> This is basically one of our GSoC projects which hasn't yet been merged with MailmanClient. It uses the REST API to to provide a command line client for Mailman, while there hasn't been any in-compatible changes in API since this project was finished, I am not sure about the current status of it. > >> yet I cannot figure out what's the official source for the installation. Official source for MailmanClient is at gitlab.com/mailman/mailmanclient and it doesn't have a CLI, the Github project you linked to says right on the top that it is not official project (Thanks for that Rajeev!). Also, I would say not to use this client to remotely access Mailman, the REST API is not meant to be exposed over internet (unless you have a VPN or other sort of setup to securely access the box remotely). -- Abhilash Raj maxking(a)asynchronous.in

8 years

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 20:21 : > On 6/15/20 9:43 AM, Gilles Filippini wrote: >> Hi, >> >> I'm seeing the above error in mailman-core logs each time an email is >> processed. Is there something I missed in the configuration? I'm using >> dockerized mailman 0.3 from maxking. > > > I'm guessing you have one message in var/archives/hyperkitty/spool/ that > is causing this issue. The message itself will probably have invalid > utf-8 encodings in a message part declared as charset=utf-8. > > Every time a new message is archived, HyperKitty reprocesses this > message and hits the error again. > > You can examine the message with `bin/mailman qfile`. It is a Python > pickle of a message object. There are 4 emails stored into this folder. 3 of them are spam, and the last one is a legitimate email. This is annoying that such emails could accumulate and stay into var/archives/hyperkitty/spool/ forever, causing more and more hyperkitty errors. Any idea how to make their processing more error proof? Thanks, _g.

5 years, 4 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Steve Brown

Mark Sapiro wrote: > The senders are defined as addresses in the headers listed in > the configuration setting sender_headers, default = from, from_ > meaning envelope sender, reply-to and sender. See > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> This was very useful in explaining why MM3 (3.3.9) accepted the problem post and attributed it to my address, even when seeing the bounce+ address as a different sender. Thank you for taking the time to reply. > Are you saying that the bounce+... address ends up as a nonmember of > the list you are sending to. I don't think that should happen. Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Steve

1 year

[MM3-users] Re: Deleting moderation requests in database

by Joachim Schrod

Mark Sapiro writes: > On 12/2/24 6:40 PM, Joachim Schrod wrote: > > > > First: I assume that all information about moderation is in the > > database mailman3. If that's not the case, please tell me. > > > It is the case, but it's easier to use mailman shell. Something like > ``` > $ mailman shell -l test.example.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 test.example.com mailing list > >>> pendingsdb = getUtility(IPendings) > >>> for token, data in pendingsdb.find(m): > ... if data.get('token_owner') == 'moderator': > ... if data['type'] == 'unsubscription': > ... pendingsdb.confirm(token, expunge=True) > ... > >>> commit() > ``` Thanks a lot, worked like a charm! Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

10 months, 1 week

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 1:04 PM, Mark Sapiro wrote: > On 10/23/20 9:37 AM, Brian Carpenter wrote: >> How would a person already be a core user outside of a registration with >> Affinity? Via a list subscription or the import21 script? > > Yes, or even just by sending a post to a list as a nonmember. > > Everyone who is or has been a member, non-member, owner or moderator of > a list has a user and one or more address records in Mailman core. And those records are kept in the database? Is that correct? >> I do want to apologize for my tone Mark. I was wrong in the way I communicated. > > Apology accepted. I understand that it can be frustrating to be > dependent on something you don't control and that this can sometimes > lead to "anomalous" behavior. > > Here's a take on this that is intended to be humorous, but is actually > quite frightening. https://xkcd.com/2347/ I actually came across that cartoon months ago and that one person reminded me of you. So the fact that you are sharing that cartoon is ironic and very funny! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Extracting mailing list users

by Eggert Ehmke

Am Montag, 2. Januar 2023, 02:40:58 CET schrieb Mark Sapiro: > Understood, but there are a couple of things at work here. One is that > this particular task is a one-off the correct the result of a bug, but > perhaps more significantly, mailman developers (at least me) are > comfortable with `withlist` (it's been around since MM 2.1) and if I can > do it that way, it reduces the motivation to make something more > friendly for the normal admin. Unfortunately doing things easily that > way requires a lot of specialized knowledge of Mailman internals, so > most admins need help with it. Mark, I completely understand your situation as a core developer with limited time and lots of requests from all directions. Being a Python programmer myself, I would be happy with a consistent documentation of the relevant Python classes to be able to develop own applications. The isolated code snippets in the mm3 documentation are not too helpful. Such a documentation would possibly remove some of the workload you feel by constantly answering admin questions.´ When you look at the documentation of the Qt library you know what I mean. Thank you again for this great project! Cheers, Eggert

2 years, 9 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 1:14 PM, Mark Sapiro wrote: > On 10/21/20 8:53 AM, Brian Carpenter wrote: >> If you set the unsubscription policy to confirm then moderate for a list >> and someone unsubscribes, they receive a confirmation request. That is >> good. They respond to it. That is also working fine. However the list >> owner/moderator than gets a request to approve the unsubscribe request >> and well, unless I am missing something, I don't see an interface to >> handles such requests via Postorius. > > This is <https://gitlab.com/mailman/postorius/-/issues/332>. > > >> How does one handle an unsubscribe request that requires moderator >> approval? > > I'm not sure at this point, I can look further later, but if the notice > to the admin has a token, it might work to send a `confirm <token>` > command to the list-request address. > > Otherwise, don't moderate unsubscription requests. Well I can't dictate that to my list owners and there is no confirm token sent with the moderation notice. Why include this option in Postorius when it can't be properly handled? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 3:47 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mark Sapiro writes: > > > 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, > > That's true from "outside", but there are internal links as well. For > example, in Postorius top page, the link to HyperKitty is .../archives. > I guess it's a good idea to grep the templates to see which URLS are > used. > > > > Now my question is about what could be adding the /mailman3. Is it > possible > > > that I installed something out of the ordinary? > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > only thing I can think of is an Apache rewrite rule. It's not in the > Postorius and HyperKitty templates. > And I do not have any rewrite rules in my VHOST config: https://pastebin.ubuntu.com/p/9MRMJST9zZ/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Remove ALL Members button - was: Re: Setting base_url for the domain to use it in the templates.

by Odhiambo Washington

On Thu, Jul 11, 2024 at 6:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/10/24 10:46 PM, Odhiambo Washington via Mailman-users wrote: > > > > I find the unsubscribe_all button quite scary! I have never used it > though, > > so I am not quite sure about its behavior. What scares me > > is the possibility of clicking it and then in one fell swoop you've > removed > > ALL the members without a "confirmation". > > See the thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > and the issue at https://gitlab.com/mailman/postorius/-/issues/545. > > Bottom line - there is a confirmation. Try it, perhaps on a test list if > you're really scared. > Will do that test :) -- 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, 3 months

[MM3-users] Re: Installation Questions [Installation}

by Gerald Vogt

Hi, On 04.11.24 02:06, Mark Sapiro wrote: > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > We should probably cover this in the docs, but for /etc/mailman3, you > should do > ``` > sudo mkdir /etc/mailman3 > sudo chown mailman:mailman /etc/mailman3 > sudo chmod 755 /etc/mailman3 > ``` > Then you can create all the subordinate files as the mailman user. For > other things like the systemd service and the postfix and web server > configs, you need to do them as root (via sudo). is it really necessary that the mailman user can write that directory? For most services, directories and files in /etc/ may be readable for the service but usually not writable as you don't want the service itself change it's core configuration. On your server it looks like this: # ls -la /etc/mailman3 total 28 drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py and it works just fine. Regards, Gerald

11 months, 1 week

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

by Flo

On 10/10/25 03:59, Mark Sapiro wrote: >> >> Is there a possibility to export all members including real names. It >> doesn't work with Postorius, yet, is there another possibility? If I >> have my user data exported, I could delete everything and start from >> scratch. Maybe this is the most reasonable ... > > You can install mailman following https://docs.mailman3.org/en/latest/ > install/virtualenv.html and keep your existing database(s) which will > include all lists and memberships. > I think I am still using a sqlite database. This is the database when I installed the packages. There is a hint that it should be replaced by mysql or postgres. I only have very few lists, yet. The only thing I really don't want to loose is the addresses and names. > The current released versions of Postorius include only emails in the > csv export. This is fixed for the next release by https://gitlab.com/ > mailman/postorius/-/merge_requests/993 > > You can currently get a list of members with display names with the > `mailman members` command. See `mailman members --help`. > This is working! That's great. Thank you! Flo

5 days, 17 hours

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

I have run "python manage.py rebuild_index" before, doesn't that do clear_index as well? Apart from that, I run hyperkitty in a docker container and didn't know fulltext_index should be persistent, so that got deleted after every version update for sure. On 4/26/19 10:18 PM, Mark Sapiro wrote: > On 4/26/19 11:14 AM, Alain Kohli wrote: >> I see loads of "A string literal cannot contain NUL (0x00) characters." >> messages, but I haven't found missing messages in the archives yet. Not >> sure how that could be related, though. Apart from that I don't see >> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to >> run and finish normally. > > Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 > version? The Haystack/Whoosh search engine databases are not compatible > between the two and "A string literal cannot contain NUL (0x00) > characters." is the symptom. > > You need to run 'python manage.py clear_index' or just remove all the > files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in > your settings file (normally 'fulltext_index' in the same directory that > contains your settings.py. >

6 years, 5 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

On 6/1/22 19:19, Mark Sapiro wrote: > On 1/6/22 4:25 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> In the last part of your suggestions you wrote: >> >> "I suggest you do >> >> pip install --upgrade hyperkitty mailman-hyperkitty >> >> and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" >> >> But this is exactly what made me fall in this mess: > > > Sorry, I was confused. I thought the error message you were seeing was > changed before HyperKitty 1.3.5 was released, but that isn't correct. > > The problem is probably in Apache. See the last 2 posts in the thread > at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > I'll try tomorrow, now I'm a bit slow-head after a hard day (and the collateral effects of the third vaccine). It looks the right way (I have apache running in that server) to solve it. What intrigues me is the fact that I didn't change anything in the apache config or update apache itself. Well, tomorrow will be antoher day. Thanks for the point.

3 years, 9 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Seth Seeger

> On Jan 2, 2022, at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks for sending me the shunted .pck. It turns out I didn't need it. Had I looked more closely at the Traceback, I would have realized that the issue is that the list's list:admin:action:post template contains non-ascii. In particular, the character in position 5 is ’ which is a unicode right_single_quote, not an ascii apostrophe. > > There may be other unicode fancy quotes ad well. > > You can fix the template to contain only ascii or you can set the character set for English to utf-8 by adding > ``` > [language.en] > charset: utf-8 > ``` > to mailman.cfg. The downside of the latter is that outgoing message bodies will always be base64 encoded which generally precludes grepping mailboxes to find things. Ah hah! Right you are. I removed the offending fancy apostrophe. What about that traceback pointed to the template? (Is it something I could have figured out?) Is it possible to filter out UTF-8 chars from the templates when they are saved in Postorius? Thanks again, Seth

3 years, 9 months

[MM3-users] Re: Python backtrace from `mailman -h`

by Peter Chubb

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 8/24/25 17:03, Peter Chubb via Mailman-users wrote: >> Hi Folks, I'm running the Debian-packaged mailman3 (yes I know ...) >> and running: sudo -u list mailman -h gives a python backtrace >> (which I've appended the tail end of). Can someone who has the >> upstream installed version (using venv) please check that `mailman >> -h` works there before I waste too much time investigating in the >> wrong places? Mark> Yes, `mailman -h` works and produces the same help output and Mark> list of subcommands as `mailman` with no arguments or Mark> options. Does it work with no options? Does it work if you do Mark> `mailman -C path/to/mailman.cfg -h`? Thanks. Without options it works; and it works with an explicit config path. So I know where to look to fix it (and will report it on the Debian bug tracker) Interestingly: sudo -u list mailman -C /etc/mailman3/mailman.cfg -h works, but sudo -u list env MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg mailman -h does not. And sudo -u list mailman info reports /etc/mailman3/mailman.cfg as the current configuration file. Peter C

1 month, 2 weeks

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Tue, Jan 8, 2019, 20:34 Abhilash Raj <maxking(a)asynchronous.in wrote: > On Tue, Jan 8, 2019, at 5:52 AM, Odhiambo Washington wrote: > > On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> > > > >> Please help me understand what steps are missing and I will try to > > > >> provide the information. > > > > > > > > > > > > Okay. > > > > > > > > At the installation stage, you say the following: > > > > "I already had some things set up in /opt/mailman including a git > > > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > > > postorius projects. On the third server I have added mailman-suite > > > > because I use the settings.py from that project as the basis for > mine." > > > > > > > > Please assume that the reader is a newbie to python3 virtualenv and > give > > > the > > > > details of the commands they need to execute to (a) clone all the > > > projects > > > > needed > > > > and (b) create the virtualenv. > > > > > > > > The next steps are: > > > > mkdir /opt/mailman/mm > > > > > > > > Then you say "I then created a /opt/mailman/mm directory and within > that > > > a > > > > Python 3.6 virtualenv" > > > > What happens here is something that needs clarification, because you > are > > > > specific about "python3.6". > > > > I have googled and realized that one has to be specific about the > python > > > > version they want to use in their virtualenv > > > > as shown here -> > > > > > > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > > > > > exact command to execute to create the /opt/mailman/mm/venv > > > > exact command to execute to activate virtualenv > > > > > > > > > I have added a comment to the page which I hope gives you what you > want. > > > > > > I also added a section on templates instead of referring to a prior > > > version of the page. > > > > > > > That makes it better. > > However, as a newbie, something is not yet clear: > > > > "When active in a particular shell, it can be deactivated with the > command > > > > deactivate > > or by exiting that shell." > > > > HI am trying to understand the effect of detaching from a venv. I am > > assuming that a virtualenv is a container that is supposed to be always > > active for the services within to be accessible. Is that right? So, how > do > > I ensure it's always running/up, or that does not matter as the scripts > > which run the services will always refer to the files? > > virtualenv is not actually a container that is supposed to be active. It > is merely a set of settings that are applied to your SHELL when you are > in the virtual environment. > > It is not supposed to be always active, only when you actually want to > run commands in that virtual environment. The services will keep on > running after you deactivate your shell and would function like other > normal services on your machine. > > -- > thanks, > Abhilash Raj (maxking) > Thank you for clarifying. So once I have a venv created, the services will just run as long as the startup scripts are running even when I'm logged out of the system? >

6 years, 9 months

[MM3-users] Re: Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

On 7/8/21 20:03, Mark Sapiro wrote: > This is the way MM 3 works. The only reason *_these_nonmembers exists > in MM 3 is to support the legacy regexps from MM 2.1. For non-regexp > addresses the address is a nonmember with the appropriate moderation > action. > > I actually find this convenient. When a nonmember posts spam to a list > and that spam is held, I discard the spam in Postorius and at the same > time set the nonmember's moderation action to discard so I never see > any more from that address. Also, when someone who I recognize as a > list member posts from an alternate nonmember address, I can accept > that post and set the nonmember address moderation action to default > processing. > I find it very convenient too, but it concerns me that spammers, really "profesional" spammers and senders of phising mail change the forged address and sender domain too rapidly to track them. As of it, the non-member database is growing more and more. It could be a "monster" in two or three years... Not a problem now. And I know now how to delete them in one go :) --

4 years, 2 months

[MM3-users] Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Stephen J. Turnbull

Mark Sapiro writes: > But postorius and hyperkitty are dependencies of mailmanweb so only Are they? I'm pretty sure that in my current project which has a pre-existing archiver they wish to keep using I only installed postorius, not hyperkitty. ... oops, HyperKitty *is* there. OK, need to uninstall that. That's actually a bit annoying, since mailmanweb is a friendlier interface for control of either of HyperKitty and Postorius than the underlying Django utilities even if you don't want the other and its unique dependencies (such as Whoosh). (Issue #32 created) OK, so your two-venv approach should actually work. I still don't think it's much of a win since to finish setup you still have to do a lot of work as root and a lot of work outside of pipx's control. Basically it saves one "python3 -m venv", at the cost of "pipx run" to run each program in its own venv. Note, it doesn't save me any venv activationss because I put that in the mailman user's shell .rc. Wikinaut asks: > Has anyone tried that already? Why not you? Steve

1 year, 8 months

[MM3-users] Re: Hiding an ML from a site

by Odhiambo Washington

On Wed, Feb 7, 2024 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On February 6, 2024 7:45:14 AM PST, Odhiambo Washington > <odhiambo(a)gmail.com> wrote: > > > >I had this set to True in settings_local.py, but False in settings.py. > >So it seems to not make a difference in my setup. > > In a standard setup, anything set in settings_local.py overrides any > corresponding setting in settings.py. > > That said, FILTER_VHOSTS is not perfect. It only works for Postorius if > the separate web hosts also have different mail hosts. See lines 1051 et > seq at > < > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… > > > What should I do then? Edit some file? Apply some patch? It's pretty easy for me to create a DNS record for the same server (IP) for use with the web host that I'd like to hide. -- 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, 8 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Torge Riedel

Am 16.01.20 um 21:43 schrieb Mark Sapiro: > On 1/16/20 10:51 AM, Torge Riedel wrote: >> Such SPAM mails are currently hold for moderation with reason "not from >> a list member". Is there no check for the "X-Spam: Yes" header or is >> this check done later? > > If you set a Header Filter (in Postorius the Header filters tab) those > checks are done before non-member moderation. > > This won't work for posts from members because the header checks are > done between member moderation checks and non-member moderation checks, > but if you create a Header Filter for header 'x-spam' and pattern 'yes' > with action hold, a message from a non-member which has an X-Spam: Yes > header should be held for that reason. > > Hi Mark, thank you for your answer. Just to understand that right: In case a posting with an "X-Spam: Yes" header comes from a member, it will not be held? It will be directly forwarded to the list? If yes, is there any chance to change or extend this? Best regards Torge

5 years, 8 months

[MM3-users] Re: postfix malformed address with confirm replies

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/27/21 4:36 AM, Stephen J. Turnbull wrote: > > is legal, and I think that most servers will accept it, but RFC > > 5321 sets a limit of 64 octets on mailboxes[1], and your > > confirmation mailbox is 67 octets. > > Since the -confirm+<token> part is fixed at 49 octets, this would imply > a limit in list names of 15 octets. Ouch! I'm pretty sure we would have run into this before, if there were a lot of servers out there imposing this limit. 15 octets is pretty darn short, there are probably quite a few list names out there longer than that. Not to mention that the RFC itself says "you SHOULD NOT be a jerk about this". :-) So I don't think this is a big problem in practice, and I hope Steve can reconfigure the obstructive server to not be so picky. For Mailman, I doubt we need a full SHA1 (?) for the purpose. We can truncate the thing, probably opportunistically (ie, so the whole confirmation mailbox fits in 64 octets, or we could even parse the bounce message and resend only if we run into a problem). Steve

4 years, 7 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Fri, Aug 2, 2024 at 6:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/2/24 08:12, Roland Giesler via Mailman-users wrote: > > > > It seems though that since I'm not running a local MTA, when then mail > > arrives at the mailman3 server, there's nothing that can process it. So > > should I run postfix in it's most basic setup to allow mail to be > > received or what is the best way to deal with it? Mailman3 has to > > receive mail like signup confirmations, etc after all, not? > > If you use transport_maps on the remote MTA to relay the list mail to > port 8024 on the Mailman server, Mailman's LMTP runner will receive the > mail and you don't need a local MTA. > Nice one! I'd love to know how this config is done in Postfix. Heading to ask Uncle G. -- 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, 2 months

[MM3-users] Re: Auth question

by Simon Hanna

On March 31, 2017 6:34:18 PM GMT+02:00, Mark Sapiro <mark(a)msapiro.net> wrote: >On 03/31/2017 01:06 AM, David Krantz wrote: >> On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna ><simon.hanna(a)serve-me.info> wrote: >>> On 03/31/2017 08:10 AM, David Krantz wrote: >>>> I think that would correspond to this line in urls.py >>>> >>>> url(r'^$', >RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), >>> Yes, that's the culprit. Replace it with the following: >>> >>> url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), >>> You can also update whatever guide you were using... >> >> Great, will try that! I don't know whether I can update the guide. >> It's the one referenced earlier in this thread named something like >> setup experience of mailman 3 in production. > > >Yes, that comes from >"https://wiki.list.org/DOC/Mailman%203%20installation%20experience", >specifically the attachment urls.py. > >The interesting thing is that works for me both at ><https://lists.mailman3.org/> and <https://mail.python.org/mm3/>. Are you using the latest version of django? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 6 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 20:44, Mark Sapiro escribió: > ... > lmtp runner did not start because at some point it had died and > restarting Mailman won't restart a runner that died and was marked to > not restart. > > You need to stop Mailman and make sure when mailman is stopped that > there are no files in mailman's var/locks/ directory (remove any that > are there) and then start Mailman and lmtp runner should start. > I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail. Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content: master.lck|www.proteccion-civil.eu|9389|7022761192045613065 will try deleting the content of var/locks and restarting the server > As to why it died in the first place, there should be something in > mailman.log from the time it died. > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 6 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-23 11:33, Mark Sapiro wrote: > On 4/22/24 17:06, Mark wrote: >> >> There was no line POSTORIUS_TEMPLATE_BASE_URL in >> /etc/mailman3/settings.py > So presumably you were getting the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > > from mailman-web/settings/mailman.py because of > from mailman_web.settings.mailman import * > in your settings.py. Yes. # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * ... > >> Then, as site-owner, creating a new custom Welcome template (again via >> the WebUI) I can see it correctly added to the database in >> mailman.template.uri >> >> - >> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… That URI should have been; https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… If I go to the above URL, the text of the list's Custom welcome message displays on an otherwise empty webpage. > > > And what happens if you go to that URL in a web browser? Also what do > you get when going to https://lists.mydomain.com/mailman3? I get the Postorius page "Mailing Lists" that displays the table of lists.

1 year, 5 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 00:16, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > > > Thank you for clarifying. > > So once I have a venv created, the services will just run as long as the > > startup scripts are running even when I'm logged out of the system? > > > As long as the startup scripts actually reference things in the venv. > > If you look at the samples in the Recommended Configuration section at > <https://wiki.list.org/x/17891998> for > > /opt/mailman/mm/bin/django-admin (sample) Script to run Django > management commands. > > /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. > > and > > /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. > > You will see they all do things like activate the venv or run a command > from venv/bin. > > > Now that has clarified the matter for me. That even when I am logged out, the scripts do the neccessary to activate the venv to run things. I hadn't looked at the scripts at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 9 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 4:09 PM, Mark Sapiro wrote: > Do you have > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > in the [mta] section of mailman.cfg? (these are the defaults) > > $ /opt/mailman/mm/bin/mailman conf|grep lmtp > [mta] lmtp_host: 127.0.0.1 > [mta] lmtp_port: 8024 I do > Is Mailman's lmtp runner listening on port 8024? > > $ sudo netstat -lntp|grep python > tcp 0 0 127.0.0.1:8024 0.0.0.0:* > LISTEN 1867/python > tcp 0 0 127.0.0.1:8000 0.0.0.0:* > LISTEN 1199/python > tcp 0 0 127.0.0.1:8001 0.0.0.0:* > LISTEN 1871/python It is. > > Is there some firewall issue blocking access to the port even from > localhost? Let me describe the problem a little better. Mail delivery from postfix to mailman works most of the time. However in the past week or so, lmtp starts refusing connections via postfix about once a day. I have port 8024 open in the firewall (UFW). There are no errors in the smtp.log file. I think restarting Mailman core seems to get things running again. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 3 months

[MM3-users] Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

3 months, 4 weeks

[MM3-users] Re: Hyperkitty messages stuck in spool

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/18/21 6:38 AM, Andrew Hodgson wrote: > > > > Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? > > I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. In theory there could be a memory leak in Python or one of the Mailman apps, but I haven't heard of it. And at least the Linux kernel seems to be perfectly happy to kill random processes that are well-behaved. So the fact gunicorn is getting killed is not strong evidence that it's causing the memory pressure, we'd really need to see the stats. Steve

3 years, 10 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by John Hein

Mark Sapiro wrote at 19:18 -0700 on May 12, 2016: > On 5/12/16 3:46 PM, John wrote: > > But mm 2 had: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > multipart/digest <--- this is the part that's gone in mm3 > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > > So was that removal intentional, a bug or ?? > > > I'm sorry. I missed the point of your OP. I think it's a bug. > > The doctest at > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, > the part just after "The MIME digest has lots of good stuff, all > contained in the multipart." is clearly missing the multipart/digest part. > > It appears that this got lost in the refactoring of the MM2 code for > MM3. Please file an issue at > <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me > (msapiro), but it any case, I'll work on fixing it. https://gitlab.com/mailman/mailman/issues/234 Thanks.

9 years, 5 months

[MM3-users] Docker, Mailman 3, templates and list user accounts

by Henrik Rasmussen

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

8 years, 2 months

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Tue, Jan 30 2018, Mark Sapiro wrote: > The underlying issue is the orange.fr domain is sending DSNs without a > Message-ID: header. Yes. Is a Message-ID header required in a DSN by any RFC? > If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] > section of your config), this log message I have verp_delivery_interval = 10 ... > would contain to=<test-bounces+user=example.com(a)my-domain.org> and you > could identify the bouncing address (user(a)example.com in this case) that > way. Yes, that's my intention, but first of all, mailman must receive the DSN. > Beyond that, there are still other issues, the biggest of which is > currently, Mailman is not processing bounces other than storing them in > the database. See <https://gitlab.com/mailman/mailman/issues/343>. Shouldn't the DSNs be forwarded to the owner of the list? > if a recipient MTA can't create a DSN that has a Message-ID:, would > you trust what else it does? I don't know. The question for me is: does the remote MTA needs a fix (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN without Message-ID should be acceptable)? -- Peter

7 years, 8 months

[MM3-users] Re: Log rotation

by Abhilash Raj

On Tue, Apr 10, 2018, at 4:12 PM, Mark Sapiro wrote: > On 04/10/2018 03:04 PM, Darren Smith wrote: > > > > 1) Has anyone come up with a good log rotation strategy that doesn't > > necessitate a restart of the service? > > I think Abhilash has answered this, but for completeness, here's what I > use on lists.mailman3.org which uses nginx and gunicorn > > Mailman's logs > > /opt/mailman/mailman-bundler/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mailman-bundler/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mailman-bundler/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > > mailman-web log > > /var/log/mailman-web/*.log { > missingok > notifempty > delaycompress > su mailman mailman > } > > > And here's mail.python.org with apache and mod_wsgi > > Mailman's logs > > /opt/mailman/mailman-bundler/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true Oh, I didn't know about the "mailman reopen" command, thanks Mark! -- Abhilash Raj maxking(a)asynchronous.in

7 years, 6 months

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

by Elias Rudberg

Hello again, Mark Sapiro wrote: > I'm not certain, but I think it's a Django issue > rather than a Mailman issue. I got a reply about this in the Django forum at https://forum.djangoproject.com/t/getting-error-need-2-values-to-unpack-in-… Quoting from that forum post: "This is not a bug in Django. This would be functioning in the manner that Django is designed and documented at [link]" "The error here is trying to use a reference in a template without having the view ensure that the context being passed is correct." "Both the template and the view should be corrected here. The view should ensure the right data is put into the context, probably under a different name, and the template should render that data from that name." (end of quote from Django forum) So they think it is not a bug in Django. Does it make sense, that "the template and the view should be corrected" as suggested there? (The template in question would be pagination.html but I'm not sure exactly how it should be corrected.) / Elias

1 year, 2 months

[MM3-users] Re: How to remove global ban using API?

by Nathan Dixon

For those who are interested. To be able to use global_bans = IBanManager(None) and not get the following error: Traceback (most recent call last): File "<stdin>", line 1, in <module>TypeError: ('Could not adapt', None, <InterfaceClass mailman.interfaces.bans.IBanManager>) You need to use: mailman shell Not a standard python3 session. To actually update the global bans not via the API, which has some limitations at the moment (see the issue on Gitlab), I have done the following workaround (later I will put in checks for an existing ban to do an update instead, or a delete then create of the new ban): 1) I create a python script within the docker container within the existing PYTHONPATH that will be the module that runs when I want to create or update my ban (in this case under /usr/bin/) #!/bin/env python def create_valid_domains_ban(valid_domains_regex): from mailman.interfaces.bans import IBanManager global_bans = IBanManager(None) global_bans.ban(valid_domains_regex) print(list(global_bans.bans)[0].email) 2) I can then invoke this as a mailman module from the server using docker exec mailman-core mailman shell -r create_valid_domains_ban $valid_domains_regex On Wed, 15 May 2019 at 21:21, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/19 9:46 AM, Nathan Dixon wrote: > > > > I can create the ban fine by the following: > > > > from mailmanclient import Client > > client = Client(URI,apiuser,apipass) > > > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") > > > This is apparently a typo - missing ')' - in the re as you have it > correct below. > > > > However, I cannot seem to be able to remove it using the api: > >>>> client.bans[0].delete() > ... > >>>> client.bans.remove(str(client.bans[0])) > ... > >>>> > > > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") > > > All of the above work for me with both API 3.0 and 3.1 in a non-docker > install of the current GitLab HEADs > > > > And also, when I now try and go into the mailman-core docker image to use > > the mailman.interfaces.bans, it will not let me see the global bans: > > > >>>> from mailman.interfaces.bans import IBanManager > >>>> global_bans = IBanManager(None) > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > TypeError: ('Could not adapt', None, <InterfaceClass > > mailman.interfaces.bans.IBanManager>) > > > I don't see this either. > > > > I have opened an issue in Gitlab for this as I feel it may be a bug > related > > to regex and global bans (there was a similar one for list banned > > addresses): https://gitlab.com/mailman/mailman/issues/598 > > > I also commented on the GitLab issue. I think this must be an issue with > the docker images. > > -- > 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/ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 4 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 15:45, Mark Sapiro <mark(a)msapiro.net> wrote: > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Right. There will eventually be additional recurring tasks for Core too though, such as processing the bounce database for disables and unsubs, pulling messages from NNTP, and possibly others as time goes on. I’ve always thought about handling these as commands that cron would run, much as in Mailman 2, but it would also be possible to implement a runner, or runners, to do those jobs. I can see advantages and disadvantages with either approach. > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Yep, thanks for the bug report. `mailman digests —periodic` seems like the right approach. Cheers, -Barry

8 years, 2 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:40 PM, Mark Sapiro wrote: > On 11/11/20 4:18 PM, Brian Carpenter wrote: >> Some sort of auto-discard procedure after a number of retries? Is it >> possible to detect a message with a null characters and automatically >> discard them? Do such messages make it into the thread table? > > The message has been delivered to the list, but it is not archived. The > list post has an Archived-At: header with a URL, but the message isn't > there at all. The only way to get it archived is to correct the message > defect. Does the problematic message (null character) make it to the hyperkitty_thread table? > Thus, I don't think it's good to just discard the message at that point. > I'm fine with moving out of or not queueing it in the first place in > var/archives/hyperkitty/spool, but I think it should be preserved > somewhere, say in var/archives/hyperkitty/bad, and along with that, some > kind of notice sent to the site admin so bad messages don't just > accumulate without being seen. > Can a message with a null character be repaired with an automatic process? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/5/22 02:37, Odhiambo Washington wrote: > > > > Here again, Google-fu came to the rescue. I added the following line to > > settings_local.py and the warnings were suppressed. > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > I need to understand how this affects everything and how this is likely > to > > impact the functionality of MM3. What is the proper solution for this? > > And should it be django.db.models.BigAutoField or > > django.db.models.AutoField? Which is which? > > > Prior to Django 3.2 Django set default primary keys to 32 bit integers. > In 3.2 Django introduced the possibility to set default primary keys to > 64 bit integers by setting the type to django.db.models.BigAutoField. > > Thus, putting > ``` > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > ``` > in your settings will maintain compatibility with pre 3.2 versions and > existing tables and this is the correct thing to do. > Thank you very much for the clarification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Hyperkitty fulltext search performances

by Mark Dadgar

On Oct 4, 2020, at 8:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/4/20 8:07 AM, Brian Carpenter wrote: >> >> On 10/4/20 8:59 AM, Loïc Dachary wrote: >>> After a little digging it turns out the mailman3-web Debian GNU/Linux >>> package I'm using is configured to use Woosh as a haystack backend. >>> And it is not fit for volumes greater than a few hundred mega bytes. I >>> should switch to something else from the list of supported >>> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >>> >> For our servers running Postorius/Hyperkitty, we use Xapian. I believe >> the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For >> our Affinity/Empathy servers, we use Elasticsearch which we are very >> happy with. Elasticsearch does have a higher memory requirement I >> believe than Xapian. > > > Brian is correct about this list. We started with Whoosh, then went to > Elasticsearch and ultimately to Xapian. Each step gave better > performance and a smaller footprint than the one before. +1 I have ~700K posts in my archive and Xapian is FAST. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Philip Colmer

On Tue, 4 Jan 2022 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/4/22 6:45 AM, Philip Colmer wrote: > > > > So ... should the archive be deleted when the list is deleted and it is a > > bug that it isn't? Or is it expected that access to the archive is > "frozen" > > once a list is deleted? > > > It is often desired to have a public archive available after the > corresponding list has been deleted. Even for a private archive, it may > be desirable for site admins to have access. Furthermore, a list might > not even have a HyperKitty archive in the first place. Thus, what to do > about a HyperKitty archive (or prototype archive or ...) when a list is > deleted is an administrative decision and is best left up to the site > admins to do it or not. > > As you note with a private archive, former members no longer have access > when the list is gone, but unless an attempt throws some uncaught > exception, that is not a bug. > Thanks, Mark, for the clarification. Regards Philip

3 years, 9 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 14:49, Jered Floyd wrote: > > The difference in behavior was using social login buttons for an existing account vs. creating a new account. > > This is another damn django-allauth regression, starting in 0.57.0. It seem to be this commit that is to blame: > https://github.com/pennersr/django-allauth/commit/be779dfee5a328a3a42edc2c9… > > In allauth/socialaccount/models.py:lookup(self):285 there is an attempt to look up the social account as one that already exists. If that fails, this commit calls self.account.get_provider() without passing the request object, which leads to the eventual error. > > I believe this is a django-allauth bug, and have submitted a pull request to fix it here: > https://github.com/pennersr/django-allauth/pull/3548 Thanks for all your work on this. It is much appreciated. However, your patch doesn't fix my issue with the URL https://example.com/accounts/social/connections/ which still produces the following: ``` ERROR 2023-12-07 00:05:55,032 169452 django.request Internal Server Error: /accounts/social/connections/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 220, in _get_response response = response.render() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", line 114, in render self.content = self.rendered_content File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", line 92, in rendered_content return template.render(context, self._request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 238, in render nodelist.append(node.render_annotated(context)) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 539, in render values = {key: val.resolve(context) for key, val in self.extra_context.items()} File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 539, in <dictcomp> values = {key: val.resolve(context) for key, val in self.extra_context.items()} File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 715, in resolve obj = self.var.resolve(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 847, in resolve value = self._resolve_lookup(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 914, in _resolve_lookup current = current() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 147, in get_provider_account return self.get_provider().wrap_account(self) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 141, in get_provider provider = self._provider = adapter.get_provider( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_provider app = self.get_app(request, provider=provider) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 284, in get_app apps = self.list_apps(request, provider=provider, client_id=client_id) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 231, in list_apps db_apps = SocialApp.objects.on_site(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 27, in on_site site = get_current_site(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/models.py", line 63, in get_current raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: API timeout for one list

by Seth Seeger

> On Sep 22, 2020, at 4:30 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 9/22/20 12:45 PM, Seth Seeger wrote: >> I apologize, because I think this was talked about before, but I could not find it in the archives. >> >> For one list, the REST API times out. Doesn’t seem to matter which page I try to go to. The uwsgi-error.log entry: >> > ... >> The other lists work fine. > > This can happen on lists with lots of members. > > Try increasing the timeout. See <https://wiki.list.org/x/17892072> Thank you - that did solve my timeout problem. However, each page for this list takes between 40 and 80 seconds to load. The list has 465 members, and it’s running (via Docker) on a 2 core, 4 GB RAM Linode VM. I’ve watch htop during the load - one CPU is around 20%, and the other hovers around 80%, mostly with the process “runner”. Is there a way to optimize this list? There are no held messages, no subscription requests, no templates. The next biggest list has 438 members, and all those pages load very quickly (0-2 seconds). I can’t figure out what the difference between the two lists. Thanks, Seth

5 years

[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Ruth Ivimey-Cook

See after: On 26/11/2022 18:18, Mark Sapiro wrote: > I found this article stating the the SMTP error message >> might be misleading: >> https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… >> >> >> How to further debug this? >> What could be wrong with my Mailman3 instance and how to fix it? > > The article is relevant and mentions the most likely issue which is > lack of permission on one or more message templates. > > Everything in Mailman's var/ directory should be owned by Mailman's > user:group - normally `list:list` in Debian packages. While this is always true for mailman-core, in some configurations the mailman-web files are also inside the ./var/ tree, and they need to be readable (and, for some, writable) by the process acting as webserver, which may or may not be list:list. In my case (a bit off-piste) I have set mailman-web it up to run as owner=www-data, for example (I forget quite why this was needed now!!). Regards Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

2 years, 10 months

[MM3-users] Re: Where are the subject templates hidden?

by Simon Hanna

On 11/29/2017 09:25 AM, Thor Atle Rustad wrote: > 2017-11-29 7:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > >> On 11/28/2017 02:56 AM, Thor Atle Rustad wrote: >>> Using Docker. Suppose I've overcome >>> https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use >>> the templates/site/no directory for my customized templates. Yes, it >> seems >>> to be working, no hickups when national characters are used in the >>> templates. >>> >>> but... >>> >>> the welcome message still says "Welcome to the "listname" mailing list" >> in >>> English. Is it possible to change that? >> >> Have you put the desired template in >> templates/site/no/list:user:notice:welcome.txt ? >> >> -- >> > Yes, I put it there, and the text in that file is what is shown in the > welcome mail. However, the subject does not change (still English) > Thor > The subjects are currently not part of the templates. The translation of these is done in the Python code, so you would need to export a list of strings Mailman Core uses and translate these...

7 years, 10 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Hi Mark, Mark Sapiro <mark(a)msapiro.net> 於 2019年10月24日週四上午8:42寫道： > > Actually, there is no 1.2.5. The next release after 1.2.4 is 1.3.0, but > you can still set preferred_language for the list using the REST API or > mailman shell. > > For example in mailman shell > > $ mailman shell -l zh-l10n.lists.linux.org.tw > Welcome to the GNU Mailman shell > The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list > >>> m.preferred_language > <Language [en] English (USA)> > >>> m.preferred_language = 'zh_TW' > >>> m.preferred_language > <Language [zh_TW] Chinese (Taiwan)> > >>> commit() > Thanks for your help. I did what you said above, but then I still got the same result even after restarting mailman3 services. ~# mailman shell -l zh-l10n.lists.linux.org.tw Welcome to the GNU Mailman shell The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>> m.preferred_language <Language [zh_TW] Chinese (Taiwan)> >>> quit() I created a new list with Chinese display name, set the preferred_language and then subscribed to it. Also got question marks. Is there anything else to try? Thanks, Franklin

5 years, 11 months

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

Oh well. Am 01.09.2017 um 23:44 schrieb Mark Sapiro: > On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >> >> Seemingly, at some point in the deep dungeons of the source code the >> "Acceptable aliases" Text-Box is not interpreted correctly. >> >> Specifically, at the start it contains the string >> >> [] > > > See <https://gitlab.com/mailman/postorius/issues/58>. there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops. Kind thanks anyway. > > In order to set things on this page, you need to clear the Acceptable > aliases box before submitting changes. You can't actually set Acceptable > aliases via Postorius until this is fixed. The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh. Thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years, 1 month

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Odhiambo Washington

On Mon, Jan 30, 2023 at 12:39 PM Onyeibo Oku <onyeibo(a)schemefusion.com> wrote: > > On Tue, 3 Jan 2023 09:46:00 -0800 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > This is all configured in your web server. It needs to proxy requests > > for lists.website.tld to gunicorn and depending on the web server, > > may need more. E.g. see > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > > for nginx. > > I have fixed this. > > > > > > Set SITE_ID = 0 in your Django settings. Also see > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Actually "SITE_ID = 1" solved that instead. I also had to go into the > database and update the values (django provided 'example.com' by > default and that was problematic). > The common practice I have see is that one creates their domain on the web interface, which then displays the SITE_ID = N. You then take the value into settings.py to replace the one that's there. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: Exception with processing subscription confirmation email

by Eric Broens

Thanks Mark, We are indeed running mailman core 3.3.2 and using mysql. The data appears indeed to be truncated judging from the missing closing curly bracket (see below). Would it be OK to already extend the data column to VARCHAR(510) before upgrading to mailman core 3.3.3, or will this cause problems with upgrading to a newer version? +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | data | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | {"pre_approved": false, "pre_confirmed": false, "pre_verified": false, "invitation": false, "address_key": "******************@************", "subscriber_key": 1, "user_key": "a44e8b9a34c64775b712f383d438ce1d", "token_owner_key": 1, "send_welcome_message" | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ Best Regards, Eric -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: donderdag 29 april 2021 18:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Exception with processing subscription confirmation email On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfc c27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- 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/

4 years, 5 months

[MM3-users] Re: Mailman messages are getting a TAG in some email clients.....how????

by Guillermo Hernandez (Oldno7)

El 12/9/23 a las 19:43, Mark Sapiro escribió: > On 9/12/23 8:51 AM, bob B via Mailman-users wrote: >> So I know about the setting "Anonymous list" but regardless of that >> setting some email clients put the list name in [] when it displays >> messages in your inbox. Does anyone know how email clients are doing >> this? I have users who email clients do not do this, and was >> wondering if it is a setting in their client or just not possible. > > > This looks like Mailman adding 'Subject prefix', so all list mail will > have this prefix added to the Subject:. So the question isn't how mail > clients are adding it, but rather why do some mail clients suppress it. I think the simple answer is that some mobile mail clients don't show the subject line by default, you have to click to show it explicitely. That users just don't see that. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 1 month

[MM3-users] converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Lucio Chiappetti

I have been instructed by Mark Sapiro to subscribe to this list to post questions related to mailman3. On Mon, 31 Jan 2022, Mark Sapiro wrote: > On 1/31/22 06:20, Lucio Chiappetti wrote: >> One of the lists of which I am a co-moderator has been moved from >> mailman 2 to 3. Actually the migration has been made operative yesterday (and so we got the first problems ...). Basic background. There are a number of lists within my institution (a nationwide research institution with many seats across our country), some are institutional (all staff subscribed ex officio) and managed by staff in one seat, some other are non-institutional (subscription is optional) and are managed by a few volunteers in other cities different from the seat where the mailman server runs. > In particular, the list settings for *_these_nonmembers are at Settings > -> Message Acceptance, but these settings in particular are deprecated > in Mailman 3 except for regexps. In Mailman 3 the preferred way to say > accept a nonmember is to create a nonmember for that user and set it's > Moderation action to Default Processing. If, a nonmember posts, the > nonmember record is automatically created, Let me explain our case, and how it was managed in mailman2. - originally our staff (of the order of 1000) had addresses like user(a)place.inaf.it or user(a)place.astro.it. Some had even two (say place1.inaf.it and place2.inaf.it), so they subscribed with ONE of their work addresses - later we got addresses like name.surname(a)inaf.it. New users subscribe with this address but MANY of the old ones continue to use the PREVIOUS address. - we implemented a spam filtering policy as follows: - staff (and former staff) can SUBSCRIBE with any address or CHANGE their address. Any subscribed address will be recognised. Mail is NOT held in moderation unless too bulky, or has undisclosed recipients - mail from non members with any address in the .it TLD or in the tng.iac.es domain (where some of our staff work) goes into moderation (this is achieved via regexp in hold_these_nonmembers) - anything else is silently discarded as spam (generic_nonmember_action = discard) - when some staff posts from a non-subscribed address (be it the home address, or one of the alternate addresses described above) it therefore goes into moderation because of hold_these_nonmembers - in mailman2 we could let them pass "manually" (if we recognised the person) or (in case they used an alternate address) tick to add them permanently to accept_these_nonmembers (in one tick) - at the end we got somehow fed up of this but we did NOT want to accept any address of the form ^.+@.+\.inaf.it (which could be forged) but found that we could simply put in accept_these_nonmembers two entries like @list1 @list2 where list1 and list2 are two institutional lists on the same server which contain all permanent and temporary staff or assimilated with their official address (these lists are automagically generated each week) (so at least any VALID EXISTING official address is accepted) What I found now (after the migration done by the administrators of the central seat) is that in mailman3: - accept_these_nonmembers is empty - there are 189 entries listed in Non-members (which look those formerly in accept_these_nonmembers) - hold_these_nonmembers was copied identical with the same regexp's as in mailman2 - I have inspected a few of them and found that they have Administration options Moderation set to List default - the effect of this apparently was that a post from some.guy(a)inaf.it (whose subscription address is guy(a)somewhere.inaf.it) was hold for moderation is this due to a loop with the regexp in hold_these_nonmembers ? the default action would be to let it pass Or should we set Administration options Moderation to Accept immediately ? - if so, how can we do it automatically for all 189 entries ? - or move back the 189 addresses to accept_these_nonmembers ? - or for the future have persons posting with alternate addrresses accepted for the future WITH ONE CLICk ? - AND LAST BUT NOT LEAST would the syntax @list1 in accept_these_nonmembers work in mailman3 ? already putting it back will save a lot of work. Many thanks -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ "All that is google does not glitter Nor all who use alpine/procmail are lost"

3 years, 8 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Sebastian Hagedorn

--On 17. Juli 2018 um 22:04:12 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/17/2018 07:27 PM, Joe Steeve wrote: >> >> I have an installation on SQLite. I want to migrate it to PostgreSQL. Is >> that feasible? Any gotchas I need to watch for? > > > It is feasible. > > You would need to stop Mailman core and all Django processes including > cron jobs and WSGI processes to ensure nothing is accessing the SQLite > database, update the database section in mailman.cfg and the DATABASES > settings in your Django settings, use SQLite tools to dump the relevant > database(s) and PostgreSQL tools to create and load them, and finally > restart Mailman core and all Django processes. I have only now started playing around with Mailman 3.2, because I never managed to get the earlier releases to work, and reading through the documentation I thought that such situations could be handled with Alembic, as described here under "Database Migrations": <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> Is that not the case, and if not, in what cases can or should it be used? -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

7 years, 2 months

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 18:37, Mark Sapiro wrote: > On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to remove all non members from a list. I know I can do it via >> Postorius, but it has to be done one at a time. (you can delete ALL >> suscribers but not all non members...) >> >> Anyone has a python recipe to do this? > > $ /opt/mailman/mm/bin/mailman shell -l list.example.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 list.example.com mailing list > >>> for nonmember in m.members.nonmembers: > ... nonmember.unsubscribe() > ... > >>> commit() > Thanks a lot for the promt response, Mark. It's not functioning. It says: "AttributeError: 'MemberRoster' object has no attribute 'nonmembers'" My system info is: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius 1.3.4

4 years, 2 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Per Jessen

Mark Sapiro wrote: >> diff --git a/src/mailman/runners/lmtp.py >> b/src/mailman/runners/lmtp.py index 6a0bdcf5e..eca474089 100644 >> --- a/src/mailman/runners/lmtp.py >> +++ b/src/mailman/runners/lmtp.py >> @@ -217,6 +217,8 @@ class LMTPHandler: >> slog.debug('%s subaddress: %s, queue: %s', >> message_id, canonical_subaddress, >> queue) >> status.append('250 Ok') >> + if queue == 'bounces': >> + config.switchboards['bad'].enqueue(msg, >> msgdata) >> except Exception: >> slog.exception('Queue detection: %s', >> msg['message-id']) config.db.abort() > ``` > will add all received bounces as queue files to var/queue/bad/ where > they can be examined with `mailman qfile`. Thanks. Yep, I'm getting NDRs kept now. "mailman qfile" seems to be a bit slow, 2-3 seconds per go. To look for a specific address that bounced, is there any mailman tool for grepping through a collection of bounces? (I have +1200 after a few days). I'm trying with this: find /var/spool/mailman/bad -type f -name \*pck |\ while read m do (mailman qfile $m | grep -q ad.dr@ess) && echo $m done Is there a better way? -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

4 years, 6 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Tue, 25 Oct 2022 14:46:06 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/22 12:56, Onyeibo Oku wrote: > > > > I must be missing necessary policy modules for mailman or I am > > missing relevant parts of the tutorial that deals with SELinux. > > Where do I go from here? > > > Create the necessary SELinux rules to allow `mailman` to access what > it needs to. Roger that. There is progress beyond the previous report (after setting mailman_lock_t on '/opt/mailman/mm/var/locks'. Systemd fails again on '/opt/mailman/mm/var/logs/mailman.log' I applied mailman_log_t SELinux policy to that folder. Unlike the previous AVC, that didn't fix it. PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/logs/mailman.log' AVC avc: denied { append } for pid=774 comm="mailman" name="mailman.log" dev="sda" ino=2070696 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:mailman_log_t:s0 tclass=file permissive=0 > > I don't know if anyone on this list can help you with that. > > Note that if `mailman` is currently a `normal user` as opposed to a > `system user` making it a system user might help. See `man usermod` > Mailman user is a System User here. Regards Onyeibo

2 years, 11 months

[MM3-users] Re: config incoming email in my domain cpanel

by tlhackque

On 03-Aug-17 17:14, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > You've said you're working with labbrands.com <http://labbrands.com>. > > labbrands.com <http://labbrands.com> has address 192.185.51.89 > mail.labbrands.com <http://mail.labbrands.com> has address > 192.185.51.89 > www.labbrands.com <http://www.labbrands.com> is an alias for > labbrands.com <http://labbrands.com>. > > telnet proves that Exim is running on that IP address. Either you're > running it, or hostgator is redirecting the SMTP ports. > > You added: > lists.labbrands.com <http://lists.labbrands.com> has address > 190.145.27.66 > > Presumably that's a different machine. > > So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > image.png > > Is it correct??? > No. And sending images to the mailing list doesn't get you help. You set up lists.labbrands.com as a secondary server, not an independent mail domain. This will cause you serious grief. You need to get some help from a more suitable list. Setting this up is not mailman-specific, and getting it right is more than a quick note. Try the Postfix documentation & mailing lists. > > > And the SPF > records ... and spam and virus filters, and all the other stuff > you need > to setup an independent, public-facing smtp server. > > But at least you won't have to relay. > > Good luck. > > On 03-Aug-17 16:55, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > > >> I think you're confused. > >> > >> You already have mail.labbrands.com <http://mail.labbrands.com> > set up as the MX record for > >> labbrands.com <http://labbrands.com>. And it has an A record > with the same address as your > >> webserver. > >> > > I'm working with the hostgator mailserver, we are not running a > local > > mailserver. > > > > As suggested I added an A record like this: > > [image: image.png] > > > > Is it correct? is it redirecting to my Ip so I can redirect it to my > > postfix/mm3 server? > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > >> server running on that IP address. You can't have 2 servers > on port > >> 25. In that case, as has been noted before, you'll need to setup a > >> relay in that server, not a firewall redirect. Depending on > your MTA, > >> you would need to relay to your internal server. And make sure > your > >> firewall setup allows your MTA to do this. > >> > >> We can see it's EXIM: > >> > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > >> Trying 192.185.51.89... > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > (192.185.51.89). > >> Escape character is '^]'. > >> help > >> 220-gator4137.hostgator.com > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > Aug 2017 15:47:48 > >> -0500 > >> 220-We do not authorize the use of this system to transport > unsolicited, > >> 220 and/or bulk e-mail. > >> 214-Commands supported: > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > >> quit > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > closing connection > >> Connection closed by foreign host. > >> > >> Or, consolidate all your e-mail to one server - which is a lot > easier to > >> manage unless you have a really big operation. Postfix is > probably the > >> right choice, but requires more setup. > >> > >> Although Mailman3 configuration is not well documented (as you've > >> discovered), you may want to get help from someone with more > general > >> network and mail experience. You're now into territory that is, as > >> Simon indicated, not Mailman-specific. > >> > >> On 03-Aug-17 16:28, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >> escribió: > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >>>> escribió: > >>>>>> You need to forward port 25 for SMTP mail delivery and if > you want the > >>>>>> web UI (Postorius and HyperKitty) accessible from the > outside, port 80 > >>>>>> for http and/or port 443 for https > >>>>>> < > >>>>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>>>> . > >>>>> I mean for incoming mail redirected from my hostgator > hosting, because > >>>> when > >>>>> I suscribe an email address MM3 sends a confirmation email, > so I have > >> to > >>>>> reply to be suscribed to the list. > >>>> As I said, for mail delivery you need to forward port 25 to > the Mailman > >>>> server. > >>>> > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local > >> centos7 > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > >>> > >>> > >>>> -- > >>>> Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> > >>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >>>> > >> -- > >> This communication may not represent my employer's views, > >> if any, on the matters discussed. > >> > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- This communication may not represent my employer's views, if any, on the matters discussed.

8 years, 2 months

[MM3-users] Re: list of subscribers

by Simon Hanna

On 02/04/2018 01:45 PM, Peter Münster wrote: > On Fri, Feb 02 2018, Mark Sapiro wrote: > >>> Yes, the question is rather: where can *normal* members (or moderators) >>> can see the subscriber list? >> Currently, they can't. If you think they should be able to, you can file >> an issue at <https://gitlab.com/mailman/postorius/issues/new>. > Thanks. Done. > > It seems, that even the owner of the list cannot get the full names of > the subscribers, only the email addresses. Is there any other > possibility for the owner (or the site admin) to get the subscriber list > with full names (perhaps with some Python scripting)? You should be able to use mailmanclient to get a list of subscribers with names. Names are optional though, if people signup without them you won't be able to get them. Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if there is one associated. IIRC one person(postorius account) can also signup at different lists using different names (regardless of address). There was some discussion about names and potentially using the from header to populate the database but I don't remember the result...

7 years, 8 months

[MM3-users] Re: mailman import21

by Brian Carpenter

On 10/11/20 11:06 AM, Mark Sapiro wrote: > On 10/11/20 7:41 AM, Brian Carpenter wrote: >> Does the import21 script also import custom templates? > No. > > >> Are these custom >> templates contained in the config.pck file? > No. They are in the same MM 2.1 directory as the config.pck, but in a > sub-directory for the language code, i.e. lists/LISTNAME/LC/ > > >> Are there any known issues >> with the importing of mm2 templates into a mm3 environment? > > The replacements are different. i.e., things like %(email)s and > %(listname)s become $user_email and $short_listname. > > Also, there are some MM 2.1 templates that have no MM 3 equivalent. > Also, things like message and digest headers and footers that are MM 2.1 > list attributes that are templates in MM 3, although import21 tries to > handle those. So are how these templates showing up on my Mailman 3 servers? They show up in /opt/mailman/mm/var/templates/lists/listname/en/. I have a client whose old footer template from Mailman 2 still showing up in list messages. He then created a custom footer template via Affinity (same thing happen in Postorius) and both custom footers were being included in list messages. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 14/2/21 2:42, Abhilash Raj wrote: > You can actually translate the templates in Weblate too. That is > actually the whole > reason to go with monolingual template format in Mailman Core. > > Mailman uses the template file's name as the msgid for translations > and all in-tree > templates are copied into English's .po file when we re-generate them. > > For example in here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > The english .po file is considered as reference in Weblate and used > for source string. I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something. Can you, please, point me in the right direction on how to do it?

4 years, 7 months

[MM3-users] Re: Setting up From: field as list address

by Steven Maddox

Hey, Thanks Mark... found that about 2 minutes after I sent this in :) If you ever get a 'moderator waiting approval' reply when sending into a mailman list... don't suppose there is some magic command you can send into the list to cancel off a pending e-mail? :D Steven Maddox Lantizia On 25/11/2019 15:30, Mark Sapiro wrote: > On 11/24/19 11:54 PM, Steven Maddox wrote: >> Hi folks, >> >> I'm trying to configure our mailman3 lists (via postorious) in a way >> that'll mean they'll behave in the way way that I've witnessed on >> another 3rd party list (one running mailman2). >> >> This is where (when receiving a message from the list) the From: is the >> list itself, and the person who actually sent it bizarrely appears as a >> CC:, for example... >> >> From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> >> Subject: [Shropshire LUG] Whatever >> To: shropshire(a)mailman.lug.org.uk >> CC: s.maddox(a)lantizia.me.uk > > > Go to Settings -> DMARC Mitigations and set DMARC mitigation action to > "Replace From: with list address" and DMARC Mitigate unconditionally to Yes. >

5 years, 10 months

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 00:21, Mark Sapiro ha scritto: > On 2/28/21 10:17 AM, blackout69 wrote: > It looks to me like a race condition of some kind or possibly an > incompletely deleted thread. Have you deleted any threads? I have not deleted threads > I'm curious as to how you happen to be going to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> > as opposed to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. > I know that ULS and similar ones are in HyperKitty's urls.py, but I > don't see them exposed on any pages. > > Anyway, when you say "from that moment the maiilan3 has stopped > working." (sic) exactly what stopped working. Did core stop delivering > messages? Did Postorius stop working. If so, this all may be related to > some underlying database issue or something like that that was fixed by > the restarts. I don't see how this HyperKitty error could affect > Postorius or Mailman core. When I say that it stops working, I mean that all members of the lists no longer receive messages. Postorius and Hyperkitty continue to work blackout69

4 years, 7 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 11:06 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: > On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On 2/16/21 9:59 PM, Mark Dadgar wrote: >>> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >>> >>> Error messages below. >>> >>> rebuild_index fails with the same error. >>> >>> This is with django version 3.0.12. >> >> >> django.utils.six was removed in Django 3.0. See >> <https://pypi.org/project/django-utils-six/> for a work around >> replacement. I.e. in your venv do >> >> pip install django-utils-six > > > OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. One last note on this for the next person who searches the list archives: I also ran into the “Key too long” error while re-indexing. Applying the patch linked here fixed it: https://gitlab.com/mailman/hyperkitty/-/issues/322 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 7 months

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

by David Partain

On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: > > This is all because you are using the Ubuntu 18.04 package which is > about 4 years out of date and is from the era where HyperKitty, > Postorius and django_mailman3 still ran under Python 2.1.7. > > 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... 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? Cheers, David

4 years, 7 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marcus Bautze

Hallo, Am 27.05.2024 um 14:33 schrieb Mark Sapiro: > Enabling archivers is done in mailman.cfg similarly to > ``` > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg Thank you, archiver is now starting. Now there's another problem: In mailman.log i'm finding: "Jun 06 10:16:16 2024 (3556489) ACCEPT: <d3072553-2f52-4bd7-b14a-2701863812c7@***> Jun 06 10:16:17 2024 (3556492) HyperKitty failure on https://[URL]/mailman3/hyperkitty/api/mailman/urls: <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>nginx</center> </body> </html> (403)" in mailman-hyperkitty.cfg there is: base_url: https://[URL]/mailman3/hyperkitty/api/mailman/urls an in mailman-web.py ALLOWED_HOSTS = [ #"localhost", # Archiving API from Mailman, keep it. # "lists.your-domain.org", # Add here all production URLs you may have. '*' ] MAILMAN_ARCHIVER_FROM = '*' (only for test, if it works i will use my domains/IPS) If i try lynx https://[URL]/mailman3/hyperkitty/api/mailman/urls i'm getting "The archiver key must be sent over the Authorization HTTP header." an no forbidden What's the problem? Where i have to change something to get it working? (I'm using plesk) CU -- Marcus Bautze marcus(a)mbautze.de

1 year, 4 months

[MM3-users] Re: Moving existing lists to a new domain

by Jeremy Stanley

On 2024-11-21 14:22:27 -0800 (-0800), Mark Sapiro wrote: > On 11/21/24 07:43, Jeremy Stanley wrote: > > > > Preparing to test this, I poked around the schema a bit and noticed > > that the domain names are also embedded as strings in the following > > fields: > > > > django_mailman3_maildomain.mail_domain > > django_site.domain > > django_site.name > > These are all Django things. You can modify those values in the db. > > Note that django_site.name is just a name and doesn't need to be the exact > domain name. > > > domain.mail_host > > This is Mailman core's domain table. Again, you can modify the value in the > db. Yeah, I was planning to address all of those with additional SQL update queries, just wanted to make sure I found all relevant references to the domain name. > > Can anyone think of any additional tables/columns which would need > > updating for this? I'll see if scanning a dump of the full DB > > content turns up anything I might be missing too. Thanks again! > > I don't think there's anything else. Awesome, thanks again, as always! -- Jeremy Stanley

10 months, 3 weeks

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Shashikanth Komandoor

Dear Mark, As I already said, your suggestion worked well on one list. But when I tried to implement the same trick on another list, I found the below error messages in the mailman.log. > * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno > 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > > *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* > * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* > * f = open(self._path, 'rb+')* > *FileNotFoundError: [Errno 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > *During handling of the above exception, another exception occurred:* > *Traceback (most recent call last):* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, > in _one_iteration* > * self._process_one_file(msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, > in _process_one_file* > * keepqueued = self._dispose(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line > 37, in _dispose* > * process(mlist, msg, msgdata, pipeline)* > * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, > in process* > * handler.process(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line > 47, in process* > * with Mailbox(mailbox_path, create=True) as mbox:* > * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* > * _mboxMMDF.__init__(self, path, factory, create)* > * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* > * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such > file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > I ran in both the ways you suggested i.e. through "mailman shell" and "mailman remove". But no luck. Could you please suggest me at this point ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Sep 22, 2020 at 10:29 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > > Thank you Mark a lot. > > It worked awesome. You don't know how much you helped me. > > Thank you once again. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_8502129290396208734_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: >> > >> > But I am trying to delete a list on an urgent basis. Because of which I >> am >> > getting the above said errors. I tried to delete >> > through the interface, through curl command and through "mailman shell" >> but >> > nothing led me to a >> > positive result. Is there any work around to delete the list ? >> >> What have you tried in Mailman shell? This should do it. >> >> $ mailman shell -l list.example.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 list.example.com mailing list >> >>> getUtility(IListManager).delete(m) >> >>> commit() >> >> So should just >> >> $ mailman remove list.example.com >> >> What happens if you do those? >> >> -- >> 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/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 21:58 : > On 6/15/20 12:37 PM, Gilles Filippini wrote: >> >> There are 4 emails stored into this folder. 3 of them are spam, and the >> last one is a legitimate email. This is annoying that such emails could >> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >> more and more hyperkitty errors. >> >> Any idea how to make their processing more error proof? > > > Change the offending .encode() method to add errors='replace'. > > The traceback from the error should tell you where it is. > > You could also open an issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If > you do that, please include an error traceback if possible. If there is > not a traceback in mailman.log associated with the error, there might be > one in HyperKitty's log (configured in Django's settings). Also, > including enough of a message to duplicate the issue is very helpful. I've now deleted the offending messages. Will open an issue with related details the next time this error occurs. Thanks a lot, _g.

5 years, 4 months

[MM3-users] Re: Welcome message template errors

by Mark

>> On 2024-04-23 11:33, Mark Sapiro wrote: >> That URI should have been; >> >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > I think you are saying the what you reported originally was not > correct and the URL in the template table was in fact the latter URL. I meant when I typed the URL in my first email I had unintentionally omitted the name of the list (mytestlist) when I redacted the real domain name to 'lists.mydomain.com'. ...emplates/list/lists.mydomain.com/list:user:noti... I should have written ...emplates/list/mytestlist.lists.mydomain.com/list:user:noti... >> If I go to the above URL, the text of the list's Custom welcome >> message displays on an otherwise empty webpage. > > > And that's what is expected. So you can go to that URL and get the > template, but when Mailman Core tries to do the same thing, it gets a > timeout. Is there some firewall or other security software blocking > this access? #ufw disable Firewall stopped and disabled on system startup Then restarted everything... # ufw status verbose Status: inactive And still getting the error in the Postorius webpage ... HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', port=443): Read timed out. (read timeout=5)

1 year, 5 months

[MM3-users] Re: Header Filter madness

by Brian Carpenter

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. > Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules. > > The "Default action to take when a member posts to the list " is set to Default Processing for the problematic list. The list members moderation action is set to "List Default" for the problematic list. I duplicated the same settings using another list. Header filters works fine on the test list, does not on the production list. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

Okay, so the issue has been fixed by updating the data to an empty list equivalent (after finding, confirming and copying another lists empty value): MySQL [mailman]> SELECT accept_these_nonmembers INTO @newatn FROM mailinglist WHERE list_name='foo_is_a_good_list_with_emptyval'; MySQL [mailman]> UPDATE mailinglist SET accept_these_nonmembers=@newatn WHERE list_name='the_borked_list'; Query OK, 1 row affected (0.02 sec) Rows matched: 1 Changed: 1 Warnings: 0 Thanks for the help on troubleshooting that! Based on your import21 comments, I'm realizing the issue may be caused by multiple runs of import21. I have been (although I've stopped it for some time now) running import21 nightly to sync up my Mailman3 list data with Mailman2. I've been doing the same for archiving as well. I've noticed now that some lists have duplicate acceptable alias entries (looks to be like <number of aliases> x <number of import21 runs>) and the same goes for *_these_nonmembers entries. Is this a symptom of running the old(er) import21 command pre-3.3.2? Will the 3.3.2 import21 work as expected w/out the duplications if I was to clear out the appropriate lists col data (i.e., is it okay to run import21 multiple times)? I tried to figure out if there were any other duplicative data, but did not come across any. Is there more that I'm missing? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:28 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 2 months

[MM3-users] Re: clearing pending db

by Morris Jones

On 8/8/25 11:48 AM, Mark Sapiro wrote: > On 8/8/25 09:59, Morris Jones wrote: >> >> But pendingdb.evict() doesn't seem to clear the list. For example, on >> one of my lists: >> >> >>> from mailman.interfaces.pending import IPendings >> >>> >> >>> from zope.component import getUtility >> >>> >> >>> pendingdb = getUtility(IPendings) >> >>> pendingdb.count() >> 5040 >> >>> pendingdb.evict() >> >>> pendingdb.count() >> 5040 >> >>> > > > pendingdb.evict() only deletes expired pendings, but by default > subscriptions pending confirmation expire after 3 days, but this is set > by pending_request_life in the [mailman] section of mailman.cfg. Have > you set that to a long time? > > On the other hand in Mailman 3.3.2, subscriptions pending approval were > pended with a 10 year lifetime. This was changed in 3.3.5 to a new > moderator_request_life setting (default 180 days). > > If you just want to delete all pendings you could do > ``` > pendingdb = getUtility(IPendings) > for pending in pendingdb: > pendingdb.confirm(pending[0], expunge=True) > # and if doing this in mailman shell > commit() > Perfect, thank you Mark. :) Mojo -- Morris Jones, Monrovia, CA

2 months, 1 week

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

by Flo

On 10/10/25 04:13, Mark Sapiro wrote: > >> I have deleted site - group - list now. And created the site again. If >> I go to 'view site' I see all mailing lists on the server and not only >> from this site/domain. This is the first thing where it shows >> irregularities. > > I'm not sure what you mean by `view site` but if you mean the VIEW SITE > link at the top of the Django admin UI, that is just a link to the host > site. I.e., if the Django admin page is https://www.example.com/admin/ > site/, its VIEW SITE link just goes to https://www.example.com/ and it's > always the same link regardless of what Django admin page you are on. > The url of the Django view is lists.example.com/mailman3/admin. The 'VIEW SITE' is in the header on the right side. It's a link to lists.example.com/mailman3 which apparently gets redirected to lists.example.com/mailman3/postorius/lists. The difference I am talking about is that lists.example1.com/postorius/lists shows only its mailing lists while lists.example2.com/postorius/lists shows all mailing lists on the server (ie. also mailing lists of example1.com) Flo

5 days, 17 hours

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Fri, Nov 3, 2017, at 08:29 AM, Fabian A. Santiago wrote: > October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > > > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: > > > >> That was it. Perfect. I manually modified my regexp map and it works > >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh > >> those maps or only as I add new domains / lists? > > > > Only when you make changes to domains or lists. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> > > Sent from my Not_an_iThing with standards compliant, open source software. > > Mark, > > I've noticed that even simply restarting the mm3 components those alias > maps get rewritten and the problem returns until I can manually edit it. Yeah, that is true. Transport maps are re-generated everytime the container restarts. I don't think think there is any way around this right now :( > > -- > > Thanks, > > Fabian S. > > OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Barry Warsaw

On Sep 21, 2017, at 18:35, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: >> On 09/21/2017 01:29 PM, Andrew Hodder wrote: >>> >>> I keep getting around this by creating symlinks to the pid file and then >>> the stop works, but it's getting silly. It seems like mailman just assumes >>> CWD + /var/ + master.pid must be the location. Once I realized this, I >>> found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since >>> it'd then add /var/master.pid). But that seems a little nonsensical. >> >> That is the normal expected behavior if devmode is enabled. Check your >> configs for this. > > I don't think `devmode` has anything to do with this, it only disables > sending out emails by accident and routes all emails to a pre-defined > address. Haven't looked at the relevant portion of the source so I might > be wrong. That’s correct. The [paths.*] sections are what control the file system layout, and [mailman]layout is what defines which of the [paths.*] sections to use. Cheers, -Barry

8 years

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

I top post just for confirming that all your recommendations worked well and I am aplying them in the rest of servers Thanks a lot and all of you have a happy new year. El 27/12/22 a las 9:23, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: >> ... >>> I don't want to put more noise in the list. But I'm confused because >>> I always updated via pip the apache mod_wsgi thinking is was needed >>> for my configuration. If it is not, I will stop updating it. >> >> Based on the above you ARE using Apache mod_wsgi and if you are still >> also running uwsgi as >> >> /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & >> >> that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) > and see how it goes. > > Again, thanks for your kind support. > > > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 9 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:50 PM, Odhiambo Washington wrote: > > > Now that has clarified the matter for me. That even when I am logged out, > > the scripts do the neccessary > > to activate the venv to run things. > > > As mentioned before, a virtualenv is not like a container. It is only a > directory that contains among other things a bin/ directory with > activate scripts and easy_install, python, pip and wheel commands. > > When you activate a virtualenv in your shell, all it really does is add > a deactivate command, modify the command prompt and insert its bin/ > directory at the beginning of its PATH. > > What this means is whether or not a virtualenv is "active", running a > command from the bin/ directory in the virtualenv is using the virtualenv. > Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 9 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > However, this is apparently not relevant because both the Member and > Non-Member actions are Hold. Thus, the post should be held unless it has > an Approved: header with the list's moderator_password attribute if > there is one, or it matches a Header filter rule with an accept action. At the risk of getting this really wrong - I have only limited MM3 knowledge - I will ask what is, I fancy, a closely related question ... My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find anything to identify Postorius which is the only interface I have to the system. From symptoms seen and described by others, I have deduced that the Postorius admin-per-user moderation options of "Default processing" and "List default" mean that a user may be set (by default on the rootsweb system!) to use the system default moderation settings rather than the list default settings. Are my deductions correct? And if so, could this be the explanation of the issue detailed in this thread? Apologies if I'm barking up entirely the wrong tree, Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

6 years, 6 months

[MM3-users] Re: Hyperkitty shows "<" as <

by Andreas Schamanek

Thanks Mark, Your support is unparalleled. On Tue, 4 Apr 2023, at 10:44, Mark Sapiro wrote: > On 4/4/23 09:53, Andreas Schamanek wrote: >> All "<" and ">" in old and new messages are shown as "<" and ">" in >> message views _however_ they are shown correctly in overview abstracts e.g. >> at //server/mm3/hyperkitty/list/testlist@server/latest > > I don't think I've ever seen this. Certainly it is not the case on this list > with either current messages such as those in this thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> I tried to dig deeper and realized that on my test list "<" and ">" are only mangled when they surround email addresses as e.g. in <user(a)example.net> (ie. < user @ example . net >) I see that lists.mailman3.org renders such addresses as e.g. <a target="_blank" href="mailto:user@example.net">user(a)example.net</a> whereas my Hyperkitty shows them as <user(a)example.nett> But I have not yet found the responsible code or setting since it seems this is related to the option to obscure addresses. Or is my Hyperkitty 1.3.4 simply too old? -- -- Andreas :-)

2 years, 6 months

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Stephen J. Turnbull

Mark Sapiro writes: > One of the runners has died, most likely the `out` runner, but > possibly another. The missing messages are stuck in a queue. Do ``` > ls -laR /opt/mailman/core/var/queue ``` to see in which queue the > messages are. The runner that processes that queue is gone or > possibly stuck. I have seen "stuck", in a multisite installation where Mailman's smarthost ended up being about 1000 miles from Mailman. I'm not sure what the issue is (we fixed the DNS, not Mailman :-), but every once in the while the connection would hang. In that case nothing showed up in the log. The only symptoms were the buildup in the out queue and a stale connection to port 25 on the smarthost. If your smarthost is not "network far" from the Mailman host, this is quite unlikely from my experience, although Mark may know better. In any case, I think the best way to start diagnosis is to check the Mailman and MTA queues for stuck messages. Of course in normal operation you will often see messages in the queue, but long queues or messages older than a minute are 99% a dead or stuck queue runner. Steve

1 year, 6 months

[MM3-users] Re: Disable Sign-up per domain

by Mark

On 2025-07-31 03:31, Mark Sapiro wrote: > Anything is possible, it's only code ;) > > You could make your own user_adapter.py which is modified like > > and set that as the ACCOUNT_ADAPTER. This depends on whatever is > proxying to Django setting the appropriate HTTP_HOST header. Thank you Mark. It's so close. After wrangling your solution a bit it's working a treat on my test server (wrangled solution below) . When I add it to the production server (same OS, MM installation, etc) I'm getting a "Bad gateway" error page and the log reports ... ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. I cannot for the life of me get my head around that. I suspect it's something to do with what you said -- "whatever is proxying to Django setting the appropriate HTTP_HOST header." -- which I don't understand. Any additional advice gratefully received. ================================== /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py ================================== COMMENT OUT THESE 2 LINES... # def is_open_for_signup(self, req): # return False REPLACE WITH THE FOLLOWING... def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.mydomain.com': return False else: return True ================================== /etc/mailman3/settings.py ================================== Append the following ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ================================== systemctl restart mailman3 systemctl restart mailmanweb ==================================

2 months, 2 weeks

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 13. Dezember 2019 um 17:10 Uhr -0800 schrieb Mark Sapiro: >key is the <message-id> of the request message >request_type is 1 for a held message >mailing_list_id is a numeric index into the mailinglist table > >The issue is there are still held message requests there for the >messages you removed. You need to delete those entries from the _request >table. Thank you again for your valuable help. I've now taken the easy route and ran DELETE FROM _requests WHERE request_type=1; , i.e. I cleared the entire held messages queue. As it turned out, there were no requests of any other type than type 1. I've deleted all remaining files below /var/lib/mailman3/messages as well (after seeing it was only spam anyway, this time non-broken spam, but still spam). Now, finally, I can go to the held messages queue in Postorius again without a 500 error. The list of held messages there is now empty, but this is obviously expected. Let's hope that disabling SMTPUTF8 prevents the problem from further occuring. In any case, I've asked a friend report the problem to the Ubuntu tracker: https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1856181 I'm back on track now. Thanks everyone! Marvin -- Blog: https://mg.guelker.eu

5 years, 9 months

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Yes, I did. But to be sure I'll try on a vanilla VM and see how it goes if I install ruby-sass and python3-dev beforehand. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 7 months

[MM3-users] Re: multiple sites on a mailman3 server question

by William Oliver

On Wed, 2021-12-29 at 09:21 -0800, Mark Sapiro wrote: > On 12/29/21 8:48 AM, William Oliver wrote: > > > > What I'm trying to figure out is where uwsgi yanks control from > > nginx > > and does the rewriting. Pulling that proxypass stuff out will stop > > mailman3 from coming up, and adding it allows mailman3 to show its > > interface, but the address gets referred regardless. > > > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow > > tell > > nginx not to push it to port 8000. But I don't see where nginx is > > getting told to go to 8000 in the www.domain.com section. > > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you have > ``` > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > ``` > in your nginx config and everything goes to uwsgi. What you want is > to > put those proxy directives in only the mailman locations as at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > and then configure your document root so other locations are served > from > there. >

3 years, 9 months

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Mark, Mark Sapiro 於 2023/7/21 12:01 寫道: > On 7/20/23 20:42, Franklin Weng wrote: >> >> Thank you. When I set it in my settings_local.py, I clicked register >> and got an error: >> >> ModuleNotFoundError at/accounts/signup/ >> No module named 'django_mailman3.views.user_adapter' >> >> (In the document the path is /etc/mailman3/settings.py but I >> installed it with Debian packages so I guess the path is somewhat >> different, and I thought setting in setting_local.py should work >> too. It seems work since it gave me the error above.) >> >> Do I have to install something else? Or disable some other options? > > > What is the version of django_mailman3 in your Debian package? As it > says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for > these settings to work." > Debian Bullseye goes with 1.3.5, and Debian Bookworm goes with 1.3.9 but as I have said in another thread it has problems in django admin. So I downloaded the 1.3.9 source code, extracted it, and copied django-mailman3/views/user_adapter.py to /usr/lib/python3/dist-packages/django_mailman3/views. It worked! For a record here. Thanks for your help. Thanks, Franklin

2 years, 2 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/30 22:39, Mark Sapiro wrote: > It appears you have a situation where the MX for the Mailman domains > is not the Mailman server. You need to configure the MTA on > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > You can to this by configuring that MTA to use transport_maps, etc as > if it were the Mailman server. In order to get Mailman's generated > files on the other server, you need to create a process to do that. > When Mailman makes changes by adding or deleting lists or when it is > started, it updates the postfix_lmtp and postfix_domains files and > calls a command (normally postmap) to update the corresponding .db > files. The command can be set by setting `postmap_command` in the > `[postfix]` section in mailman.cfg. I'm not able to find any documentation about `postmap_command`, not even in the schema.cfg. If I have to provide method to update the postfix_lmtp and postfix_domains on another server, then it would have to something like sftp? mailman changes the files on the mailman server (in a location I set) and then postmap_command copies those files to the destination on the MTA server. Is that in principle what needs to be done? thanks again! Roland

1 year, 2 months

[MM3-users] Re: MM3 in virtualenv - FreeBSD-11

by Odhiambo Washington

I am keeping all of my steps in a text file. If I end up with a functional install, then I believe FreeBSD users will be able to install MM3 using virtualenv. I am banking on the help of the experts here to achieve that and document it. So far, I don't know anyone who is using FreeBSD who has managed to install and run MM3. This will be the first time anyone has ever done it. I therefore beg all of you to accommodate my stupidity. I'm 50 in April so it's not a mean feat 😂 😂 On Fri, Jan 11, 2019, 23:10 Mark Sapiro <mark(a)msapiro.net wrote: > On 1/11/19 6:51 AM, Odhiambo Washington wrote: > > > > Now that I look at it, I think you should clarify that if one is not > > interested in using PostgreSQL (which is what `pip install > psycopg2-binary` > > is for), > > then there should be some different binary they need to install, no? And > > which one is it? > > > I have added a note to the comment at > https://wiki.list.org/DOC/Mailman%203%20installation%20experience which > says: > > """Also, please note the first paragraph of the introduction. This is > documentation of my decisions and experiences. It is not a how-to and > does not replace the documentation at http://docs.list.org/""" > > In particular, documentation of the requirements for different databases > is at > <https://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>. > > > > Under your "*Recommended Configuration*", I have followed each step, > > getting the files and editing them to suite my needs, until I got to > where > > you refer to: > > /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file > but > > with DEBUG = False) > > I tried to get this file using `git clone > > https://gitlab.com/mailman/mailman_suite.git` > <https://gitlab.com/mailman/mailman_suite.git> and realized that > > authentication is required in order to get it. > > > Because you should be getting > <https://gitlab.com/mailman/mailman-suite.git> (hyphen, not underscore) > which works without authentication. > > Or you could just go to > < > https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… > > > and copy it from there. > > > > What is the reason you did not include a copy like for the rest?? > > > Because it's available on GitLab. > > > > I have created the executables - all of them. > > I have created the templates and did `find . -type f -exec sed -i.BAK 's/ > > mailman3.org/mydomain.name/g' {} \;` > > Maybe you should state explicitly that once one gets these templates, > they > > need to change the url to match theirs. You said it, but it doesn't come > out > > forcefully :0 > > > I added "Of course, if you use these you need to edit the URLs for your > site." > > > > In your "MTA" section, I suppose you need to be a little more generic as > > well and accommodate Exim users. > > First I suggest you clearly state that one needs to edit /opt/mailman/mm/ > > mailman.cf to ensure that the values under [mta] match what is required. > > Maybe there is a different file to edit for MTA settings??? > > > Again, I'm documenting MY experience, not trying to replace the official > documentation. I refer to > < > https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix > > > because I use Postfix. That same page also has Exim documentation. > > > > So far ..... > > > > Next, I will be looking into "Running Things".... which is where I > believe > > things will get thicker .... > > > Perhaps when you're done you will write u your experiences with FreeBSD > and Exim. > > -- > 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/ >

6 years, 9 months

[MM3-users] Re: Problems with web interface after upgrade

by Victoriano Giralt

De: Mark Sapiro <mark(a)msapiro.net> > On 2/9/21 3:26 PM, Victoriano Giralt wrote: >> >> It's CentOS7, but sassc was already installed and has -t as short for --style. > > You wrote > >> ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' > > It should be looking for just sassc, not 'sassc -t compressed {infile} > {outfile}'. Whats in your settings for COMPRESS_PRECOMPILERS. I'll check this anyhow. > That may not be the issue. You also wrote > >> compressor.exceptions.FilterError: Error: It's not clear which file to >> import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. >> Candidates: >> ../libs/bootstrap/stylesheets/_bootstrap.scss >> ../libs/bootstrap/stylesheets/bootstrap.scss >> Please delete or rename all but one of these files. >> on line 4 of static/hyperkitty/sass/hyperkitty.scss > > You need to remove the older of > > hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss > > and > > hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss > > That may be the whole issue. And it was! You clearly have telepathy, as I was testing this while you were writing, and your message arrived when I had just clicked send on my "SOLVED" message :-D :-D -- Victoriano Giralt Sent from mobile device

4 years, 8 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

Finally got a scenario where there was contents queued up for digest delivery and not enough traffic to kick off size based digest volumes. Running "/usr/local/bin/mailman digests --periodic --verbose" ran through all the lists and kicked out digests successfully. So something is making this work when I run it as the lists user by hand, but fail when I run it from cron as the lists user. Clearly this is on my end, I'll report back if I find anything useful or interesting. On 6/13/2023 2:14 PM, Mark Sapiro wrote: > On 6/13/23 10:58, Joel Lord wrote: >> I ran the "/usr/local/bin/mailman digests --periodic" again, sadly >> without the --verbose, and it kicked out the digests as it ought to >> have the first time. Now I have to wait for some list traffic to come >> in to "recharge" the digests so I have something to test with again. > > Even with the --verbose option, it wouldn't have helped much because it > worked. What we would really like to see is the output with the > --verbose option when it fails. > > It is a mystery to me why it would sometimes fail and sometimes not with > the same digest.mmdf file. > -- Joel Lord

2 years, 3 months

[MM3-users] Re: Getting connection timed out

by peter＠chubb.wattle.id.au

>>>>> "Stephen" == Stephen J Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> writes: Stephen> blackout69 writes: >> Il 23/05/21 01:21, Mark Sapiro ha scritto: > Can you successfully >> telnet to port 25 on mail.simail.it from the > Mailman server? No >> > If you can connect (via telnet) to port 25 on mail.simail.it from >> the > Mailman server, then I'd suggest stopping and restarting >> Postfix. >> >> if i try from the mail server i get >> >> telnet mail.simail.it 25 Trying 217.27.113.30... telnet: Unable to >> connect to remote host: Connection timed out Stephen> mail.simail.it is ignoring your mail server. This is not a Stephen> Mailman problem. 1. Check to see if that server has a Stephen> stated policy for "abusive" mail and some way of getting back Stephen> in their good graces. 2. Check if your mail server is in Stephen> the RBLs. Some of them are very aggressive about adding IPs Stephen> and domains. 3. Try writing the postmaster at Stephen> mail.simail.it. 4. Ask your subscriber(s) at mail.simail.it Stephen> to write their postmaster. Also check your firewall rules. Outgoing port 25 is usually blocked by ISPs unless you explicitly ask for it not to be. Peter C

4 years, 4 months

[MM3-users] Re: import an mm3 hyperkitty archive

by Eggert Ehmke

Thank you Mark, this got me on the right track. But I still think this not at all clear when reading the docs. My system is in a venv. I had to run these commands: mailman-web hyperkitty_import --since=01.01.2022 -l mylist@mydomain my-mbox-file mailman-web update_index_one_list mylist@mydomain Where is it stated that in this situation I have to run mailman-web instead of django-admin? Thanks anyway, problem solved. Am Donnerstag, 8. Dezember 2022, 17:51:58 CET schrieb Mark Sapiro: > On 12/7/22 05:57, Eggert Ehmke wrote: > > I was able to export the archive of my old mm3 installation in hyperkitty. > > However, I seem to be blind when looking for hyperkitty_import in the > > documentation. Where to start? > > There is documentation at > <https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html#im > porting-the-current-archives> and also at > <https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy>. > You can also run `django-admin hyperkitty_import --help`. The docs refer > to importing messages from MM 2.1, but you can import messages from any > unix like mbox file. > > Note in the above, `django-admin` is the command you use to invoke > Django's management which may be `django-admin`, `manage.py`, > `mailman-web` or something else depending on how Mailman is installed.

2 years, 10 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Broken web UI after upgrade - SOLVED

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:59 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Sat, Dec 17, 2022 at 9:33 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/16/22 22:21, Mark Sapiro wrote: >> > >> > I suggest you look at ownership and permissions. >> > >> > ``` >> > find /opt/mailman/mm/static/ -not -user mailman >> > find /opt/mailman/mm/static/ -not -perm -u+rw >> > find /opt/mailman/mm/static/ -type d -not -perm -u+x >> > ``` >> > and the same on >> > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ >> > >> > >> >> If the above doesn't reveal anything substantial, then let me know and >> I >> >> can bump up the verbosity. >> > >> > >> > I don't know if --verbosity 3 will reveal anything or not. You could >> try. >> >> >> Did you see the post at >> < >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>? >> >> Have you tried >> ``` >> django-admin clear_cache >> > > (venv) mailman@list:~$ /opt/mailman/mm/bin/django-admin clear_cache > Cache "default" has been cleared! > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ > total 16 > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 css > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 js > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ > total 8 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/js/ > total 8 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. > (venv) mailman@list:~$ > > So all the css files that were in /opt/mailman/mm/static/CACHE/css/ are > gone after running `django-admin clear_cache`. > > After that, I did run my mailman-post-update script again which created > dirfferent files under CACHE/css/ as the date shows > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ > total 20 > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 . > drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 css > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 js > -rw-r--r-- 1 mailman mailman 621 Dec 16 22:46 manifest.json > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ > total 176 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 .. > -rw-r--r-- 1 mailman mailman 162923 Dec 16 22:46 output.1d3a3c0dd51d.css > -rw-r--r-- 1 mailman mailman 1209 Dec 16 22:46 output.9a7b11621c5a.css > -rw-r--r-- 1 mailman mailman 569 Dec 16 22:46 output.e68c4908b3de.css > (venv) mailman@list:~$ > > I then rebooted the system just to be sure everything is restarted. > > And the PROBLEM IS SOLVED :-) > > Thank you very much for your time spent in following this up with me to > the conclusion. > So just for the record, I have added the clear_cache option to the script. Maybe this will benefit someone else one day. <CUT> #!/bin/bash set -e BINDIR="/opt/mailman/mm/bin" CONFDIR="/opt/mailman/mm" SETTINGS="settings" DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" STATIC_DIR="$CONFDIR/static" DEBUG="False" set -x if [ "$DEBUG" == "False" ]; then mkdir -p "$STATIC_DIR" || : "$DJANGO_CONTROL_SCRIPT" clear_cache "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput --verbosity 0 "$DJANGO_CONTROL_SCRIPT" compress "$DJANGO_CONTROL_SCRIPT" compilemessages fi syncdb_cmd="$DJANGO_CONTROL_SCRIPT migrate" if [[ ! -t 1 ]]; then # stdout is not a terminal syncdb_cmd="$syncdb_cmd --noinput" fi $syncdb_cmd echo 'Do you want to rebuild the search index? This takes a long time.' echo 'Type "Yes" to continue; anything else to quit.' read -p "> " response if [ "x$response" != "xYes" ] ; then exit; fi "$DJANGO_CONTROL_SCRIPT" update_index </CUT> The important thing here is that after an update, it helps to run the following 4 options with your "django-admin" script (whatever it is named) - clear_cache, collectstatic, compress, compilemessages. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/6/22 6:28 PM, Stephen J. Turnbull wrote: > > In my Debian configuration [mod_proxy_http.conf] is needed > > because it contains the necessary directives to enable proxying. > > Actually though, I think that's enabled as part of proxy. The Apache documentation strongly implies that this needs to be explicitly enabled by the admin: The forward proxy is activated using the ProxyRequests directive. Because forward proxies allow clients to access arbitrary sites through your server and to hide their true origin, it is essential that you secure your server so that only authorized clients can access the proxy before activating a forward proxy. By contrast for a reverse proxy: A reverse proxy is activated using the ProxyPass directive or the [P] flag to the RewriteRule directive. It is not necessary to turn ProxyRequests on in order to configure a reverse proxy. Both are from https://httpd.apache.org/docs/2.4/mod/mod_proxy.html. > However, see > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > I now suspect the real issue is there's no wsgi server listening on port > 8000. Could be. Apache docs notwithstanding, I'm happy to trust your intuition, and that would make things simple for the OP. :-) Steve

3 years, 9 months

[MM3-users] Fwd: Re: Removing a mail addresses and users

by Allan Hansen

All, This disconnect between Mailman Core and Django and Postorius is, by far, the weakest and, for subscribers, most confusing aspect of MM3 (once it has been installed, which is extremely hard and confusing). In a true account-centric system, you set up a web account and from there manage your emails and, for each email, your subscriptions. Subscription options would be hierarchical: account/email/list, with lower levels inheriting/overriding settings from/the level above. That’s really what I had expected when I pushed for us to move our 50 email lists to MM3 and I was very excited about the prospect, as it would solve a lot of system/subscriber management issues I had managing MM2. Alas, I was very surprised that that’s not how MM3 works. Some things got harder, even, such as the inability to change subscription addresses, which should have been a showstopper from the start! I still hope that MMxx OOTB will get there, but I guess it’ll be along haul. Would we be talking about MM4 to be released 20 years from now? Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. The above is not meant to aggravate the MM3 development team, for which I have utmost respect and gratitude, and which I admire for their tireless support given over decades to the community of admins. Software development is devilishly hard and time consuming. Yours, Allan Hansen hansen(a)rc.org > Begin forwarded message: > > From: Mark Sapiro <mark(a)msapiro.net> > Subject: [MM3-users] Re: Removing a mail addresses and users > Date: June 10, 2020 at 12:46:01 PDT > To: mailman-users(a)mailman3.org > > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) > > >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > > -- > 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/

5 years, 4 months

[MM3-users] Re: Moderation not working?

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: >> >> Hi Folks, Running a shiny new instance of mailman3, as per the >> Debian package (version 3.2.2) but the moderation doesn't seem to >> work. WE got hit by a heap of spammers overnight, even though the >> 'hold for moderation' bit is set for non-members (and now for >> members too). Mark> If the action for member posts was accept ot default processing Mark> at the time, perhaps the spam spoofed a member address in one of Mark> From:, Reply-To:, Sender: or the envelope sender, Nope ... >> Emails seem just to get straight through. Mark> Even now with both member and non-member actions set to hold? Haven't seen any emails since setting that bit, so can't tell yet. The only think I noticed after trawling through all the configs is there was no moderator address set up. In Mailman 2.1 that meant the list owner would be asked to moderate. I've added a couple of addresses to see what happens next For other lists on the same mailman instance I *am* seeing moderation requests for non-member postings --- but they had explicit moderator addresses configured. Peter C

4 years, 10 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by David Newman

On 12/29/21 4:11 PM, Mark Sapiro wrote: > On 12/29/21 3:58 PM, William Oliver wrote: >> >> I'd like to delete all my archives that are more than a certain age, >> e.g. more than a week old. I can easily do that with a cron job, >> deleting old files in >> >> >> /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* >> >> which is, as far as I can see the only place archive emails live. > > > Those are emails archived in the prototype archiver. That's all the > prototype archiver does - store the mail there. The HyperKitty archived > emails are stored in the mailmanweb database in the hyperkitty_email > table. Attachments are in the hyperkitty_attachment table and other > tables are also involved. As a followup: Is there any need or advantage to running both the prototype and hyperkitty archivers? I did an installation following the venv directions, and it looks as though the system now uses both archivers. If this is a duplication of effort and storage, is it safe to disable the prototype archiver like this: # /etc/mailman3/mailman.cfg .. [archiver.prototype] enable: no and then delete anything under here? /opt/mailman/mm/var/archives/prototype/ Thanks dn

3 years, 9 months

[MM3-users] Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: New installation, new issue: mailman3 migrate -- no module CommonMark

by Bill Oliver

On Sun, 2024-10-27 at 10:01 -0700, Mark Sapiro wrote: > On 10/27/24 05:13, Bill Oliver wrote: > > > > (venv) mailman@mail:~$ pip freeze | grep readme > > readme-renderer==17.4 > > > Which is over 6 years old. Howat did that get installed? Current > version > is 44.0. There may or may not be an issue with the current version as > it > imports cmarkgfm which is in the venv of all the MM 3 installations I > support, but I don't know how it gets there as even though > readme_renderer imports it, it is not listed as required by > readme_renderer or anything else. > > In any case, in your venv, do > ``` > pip install --update readme_renderer cmarkgfm > ``` > That did the trick, though I had to use --upgrade instead of --update. Thanks... Now on to the next step. I don't know about the libraries. Here's my mailman info. It seems like the right version of python. (venv) mailman@mail:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:qazASD%401cko@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Thanks for your help! billo

11 months, 2 weeks

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by ulf.rapphahn＠offis.de

Mark Sapiro wrote: > Lists, not Mailman lists. When you create a list in Postorius or Mailman > core, this is a Mailman list. A corresponding HyperKitty list will also > be created if hyperkitty is one of the active archivers for the list so > you see it in Django. > When you create a list in Django, it is only a HyperKitty list and will > be visible in HyperKitty, but no Mailman list is created so the list is > not in Mailman/Postorius. Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

11 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!

by Marco Emilio Poleggi

Thanks, Mark. On 2025-09-01 19:40, Mark Sapiro wrote: > On 9/1/25 08:17, ^m'e via Mailman-users wrote: >> >> The same problem appeared today with my mariadb-based installation. @Mark, >> do you have a mysql version of your scripts? > > I'm not certain as I don't offhand have a way to test, but I think > > g/psycopg2/s//pymysql/ > > (i.e. just replace both occurrences of `psycopg2` with `pymysql`) will do it. > Yeah, it works! In my case, no uppercase addresses were found by the UC_fix script, whereas the Mult_primary did spot two accounts, both with 'staff status' in Django admin UI and with the same set of extra addresses. Most probably my fault, as I intended to use both accounts for administrative tasks and played to far with assigning the same sets of addresses, one of which was primary for one account. I guess that was causing the failure, right? -- ^m'e ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0xC366FCF67CDBD9F9.asc

1 month, 1 week

[MM3-users] Re: Error: 451 Requested action aborted

by Hagen Bauer

On 16.11.18 00:41, Mark Sapiro wrote: > On 11/15/18 8:23 AM, Hagen Bauer wrote: >> Hi >> I am running mailman in docker and I start to receive this error when my >> postfix tries to deliver a mail >> >> said: 451 Requested action aborted: error in processing (in reply to end >> of DATA command)) >> >> Any idea what is going wrong and where to look for problems? > > > Is there more information in the Postfix mail.log? > > no, in postfix this is the only entry. But I believe I solved one problem and now have to work on the next one. First I saw this error in in a log file ERROR could not translate host name "database" to address: Name does not resolve Based on this hint https://github.com/moby/moby/issues/8425 adding external dns server made this message go away. Now I find this error in my logs. : ERROR: xlog flush request 0/1FA5640 is not satisfied --- flushed only to 0/1E9C7A0 CONTEXT: writing block 0 of relation base/16384/16525 I believe this is related to some sort of database corruption but since I have no idea about postgres I am not sure (I chose the docker images because I didnt want to care about the Internals) any suggestions are welcome

6 years, 10 months

[MM3-users] Re: SUBSCRIBE_FORM_SECRET in MM3?

by Phil Stracchino

On 2020-01-30 12:01, Mark Sapiro wrote: > On 1/30/20 1:50 AM, Gila Halpern wrote: >> I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? > > > This feature in MM 2.1 is not very effective. On mail.python.org, this > feature as well as reCAPTCHA is enabled (e.g. > <https://mail.python.org/mailman/listinfo/mailman-users>) and we still > get periodic attacks of robotic subscribes that get around these measures. Human verification vs. verification-defeating countermeasures is an ongoing arms race which, frankly, humans have been losing for a long time. I have more than once commented, not entirely joking, that we're reaching a point where *FAILURE* to complete the CAPTCHA is evidence that you're a human. We need to come up with a better verification paradigm than presenting increasingly difficult puzzles which AI agents are better overall at solving than humans are. -- Phil Stracchino Babylon Communications phils(a)caerllewys.net phil(a)co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958

5 years, 8 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Hello every body I have progress to try to reinstall mailman3 on yunohost server but I still have an error, if somebody can help me as I don't understand the log https://paste.yunohost.org/raw/ugijepuyuv Sincerely. Yvan Le 14/03/2022 à 16:31, Yvan ♞ a écrit : > Ok thanks, I'll try on debian forum as I already unsuccessfully tried > on yunohost since 6 months. > > Le 14/03/2022 à 16:23, Mark Sapiro a écrit : >> On 3/14/22 08:12, Yvan ♞ wrote: >>> Maybe an idea of my problem as I have pgadmin app installed, it >>> could be in conflict to create a postgresql db? >> >> Your original dbug logs seem to show no issue with postgresql. >> >> I don't think people on this list can be much help for installing the >> Debian package on YunoHost. As I said earlier, I would go first to >> YunoHost for help and then to Debian if necessary. >> >> If you want help from us, I recommend installing as documented at >> https://docs.mailman3.org/en/latest/install/virtualenv.html >> > _______________________________________________ > 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/

3 years, 6 months

[MM3-users] Re: combine postorius and hyperkitty into one Apache vhost

by Eggert Ehmke

So you prefer Gunicorn over uWSGI? When I have a working installation that uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason for this, and while I am open for alternate solutions, ... ´ never change a running system Am Donnerstag, 29. Dezember 2022, 21:48:54 CET schrieb Mark Sapiro: > On 12/29/22 05:51, Wolfgang Rosenauer wrote: > > Hi, > > > > I'm in the process to set up a new mailman3 site. > > (Migrating from mailman2) > > > > There are RPMs for my distribution which integrate postorius and > > hyperkitty with uwsgi. > > I think you'll be much happier if you don't use the distro's RPMs which > are probably out of date and instead follow > <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those > instructions use uWSGI as a WSGI interface, but Gunicorn > <https://gunicorn.org/> is what is used on the site supporting this > list. The advantages of Gunicorn are it's already installed as a > dependency of Mailman core, and it's what the Mailman developers are > more familiar with. > > I'll work on updating > <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include > Gunicorn as an alternative.

2 years, 9 months

[MM3-users] Re: Upgrade to 3.3.2 fails

by Joel Lord

On 12/26/2020 3:07 PM, Mark Sapiro wrote: > As far as utf8mb4 vs. utf8 is concerned. There will be issues with the > hyperkitty_email table subject and content columns in particular and > maybe others if email messages contain 4-byte utf-8 unicodes. However, > as I read the MySQL docs, for columns like VARCHAR(255) and > VARCHAR(510), the difference affects only the number of characters that > can be stored in the column and not the actual column width. I.e., a > VARCHAR(255) column is actually up to 256 bytes wide (1 byte for length > and up to 255 butes of data) and can thus hold up to 85 3-byte utf-8 > encodings or up to 63 4-byte utf-8 encodings, but since any string > normally contains only a few if any (probably none in the case of the > mailinglist table) the actual limit is much closer to 85. > Earlier I had attempted changing the encoding and collation and manually adding the new column, and it failed with the same error. This fits with Mark's explanation of how the column size and encoding go together. I just ran an "optimize table mailinglist;" and then the update ran clean. Thanks for the eyeballs today, no idea why that would have worked but now we're up and running. -- Joel Lord

4 years, 9 months

[MM3-users] [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by William Oliver

On Fri, 2021-12-24 at 21:12 -0800, Mark Sapiro wrote: > On 12/24/21 8:22 PM, William Oliver wrote: > > > > I clicked on that, and it took me to a page where I could add > > servers. > > So, I added my real domain (libertyfp.org) It successfully added > > it, > > so I decided that I clearly didn't need "example.com" as a server, > > and > > deleted it using the same page. > > > > Immediately, I got an "internal server error" and have now lost all > > web > > interfaces. I tried restarting the daemons and rebooting the box, > > to > > no avail. > > > You have to set SITE_ID in your Django settings to the correct value > for > your site. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > > Joy! You are a lifesaver. I had to guess at the ID number, but "2" worked. Just out of curiosity, if I could not have guessed a valid ID number and did not have the admin interface, how could I have figured out what site IDs were available? Thanks. billo

3 years, 9 months

[MM3-users] Re: Archive search failing on one list

by Mark

On 2023-09-24 13:28, Mark Sapiro wrote: > On 9/23/23 19:19, Mark wrote: >> >> Yes, the query returns a result and the case in "name" matches that in >> the query ... >> >> select * from hyperkitty_mailinglist where name like >> 'listname(a)domain.com' >> >> id | 91 >> name | listname(a)domain.com >> display_name | Listname >> description | ... >> subject_prefix | [Listname] >> archive_policy | 1 >> created_at | 2023-09-21 08:55:36.385239+2 >> list_id | listname(a)domain.com > > Is that really what you get for list_id? It should have a dot, not at > as listname.domain.com. > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models.mailinglist import MailingList >>>> mlist_name = 'listname(a)domain.com' >>>> mlist = MailingList.objects.get(name=mlist_name) >>>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> >>>> > ``` My bad. I was in too much of a hurry when redacting. The list_id is as you say: listname.domain.com

2 years

[MM3-users] Re: Mysterious Bounces Being Logged

by Allan Hansen

All, Appreciation to Brian for bringing this up. After upgrading to MM3, a lot of legitimate users' subscriptions on my lists have been disabled even though they still get at least some messages (according to them), while some were correctly disabled. Yes, I need to be informed of bounces, because when the accounts get disabled, I don't want my reply to be 'Huh? I don't have a clue why.' I reported this before. Yours, Allan On 3/26/21, 14:08 , "Brian Carpenter" <brian_carpenter(a)emwd.com> wrote: On 3/26/21 2:59 PM, Mark Sapiro wrote: > They are being bounced by a downstream MTA. If you want to know why, you > have a few choices. You can mail the address yourself and hopefully get > a DSN back. You can install this patch: I would think any mail administrator for a mailman server would want to know why bounces are happening. I never saw this issue with Mailman 2. Did it exist? Is the patch going to make it to the next version of Mailman 3 core? Are there any plans to make bounce processing more transparent to server admins so we can troubleshoot delivery issues? -- Brian Carpenter Harmonylists.com Emwd.com _______________________________________________ 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/

4 years, 6 months

[MM3-users] Re: Moving existing lists to a new domain

by Jeremy Stanley

On 2024-09-18 16:36:50 -0700 (-0700), Mark Sapiro wrote: > On 9/18/24 10:13, Jeremy Stanley wrote: [...] > > Since all the lists for the given domain will be moving to the same > > unused new domain on the existing server, and can move at the same > > time, I suppose this could be done through (offline if necessary) > > backend database update queries. [...] > ``` > UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = > 'old_domain'; > ``` [...] > ``` > UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE > mail_host = 'new_domain'; > ``` > For HyperKitty, similar changes need to be made to the > hyperkitty_mailinglist table. The `name` column entries need to be changed > from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column > entries need to be changed from `listname.old.domain` to > `listname.new.domain` Preparing to test this, I poked around the schema a bit and noticed that the domain names are also embedded as strings in the following fields: django_mailman3_maildomain.mail_domain django_site.domain django_site.name domain.mail_host Can anyone think of any additional tables/columns which would need updating for this? I'll see if scanning a dump of the full DB content turns up anything I might be missing too. Thanks again! -- Jeremy Stanley

10 months, 3 weeks

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Oops sorry I hit send to soon. If I try to go to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> I get a 404, it looks like unsubscription_requests<http://listname.example.com/unsubscription_requests> isn’t in my urls.py list for Postorius? (venv) [mailman@mailman postorius]$ grep version __init__.py # Software Foundation, either version 3 of the License, or (at your option) # any later version. __version__ = '1.3.4' (venv) [mailman@mailman postorius]$ grep _requests urls.py url(r'^subscription_requests$', list_views.list_subscription_requests, name='list_subscription_requests'), I’m upgrading this week to: django-mailman3 1.3.7 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 And I’ve just confirmed that 1.3.6 does have the url endpoint. So I’m guessing it came in in 1.3.5+? (venv) [mailman@mailman-dev postorius]$ grep version __init__.py # Software Foundation, either version 3 of the License, or (at your option) # any later version. __version__ = '1.3.6' (venv) [mailman@mailman-dev postorius]$ grep _requests urls.py re_path(r'^subscription_requests$', list_views.list_subscription_requests, name='list_subscription_requests'), re_path(r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests'), -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:15 pm, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

3 years, 11 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Abhilash Raj

> On Nov 1, 2021, at 9:07 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/31/21 10:42 PM, Simon Coggins wrote: >> Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: >> https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 >> But it’s not in 1.3.5: >> https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 > > > Yes, I was mistaken. That code was merged on 14 Feb 2021 and is not in Postorius 1.3.4 which was released on 2 Feb. It should have been in 1.3.5 and I don't know why it is not at https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49, but that is moot in any case. > 1.3.5 was a security release with no fixed included. It was branched off from 1.3.4 and only the security fix was applied. One Gitlab pro tip is when you are trying to determine which particular release a particular commit is included in, you can click on the the “…” three dots next to "parent 6096958a master” just under the title and it will show all the tags and branches that this commit is included in. https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3… for example, is included in 1.3.6b1, 1.3.6 and jquery and master branch. -- thanks, Abhilash Raj (maxking)

3 years, 11 months

[MM3-users] Re: Show diplay_name in a list

by Abhilash Raj

On Mon, Sep 30, 2019, at 6:33 AM, Joel Lord wrote: > On 9/29/19 5:59 PM, Mark Sapiro wrote: > >> Any idea what I was missing there? > > Often, member.display_name doesn't exist or is "None". > This seems to also be the problem that I submitted a while back (6 > months ago?) that the notification to the moderator of subscription > requests, which should include both display name and email address of > the requestor, only has the email address. We've been trying to track > the problem down in code but it keeps going deeper and deeper... This should be the UI trying to unconditionally convert a Python object to string. Name string transforms correctly, but since the absence of a name is denoted by a None object (as opposed to an empty string ''), the renderer mindlessly converts it to "None". It could be fixed with a simple {% if member.display_name is not None %}{{ member.display_name }}{% endif %} in the right place in the Django template. > > -- > Joel Lord > Web Administrator, Alpha Psi Omega Grand Cast > etc... etc... etc... > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years

[MM3-users] Re: Whitelist non subscriber

by Stephan Krinetzki

Mark Sapiro wrote: > On 08/06/2018 06:43 AM, Stephan Krinetzki wrote: > > > The steps are as follows, right? > > - Add users to the list and give the role "nonmember" > > - Set moderation action ('defer' or 'accept') > > Right. Good. So i understand it :) > > > > The only thing missing in the documentation is a note on how to do > > this via the Admin API. Who can explain that to me? > > Can you be more specific about what you are looking for? If by "Admin > API" you mean the REST API, are you asking how to interact with it or > what specific POST/PUT/PATCH commands to send? > > Or are you asking about the 'mailman shell' command? > With Admin API I mean the REST API from the localhost. Whether it's the REST API, the Mailman shell or the Admin API, I personally don't care. The only important thing is that we can set and use this role. However, I think that's settled anyway, since you're writing > > Also, we want to expose the nonmember role in Postorius and enable > setting moderation action for nonmembers, but we didn't get that in MM > 3.2/Postorius 1.2. So the whitelistening is not working at the moment, right?

7 years, 1 month

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Joachim Schrod

Mark Sapiro writes: > > > I maintain a mailing list for a private holiday where people don't > > subscribe themselves; I subscribe them. I have vetted their email > > address beforehand. (The subscribers are mostly not able to handle a > > verification email, nor any email-based workflow at all.) Is there a > > configuration option for a mailing list that sets "Pre Verified" to > > true as a default? > > > This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed > by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was > later extended by > https://gitlab.com/mailman/postorius/-/merge_requests/945 however these > are not available until Postorius 1.3.14 which is not yet released. > > These add a setting, POSTORIUS_DEFAULTS, which can be used to set these > defaults. E.g., setting > > POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True} > > will set the default for Pre Verified to True. So far, the only defaults > that can be set in this manner are mass_subscription_pre_confirm, > mass_subscription_pre_approve, mass_subscription_pre_verify and > mass_subscription_invite and those not until Postorius 1.3.14, but more > may be added. Thanks a lot for this info -- I'm looking forward for an upcoming Postorius 1.3.14 release! ;-) :-) Happy holidays and a good new year to everyone, Joachim

9 months, 3 weeks

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Abhilash Raj

> On Mar 27, 2021, at 3:03 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/27/21 2:08 PM, Brian Carpenter wrote: >> I was testing out the process of rejecting an incoming subscription >> request. Choosing the reject option for a moderated subscription request >> does send out a rejection notice but it gives no reason for the >> rejection. > ... >> Is there a place somewhere in Postorius to provide a rejection reasons >> for moderated subscription requests? Does Mailman 3 core provide this >> via its REST api but it is just not revealed in Postorius yet? > > > It's in Postorius since 1.3.3. If in the held message view, you click > the subject of a held message, you get a popup dialog the shows the > message with options to also show headers or the raw message. There is > also a dropdown t=o set the poster's moderation action and a box for a > reject reason if you click the reject button in the dialog. > > Do you not see this? I guess Brian was asking about Subscription Requests. Support for specifying reason when rejecting subscription requests has been added in master and will be a part of next release, 1.3.5 most probably. -- thanks, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Andreas Barth

* Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: > > > --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro > <mark(a)msapiro.net> wrote: > > >On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: > >> > >>My conclusion: > >>I ask you to consider these experiences in an update for the mailman3 > >>packages in debian bullseye. It would save time, questions and nerves. > > > > > >Issues with Debian packaging should be directed to Debian. > > Or as previously discussed, the debian packages should be avoided entirely. I strongly disagree with that statement. Distribution packages have their own up- and downsides. Of course, how they are done is to be discussed with the distribution, so: if something is wrong with a debian package, please follow the instructions on bugs.debian.org on reporting bugs. However, they have the advantage that they're integrated with the distribution. They have the disadvantage that they're stable for some time - that is why it's called a stable release. If they have all the features someone wants, they usually work fine (and my first mm3-installation was the default debian package). If one looks for bleeding edge, of course that's not what one can expect from a distribution package - but that's also a feature. Andi

3 years, 11 months

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > On 6/29/20 1:38 AM, Florian Schulze wrote: >> Hi! >> >> After upgrading to HyperKitty 1.3.x I get the following error for >> qcluster: >> >> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >> 300, >> in pusher >> task = SignedPackage.loads(task[1]) >> File ".../lib/python3.7/site-packages/django_q/signing.py", line >> 31, >> in loads >> serializer=PickleSerializer) >> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >> line >> 38, in loads >> return serializer().loads(data) >> File ".../lib/python3.7/site-packages/django_q/signing.py", line >> 44, >> in loads >> return pickle.loads(data) >> AttributeError: Can't get attribute 'process_task_result' on <module >> 'hyperkitty.tasks' from >> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >> >> How do I recover from that? It seems like there are still persisted >> tasks in the qcluster queue using the old code from 1.2.x with the >> old >> locking implementation. > > Have you stopped ans started qcluster since upgrading? Yes > Are you running the Django periodic jobs? They were disabled because of the errors (someone else did the upgrade). I have enabled them again and will watch it and report back. Regards, Florian Schulze

5 years, 3 months

[MM3-users] Re: Emailing a list from the list server

by Mark Dadgar

On Jun 1, 2020, at 11:45 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/1/20 10:02 AM, Mark Dadgar wrote: >> >> I cannot email a list from an account on the list server itself (for example, programmatically by script, but also manually) using mail / mailx / mutt / etc from the command line. The emails just disappear into the ether. > > > What's in Postfix's mail.log? Jun 1 11:54:55 mail postfix/lmtp[238922]: 1F42613BEB5: to=<test3(a)pdc-racing.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.02/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) smtp.log: Jun 01 11:54:55 2020 (238852) Peer: ('127.0.0.1', 53402) Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) handling connection Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'LHLO mail.pdc-racing.net' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'MAIL FROM:<mark(a)pdc-racing.net>' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) sender: mark(a)pdc-racing.net Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'RCPT TO:<test3(a)pdc-racing.net>' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) recip: test3(a)pdc-racing.net Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'DATA' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'QUIT' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) connection lost Jun 01 11:54:55 2020 (238852) Connection lost during _handle_client() Test3 is a working mailman3 list. There are no posts held for moderation. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 4 months

[MM3-users] Re: {Spam?} Re: Monthly mailman-web job using a lot of memory

by Andy Smith

Hi, On Fri, Jul 01, 2022 at 12:57:41PM -0700, Mark Sapiro wrote: > I second Mark Dadgar's comment to replace whoosh with xapian. It > will help, although it requires rebuilding the entire search > index. Thanks both. Yes I am currently using whoosh which is the Debian packages' default. I decided to dramatically reduce the number of messages in our archives, as the vast majority of them are for lists that had never actually been looked at ever when under Mailman2, and external archives of them already exist. For ~6k messages it still took approx 16 hours to run that monthly job, and during that time spewed out thousands of these errors: Failed to remove document 'hyperkitty.email.29351' from Whoosh: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query w = self.writer() File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer return SegmentWriter(self, **kwargs) File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ raise LockError whoosh.index.LockError …so I'm not even sure if it worked. I will definitely have to look in to switching to Xapian. Thanks, Andy

3 years, 3 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

Hi Mark, 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. This is weird because other mails have been distributed. The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings Best Regards,Eric On Sunday, December 13, 2020, 06:29:19 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote: > There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value. I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log. > I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." What if you look at "threads by month" and select the current month? > Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago? As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job) -- 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/

4 years, 10 months

[MM3-users] Re: Enable delivery

by Hirayama, Pat

Apologies, I should've said my "Mailman 3" server, not listserv. MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs. As for the CLI commands, I keep getting Attribute Error when I try them, like: /opt/mailman # mailman shell -l listname(a)mailman.tld 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 listname(a)mailman.tld mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)domain.com.') >>> print(mbr.delivery_status) Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'delivery_status' >>> Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, December 9, 2024 18:38 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Enable delivery CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20… > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://urldefense.com/v3/__https://gitlab.com/mailman/mailman/-/blob/maste… Also see the various tabs at https://urldefense.com/v3/__https://www.example.com/mailman3/accounts/subsc… > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` mailman shell -l list(a)example.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 list(a)example.com mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

10 months

[MM3-users] Re: configuring postfix local recipient table

by Alexander Inzinger-Zrock

Am 29.04.25 um 18:27 schrieb Mark Sapiro: >> Last idea before that would be to >> >> 1. delete the files: >> >> -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_domains >> -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_domains.db >> -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_lmtp >> -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_lmtp.db >> >> 2. restart services >> >> 3. test if programms make new files >> >> 4. report to mailinglist >> >> Would that be of interest to someone? > > Yes. + [X] deactivate services + mailman3.service + mailmanweb.service + postfix.service + postfix(a)-.service + [X] deleting files under /opt/mailman/mm/var/data + postfix_domains + postfix_domains.db + postfix_lmtp + postfix_lmtp.db + [X] restart services + mailman3.service + mailmanweb.service + postfix.service + postfix(a)-.service LEARNINGS: + no new files made (expected). + despite mailman3.service reports: + 'Apr 30 14:37:40 mlist01-prod mailman[533171]: Generating MTA alias maps' + postfix warns about the deleted files (expected): Apr 30 14:41:02 mlist01-prod postfix/error[533928]: warning: hash:/opt/mailman/mm/var/data/postfix_domains is unavailable. open database /opt/mailman/mm/var/data/postfix_domains.db: No such file or directory Apr 30 14:42:02 mlist01-prod postfix/error[533928]: warning: fast_flush_domains: hash:/opt/mailman/mm/var/data/postfix_domains: table lookup problem Apr 30 14:42:02 mlist01-prod postfix/error[533928]: warning: C5B821C00E5: flush service failure

5 months, 2 weeks

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Andrew Bernard

Hi Mark, Thanks for your great help. But despite decades of UNIX experience, my area is not Django (yet). The nub of my question is that I thought you have to have a manage.py file for Django to be able to set up the various affairs, such as making the database migrations and so on. It is that that is eluding me. Apologies for this hopelessly newbie question. I was impressed with your method of installation in the page referenced, and I have foolwed that closely. But I am puzzled about the build script. If I run as user mailman, not root, it wanted to install under /usr. which of course results in permission denied. I had to modify the script to say this: python setup.py install --prefix /opt/mailman/mm/venv I am concerned that I have also misunderstood something here. A On Sun, 9 Jun 2019 at 00:57, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/8/19 4:04 AM, Andrew Bernard wrote: > > > > Where is the Django config area for the > > pip installed modules? It is this that I find obscure. > > The short answer is wherever you put it. If you look at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > which Abhilash mentioned, you'll see what I do. > > >

6 years, 4 months

[MM3-users] Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Thursday, March 17, 2022 12:06 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This says that there is no Address object with the email > xxxxxxxx(a)xxxxx.org > > What do you get in `mailman shell` for > ``` > >>> um = getUtility(IUserManager) > >>> um.get_address('xxxxxxxx(a)xxxxx.org') > >>> um.get_user('xxxxxxxx(a)xxxxx.org') > ``` > These should return an Address and a User respectively. If they don't, > did you perhaps run some process to delete the user? I've done nothing in regard to this user. Neither command returns anything. I see it return my user object if I test with my own email address. > If the user is gone, you should be able to replace > ``` > ... sub_mgr.confirm(token) > ``` > in the above with > ``` > ... wfm = getUtility(IWorkflowStateManager) > ... pendings.confirm(token, expunge=True) > ... wfm.discard(token) > ``` > to clear the pending subscription and workflow and then be able to mass > subscribe the user. I did this, and can confirm that they no longer show up in the list of pending subscriptions via the mailman shell interface for that list. However, if I go to mass subscribe them via the interface, I get: HTTP Error 409: b'Subscription request already pending' Regards, Quanah

3 years, 6 months

[MM3-users] Re: message awaits moderator approval

by Eggert Ehmke

Yes, the templates did have URL's of the old lists. I changed them to refer to the new lists. Am Mittwoch, 21. Dezember 2022, 21:33:26 CET schrieb Mark Sapiro: > On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > > database, in particular in the template table. I removed them using direct > > SQL commands. > > > > Now my new mailing lists work as expected. > > > > Is this a bug in postorius? I think when I delete a mailing list, all > > relicts should be deleted from the database. > > Were there Postorius custom templates for that list?, I.e. did the > template table entries have Postorius URLs. If so, this is probably a > Postorius issue. I haven't actually looked, but when Postorius deletes a > list, it should delete any of it's templates from the > postorius_emailtemplate table and revert the template table entries. > > Beyond that, Postorius is just telling Mailman core to delete the list, > and when Mailman core does that it should probably also remove any > var/templates/lists/<list_id> directory and any entries from the > template table with context = the list_id. If it doesn't, this is a core > issue.

2 years, 9 months

[MM3-users] Re: mail loops back to myself

by Florian Sukup

On 6/12/25 19:48, Mark Sapiro wrote: > > That is not correct. Postfix should receive the initial connect and smtp > for the list and then transport_maps should tell it to relay the message > via lmtp to the configured lmtp_host and lmtp_port (127.0.0.1:8024 per > your previously posted mailman.cfg). You have also posted that Postfix > main.cf contains > > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > > What is the content of that file? In particular does it contain > > mylists(a)lists.yyy.com lmtp:[127.0.0.1]:8024 > Yes, that's exactly the case. > and is the timestamp of /var/lib/mailman3/data/postfix_lmtp.db >= that > of /var/lib/mailman3/data/postfix_lmtp, and have you restarted/reloaded > Postfix since updating main.cf? And, is Mailman core running and > listening on port 8024? > # ls -rtl total 296 -rw-rw---- 1 list list 270336 Jun 8 21:58 mailman.db -rw-rw---- 1 list list 1123 Jun 12 08:43 postfix_lmtp -rw-rw---- 1 list list 367 Jun 12 08:43 postfix_domains -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_lmtp.db -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_domains.db # lsof -i :8024 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python3 1146914 list 23u IPv4 78503106 0t0 TCP localhost:8024 (LISTEN) I always restart mailman3 after changing main.cf if there is any interest, postfix_domains contains this line: lists.yyy.com lists.yyy.com Florian.

4 months

[MM3-users] Re: auto-away notices as bounces

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > On 8/24/21 11:17 AM, Andreas Barth wrote: > > > >Well, the mail adress got disabled, and the user got warning mails > >("Your subscription for list mailing list has been disabled"). As none > >of the list owners did that, I don't think there is any other > >explanation. Please note that individualsation was enabled, so all > >mails are sent out with per-subscriber mail envelope address, which > >then makes bounce detection quite straight-forward. > > > If by 'individualsation was enabled' you mean messages were VERPed, > there could be a bug here. Yes, that's what happens. > There are a couple of considerations. First the vacation responder > should not respond to list messages. See > <https://www.rfc-editor.org/rfc/rfc5230.html#section-4.6>. I fully agree with you, and already responded with the same remark to the user before sending my initial mail here. > That said, bounce processing should treat even a VERPed message as > unrecognized if it doesn't look like some kind of DSN. This may not > be the case in MM 3. Thanks, that's what I also think. Looking at the returned mail, they definitly don't look like DSNs / bounces to me. Anything I should be doing re this topic? Thanks, Andi

4 years, 1 month

[MM3-users] Re: How to delete non-users

by Allan Hansen

That worked, Mark. Thank you. Now I just have to figure out how to put it all in a script for the cron utility, so I can run it daily (or hourly, for that matter). But for now I have no more non-members. Yours, Allan As for non-members, the list settings for 'Message Acceptance' has a number of options to accept, hold, reject or discard messages for a list of addresses (entered using regexps, even) of non-members. Under 'Users' there is an option to add non-members. Given this, the notion that non-members are being automatically created in the database, has been a source of confusion to me, let alone my users/moderators. On 9/17/22, 11:18 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 11:01 AM, Allan Hansen wrote: > Sure: > >>>> lm = getUtility(IListManager) >>>> for l in lm: > ... print(l.posting_address) > ... >>>> > > Nothing here, either. So your `mailman shell` command is not pointing at your productiom mailman.cfg. Try `mailman -C /path/to/production/mailman.cfg shell` -- 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/

3 years

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Dan Caballero

> But I am confused as to your goal. Previously when the list was > anonymous, all replies went to the list. Maybe your goal is to have list > replies be addressed to <list-name(a)caltech.edu> rather than Last Name, > First Name via list-name <list-name(a)caltech.edu>. If that is the goal, > you could try setting Reply goes to list setting to Reply goes to list. > That will set a Reply-To: list's short description > <list-name(a)caltech.edu>. That may be what you want as long as the > responder's MUA honors Reply-To: over From: > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Thanks. I had forgot to mention that we did also configure the DMARC mitigation to show the sender's email. You're correct about us looking to set the "reply-to" to the list address instead of the sender. I've done some testing and this is close to what we need. However, I seem to be having an issue with the option for "Explicit Reply-to set; no Cc added". The messages are still including a Cc field with the sender's email. Is there another setting that affects the Cc field? Thanks again.

4 months

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Stephen J. Turnbull

Mark Sapiro writes: > Then the people who developed the web based management UI (Postorius) > and archive UI (HyperKitty) chose to develop those within a Django > framework and Django has its own concept of User separate from Mailman > Core and that is where the disconnect occurs. > > It's not that Mailman Core lacks what you want. It's that Django doesn't > use it. I think that's mostly right, in terms of the features that users miss. However, as far as I know, Mailman core does lack facilities for identification, authentication, and authorization of connections to the REST API. And that means that the front ends have to handle this. I would guess that's why the web interfaces are built around Django user authentication. I think it would be possible to have somewhat tighter integration between the Django "web users" and the Mailman core User objects, but it's not necessarily going to be trivial. I see that Abhilash is pretty optimistic, but I fear this this is going to be a long-tail situation where we're going to be seeing core user vs. web-gui user integration issues in 2030 (maybe by then only 1 every 450 days ;-). I have some ideas, maybe in a couple weeks I can sketch them out. Steve

5 years, 4 months

[MM3-users] Re: customized welcome message

by Nils

On 12/7/23 22:40, Mark Sapiro wrote: > How and to what did you set the URL for the template? What does the > database query > > SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; > > show? http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD This value can't work. Now it makes sense that it gets redirected and the use of localhost also explains why it didn't show in any of the virtual hosts log files that I was checking until it was redirected. However, I didn't set that value. I edited the template at postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can just select a template type and then I get one textarea input field for the content. The value in the database is set automatically, when I create a template in postorius (and is also automatically removed when I delete a template there). I can't edit this value without manually changing it in the database. > This is very old. Current Postorius is 1.3.10. 1.2.4 is from February > 2019. The Debian/Ubuntu packages are out of date. We recommend > installing via the doc at > https://docs.mailman3.org/en/latest/install/virtualenv.html The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) very soon. The Debian/Ubuntu packages sure have their downsides but once they work, they update automatically and require very little maintenance.

1 year, 10 months

[MM3-users] Re: Hyperkitty messages stuck in spool

by Andrew Hodgson

Stephen J. Turnbull wrote: >Mark Sapiro writes: > > On 11/18/21 6:38 AM, Andrew Hodgson wrote: > > > > > > Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? > > > > I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. > >If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. Thanks. Andrew.

3 years, 10 months

[MM3-users] Re: [Mailman-Users] Web interface for users (not admins)?

by Stephen J. Turnbull

Mark Sapiro writes: > No, Posting from HyperKitty without using the "Use email software" > button is plain text only. That surprised me. There is the possibility of enabling Markdown in the viewer, but that's not a real solution for atechnical users who are used to mousing around, and by itself doesn't enable attachments. > There is no plan to add any sort of rich text capability. That doesn't surprise me. A number of things are possible, but I think that providing the mailto link give the atechnical user the best of both worlds: a quick text-based response or the comfort (? :-þ) of their usual mail client. One constraint that we have is that many of our users value "no Javascript" quite highly, so just dropping in the Electron-based editor du jour is something we don't want to do. By the way, Skip, if you decide that richtext followups are an important feature, earlier I mentioned EMWD's commercial offerings Affinity (for admin) and Empathy (for archiving). I don't know if Empathy offers more features for posting than HyperKitty does, but I encourage you to check with Brian Carpenter <brian(a)emwd.com>. These are commercial, closed-source (at least for now) offerings, but I believe rates are reasonable and support has a very good reputation. Regards, Steve

4 years, 5 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Wed, Dec 14, 2022 at 8:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/22 08:15, Odhiambo Washington wrote: > > After upgrading MM3 and running all the post-update tasks and even > > re-indexing all the posts, I have ended up with a somehow "broken" > > hyperkitty. > > The archives display on a browser six, to say the least. > > The site is public, so I can share the link: > https://list.rc.org/archives/ > > > > What should I do in order to fix this? > > > > > Are you asking about the lack of style or the "No archived list yet."? > The lack of style is the main issue. > The former indicates an issue in your web browser with accessing the > `static` directory or an issue with the django admin collectstatic or > compress commands. > So I have tested this with Brave, Google Chrome, Firefox - all on MS Windows and I do clear the browser cache. > I don't know about the latter - could it be because all the archives are > private and I'm, not logged in? > Even when logged in, the situation is the same, unfortunately. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Social signup?

by Duane Raymond

HI Mark, On Sun, 12 Mar 2023 at 22:06, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/12/23 13:56, Duane Raymond wrote: > > Is there a way to enable social signup (vs just login for existing > users)? > > It isn't at all clear or documented, but a user without an account can > go to the login page and login via a social account button and this will > create an account connected to that social account and log the user in. > Thanks for clarifying. Once I implemented social login, the buttons for social login did appear fine on the login page, but not on the signup page. I noticed for this list as well, there are no social signup buttons. So if it works, how does this happen? 1. Is there something I am missing adding to my settings.py and settings_local.py files to make it appear on the Posterius/Hyperkitty signup (vs login) page? (I searched but couldn't find anything) 2. Do I manually add this code to the Posterius/Hyperkitty signup template? 3. If a user tries to login via the login page and isn't registered will it be counted as a signup? 4. something else :-) I'm trying to get my head around where this is working from / what I need to do to get social signup obvious on the signup page (or other route) Cheers, Duane

2 years, 7 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 9:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/25/22 01:14, Odhiambo Washington wrote: > > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> 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? > > > It is defined in django_mailman3/urls.py which is referenced by > > re_path(r'', include('django_mailman3.urls')), > I have seen that now. > > 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/ > > It shouldn't include `allauth.urls`. That URL is appropriate if you > aren't logged in, but what do you get when you are? > > Go to https://lists.mailman3.org/user-profile/ and log in if necessary > and you'll see what it should look like. > Here when I log in. I land on the /archives ( https://lists.mailman3.org/archives/?sort=popular) I then head to the dropdown and click "Account " and I am taken to https://lists.mailman3.org/user-profile/ (very clean URL!) and that's the same thing I am seeing on my server at the moment.. When I comment out the edit I had on /etc/mailman3/urls.py and uncomment to /user-profile alias in the VHOST, I end up with 1. https://mm3-lists.kictanet.or.ke/user-profile/mailman3/lists/ - once I am logged in 2. https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ - when I click on "Account " # I hope you can see the duplication of /user-profile, which is ugly. However, your server isn't using mod_wsgi, I believe, so I shouldn't be comparing it to mine. I just don't like the extra URLs being added. > 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. > > They are in your instance because of > > re_path(r'^user-profile/', include('allauth.urls')), > > but they should not be. > I have changed that, as already pointed out, but with consequences :) There must be a way to not have "/user-profile/user-profile" > >> 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. > > > Why? Intellectual curiosity or do you have an actual need. > It's out of intellectual curiosity actually. The bottom line is with mod_wsgi, whatever you have in your > WSGIScriptAlias is going to be prepended to the URL path. If you don't > want anything prepended, you need > ``` > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > ``` > but then in order for user-profile to work, you need to replace > ``` > re_path(r'', include('django_mailman3.urls')), > ``` > in urls.py with the urlpatterns from django_mailman3/urls.py > ``` > re_path(r'^user-profile/delete$', delete_account, > name='mm_user_account_delete'), > re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), > ``` > and also add > ``` > from django_mailman3.views.profile import delete_account, user_profile > ``` > to the imports in urls.py > And with that, I am now happy with what I am seeing. Again, thank you very much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > We're really working on getting a consistent, workable installation > story and even getting some packaged solutions. I know we're not yet > there, but we're here to help when people run into problems. The site now works, but not the / url for the site. I get this error in the mailman-web.log (with a very long stacktrace before it) NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. 'hyperkitty.views.index.index' is not a valid view function or pattern name. I think that would correspond to this line in urls.py url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), but this corresponds exactly to what the example config says and I know of no other name for hyperkitty. Probably it is dependent upon understanding the url dispatching in Django but that takes some time to read up on. The interesting thing is that /archives works so it is just this redirect that has problems. I can probably get apache to do the redirect instead but that is not the most elegant solution. Then I of course have things to do on getting social logins to work. I currently get "DoesNotExist: SocialApp matching query does not exist." if trying to connect an account to google (which I started with). Not a showstopper as passwords do work. cheers // David

8 years, 6 months

[MM3-users] Re: Where is postorius.wsgi?

by Peter Münster

On Thu, Jan 25 2018, Mark Sapiro wrote: > It's got a different name. It's in the above directory, at > example_project/wsgi.py Thank you. Unfortunately, it does not work... First I tried with python-3 (installed package was "apache2-mod_wsgi-python3"), but I got this error: Invalid command 'WSGIScriptAlias', perhaps misspelled or defined by a module n...ration Then, I tried with python-2 (installed package is now "apache2-mod_wsgi"), and this is the error message of apache: mod_wsgi (pid=18880): Target WSGI script '/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py' cannot be loaded as Python module. mod_wsgi (pid=18880): Exception occurred processing WSGI script '/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py'. Traceback (most recent call last): File "/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py", line 16, in <module> application = get_wsgi_application() File "/usr/lib/python2.7/site-packages/django/core/wsgi.py", line 14, in get_wsgi_application django.setup() File "/usr/lib/python2.7/site-packages/django/__init__.py", line 17, in setup configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup(name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) ImportError: No module named settings Could you help me please, to get Postorius working (and later also HyperKitty...)? TIA for your efforts, -- Peter

7 years, 8 months

[MM3-users] Re: MM3+Python3.11

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:52 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Mon, Mar 6, 2023 at 7:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/6/23 08:23, Odhiambo Washington wrote: >> > >> > I install Python3.11 manually on Debian12 (maybe this is the issue!) VM >> > using the script below: >> > #!/bin/bash >> > cd Python-3.11.2 >> > ./configure --enable-optimizations >> >> You also want --enable-shared >> > > I had done that, but somehow the build had failed with it. I will try it > again. > I managed to reinstall Python3.11 the correct way: <CUT> #!/bin/bash cd Python-3.11.2 ./configure --enable-optimizations --enable-shared make altinstall # Set Python 3.11 as the Default update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.11 1 # Install PIP using the following command if you do not have it. curl -sS https://bootstrap.pypa.io/get-pip.py | python3.11 </CUT> After this, I installed a fresh venv, activated and installed everything according to ``` https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… ``` MM3 is running fine with uwsgi as documented. I have not deviated even a single step from the documentation above. Now I will test with mod_wsgi and gunicorn and report back. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users]Re: Installation issues

by Andrew Hodgson

Mark Sapiro wrote: >On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > >> I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? >Sort of, but it's not (yet) public. The process I followed is very >convoluted and not what I would recommend anyone follow. Part of the >issue is I started with mailman-bundler not using a venv, but bundler >still installs a lot of stuff in Python 2 and Python 3 venvs. I then >proceeded to install the git master branches of mailman, >mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their >dependencies system wide and ripped out most of the venv stuff. I started off without using venvs and ran into several issues, though one of them I think was due to the bundler pulling down an outdated dependency. My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible. Thanks. Andrew.

9 years, 5 months

[MM3-users] Re: Announce Only List

by hansen＠rc.org

Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > > So if we want to make a list announce only (e.g. > > only specific > > folks) can post, I've found I can set the list settings to > > automatically discard messages from members and non-members. Then > > I go into the individual permissions on each user to be allowed > > to post without moderation. This works fine, however it seems > > cumbersome. > > Don't we have a list style for announce lists? If we don't, we > should.... > I don't see what's "cumbersome" about the individual permissions. You > need to do something per allowed user, if only sending email to > their individual addresses to tell them the password in the anternate > method: > > There is an alternative. Set a moderator_password for > > the list. Then > > anyone can successfully post with an Approved: <password> header or > > pseudo header if they know the password. > > Steve I have a few lists that I set up as announce-only lists by simply dumping all email but that from a couple of authorized members. It's a one-off deal and was trivial to set up. There are more urgent things to spend time on, IMHO. :-)

5 years, 2 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Odhiambo Washington

On Sat, Oct 28, 2023 at 7:19 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/23 01:59, Odhiambo Washington wrote: > > Running an install on Debian12 VM. Getting a new error message that I > > haven't seen previously: > > > > (venv) mailman@debian12:~$ mailman-web compress > > Compressing... Invalid template socialaccount/login_cancelled.html: > Invalid > > block tag on line 7: 'element', expected 'endblock'. Did you forget to > > register or load this tag? > > Invalid template account/verified_email_required.html: Invalid block tag > on > > line 7: 'element', expected 'endblock'. Did you forget to register or > load > > this tag? > > > These templates are part of django_allauth. What is your version of > that? There are backwards incompatible changes in version 0.58. See > > https://github.com/pennersr/django-allauth/blob/main/ChangeLog.rst#backward… (venv) mailman@debian12:~$ pip freeze | grep django-all django-allauth==0.58.0 If you have 0.58 try > ``` > pip install django_allauth\<0.58 ``` > After that, I end up with: (venv) mailman@debian12:~$ pip freeze | grep django-all django-allauth==0.57.0 And then `mailman-web compress` is happy. -- 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, 11 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Thanks Mark! I changed the outgoing.py per cut&paste because I didnt know, whow th patch a python file ... But succeeded: /var/log/mailman3/mailman.log Apr 08 19:08:10 2020 (9234) Master started Apr 08 19:08:12 2020 (9241) bounces runner started. Apr 08 19:08:12 2020 (9263) virgin runner started. Apr 08 19:08:12 2020 (9259) out runner started. Apr 08 19:08:12 2020 (9255) lmtp runner started. Apr 08 19:08:12 2020 (9259) Cannot connect to SMTP server localhost on port 25 [Errno 13] Permission denied: '/var/lib/mailman3/cache/7d/c6/7dc6d1a99a5ecf2b2241d6d0958a2bc704e32238150e5cc273f6779b124bd04f' Apr 08 19:08:12 2020 (9237) archive runner started. .... Checked the ownership .... ls -la: /var/lib/mailman3/cache drwxrwx--- 3 root root 4096 Nov 9 22:27 61 drwxrwx--- 3 root root 4096 Feb 3 17:37 6c drwxrwx--- 3 root root 4096 Nov 12 11:59 71 drwxrwx--- 3 root root 4096 Nov 6 12:01 72 drwxrwx--- 3 root root 4096 Feb 5 21:52 7d drwxrwx--- 3 root root 4096 Feb 5 23:05 8b drwxrwx--- 3 root root 4096 Nov 12 23:41 94 drwxrwx--- 3 root root 4096 Nov 7 08:31 ae drwxrwx--- 3 root root 4096 Nov 12 23:40 fa /var/log/mailman3/mailman.log .... Apr 08 19:08:19 2020 (9259) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 100, in deliver self.decorate(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate decorator.process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 264, in process process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 73, in process for archiver in IListArchiverSet(mlist).archivers: File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__ adapter = self.__adapt__(obj) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__ adapter = hook(self, obj) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter return self.adapter_hook(provided, object, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook result = factory(object) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 600, in __init__ for archiver in config.archivers: File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 260, in archivers archiver = call_name(class_path) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 70, in call_name return named_callable(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/archiving/mhonarc.py", line 46, in __init__ config.archiver.mhonarc.configuration) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 335, in external_configuration cfg_path = str(expand_path(resources, path)) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 80, in expand_path cfg_path = resources.enter_context(path(package, resource + '.cfg')) File "/usr/lib/python3.7/contextlib.py", line 426, in enter_context result = _cm_type.__enter__(cm) File "/usr/lib/python3.7/contextlib.py", line 112, in __enter__ return next(self.gen) File "/usr/lib/python3.7/importlib/resources.py", line 188, in path yield Path(reader.resource_path(resource)) File "<frozen importlib._bootstrap_external>", line 932, in resource_path File "<frozen importlib._bootstrap_external>", line 941, in is_resource File "<frozen importlib._bootstrap_external>", line 95, in _path_isfile File "<frozen importlib._bootstrap_external>", line 87, in _path_is_mode_type File "<frozen importlib._bootstrap_external>", line 81, in _path_stat File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 114, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Apr 08 19:08:19 2020 (9259) SHUNTING: 1586365699.6492867+798bd45a31fb2b8d5fd24a481a3cf95710994bf7 Apr 08 19:08:19 2020 (9259) out runner exiting. Apr 08 19:08:19 2020 (9234) Master watcher caught SIGTERM. Exiting. Apr 08 19:08:19 2020 (9234) Master stopped Changed the ownership for /var/lib/mailman3/cache to list:list and from that point my lists are responding. Same problem occurs before fort he list-directory, which I corrected some days ago. Is the ownship misconfiguration a coincidence or did I made a mistake somewhere?? Thanks for your assistance! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Mittwoch, 8. April 2020 00:23 An: MM3 Users <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 2:40 PM, Wolfgang Bock via Mailman-users wrote: > Yes, I assume that means telnet localhost 25 succeeds. Try the attached patch to mailman/runners/outgoing.py. It should log more about the actual exception. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 20:25:44 CEST schrieb Mark Sapiro: > On 10/13/22 10:55, Eggert Ehmke wrote: > >> It shouldn't have been necessary to apply any patch. The head of the > >> GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > > > > strange, I still had the line with the (not working) > > from mistune.scanner import escape_html, escape_url > > > > maybe because the migration step was not working at that time? > > It should have nothing to do with migrations. The command > ``` > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > ``` > run as the mailman user with your venv active should have set the > content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > to be the same as > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer. > py, but it didn't. I wonder what else didn't get upgraded? Clearly it did do > something because mistune was upgraded. In the meantime I run pip install --upgrade --force-reinstall git+https://gitlab.com/mailman/hyperkitty@master and that installed the correct renderer.py. Should I do this with all packages? > If you run `pip freeze` in your active venv,, what versions do you see > for the things you upgraded? Do they look for example like > ``` > HyperKitty @ > git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a28 > fd7803 ``` Yes that version is installed.

3 years

[MM3-users] Re: Mailman3-Web lots of database queries

by Abhilash Raj

On Thu, Nov 22, 2018, at 2:14 AM, Stefan Tatschner wrote: > On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > > No. This is not normal. This is apparently coming from Django qcluster. > > At least it is qcluster that uses the django_q_ormq table, but these > > repeated queries are not normal, at least I don't see them in the sites > > I administer. > > These calls are normal, since qcluster polls the database at a high > rate: > > https://django-q.readthedocs.io/en/latest/configure.html#poll > > Fortunately this setting can be reduced, but yeah, polling happens > though. So, if you are using Django's ORM to keep the task states in Django Q, this is bound to happen depending on how frequently do you run tasks. In Hyperkitty, we have some minutely tasks, which means the polling is going to be high. You can however, configure Django Q to store the tasks outside of database in a better high-speed in-memory database like Redis for example[1] for queuing the tasks. Other options like MongoDB, Amazon SQS is also available. [1]: https://django-q.readthedocs.io/en/latest/configure.html#redis > > Stefan > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 11. Dezember 2019 um 09:55 Uhr -0800 schrieb Mark Sapiro: >Here's a revised script: [...] >Now we expect to see the hash of each message-id followed by the >message-id followed by the exception for the offending message. Success! This time it crashes with the expected exception. I've attached the shell transcript. As expected, it's a spam message. I've uploaded the offending file here for you to look at: <https://ftp.secretchronicles.org/misc/Q5PQZI4QEE4C42XNZMXESSKDCSZBUT4T> This way I don't risk getting caught by spam filters. I'm going to put that down quickly again, though, I don't want to distribute spam messages. Now that the problem is identified, I'm going to purge it from both database and file system. Thank you for your help. If you need any further information for debugging the problem, please tell me. >As to why you didn't receive owner notices about the held spam, perhaps >they were spam filtered or somehow otherwise lost. Maybe. I'll ensure I update quickly when the new Ubuntu LTS comes out to get that functionality. Installing Mailman not via the repos is not really an option for me; this list is for a hobby project and should run with as low maintenance effort as possible (i.e. automatic updates). Thanks a lot. Marvin -- Blog: https://mg.guelker.eu

5 years, 10 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Dadgar

On Feb 15, 2021, at 10:14 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. >> >> The resulted in a broken web interface. >> >> Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. >> >> Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. >> >> Anyone got a solution to this? > > > From the tracebacks it looks like Django is broken. I would suggest > starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ > aside and create a new venv > > virtualenv /opt/mailman/mm/venv/ > > and then activate it and pip install everything. Ok, that worked. THANK YOU. My lists are back up. The CPUs getting pounded by some failing process is back, though. I’ll post about that separately. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 7 months

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Wed, Jan 31 2018, Mark Sapiro wrote: >> I have verp_delivery_interval = 10 ... > > Which says only every 10th message will be VERPed. You want > verp_delivery_interval = 1 to VERP every message. Hi, Why? The smtp relay host would get much more outgoing messages. With verp_delivery_interval = 10, only 10% of the messages would be personalized. Shouldn't this be enough to detect sooner or later, that a recipient address is no more valid? Or is it important, to detect such failure immediately? > The message does appear in the mail log, but until the issues below are > fixed, even if Mailman receives it, you won't see it. Ok. For now, I could do a grep of the syslog messages of Postfix, for example once per month, to check for DSNs. > They should be processed by Mailman and scored as bounces for the > recipient if recognized and forwarded if not (depending on settings), > but they currently are only stored. Ok. >> The question for me is: does the remote MTA needs a fix (i.e. the >> Message-ID is required by some RFC), or mailman (i.e. a DSN without >> Message-ID should be acceptable)? > > I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. Thanks! That means, that I won't need to teach Postfix to add a Message-ID to the DSNs. :) Kind regards, -- Peter

7 years, 8 months

[MM3-users] Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210530 09:19]: > Mark Sapiro writes: > > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > > > Membership adapter is a Mailman 2 feature that allowed use of an > > > external membership database (such as a corporate LDAP system). I > > > thought it was ported to Mailman 3 but maybe not. > > > Actually, it's not quite that simple. Mailman 2.1 defines a > > MemberAdaptor class, [...]. > > The Mailman 3 analog of this is the IMember interface defined in > > mailman/interfaces/member.py and implemented in mailman/model/member.py > > OK, but for Andi it is "simple" in the sense that he doesn't have an > existing MemberAdapter, so the plan is "Implement the IMember interface". Not sure if this is the right approach, or if it wouldn't be more appropriate to "just" replace the dependency on allauth in postorius, and do all the magic in the frontend only (because that's where people actually subscribe). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands. That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not? Andi

4 years, 4 months

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

On 12/28/21 6:15 PM, William Oliver wrote: > So, I have successfully installed mailman3 and it's working great. > However, the way it works now, if someone goes to the domain website, > he or she will get the mailman page. I'd prefer that it work something > like: > My > www.example.com goes to a home page > lists.example.com goes to the mailman3 page > mail.example.com goes to a roundcube page > > > I'm using nginx I'd asked about this a few weeks ago for a MM3 host running Ngnix with a few virtual domains, one of which runs Roundcubemail as its default. Mark Sapiro suggested the following, and it seems to be working OK. You'll need these lines in the Nginx config file for each virtual host you define. # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff dn

3 years, 9 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marcus Bautze

Hi, Am 07.06.2024 um 06:22 schrieb Mark Sapiro: > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "Thank you, archiver is now starting. Now there's another > problem:". Does this mean messages are being archived in HyperKitty or > are they accumulating in (I think the Debian path is) > /var/lib/mailman/archives/hyperkitty/spool/? They are in /var/lib/mailman3/archives/hyperkitty/spool/, i doesn't find them in the HyperKitty-archives. > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py > and this are the same Keys." To be clear, in mailman-web.py the key is > quoted and in mailman-hyperkitty.cfg it is not. E.g., in > mailman-hyperkitty.cfg > > api_key: Some_key here is the key unquoted: api_key: *** > > and in mailman-web.py > > MAILMAN_ARCHIVER_KEY = 'Some_key' here's the Key quoted: MAILMAN_ARCHIVER_KEY = '***' > > What are your versions for mailman-hyperkitty and HyperKitty? > HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 > and if I recall corectly, at least one Debian package was shipped with > this incompatibility > i found: python3-django-hyperkitty 1.3.7-1 python3-mailman-hyperkitty 1.2.1-1 mailman3-full 3.3.8-2~deb12u1 (no other hyperkitty-related packages) -- Marcus Bautze marcus(a)mbautze.de

1 year, 4 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Wed, Mar 1, 2023 at 6:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/28/23 21:33, Odhiambo Washington wrote: > > > > Now that I have the error message - mail was generated at 0600hrs - what > > should I grep for in mailmanweb.log to ascertain when the cron job > started? > > > You could look in /etc/crontab to see what time the cron.monthly jobs > are run or you could look in syslog for 'cron\.monthly'. > In FreeBSD we have the /var/log/cron. Mar 1 00:00:00 gw /usr/sbin/cron[66206]: (mailman) CMD (/opt/mailman/mm/bin/django-admin runjobs monthly) So the job was started at 00:00, and the email was generated at 06:00: 2023-03-01 06:00:52 1pXCi4-000N2h-2D <= mailman(a)gw.kictanet.or.ke U=mailman P=local S=1466 T="Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly" from <mailman(a)gw.kictanet.or.ke> for mailman That is 6hrs and the lock was still there. Given that my search engine is whoosh and my archive is heading to 3GB, I should probably try setting the value to 10hrs for a start? PS: Is there any documentation (for laymen) on how to set up an alternative search engine for MM3? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Joel Lord

On 11/23/2020 10:48 PM, Mark Sapiro wrote: > On 11/23/20 7:22 PM, Mark Dadgar wrote: >> >> I also believe that it’s common for unsophisticated users to just start marking list emails as spam stop seeing them instead of figuring out how to unsubscribe. Which really sucks for everyone else. > > > Several servers I'm involved with managing are subscribed to Yahoo's > feedback loop (go to https://help.yahoo.com/kb/postmaster and select > "Complaint Feedback Loop"). Reporting list mail as spam is one way to > get quickly removed from a list. However, this is a bit complicated > because the "report spam" button in Yahoo's web mail UI is right next to > the "delete" button, so some reports are accidents. > I've done the same thing, but Yahoo is pretty good at sanitizing their report to make it difficult to impossible to tell who actually needs to get ejected. I added "Sent to %(user_name)s at %(user_address)s" to the footer and while they'd generally get the user_address wiped out, the user_name would generally survive. And because Yahoo's UI is flawed as Mark pointed out, with the delete and spam buttons adjacent, I'd usually give people a couple chances before I'd airlock them. -- Joel Lord

4 years, 10 months

[MM3-users] Re: Problems with shunted Mails

by Stephan Krinetzki

Mark Sapiro wrote: > > One of the list's regular members has no associated address record. I > don't know how this can happen. That doesn't sound good. When something is unknown, that's never good. > You could find the member with mailman shell, e.g. > mailman shell -l list.example.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 list.example.com mailing list > >>> for mbr in m.regular_members.members: > ... if mbr.address is None: > ... mbr.subscriber > ... mbr.user > ... mbr.user.addresses > ... mbr.user.preferred_address > ... Yupp, this returns two entries (or better: User Objects?) > You might be able to fix this with something like > >>> for mbr in m.regular_members.members: > ... if mbr.address is None: > ... mbr.address = mbr.user.preferred_address or > member.user.addresses[0] > ... > >>> commit() This fix didn't worked. It returned a "Index out of bounds" exception. Instead, we have deleted the corresponding entry in the database. It should be possible to find it this way: select * from member where list_id = 'list.lists.example.com' AND address_id IS NULL; After deleting the row, the list works again.

3 years, 5 months

[MM3-users] Re: REST API authorization failed

by Axel Rau

Hi Mark, thanks for your answer. > Am 08.01.2022 um 23:07 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Is the password unquoted in mailman.cfg as > > admin_pass: ??? yes. > > and quoted in settings.py as > > MAILMAN_REST_API_PASS = '???‘ yes. > > Does the `mailman info` command report what you think for REST credentials? yes. > > To you get an appropriate JSON response from > > > wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists <http://localhost:8001/3.1/lists> I used curl: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# curl -v -u restadmin:??? http://localhost:8001/3.1/lists * Trying 127.0.0.1:8001... * Connected to localhost (91.216.35.42) port 8001 (#0) * Server auth using Basic with user 'restadmin' > GET /3.1/lists HTTP/1.1 > Host: localhost:8001 > Authorization: Basic cmVzdGFkbWluOnc2cmtuQXpJZmVRc1o4WnlkMFpBcmNjcm55OA== > User-Agent: curl/7.80.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Server: gunicorn < Date: Sun, 09 Jan 2022 13:51:43 GMT < Connection: close * Authentication problem. Ignoring this. < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" < content-type: application/json < vary: Accept < content-length: 77 < * Closing connection 0 {"title": "401 Unauthorized", "description": "REST API authorization failed“} - - - I see "Server: gunicorn“, does this mean, I must install gunicorn? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' This looks good to me. > > What should I use in user and password?? Does Django use postfix to send the email??? I think you don't need a password and username as long as your postfix is configured to relay local emails without authentication (which it is by default if you installed from distro packages and if you haven't changed the settings). > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió:>> Hi, >> >> >> >> On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: >> > It's ok now, but still I can't make it send the confirmation email>> > >> > This is from mailman.log: >> > >> > >> > [mailman@localhost logs]$ tail -f mailman.log >> > Aug 01 15:59:18 2017 (2327) lmtp runner started. >> > Aug 01 15:59:18 2017 (2333) virgin runner started. >> > Aug 01 15:59:18 2017 (2332) retry runner started. >> > Aug 01 15:59:18 2017 (2330) pipeline runner started. >> > Aug 01 15:59:18 2017 (2325) command runner started. >> > Aug 01 15:59:19 2017 (2328) nntp runner started. >> > Aug 01 15:59:19 2017 (2326) in runner started. >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET >> > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET >> > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200>> > 90 >> > >> > >> > >> > >> > What should I do? >> >> If you are talking about Account confirmation emails, they usually are>> sent out from Django and not Mailman Core itself. >> >> To configure Django you need to edit the `settings.py` file, wherever>> that is one your installation. If you are following the guide mentioned>> at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at>> `mailman-suite/mailman-suite_project/settings.py`. >> >> To configure your Django to send emails, have a look at >> http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required.>> >> That documentation page has pretty much everything you need in order to>> have a running Web Frontend, please go through it and make sure you have>> everything configured. >> >> Finally, the actual emails from Mailing lists are supposed to be handled>> by Core. You need to configure Postorius & Mailman both to communicate.>> The settings are mentioned >> http://docs.mailman3.org/en/latest/config-core.html#configuring-mta >> here. >> >> >> Hope that helps! >> >> > >> > >> > >> > >> > >> > >> > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>)>> > escribió: >> > >> > > On 8/1/17 1:14 PM, Rafael Mora wrote: >> > > > >> > > > Why does it say Address already in use? >> > > >> > > >> > > Because you are starting lm tp runner and it's already running.>> > > >> > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill>> > > any if necessary. Then do 'mailman start'. >> > > >> > > -- >> > > 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 >> > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>> > > >> > -- >> > >> > Atentamente / Best Regards >> > >> > Ing. Rafael Mora >> > _______________________________________________ >> > Mailman-users mailing list >> > mailman-users(a)mailman3.org >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>> >> >> -- >> thanks, >> Abhilash Raj >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> -- > Atentamente / Best Regards > Ing. Rafael Mora -- thanks, Abhilash Raj

8 years, 2 months

[MM3-users] Re: mailman2 import not working

by Abhijith PA

On 29/07/20 10:38 pm, Mark Sapiro wrote: > On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: >> >> ------------------------------------------- >> mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com >> mailman import 21 foo-bar(a)lists.example.com path/to/config.pck >> ------------------------------------------- > > > You don't need to specify an owner for `mailman create`. The owners will > be imported. Ok, noted. >> After everything done tried a test mail, but didn't reach any of the >> inbox though mail is archived. mailman.log says message is accepted >> >> ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> >> Nothing after this. > > It is surprising that no exception/traceback/SHUNTING message(s) are > logged. That would seem to say that Mailman's `out` runner is not running. When I restarted mailman. I got, Jul 29 16:58:21 2020 (14473) SHUNTING: 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d > I think Mailman's var/ directory in the Debian package is > /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? > Is there a .pck file either in shunt/ or in out/? There is many .pck files in /var/lib/mailman3/queue/shunt and /var/lib/mailman3/queue/out. And a lot of .psv files in /var/lib/mailman3/queue/bad > what does `ps -fwwu list` show? There should be a lot of runner > processes. Is there one with argument --runner=out:0:1? > Yes. I can confirm. --a

5 years, 2 months

[MM3-users] Re: MM3 gateway errors and frequent reboot needs

by Brian Carpenter

On 4/19/20 4:38 PM, Mark Sapiro wrote: > On 4/19/20 1:21 PM, hansen(a)rc.org wrote: >> We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? > > We are not seeing an issue like this on either lists.mailman3.org (this > list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) > > What are you seeing in web server logs? > I concur with Mark. I am not seeing any such behavior on none of my MM3 servers. One server we were having similar problems and that was due to a bunch of bad behaving indexing bots (semrush, ahrefbot) hammering the server. So definitely check your web server log. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 5 months

[MM3-users] Re: Held messages page not rendering the message

by Andreas Schamanek

On Sat, 25 Mar 2023, at 17:32, Mark Sapiro wrote: > On 3/25/23 10:01, mike-mailman(a)earth.li wrote: >> >> This seems like maybe its a CSS issue? The class of the held-message-modal >> is "modal fade show" but I am not sure where that is or should be defined >> (or even if I'm looking at completely the wrong thing. >> >> Anyone able to suggest where to look? > > This is bootstrap. See > https://www.w3schools.com/bootstrap/bootstrap_modal.asp > > One possible issue is if you have older bootstrap cached in your browser it > could cause problems. It's unlikely considering you've tried different > browsers, but try clearing your browser cache. I had the exact same issue. As you guessed, Mark, it was related to bootstrap, though not from the browser cache but a mixup of versions served by the server. Also thanks to your research, Mike, I found that my Apache server has Alias /mailman3/static /var/lib/mailman3/web/static /var/lib/mailman3/web/static included a directory "postorius" which served bootstrap.min.css v3.3.5 whereas on my server v4.0.0 is included in python3-django-postorius 1.3.4-2+deb11u1 cd /var/lib/mailman3/web/static mv postorius postorius.bak ln -s /usr/share/python3-django-postorius/static/postorius fixed it for me. There's also a Debian bug report for it: https://bugs.debian.org/1010273 -- -- Andreas :-)

2 years, 6 months

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

by Mark

On 2024-11-14 23:58, Mark Sapiro wrote: > On 11/14/24 13:57, Mark wrote: >> Most message emails (such as the Welcome email) all arrive in French, >> but not the Password Reset email (shown below) - it arrives in >> English. > This message comes from django-allauth. there is a French message > catalog for it. These are in > site-packages/allauth/locale/fr/LC_MESSAGES and should be good. You > can always run `django-admin compilemessages` to update all the .mo > files for all the projects. I can see the French text for the "Password Reset Email" in the django.po file. And running the compilemessages command reports the "django.po" for French is okay and up to date. Should I be recompiling the ".mo" file? cd /opt/mailman/venv/lib/python3.11/site-packages/allauth (venv) ... $ django-admin compilemessagespwd ... File “/opt/mailman/venv/lib/python3.11/site-packages/allauth/locale/fr/LC_MESSAGES/django.po” is already compiled and up to date. ... > However, the issue is probably that Django doesn't get the language > context from the list's preferred language. In fact, the password > reset is not in a list context at all. See > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > for how it determines the language to serve. I'm afraid I don't understand the Django documentation. It seems to be referring to site-wide settings for language, and not "per list".

10 months, 4 weeks

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Now I do have a running instance, too. Seems my error was to do all of the installation via ansible from the start and I wouldn't seen many things failing: - missing wheel - missing gcc The link to the virtualenv user guide seems to be broken. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 7 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > First, we are not silently dropping this message. We are rejecting it at > LMTP time so the sender should be notified. Sure, but you know how users are about being told that their broken MUAs are spewing crap into the Internet. And most of them will get their mail back and will have no idea how to diagnose what the problem is, let alone repair it. > Then the broader question is should we accept all messages with > defects, almost all of which are spam, or only certain defects and > which ones. No (for the reason given), yes, and "it depends". This one I think we can pass through by default. Some lists might want to pass some of the defects that are characteristic of spam. For example, lists for projects developing MUAs in Japan. I regularly got mail with unencoded Japanese in Subject, display names, and occasionally Date at one point in time. > I note that Apple has now released Mail 16 so maybe they've fixed this. > My macs are still on Big Sur, so I can't test this. I have a Mac on Monterey but I haven't switched to it yet, and I'm not a regular user of signed mail and I've never ever used Apple Mail. I'll probably need a bit of handholding to set up a test. Steve

3 years, 5 months

[MM3-users] Re: URLs in moderation messages

by Odhiambo Washington

On Fri, Mar 3, 2023 at 8:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/3/23 01:55, Tim Cutts wrote: > > > > I’ve clearly got something wrong in my configuration, but I can’t work > out what. > > > > All my URLs seem to have the “mailman3” part duplicated, i.e. > > > > Https://example.com/mailman3/mailman3/lists > > > > Is where I have to go to get a list of my mailing lists, which just > doesn’t seem right. > > > > In my settings.py file I have: > > > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com/mailman3/' > > > > If I change the value of this to just https://example.com/ it doesn’t > change this, > > > That setting has nothing to do with your issue. It only determines the > base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the > problem lies. See > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > for a suggested nginx config and > > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… > for Apache. > Are these proposed VirtualHost configs independent of whether one is using gunicorn/mod_wsgi/uwsgi? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: MM2 -> MM3 Migration: listinfo page

by Odhiambo Washington

On Wed, Mar 8, 2023 at 6:16 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/8/23 02:21, Odhiambo Washington wrote: > > > > For those who have migrated from MM2 to MM3, does someone have an > elegantly > > modified listinfo page they are willing to share? > > I remove the MM 2.1 list, but leave the archives. Instead of having any > kind of listinfo page, I put a redirect in Apache for each migrated > list. E.g. > > RedirectMatch permanent /mailman/listinfo/mailman-users(/.*)?$ \ > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > > For archives, I add a note to archives/private/<listname>/index.html. > See https://mail.python.org/pipermail/mailman-users/ for an example. > This works for public archives, but not for private archives because > there is no longer a list to use for private archive authentication. I'd rather not touch the MM2.1 domain because references have been made to it in publications. What I am struggling with is the listinfo.html file: ``` https://lists.kictanet.or.ke/mailman/listinfo/kictanet ``` I am struggling to add reference to the MM3 subscription link user the " Subscribe to KICTANet by filling out the following form:" The HTML code to insert there beats me :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: Hyperkitty error - not archiving

by Odhiambo Washington

On Sat, Jul 26, 2025 at 8:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/25 10:35 AM, Odhiambo Washington via Mailman-users wrote: > > > > I had examined the message using 'mailman qfile', but did not see > anything > > obvious. > > There were 3 files inside the spool/ directory. > > I have just checked again and they are no longer there. > > If the files `disappeared`, they were eventually successfully delivered > to HyperKitty. If you made no changes to mailman-hyperkitty.cfg, there > was probably some transient network issue that caused the initial error. > Most likely. Another thing I have seen, inside /etc/mailman3/ root@list:/etc/mailman3# ls -al total 40 drwxr-xr-x 3 mailman mailman 4096 Jul 26 10:52 . drwxr-xr-x 110 root root 12288 Jul 26 07:17 .. -rw-r--r-- 1 mailman mailman 948 Jul 25 02:48 mailman.cfg -rw-r--r-- 1 mailman mailman 352 Oct 25 2023 mailman-hyperkitty.cfg drwxr-xr-x 2 mailman mailman 4096 Jul 26 03:11 __pycache__ <===== Is the presence of this directory expected? -rw-r--r-- 1 mailman mailman 4971 Jul 26 03:10 settings.py -rw-r--r-- 1 mailman mailman 863 Jul 25 04:14 uwsgi.ini -- 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]

2 months, 2 weeks

[MM3-users] Re: Another interesting error...

by Darren Smith

As for the traceback - I'm assuming it's from postorius, as this happens when attempting to load the held messages in the Postorius UI. On Mon, Apr 23, 2018 at 3:29 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > "It's in Mailman's database in the 'message' table." > > I can see the message table - is there a way to see where it is marked as > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > and path. > > I'm wanting to be able to query for held messages for a given mailing > list, as there are currently over 98,000 entries in the message table. > > -Darren > > > On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/23/2018 01:31 PM, Darren Smith wrote: >> > So it appears that there was a message sent to one of our mailing lists >> > that was put into the held message queue. However, when attempting to >> go to >> > the message to do the moderation, the web page returns and Error 500. >> > >> > Looking in the mailman log, I found this: >> > >> > Apr 23 14:21:02 2018 (17878) REST request handler error: >> > Traceback (most recent call last): >> > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line >> 137, >> > in run >> > self.result = application(self.environ, self.start_response) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> database/transac >> > tion.py", line 50, in wrapper >> > rtn = function(*args, **kws) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/wsgiapp.py" >> > , line 214, in __call__ >> > return super().__call__(environ, start_response) >> > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", >> > line 227 , in __call__ >> > responder(req, resp, **params) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 167, in on_get >> > resource = self._make_collection(request) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in _make_collection >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in <listcomp> >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 157, in _resource_as_dict >> > resource = self._make_resource(request.id) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 100, in _make_resource >> > make_header(decode_header(resource['subject']))) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, >> in >> > make_he ader >> > h.append(s, charset) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, >> in >> > append >> > s = s.decode(input_charset, errors) >> > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: >> > illegal multibyte sequence >> > >> > It LOOKS as if there might be a character in the email somewhere - >> possibly >> > in the subject or sender fields? - that is somehow unexpected. >> >> >> It appears that the Subject: header is RFC 2047 encoded and there is an >> encoded word with charset gb2312 that contains an invalid encoding. >> >> The message is apparently defective, but this kind of defect shouldn't >> cause a 500 error. >> >> I can't tell for sure from the traceback if this is Postorius or some >> other application accessing the REST api. Is it Postorius or something >> else? >> >> >> > I am attempting to find the held message - can someone point me where I >> can >> > go to see the message so that I can see what might be causing the >> problem? >> >> >> It's in Mailman's database in the 'message' table. >> >> -- >> 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 >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 5 months

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 1:31 PM, Mark Sapiro wrote: > On 2/14/21 5:44 AM, Tom Stoddard wrote: >> I'm a list owner who has recently (within the last week) had my lists >> migrated from mailman 2 to mailman 3. The UI that we are using is >> Affinity. > So you should be getting your support from EMWD. > > >> I've reviewed all of the list templates and begun to customize >> some of them. My issue is that I'm receiving messages that don't match >> any of the templates. Here is an example of one that I just received >> this morning. (The x's are inserted by me. The actual message provided >> valid addresses.) >> >> Thexxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. >> >> >> Held Subscriptions: >> User:xxxxxxxxxx@gmail.com >> >> Please attend to this at your earliest convenience. Yeah, the funny thing here Mark is he is not asking for support for the interface. He is wanting to know why isn't there a way for List Owners to modify moderation notices. It had nothing to do with Affinity. BTW - I told this client CLEARLY there was no template for that notification but he was welcome to join the list to ask for the source of it since I did not know. Geez. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: MM3 to MM3 migration

by David Newman

On 1/31/23 2:01 PM, Mark Sapiro wrote: > On 1/31/23 13:34, David Newman wrote: >> >> Is this really as simple as building the new server, creating the >> same lists on the new server, and rsync’ing the archives from the old >> server? If not, how to do the migration? > > > If you want to mirror the entire installation, you can dump the > databases off the old server and import them to the new server. > Depending on the installation, everything may be in one database or > there may be separate ones for mailman core and mailman web. This is a > little tricky because some of the tables have to do with Django stuff. > > To do only selected lists is much more difficult and there are no > scripts that I am aware of. > > HyperKitty can dump a list's archive as a mbox which could then be > used as input to hyperkitty_import on the new server to move archives, > but there are no similar scripts to dump list settings, users, > memberships, etc. in a format that can be imported. Thanks for this. Would I need to create the lists first on the new server before restoring databases and running hyperkitty_import? Also, I'm unclear about there not being scripts for settings, users, etc. –– isn't that stuff in the mailman database? Thanks! dn

2 years, 8 months

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Ugnius S

Hi, Mark. Thank You for trying to help me. I do not remember how exactly I installed mailman or by apt-get or: $ sudo pip3 install mailman ---I think, have tried this way, but it already was installed. ~/mailman-suite$ mailman info GNU Mailman 3.2.2 (La Villa Strangiato) Python 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] config file: /home/user/mailman-suite/mailman.cfg db url: sqlite:////home/user/mailman-suite/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:Rest_password MTA works correctly. Yes, I understand the error is very strange, but this exactly happens when I add footer custom template to list's regular message via web interface. "telnet loclhost 25" answers correctly. Messages about new members adding and new list creating works and reach the recipients. But Mailman for some strange reasons could not to sent messages from member to other list's members. And nothing to do more: it is enough to delete template and mailman starts send new messages correctly. One remark all messages during with customs template was active remain somewhere in between and do not go out even if template is deleted. I can't even imagine how to debug that. I have noticed that by experience - method to check does mailman work after every small update. This system is so easy to make not working, and then is so hard to understand what did happen. It would be good to read about working example how to setup, and which moments are important. There are many places documented about separate packages, but not full example. I have found one here https://lab.uberspace.de/guide_mailman-3.html, but here part of steps seems are not written as well. For example uwsgi ini and pre required environment. It could happen that for author these steps were trivial, but for person from side some small explanations are very important to understand whole picture of setup and why small parameters where set exactly that way. Of course I am very thankful for authors of that example, because that helped me as well. 2019-08-23, pn, 20:28 Mark Sapiro <mark(a)msapiro.net> rašė: > On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > > I have read documentation, but still have stupid questions, could You > please help, because I can't make it working. I do not understand something > important. I have no experience with python at all. I have mailman 3, > python 3.5 in my debian OS system, and additional packages like uwsgi and > ect. using > https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… > about till chapter 6. I understand mailman suite has hyperkitty already. > But I am not sure about: > > > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python > manage.py runserver - it runs. In installed it under dedicated OS user home > and fonfigured to run. > > I can create lists, event add lists to hyperkitty page using: > $django-admin runjob new_lists_from_mailman list server sends messages to > list members as well. But nothing happens more. No emails come to > hyperkitty, arciver log 0 size. > > $ python manage.py runjobs -l shows the lists of the jobs, so seems > nothing to add. > > > > How exactly did you install Mailman? The document you reference gives > alternatives. You don't say exactly what you did. > > > > 2. If I (using Postorius web interface) add footer template to my list > under regular message, something strange happens. Mailman stops to send > messages for list members. No any entries in the logs. Just Mailman log > writes: "unable to connect localhost port 25" and no more explanation. If > I delete list's footer template (web interface), mailman starts working > again. What is bad here? How to add custom footer? In mailman 2 if was > working so good and was easy to setup. > > > It appears that no MTA is listening on localhost port 25. Is your MTA > even running? It is extremely unlikely that this has anything to do with > adding a termplate in Postorius. > > You might be better off installing Debian's 'mailman3-full' package > < > https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su… > >. > > -- > 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/ >

6 years, 1 month

[MM3-users] Re: Memory footprint

by Richard Shetron

some systems also support the sar command (system activity report). If you have it read the manpages to see all the options as there are many. When looking for performance issues/problems that aren't real easy to find I like to just let 'vmstat 5' run in a window and take a look occasionally, particularly when things seem slow. I prefer the 5 second readings to see more about general trends. On 4/11/2017 8:33 PM, Mark Sapiro wrote: > On 04/10/2017 02:25 PM, David Krantz wrote: >> Hi. >> >> Now running mailman 3 I am a bit surprised that the memory footprint >> is so large. I count to 13 processes with each a virtual space of >> 160-250MB and a reserved space of about 50MB each. Not much, but quite >> much to run on smaller cloud instances which generally have limited >> memory. This is (a lot) more than the corresponding postgres >> installation uses, >> >> Is this normal? > > > Those numbers seem "normal" but you really have to look deeper to > understand if you just have a bunch of processes sitting in memory > because the memory is available and nothing else wants it, or if there's > real memory contention going on. > > The article at <https://wiki.list.org/x/4030711>, while written about > Mailman 2.1, has some general information which may be of interest. > >

8 years, 6 months

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Ludwig Grandpré

> but apparently dpkg wants to > create databases for Mailman and Mailman Web. During the installation process dpkg creates not only a database and a database user with approriate permissions, but also many tables. Dpkg allows to skip database configuration. Is there routine or skript to create database, database user and all required tables after the installation process has finished? Best regards, Markus On 31.10.22 18:52, Mark Sapiro wrote: > On 10/31/22 07:04, Markus Ludwig Grandpré wrote: >> Dear Mailman3 list, >> >> I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system >> with a remote Postgres database server. During the installation >> process dpkg is asking for the DBA password that our DBA team would >> not provide to me. So what can I do? > > > This is really a question for Debian, but apparently dpkg wants to > create databases for Mailman and Mailman Web. You will need to get your > DBA team to create these databases (probably named `mailman` and > `mailmanweb`) and a Mailman user (probably `list`) with all access to > these databases and probably manually configure the `[database]` section > of mailman.cfg and `DATABASES` on Django's settings > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

2 years, 11 months

[MM3-users] Re: Importing mbox file into MM3

by Mark

On 2023-06-23 12:19, Mark Sapiro wrote: > On 6/22/23 7:00 PM, Mark wrote: >> Hi All >> >> I'm trying to import a large mbox file from a MM2 list into a new list >> on MM3. >> >> The new MM3 list has 3 test emails in its archive. >> ... >> The import or rebuild has failed as it's just rebuilding the existing >> archive of the 3 test messages. >> >> What am I doing wrong? > > > Presumably, the 3 test emails are newer than the messages in the > archive .mbox. The default for hyperkitty_import is to not import > messages older than the newest message in the existing archive. > You need to specify something like `--since='1970-01-01'` on the > hyperkitty_import command to import these older messages. > Thanks Mark. That looks more promising. It's been chugging away now for 3 hours with only 4 errors reported so far. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import --since='1970-01-01' -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox "Failed adding message ......(a)mail.yahoo.com>: A string literal cannot contain NUL (0x00) characters". The mbox file is about 3 GB. The errors look like they're for messages that aren't kosher (maybe misplaced "From"s in replies). I can live with a few missing messages. Back to watching the spinning pipe. Chug chug. Cheers Mark

2 years, 3 months

[MM3-users] Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Simon Liebold

Am 28.05.2017 um 22:24 schrieb Mark Sapiro: > 'Delete this message' is in the 'message' view. "Delete this thread" is > in the 'thread' view. Now found the message view. Thanks. > HyperKitty requires Django<1.11. The comment in the requirements in > setup.py implies this is only a django-haystack requirement > > "Django>=1.8", > # Don't upgrade to 1.11 until django-haystack supports it: > # https://github.com/django-haystack/django-haystack/pull/1499 > "Django<1.11", > > but since it works for me with Django 1.10, you might want to try that. OK, I was still running an RC version. Silly me. > In particular, this looks like Django 1.11 bug > <https://code.djangoproject.com/ticket/27975>. Which was closed in the release version that I initially upgraded to (1.11.1). Now, I get to see the confirmation view and upon confirming I see these (luckily different) errors like below (same with Django 1.10): Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") True, this table doesn't exist in the database. It isn't created by python manage.py migrate. The error is served with HTTP-200. No stack trace in mailmansuite.log. Headscratching: Simon

8 years, 4 months

[MM3-users] Re: multiple sites on a mailman3 server question

by William Oliver

On Tue, 2021-12-28 at 18:23 -0800, David Newman wrote: > > > > [snip] > > I'm using nginx > I'd asked about this a few weeks ago for a MM3 host running Ngnix > with a > few virtual domains, one of which runs Roundcubemail as its default. > > Mark Sapiro suggested the following, and it seems to be working OK. > You'll need these lines in the Nginx config file for each virtual > host > you define. > > # begin mailman3 stuff > > location /static/ { > alias /opt/mailman/web/static/; > } > [snip] No joy. This just makes it kind of work as the mailman interface when it gets rewritten. My problem is that the url is getting referred to domainname/mailman3/lists even when I don't want it to. Adding these changes just (partially) loads the mailman3 interface when it gets rewritten. What I'm trying to figure out is where uwsgi yanks control from nginx and does the rewriting. Pulling that proxypass stuff out will stop mailman3 from coming up, and adding it allows mailman3 to show its interface, but the address gets referred regardless. Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell nginx not to push it to port 8000. But I don't see where nginx is getting told to go to 8000 in the www.domain.com section. billo

3 years, 9 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Nelson Strother

Well, this is using the default libsqlite 3.34.1 . One improvement is to use write-ahead logging: mailman@localhost:~$ sqlite3 /var/tmp/mailman/data/mailman.db SQLite version 3.34.1 2021-01-20 14:10:07 Enter ".help" for usage hints. sqlite> PRAGMA journal_mode = WAL; wal sqlite> This setting is persistent, and based on a small sample this seems to dramatically speed up the completion of root@localhost:~# systemctl stop mailman ## consumes <2 minutes with journal_mode = WAL; root@localhost:~# ## instead of up to 20 minutes with the default journal_mode = delete But this does not make a big change the completion time for: root@localhost:~# systemctl start mailman Since there is no point in busy waiting when running on a processor with only one core (as this virtual server), the next setting that I would like to try is change the sqlite busy_timeout from the default of none to 1 or 2 seconds, e.g.: sqlite> PRAGMA busy_timeout = 2000; 2000 sqlite> However, this setting is not persistent, and thus needs to be applied to each connection (i.e. tens of database connections are made during `systemctl start mailman`). I have not yet found where to insert this directive in mailman's database wrapper for SQLite. Might someone who has read more of the source be able to offer me a clue? On 6/8/23 15:47, Mark Sapiro wrote: > I would look to your database manager for the issue.

2 years, 4 months

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

by Helio Loureiro

Hi, And here we have it: (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... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK tl;dr: it was the database. So the django was spitting out absolutely horrible traceback errors to diagnose the issue. I modified the code to print the query and then raise exception (what is expected from an error, not only "I just failed, sorry do whatever"). Then I got the query and tried manually. And it failed. (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...Error running query: b'*ALTER** TABLE `account_emailaddress` DROP INDEX `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) [...] (venv) mailman@new-server ~ (v3.3.9) [0|1]> 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]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2013 (HY000): Lost connection to server during query MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2006 (HY000): Server has gone away No connection. Trying to reconnect... Connection id: 32 Current database: mailman3web ERROR 2013 (HY000): Lost connection to server during query So I looked to the mysql error logs and searched Internet for the issue. It recommended to run a "mysql_upgrade", which failed with another error: root@seliius26224 /e/mailman3# mysql_upgrade -u root --force Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.engine_cost Error : Table 'mysql.engine_cost' doesn't exist status : Operation failed mysql.event OK mysql.func OK [...] sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1932 (42S02) at line 477: Table 'mysql.innodb_index_stats' doesn't exist in engine FATAL ERROR: Upgrade failed I searched again the Internet and found a fix: https://stackoverflow.com/questions/37856155/mysql-upgrade-failed-innodb-ta… Now migration is progressing. Thanks for all the patience and support. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Tue, 19 Dec 2023 at 15:23, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/19/23 3:11 AM, Helio Loureiro wrote: > > Hi, > > > > No luck :( > > > > (venv) mailman@new-server ~ (v3.3.9)> *pip install -U > > django-allauth==0.58.0* > > You need to install django-allauth<0.58.0 as in > ``` > 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, 9 months

[MM3-users] Re: How to delete large numbers of held messages

by lists＠g1fef.co.uk

Mark Sapiro wrote: > On 4/21/22 14:56, Chris via Mailman-users wrote: > > We had a mail loop on one of our lists and ended up with over 51k messages in pending (held due to post not form a list member) > > Trying to delete them from the web UI will take forever, as the largest pagination you can view is 200 at a time. > > Tried to delete them from the Python interactive shell, but it looks like the API times out after a while. > > Is there another way to delete all these unwanted held posts? > > I suggest the following in mailman shell > $ bin/mailman shell -l list.example.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 list.example.com mailing list > >>> from mailman.app.moderator import handle_message > >>> requestdb = IListRequests(m) > >>> for id, type in requestdb.held_requests: > ... if type == RequestType.held_message: > ... handle_message(m, id, Action.discard) > ... > >>> commit() Thanks for the reply, unfortunately that gives an error: Traceback (most recent call last): File "<console>", line 1, in <module> TypeError: cannot unpack non-iterable _Request object

3 years, 5 months

[MM3-users] Re: Templates do not work

by Eggert Ehmke

It seems my apache vhost settings are messed up. To access the postorius page, I have to use URLs like this: https://lists.[1]tld_/mailman3/mailman3/lists/_ That does not look right, and maybe is the cause of my problem. There are very few guides to set up apache virtual hosts with mailman virtualenv installation. Any hint? Am Donnerstag, 28. April 2022, 19:02:42 CEST schrieb Mark Sapiro: > On 4/28/22 02:50, Eggert Ehmke wrote: > > I created some templates in Postorius to get > > personalized notifications when there are > > moderator requests. The notifications I get seem to > > be the standard texts. When I look into mailman/ > > mm/var/templates > > the directory is empty. Nevertheless, the templates I > > create in Postorius seem to be stored (where?), they > > just do not work. > > As Steve said the templates are stored in the database. > > I suspect the issue is and incorrect value for > `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to > construct the URI to retrieve the template. The URI is stored in the > `template` table in the database. It is normally just `http(s)://host.name/` > > If this is the issue, after correcting the setting and restarting the > web service, you will need to delete and re-enter the template in > Postorius to correct the `template` table entry. -------- [1] https://lists.ftv-spandau.de/mailman3/mailman3/lists/

3 years, 5 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/5/23 01:13, Odhiambo Washington wrote: > > > > So in my case, I should at least increase the value of > > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? > In the last episode, I did set: HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE = 3600 However, the same error has reared its head again. > It probably isn't even set in your case and defaults to 900 if it isn't > set. Yes, you can set it to a larger value. If your archive search > engine is woosh and your archive is even moderately large, 1800 probably > isn't nearly enough. There was no indication of timing in your OP, but > you should determine when that cron job started and when the error was > reported. Now that I have the error message - mail was generated at 0600hrs - what should I grep for in mailmanweb.log to ascertain when the cron job started? > The difference is the absolute minimum you should set for > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin > to that. > ..so as to get this difference, that I need to set as the _ bsolute minimum_, with some margin? Thanks in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Thomas Ward

Is there a way to oerhaps custom-plugin my way through to set this up as an integration into Core? And specify the custom handler process or such to allow that integration? I see that there are ways to code plugins into existence so it may be a custom-processor plugin or such for this purpose. Replies to threads would still have the corresponding RFC headers and such for replies and would properly get Hyperkitty to index threads properly, but subject munging on this case might be something I would custom-code into the system if that's doable. Thomas On 10/18/23 18:03, Mark Sapiro wrote: > On 10/18/23 14:54, Thomas Ward via Mailman-users wrote: >> >> Is there any way to have Subject based thread tagging, etc.? I ask >> this only because we're trying to thread items for easy ID in a >> system right now that does thread ID tagging in the subject line >> (i.e. "[Test-0000004] Something" and "Re: [Test-0000004] Something" >> are identified as the same thread, but a brand new message >> "Something" would end up as "[Test-0000005] Something" in the chain >> if it was a new message.) > > > It is not possible with the current design. > > The issue is the tagging is done by Mailman core and Mailman core > knows nothing about threads. >

1 year, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Why isn't it sending emails? What do you think? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' > > > This looks good to me. > > > What should I use in user and password?? Does Django use postfix to send > the email??? > > > I think you don't need a password and username as long as your postfix is > configured to relay local emails without authentication (which it is by > default if you installed from distro packages and if you haven't changed > the settings). > > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) > escribió: > > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > 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 > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > > > -- > thanks, > Abhilash Raj > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I thought I could not configure Mailman, but with Kyle and Mark help and support I could. So, I don't want to be demeaning as you also said but maybe we could try, maybe you can also help, if it turns too complicated I will use mailchimp, but let me try before givin' up, don't you think?? El sáb., 22 jul. 2017 a las 9:01, Simon Hanna (<simon.hanna(a)serve-me.info>) escribió: > On 07/22/2017 03:46 AM, Rafael Mora wrote: > > Can I use it for mailing lists? like MailChimp? > > > > El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > >> On 07/21/2017 06:07 PM, Rafael Mora wrote: > >>> I want to use Mailman to send emails to our customers. > I would highly recommend using a service like MailChimp. > MailChimp has a decent free tier and if you are above that, > I'm not sure if you can handle configuring Postfix the right way. > It's not my intention to be demeaning or anything, but it sounds like > that would be a little too complicated for you... > (I wouldn't want to manage a Mailserver in charge of tens of thousands > of emails per month) > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 2 months

[MM3-users] Re: unwanted chunked delivery

by mm3-omf＠sh.werbittewas.de

Am 07.01.22 um 21:33 schrieb Mark Sapiro: >> nevertheless, we've tried to set it to a high value, but even this >> doesn't change anything in behaviour. > > Right, because chunking isn't arbitrary. Chunking is done by recipient > domain. The addresses are placed in `buckets` by TLD. All `.com` goes in > one bucket; `.net` and `.org` in another; `.edu`, `.us` and `.ca` in a > third, and all the rest in a fourth. thanks for this info. > My question is why is this important to you? See the FAQ article at well, most of these 81 users are handled on our local system, but with different domains and TLDs (mainly 80% .de and 20% .org/.net). therefore we don't see any benefit in chunking here, especially in case 50% of the chunks are unused (.com,.edu/.us/.ca). to simplify our logging-analysis in case of problems it seems beeter for us to have one entry for delivery to list-server and one entry for delivery from there. > https://wiki.list.org/x/4030582 (which is for Mailman 2.1 so it talks > about SMTP_MAX_RCPTS which is what max_recipients used to be called) > which suggests a much smaller number. I understand, why chunking may have benefits perhaps in most situations, so it's set as default, but it would be great, to have the possibility to disable this without patching code, which might get overwritten with an update. omf.

3 years, 9 months

[MM3-users] Re: more about spanish translations

by Guillermo Hernandez (Oldno7)

On 19/2/21 18:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 19/2/21 18:26, Mark Sapiro wrote: >> On 2/19/21 5:09 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> I would like to translate it all, but as said, I cannot find where >>> to do >>> it. I wonder if it's comes from another package as allauth or something >>> like this. >> >> Yes, it does come from allauth, specifically >> allauth/templates/account/email/email_confirmation_message.txt. >> >> The Spanish allauth message catalog is at >> <https://github.com/pennersr/django-allauth/tree/master/allauth/locale/es/LC…>. >> >> I suppose you could submit a pull request to update it. >> >> Or you could just update your local file in your installation. >> > I will do both: first translate locally. Test it, and then see if I > can share it with the rest of the people (and then I will not have to > worry to maintain it when next upgrades come) I went first with the translation in github and the pull request. Let's see if it's approved and then how to upgrade locally. > > Thanks a lot, as always, Mark. > _______________________________________________ > 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/ >

4 years, 7 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > > total 104 > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > > > I imagined I needed an executable. > > > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass > > > Those are headers for compiling some sass. Possibly you actually have a > `sassc` installed in which case you may need > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > This change makes the error I was getting to go away. However, I cannot login to manage lists, even after restarting mailman. The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 5 months

[MM3-users] Re: REST API authorization failed

by tlhackque

On 10-Jan-22 13:30, Mark Sapiro wrote: > On 1/10/22 1:58 AM, Axel Rau wrote: >>> >>> Anyway, the above is saying that restadmin:??? doesn't match what's >>> configured in Mailman core and reported by `mailman info`. Please >>> check carefully that these are the same in both mailman.cfg >>> admin_pass and settings MAILMAN_REST_API_PASS. >> >> Yes, again with password disclosed: >> - - - > ... >> (mailman_33) [root@lists5 /usr/local/mailman3]# grep admin >> var/etc/mailman.cfg >> admin_user: restadmin >> admin_pass: restpass > > Does `mailman info` show the same password? A common issue that may (or may not) be in play here is leading/trailing whitespace and/or non-spacing control characters. It may be worth making the output (& input) use quotes & escaping, where the input should accept non-spacing controls, leading/trailing whitespace, and non-traditional interior whitespace (e.g. nbsp, numsp, NoBreak, tab) only in escaped form. By escaped form, I mean one or more formats like HTML's  , or Python's at https://python-reference.readthedocs.io/en/latest/docs/str/escapes.html When dealing with user quantities, if it looks like a space, it should be a space. And if you can't see it, it shouldn't be there (using escapes to make the invisible visible is fine). ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: "Unsubscribe all" button

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/20/22 17:32, Philippe B wrote: > > Would it be possible to add a confirmation screen after you click > > on it? Like: WARNING! Clicking "Confirm" will empty the list of > > all its existing members, regardless of what was entered on the > > previous screen. That operation cannot be reversed. Are you > > absolutely sure that you want no one to be on your list anymore? > > There is a confirmation screen although it is not as strongly worded as > you suggest. I'll go check the issue, but let me say I think a confirmation screen is bad UI here. People who know what they're doing shouldn't have to pay the price of a confirmation screen. I know of at least two universities where they "unsubscribe all" from thousands of class mailing lists every term. Of course they automate that pretty quickly when they get to thousands, but it seems plausible to me that such lists for groups that regularly turn over (nearly) 100% of subscribers are a reasonably common use case. Instead, there should be a check for selected users, either disabling the "unsubscribe all" button itself (if we decide to implement more Javascript in the UI) or presenting the confirmation screen if there are any selected users. Also, at least for native speakers, "Unsubscribe everyone" will probably be a better label for the button.

2 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Postfix is listening on 127.0.0.1:25 is it ok? or should listen on 0.0.0.0:25?? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' > > > This looks good to me. > > > What should I use in user and password?? Does Django use postfix to send > the email??? > > > I think you don't need a password and username as long as your postfix is > configured to relay local emails without authentication (which it is by > default if you installed from distro packages and if you haven't changed > the settings). > > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) > escribió: > > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > 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 > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > > > -- > thanks, > Abhilash Raj > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 2 months

[MM3-users] Re: SpamAssassin and clamav?

by Jeremy Stanley

On 2024-03-15 18:50:32 -0700 (-0700), Marisa Giancarla via Mailman-users wrote: > On 3/15/24 18:40, Mark Sapiro wrote: > > On 3/15/24 17:52, Marisa Giancarla via Mailman-users wrote: > > > Is there a way to have mm3 use SpamAssassin and/or clamav? > > > Marisa > > > > It would require custom code modification to invoke SpamAssassin > > and/or ClamAV from mailman. It is much better to integrate these > > in the MTA. > > Ok sounds good... A big reason this is the preferred approach is that your MTA, if appropriately configured, can scan incoming messages before deciding whether to accept or reject them into its delivery queue. For messages rejected at receipt, this means legitimate senders whose messages were incorrectly misclassified get useful error messages in the NDR generated by their own mail provider, while spoofed spam and malware doesn't generate backscatter to unwilling victims and put your own server at risk of getting listed as a spam source. If Mailman were in charge of checking for spam or malware, its only options would be to silently drop offending messages (providing no feedback to senders of misclassified messages) or reject them (causing your MTA to generate an NDR which often times ends up either part of a coordinated attack against some victim organization or sitting undeliverable in the queue because that address is at an unreachable domain). These are obviously undesirable, even actively harmful, results. -- Jeremy Stanley

1 year, 6 months

[MM3-users] Re: Google Summer of Docs

by Abhilash Raj

On Sun, Mar 24, 2019, at 11:58 PM, Terri Oda wrote: > > > On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" > <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >Ralph Seichter writes: > > > * Mark Sapiro: > > > > >> > If you post an issue at > ><https://gitlab.com/mailman/mailman/issues>, > > > > one of our GSOC aspirants may pick it up. > > > > > > Done, although I wonder if any GSOC participant would want to write > > > documentation instead of code... ;-) > > > >For their actual, Google-supported, project, Google explicitly > >excludes documentation. > > > > They do for Google Summer of **Code** but they've just announced Google > Summer of **Docs** which sounds really neat and we might want to > participate. They are calling it Season of Docs, happening in winter I think Sept-Dec AFAIK. Yep, we should participate in that, I sent out an email earlier about this too. > > (It's my personal opinion that our docs have really suffered since I > finished my PhD and stopped using them as a warmup exercise when I was > procrastinating on writing my thesis. *grin*) > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 6 months

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

by Odhiambo Washington

On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 01:19, Odhiambo Washington wrote: > > Apart from all the defaults in settings.py (derived from gitlab), I also > > have this line: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > > Before the New Year releases of MM3, I used to get errors written to this > > file. > > Not anymore after I updated to the New Year releases. > > Another thing that I have realized is that prior to the New Year > releases, > > I would get an error logged to that file and also mailed to me. > > I don't think that I have changed anything in settings,py related to > > logging. > > > 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? When I upgraded, the command I ran was: pip install --upgrade --force mailman mailmanclient postorius hyperkitty mailman-hyperkitty django-mailman3 And how do I find out what is suppressing the logging for the social accounts? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 5:39 PM, Mark Sapiro wrote: > On 10/21/20 12:14 PM, Brian Carpenter wrote: >> >> Well I can't dictate that to my list owners and there is no confirm >> token sent with the moderation notice. Why include this option in >> Postorius when it can't be properly handled? > > Postorius is still a work in progress. The unsubscription policies are > in core and are exposed in Postorius. Certainly the ability to moderate > an unsubscription should be in Postorius, but it isn't yet. We are an > all volunteer project and there aren't that many of us, and perhaps I'm > overreacting, but the tone of some of your recent posts seems a bit > demanding. I apologize. I didn't think I was coming across demanding but I am somewhat exasperated at some of these issues. I have a list owner who is now going to get a moderated request notice everyday that he can't do anything about it. But my question still remains: why is this option in Postorius when it can't be handled properly? Surely the option can be easily removed, right? Is the ability to list (via the pending moderation notices tab) and handle (as in the List owner can decide a moderation response) an unsubscribe moderation request there in Mailman core so that I can properly address it via Affinity? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Abhilash Raj

On 12/14/22 03:31, Mark Sapiro wrote: > On 12/13/22 10:38, Dan Caballero wrote: >> Hi Mark, >> >> I ran the commands and it took about 35 seconds for the loop to run. >> >> Here's the result. >> >>>>> count >> 4168 > > > So that's at least part of the issue. How does 35 seconds compare to the > length of time to process one moderated message through Postorius? > It seems it has to do with in-efficient lookup of the actual entry in the pendings table which needs to be purged after handling a held message. It scales linearly with how many entries are there in pendedkeyvalue and pendings tables. I was actually browsing through the perf metrics on mail.python.org and found the slowest API response from Core is handling held messages and spent some time last night trying to improve it [1]. The linked MR should significantly reduce the time, although there is more that can be done to make it even better. I haven't had a chance to benchmark my solution yet, but I am hoping it will reduce the latency quite significantly. I'll report on the linked issue [2] after deploying [1] on m.p.o. how much it helped. [1]: https://gitlab.com/mailman/mailman/-/merge_requests/1068 [2]: https://gitlab.com/mailman/mailman/-/issues/1045 -- thanks, Abhilash Raj (maxking)

2 years, 10 months

[MM3-users] Re: New domain cannot set set host

by Alain D D Williams

On Thu, Nov 28, 2024 at 01:04:13PM -0800, Mark Sapiro wrote: > > I did not see this y/day and created the entry in table django_site using SQL. > > This might be the cause of the other problems that we have been talking about. > > > It's not likely that this is the cause. It is fixed - the mail list works. I had forgotten to put the reverse proxy into the Apache config -- this is what led to the many, rapid retries. I had a problem for a while in the nothing to one particular list was sent to users. This had several users who's delivery status was 'disabled' (correctly, as on the old instance). If was only after a lot of fiddling (trying to delete from the list) that it started to work for the others. There are still rough edges, eg trying to delete a list member gives a server error. In /var/log/mailman3/mailman.log I see a 404: "DELETE /3.1/lists/chat.bray.phcomp.co.uk/member/a.chentouf(a)hotmail.com HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.5" I am not to worried about that today, will look at it in the future. Thanks for your help -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

10 months, 2 weeks

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

`mailman qfile` on the 5 pck files that were in the /out directory looked OK, although I am not sure if I should have looked at something specific. The bak file disappeared as soon as I stopped mailman. When I started mailman again the name of the bak file had changed, and it changed every time I listed the directory.After stopping and starting mailman once more it didn't appear anymore. There are also 6 files in the shunt directory. I don't know what this directory is used for. For now I have disabled the hourly jobs.I will rebuild the search index for each mailinglist separately since the update_index was apparently killed before it finished. Best Regards,Eric On Sunday, December 13, 2020, 06:18:21 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. > This is weird because other mails have been distributed. > The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried. > webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" > <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" > This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer. Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried. I would stop Mailman and move that one .pck or .bak file out of Mailman's var/queue/out/ directory and then start mailman. You can then examine the queue entry with `mailman qfile` and maybe see what the issue is. > 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. OK. > 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? > mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings /opt/mailman/venv/bin/django-admin runjobs --list will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists. -- 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/

4 years, 10 months

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

by Odhiambo Washington

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. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years

Search results for query "sapiro"