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

[MM3-users] Re: anomalous behavior

by Donato Molino

On Saturday 05 October 2024, alle 08:59, Mark Sapiro wrote: > On 10/5/24 04:14, donato(a)molino.it wrote: > > Hi, > > I installed mailman-full on debian 12. > > How? Did you follow > https://docs.mailman3.org/en/latest/install/virtualenv.html or did you > install the Debian packages. If the latter, please see > https://wiki.list.org/x/12812344 Ok you're right, I'll try to contact the debian developers. In any case, I will answer your questions below > > > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > > I have three MLs: > > 1) example(a)example.com > > 2) test(a)example.com > > 3) hello(a)example.com > > > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > > The configurations are identical for all 3: > > > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > > I also enabled all debugging in mailman.cfg. > > But everything is fine > > What's in the MTA log? Does list 1 have any non-digest members with delivery > enabled > `mailman members --regular --nomail enabled example(a)example.com` No all members have regular enabled no digest. MTA log accept the message: (relay=127.0.0.1[127.0.0.1]:8024 - status=sent (250 Ok)) then HyperKitty archived message, then smtp log show the message above but does not send to recipients. > > In addition to the above in smtp.log, I would expect to see entries similar > to the following for your post to this list. me too but nothing. All other list with the same configuration are perfect. I tried also delete an recreate the list but nothing. All the lists are no moderate. in any case thank you for the work you do for the Mailman community. Donato > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 > seconds > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 > seconds > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes > ``` > (the delay between 11:15:02 and 15:22:57 above is the time between arrival > and held message approval) > > Do you see things like that? > > -- > 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 donato(a)molino.it

9 months, 4 weeks

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Dadgar

On Nov 10, 2020, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> The downside to this is that you lose automated bounce processing, of course. > > > You don't lose bounce processing. It just becomes a bit less reliable. > The VERPed envelope sender says exactly what address the message was > sent to. Without this information, Mailman (actually flufl.bounce > <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse > the returned bounce message to determine the bouncing address. There are > many MTAs that do not send RFC 1894 compliant DSNs and we have several > heuristic recognizers to try to parse these, but they can fail. Brian specified: verp_personalized_deliveries: no Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 8 months

[MM3-users] Re: Time Zone Issue in Postorius

by Henrik Rasmussen

> -----Oprindelig meddelelse----- > Fra: Mark Sapiro <mark(a)msapiro.net> > Sendt: 8. februar 2022 07:48 > Til: mailman-users(a)mailman3.org > Emne: [MM3-users] Re: Time Zone Issue in Postorius > > It should be TIME_ZONE = 'UTC' > > Times passed from Mailman core are naive times, I.e. they don't have > time zone info, but they are in UTC. Thus for Django to get the correct > time with time zone you need USE_TZ = True (without that, Django will > throw an exception about naive times) and the TIME_ZONE to apply is UTC. As https://stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-dja… seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), to make sure, am I right to understand it as for Mailman, Danish time should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? /Henrik Rasmussen

3 years, 5 months

[MM3-users] Re: mailman-full question

by Dave McGuire

On 9/25/22 13:34, Mark Sapiro wrote: >> - to configure the db in venv i would use mailman-web migrate - this >> works fine - but mailman-full install does not seem to include >> mailman-web >> or mailman3-web - the mailman info cmd works fine - do i need to >> also install mailman-web? i had thought the mailman-full included all >> components > > I'm not sure what it's called in the Debian/Ubuntu mailman-full package, > but the `mailman-web` command installed by `pip install mailman-web` is > the Django admin command, possibly called `django-admin` or `manage.py` > in the mailman-full package. In my (old) Ubuntu package installation, which I got locked into before I realized how awful that was going to be, mailman-web should be symlinked to /usr/share/mailman3-web/manage.py but isn't. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 years, 10 months

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Bill Oliver

On Mon, 2024-10-28 at 21:08 -0700, Mark Sapiro wrote: > [ > [snip] > es. See the last part of the section at > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… > > where it says in part `And, create the > /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: > ...` > > > I found a template here: > > > > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman- > > hyperkitty.cfg > > > > > > Do I need to copy and paste that in my installation? > > > It, or something as mentioned in the above doc needs to be at the > location defined in the `configuration:` setting in the > `[archiver.hyperkitty]` section of mailman.cfg > > -- Hah! If it were a snake it woulda bit me. I can't believe I scanned right over it. Thanks! billo

9 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

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, 7 months

[MM3-users] Re: Tracking from gravatar

by Abhilash Raj

On Mon, Feb 18, 2019, at 7:16 PM, worik wrote: > On 15/02/19 3:51 PM, Mark Sapiro wrote: > > You can disable them by setting > > > > GRAVATAR_SECURE_URL = '' > > > > in your local settings. See > > <https://github.com/twaddington/django-gravatar> > > Where do I make that setting? There is nothing like it in any of my files. This should go in your Django's settings.py (or settings_local.py) depending on how you installed Mailman. > Worik > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > 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, 5 months

[MM3-users] Re: Welcome Message

by brian＠emwd.com

Mark Sapiro wrote: > Can you do bin/mailman shell? > > That would be even better. bin/mailman shell -bash: bin/mailman: No such file or directory Apparently not. Again this is the Docker version. Would love to have the Docker maintainer help out here. > If you're installing via pip you must have Python 3. Your tracebacks show a Python 3 > library in /usr/lib/python3.6/ /usr/lib/python3.6 -bash: /usr/lib/python3.6: No such file or directory I am installing it via pip on a Ubuntu server which is a different server from this template problem. Sorry about the confusion. The one where I need the templates to work is on a Centos server that used Docker to install it. I simply do not know how to get a python3 prompt when it has been setup via Docker. I will be requesting some assistance for the Ubuntu server once I get this template issue resolved. Brian

6 years, 3 months

[MM3-users] Re: Hyperkitty Authorization Required

by Andrew Bernard

Hi Mark, Thanks. But that is not the problem. It's hyperkitty background processes that show the error in the logs. I was probably not clear in my statement of the problem. I was testing it by typing in URL's. Sorry! I solved it by searching these archives. There was a post in January regarding the same issue, and the solution turned out to be replacing the given api keys with new ones, and all it all just works. Why that should be is a mystery to me, but now at least two people have found this. I would have thought a key is just a key. Andrew > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Friday, 7 June 2019 1:22 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty Authorization Required > You have to be logged in to post from HyperKitty. You can't post > anonymously.

6 years, 1 month

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Wolfgang Bock

Am 15.11.2019 um 02:21 schrieb Mark Sapiro: > Your Apache config needs to define separate a VirtualHost for each > domain, either by IP address or ServerName, and each VirtualHost points > to its own SSL certificates. Thanks for your info, that did it. I had to include the text of the apache.conf in all my apache-config-files for my virtual-domains. >> If I set use_https to yes in mailman.cfg I get on the website for all lists: >> >> postorius: Something went wrong >> Mailman REST API not available. Please start Mailman core. >> >> >> Does your setting in settings(_local).py for MAILMAN_REST_API_URL have >> an https scheme? That doesn't solve the problem. I changed that in mailman-web.py (MAILMAN_REST_API_URL = https://localhost:8001) and after that in mailman.cfg (use_https: yes). But got the same errormessage on postorius website. Regards Wolfgang

5 years, 8 months

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

by Abhilash Raj

> On Mar 27, 2021, at 6:03 PM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 3/27/21 6:42 PM, Mark Sapiro wrote: >> Ooops, Abhilash is correct. I have a bad habit of focusing on what's in >> the body of a post and sometimes missing relevant info in the subject. >> Sorry. > > Ok, can you or Abhilash reply to my previous questions. I thought I did, the support for specifying reason has been added in Postorius’s master branch. It will be in the next release, 1.3.5 probably. Core has had support for specifying reason when rejecting requests since 3.3.3. > > -- > 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/ -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Message shows up individually but not in the thread

by Marvin Gülker

Am 04. November 2017 um 10:51 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > There is a possibly related issues at > <https://gitlab.com/mailman/hyperkitty/issues/151> and some older ones > at <https://gitlab.com/mailman/hyperkitty/issues/131> and > <https://gitlab.com/mailman/hyperkitty/issues/149>. > > I'm sorry I can't offer more help than that at this point. Okay. I'll have an eye on the problem and see whether I can make out any pattern on messages not appearing. I'm not (yet?) seeing the other symptoms described in #151, but our mailinglists are usually rather quiet until some burst of discussion arises. There have not been any newer posts than the linked ones yet. The mails all went out properly via email. It's a problem related to Hyperkitty thus. Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 8 months

[MM3-users] Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

2 years

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

by Mark

>> On 12/17/24 13:35, Mark wrote: >> ... if I subscribe with an address that has never been used before, I >> receive an email that requires me to confirm the subscription. >> >> The subscription is also held in the administrator's "Subscription >> requests: Pending confirmation". >> >> This happens when subscribing by both email and the web UI. >> >> Ideally, as the Policy is set as "Open", the subscription of any new >> email address should be added automatically. > On 2024-12-18 00:00, Mark Sapiro wrote: > It is not the subscription that requires confirmation. It is the user's > email address. Even though the list's subscribe policy is open, a > previously unknown email address has to be confirmed. Thank you Mark. Your explanation is very much appreciated. Best, Mark

7 months, 2 weeks

[MM3-users] Re: Cannot setup announce-only mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/1/20 9:53 AM, Abhilash Raj wrote: > > Mark, do you think we should make the actual announce-only style reflect > > these settings so folks don't have to manually set these after they create > > a announce-only list? > > > > I am not sure the reason behind these settings lacking for the current > > announce-only style. Are there situations where announce-only list would > > have different list setting? > > I think it was probably done as it is just as a start. I do think it > would be good to set more things appropriately for the announce-only > style, ultimately we may need to add templates for post rejection > notices and things like that. If this involves a fair amount of coding maybe it could be a suggested GSoC task? Steve

5 years, 5 months

[MM3-users] Re: Centralizing logging

by Odhiambo Washington

On Wed, Sep 29, 2021 at 7:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/29/21 4:51 AM, Odhiambo Washington wrote: > > > However, there is this process that *forced* me to create > > usr/local/mailman/*logs/mailmansuite.log > > *as opposed to it just writing to var/logs/ path above > > > > Is there a way to make it write its log $var_dir ? > > > This is Django's log. Django knows nothing about mailman.cfg which is > for core only. You can set the path in your Django settings. See > LOGGING['handlers']['file']['filename'] > > I deal with this by creating a symlink like > > /usr/local/mailman/logs -> /usr/local/mailman/var/logs > Wuah. I did not even think about a simple symlink. Thank you so much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 10 months

[MM3-users] Re: All users getting disabled after upgrade of mailman3

by Quanah Gibson-Mount

--On Thursday, January 18, 2024 6:09 PM -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/24 15:08, Quanah Gibson-Mount wrote: >> Hello, >> >> We just upgraded our mailman to the latest provided from Debian bookworm >> (I know, not the recommended installation method). >> >> >> >> Now everyone's having their addresses disabled due to "bounce" errors. >> This is odd, because I'm disabled, even though I received the 2 emails I >> sent to the list today (and that's the only list traffic today). > > > Did you upgrade mailman core from a version older than 3.3.1? > > If so, see this post > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess > age/IC3LXQMANJGOVUOCVUBHIOGYZ4PA24F7/>. That's it! Thank you so much Mark! Excellent help as always. Regards, Quanah

1 year, 6 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

Oh wow.. so that was special. Sorry for the massive logs and back and forth. It turns out all I was missing was that I needed to re-run sudo mailman aliases before restarting the service. I have a different set of issues right now but I need to debug that a bit more to figure out what is going on. Thanks for all the help Mark, much appreciated. -- Samir Faci On Mon, May 4, 2020 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/20 11:07 AM, Samir Faci wrote: > > The only way I've gotten it to work so far is by using the FQN. I can > > switch back to 127.0.0.1 but that wasn't working. > > > > Here's the configuration I have. > > > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > smtp_host: 127.0.0.1 > > smtp_port: 25 > > smtp_user: > > smtp_pass: > > > > lmtp_host: 127.0.0.1 > > lmtp_port: 8024 > > > > > > > > and the end result: > > > > https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 > > which includes > > May 4 17:50:09 lists postfix/lmtp[2600677]: connect to > lists.domain.org[198.199.98.177]:8024: Connection refused > > So the question is, why is Postfix trying to connect to > lists.domain.org[198.199.98.177] and not to localhost[127.0.0.1] > > > > > smtp_host: 127.0.0.1 > > lmtp_host: 127.0.0.1 > > > > #fail > > > But it should work. > > > > smtp_host: lists.domain.org > > lmtp_host: lists.domain.org > > > > # success. > > > And this should not be necessary. > > > > The error I get if I don't open port 8024 is below and in the gist i > linked > > earlier. > > > > May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< > > testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, > > dsn=4.4.1, status=deferred (connect to lists.domain.org > [198.199.98.177]:8024: > > Connection refused) > > > This is what is expected if port 8024 is not open and you are connecting > to lists.domain.org. > > > > The only way I've gotten it to work so far is by binding both the > smtp_host > > and lmtp_host to be lists.domain.org and opening up port 8024. > > > > I'd rather not have that port open but I'm open to suggestions on what > else > > to try. > > > You need to get Postfix to use localhost[127.0.0.1] and not > lists.domain.org[198.199.98.177]. > > One issue is when you change > > lmtp_host: lists.domain.org > > to > > lmtp_host: 127.0.0.1 > > you need to run `mailman aliases` to change the settings in > var/data/postfix_lmtp. I think if you go back to > > smtp_host: 127.0.0.1 > lmtp_host: 127.0.0.1 > > and run `mailman aliases`, restart mailman and reload Postfix, it should > all work without opening port 8024 and probably without needing to put > 198.199.98.177 explicitly in mynetworks in Postfix. > > I suspect you will have issues with mail not being accepted or treated > as spam by some recipient ISPs however. See > <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS> > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 2 months

[MM3-users] Looking for large sites that have migrated to mailman3

by Stephen J. Turnbull

ssw(a)washington.edu writes: > We're looking for information on large sites that have migrated to > mailman3. Preferably academic institutions. As we start to look > at a migration project we're hoping to hear any 'lessons learned' > from those who have gone before us. The largest site I know of that has begun migration to Mailman 3, and has a non-trivial (dozens, maybe?) number of lists in operation is python.org. You can try searching the archives for this list and in mailman-developers(a)python.org for python.org and mailman3.org postmaster Mark Sapiro's opinions on the matter. I think the EMWD hosting site is also in process of migrating. I know there are several others (specifically a couple of academic institutions) basically at the very beginning of their migrations, but I don't know any in the later stages. Steve

6 years

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

On 10/24/23 18:29, Mark Sapiro wrote: > On 10/24/23 12:34 PM, Thomas Ward via Mailman-users wrote: >> >> ... I get a hard load error on "ModuleNotFoundError: No module named >> 'MailmanCustomizations'" >> >> To confirm this is a Python module/class, I did a pure python shell >> with `from mailman_customizations.hooks import >> MailmanCustomizations` and it properly imports that class, so I'm >> not sure where to go from here in debugging. > > What if you try this with `mailman-web shell`? > Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. Thomas

1 year, 9 months

[MM3-users] Re: Messages in var/queue/shunt

by Brian Carpenter

On 10/20/20 6:15 PM, Mark Sapiro wrote: > On 10/20/20 2:29 PM, Brian Carpenter wrote: >> I have a large number of messages in the shunt directory due to some >> testing done. What is the proper method of dealing with them? Is there a >> way to release them again to the archiver or can I safely delete them? > > I'm assuming based on what you say above that these were all shunted in > the archiving process because of some issue in that process which has > been fixed. > > If that is the case, you have choices. If you want the messages to be > archived, just run `mailman unshunt`. If you don't want them archived > you can run `mailman unshunt` --discard` or you can simply remove the > .pck files from var/queue/shunt. That worked wonderfully. Thank you. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Mark Sapiro writes: > This apparently confuses the Python email package so that the > get_payload() method returns a list of strings rather than a list of > message objects. Yes, I got that far too. I'm guessing that in the absence of a Content-Type, which then *should* default to text/plain, the email package goes ahead and detects the MIME headers anyway (although I don't think it should do that) and breaks the message into MIME parts. I would think we'd raise an Exception here. If there's a reason for the email package to do that detection (*shrug*, it seems to work), then the dispatching in _handle_text should be done on the Python type rather than the MIME Content-Type. I forget exactly how the code is structured, the relevant dispatching may be in _dispatch or in _dispatch_meth. Steve

2 years, 10 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Ken Alker

--On Saturday, June 24, 2023 2:09 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/23/23 10:44 PM, Ken Alker wrote: > > > 4) python3: can't open file 'manage.py': [Errno 2] No such file or directory > > > > The last one looks the most concerning, and is looping. > > > If you installed the mailman-web package from PyPI, the django admin > command is bin/mailman-web in your venv, not manage.py. I found that in /etc/mailman3/uwsgi.ini and changed it and it solved the problem. Thank you! I sent a reply to my original email this morning but when I view it in the web archives, it see that it didn't get threaded with my original email. I hope this one does. I wonder why the original did not. Ken

2 years, 1 month

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/8/21 6:44 AM, rrosner5(a)gmail.com wrote: > > I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. Please see <https://wiki.list.org/x/12812344>. > I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. > > I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. > Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: > > /usr/share/mailman3-web/manage.py mmclient > Python 3.7.3 (default, Jan 22 2021, 20:04:44) > [GCC 8.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> client.system > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect > raise socket_err > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect > sock.connect((self.host, self.port)) > ConnectionRefusedError: [Errno 111] Connection refused The REST API is apparently not listening on the host/port this is trying to connest to. > An excerpt from /var/log/mailman3/web/mailman-web.log: > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ > command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute > settings.INSTALLED_APPS > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ > self._setup(name) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup > self._wrapped = Settings(settings_module) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ > mod = importlib.import_module(self.SETTINGS_MODULE) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/share/mailman3-web/settings.py", line 486, in <module> > from settings_local import * > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 724, in exec_module > File "<frozen importlib._bootstrap_external>", line 859, in get_code > File "<frozen importlib._bootstrap_external>", line 916, in get_data > PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' > [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds > > not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. What is executing the manage.py command to start Django. Is it user list? > The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are > [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully > [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations > [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2' I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Thomas G

Hi, It's a complete migration, not just a upgrade. I rebuild every things on the new server, without data transfers (mailman data dir) other than archives. "" You can't import a gzipped mbox. You have to gunzip it. "" Omfg, yes indeed, it's work better... I have just a problem with statistics not available. "" it won't import any messages older than the most recent message in the existing archive "" It should be not a problem. I will do a dead time to process this change. > Stop prod / migrate archives / start prod on new server. Thanks, Thomas. Le mar. 2 oct. 2018 à 05:11, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 09/30/2018 11:42 PM, Thomas G wrote: > > Hi, > > > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > > install in Mailman3.2. > > > > I didn't found how migrate the archives. > >>From : HyperKitty - Version: 1.1.1 - Python2.7 > > To : HyperKitty - Version: 1.2.1 - Python3.5 > > > As Abhilash said, you shouldn't need to migrate anything but the search > index. > > > > I exported a mbox from hyperkitty (web interface) and tried to re-import > > it, without result. > > """""""""""""""""""""""""""""""""""""""" > > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > > listedetests(a)hatlab.fr > > > You can't import a gzipped mbox. You have to gunzip it. > > > > Computing thread structure > > Synchronizing properties with Mailman > > Warming up cache > > The full-text search index is not updated for this list. It will not be > > updated by the 'minutely' incremental update job. To update the index > > for this list, run the 'manage.py update_index_one_list > > listedetests(a)hatlab.fr' command. > > """""""""""""""""""""""""""""""""""""" > > The database stay empty (and web interface): > > """""""""""""""""""""""""""""""""""""" > > mailmandbnameprod=# select * from hyperkitty_email; > > id | message_id | message_id_hash | subject | content | date | timezone > > | in_reply_to | archived_date | thread_depth | thread_order | > > mailinglist_id | parent_id | sender_id | thread_id | sender_name > > > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > > (0 rows) > > """""""""""""""""""""""""""""""""""""" > > > > Any idea to do this importation ? > > > Why is the database empty? It should be as it was with the prior > HyperKitty. > > Also, it doesn't seem to be the issue here, but if you don't specify a > --since option to hyperkitty_import, it won't import any messages older > than the most recent message in the existing archive. i.e., if there are > any messages in the existing archive, the default for --since is the > date of the most recent such message. > > -- > 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] Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Stephen J. Turnbull

Mail Person writes: > Hello everyone. I am trying to sort out an error happening when > messages are sent to the mailman server. The emails are being sent > to the list but I get this error each time: > > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") This looks like the MySQL "we don't do 4-byte UTF-8" bug. > File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute > 209. res = self._query(query) and it is MySQL, so the problem is most likely that your MySQL is not configured to handle Unicode properly. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… for a lot of information about this. All the posters have useful comments but start with Mark Sapiro's.

1 year, 11 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > So it's even weirder – however, I'm really not sure if this is > > the address HyperKitty is checking for, as I have 3 attached to > > my account! How may I know which one it's trying to use? > > If you go to https://example.com/user-profile/ what Primary email > and Other emails do you see? Do you see all three? And if you go to > https://example.com/mailman3/users and click Manage for your > address, do you see all 3 under Addresses? Is it possible this is a weird new symptom of the "multiple entries for archiver" bug? -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 3 weeks

[MM3-users] Re: Mailman-web showing "An error occurred while processing your request."

by C. Souza

Hello Guys, Thank you for the help. Mark, I followed your recommendation running your code and it's done, problem solved. Just for curiosity, does anyone know the reasons for this kind of problem and how to avoid it? Thank you very much. -- Carlos Adean On Thu, Feb 9, 2023 at 1:55 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/8/23 08:34, C. Souza wrote: > > I'm trying to manage 2 held messages in a specific list and I'm getting > > this error below when I click on /held_messages. It never happened > before. > ... > > ==> mailmanweb.log <== > > ERROR 2023-02-08 16:01:30,149 1516 django.request Internal Server Error: > > /mailman3/lists/mylist.domain.com/held_messages > > Traceback (most recent call last): > ... > > File > > > "/opt/mailman/venv/lib64/python3.6/site-packages/django/utils/dateparse.py", > > line 107, in parse_datetime > > match = datetime_re.match(value) > > TypeError: expected string or bytes-like object > > > I'm not certain, but it looks like one of the held messages has a bad or > possibly missing Date: header. Working around this is tricky. You can do > the following 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.example.com mailing list > >>> requests = IListRequests(m) > >>> msgstor = getUtility(IMessageStore) > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if data['_request_type'] == 'held_message': > ... print(f'request ID = {request.id}Message-ID = {key}\n ' > ... f'message = {msgstor.get_message_by_id(key)}') > ... > This will print for each held message output like > > request ID = nnn > Message-ID = <the message id> > message = the message content > > > You can then handle these messages with > > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, nnn, action) > > where nnn is the request ID and action is either Action.discard to > discard the message or Action.accept to accept it. And finally > > >>> commit() > ``` > If you decide you want to edit the message content before accepting it, > you could find the message in the file system. One of the headers in the > displayed message is something like > > Message-ID-Hash: IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL > > the message is saved as a python pickle in the file system in Mailman's > var/messages/ directory. This has subdirectories of the first two > characters of the Message-ID-Hash value and those have subdirectories of > the second two characters of the Message-ID-Hash value, so if the above > were the actual Message-ID-Hash the pickle would be at > var/messages/IW/L2/IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL. You would need to > pickle the new message content and save that over the existing file. > > -- > 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 skooperit(a)gmail.com >

2 years, 5 months

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

by Thor Atle Rustad

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

7 years, 8 months

[MM3-users] Re: Filter who can send on mailman3 list?

by marcus.granath＠gmail.com

Thank you @Mark Sapiro for you quick reply. So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: Settings -> Message Acceptance "Default action to take when a member posts to the list": "Hold for moderation" "Default action to take when a non-member posts to thelist": "Hold for moderation" Members -> Administration options -> Moderation: "List default" BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? How will they then be able to send messages, or what do I misunderstand here? Also, how do I create a "non-member" user "no-reply(a)abc.com"? Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there?

4 years, 3 months

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

by Jered Floyd

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 Patch also included below. --Jered --- a/allauth/socialaccount/helpers.py +++ b/allauth/socialaccount/helpers.py @@ -205,7 +205,7 @@ def _add_social_account(request, sociallogin): def complete_social_login(request, sociallogin): assert not sociallogin.is_existing - sociallogin.lookup() + sociallogin.lookup(request) try: get_adapter().pre_social_login(request, sociallogin) signals.pre_social_login.send( --- a/allauth/socialaccount/models.py +++ b/allauth/socialaccount/models.py @@ -274,12 +274,12 @@ class SocialLogin(object): return False return get_user_model().objects.filter(pk=self.user.pk).exists() - def lookup(self): + def lookup(self, request=None): """Look up the existing local user account to which this social login points, if any. """ if not self._lookup_by_socialaccount(): - provider_id = self.account.get_provider().id + provider_id = self.account.get_provider(request).id if app_settings.EMAIL_AUTHENTICATION or app_settings.PROVIDERS.get( provider_id, {} ).get("EMAIL_AUTHENTICATION", False): ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise 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." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > 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 jered(a)convivian.com

1 year, 7 months

[MM3-users] Re: Can't remove footer(s)

by Henrik Rasmussen

Mark Sapiro wrote: > On 10/02/2018 12:14 AM, Henrik Rasmussen wrote: > > Did I miss something in order to remove the footers? > > Removing the files won't work because Mailman will fall back the the > built-in footer. You have to create empty files. The easiest thing is > just to 'cp /dev/null' to the footer files created by import21 Copying /dev/null doesn't help. It seems to be the same old content of the footer files before I removed the files and restarted Mailman, as if Mailman keeps the cache. I've just (again) ran # docker exec -it mailman-core mailman shell -l [LISTNAME_FQDN] >>> getUtility(ITemplateManager).delete('list:member:digest:footer', m.list_id) >>> getUtility(ITemplateManager).delete('list:member:regular:footer', m.list_id) after copying /dev/null to the files in /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/list_member_digest_footer.txt and list_member_regular_footer.txt ,but that doesn't change anything. -- Henrik Rasmussen

6 years, 10 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Wed, Aug 7, 2024 at 2:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/6/24 14:27, Mark Sapiro wrote: > > > > Is this with only one browser? It's a long shot, but clearing browser > > cache might work. > > > Actually, I see the same issues from my browsers, so it's not a browser > caching issue. The only thing left is nginx caching, but, while I know > very little about nginx, I think it doesn't cache by default and I don't > see where in your posted config it's enabled. Perhaps there's more in > your config that you didn't post. > > If there is a proxy_cache_path directive in your config try > > find /the/proxy/cache/path -type f -delete > > to clear the cache. > > As a last resort, your /opt/mailman/mm/static/CACHE/ directory should > contain a css/ directory with 3 files and a js directory containing one > file and a manifest.json file with a template for the `link` directives > referencing those files. > > The js/ directory is easy as its only one file, so your server is > looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create > a symlink in the js/ directory from output.3aaa7705d68a.js to the actual > file. For the css directory, your server is looking for > output.158acc288604.css and output.6dab123e4897.css, and I don't see the > third file in the logs you posted, but if I go to pages in your archive > that I see as unstyled and look at the stylesheet references, they are > to output.44ea6c55e917.css, output.e68c4908b3de.css and > output.9efeb5f3d52b.css so you could just symlink those to the actual > files, it doesn't matter which as all three are loaded on each page. > Could you allow me to revisit this issue since I haven't solved it? First, I bypassed CloudFlare DNS proxying just to ensure I have nothing is coming in between my browser and the web server. That did not help with the issue of the "missing" CSS files. Ideally, I should not be creating these symlinks, right? On my old server the symlinks weren't necessary. I have created some symlinks and that appears to help with Apache. I will test with Nginx and see how it goes. ``` root@eu:/opt/mailman/mm/static/CACHE/css# ls -al total 196 drwxr-xr-x 2 mailman mailman 4096 Sep 29 10:40 . drwxr-xr-x 4 mailman mailman 4096 Mar 21 2024 .. lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:40 output.ac23d5f5127c.css -> output.d29798365ddb.css lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:31 output.bacec526ec98.css -> output.e69dbb26da3b.css -rw-r--r-- 1 mailman mailman 1209 Mar 21 2024 output.d29798365ddb.css -rw-r--r-- 1 mailman mailman 569 Mar 21 2024 output.e68c4908b3de.css -rw-r--r-- 1 mailman mailman 180904 Mar 21 2024 output.e69dbb26da3b.css root@eu:/opt/mailman/mm/static/CACHE/css# ``` My question though: What is the source of truth for the files that should be in /opt/mailman/mm/static/CACHE/css/ ?? Maybe that is what I need to focus on. If need be, then I should *fix* the contents of that file so that it doesn't contain the nonexistent files, no? Lastly, why is it that my https://mm3-lists.kictanet.or.ke/archives/ does not display content similar to what https://lists.mailman3.org/archives/ does? What change should I make in which settings.py? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Seth Seeger

On May 8, 2020, at 10:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/8/20 7:34 AM, Seth Seeger wrote: >> >> There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change. > > > You have to edit the display name for the domain in the Django web admin > Sites section. Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for. Thanks, Seth

5 years, 2 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Mark Sapiro a écrit le 12/03/2021 à 00:59 : > On 3/11/21 3:10 PM, Gilles Filippini wrote: >> >> Looking at the offending message with 'mailman qfile', it appears it is >> a legitimate one actually, sent from an Android phone. >> >> Couldn't hyperkitty be a bit less strict? > > > Possibly. It looks like this may be > <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by > <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What > HyperKitty version is this? > <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. > > If your HyperKitty is >= 1.3.2, please file a new issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> This is Hyperkitty 1.3.4. I'll file an issue tomorrow. Thanks, _g.

4 years, 4 months

[MM3-users] Re: Django: An error occurred while processing your request.

by Florian Sukup

Thank you both very much. On 5/26/25 18:30, Mark Sapiro wrote: > On 5/26/25 12:08 PM, Florian Sukup wrote: >> >> When I received emails from postorius, then it came from example.com >> which is nonsense as I worked with the real lists. So I deleted >> example.com. > > > Set DEFAULT_FROM_EMAIL and SERVER_EMAIL appropriately in your Django > settings. > seem to produce reasonable results >> When I call https://.../mailman3/admin or any of the lists, the result >> is: >> Server error >> An error occurred while processing your request. > > You need to set SITE_ID appropriately in your Django settings. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > This made the difference. I set it to 0 now as I have more than one site/domain. Thanks again, Florian.

2 months

[MM3-users] Re: Deleting messages from HyperKitty archive

by Mark

On 2024-03-26 08:45, Mark Sapiro wrote: > On 3/25/24 13:00, Mark wrote: >> >> Regarding updating, the Hyperkitty docs say to (a) update the code >> base; and (b) update the database schemas. >> >> Although updating the database is mentioned, there isn't anything >> about updating the code base. > > Updating the code base just means installing an updated version. E.g. > upgrading from 1.3.8 to 1.3.9. > Thanks Mark. Was another case of "If all else fails, read the instructions..." $ sudo systemctl stop mailman3 $ sudo systemctl stop mailmanweb (venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web (venv) $ mailman-web migrate (venv) $ mailman-web compress (venv) $ mailman-web collectstatic (venv) $ mailman-web compilemessages $ sudo systemctl start mailman3 $ sudo systemctl start mailmanweb https://www.mailman3.org/en/latest/upgrade-guide.html Successfully upgraded to Hyperkitty 1.3.9 and the delete message link now shows for the list owners. Best, Mark

1 year, 4 months

[MM3-users] Re: Extracting mailing list users

by Jan Eden

On 2022-12-30 10:29, Mark Sapiro wrote: > On 12/30/22 03:25, Jan Eden via Mailman-users wrote: > > On minor issue: All user names with > > non-ASCII characters appear with quoted-printable encoding (e.g. > > =?utf-8?q?J=C3=BCrgen?=). Is there a way to output UTF-8 instead of QP? > > I just created https://gitlab.com/mailman/mailman/-/issues/1048 for this. I > think this patch > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -104,10 +104,10 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - if email_only: > + if email_only or not address.display_name: > print(address.original_email, file=outfp) > else: > - print(formataddr((address.display_name, > address.original_email)), > + print(f'{address.display_name} <{address.original_email}>', > file=outfp) > > ``` > (line may be wrapped) will fix it. Excellent – thank you! - Jan

2 years, 7 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

David Bremner <david(a)tethera.net> writes: > Mark Sapiro <mark(a)msapiro.net> writes: >> >> Thank you. I tested that DSN with current flufl.bounce and it is >> recognized as a temp failure for the reported address and that in turn >> should just be ignored by Mailman's bounce runner and not reported as >> unrecognized. >> >> What version of Mailman core is this and what version of flufl.bounce? >> > > Sorry, meant to reply on list with the rest of the details, but got > distracted by making dinner. So it sounds like the problem is old > versions of flufl.bounce. > > This particular machine is running debian oldstable, so things are a bit > out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look > into upgrading at least flufl.bounce. Oh. It's actually 3.0.1. Still not new enough, but 3 years newer. d

3 years, 9 months

[MM3-users] Re: emails to list missing from archive after upgrade

by Quanah Gibson-Mount

--On Thursday, January 18, 2024 8:13 PM -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/24 19:57, Quanah Gibson-Mount wrote: >> >> Ok, I've found them in /var/lib/mailman3/archives/hyperkitty/spool, so >> it does seem like the issue is the indexer hasn't run. Not sure what >> process controls that. > > > That's not the issue. There was an exception in mailman-hyperkitty's > communication with HyperKitty. You will find the errors and tracebacks in > mailman.log. Once you fix the issue, whatever it is, the messages will be > archived. mailman-hyperkitty retries all the messages in > /var/lib/mailman3/archives/hyperkitty/spool with each new post. Thanks Mark! The debian upgrade munged the hyperkitty config. Once that was fixed and a new message posted to the list, everything got archived as it should have been. Regards, Quanah

1 year, 6 months

[MM3-users] Re: Your Dashboard

by Allan Hansen

All, Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. Time to visit gitlab? Yours, Allan Hansen hansen(a)rc.org > On Feb 11, 2020, at 12:26 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/11/20 11:00 AM, Mark Dadgar wrote: >> On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >>> everytime I receive a mail for moderation it says: >>> >>> At your convenience, visit your dashboard to approve or deny the >>> request. >>> >>> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. > > > There's no overall dashboard per se. The message actually refers to > whatever web UI you use to manage the list. The default template for > this message is non-specific because it comes from Mailman core, and > core doesn't know if you are using Postorius or some other web > management system or non at all, and even if it were to assume > Postorius, it doesn't know the URL. > > >>> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >>> >>> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? > > > As I said, there is no overall dashboard in Postorius, just the > individual list management pages. > > >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via Postorius. > > -- > 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, 5 months

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

by Manos Pitsidianakis

Thank you for your prompt response Mark, Στις 2019-09-18 19:12, Mark Sapiro έγραψε: > Is only one list affected, and is it all messages from this list or > only > some? Just two messages from this certain list. Subsequent messages and other activity seems to work properly > Do some deliveries of the problem message succeed? > I think not, the IndividualDelivery lines list all all recipients (list is small so I was able to check) > Postfix can return a 421 status > and drop the connection if there are too many invalid local recipients, > although I don't know if this would apply in the VERP case. Well there is no connection to postfix at all when the runner starts and the "Cannot connect to SMTP server" log shows up. Otherwise I'd have seen something in the postfix logs or tcpdumps in localhost.

5 years, 10 months

[MM3-users] Re: export/import list?

by Dave McGuire

On 8/22/23 17:59, Mark Sapiro wrote: >> I'm moving from sqlite3 to postgres; I can handle that migration. >> But I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone >> else) know of any schema changes? I spot-checked the first few and >> they looked the same, but before going through all of them I figured >> I'd just ask here. > > Schema changes are handled automatically by alembic. The migrations are > defined in /mailman/database/alembic/versions/. Your current version is > is stored in the database in the alembic_version table. When Mailman > core is started, all migrations from your current version to the latest > version will be applied to bring your database up to date. I.e., you > don't need to be concerned about schema changes upon upgrade. They are > handled automatically. Brilliant! Thank you Mark. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

1 year, 11 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Thanks Mark for your time. I will follow your recommendation and try mailman bundler again, with care so that new conflicts won't occur as happened yesterday. Mailman bundler docs, in the first paragraph, refer to combined installation of GNU Mailman, Postotius, and Hyperkitty. Does that mean that mailman.client will be installed later separately? My CentOs 7 distribution does not offer python3.4.pip. https://pypi.python.org/pypi/pip offers pip 8.1.2 in two versions: Python Wheel pip-8.1.2-py2.py3-none-any.whl (md5, pgp) Source pip-8.1.2.tar.gz (md5, pgp) Which one should I choose? I also notice that postfix is required. yum offers the following options: pcp-pmda-postfix.x86_64 : Performance Co-Pilot (PCP) metrics for the Postfix (MTA) postfix.x86_64 : Postfix Mail Transport Agent postfix-perl-scripts.x86_64 : Postfix utilities written in perl postfix-sysvinit.noarch : SysV initscript for postfix spamass-milter-postfix.noarch : Postfix support for spamass-milter postgrey.noarch : Postfix Greylisting Policy Server pypolicyd-spf.noarch : SPF Policy Server for Postfix (Python implementation) sqlgrey.noarch : Postfix grey-listing policy service Which of these options are useful? Which ones are unnecessary? Again, thanks very much for your time and hope that the other subscribers in this list find this thread adequate. Haven't found the link on our distribution list profile settings for uploading an avatar. Best regards, Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) 2016-05-28 14:06 GMT-04:00 Mark Sapiro <mark(a)msapiro.net>: > On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > > > In order to avoid compatibility issues, I reinstalled CentOs 7. > Firewalld, Apache and BIND are operational. I also installed Python 3.4 at > http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; > however I understand that Python 2.7 is still available and am confused > about usage of each version. > > > Mailman 3 consists of several pieces. There is a core engine which is > Python 3. The core does the basic email list management and exposes many > options and settings via a RESTful API. > > There is also mailman.client which provides Python bindings for the REST > API. This is Python 2. > > We also provide a web management UI, Postorius and an archiver, > HyperKitty. These are Django applications and all of this is Python 2. > > There are other pieces as well. > > > > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if > you quickly let me know how to install it. I do not wish to use mailman > bundler. > > > This is only the core. You can install it with > > python3 setup.py install > > either in a python 3 virtualenv or not, but this will only give you the > core. > > I suggest you see the docs at <http://docs.list.org/en/latest/>, and if > you don't want to use bundler, see > <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the > recommended way to set up a working, non-development Mailman suite. > > In short, the core requires Python 3.4, most of the rest of the suite > requires Python 2.7 because of dependencies not yet ported to Python 3. > > -- > 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/ >

9 years, 2 months

[MM3-users] Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

7 years, 10 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Odhiambo Washington

On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > Am 2024-04-26 00:52, schrieb Mark Sapiro: > > On 4/25/24 14:01, Thomas Stein wrote: > >> Am 2024-04-25 22:03, schrieb Mark Sapiro: > >>> > >>> I don't know how things are arranged in the Debian/Ubuntu package, > >>> but you may have a settings.py which at the end does something like > >>> ``` > >>> try: > >>> from settings_local import * > >>> except ImportError: > >>> pass > >>> ``` > >>> If that is the case, adding the above snippet to the end of > >>> settings_local.py should work. > >> > >> Yes, that's the case. I added the snippet in question to > >> settings_local.py but this leads to another error: > >> > >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> > >> from settings_local import * > >> File "/usr/share/mailman3-web/settings_local.py", line 194, in > >> <module> > >> x = list(MIDDLEWARE) > >> ^^^^^^^^^^ > >> NameError: name 'MIDDLEWARE' is not defined > >> dpkg: error processing package mailman3-web (--configure): > > > > Yes. I understand. In your case, MIDDLEWARE is only defined in > > settings.py and not in settings_local.py. As I understand it originally > > you added > > ``` > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to settings.py and you say it didn't help. I don't know why that > > wouldn't work as long as there is no setting for MIDDLEWARE in > > settings_local.py and you added that after the MIDDLEWARE setting in > > settings.py. > > When you say it didn't help, do you mean you still get the > > > > django.core.exceptions.ImproperlyConfigured: > > allauth.account.middleware.AccountMiddleware must be added to > > settings.MIDDLEWARE > > > > message or something else? I note that the original post in this thread > > refers to /etc/mailman3/mailman-web.py which is presumably where the > > package ultimately puts the Django settings, and I don't know what > > `dpkg --configure` is doing. > > > > One thing you could try is in settings_local.py, put > > ``` > > from settings import MIDDLEWARE > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to work around the NameError. > > After that I get: > > File "/usr/share/mailman3-web/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' > (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > > I guess I'll wait for the new package for now. > How about adding: MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) in settings_local.py And how about you use the virtualenv method <https://docs.mailman3.org/en/latest/install/virtualenv.html> for more peace of mind in the future? -- 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: Converting discussion list to read-only list (settings)

by Paul Arenson

Mark Sapiro wrote: > Issue is HyperKittyb-when replying to a message in an existing thread instead of >using the 'reply' action on that message, they use the Start a new thread button. So then >If by "read only" you mean the "Announce only mailing list style" as >opposed to the "Ordinary discussion mailing list style" the only >difference is that for the Announce only style the list attribute >allow_list_posts is False and for the Discussion style, it's True. > >This is the setting in Postorius -> Settings -> Alter Messages -> >Include the list post header an all it does is include or not include >the List-Post: header in mail from the list. Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? Thank you.

5 years, 9 months

[MM3-users] Re: more about spanish translations

by Guillermo Hernandez (Oldno7)

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) Thanks a lot, as always, Mark.

4 years, 5 months

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mike Wertheim

Thanks for the response. A while back I experimented with enabling verp-probes. The users on the list were confused by the probe emails and sent me a lot of messages asking about them, so I disabled it. There is zero spam on the list. Ill try reducing "bounce info stale after" to "2d". (Actually, would "1d" be even better?) On Fri, Jun 16, 2023 at 7:46 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/16/23 19:20, Mike Wertheim wrote: > > I'm running an email list on mailman3. > > > > My users are getting inundated by messages saying that their > subscriptions > > have been disabled due to their bounce score exceeding the mailing list's > > bounce_score_threshold. > > > > But there is nothing wrong with these users' email accounts. They are all > > perfectly fine. Apparently the issue is somehow related to spam. > > > Is spam being posted to your list? If so, you should ensure that Default > action to take when a member posts to the list is set to Hold for > moderation so that spammers can't subscribe to your list and post > without the post being reviewed by a moderator. Then if the post is on > topic, the moderator can set the user's moderation action to Default > processing when accepting the post so subsequent posts won't be held. > > Also set `verp_probes: yes` in the [mta] section of mailman.cfg. Then > when a user's score reaches threshhold, a probe message is sent and > delivery is only disabled if the probe bounces which it probably won't > if the issue is spam bounces. > > > > Whenever I (as admin) get these emails, I just unsubscribe the user and > > then re-subscribe them. But also, the user gets confused and emails me > > about it, which unnecessarily takes up their time and mine. > > > That should be unnecessary. Just click on the member in the members list > and set the member's Delivery status to Enabled. However, this may not > work because of https://gitlab.com/mailman/mailman/-/issues/1061 which > is not fixed until the next release, but enabling verp_probes will avoid > that issue. > > > > The relevant list settings are currently... > > bounce score threshold: 5 > > bounce info stale after: 7d > > bounce disabled warning interval: 7d > > bounce disable warnings: 5 > > > > What's the best way to fix this? I'm considering reducing "bounce > > info stale after" to "2d" and/or increasing "bounce disabled warning > > interval" to "90d". > > > Increasing "bounce disabled warning interval" or "bounce disable > warnings" won't help because the user's delivery will still be disabled. > It will just take longer for them to eventually be removed. Reducing > "bounce info stale after" to "2d" might help as long as the list gets > good posts more frequently than that, but the best way to deal with this > is to enable verp_probes and then only consider other things if that > doesn't 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://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 mike.wertheim(a)gmail.com >

2 years, 1 month

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Stephen J. Turnbull

Mark Sapiro writes: > Filtering by extension only works on message parts that have an > associated file name. Thus, while you can add things like 'exe', 'bat', > 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it > won't be completely effective. > > A better approach is to use MIME types[1] and only allow those you want. > For a discussion list, a reasonable set is what this list uses: I wouldn't say "better" if you're concerned about the executables being malware. There's long history of concealing malware by giving it a MIME type different from what the extension implies, and there was at least one Windows exploit that used this technique to achieve automatic execution of malware simply by displaying the message.

4 years, 10 months

[MM3-users] Re: Sibling lists in Mailman3

by Markus Grandpre

Is there an equivalent approach to implement sibling lists in Mailman3? Best regards, Markus Grandpré Am 3/28/24 um 16:06 schrieb Markus Grandpré: > Thank you. > > Am 27.03.24 um 17:26 schrieb Mark Sapiro: >> On 3/27/24 08:05, Markus Grandpre wrote: >>> >>> after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or >>> something similar) in Mailman3. How are sibling lists treated in Mailman3? >> >> The sibling list features do not exist in Mailman 3. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 3 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by Andy Smith

Hello, On Sat, Jun 25, 2022 at 08:22:31PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > Mark Sapiro wrote: > > In the pop-up dialog from clicking the subject of a held post you can > > set the sender's moderation status when discarding the post. > > Sorry but I can only see: > > - “--- Set member moderation ---” (non selectable, I guess) > - “Hold for moderation” > - “Reject (with notification)” > - “Discard (no notification)” > - “Accept immediately (bypass other rules)” > - “Default processing” > > and cannot see how I can at the same time “Discard (no notification)” > and “Banish the email of the post's sender”. These are actions for all future messages from that member, so "Discard (no notification)" would set it to (silently) discard all future mails from them. Is that not what you mean by "banish"? Cheers, Andy

3 years, 1 month

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Correct I used list.louisvillecommunitygrocery.com On Wed, Jan 29, 2025, 2:58 PM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > Thanks! Looks resolved however I'm not 100% sure which steps fixed it: > > My Steps: > ``` > cat /etc/hosts > 127.0.1.1 list.louisvillecommunitygrocery.com list > 127.0.0.1 localhost > ``` > > Updated > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' > ``` > Restarted mailman3 AND mailmanweb service > > Updated /etc/mailman3/gunicorn.conf adding workers=9 > > Restarted mailman3 AND mailmanweb service > > Deleted custom template from Postorious > > Created new custom template from Postorious > > Added test user to list > > User was added with no errors and also received the custom Template. > > Thanks Mark, Gerald > > Bonus question: how should I calculate how many workers I should have on > my system? > > > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Wed, Jan 29, 2025 at 2:36 PM <vogt(a)spamcop.net> wrote: > > > > Sounds somewhat like the problem I have had: > > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > The problem for me was that I am using gunicorn but did not increase the > number of workers… > > _______________________________________________ > > 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 paul.m.robey(a)gmail.com > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Wed, Jan 29, 2025 at 2:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > > > Ok I did install using the > > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > > > I added > > > ``` > > > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > > > ``` > > > > I hope you didn't add the above literally without replacing > > www.example.com with your actual host name. > > > > It should be > > ``` > > POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' > > ``` > > > > > to /etc/mailman3/settings.py and restarted mailman services > > > > > > However I'm still getting the same error from mailman.log > > > > > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > > > port=8000): Read timed out. (read timeout=5) > > > > I don't understand why it should still be trying to connect to > > localhost:8000. Also, I don't understand why localhost:8000 times out. > > What is your setting for localhost in /etc/hosts? it should be > > `127.0.0.1`. If it is `::1` that could be the issue. > > > > > Not sure if I'm editing the correct config file. > > > > /etc/mailman3/settings.py should be correct. > > > > -- > > 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 paul.m.robey(a)gmail.com >

6 months

[MM3-users] Re: Moderate first postings of new members

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 11/3/22 04:55, c.buhtz(a)posteo.jp wrote: >> >> What I want is that I would like to moderate the messages of new >> subscribed members until I set them to auto-accept all messages. I >> want to see what a new member is posting before it is send/accepted >> to the list. Mark> Set "Default action to take when a member posts to the list" to Mark> "Hold for moderation" Then, in the held messages view, click the Mark> subject and in the resultant dialog, select "Default processing" Mark> from the "set member moderation" dropdown and Accept the Mark> message. If you've set the default processing to 'hold for moderation' won't this just continue to moderate the member? Ive been selecting 'Accept immediately' in the dialog. Peter C

2 years, 8 months

[MM3-users] Re: Migrating to mailman-web and Ubuntu 22.04

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 11/15/22 06:30, Andrew Hodgson via Mailman-users wrote: >> >> I've potentially resolved to use Uwsgi for this and install another package which makes the installation more in line with this: >> https://docs.mailman3.org/en/latest/install/virtualenv.html > >That doc needs to be updated to at least include gunicorn as an alternative to uwsgi. As time permits, I'll work on that. I've managed to complete the install now using that doc using Uwsgi in the venv. I think I used Gunicorn before because Mailman installs it as a dependency so it was something I just used. I also didn't need to install python3-dev on the host with Gunicorn, Uwsgi needed that install to complete the compilation task. I did also try using the packaged version of Uwsgi with Ubuntu but that was a bit of a non-starter. Thanks. Andrew.

2 years, 8 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. [...] > For the mailing list, the only changes needed are to the > mailinglist table; but this leaves the question of list_id. > According to RFC 2919, section 4, the list_id should not change, > but this is problematic in that if it isn't changed, [...] > so to reduce confusion, it may be better to update the list_id > values [...] > For HyperKitty, similar changes need to be made to the > hyperkitty_mailinglist table. [...] Thanks! This looks even more straightforward than I'd hoped. -- Jeremy Stanley

10 months, 2 weeks

[MM3-users] Re: MM2 to MM3 Archives Loading

by Odhiambo Washington

On Fri, Nov 22, 2024 at 11:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/22/24 11:02, Joshua Bushe wrote: > > Unsure where these hide inactive or hide private boxes are located. > Looked through all settings. > > > They are at the top of the main Hyperkitty overview page. E.g. like > https://lists.mailman3.org/archives/ My lists are public, and I have nothing to hide, so let me expose my issue—which I believe is similar to that of the OP. https://mm3-lists.kictanet.or.ke/archives/ - is empty, but there is this active list, which has archives: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… I have been wondering why. -- 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]

8 months, 1 week

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

On Montag, 10. Februar 2025 20:26:26 CET Mark Sapiro wrote: > On 2/10/25 01:07, Andreas Vetter wrote: > > That is unfortunately not enough to get rid of the Warning, because > > venv/lib/ python3.11/site-packages/mailman_web/settings/mailman.py > > contains the old ACCOUNT_AUTHENTICATION_METHOD and allauth is complains > > about it. > > In the recommended virtualenv installation, the settings that Django > sees are /etc/mailman3/settings.py. That in turn contains > ``` > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > ``` > but if following those imports you have > ``` > del ACCOUNT_AUTHENTICATION_METHOD > ``` > Django won't see it and won't complain. Did you actually try this? If > so, did you put the `del ACCOUNT_AUTHENTICATION_METHOD` after `from > mailman_web.settings.mailman import *` in /etc/mailman3/settings.py? You are right, it is enough, when one does not have a typo in it. My fault. Thanks a lot, Andreas

5 months, 3 weeks

[MM3-users] Re: Hyperkitty_import.py Error

by Brian Carpenter

On 2/7/21 2:40 PM, Mark Sapiro wrote: >> I am trying to import some old archives (going back to 2003) into a >> Mailman 3 list. The import job is terminating very early in the process >> with the following error: >> >> IndexError: string index out of range >> >> 1. Is there a way to fix a mbox file that is generating this type of error? > Yes, but you need to understand what message is causing the error and > why. The full traceback from the error can help. So can the script at > <https://www.msapiro.net/scripts/check_hk_import>. > Hi Mark, I wanted to follow up to say that I solved the import error by updating to the latest stable version of MM3/Hyperkitty. You actually had a fix recently to address the "IndexError: string index out of range" error specifically. Your other comments were also very helpful. Thank you! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Migrating archives from Mailman21 to Mailman3

by Odhiambo Washington

On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/24/24 05:49, Markus Grandpré wrote: > > Dear List, > > > > I have a question about migrating archives from Mailman21 to Mailman3: > > Is it possible to migrate only the archive of a list, but not the list? > > > Yes. There is no requirement that archives have a matching list in > Mailman core. So the documentation at https://docs.mailman3.org/en/latest/migration.html needs revision as it creates the impression that a matching list needs to be there: ``` $ python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months, 1 week

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

I’m still wondering about mailman’s cache (cache_dir setting). I have 2x cache files under it that are 3-4 days old. These are mailman cache files, not mailman-web. # pwd /opt/mailman/mm # find cache -type f -ls 38627053 4 -rw-rw---- 1 mailman mailman 13 Feb 6 16:42 cache/26/26/2626c32ded811be4e9631d2215f32d88522b67142bf0eea502362d2b15c4743e 118392 4 -rw-rw---- 1 mailman mailman 11 Feb 7 09:42 cache/98/14/9814e4457e2489e2ec77d19ce982d3643fac3ad849c9861a9198eebf53f1fcde I haven’t figured out how to work with these cache files. I found some mention that a runner would clean up cache files after a week (default) and that one could use ‘cache_life’ to change that default. So, I set the following and restarted mailman. The cache files hadn’t been removed after > 4 hours, so I unset it and restarted again. Cache_life: 1d Without further information or direction, I’m tempted to just remove those cache files and move on with life. Thank you Tom Lieuallen From: Lieuallen, Thomas Otis via Mailman-users <mailman-users(a)mailman3.org> Date: Friday, February 7, 2025 at 1:43 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] Mark, I checked the database; nothing there. Note that there are only 3x entries and only one is list:member:regular:header (my test), so just nothing of interest. The URL works and produces the proper template information. I finally did a find/grep in the mailman tree and found a match for this errant string. It is under the cache folder. This corresponds to the cache_dir value. I could wipe the file out, but what is the proper way of doing so and should they be cleaned out via a schedule? These don’t appear to be web related, as far as I can tell. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Friday, February 7, 2025 at 10:37 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/7/25 10:08, Lieuallen, Thomas Otis via Mailman-users wrote: > > I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. What do you get from the following database queries? SELECT * FROM template WHERE name = 'list:member:regular:header'; SELECT * FROM postorius_emailtemplate WHERE name = 'list:member:regular:header'; Depending on your installation, these tables may be in separate databases, i.e., template table in mailman db and postorius_emailtemplate in mailmanweb db. And what do you get if you go to the uri in the result(s) from the first query? The context in the first results and maybe the second results should also be a clue. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

5 months, 3 weeks

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > Then if collapse_alternatives is True (settable here or in Postorius), > any multipart/alternative parts will by replaced by the first, > presumably text/plain, sub-part. > > Finally, if convert_html_to_plaintext is True (settable here or in > Postorius), any remaining text/html parts will be converted to plain > text by lynx or whatever is configured as html_to_plain_text_command in > mailman.cfg. > This will ensure that filter_action is applied only to those messages > which have no text/plain or text/html parts. Great, that helped for the content. Thanks. Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. If that doesn't work, we have talked about deleting the list and add it from scratch. Is the any prolems (with left overs from the old imported list), when deleting the list from Postorius? /Henrik Rasmussen

6 years, 1 month

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Mon, Jan 23, 2023, 23:09 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/23 02:41, Johannes Rohr wrote: > > > > I don't understand what the cause for the "permission denied" could be. > > The directory "fulltext_index" is owned by mailman:mailman > > > > Does anyone have a hint? I did some googling for the error, but to no > > avail, unfortunately. > > > It's actually trying to create fulltext_index, so clearly it's not > looking at the fulltext_index that you are. If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you probably > need to specify the path in /etc/mailman3/settings.py as in, e.g. > ``` > HAYSTACK_CONNECTIONS['default']['PATH'] = > '/opt/mailman/mm/var/fulltext_index' > Doesn't this follow the same rules of getting the settings.py from gitlab? > >

2 years, 6 months

[MM3-users] No e-mail distribution after import of archive

by Markus Grandpré

Dear Mr. Sapiro, on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list. Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months. With kind regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

8 months, 3 weeks

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, You were (of course), absolutely on target, thank you! I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. I have searched on the file system for any such templates and only see the default ones; all zero length files. There are no templates defined for the domain in postorius – but if there were, I’d expect to see that test header all the time. I’m just baffled. Any clues? I’m a relative newbie to mailman3. When I first set it up, I tried the postorius templates for the domain. They didn’t work (had to have been due to the POSTORIUS_TEMPLATE_BASE_URL being wrong. So, I scrapped that and went with templates in the file system. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 3:46 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

5 months, 3 weeks

[MM3-users] Re: outgoing.py mailman@example.com issue

by dancab＠caltech.edu

Mark Sapiro wrote: > On 11/7/21 1:22 AM, Stephen J. Turnbull wrote: > > dancab(a)caltech.edu writes: > > I deployed Mailman3 last night and today we've had some "bounced" > > messages with headers referencing mailman(a)example.com. This has > > only happened with a few lists. Any ideas what causes this? > > ... > > Mark may have a better idea. > > This is a fake DSN that is generated when Mailman's attempt to send a > bounce probe results in a failure from the MTA to which Mailman > delivers. See code at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... > and around > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... We do have mailman(a)caltech.edu configured with valid members/owners. We're using Postfix for the MTA. Is it possible there's a misconfiguration there? We've been testing the system with a handful of lists for months. -- Dan

3 years, 8 months

[MM3-users] Re: Unable to update templates

by Mark

************************************************** > On 5/27/25 18:54, Mark wrote: >> >> However when I update the template, the databases are updated >> correctly but the Welcome message is still sent with the old template >> content. >> >> mailman.templates >> mailmanweb.postorius_emailtemplate >> >> Additionally, if I delete the template and create a new one the old >> content still gets sent. >> >> I cannot find where this content is written or is being cached. ************************************************** On 2025-05-28 02:34, Mark Sapiro wrote: > The content is stored in the mailmanweb.postorius_emailtemplate table. > As far as Mailman core and Postorius are concerned, that's the only > place. > ... If the template is deleted, the > mailman.template table entry is deleted and at that point Mailman core > will get the template from the file system following it's normal > search rules, ************************************************** Where does Mailman core search for the file if the table entry is deleted?

2 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

4 years, 7 months

[MM3-users] Re: unknown encoding: windows-874

by Stephen J. Turnbull

Mark Sapiro writes: > Python doesn't recognize windows-874 as known charset. iso-8859-11 is a known character set for Thai, with a few missing punctuation marks. If the message turns out to be not Thai, but mostly ASCII with a few broken characters that are probably punctuation (including directed quotes, ellipsis, and the EURO SIGN), any Windows-12xx character set (IIRC, Windows-1252 is closest to Latin-1) should have those in the same positions. > You can move it aside, and if it looks like something you actually want > to archive, you might be able to fix it, but that's tricky. The file in > var/archives/hyperkitty/spool/ is I think a pickled email message > object. You can view it with `mailman qfile`, but editing is tricky. If any of the above codecs seem to work, just editing the charset parameter in Content-Type header(s) should do the trick. Sorry, can't help with the editing process itself, though. Steve

5 years, 2 months

[MM3-users] Re: per domain SITE_ID views?

by David Newman

On 12/28/21 1:30 PM, Mark Sapiro wrote: > On 12/28/21 1:14 PM, David Newman wrote: >> Using FILTER_VHOST, I have two domains set up and working with MM3, >> Postorius and Hyperkitty. However, because SITE_ID in settings.py >> points to one of the domains, that domain name always appears on >> Postorius and Hyperkitty pages. > ... >> How to get the correct domain to appear on that domain's Postorius and >> Hyperkitty pages? > > > I don't think the domain is actually displayed on Postorius pages. You are almost certainly correct. I saw dom1.tld on a login page, but hadn't realized that login page comes from Hyperkitty and not Postorious. > If > I'm wrong, on what Postorius view do you see it? As far as HyperKitty is > concerned, please file an issue for this at > https://gitlab.com/mailman/hyperkitty/-/issues/new Opened an issue here: https://gitlab.com/mailman/hyperkitty/-/issues/404 dn

3 years, 7 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 3:02 PM, Mark Sapiro wrote: > On 7/7/22 1:36 PM, David Newman wrote: >> >> That was my first thought too. But there's nothing in that directory >> beginning with a hyphen, not even with the -a switch. > > What about > ``` > ls -la /opt/mailman/venv/lib/python3.9/site-packages/*-jango* > ``` > and if that shows nothing, > ``` > grep -r '-jango' /opt/mailman/venv/lib/python3.9/site-packages/ Nothing from the first command. The second command thinks '-j' is grep switch, and throws an invalid-option error: root@somehost:/opt/mailman/venv/lib/python3.9/site-packages# grep -r '-jango' /opt/mailman/venv/lib/python3.9/site-packages/ grep: invalid option -- 'j' Usage: grep [OPTION]... PATTERNS [FILE]... I *think* the command runs if I escape the hyphen: root@somehost:/opt/mailman/venv/lib/python3.9/site-packages# grep -r '\-jango' /opt/mailman/venv/lib/python3.9/site-packages/ But then that doesn't return anything. dn

3 years

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Guillermo Hernandez (Oldno7)

El 21/4/23 a las 14:29, Mark Sapiro escribió: > On 4/21/23 1:19 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I'm having troubles with Django and cannot access to web admin. >> >> I need to unhold a message while figures out what is happening. >> >> Searching the mailman cli help commands didn't help me. >> >> Anyone who knows how to unhold a message, please? > > > See this post > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Thanks, Mark. That could have been a life saver if I hadn't reset the UI. I'm writing it down for a future need. -- ___________________________________________ 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, 3 months

[MM3-users] Re: Template URI gets written incorrectly

by Mark Dale

On 2023-05-24 10:11, Mark Sapiro wrote: > On 5/23/23 16:51, Mark Dale via Mailman-users wrote: >> >> When I create a template, it writes the URI incorrectly into the template table in the mailman3 database and the list stops working. >> >> For example, it writes: >> >> http://localhost/mailman3/postorius/api/templates/list/markslist.lists.post… >> >> When I correct it like so, all is well: >> >> https://lists.postmark.io/mailman3/postorius/api/templates/list/markslist.l… >> >> Have I missed a config setting somewhere, or is this a bug with the older Debian Mailman 3.3.3 ? > > > You need to set > > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/' > > in your Django settings. Debian probably has set it to 'http://localhost/'. > Indeed that was it! Thanks very much Mark. /etc/mailman3/mailman-web.py Line 190: POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/'

2 years, 2 months

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

by William Oliver

On Sat, 2021-12-25 at 10:19 -0800, Mark Sapiro wrote: > On 12/25/21 7:13 AM, William Oliver wrote: > > > > 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? > > > If Postorius is working, recent versions show the SITE_ID in the > domains > view. I.e. after you added your domain you could have noted the > SITE_ID > and made the change in settings before deleting the example.com > domain. > > In any case, the django_site table in Mailman's database has the > information. > Thanks. Yep, I peeked at the database and there it was. That would probably been more efficient than randomly choosing numbers... billo

3 years, 7 months

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Odhiambo Washington

On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > I'm having troubles with Django and cannot access to web admin. > > I need to unhold a message while figures out what is happening. > > Searching the mailman cli help commands didn't help me. > > Anyone who knows how to unhold a message, please? > TBH, I find it a lot easier to fix the web UI than mess with the python shell :-) While you wait for @Mark Sapiro <mark(a)msapiro.net> to save you, you can be reading the following: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… -- 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]

2 years, 3 months

[MM3-users] Re: Permissions issue after upgrade of virtualenv

by Odhiambo Washington

On Thu, Mar 9, 2023 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/9/23 11:25, Odhiambo Washington wrote: > > > > Thu Mar 09 22:17:59.313459 2023] [core:error] [pid 15655] (13)Permission > > denied: [client 197.232.xx.xx:26574] AH00035: access to / denied > > (filesystem path '/opt/mailman/mm') because search permissions are > missing > > on a component of the path, referer: https://mm3-lists.kictanet.or.ke/ > > I did not change Apache config and I made sure that /opt/mailman is all > > owned by mailman:mailman. > > > > What am I missing? > > > X permission on one or more of /opt, /opt/mailman, /opt/mailman/mm > Wow. That would have taken me a decade to spot! The X permissions were missing on /opt/mailman. 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, 4 months

[MM3-users] Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

3 years, 4 months

[MM3-users] Re: clicking on a username when viewing a thread results in "Page not found"

by Ken Alker

Mark Sapiro wrote: > On 6/26/23 12:20 AM, Ken Alker wrote: > > If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? > This is a problem. That link goes to, e.g., > https://example.com/archives/users/<user_id>/. What do you get if you > strip the user_id and just go to what > https://example.com/archives/users/ translates to on your system? > You should get a page saying > Not implemented > > This feature has not been implemented yet, sorry. > > If you get a 404, there is an issue with your web server configuration > or maybe your top level urls.py. I get "Not implemented". I do not get a 404 error.

2 years, 1 month

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

by Helio Loureiro

Hi, I looked to the version I in the old installation: mysql> select * from alembic_version; +--------------+ | version_num | +--------------+ | 4bd95c99b2e7 | +--------------+ 1 row in set (0.00 sec) I set the same version on the new. Actually I loaded a fresh dump from DB to be sure it was the same. And now it is starting without errors. I guess that was it. Thanks a lot! Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:47, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 01:48, Helio Loureiro wrote: > > > > > But it is failing to start displaying the domain name from the previous > > machine. > > > > (venv) mailman@new-server ~ (v3.3.9)> mailman start > > Starting Mailman's master runner > > Generating MTA alias maps > > Traceback (most recent call last): > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", > > line 1969, in _exec_single_context > > self.dialect.do_execute( > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", > > line 922, in do_execute > > cursor.execute(statement, parameters) > > File > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", > line > > 153, in execute > > result = self._query(query) > > File > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", > line > > 322, in _query > > conn.query(q) > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 558, in query > > self._affected_rows = self._read_query_result(unbuffered=unbuffered) > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 822, in _read_query_result > > result.read() > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 1200, in read > > first_packet = self.connection._read_packet() > > File > > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", > > line 772, in _read_packet > > packet.raise_for_error() > > File > > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/protocol.py", > > line 221, in raise_for_error > > err.raise_mysql_exception(self._data) > > File > "/local/mailman/venv/lib/python3.10/site-packages/pymysql/err.py", > > line 143, in raise_mysql_exception > > raise errorclass(errno, errval) > > pymysql.err.OperationalError: (1054, "Unknown column > 'domain.alias_domain' > > in 'field list'") > > > The issue is your domains table and possibly others are not up to the > current schema. This should be accomplished by Mailman core running all > the necessary migrations in mailman/database/alembic/versions/. For some > reason, alembic's MigrationContext thinks the migrations have been run, > but they haven't. In the `mailman` database, the alembic_version table > has the version_num of the putative current version. The migration that > added alias_domain is dfe82cf73702_add_alias_domain.py. If there is no > alias_domain column in the domain table, alembic_version.version_num > should be a version older than 'dfe82cf73702'. > > I suggest querying the prior mailman database for the > alembic_version.version_num value and setting that in the current > database, assuming that that migration exists in > mailman/database/alembic/versions/. > > This may be sufficient, but there may be other inconsistencies depending > on exactly what you did. > > -- > 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, 7 months

[MM3-users] Re: How to see the admin password reset in docker with mailman3

by Jeremy Stanley

On 2023-04-06 14:38:41 -0700 (-0700), Mark Sapiro wrote: [...] > I can't answer that question, but you can set an admin user and > password with the django admin createsuperuser command. And for reference, here's how it's run at setup for the containers: https://github.com/maxking/docker-mailman/blob/b581310/web/docker-entrypoin… python3 manage.py createsuperuser --noinput --username \ "$MAILMAN_ADMIN_USER" --email "$MAILMAN_ADMIN_EMAIL" For a maybe more automate-able example, here's how we call it from outside the container via docker exec on our deployments: https://opendev.org/opendev/system-config/src/commit/ab0e6e1/playbooks/role… docker exec mailman-web bash -c \ "DJANGO_SUPERUSER_PASSWORD={{ mailman3_admin_password }} \ python3 manage.py createsuperuser --no-input --username \ {{ mailman3_admin_user }} --email \ '{{ mailman3_admin_email }}'" The things in {{}} are Jinja2 templated values we supply through Ansible, you could just replace them with whatever values are appropriate for your deployment. -- Jeremy Stanley

2 years, 3 months

[MM3-users] Re: not correct language in subject(s)

by Jens Günther

Am 23.05.23 um 00:54 schrieb Mark Sapiro: > For list welcome and goodbye messages to users, this is > https://gitlab.com/mailman/mailman/-/issues/993, fixed by > https://gitlab.com/mailman/mailman/-/merge_requests/1000 but since that > was fixed in Mailman 3.3.6, this would be a separate issue. I find those changes, but: in the merge request there is mentioned a /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po -> but I don't find a mailman-de.po ... is it maybe that? > Please be more specific than `all types of system mails`. Which specific > message subjects are not translated. It's exactly as mentioned in issue 993 the welcome and goodbye-messages that I don't see translated. But also other examples: - bounce-mail for the user that moderator approval is necessary (there the text is in german, but the reason is in english) - approval-mail for moderator (also text is in german, but subject and reason in english) Thank you for checking!

2 years, 2 months

[MM3-users] Re: Hyperkitty on Debian 12

by Markus Grandpré

short addendum: I was able to correct the following warnings when performing database operations on the mailman-web database: 1) /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. 2) django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. on our Debian 12 system in file </etc/mailman/mailman-web.cfg>: 1) Q_CLUSTER = { 'orm': 'default', 'retry': 360, 'save_limit': 100, 'timeout': 300, 'worker': 2 } 2) DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField' Best Markus Am 26.03.24 um 08:06 schrieb Markus Grandpré: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > > > Am 25.03.24 um 18:56 schrieb Mark Sapiro: >> On 3/25/24 07:58, Markus Grandpre wrote: >>> Dear list members, >>> >>> when following the instructions to migrate list archives from >>> Mailman21 to Mailman3 (see [1]), I face the following problem: >>> >>> # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 >>> /var/mailman21/testlist.mbox >>> python3: can't open file '/var/mailman21/manage.py': [Errno 2] No >>> such file or directory >>> >>> and have no clue, where to find the right <manage.py> file. The command >> >> >> This depends on how you installed Mailman 3. You may or may not want >> `python3 manage.py` at all. The required command could be something >> like `django-admin` or `mailman-web`. >> >> Also the `#` prompt indicates you may be running as root. Mailman >> related commands should be run as the Mailman user (could be `mailman` >> or `list` or ... depending again on how you installed Mailman). >> Running as root can create files owned by root that later can't be >> read by the Mailman user. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 4 months

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

by Stephen Willey Mats Mats

> On Feb 26, 2021, at 16:08:35 PST, Mark Sapiro <mark(a)msapiro.net> wrote: > > >>> The mail system >>> >>> <matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>: >>> host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address >>> (in reply to RCPT TO command) >>> Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal >>> X-Postfix-Queue-ID: E144B8BC3C5 >>> X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com >>> Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST) >>> >>> Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >>> Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >>> Action: failed >>> Status: 5.1.3 >>> Remote-MTA: dns; 172.19.199.2 >>> Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address > > I have no idea why Postfix is saying > `matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu` > is a malformed address, but this is a Postfix issue, not Mailman. > > Can you successfully post to `matsmats-mm3-test1 > @mm3.aca-aws.s.uw.edu` how about a `help` command to > `matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu` > Yep, all day long. A ‘help’ command succeeded. As did sending the confirm command to the -request address. oh, and looking further at the postfix logs the message was accepted by postfix but the error pops-up when postfix tries to pass it on. Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: connect from mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: E144B8BC3C5: client=mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/cleanup[5966]: E144B8BC3C5: message-id=<9B650420-A50D-4E25-8B5B-C696C388B7DA(a)selby.com> Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: E144B8BC3C5: from=<stephen.s.w.matsmats(a)gmail.com>, size=4575, nrcpt=1 (queue active) Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: disconnect from mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/lmtp[5967]: E144B8BC3C5: to=<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>, relay=172.19.199.2[172.19.199.2]:8024, delay=0.08, delays=0.05/0.01/0/0.01, dsn=5.1.3, status=bounced (host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address (in reply to RCPT TO command)) Feb 26 14:08:54 ip-172-31-18-222 postfix/cleanup[5966]: F0C468BC3C6: message-id=<20210226220854.F0C468BC3C6(a)ip-172-31-18-222.us-west-2.compute.internal> Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: F0C468BC3C6: from=<>, size=6993, nrcpt=1 (queue active) Feb 26 14:08:54 ip-172-31-18-222 postfix/bounce[5968]: E144B8BC3C5: sender non-delivery notification: F0C468BC3C6 Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: E144B8BC3C5: removed The mailman smtp.log show that the message came in but not much else. the mailman.log (and bounce.log) don’t show anything for that time. Feb 26 22:08:54 2021 (27) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Feb 26 22:08:54 2021 (27) Peer: ('172.19.199.1', 51934) Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) handling connection Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'LHLO ip-172-31-18-222.us-west-2.compute.internal' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> SIZE=4575' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) sender: stephen.s.w.matsmats(a)gmail.com Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'RSET' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'QUIT' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) connection lost Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) Connection lost during _handle_client() I’ve also reproduced this another address that is on an exchange server which is maybe a more vanilla example. steve > -- > 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: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210526 17:24]: > Mark Sapiro writes: > > > As far as I know, none of this has ever been migrated to Mailman 3. > > It has been migrated to Mailman 3, there were at least two related > GSoC projects, and the repo was on GitHub, but it's not at the same > URL now. Not sure if they've stopped using it, I haven't mentored > there for four or five years. Let me look around. https://github.com/systers/systers.github.io/wiki/Features-for-Mailman-3 seems to be existing but some links broken. https://github.com/khushboo9293/mailman/tree/Feature-CountUnsubscribers is a clone, the original code being moved or removed. However, looking through I don't see so many additions, especially not a membership adapter. I can't find the result of GSoC 2018 which should have worked on the membership adapter. That's so far as I can find. Andi

4 years, 2 months

[MM3-users] Re: set a new default for max_message_size

by Abhilash Raj

> On Apr 22, 2022, at 13:09, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 4/22/22 12:28, Paul Paulchen wrote: >> According to the answer of Mark you can change the "/usr/lib/python3/dist-packages/mailman/styles/base.py" - mlist.max_message_size. >> Now time went by, is there a possibility to use the mailman.cfg to set a new default? > > > No. It still is not configurable except by patching or creating a new style, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… It is however possible to create new Styles using Mailman plugins, without having to patch Mailman. We have an example style that demonstrates how to do that: https://gitlab.com/mailman/example-mailman-plugin/-/blob/master/example_mai… The repo’s README has more details on how to create and install the plugin. There is more documentation about plugins in Mailman Core’s docs: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… -- thanks, Abhilash Raj (maxking)

3 years, 3 months

[MM3-users] Re: Postorius not HTML-decoding < to "<" characters

by Ron / BCLUG

Mark Sapiro wrote on 2024-11-09 13:05: > This is a HyperKitty issue. Ah, I see, I thought it'd be on the display process. Does that mean the DB has data with mismatched tags in it? If so, will that require a query to fix? Interestingly, the quoted part of my message has < where my message has proper less-than and greater-than for the Apache tags. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… It's inconsistent with the archive rendering mode at lists.mailman3.org. I haven't currently got an instance that I can test on but will keep this in mind when the time comes to migrate. Should the rendering at lists.mailman3.org get modified, please share the procedure. Testing: less-than and greater-than around a tag: <Location /mailman/accounts/signup> Testing: less-than and greater-than around a tag in a quoted block: > <Location /mailman/accounts/signup>

8 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Clever idea Abhilash! Thanks El mié., 2 ago. 2017 a las 11:50, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > When you set DEBUG=False, Django doesn't serve static files because of > which you see only text and no styles. > > > http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… > > If you do set DEBUG=False, you need to serve the static pages somehow. > > Alternatively in you case, you can remove the part of the `settings.py` > which changes the Emailbackend when `DEBUG=False` so that you don't have > to worry about serving static files and still send out emails. > > On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > > For testing purpose I turned back to false the DEBUG var and everything > > started working fine with HyperKitty > > > > I don't understand... this is the trace when I click Login from Postorius > > to HyperKitty > > > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > > HTTP/1.1" 200 10950 > > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > > HTTP/1.1" 200 156657 > > > > > > What should I check? > > > > > > > > > > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > > HyperKitty is looking for some files in /static/CACHE/... but it > doesn't > > > > find them: > > > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > > > > You need to ensure you have a working sass compiler. As I said at > > > < > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >, > > > See the third bullet under > > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > > > Then you need to run commands like > > > > > > django-admin collectstatic --clear > > > django-admin compress > > > > > > > > > -- > > > 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

8 years

[MM3-users] Re: Announce Only List

by Stephen J. Turnbull

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

4 years, 11 months

[MM3-users] Re: [RESOLVED] REST API authorization failed

by Axel Rau

> Am 10.01.2022 um 19:30 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/10/22 1:58 AM, Axel Rau wrote: >> Is something wrong with my installed python packages? > > > The relevant code is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/wsgiapp.p… > > Does that match yours? I suspected the cryptography package for which I did a fake install, because there is no wheel for my platform and I could not build it. After an odyssey with strange cert errors while building the rust tool chain from their website, I finally managed to install it and could build the wheels for 36.0.1 and created the complete installation in a dedicated jail with ansible. Authentication now works and the website shows 'There are currently no mailing lists.‘ (-: After all these delays, I have only one day left to import 2 lists and to get them up. Thanks for all your help, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 years, 6 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hello, On Fri, Sep 30, 2022 at 08:53:38PM +0000, Andy Smith wrote: > On Fri, Sep 30, 2022 at 01:16:10PM -0700, Mark Sapiro wrote: > > I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which > > was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this. > > So that probably answers that then. Hmm, I wonder about the best way > to proceed. The next stable release of Debian will have something > that calls itself 4.0-2 and looks like it is fixed there: > > https://salsa.debian.org/python-team/packages/flufl.bounce/-/blob/master/fl… It seems that this package version can be downloaded and installed in Debian stable (bullseye): https://packages.debian.org/bookworm/all/python3-flufl.bounce/download It isn't recommended to mix packages from different releases of course, but the changes seem quite minimal and it fixes the problem for me. Cheers, Andy

2 years, 10 months

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

by Onyeibo Oku

> 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). Yaaay! The mailing-list is up and running. I am super grateful to the mailman support here in this list. Thank you so much Mark, Stephen J, and Eggert. I have more questions but I think it is better to start a new thread for that. Best regards Onyeibo

2 years, 6 months

[MM3-users] Getting connection timed out

by Stephen J. Turnbull

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 mail.simail.it is ignoring your mail server. This is not a Mailman problem. 1. Check to see if that server has a stated policy for "abusive" mail and some way of getting back in their good graces. 2. Check if your mail server is in the RBLs. Some of them are very aggressive about adding IPs and domains. 3. Try writing the postmaster at mail.simail.it. 4. Ask your subscriber(s) at mail.simail.it to write their postmaster. Steve

4 years, 2 months

[MM3-users] Re: File in /var/lib/mailman3/queue/bounces/

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [211212 05:41]: > On 12/11/21 6:29 PM, Andreas Barth wrote: > > > >in my local installation there is a file in > >/var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how > >to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in > >queue/bounces and now queue/shunt. > > > I suspect the issue is that bounce runner is not running. If you > grep Mailman's mailman.log for `bounces` I suspect you will see that > it has died and not restarted. You may or may not find additional > information in the log as to why it died, but in any case restarting > Mailman should start everything again. Thanks for your answer. Actually I didn't find anything in the log, but according to ps the bounce runner is actually not running. A restart of mailman fixed the issue for me. Andi

3 years, 7 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Ron / BCLUG

Mark Sapiro wrote on 2024-04-10 14:09: > I suspect you are not starting the services with your venv active. > What's in your mailman3.service and mailman3-web.service files? Thanks for the pointer! I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` somehow. I changed that to match the docs, did the `systemctl daemon-reload`, etc. but still had similar problems. I went through all my config files carefully, I wiped the static folder completely and rebuilt it, and I finally have the last piece of the puzzle in place and my web interface is working! I'm not sure which change actually fixed the issue though. (When looking at "Available lists" my header has "example.com" in the top-left corner?!?) Thank you! I think I need to backup what I have and do a clean re-install so I have a better grasp of what's going on with all these components. Mailman3 looks quite nice, gotta say! rb

1 year, 3 months

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

by Alain D D Williams

On Wed, Nov 27, 2024 at 12:42:41PM -0800, Mark Sapiro wrote: > On 11/27/24 12:18 PM, Alain D D Williams wrote: > > > > But it is not in table mailman3web.django_site > > > > Please how do I do this ? > > Add the domain as a site in the Django web admin UI. 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. I must admit to finding django daunting -- something that I know nothing about; I ran "mailman-web --help" and was non the wiser. I found the following which did not help either: https://docs.mailman3.org/en/latest/django-primer.html -- 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>

8 months

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/10/23 09:03, Christian via Mailman-users wrote: > > Again, that's only the post being delivered to Mailman. What comes after > that in the log? > > Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO > zarathustra.ccalternatives.org' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL > FROM:<christian(a)naturalintelligence.us> SIZE=3498' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: > christian(a)naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', > 55662) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: > redlatinleg(a)lists.ccalternatives.org > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during > _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: > LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: > ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) > handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> > b'LHLO zarathustra.ccalternatives.org' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> > SIZE=1139191' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 > 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT > TO:<medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org>' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: > medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 > 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during > _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: > LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: > ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) > handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> > b'LHLO zarathustra.ccalternatives.org' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> > SIZE=1155595' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 > 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT > TO:<medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org> > ' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: > medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 > 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during > _handle_client() There are no messages from the out runner process. it isn't running or it's hung. > And have you checked if Mailman's out runner is running? Note that if it > died for some reason and wasn't restarted or used up its restarts, > restarting Mailman core won't start it. You need to stop Mailman core and > then start it. > > OK I DID THAT Did the mail start flowing? > Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories? > > root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 > drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . > drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. > -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 > 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak > -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 > 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck > -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 > 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck > -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 > 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck > -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 > 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck > -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 > 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck > -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 > 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck > -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 > 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck > -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 > 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck > -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 > 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck > -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 > 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck > -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 > 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck > -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 > 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck > -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 > 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck > -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 > 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck > -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 > 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck > -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 > 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck > -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 > 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck > -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 > 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck > -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 > 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck > -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 > 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck > -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 > 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck > -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 > 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck Was this before or after you stopped and started Mailman core. If before, what is the situation now? Is mail being delivered? If after, is there still a 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak file in que/out? If this file is still there, it is hanging the out runner. Stop Mailman, move this file aside and start Mailman and see if the rest of the messages are processed. If that fixes it, there is something in that one message causing this. You can examine it with `mailman qfile`. That message arrived at Wed Mar 8 14:59:05 2023 (1678316345.5510073 is a time stamp) and is apparently causing the problem. If moving it aside fixes things, you can send it to me off list and I will try to figure out what the issue is. > root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 > drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . > drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. > -rw-rw---- 1 mailman mailman 447 Apr 26 2021 > 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck This is an old shunted message. The exception that caused it and a traceback were written to mailman.log on April 26 2021. If you still have that log, the exception and traceback will show what happened. In any case, `mailman qfile queue/shunt/1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck` will show the msg and its metadata. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Thu, Dec 26, 2024 at 1:27 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On December 25, 2024 2:01:27 PM PST, Odhiambo Washington via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > members --role nonmember LISTSPEC | wc -l > > 13 > > What do you get if you do > ``` > mailman shell -l LISTSPEC > ... > >>> len(list(m.nonmembers.members)) > (venv) mailman@eu:~$ mailman shell -l LISTSPEC 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 LISTSPEC mailing list In [1]: len(list(m.nonmembers.members)) Out[1]: 873 In [2]: -- 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]

7 months, 1 week

[MM3-users] Re: Help with fresh debian install

by Jonas Meurer

Mark Sapiro: > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> [...] >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. The Debian package uses user `list` for this. It also provides a command `mailman-wrapper` which takes care of running mailman commands as this user. It would be awesome if the upstream /usr/bin/mailman command could take care of this automatically, making the wrapper command obsolete. Cheers jonas

5 years, 9 months

[MM3-users] Re: Cron of Mailman notify is not working

by Shashikanth Komandoor

Thank you Mark Sapiro. I have tried as per your suggestion but failed unfortunately might be because of my improper setup. But I learnt one thing and fixed it and would like to share with you so that you may correct me if I am wrong or it would be useful for others. I observed that the "notify" subcommand can be run only while I am in the /var/lib/mailman/mailman directory where my mailman core is installed (through GITHUB). And moreover I installed all the components of the mailman using the root user only and so there is no mailman user on my machine. And hence I wrote the below entry in the crontab directly and found it is working fine. 00 08 * * * cd /var/lib/mailman/mailman; /var/lib/mailman/venv3/bin/python /var/lib/mailman/venv3/bin/mailman notify Please correct me if my analysis is wrong or please also suggest me if I could work it out in a more optimal manner.

5 years, 6 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Mark Sapiro: >> $ grep ^EMAIL settings.py >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 > > but is this perhaps overridden in a settings_local.py file? I don't have a local settings file. I cloned the suite from GitLab[1] master branch and modified the existing settings.py, based on Mailman's documentation. [1] https://gitlab.com/mailman/mailman-suite.git I just verified that EMAIL_BACKEND is not redefined anywhere: $ grep -r 'mail\.backends' . Binary file ./__pycache__/settings.cpython-38.pyc matches ./settings.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' ./settings.py:# EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' I commented out the "if DEBUG == True" lines, which explains match number three. As far as I can see, the mail backed definition for Django is as it should be. I could provide the differences between my settings.py and the Git HEAD version if you think that might help. -Ralph

5 years, 4 months

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

by Mark Dadgar

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. I really appreciate the support of this community in general and you in particular, Mark. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 5 months

[MM3-users] Re: CSV import for mass subscription

by Odhiambo Washington

On Fri, Sep 20, 2024 at 7:43 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/20/24 01:26, Markus Grandpré wrote: > > Dear list, > > > > we noticed that there is a function to convert the member list into a > > CSV format and save it.Therefore, we would like to know if the > > implementation of a CVS import for mass subscription is already planned? > > If not, how can we submit a corresponding feature request? > > The exported CSV is just a list of email addresses, and that could be > easily just pasted into the mass subscription form. > Why was it called a CSV? Appropriateness or future plans to download a true CSV? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months, 1 week

[MM3-users] Re: Post log?

by Mark Dadgar

On May 5, 2020, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/5/20 5:28 PM, Mark Dadgar wrote: >> Is there the equivalent of the post log from mailman 2.x available? > > It's not a separate log as it was in Mailman 2.1, but the information is > in the smtp log. For example, here are a couple of entries relating to > your post to which I'm replying: > > May 06 00:29:15 2020 (27320) > <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> smtp to > mailman-users(a)mailman3.org for 238 recips, completed in > 39.014487743377686 seconds > May 06 00:29:15 2020 (27320) > <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> post to > mailman-users(a)mailman3.org from mark(a)pdc-racing.net, 4429 bytes Ahh. I saw a ton of entries of the first type but missed the entries of the second type (it was a big file), which were the ones I needed. Thanks for the pointer. The script is up and running nicely now. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 3:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/18/20 2:23 PM, Mark Dadgar wrote: >> >> There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. >> > ... >> Could this somehow be related to my recent migration from sqlite3 to postgres? > > I think it's quite likely that that migration is involved and your > database is now corrupted in some way. Exactly how or in what way, I > don't know, but it seems likely to me that that's the issue. Oh good. Any thoughts on how to salvage ~20 years of list archives? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 1 month

[MM3-users] Re: MTA authentication and smtpd_sender_login_maps

by Jan Eden

On 2022-11-25 11:44, Mark Sapiro wrote: > On 11/25/22 11:00, Jan Eden via Mailman-users wrote: > > > > I obviously do not want to add an entry to the map file for each mailing > > list created by someone on the server. Is there a way to > > programmatically create a sender login map with Mailman? > > > You could modify mailman/src/mailman/mta/postfix.py to create a > smtpd_sender_login_maps file with the desired content or you could create a > script that creates the file using data in the generated > var/data/postfix_lmtp. If the latter, you might be able to create a plugin <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do…> > to run the script whenever a list is created or deleted Thanks! I feel rather stupid, but the obvious and really simple solution is a wildcard entry for the SASL user in controlled_envelope_senders: @lists.domain.org mailman_sender(a)domain.org Sorry for realizing this *after* bothering you. - Jan

2 years, 8 months

[MM3-users] Re: To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues

by Ron

On 2024-06-08 14:48, Mark Sapiro wrote: > The "PermissionError: [Errno 13] Permission denied: '//var/templates'" > is what it says. It is trying to create the absolute path /var/templates > and user mailman3 doesn't have permission to create a templates/ > directory in /var. > > I'm not sure why this is. It should be trying > /opt/mailman3/mm/var/templates. What does I experienced the fun of having /var being where mailman3 tried to create files & folders. Some combo of the following worked for me: mailman3.service Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var I explicitly set many / most of the other vars in that section too (i.e. lock_dir was one that also caused issues). This might be the Wrong Way, but it solved issues similar to the ones being discussed. rb

1 year, 1 month

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

by Joachim Schrod

Mark Sapiro writes: > > It is not the subscription that requires confirmation. It is the user's > email address. Even though the list's subscribe policy is open, a > previously unknown email address has to be confirmed. I assume that's the verification that one can turn off in Postorious `Mass Suscription' with the checkbox "Pre Verified". 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? I checked the options of "mailman conf" and "mailman-web help" (the latter seems to be Postorious' manage.py on my Debian system), but to no avail. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod <joachim(a)schrod.org>

7 months, 2 weeks

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

Hi Mark, This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. Now the email address that made this request does not show up at all in any of my logs. There is no record of them making a previous subscription attempt before the subscription policy was changed to moderate. Here are some observations: 1. The two occurrences of this happening was to Gmail users. 2. The two occurrences of this happening was when an email is being sent to the listname-subscribe@listdomain address. 3. This is only happening on 1 list. This may have no bearing on the issue but the list address of this problematic list is ******-owners@listdomain. I know there is an alias created for each list that is listname-owner@listdomain. Just throwing that out there. <princess-leia-voice>Help me Obi-Wan Sapiro. You are my only hope.</princess-leia-voice>

4 years, 9 months

[MM3-users] Re: Outgoing messages fro Mailman fails DMARC

by Henrik Rasmussen

> On 04/10/2018 06:53 PM, Mark Sapiro wrote: > > I'm not sure I understand what you are saying. Mailman's (both 2 and 3) > DMARC mitigations allow modifying the outgoing message in some or all > cases so the From: domain is the list's domain so the message won't be > dealt with by the recipient MTA according to the original From: domain's > DMARC policy. > > See <https://wiki.list.org/DEV/DMARC>;. Also, > <https://wiki.list.org/x/17891458> may be of interest. Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? Henrik Rasmussen

7 years, 3 months

[MM3-users] Re: How to hide sender completely

by Odhiambo Washington

On Wed, May 10, 2023 at 2:08 PM Roland Miyamoto via Mailman-users < mailman-users(a)mailman3.org> wrote: > Thanks, Mark, > > On 10/05/2023 01:50, Mark Sapiro wrote: > > Both this and all other incoming Received: headers are removed from > > posts to anonymous lists beginning with Mailman 3.3.4. > > X-MailFrom: headers are also removed as of Mailman 3.3.4. > > For clarifying. > > I am currently running > > GNU Mailman 3.2.1 (La Villa Strangiato) > > under Debian buster (10). > Seems I will have to upgrade to Debian bookworm (12) > if I want to stick with the deb package > and want complete anonymity to work. > > Or else dive into the virtualenv, which seems to be recommended option > anyway. > And virtualenv gives you more freedom. -- 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]

2 years, 2 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Alain D D Williams

On Thu, Jan 09, 2025 at 09:06:56AM -0800, Mark Sapiro wrote: > On 1/9/25 06:07, Alain D D Williams wrote: > > > > For an example see: > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > The above URL and also https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > and even https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/ all give a 500 > internal server error response. Sigh - try again. The 500 error happens several times a day. After 5 minutes it behaves as it should ... until it happens again some time later. I have not found out what is happening; nothing obvious in the logs, not high system load. I can live with it for now as I am busy elsewhere. -- 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>

6 months, 3 weeks

[MM3-users] Re: changing the main template for subscriptions and more

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210622 14:22]: > It isn't necessary to patch the source in this way. If you put the > modified templates in Mailman's var/templates/site/de/ directory, > ensuring that the Mailman user can read them, they will be used and > you won't have to patch the source every time you upgrade. Thanks Mark for pointing that out. I also should have mentioned that this would be the recommendation for operations, especially if mailman is install by some normal means (pip, distribution packages, etc). I perhaps took it for granted too much to never touch files coming out of automated systems by hand (except where the automated system caters for, e.g. debian conffiles), because that is a sure way to get into trouble with the next upgrade. (My mailman installation is the exception and not the rule, so unless you know what you're doing and have done similar before, just follow Marks advice) Andi

4 years, 1 month

[MM3-users] Re: AttributeError: ,> 'ReopenableFileHandler' object has no attribute '_stream'

by David Newman

On 11/19/21 10:04 PM, Mark Sapiro wrote: >> but then mailman3 wanted me to create a bunch of directories under >> /etc, even though $var_dir was set to /var/lib/mailman3. Things seem >> to go better, except for the confusion between lists/mailman >> ownership, when I set layout to "debian", which was the default. > > > It seems you may be using the Debian packages as our source has no > `debian` layout. Thank you for spotting that. I'd cloned a test server from a production machine that did have the Debian mailman3 package installed, something I should have checked first. The rest of the installation went OK. I'm using MariaDB and not Postgres, and that required a few deviations from the Virtualenv Installation documentation, but those tweaks things went OK from there. I have a follow-up question about post-installation setup but will start a new thread for that. Thanks again! dn

3 years, 8 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 23:31]: > I understand that, but even Debian sid has mailman3 3.3.3-1 and > mailman3-web 0+20200530-2 which are quite old for a package like > Mailman 3 which is still in active development. If we speak about unstable, that's something else. However, Debians next stable release won't release with mailman 3.3.3, as this package is removed from testing at the moment. I'd be happy if someone would update this package, however, I don't think I should get myself also involved there. ('Removed from testing' means: the current unstable package is considered not to be in shape to be released with the next stable release). So, if someone wants to get involved into Debian package maintainership with mailman3 (and related packages), that would be great, and I'm happy to support. As said, the most easiest way to get things fixed in Debian is by doing it. Andi

3 years, 4 months

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-27 07:08, Mark Sapiro wrote: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > > In that case, it's probably just an oversight. The instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html are an evolution > of a process that started with an obsolete mailman-bundler package, the > initial iterations of which are documented at > https://wiki.list.org/x/17891998 and prior revisions of that page. > https://docs.mailman3.org/en/latest/install/virtualenv.html is still a work > in progress. Ok – as long as I can consolidate all settings in one place for backup purposes (with symlinks, if need be), any layout is fine. Thank you, Jan

2 years, 8 months

[MM3-users] Re: RemoteUserBackend for Mailman3?

by Markus Grandpré

Dear Mr Spiro, thank you so much for your reply. On my Debian 11 system I don't find 'django_mailman3.lib.auth.fedora' in my Django settings in </usr/lib/python3/dist-packages/django/conf/global_settings.py>: # List of strings representing installed apps. INSTALLED_APPS = [] But I find: INSTALLED_APPS = ( ... #'django_mailman3.lib.auth.fedora', ... ) in </etc/mailman3# less mailman-web.py>. After commenting this line out I restarted the mailman3 application by restarting the apache2 web server. Unfortunately, the Fedora button is still visible on login site of mailman3 and a server error occurs when I click the button. Best regards, Markus On 27.03.23 19:22, Mark Sapiro wrote: > On 3/27/23 06:00, Markus Ludwig Grandpré wrote: >> >> Btw. how can I disable and remove the Fedora button from Maliman3's >> login page? > > > remove 'django_mailman3.lib.auth.fedora' from INSTALLED_APPS in your > Django settings. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

2 years, 3 months

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

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 04:26, Odhiambo Washington wrote: > > > > Okay. This is a bit off from my understanding. > > > > What is the cause and how do I mitigate it? > > The cause is the monthly hyperkitty update_and_clean_index job runs for > a long time, i.e. hours, because it is rebuilding the entire search > index so during the time it's running multiple hourly hyperkitty > update_index jobs are started and they are competing for the same lock. > > See > > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > for mitigation. What is the danger of replacing my settings.py with this one, seeing as it differs in a number of ways with mine? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Subscription requests = 0 ? Bug or feature?

by Odhiambo Washington

On Fri, Mar 24, 2023 at 6:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/24/23 04:15, Odhiambo Washington wrote: > > Even though I have a "Pending confirmation" request, the total entries > > under the subscription requests reads zero. > > I thought it should read whatever the total of (pending confirmation + > > pending approval) is. > > It only counts the requests waiting moderator approval because this is > the number requiring moderator action. It doesn't count the requests > waiting user confirmation. The only reason these are even available in > the moderator interface is so the moderator can discard them in cases > where the user has lost the confirmation email and can't confirm and > can't subscribe again because of the pending confirmation. > Thank you for the explanation. The logic is justified. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Yes, thank you! I’ll have a look into changing our backend to Xapian. Hopefully it will be trivial :) Marco van Tol > Op 16 jan 2024, om 09:20 heeft Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> het volgende geschreven: > > Mark Sapiro writes: > >> I have tested and I can confirm that with two lists in the same >> domain named `test` and `x-test` and with Whoosh as the backend >> searching the `test` list returns hits from both lists, but with >> Xapian as the backend, only hits from the `test` list are returned. > > Wow! Thanks, Mark! > > Steve > > _______________________________________________ > 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 mvantol(a)ripe.net >

1 year, 6 months

[MM3-users] Re: Sign and encrypt e-mail responses

by Markus Grandpre

Dear Mark, thank you very much for your response. Is there already a way to enable signing in Mailman v3.3.8 / v3.1 or does the signing support still have to be implemented? Best regards, Markus Grandpré Am 6/3/24 um 18:51 schrieb Mark Sapiro: > On 6/2/24 11:51 PM, Markus Grandpré wrote: >> Dear List, >> >> is it possible to sign and encrypt all e-mail responses from the Mailman3 server with a digital certificate? > > > Not without significant code changes. Signing alone should not be difficult. Encryption is more difficult if the > recipients are going to be able to read the encrypted mail without access to the server's private key. This would > require mail to be personalized, which digests currently aren't, and encrypted with the recipient's public key which > requires the server to have all those keys. > -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 1 month

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

by Wolfgang Bock

Hello Mark, I reconstruct the configuration problems regarding the creation of templates in mm3: I installaed mailman3 via the debian bullseye package(s). BTW: My experience is to install it step by step, not as mailman3-full, but as mailman-3, mailman3-doc, mailman3-web and python3-django-mailman3. In my case the full installation did not run clean, the step-by-step variant run clean. The debian bullseye variant comes with a nginx conf-file in /etc/mailman3/nginx.conf ... # This nginx config file is part of the mailman3-web package. # # This nginx configuration file is a vhost configuration. ... # Nginx SSL snippet. To enable it, please uncomment and update the server_name and the ... server { listen 443; listen [::]:443; server_name mailman.example.com; server_tokens off; # # ## Strong SSL Security # ## https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html & https://cipherli.st/ ssl on; ssl_certificate /etc/letsencrypt/live/mailman.example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mailman.example.com/privkey.pem; # ... The configuration "ssl on" is outdated as nginx -t comments. The actual configuration should be: /etc/nginx/ /etc/nginx/sites-available/nginx.lists.mydomain.ssl (and /sites-enabled) .... server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name lists.mydomain.com; # for example server_tokens off; ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; ... If you - as proposed in the mailman3 nginx.conf - include in nginx.lists.mydomain.ssl the following: .... upstream mailman3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0; } .... you cannot in include this in another vhost-nginx configuration (for example): /etc/nginx/sites-available/nginx.lists.mydomain_2.ssl as nginx -t says something like "no double entries please". So I put this in another file like /etc/nginx/sites-available/nginx.00.mailman3.upstream (and via symlink in .../enabled/...) and both nginx-domain-files work. The debian bullseye also serves a file mailman-web.py with an entry ... POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' ... As mentioned in a mail before that could not work: 1. letsencrypt doesnt serve an entry match for localhost. That floods your syslog. 2. "localhost" doesnt match with the nginx.conf-proposal. It must be something like /etc/mailman3/mailman-web.py .... POSTORIUS_TEMPLATE_BASE_URL = 'lists.mydomain.com/' .... In this combination the creating of templates on the postorius website works. 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. Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 2. November 2021 23:44 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: mailman3 postorius cannot retrieve template On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to > a suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because > django is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 > (175334) Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is > impossible to configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command > which includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- 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, 8 months

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

Hi Mark, Thanks for your answer and your lead > Le 16 mars 2023 à 18:34, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: > >> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read >> with open(self._lockfile) as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' >> —————————————————————————————————————————————————— >> CRON content: >> —————————————————————————————————————————————————— > ... >> # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured >> */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi > > Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. No, we don’t have > >> I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". >> When I run "/usr/bin/mailman gatenews" by hand everything is correct. > > Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. Their is no file with this name! listesman:~# ls -ld /var/lib/mailman3/locks/dbcreate.lck ls: impossible d'accéder à '/var/lib/mailman3/locks/dbcreate.lck': Aucun fichier ou dossier de ce type > > >> The questions I have are these: >> We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". >> What are they for? >> Can we delete them? > > They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. Ok, is done. We will see today if it continues > >> We have 2 files "master.lck..." dated from the day after tomorrow ! >> What is this date? >> Aren't these files the problem? > > > Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. Ok, that’s smart :-) > > -- > 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 plm(a)teledetection.fr -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Je n'ai jamais séparé la République des idées de justice sociale, sans laquelle elle n'est qu'un mot » Jean Jaures - 1887 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 4 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Alain D D Williams

On Thu, Jan 09, 2025 at 10:19:17AM -0800, Mark Sapiro wrote: > This is a long standing issue. See > https://gitlab.com/mailman/hyperkitty/-/issues/79 Thanks > > For an example see: > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > The style of this page is not standard. Is this a downstream packaged > HyperKitty? See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2025/1/ > for the standard page or > https://mail.python.org/archives/list/mailman-i18n@python.org/2024/12/ for > one with no posts. I installed from the Debian repositories as it seemed more straightforward than following the instructions on the mailman project. But it has left me running code that is ~2 years old. I might try to migrate at some point. -- 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>

6 months, 3 weeks

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

by Odhiambo Washington

On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 5:02 AM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > > > >> > >> > >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >> wrote: > >> > >> /bin/sh: sass: Permission denied* > >> > >> > >> > >> Did you check the permissions on your sass binary? > >> > > > > My mailman installed in /opt/mailman/mm > > > > find /opt/mailman/ -type f -name sass > > > > yielded nothing! > > > > Try `which sass` > root@gw:/usr/home/wash # su mailman3 (venv) [mailman3@gw /usr/home/wash]$ which sass (venv) [mailman3@gw /usr/home/wash]$ There is no sass. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Gilles Filippini

Andrew Hodgson a écrit le 18/04/2020 à 12:26 : > Mark Sapiro wrote: > >> On 4/17/20 4:51 PM, Abhilash Raj wrote: >>> >>> If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. > >> I created <https://gitlab.com/mailman/mailman/-/issues/699> for this. > > In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not. There is no need for these directories on the Exim side actually. You can safely drop the related checks from the Exim configuration [1]. [1] https://github.com/maxking/docker-mailman/pull/371 _g.

5 years, 3 months

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

by Franklin Weng

Franklin Weng 於 2019/10/24 上午8:05 寫道: > Hi Mark, > > Thanks for your reply. > > Mark Sapiro 於 2019/10/24 上午6:10 寫道: >>> Is there any other setting I should look at? >> The list's preferred_language setting (Postorius -> Settings -> List >> Identity -> Preferred Language. The list welcome message is encoded in >> Mailman's character set for the list's preferred_language. If this is >> English (USA), the character set is us-ascii. If it is set to Chinese >> (Taiwan), the character set is utf-8, and it should work. > However in my settings -> List Identity page I didn't see Preferred > Language option. > > https://nextcloud.slat.org/index.php/s/45tGaE7ALgAFQFK > > What may be possible wrong that I couldn't see Preferred Language > settings in the web interface? I got it. It is implemented in postorius 1.2.5 but my Debian buster contains 1.2.4-1 for now. Franklin

5 years, 9 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect: - I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org - Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' What am I missing, where do I have to set this value correctly? Thanks for the help! Jens. Am 08.06.23 um 01:57 schrieb Mark Sapiro: > On 6/7/23 14:13, Jens Günther wrote: >> >> The more important question would be, where :-) since I already >> checked if I can set it to something alse, I might need a hint where >> exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not >> stumble upon it. If you don't know it, no problem, let's just wait for >> somebody who does, thanks. > > > It's the EMAIL_CONFIRMATION_FROM setting in your Django settings. >

2 years, 1 month

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 19:09:20 CEST schrieb Mark Sapiro: > On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > > > All packages were upgraded fine. I applied the patch to > > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > > 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? > I'm guessing at some point you installed something which required you to > manually make this migration and that produced this conflict. Do you > have both 0017_alter_emailtemplate_language.py and > 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, > probably just removing 0017_auto_20220628_1132 will fix this? That's what I did in the meantime, and it works now! Thank you.

2 years, 9 months

[MM3-users] Re: Hyperkitty no longer archiving

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/21/22 16:33, Hirayama, Pat wrote: > > > > mailmansuite.log is full of: > > > > ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured > > > Set > ``` > MAILMAN_ARCHIVER_FROM = '172.31.0.1' > ``` > in your Django settings, or to accept any IP set > ``` > MAILMAN_ARCHIVER_FROM = '*' > ``` Hm. Pat wrote: > settings_local.py: > MAILMAN_ARCHIVER_FROM = ('172.18.8.14', '172.31.0.1', '172.31.0.2', '172.31.0.3', '172.31.0.4', '172.31.0.5', '127.0.0.1', '::1') where '172.31.0.1' is the second element. So we need to figure out where HyperKitty is getting its setting for MAILMAN_ARCHIVER_FROM. 1. Are there multiple copies of settings_local.py lying around? 2. Does settings.py have "from settings_local import *" in it? 3. Are there multiple copies of settings.py lying around? 4. What else may have changed in the migration? Any software upgrades in mailman, hyperkitty, mailman-web (or wherever the settings*.py are coming from)? Steve

2 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

The confirmation email says: Hello from example.com! Where can I change example.com to mydomain.com ???? Thanks El mié., 2 ago. 2017 a las 11:50, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > When you set DEBUG=False, Django doesn't serve static files because of > which you see only text and no styles. > > > http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… > > If you do set DEBUG=False, you need to serve the static pages somehow. > > Alternatively in you case, you can remove the part of the `settings.py` > which changes the Emailbackend when `DEBUG=False` so that you don't have > to worry about serving static files and still send out emails. > > On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > > For testing purpose I turned back to false the DEBUG var and everything > > started working fine with HyperKitty > > > > I don't understand... this is the trace when I click Login from Postorius > > to HyperKitty > > > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > > HTTP/1.1" 200 10950 > > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > > HTTP/1.1" 200 156657 > > > > > > What should I check? > > > > > > > > > > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > > HyperKitty is looking for some files in /static/CACHE/... but it > doesn't > > > > find them: > > > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > > > > You need to ensure you have a working sass compiler. As I said at > > > < > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >, > > > See the third bullet under > > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > > > Then you need to run commands like > > > > > > django-admin collectstatic --clear > > > django-admin compress > > > > > > > > > -- > > > 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

8 years

[MM3-users] Re: Mail control not given from Mailman 3 to postfix

by Shashikanth Komandoor

Thank you Mark for your help. Unfortunately, I felt myself dummy after seeing the mailman.log and the shunt queue. I did not find any clue from them. I did not see any log records based on that message id in mailman.log. There is a lot much of shunt queue but I don't see any file with the required message id. The same is the bad queue also. I find below two lines at that particular time stamp by when the log recorded in vette.log *Uncaught runner exception: sequence item 0: expected str instance, Header foundTypeError: sequence item 0: expected str instance, Header found* But I am not sure if the above lines are related to that missing message or not. I am using postgresql as database. FYI, if it brings an idea to you to help me. Could you please help me out how to trace further ? On Tue, Jul 7, 2020 at 9:12 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/6/20 11:07 PM, Shashikanth Komandoor wrote: > > > > Recently I observed a peculiar case. There is a list say > > testlist(a)lists.testdom.com has a non member say testuser(a)testdom.com > whose > > Moderation attribute is set to "Accept immediately (bypass all other > rules). > > > > This testuser(a)testdom.com has sent a mail to > testlist(a)lists.testdom.com > > and postfix of my Maliman 3 received the request and handed over to > Mailman > > at 0.0.0.0:8024 socket running on the same machine and the same is > logged > > in /var/log/maillog. > > > So it was received by Postfix and delivered to Mailman. > > > > Since the user has the moderation attribute set to Accept, the > > /var/lib/mailman/mailman/var/logs/vette.log also displayed "ACCEPT" on > > searching with the same message id. > > > And the post was accepted. (Apparently you override the path for > logging.vette in your mailman.cfg since the default logs these to > mailman.log) > > > > At this point, to my expectations, there should be 2 entries for this > > message id in smtp.log one for smtp and one for post. But I don't find > any > > log records with this message id in smtp.log and of course the mail is > not > > delivered even. > > > You don't find the message-id in the smtp.log for the incoming LMTP > because the message-id is not logged in this entry. It only logs the > actual LMTP commands and the envelope sender and recipient(s). > > You don't find the > > <messageid> post to testlist(a)lists.testdom.com ... > and > <message-id> smtp to testlist(a)lists.testdom.com for nn recips, ... > > entries because the post never got to that point in the processing > (those are logged when the post is delivered to the list members). > > > > Could you please help me out if I have missed any point or improperly > > understood the mail flow while using the mailman 3? > > There was probably some exception in processing causing the message to > be shunted. If so, the message is in the shunt queue and there is an > entry in mailman.log for the exception and shunting with a traceback > from the exception which will help in diagnosing the reason. > > -- > 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

5 years

[MM3-users] Re: Disable "confirmation emails"

by Jonas Meurer

Am 18.09.2018 um 23:25 schrieb Mark Sapiro: > On 09/18/2018 01:46 PM, Hagen Bauer wrote: >> >> even after a lot of google search I could not find a way to disable the >> Confirmation Mails like >> .... >> The results of your email command are provided below. >> >> - Original message details: >> ....... >> >> Is there a way to do this? I have users who would be irritated and I >> dont want them to recieve this > > > Where are you seeing these? There were changes in this area in Mailman > core v. 3.2.0 and I think these now should only be sent in response to > mail to the -request address that contains a command other than > (un)subscribe or confirm. I can confirm that these mails are sent in response to messages to -subscribe (not only to -request) with Mailman 3.2. I experienced the same as Hagen and I also wonder how to turn them of. Cheers, jonas

6 years, 10 months

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

by Odhiambo Washington

On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > /usr/local/include/sass > > > > That is the only thing found that is in the base system. > > And that's the one you want. What is it's mode? > 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 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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 = '******' What should I use in user and password?? Does Django use postfix to send the email??? 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

8 years

[MM3-users] Re: 120 gmail users removed from lists !

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/23/23 9:51 PM, Yvan ♞ wrote: >> Hello, >> Thanks for this answer, my problem is I'm on yunohost server and the >> update 3.3.9 is not available now. >> Any "handmaid" solution should be great. >It may be more disruptive than you want, but you can just set DMARC Mitigate unconditionally to Yes to apply DMARC mitigations to all list mail. Another thing which helped me a lot with Gmail bounces was setting VERP options everywhere in Mailman. I'm not sure what has made more of a difference, setting the DMARC to unconditionally apply the mitigations or setting VERP everywhere. Speaking of the new additions in Mailman 3.3.9, does anyone have a list of the domains Google are using which we can add to the list so we can disable the unconditional DMARC mitigations for all list posts? Its probably somewhere obvious on a Gitlab issue or similar, but haven't found it yet. Thanks. Andrew.

1 year, 9 months

[MM3-users] Re: Scheduled tasks

by Darren Smith

So I don't know how in the world we missed the qcluster and running that. Pretend I'm a python novice (that would be correct) - can you tell me what the ramifications of not running this? I have attempted to start the queues running, but it caused the entire machine to be consumed processing things. So I'm going to have to do this later at night again when our customers won't be as inconvenienced. This is one of those times that I wish that I had been able to understand everything deeper before we had to switch to the new system. Live and learn I guess. -Darren On Thu, Jun 7, 2018 at 9:57 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > I will take up any problems with the installation with the creator. > However, I was able to find and run some of the scripts this afternoon, and > I'm running some of the longer-running ones tonight while the usage is > lower. > > As for bogging down - I mean attempting to click on an email can take a > LONG time to render, and we frequently get 504 gateway timeouts (the calls > to hyperkitty are timing out). I am trying hard to figure out why this is > happening and to try to tune the system. I still suspect that there are > some inefficiencies with how the database is being used, or how the > database is doing things. > > I will take a look at qcluster, that was interesting info and hopefully it > can help me out. > > Thanks for your response, > > -Darren > > On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/7/18 9:59 AM, Darren Smith wrote: >> > All, >> > >> > I am looking more through the documentation of the Mailman Suite here: >> > >> > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf >> > >> > In section 3.2.5 it talks about the scheduled tasks that need to be run >> to >> > do "specific routine functions" in hyperkitty. >> > >> > I installed through the easy install script found here: >> > >> > https://github.com/iomarmochtar/mailman3_ei/ >> > >> > However, I can't find anything in THAT documentation that talks about >> these >> > cron jobs, and in fact the Mailman Suite isn't installed through that >> > script. >> >> >> That is a third party project. If you have issues with it, you should >> take them up with @iomarmochtar. >> >> >> > Can someone point me to any other documentation about the tasks that >> need >> > to be run on a continual basis? >> >> >> The section 3.2.5 you refer to tells you what needs to be set up in >> cron. For a list of the jobs tat are run, use >> >> django-admin runjobs --list >> >> >> . Our hyperkitty installation seems to be >> > bogging down more and more, and I am hoping that it will be as simple as >> > just running some jobs that haven't been on our radar. >> >> >> what do you mean by 'bogging down'? If you aren't doing so, setting up >> qcluster as in section 3.2.3 may 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 1 month

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Mark Sapiro a écrit le 11/03/2021 à 22:15 : > On 3/11/21 12:59 PM, Gilles Filippini wrote: >> Hi, >> >> I have this error message repeating endlessly into the mailman-web logs. >> The related list is an open one on which we receive spam sometimes. I >> understand these emails can me malformed and cause this error. How to >> deal with them? They can't stay forever at the hyperkitty door. > > > The message is queued at `var/archives/hyperkitty/spool/`. The files in > that directory are Python pickles. You can examine them with the > `mailman qfile` command and delete the spam ones. Looking at the offending message with 'mailman qfile', it appears it is a legitimate one actually, sent from an Android phone. Couldn't hyperkitty be a bit less strict? _g.

4 years, 4 months

[MM3-users] Re: Not able to start mailman server

by Stephen J. Turnbull

Mark Sapiro writes: >>>>> Kartheek wrote: > > I am trying to setup postorius using this website - I've used up all my bandwidth for now with the "can't send mail in Docker" thread, but FWIW Kartheek appears to be using Homebrew to manage third party packages on Mac, and in particular to install Python. I don't recall specifically with respect to Python, but I suspect that there's a "Homebrew system 'python'" (I know Homebrew does that with certain important programs that the Homebrew system depends on). That might very well confuse pip and other setup programs, since Homebrew likes to put stuff in places where you normally wouldn't find them to avoid conflicts (eg, multiple versions of Python). I can't be more specific about problems, and you'd hope that such stuff would "just work", but that might at least explain Mailman looking for stuff in "wrong places" (which might actually be right for Homebrew). Steve

3 years, 11 months

[MM3-users] Re: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Dadgar

On May 8, 2020, at 3:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > We tend to do this differently. For example, on mail.python.org which > currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends > about 135,000 individual messages per day from the two Mailman > instances, we define in /etc/postfix/master.cf > > 127.0.0.1:8026 > inet n - - - - smtpd > -o smtpd_authorized_xforward_hosts=127.0.0.0/8 > -o mynetworks=127.0.0.0/8 > -o smtpd_recipient_restrictions=permit_mynetworks,reject > -o smtpd_client_restrictions= > -o smtpd_helo_restrictions= > -o smtpd_sender_restrictions= > -o smtpd_data_restrictions= > -o receive_override_options=no_unknown_recipient_checks > -o smtpd_milters=inet:127.0.0.1:8891 > > Then port 8026 only accepts locally generated mail and only does dkim > signing (milter on port 8891) and essentially no other checks. > > Then in the [mta] section in mailman.cfg we only need > > smtp_port: 8026 Yep - I used to do something similar back when I was running dspam with mm2.1. This is a slightly more complicated to set up, but cleaner. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: troubleshooting hyperkitty

by Morris Jones

On 12/10/20 9:13 AM, Mark Sapiro wrote: > Morris Jones wrote: > >> So this part is all set, it would seem ... >> [archive.hyperkitty] >> class: mailman_hyperkitty.Archiver >> enable: yes >> configuration: /opt/mailman/var/etc/mailman-hyperkitty.cfg > > That should be [archiver.hyperkitty], not [archive.hyperkitty]. Is that the issue or a typo in your email? whew ... that was it. After fixing the config typo, my first test message generated errors in archiver.log because I'd intentionally broken the key. The second message worked, and the first one was delivered to the archive as well once the key was fixed. So now I'll see if I can discover a way to make the setup less susceptible to that typo for those coming after me. I sure I probably induced the failure by typing the config instead of copying and pasting. Thanks so much for the second pair of eyes. Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 7 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Brian Carpenter

On 3/26/21 6:13 PM, Mark Sapiro wrote: > Absolutely. At first MM3 wasn't processing bounces at all. A GSOC student did the bulk of the current implementation and we were happy to get that even though this piece was missing. We know we need it. If you don't think we're working fast enough, you can submit a merge request or dock our pay. I don't understand the sarcasm here at all. I am just trying to figure out what the PRIORITIES are from the Mailman 3 developers. That's all. BTW, I still haven't figured it out. It still doesn't explain why Postfix is not recording the delivery issues which I assume has nothing to do with Mailman 3. I see successful deliveries with Postfix and bounces with Mailman 3 core. I never seen that with Mailman 2 and Exim. They always matched. If you can help me to understand that with out the petty sarcasms then that would be great. If not, then ok. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

[MM3-users] Re: How to run 'manage.py update_index_one_list' command.

by Brian Carpenter

On 2/25/20 7:09 PM, Mark Sapiro wrote: > The issue is we don't in general know exactly how Django has been > installed or what the management command is, byt hyperkitty_import > should be able to figure out how it was invoked and use that. I did their installation for them basically using your setup listed at: https://wiki.list.org/DOC/Mailman%203%20installation%20experience I used a venv and pip to install the various components: pip install mailman pip install hyperkitty pip install postorius pip install mailman-hyperkitty -- 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/ Mailman 2 & 3 Hosting https://www.mailmanhost.com -- 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: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/3/20 6:43 PM, Mark Sapiro wrote: > On 11/3/20 3:32 PM, Brian Carpenter wrote: >> Hello Everyone, >> >> There was a message sent to a list that could not be archived by >> Hyperkitty for the following reason: >> >> >> WARNING 2020-11-03 17:20:54,507 800 hyperkitty.views.mailman Could not >> archive the email with message-id >> '<67BEBD75-B3DC-45E3-9C2F-55482F811238(a)ispdomain.com>': A string literal >> cannot contain NUL (0x00) characters. >> >> It looks like there was a problem with the email message itself. What >> causes such an error? > A null byte in the message body. > > I suspect the message is still queued in Mailman's > var/archives/hyperkitty/spool/ directory and is being retried with each > new post. You can examine the message with Mailman's `mailman qfile` > command. > Thanks Mark. I think the sender embedded a PNG file into the body of the message instead of adding it as an attachment. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error:

by Wolfgang Bock

Hello Mark, thanks for your reply. I'll check it out and report. Reagrds Wolfgang Am 18.11.2019 um 18:57 schrieb Mark Sapiro: > On 11/18/19 9:26 AM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> I got an errormessage via mail to root@[domain-01]. >> >> The complete text is attached in a utf-8-text-file. >> >> In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, >> 165, 166, 169, 187, 247, 251, 321 ....you can find links to different >> domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. > > You attempted to delete testliste02.[domain-01] via Postorius and > Mailman's REST API returned a 500 status. You may find more information > in mailman.log. > > I'm only guessing, but possibly this is because you posted to the URL > <https://[domain-02]/mailman3/postorius/lists/testliste02.[domain-01]/delete>. > I.e., you were accessing Postorius at > https://[domain-02]/mailman3/postorius/ (domain-02) and deleting a > domain-01 list. >

5 years, 8 months

[MM3-users] Re: Moving/cloning mailman3

by Dmitry Makovey

On 10/18/2017 11:10 AM, Mark Sapiro wrote: > On 10/18/2017 08:56 AM, Dmitry Makovey wrote: >> Hi, >> >> I am drawing a blank looking for documentation for mailman3 migrations. >> How can one dump existing settings for mailman and import it into >> another instance? > > > The Mailman 3 command 'mailman import21' is what does this > <http://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.ht…>, > however there are issues in that not all 2.1 settings are imported at > all or correctly and in at least one case on an announce only list, the > membership wasn't imported. > > I intend to work on this, but haven't got as far as even documenting the > problems, much less coming up with fixes. isn't above more about MM2 -> MM3 moves? I can't file .pck files for MM3 setup thus assuming there are some other files/commands I need to tackle to move MM3 from host to host. -- Sr System and DevOps Engineer SoM IRT

7 years, 9 months

[MM3-users] Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:29 PM, Thomas G wrote: > Yes, of course. > > Nginx and Apache works on the same server. (Nginx is stopped) > I would like switch to Apache to add in front of hyperkitty a ldap > connection.> I need to re-compile nginx for this feature. It's directly available > in apache with a module. Not sure the reason for this, the docs mention that what you had initially and also what Mark mentioned should have worked. Both of them seem to be supported syntax from the docs[1]. The only difference that I can see is quotes, not sure if that would affect things. [1]: https://httpd.apache.org/docs/2.4/mod/mod_alias.html#alias > > In fact, a tried directly to integrade LDAP with django > (https://gitlab.com/mailman/postorius/issues/132) without results.> > > > > > > > > Le ven. 19 oct. 2018 à 20:18, Abhilash Raj <maxking(a)asynchronous.in> > a écrit :>> >> >> On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: >> > Hi tried both. >> > >> > Same result. >> > >> > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET >> > /static/postorius/js/script.js>> > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) >> > Gecko/20100101 Firefox/60.0" >> >> >> And, you have verified that the files exist at `/opt/mailman/static` >> on your host?>> >> > >> > >> > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a >> > écrit :>> > >> > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: >> > > > Hi, >> > > > Currently, I use a nginx configuration for mailman. It's work >> > > > perfectly.>> > > > >> > > > I tried to do the same with Apache, but the statics files are >> > > > not>> > > > delivered (404). >> > > ... >> > > > <VirtualHost *:80> >> > > > ServerName mailing.ddd.fr >> > > > >> > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log >> > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined >> > > > >> > > > <Location /static/> >> > > > Alias "/opt/mailman/static/" >> > > > </Location> >> > > > >> > > > <Location /> >> > > > ProxyPass http://localhost:8000/ >> > > > ProxyPassReverse http://localhost:8000/ >> > > > ProxyPreserveHost On >> > > > </Location> >> > > > </VirtualHost>/ >> > > >> > > >> > > In Apache, location >> > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not>> > > appropriate for resources in the file system. >> > > >> > > Try >> > > >> > > Alias /static/ /opt/mailman/static/ >> > > >> > > not within a location block. >> > > >> > > -- >> > > 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/>> > > >> > _______________________________________________ >> > 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) -- thanks, Abhilash Raj (maxking)

6 years, 9 months

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Torge Riedel

Am 27.10.20 um 00:45 schrieb Mark Sapiro: > Note that the only times both the `postfix_domains` and `postfix_lmtp` > are updated together is when one of the `mailman` subcommands `aliases` > or `start` is run. Are you possibly running both these at the same time > causing some kind of race condition? Hi Mark, thanks for your answer. First of all I ran a 'systemctl restart mailman', which now gives expected timestamps via 'stat' on the four files. I then checked what could cause a kind of race condition (there is only one server involved): - I have logrotate configured for daily rotate (which includes a 'systemctl reload mailman') - I have the cron jobs configured for mailman-web So it could be that cron jobs for mailman-web are running at the same time when mailman-core is asked to reload after log rotation. Could this lead to a race condition? But as you said: A 'reload' should not update the files. Kind regards Torge

4 years, 9 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-02-16 11:06:40 -0800 (-0800), Mark Sapiro wrote: [...] > Yes, that doc really isn't appropriate for your purpose, but it's > the only one I could find on Django sites. Most of what it talks > about is for more complex situations than ours and whatever bits > are relevant are already done in Postorius/HyperKitty. Sorry for > leading you astray. [...] Please don't apologize, you've gone well out of your way to be helpful and it's very much appreciated. I've been on the other side of this conversation for plenty of projects and understand the challenges. > I don't think Django's docs address the simple task of adding a > site. While part of me wants to find that hilarious, I can't honestly claim the projects I work on are any better in that regard. Your latest recommendations have me un-stuck and left with a far better sense of how this fits together now. -- Jeremy Stanley

2 years, 5 months

[MM3-users] Re: MM3 generates long lines?

by Jörg Schulz

Maybe the solution would be to change the calls to email.sendmail like: results = self._connection.sendmail(envsender, recipients, msg.as_string(maxheaderlen=XXX) ) ? This error comes from some ios mail users after a number of answer/reply sessions; the References: in the header grow. Is this of any help? Am 09.02.24 um 23:07 schrieb Mark Sapiro: > On 2/9/24 13:50, Jörg Schulz wrote: >> did you ever find a solution to the issue "maximum allowed line >> length is 998 octets, got ... "? In the last days, I had some apple >> iphone originating emails in longish email threads where this happened. > > I'm not aware of a solution other that fixing the email clients involved. > >> Can the prototype archiver be activated additionally to hyperkitty or >> only as alternative? In the latter case: (how) can I archive the >> messages in question manually afterwards? > > It can be active additionally to hyperkitty. There's nothing that > prohibits all enabled archivers from being active on a list. >

1 year

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 18/9/21 20:42, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 18/9/21 20:27, Mark Sapiro wrote: >> from mailman.interfaces.action import Action >> def moderar(mlist, member): >> memb = mlist.members.get_member(member) >> if not memb: >> print('{} is not a list member.'.format(member)) >> return >> memb.moderation_action = Action.hold >> print('{} moderation_action set to hold.'.format(member)) > Just a one more silly question: Where do I can find the diferent values that memb.moderation_action can take? (I want to prepare the "unhold" script too) Thanks in advance. > That completely did it. The problem about finding the module was > completely gone when I made a soft link in the same directory where > mailman command is (in /usr/local/bin, for your info). > > Thank you very, very much. > > _______________________________________________ > 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, 10 months

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

by Yvan ♞

Yes, always this folder file problem, if I create the folder, when trying install answer is "mailman allready installed" https://paste.yunohost.org/raw/avaweyiqom Still searching... But I'm really not an expert... Yvan Le 12/03/2022 à 21:32, Mark Sapiro a écrit : > On 3/12/22 08:38, Yvan ♞ wrote: >> Yes it's debian and I have root access but it's a more "user >> friendly" server release. >> I tryed this but it block >> https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md >> >> https://yunohost.org/en/administrate/whatisyunohost >> Sincerely > > I don't read French very well, but your original logs at > https://paste.yunohost.org/raw/xiqoyajegi and > https://paste.yunohost.org/raw/hujesebita show installation failing > because it fails to create /etc/mailman3/mailman.cfg. > > This is either an issue with the Debian package or the YunoHost > installer or an incompatibility between them. > > I would go first to YunoHost for help and then to Debian if necessary. >

3 years, 4 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Andrew Hodgson

Mark Sapiro wrote: >On 1/1/21 4:41 PM, Andrew Hodgson wrote: >> I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? >I have attached a script that will delete users from Django's user >database (the auth_user table) if there is no Mailman user with the >Django user's email address or if there is a Mailman user but it's not a >member, nonmember, owner or moderator of any lists. Thanks for this. >The setting DELETE_MAILMAN_USER controls whether it will also delete the >corresponding Mailman user that's not a member, nonmember, owner or >moderator of any lists. If set to True, it will. I did set this to true. The majority of users existed only in Django but around 20 existed in Mailman as well and looked like old addresses. Thanks again. Andrew.

4 years, 7 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 2024-06-23 03:24, Mark Sapiro wrote: On 6/22/24 20:04, Mark wrote: >> >> Oh? I was indeed assuming that 0 meant unlimited. The threshold was >> set at 0. >> My thinking was that meant the file size was not a factor in >> determining when the digest was sent and that the sending would be >> triggered by the daily cron. >> So my understanding of what you are saying is: if the threshold is set >> very large, say 100,000 kB - then a digest will be be sent by the >> daily cron even if it is smaller than 100,000 kB. > Correct. If Send Digest Periodically is Yes, any accumulated digest > will be sent when `mailman digests --periodic` runs, regardless of > size. Mark - Thank you very much for setting me straight on this. I had been stumbling around in the dark for days. With the threshold set extremely high, the daily digests are on track and list members are happy again. Best, Mark

1 year, 1 month

[MM3-users] Re: Mailman3 via Docker and NGINX

by brian＠emwd.com

Abhilash Raj wrote: > On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote: > > On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > > > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe > > the installation went fine and running "curl > > http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will > > be using exim and nginx with this installation. > > ... > > > location / { > > > include uwsgi_params; > > > uwsgi_pass 172.19.199.3:8000; > Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for > uwsgi protocol. > > See the docs[1]. > > [1]: https://github.com/maxking/docker-mailman#setting-up-your-web-server Thanks Abhilash. It is working now. FYI, I made the change directly in the nginx.conf file. I got rid of trying to use the conf.d/sitename.conf file. I now move on to getting exim to work. If I need help, I will start a separate thread. Brian

6 years, 7 months

[MM3-users] Re: mailman-web migrate fails: KeyError: 'django'

by David Newman

On 12/6/21 7:25 PM, Mark Sapiro wrote: > On 12/6/21 6:10 PM, David Newman wrote: >> Following the venv installation docs on a Debian 10 system, the >> command "mailman-web migrate" fails with a "KeyError: 'django'" error. >> >> Output pasted below [1]. > ... >> from mistune.scanner import escape_html, escape_url >> ImportError: cannot import name 'escape_html' from 'mistune.scanner' > > > You need to install > https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 or downgrade > mistune in your venv with > > pip install mistune==2.2.0rc1 Thanks for this. I applied the one-line fix by hand from 379 and the command now runs clean. I first tried the 'pip install' command but it returned this error: venv) mailman@somehost:~ $ pip install mistune==2.2.0rc1 ERROR: Could not find a version that satisfies the requirement mistune==2.2.0rc1 (from versions: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.4, 0.4.1, 0.5, 0.5.1, 0.6, 0.7, 0 .7.1, 0.7.2, 0.7.3, 0.7.4, 0.8, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 2.0.0a1, 2.0.0a2, 2.0.0a3, 2.0.0a4, 2.0.0a5, 2.0.0a6, 2.0.0rc1, 2.0.0) ERROR: No matching distribution found for mistune==2.2.0rc1 Thanks again. dn

3 years, 7 months

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Sunday, November 5, 2017 12:09:53 PM EST Mark Sapiro wrote: > When you run > > mailman info > > it will report among other things the location of 'config file:'. The > user who owns this file is the user that should run the > > mailman digests --send > > command. I.e., it should be in that user's crontab or in something like > '/etc/cron.d/mailman' with that user specified. > > Also see <https://gitlab.com/mailman/mailman/issues/436>. /etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, my laptop, and my new Mailman box. ALL files in /etc (except links, which are lrwxrwxrwx and I didn't check what they point to) are owned by root.root or owned by root.<other> and not group writable, except one, the directory /etc/ mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are you saying that Mailman should be able to change its own config file? Pierre -- Don't buy a French car in Holland. It may be a citroen.

7 years, 8 months

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Thu, Dec 26, 2024 at 7:24 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/25/24 15:02, Odhiambo Washington via Mailman-users wrote: > > > > (venv) mailman@eu:~$ mailman shell -l LISTSPEC > > 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 LISTSPEC mailing list > > In [1]: len(list(m.nonmembers.members)) > > Out[1]: 873 > > > Then it appears that your version of mailman/commands/cli_members is > broken. Compare it to > > https://gitlab.com/mailman/mailman/-/raw/master/src/mailman/commands/cli_me… That's right. This one does what is expected. -- 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]

7 months, 1 week

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

by Fabian A. Santiago

On October 25, 2017 7:53:39 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/25/2017 01:08 PM, Fabian A. Santiago wrote: >> Hello, >> >> I have mm3 up and running via docker (courtesy of >maxking/docker-mailman) but when i send an email to my test list, it >bounces back claiming user unknown. it states: >> >> <"lmtp:[172.19.199.2]:8024"@>: unknown user: >> "lmtp:[172.19.199.2]:8024" >> >> looking at the email source, it seems as though the message is trying >to be delivered to: >> >> Final-Recipient: rfc822; "lmtp:[172.19.199.2]:8024"@<my email >server's FQDN> >> Original-Recipient: rfc822;test123@<my list's email domain> >> >> all of various alias transport maps are defined in postfix's main.cf. >not sure where to go from here. does anyone have any clues? > > >For the docker image, the tables have to be defined in Postfix as >regexp: tables. Are they? Yes they are. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 9 months

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

by Guillermo Hernandez (Oldno7)

On 18/2/21 11:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > 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? > > Forget this, I've just found how to do it. Selecting by "key/context" > and the name of the file seems to do the trick. Done. Now the Weblate translation of templates is consistent with the gitlab src repository.

4 years, 5 months

[MM3-users] Re: Hyperkitty

by Onyeibo

On Mon, 30 Jan 2023 14:43:54 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 13:17, Onyeibo wrote: > > > > The mails don't have that header. I suspect I may have to > > investigate SELinux. > > > I think it's unlikely a SELinux issue unless you mean it's an issue > writing the log, but if there are any entries at all in mailman.log, > that should be OK. > YES. There were entries in the log. They are good entries. There were no alarming entries. I was right. Selinux was preventing Python {name connect} to a mailman path. After resolving that, all Archives built/updated. Now I see entries in the log about receiving mails and archiving them. I also see the archived messages via Hyperkitty web interface. Super! However, I no longer receive my own message to the list. That was working before. The post arrives at the List and gets archived but I don't see it via my mail client -- looks like Mailman is now recieving but not posting back to the subscriber. Strange

2 years, 6 months

[MM3-users] Re: Spam sent to list owner causes bounce increment for list owner

by Allan Hansen

Hi Mark, Thank you for the explanation, and it all makes sense. I prefer your verp_probes solution, as I do prefer to have my list work concentrated in one place. I did have 5 bounces on the list - I guess a lot of spam is happening due to the holidays. I noticed a big uptick myself. Thanks again, Allan > On Dec 18, 2023, at 10:30, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 12/18/23 9:59 AM, Allan Hansen wrote: >> Hi all, >> Someone sent a spam message to the list owner (me) of one of my lists. Then I got booted from the list. >> The scenario in more detail: >> The list server forwards the message to me, as I’m the list owner. This message is sent from <list>-bounces+hansen=rc.org(a)list.rc.org to hansen(a)rc.org. >> My service provider’s spam filter rejects the spam (correctly) in a message and informs the list server. >> The list server sends a message to <list>-bounces+hansen=rc.org(a)list.rc.org (the fake sender) saying that the message to hansen(a)rc.org (the recipient) could not be delivered because it was spam. >> The list server also blames hansen(a)rc.org (me) for the bounce and increments my bounce score, which, to me, is unfair. >> So I wonder: >> Is the Mailman host at list.rc.org at fault for not catching the spam before it reaches the list server? (One could argue that) > > Depends on what kind of spam filtering if any you have on incoming mail to list.rc.org. > >> Is my rc.org service provider at fault for sending the bounce message to the server instead of the to the original sender? > > Absolutely not. The envelope sender of the mail was set by Mailman to <list>-bounces+hansen=rc.org(a)list.rc.org in order to enable automated bounce processing. rc.org correctly sent the bounce to the envelope sender. > >> Is Mailman at fault for thinking that the bounce message was caused by a list message FROM me, instead of a bounced message TO the list owner? > > Arguably, yes, but not based on FROM. FROM has nothing to do with it. The message was sent TO you so if it bounces, it is a message to you that bounced, so you are the one bouncing this message. All Mailman knows is a message was sent to you and it bounced so it's your address that is bouncing. It doesn't matter whether this was a post to the list that bounced or a message to <list>-owner. A bounce is a bounce. > > Note that this list's bounce processing is very aggressive. If you got removed from the list after one bounce, the list must have Bounce score threshold = 1 and Bounce disable warnings = 0. You might consider adjusting these. > > There is an easy fix for this. Set `verp_probes: yes` in mailman.cfg. Then when your bounce score reaches threshold, instead of disabling/removing you, Mailman will send a probe message to you. It will only disable/remove you if the probe bounces which it presumably won't. > > Another avoidance would be to use an address for the owner which is not the address of a member. Then if the owner address bounces, nothing is done because the bouncing address isn't a list member. > > -- > 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 hansen(a)rc.org

1 year, 7 months

[MM3-users] Re: Archiver "prototype" and disabling archiving at all

by Torge Riedel

Am 24.03.19 um 16:49 schrieb Mark Sapiro: > On 3/24/19 5:40 AM, Torge Riedel wrote: >> in the settings of a mailing list I can choose two archivers: >> "Hyperkitty" and "prototype". What is this archive "prototype" and how >> can I disable/remove/deinstall it? And how can I disable archiving at >> all, so no archiver can be chosen in the settings. > > The prototype archiver stores messages individually in > var/archives/prototype/LIST_NAME/. > > You can disable the prototype archiver by putting > > [archiver.prototype] > enable: no > > in your mailman.cfg. To disable all archiving, just remove all the > [archiver.*] sections from your mailman.cfg or set them to 'enable: no' > > Hi Mark, thanks. This disabled the archivers, but there is still the "Archives" link on top of the page. Is it possible to remove it? Cause there is nothing to see there. I tried commenting "'hyperkitty'," in INSTALLED_APPS, but then I got a 500.

6 years, 4 months

[MM3-users] Re: Topics - Tags

by Mark

On 2024-03-23 06:36, Mark Sapiro wrote: > On 3/21/24 21:10, Mark wrote: >> Hi, >> >> I'm reading the docs on "Message tagging" >> (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) >> as saying shell access is needed to: (a) enable topics, and (b) write >> the keywords. >> >> In Mailman 2 there is an Admin web UI for "Topics". Is there such a >> web UI that can be enabled in Mailman 3 so that the list owners can >> create topics (tags) in their lists? > > > At this point, topics are not exposed in REST. Managing them via > Postorius first requires updating the REST API to read and set the > topic attributes and then updating Postorius to display/set them. > > Further, there is currently no implementation for list member topics > of interest either in Mailman core or the REST API. I.e., there is no > way for a list member to indicate topics of interest. > Thank you for this information Mark. Best, Mark

1 year, 4 months

[MM3-users] Re: Remove old bounces in bouncedir

by Stephan Krinetzki

Mark Sapiro wrote: > On 3/10/22 00:31, Stephan Krinetzki wrote: > > Mark Sapiro wrote: > > If you are referring to messages in Mailman's bounces queue, if these > > are not processed and removed within 15 minutes of arrival, Mailman's > > bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > > > The process it self is there > > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > > > > I don't understand what's happening. If the bounces runner is processing > it's queue, those .pck files should be processed and deleted. > Are there errors in /opt/mailman/var/logs/mailman? Nope. Only the daily info, that it runs. For today: Mar 14 03:15:34 2022 (21507) Task runner evicted 25336 expired pendings Mar 14 03:15:43 2022 (21507) Task runner deleted 3696 orphaned workflows Mar 14 03:16:09 2022 (21507) Task runner deleted 7965 orphaned requests Seems to be okay > If you examine (some of) those files with mailman qfile do you see > anything strange? Nope. Just regular Bounce Files. > Is there an ownership/permissions issue? Sometimes people run Mailman or > some Mailman command as root and things get owned by root and then > when Mailman is later run as mailman it can't delete or maybe even > read them. Nope: /opt/mailman/var/queue/bounces ls -altrh | head total 12G -rw-rw---- 1 mailman mailman 37K Jan 5 09:51 1641372708.3212914+fc901998d5e2ace166db31ace6d77081b0c7650c.pck -rw-rw---- 1 mailman mailman 42K Jan 5 09:52 1641372768.1659493+7afbcddc270547485732252874adcc27e04c9983.pck -rw-rw---- 1 mailman mailman 42K Jan 5 09:52 1641372768.2633681+73c527870449492689fd30502b73f455a191701e.pck -rw-rw---- 1 mailman mailman 7.7K Jan 5 09:58 1641373138.119037+2d5dd400e989db3303517b900d7f2b312d4cd7b5.pck -rw-rw---- 1 mailman mailman 7.7K Jan 5 09:58 1641373139.585048+ee824dec757735ef8bd8139ee0cd858cc7c92606.pck -rw-rw---- 1 mailman mailman 288K Jan 5 09:58 1641373139.846666+d75af26011eb1a8ef5673d9ee13c5425daec2bd4.pck -rw-rw---- 1 mailman mailman 288K Jan 5 09:59 1641373140.024808+be60d1d97590d77eaec46751524d1bfe7a2f9ee7.pck -rw-rw---- 1 mailman mailman 289K Jan 5 09:59 1641373140.8432257+678f545d176008a5483b8bc6747aebc2b84a7f4e.pck -rw-rw---- 1 mailman mailman 288K Jan 5 09:59 1641373141.505824+c253072ebeb3f07b2b455725ace225abdd621b22.pck As you can see, there are old messages (not 3 years old, but some months old) > > If you are referring to bounce messages in the message store > > (var/messages/), there have been issues with those not being removed, > > but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. > > Is the size of the /opt/mailman/var/messages directory very big? Nope, it's 1.9GB at the moment. I don't think that's big. Is there anyway to run the bounce runner manually and get the debug output of it?

3 years, 4 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/20/22 07:54, Rainer Herbst wrote: > > The user suggested that the problem is caused by a line containing only > > "-- " somewhere in the text, but I can not confirm this. This is very unlikely. A very large portion of the mail processed at Mailman sites has "-- " in it because that is the conventional "start of .signature" marker, and much of that is multipart and even signed nowadays, yet we've never seen a problem with it. > > Please find enclosed the refused mail (anonymized). > > That message has no defects. In particular, it has no Content-Transfer-Encoding in the header of any multipart part, which is the defect reported before. I guess there's no list of defects either in the returned message or in the MTA logs? It seems strange that the message has no Received headers. Is this normal for aip.de address to aip.de address mail? Or is it a sent file copy of the sender or something like that? Steve

3 years, 3 months

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

by Darren Smith

"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, 3 months

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

by Simon Hanna

On 05/12/2016 09:26 PM, Barry Warsaw wrote: > On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: > >> It is the intent that Postorius will eventually expose all these >> settings. We're not there yet. At present you could possibly do this by >> interacting with mailmanclient, although I'm not certain the settings are >> exposed there. > > I'm not sure if they're exposed in mailmanclient, but they are exposed in the > core's REST API, on the member resource. It's the `delivery_mode` attribute > and it takes as legal values one of 'regular', 'plaintext_digests', > 'mime_digests', and 'summary_digests' (IOW, the enum item names for the > DeliveryMode enum). They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > Cheers, > -Barry > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

9 years, 2 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 18:05 schrieb Mark Sapiro: > On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: >> >> Right now everything is running as root (except for Apache). I realized >> too late that I should've used a mailman user. Could that be the reason >> for the issue? > > Since you have determined it was a browser issue, that probably isn't > the reason, but running Mailman as root is a bad idea in general for > security reasons. Thanks, I'm aware, and I'm not going to on a production system. This installation is just a trial run. > I don't know if it's relevant or not, but I have just recently had > issues with Firefox not working properly on two different (not mailman) > web sites, and these issues were fixed by clearing cookies and cached > data from the affected sites and restarting Firefox. I can confirm that that worked in my case as well.

4 years, 11 months

[MM3-users] Re: cache files?

by Dave McGuire

On 7/12/21 10:45 PM, Mark Sapiro wrote: >> Hi folks. I'm seeing quite a few .css files, thousands of them >> totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. >> Some of them date back to when I set up the mm3 instance a few years ago. >> >> Is this expected, or am I missing a cron job or something to clean >> them up? > > This is not expected. I don't see it on the instances I manage. > > In the `static` directory, I see > ``` > $ du -h -d 1 > 1.7M ./admin > 12K ./facebook > 68K ./django_extensions > 4.0K ./browserid > 68K ./django-mailman3 > 2.6M ./postorius > 12K ./paintstore > 1.6M ./rest_framework > 5.2M ./hyperkitty > 404K ./CACHE > 12M . > $ find -type f|wc > 401 401 18253 > ``` > > I think when you run the Django admin `collectstatic` command, you need > to specify the `--clear` option. Interesting, I know nothing of that command. Is that something that should be run periodically? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years

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

by Guillermo Hernandez (Oldno7)

On 6/8/21 19:33, Mark Sapiro wrote: > On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> Thanks. Now it's no showing errors (and nothing at all) but >> apparently it does nothing. The non mebers of the list (the few that >> remains: I've been deleting one at a time from the web) aparently >> still are there.. >> >> Knowing the correct procedure will ease me to try tomorrow with a >> clean head. > > It doesn't report anything, and if you don't commit() or exit with > control-D, any changes will be rolled back. I think I did a typpo. (forgot to add "()" after the "commit" sentence). And exit with quit() maybe not helps. I've done it exactly as you wrote it and it worked like a charm. Thank you very very much > > What does > > list(m.nonmembers.members) > > show before doing the unsubscribe() and commit() and then what after? >

3 years, 11 months

[MM3-users] Re: Is logging.subscribe working in /etc/mailman.cfg?

by Alan So

Mark Sapiro wrote: > On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote: > > I have put the following in /etc/mailman.cfg and restart mailman. An > > empty file can be created but nothing can be logged when admin or non-member > > subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in > > mailman.log and smtp.log. Thanks. > > > > [logging.subscribe] > > path: subscribe.log > > level: debug > > The above is correct. As far as not seeing things in the log, very > little is logged in the subscribe log. Only (un)subscription requests > held for moderator approval and moderator approval of held unsubscribes > but not subscribes. > > In other words, unless your list's subscription police includes > 'moderate' nothing will be logged in subscribe.log. It looks like there is only a subscription policy but no unsubscription policy. I can't find anything even by exporting the settings using Python mailman client. Is it correct?

6 years, 7 months

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-26 22:59, Mark Sapiro wrote: > > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > > files when using the virtualenv installation instructions > > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, > not mailman-web. If you want, you could put mailman-hyperkitty.cfg in > /etc/mailman3/ by putting > ``` > configuration: /etc/mailman3/mailman-hyperkitty.cfg > ``` > in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really > belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. I see. But the mailman.cfg is placed in /etc/mailman3, and this file also belongs to the core, doesn't it? In any case, I changed the configuration parameter for [archiver.hyperkitty] as you suggested and all settings are in one place now. I will post two more questions to this list today, and promise to stop spamming you afterwards. :) Thanks again, Jan

2 years, 8 months

[MM3-users] Re: Sending to mangled 'From' addresses.

by Jeremy Stanley

On 2024-06-01 09:49:54 -0700 (-0700), Mark Sapiro wrote: [...] > If this is the result of a `reply` and not `reply-all` the client > is not behaving reasonably. [...] I haven't seen it with replies, but rather mail clients recording every address they see into their address book, and then when the user of such a client wants to send new mail to someone they start typing that person's name and their mail client happily auto-completes it with the mailing list's address instead of the intended personal address. This is one of the reasons we don't use DMARC mitigations for most of our lists, and instead we just try to make Mailman avoid altering anything in the message headers or body that might invalidate DKIM signatures (so no changing From or Reply-To, no adding list-specific subject prefixes, no appending list unsubscribe info to the end of messages...). It's an unfortunate trade-off, but some of our users do tend to get confused by address book pollution. -- Jeremy Stanley

1 year, 2 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' > Sep 25 07:20:57 2017 (35) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/usr/local/lib/python3.6/site-packages/mailman/core/pipelines.py", line 53, in process > handler.process(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 174, in process > mlist, msgdata, subject, prefix, prefix_pattern, ws) > File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 72, in all_same_charset > chunks.append(chunk.decode(charset)) > AttributeError: 'str' object has no attribute 'decode' > Sep 25 07:20:57 2017 (35) SHUNTING: 1506324057.584686+a13cc47dc1027a0cfb00c892396b3ba7efabb3dc This is <https://gitlab.com/mailman/mailman/issues/359> It is fixed in the current source by <https://gitlab.com/mailman/mailman/commit/e92359323cda1fb118415c2ccb6967979…>. > In addition, the log contains other trace backs that might or might not associate to this problem: > > Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) > Sep 24 21:11:28 2017 (34) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail > results = self._connection.sendmail(envsender, recipients, msgtext) > File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail > msg = _fix_eols(msg).encode('ascii') > UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) > Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 This may be a bug. The msgtext argument in 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed to be a string containing only ascii characters. I'm interested in what's in Mailman's var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. You may be able to print the contents with Mailman's bin/mailman queue var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck There shouldn't be raw unicodes like \udcea in the text of the message, but we should defend against that anyway. > Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' Same as above. > Sep 25 09:19:58 2017 (30) deque: do_confirm_verify > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 420, in _step_send_confirmation > raise StopIteration > StopIteration This is normal. It is not an issue. > Sep 26 09:21:07 2017 (36) deque: > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 217, in _step_sanity_checks > MemberRole.member) > mailman.interfaces.member.AlreadySubscribedError: sender(a)foo.bar is already a MemberRole.member of mailing list listname(a)listserver.foo.bar This appears to be an attempt to subscribe someone who's already a member. This should have resulted in an appropriate message to the attempted subscriber. > Sep 26 13:32:29 2017 (30) Uncaught runner exception: > Sep 26 13:32:29 2017 (30) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/command.py", line 196, in _dispose > mlist, msg, msgdata, parts, results) > File "/usr/local/lib/python3.6/site-packages/mailman/commands/eml_confirm.py", line 53, in process > mlist).confirm(token) > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 540, in confirm > PendableUnsubscription.PEND_TYPE) > AssertionError I'm not sure about this one. a message has been sent to the LISTNAME-confirm address to confirm a subscription or unsubscription. The confirmation token exists but is neither a pending subscription or unsubscription token. > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 As I said in a prior reply, this is <https://gitlab.com/mailman/mailman/issues/256>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Strange issue with bounce processing

by Brian Carpenter

On 12/25/20 10:07 PM, Mark Sapiro wrote: > On 12/25/20 6:36 PM, Brian Carpenter wrote: >> Dear List, >> >> First of all Merry Christmas to those of you that are observing it. >> >> I have an issue on one of my Mailman 3 servers. The bounce runner is not >> running, even after restarting mailman core. All the other runners are >> working fine. Here is the problem, after restarting it, a number of >> messages show up in queue/bounces from a single list. > > What happens if instead of restating core, you stop and then start it? Same behavior. > I don't really understand what's going on. The only messages which get > queued in queue/bounces/ are messages to the LIST-bounces address > delivered from the MTA, unless possibly they are somehow in queue/retry/ > and being retried. What do you see in the MTA logs? > The mail logs shows bounce notifications being sent out as per the list settings. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Unnecessary coded-words? [was: Shorted Subjects in Mailman]

by Stephen J. Turnbull

Mark Sapiro writes: > However, I did a test injecting directly to Mailman a message with > ``` > Subject: [SAV-LINUX] Notice from Sophos_Anti-Virus on server.example.com > [DEMO1] > ``` > on a German language test list with subject prefix [Janinsliste] and I > get the same result, I.e. the RFC 2047 encoded > ``` > Subject: > =?utf-8?q?=5BJaninsliste=5D=5BSAV-LINUX=5D_Notice_from_Sophos=5FAnti-Virus_on_server=2Eexample=2Ecom?= > ``` > so this is definitely a Mailman bug (or a bug in the underlying Python > email package. There seem to be other bugs here. First, I can't see any content-based reason for encoding this 100% ASCII content. I guess the list is set to always encode the subject prefix, and we just encode the whole field body if any part is encoded? Perhaps this is a quick workaround for the OP: set MIME-encoding for the subject prefix to "as needed". Second (and this is important because of RFC conformance!), the encoded word is over 75 characters. I've filed https://gitlab.com/mailman/mailman/-/issues/1021 for this.

3 years

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

Thanks, Mark. @Abhilash, any chance for an update to Docker-mailman to fix these known issues soon? https://gitlab.com/mailman/mailman/issues/256 https://gitlab.com/mailman/mailman/issues/359 @Mark, Mark Sapiro wrote: >>> In addition, the log contains other trace backs that might or might not associate to this problem: >>> >>> Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> >> This may be a bug. The msgtext argument in >> 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed >> to be a string containing only ascii characters. I'm interested in >> what's in Mailman's >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. >> You may be able to print the contents with Mailman's >> >> bin/mailman queue >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck Isn't this a Mailman 2 command? What is the Mailman 3 equivalent? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

7 years, 10 months

[MM3-users] Re: How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

On Fri, 1 Nov 2024 20:56:42 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/1/24 20:14, Jigme Datse wrote: > > > > python venv/lib/python3.12/site-packages/mailman_web/manage.py > > migrate > > > > which *might* be the wrong manage.py but other than the change with > > the migrate command, without it looks to throw the same output. > > > > The Django log was at that time empty it's now attached (larger than > > I'd like). > > It is not necessary to post the entire log which repeats the same > ERROR and traceback over 300 times. The errors all seem to be > disallowed hosts. 321 from IP 45.79.102.219, 5 from > mail01.datsemultimedia.com and a few others. The PTR from IP > 45.79.102.219 is mail01.datsemultimedia.com and its A is > 45.79.102.219. Is this your server, if so add both 45.79.102.219 and > mail01.datsemultimedia.com to ALLOWED_HOSTS. > Thank you... I while helpful, I think I'll abandon this project... Appreciate the help.

9 months

[MM3-users] Re: Mailman not able to process "big" requests

by Darren Smith

Our installation at https://lists.rootsweb.ancestry.com has around 33,000 lists and somewhere around 1.5 million members. We have lists with 5,000+ members. Note that I haven't tried any mass subscriptions. When we upgraded from mailman 2 to mailman 3, we used the old .pck files and ran the import on each of the lists. It did take about 6 weeks to do the full import all 33,000 lists. I'm not joking. As for sending messages - there isn't any problem sending that many messages out, but then we are also not trying to subscribe list members at the time. We are, though, in the process of importing the old archives from our old mailman 2 system. This doesn't seem to affect the rest of the system. We have seen some inefficiencies in the new system, such as the front page of postorius - loading all of the information for 200 lists (if the user set the "lists per page" to 200) was bringing down the system. We have our own metadata system to be able to search for lists by state/region/surname (ours is a genealogy mailing list system), so we had to replace the front page with our own "find a list" functionality. The other main problem was the page where a user can see what lists they subscribe to. That page was also a denial of service if the user had several hundred lists they are subscribed to. And for a genealogy mailing list system, this is common. We have actually ended up creating our own API layer (only accessible on the local machine) and make certain calls to it for the most painful of the issues. One of these days (when we get a moment to breathe) we are going to post some of our changes to the project so that we can ditch our own API and just use the internal REST API. To be fair, the inefficiencies are not necessarily with mailman or the rest API itself - but with Postorius making hundreds of calls to load a single page. Though if the API supported loading multiple lists at once instead of having to load them serially, that might help as well. So while we have not seen any timeout issues on the call to mass subscribe users, we HAVE found several other calls that are effectively a denial of service and have gotten around them ourselves, with plans to contribute to the project in the near future. -Darren On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/24/2018 12:36 AM, Abhilash Raj wrote: > > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > > >> We also have a problem with sending out emails to "large" (>50) groups, > >> as they seem to not getting sent out at all. Do you have any idea what > >> the problem here could be? > > > > Which MTA are you using? What do you see in mailman's logs and MTA's > logs? > > > > I haven't seen this kind of problem before with Mailman 3. This very > list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > > Nor have I seen this issue. This list currently has 158 non-digest > members. There are several @python.org Mailman 3 lists with over 100 > non-digest members including the active yt-users(a)python.org list with > 301 members, and I have gotten no reports of an issue like this. > > Also, there are over 600 lists at <https://lists.fedoraproject.org/>, > and I don't think this is an issue there either. > > -- > 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, 3 months

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

by Stefan Tatschner

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. Thank you for the pointer to qcluster. I don't know so much about these web components and their relationships. According to the documentation [1] it seems that qcluster is not needed as long as cronjobs are configured. Since debian ships the entries in /etc/cron.d [2, 3] I disabled the qcluster components. Also there is a debian package issue; qcluster is started twice when using the provided service files: * the uwsgi script ini starts qcluster * the mailman3-qcluster service starts it as well I know the debian thing is out of scope here, I just want it documented somewhere. Stefan [1]: https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks [2]: https://gitlab.com/mailman/hyperkitty/blob/master/example_project/crontab [3]: https://salsa.debian.org/mailman-team/mailman-suite/blob/master/debian/mail…

6 years, 8 months

[MM3-users] Re: import21: ModuleNotFoundError: No module named 'Mailman'

by Christian Schwarz

On Sun, 2019-07-28 at 17:07 -0700, Mark Sapiro wrote: > As to how to proceed, there are a couple of ways. One is to fix import21 > so it ignores this issue. I just reported > <https://gitlab.com/mailman/mailman/issues/618> on this, but I'm not > sure how to fix it. I don't think it will work to try the pickle.load > and pass the ModuleNotFoundError exception because I think the rest of > the pickled data won't be returned. > > It looks like you still have the MM 2.1 installation, so you could use > either MM 2.1's bin/withlist or bin/config_list to set the list's > bounce_info to an empty dictionary. and then use the updated config.pck > for the import. > > This assumes that bounce_info is the issue. You can verify that there is > a non-empty bounce_info dictionary with either bin/withlist or bin/dumpdb. Indeed, bounce_info is not empty! I think I need more precise instructions on how to empty bounce_info using config_list, though.

6 years

[MM3-users] Re: An archive/read-only list on a full setup?

by Andreas Schamanek

Thanks a lot, Mark! After some tests with a test setup I came to the conclusion that what you suggested was better than what I had so far (i.e. the empty Mailman list). So, I deleted the empty list, leaving only the Hyperkitty list. On Tue, 11 Apr 2023, at 11:22, Mark Sapiro wrote: > Since there is no Mailman list, attempts to post or reply directly from > HyperKitty will fail, ... Yep, I get a 404. Doesn't look nice but should be OK. Not many people will try, and the description of the list makes clear that it is only an archive. I have also added a Redirect on the webserver so that people who click [Manage subscription/this list] are redirected to the actual remote list. That helps, too. So, no fake list, and the link to subscribing still works. The particular list is low volume. So, it will take some time until I can report how well it worked out. But after my tests I am confident. Thanks again, -- -- Andreas :-)

2 years, 3 months

[MM3-users] Re: mailman.cfg (use_https: yes) fails

by Wolfgang Bock

Hi again, in this case I'll check out either and report. Regards Wolfgang Am 18.11.2019 um 05:06 schrieb Mark Sapiro: > On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > > >> In this context I faced a strange behavior: >> >> In the database mailman3web in table django_site are listed several >> domains, either in the django-domain-management site >> https://[mydomain]/mailman3/admin/sites/site/ >> >> id domain name >> 1 example.com Example.com >> 2 [mydomain-1] [mydomain_name_1] >> 3 [mydomain-2] [mydomain_name_2] >> 4 [mydomain-3] [mydomain_name_3] >> >> In case I delete line 1 with the id 1, in the database or in the >> django-web-site, postorius fails to work. After re-inserting this line, >> postorius works again. > > In your settings.py, you probably have SITE_ID = 1. Thus, when you > delete the site with id = 1, Postorius fails. You need to set SITE_ID to > an existing site in settings_local.py. >

5 years, 8 months

[MM3-users] Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Ralf Wiegand

Hello Mark, Can I substitute Django with something that will be FIPS complaint? Can I do without it? Thank You, Ralf On 5/19/20 1:02 PM, Mark Sapiro wrote: > On 5/19/20 5:57 AM, Ralf Wiegand wrote: >> (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate >> Operations to perform: >> Apply all migrations: account, admin, auth, contenttypes, >> django_mailman3, django_q, hyperkitty, openid, postorius, sessions, >> sites, socialaccount >> Running migrations: >> Applying contenttypes.0001_initial...Traceback (most recent call last): > ... >> File >> "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", >> line 221, in names_digest >> h = hashlib.md5() >> *ValueError: error:060800A3:digital envelope >> routines:EVP_DigestInit_ex:disabled for fips* >> >> >> >> Hello group, I am running into this error. any idea what is going >> wrong here? > This is a Django issue, not Mailman per se. The migration that's failing > is django/contrib/contenttypes/migrations/0001_initial.py. A brief > search seems to indicate that this won't work with NSS FIPS. >

5 years, 2 months

[MM3-users] Re: certain msgs not archived

by Sandor Dibuz

On 2/17/22 19:16, Mark Sapiro wrote: > > If you rerun hyperkitty_import with the since= option set to a date > earlier that the oldest message to import, it should just work. Messages > which are already in the archive (by Message-ID:) will be ignored by the > import process. Great! So valuable info. Thank you, Mark. "earlier that the oldest message" you sure mean earlier then the oldest of already archived. Or since= any date of the mbox messages to be imported. Will check the hyperkitty_import for since= option format. Yet another question. Is it supposed to stop minutely/hourly/etc. mailman3-web cron jobs during import to avoid any collisions? Or even mailman3-web completely but probably it needs to be running. I only ask because my last import attempt on a test maillist failed with [ERROR/MainProcess] Failed indexing 1 - 2 (retry 5/5): (1712, 'Index hyperkitty_attachment is corrupted') (pid 5841): (1712, 'Index hyperkitty_attachment is corrupted') Optimizing cured the hyperkitty_attachment InnoDB index corruption problem but scared the sh.. out of me for a moment... Thank you for your help, Mark. Sanyi

3 years, 5 months

[MM3-users] Re: bulk deletion of messages from Hyperkitty

by Timour Bakeev

Hi Mark! Mark Sapiro wrote: > On 7/10/24 12:27 PM, Danil Smirnov via Mailman-users wrote: > > I'm aware of the tools you mentioned and they were properly used. > > Your issue is almost certainly caused by unescaped From lines in > message bodies and preprocessing the mbox with the > hyperkitty/contrib/cleanarch3 script should fix those. Could you take a look at my MR for this script? Right now I have to use a locally modified version of it, as the one in contrib/ doesn't work out of the box. > > Please let us focus on the question I asked - how do we delete messages of > > a particular date if there are too many of them so using Hyperkitty UI > > isn't an option? > > You can do > DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; Thanks a lot for this detailed walk-through, it is very helpful and I'm going to use it to clean up my migrated archives. With best regards, Timur Bakeev.

1 year

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Using the virtenv installation method seems to be reasonable, yes. Adding the suggested line i did not try yet. Thanks! Am 26. April 2024 10:29:18 MESZ schrieb Odhiambo Washington <odhiambo(a)gmail.com>: >On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > >> Am 2024-04-26 00:52, schrieb Mark Sapiro: >> > On 4/25/24 14:01, Thomas Stein wrote: >> >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >> >>> >> >>> I don't know how things are arranged in the Debian/Ubuntu package, >> >>> but you may have a settings.py which at the end does something like >> >>> ``` >> >>> try: >> >>> from settings_local import * >> >>> except ImportError: >> >>> pass >> >>> ``` >> >>> If that is the case, adding the above snippet to the end of >> >>> settings_local.py should work. >> >> >> >> Yes, that's the case. I added the snippet in question to >> >> settings_local.py but this leads to another error: >> >> >> >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> >> >> from settings_local import * >> >> File "/usr/share/mailman3-web/settings_local.py", line 194, in >> >> <module> >> >> x = list(MIDDLEWARE) >> >> ^^^^^^^^^^ >> >> NameError: name 'MIDDLEWARE' is not defined >> >> dpkg: error processing package mailman3-web (--configure): >> > >> > Yes. I understand. In your case, MIDDLEWARE is only defined in >> > settings.py and not in settings_local.py. As I understand it originally >> > you added >> > ``` >> > x = list(MIDDLEWARE) >> > x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> > MIDDLEWARE = x >> > ``` >> > to settings.py and you say it didn't help. I don't know why that >> > wouldn't work as long as there is no setting for MIDDLEWARE in >> > settings_local.py and you added that after the MIDDLEWARE setting in >> > settings.py. >> > When you say it didn't help, do you mean you still get the >> > >> > django.core.exceptions.ImproperlyConfigured: >> > allauth.account.middleware.AccountMiddleware must be added to >> > settings.MIDDLEWARE >> > >> > message or something else? I note that the original post in this thread >> > refers to /etc/mailman3/mailman-web.py which is presumably where the >> > package ultimately puts the Django settings, and I don't know what >> > `dpkg --configure` is doing. >> > >> > One thing you could try is in settings_local.py, put >> > ``` >> > from settings import MIDDLEWARE >> > x = list(MIDDLEWARE) >> > x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> > MIDDLEWARE = x >> > ``` >> > to work around the NameError. >> >> After that I get: >> >> File "/usr/share/mailman3-web/urls.py", line 20, in <module> >> from django.conf.urls import include, url >> ImportError: cannot import name 'url' from 'django.conf.urls' >> (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) >> dpkg: error processing package mailman3-web (--configure): >> installed mailman3-web package post-installation script subprocess >> returned error exit status 1 >> Errors were encountered while processing: >> >> I guess I'll wait for the new package for now. >> > > >How about adding: > >MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) > >in settings_local.py > >And how about you use the virtualenv method ><https://docs.mailman3.org/en/latest/install/virtualenv.html> for more >peace of mind in the future? > >

1 year, 3 months

[MM3-users] Re: Any good ideas on how to troubleshoot django allauth

by Stephen J. Turnbull

Mark Sapiro writes: > I only discovered this because I saw the ERROR entries in the log while > looking for something else. In any case, it turned out that > python-openssl was installed on mail.python.org and not on > lists.mailman3.org. Removing it from mail.python.org allowed OAuth2 > logins to work. I think that part of the problem here may be that distros have not caught up to current Python upstream distribution practices. MacPorts is particularly bad (ie, heinous), in that they don't even follow their own Python distributions. In MacPorts, OpenSSL and GNU readline have both bitten me; basically, the add-on packages should be labeled "unless you know you need this, and know why, and accept that NO WARRANTEE means what it says (we don't support it at all), don't install this!" I've opened Mailman/Mailman issue#323 for this. Probably it should be moved to Installation and Troubleshooting documentation, but maybe leaving an open issue in the tracker would help discoverability?

8 years, 3 months

[MM3-users] Re: Templates and docker-mailman

by Abhilash Raj

On Tue, Mar 20, 2018, at 2:47 PM, Mark Sapiro wrote: > On 03/20/2018 02:13 PM, jwhathaway(a)locklaw.com wrote: > > > > /opt/mailman/core/var/templates/site/en/list:member:generic:footer > > > > But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do? > > > That's only one place the template is looked for. The search is first > list, then domain then site. > > So the search will be first in > /opt/mailman/core/var/templates/list/<list-id>/en/ followed by > /opt/mailman/core/var/templates/domains/<domain>/en/ followed by > /opt/mailman/core/var/templates/site/en/ > > and the first list:member:regular:footer or list:member:generic:footer > found is what will be used for regular deliveries and the first > list:member:digest:footer or list:member:generic:footer found is what > will be used for digest deliveries. I'd probably have to look at the code, but aren't they supposed to have either .txt or .html extensions? -- Abhilash Raj maxking(a)asynchronous.in

7 years, 4 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Élodie BOSSIER

Le 18/02/2022 à 18:23, Mark Sapiro a écrit : > If you go to https://example.com/mailman3/domains/ (the Domains view > in Postorius) you will see at least two entries, one with Mail Host > ml.franceserv.fr and one with Mail Host ml.viticreation.fr. > > What are the Web Host entries for these? > You should have two separate site entries in the django_site table > (https://example.com/admin/sites/site/) for these domains. Ah alright, now I understand how to proceed and it's working perfectly. I need to add domains through https://ml.franceserv.fr/admin/sites/site/ and define a new site_id for each domain name. Thank you very much for your help. This is my result : https://images.franceserv.fr/images/2022/02/18/06d4eb84a0ded88d55c0296ff0c3… Now, I need to find how to set it automatic when I will add a new list. Perhaps I could do it with an an SQL command if there are no bash command ? I will check with "mailman create" and the --domain argument. Thank you again for your help.

3 years, 5 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Sat, Jan 28, 2023 at 11:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/23 11:48, Stephen J. Turnbull wrote: > > Odhiambo Washington writes: > > > > > from mailman_web.settings.base import * > > > from mailman_web.settings.mailman import * > > > > I think just putting these as close to the top as possible, and > > including a comment (or two) saying that this is importing defaults > > that can be overridden by any assignment made later in the file is > > about as far as we can go for explaining. > > > I've Just updated this. It now says: > ``` > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > > # Settings below supplement or override the defaults. ``` > Yes, this now is awesome - for reading between the lines :) Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

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

by Shashikanth Komandoor

Thank you Mark for your response. I am not sure. How can I check that if it is from unshunting ? <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 Wed, Sep 23, 2020 at 10:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/23/20 6:32 AM, Shashikanth Komandoor wrote: > > 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 ? > > > Mailman is trying to add a message to the digest of the > press.dpr-pb.lsmgr.nic.in list, but the > /var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/ directory > doesn't exist, presumably because the list has been removed. > > The question is why is Mailman trying to write to this list's > digest.mmdf? Did the above result from unshunting something from before > the list was removed? > > -- > 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 <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>

4 years, 10 months

[MM3-users] Re: Archive date/time vs elapsed time

by Mark

On 2023-06-27 13:34, Mark Sapiro wrote: > On 6/26/23 7:46 PM, Mark wrote: >> Hi >> >> In the archive's "Recent", "Most active" etc displays, the date and >> time of each post is shown. >> >> However, when viewing by "Thread" listing, each post shows the elapsed >> time since it was posted ie. the number of days, hours since it was >> posted (eg. 1 day, 2 hours). > > I don't see this. It may have been recently changed. Please visit the > archive of this list at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > and if you see the issue there, post a URL of a page on which you see > it. No, I don't see it on the MM users' archive. The archive where I'm seeing it is HyperKitty version 1.3.4 on a Debian packaged MM 3.3.3 The problem lay therein? In the Hyperkitty docs there doesn't appear to be any mention of options or changes for the display of datetime/elapsed-time

2 years, 1 month

[MM3-users] Re: postorius configuration of the from-part

by Wolfgang Bock

Hello, thanks for your information. After creating the dmarc-entries in the DNS-databases everthing works as wanted! Regards Wolfgang Am 13.11.2019 um 06:02 schrieb Mark Sapiro: > On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> can someone give me an advice how I can configure in the >> postorius-menues the view of the from-part of my list-member like in >> this mailinglist: >> >> Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> > > The above is the result of Settings -> DMARC Mitigatations -> DMARC > mitigation action = "Replace From: with list address" > > You can apply that to only messages From: a domain the publishes a DMARC > policy of reject or quarantine or to all messages depending on DMARC > Mitigate unconditionally. > > >> case 1 reply goes to the list or to the member >> case 2 reply goes only to the list > > The DMARC Mitigatations settings are independent of the various reply > settings on the Alter Messages tab. >

5 years, 8 months

[MM3-users] Re: From address of subscription notifications

by worik

On 27/02/19 11:54 AM, Mark Sapiro wrote: > On 2/26/19 2:11 PM, worik wrote: >> When I subscribe some body to to a list I on I get a notification that >> says it comes from changeme(a)example.com >> >> As far as I can tell no subscribers are getting mail with that, so this >> is not a crises. But it is untidy and I cannot find where to change it. >> >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of >> docker-compose.yaml (I am using the docker distribution...) > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > There is no `mailman/config/schema.cfg` on my system. Should I raise a issue over at the docker-mailman github? I have: /opt/mailman/core/mailman-extra.cfg /opt/mailman/core/var/etc/mailman.cfg Should I change it in the second one? -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 5 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 3:34 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On May 24, 2023 9:45:45 AM PDT, Quanah Gibson-Mount > <quanah(a)fast-mail.org> wrote: > > >> That shell script seems to have errors: >> >>>>> pendings = getUtility(IPendings) >>>>> for token, data in pendings.find( >> ... token_owner=TokenOwner.subscriber, >> ... pend_type='subscription'): >> ... print("hello") >> ... >> Traceback (most recent call last): >> File "<console>", line 3, in <module> >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper return function(args[0], config.db.store, *args[1:], >> **kws) >> TypeError: find() got an unexpected keyword argument 'token_owner' > > > Your Mailman core is too old for that script. Tell me your core version > and I will try to make one that works for you. Thanks Mark! We're hoping to upgrade to something more current next month. Right now apt shows: apt show mailman Package: mailman Version: 1:2.1.29-1+deb10u5 Regards, Quanah

2 years, 2 months

[MM3-users] Re: howto reallow a banned email ?

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: >> >> By mistake a user has been banned to post to mailman list. How can I >> allow him not only to post but also to become a member of a list ? >> >> I have not found any info on the web, or I have been unable to search >> correctly. > > > Do you have the Postorius web UI in your installation? If so go to the > list's Ban List and remove the unwanted entry. > > Or is this perhaps a Mailman 2 question? If so you'll find the ban_list > in the web admin UI at Privacy options... -> Subscription rules.

6 years, 1 month

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Thank you very much for your response. I understood myself as quite ignorant even to find out the versions of each of the component. But my "mailman info" output looks like the below: *(venv3) [root@dlist-lsmgr mailman]# mailman info* *GNU Mailman 3.3.2rc2 (Tom Sawyer)* *Python 3.6.8 (default, Aug 10 2019, 06:54:07)* *[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]* *config file: /var/lib/mailman/mailman/var/etc/mailman.cfg* *db url: postgres://<username>:<password>@127.0.0.1/mailman* *devmode: DISABLED* *REST root url: http://localhost:8001/3.1/ <http://localhost:8001/3.1/>* *REST credentials: restadmin:restpass* *(venv3) [root@dlist-lsmgr mailman]# pwd* */var/lib/mailman/mailman* How to find out the versions of the each and every component of the mailman 3 like mailman core, mailmancilent, postorius, hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, after installation? If I am running an old mailmanclient or older version of any other mailman component, please suggest how to upgrade either one or multiple components based on the requirement. Is there any link that would help me to upgrade ? I have used the link https://docs.mailman3.org/en/latest/devsetup.html to install the mailman 3 components. I expected that the procedure followed in this link would install the latest versions of the mailman 3 components. Please correct me if I am wrong. Is there any latest version compatibility table ? Also please suggest me an URL that would install the latest versions of mailman 3 components and allow me to do customizations related to our domain. <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 Mon, Oct 26, 2020 at 4:16 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.2rc2 and > in > > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > > with default values. As of now, we don't have any lists and just > installed > > software components only. > > > > After the installation and configuration, I have tried > > creating the domains and lists. I was successful in creating them but > when > > I tried to login and browse the lists using LDAP authentication, I am > > getting the "Mailman REST API not available. Restart Mailman core". > > > > I see the below trace in the mailmansuite.log. > > > > > *Traceback (most recent call last): File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ return self._get(name) File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count > ... > > > > I don't see any error messages in the mailman.log. And I > > also executed a few curl commands in getting the details of the lists > > created and list info which I got their results successfully. > > > > Could you please guide where exactly I am missing or do I > > need to make any changes in my customizations ? > > > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. > > > -- > 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

4 years, 9 months

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 19:58, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 17/9/21 17:24, Mark Sapiro wrote: >> On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> On 16/9/21 16:40, Mark Sapiro wrote: >>>> >>>> Are you asking what the equivalent MM 3 scripts would be? >>>> >>> More or less: I'm asking for a general direction here. I think I >>> cannot use tthe "withlist" method as before, inside a python script, >>> and I'm not sure how to do it. >> >> >> You can run scripts via withlist in Mailman 3 similarly to Mailman 2. >> See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… >> >> > First, thanks for the prompt response, Mark. > > Maybe I'm a little bit ofuscated, but I readed this doc many times > when I was searching how to do it... but I cannot imagine how to do a > shell or a python script, using the needed parameters, that sets hold > on a member of a list. > > I'll try to do some tests tomorrow. I've followed the indications of a mailman -C /usr/local/mailman3/var/etc/mailman.cfg shell --details I've been trying to "translate" the python script that I made for mailman2 to new mailman3, but obviously, I'm missing something. It seems that mailman cannot locate the "module" needed. The script is named "moderar.py": *-*-*-*-*-*-*-*-*-* (begin of /usr/local/mailman3/moderar.py) /usr/local/mailman3 # cat moderar.py #! /usr/local/bin/python3 # # script via withlist para moderar a pelo en mailman3 # import os import sys sys.path.insert(0, '/usr/local/mailman3') os.environ['PYTHONPATH'] = '/usr/local/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' os.environ['MAILMAN_CONFIG_FILE'] = '/usr/local/mailman3/var/etc/mailman.cfg' import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() *-*-*-*-*-*-*-*-*-* (end of /usr/local/mailman3/moderar.py) When I execute a mailman withlist -r moderar -l list_to_use(a)mydomain.com address(a)moderate.com The system returns: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.7/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'moderar' I've done a ln -s /usr/local/mailman3/moderar.py /usr/local/lib/python3.7/site-packages/mailman/bin/moderar.py But with the same result. And I'm not sure if I'm doing well importing "mm_cfg" in the script. My enviroment is open wide installation of mailman, python, etc. in a FreeBSD 12.2-RELEASE-p10 Mailman Core Version GNU Mailman 3.3.4 (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 version: 1.3.5 If someone can give a hint it will be much appreciated.

3 years, 10 months

Search results for query "sapiro"