Search results for "Postorius" - Mailman-users

Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull: > You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right? No, I'm not that guy. I've not said anything like that, nor have I knowingly configured Postfix to use that. I've looked up how to do it now that you mention it, and found the smtputf8_enable parameter[1]. I have not used it, but it turns out that it is enabled by default. I can turn it off and see if that makes any difference in the future. Testing with telnet, Postfix indeed announced "250 SMTPUTF8" on EHLO. > If you're right about the umlaut being the trigger, the first thing I'd look at is a feature-negotiation problem in the MTA delivering to Mailman. I'm pretty sure our LMTP does not offer the SMTP UTF8 feature. In that case the problem should go away with disabling SMTPUTF8, I suppose? > I would guess this is in the shunt queue. If there's only one file there, you can just delete it. There was a whole bunch of files in that directory. I've taken a look several of them, and as they were all spam, I've taken the liberty to delete them all (this list is so low volume that I know all the senders personally anyway). However, even after restarting mailman, the 500 error persists when visiting the held messages page in postorius. I've also looked into all the other queue directories, they were all empty. > Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name. I confess that I haven't visited the held messages page for a very long time (because I didn't have a reason to; I received no notifications of held messages). Only after I received the notification that my errorneous message was being held, I visited it, and I was faced with the 500 error. If Mailman failed to notify me of held messages previously, they might have been in hold status already and one of them might be the cause. Marvin [1]: http://www.postfix.org/postconf.5.html#smtputf8_enable PS: Sorry for the missing link [1] from the last mail. Here it is: https://gitlab.com/mailman/hyperkitty/issues/201 -- Blog: https://mg.guelker.eu

5 years, 9 months

Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/12/22 01:24, Onyeibo Oku wrote: > > Good Morning Everyone, > > I installed and managed mailman 2 for about two years. I am now > ready to try Mailman 3. The documentation for version 2 was lucid and > this forum was quite helpful in the past. > > Now I'd like to proceed with installating MM3 but I doubt my > understanding of the docs. It seems to assume that users will know what > to do. > > Okay, don't laugh! I just want to be sure what I am doing. Does the > following sequence resemble the proper steps? As Eggert says, we aren't laughing ... > 1. Download the source from a git repo (I understood that one) > 2. Create a virtual environment (venv perhaps ... not stated explicitly) > 3. activate the virtual environment > 4. from the git project root, run: ./mailman start Step 4 is premature. More below. > I know, its stupid. I had to ask. Not stupid ... > It would really build my confidence > someone would confirm the above steps or counter then with something > very explicit. What about process ownership? Do I need to have a unix > mailman user? What else do I need to get mailman up and running > before proceeding to configuration. Ahaa! I perused the config docs a > bit. Where can I find the .cfg file? As Eggert suggests, see https://docs.mailman3.org/en/latest/install/virtualenv.html and follow that. You don't need to download the source from GitLab. Following that doc will get the latest releases from PyPI via pip. Those are still somewhat out of date - we really should make new releases - so if you want the latest from GitLab, there are a couple of ways to do it. Perhaps the easiest is to just run the various `pip install` commands as documented and then upgrade Mailman core in your venv with ``` pip install --upgrade git+https://gitlab.com/mailman/mailman@master ``` and update the various mailman web packages with ``` pip install --upgrade git+https://gitlab.com/mailman/xxx@master ``` where xxx is mailman-web, mailman-hyperkitty, django-mailman3, postorius, hyperkitty. I.e., run it 5 times, once for each value of xxx. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: Trying to save a new style

by pcjkollmorgen＠hotmail.com

Thanks. I was able to create a python module and install it which sets up 2 new styles, and I have one of those now set as the default list style in Postorius. I needed to include a few more interfaces but otherwise kept to the example plugin file (just made another file for the other list). ``` from public import public from mailman.interfaces.styles import IStyle from mailman.styles.default import LegacyDefaultStyle from zope.interface import implementer from mailman.interfaces.action import Action, FilterAction from mailman.interfaces.archiver import ArchivePolicy from mailman.interfaces.autorespond import ResponseAction from mailman.interfaces.bounce import UnrecognizedBounceDisposition from mailman.interfaces.digests import DigestFrequency from mailman.interfaces.mailinglist import ( DMARCMitigateAction, Personalization, ReplyToMunging, SubscriptionPolicy, ArchiveRenderingMode) from mailman.interfaces.nntp import NewsgroupModeration from mailman.model.roster import RosterVisibility # Documentation on List styles # https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… # also some was worked out from src/mailman/styles/base.py @public @implementer(IStyle) class MyPrivateStyle(LegacyDefaultStyle): # Provide a unique name to this style so it doesn't clash with the ones # defined by default. name = 'my-announce-style' # Provide a usable description that will be shown to the users in Web # Interface. description = 'My Announce mailing list style.' def apply(self, mailing_list): """See `IStyle`.""" # Set settings from super class. super().apply(mailing_list) # Make modifications on top. mailing_list.admin_immed_notify = True mailing_list.admin_notify_mchanges = True mailing_list.advertised = True mailing_list.allow_list_posts = False mailing_list.anonymous_list = False mailing_list.archive_policy = ArchivePolicy.private mailing_list.archive_rendering_mode = ArchiveRenderingMode.markdown mailing_list.collapse_alternatives = False mailing_list.convert_html_to_plaintext = False mailing_list.default_member_action = Action.defer mailing_list.default_nonmember_action = Action.hold mailing_list.digest_send_periodic = False mailing_list.digests_enabled = False mailing_list.include_rfc2369_headers = True mailing_list.max_message_size = "40000" mailing_list.max_num_recipients = "30" mailing_list.member_roster_visibility = RosterVisibility.moderators mailing_list.send_goodbye_message = True mailing_list.send_welcome_message = True mailing_list.subscription_policy = SubscriptionPolicy.moderate mailing_list.unsubscription_policy = SubscriptionPolicy.moderate ``` Having a docker-mailman setup means needing to install this any time that the mailmail-core container is rebuilt (not all that often), however the source code for the module can live in a host volume such as /opt/mailman/core/var/plugins , it is simply an execution of the install which is need after a container is rebuilt. eg: docker exec mailman-core pip install -E /opt/mailman/var/plugins/yourplugin I currently need to pip install django-allauth[saml] and apk add openldap-dev (this one should be in a new version of the container) on any new mailman-core container anyway so I'm not too worried.

1 year, 3 months

Re: LookupError: unknown encoding: _iso-2022-jp$esc

by Mark Sapiro

On 09/07/2018 08:30 AM, Thor Atle Rustad wrote: > This happens when I open a page of Held Messages containing an offending > message. I get Server Error (500) in Postorius. Here is the mailman.log: > > > Sep 07 15:25:39 2018 (32) REST request handler error: > Traceback (most recent call last): > File "/usr/local/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File > "/usr/local/lib/python3.6/site-packages/mailman/database/transaction.py", > line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", > line 214, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/site-packages/falcon/api.py", line 244, in > __call__ > responder(req, resp, **params) > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 160, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 159, in _make_collection > for resource in collection] > File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 159, in <listcomp> > for resource in collection] > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 150, in _resource_as_dict > resource = self._make_resource(request.id) > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 77, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", > line 54, in as_string > value = email.message.Message.as_string(self) > 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 243, in > _handle_text > msg.set_payload(payload, charset) > File "/usr/local/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > LookupError: unknown encoding: _iso-2022-jp$esc I think this should be fixed in Mailman core 3.2.0. It is related to Mailman core issues 256, 437 and 470 and merge requests 197, 322, 350 and 375. In particular, it looks like you are missing at least <https://gitlab.com/mailman/mailman/merge_requests/375>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: Moderate mails from owner

by Mark Sapiro

On 4/30/19 1:04 AM, Henrik Rasmussen wrote: > @Mark: I am really sorry for the delayed responses, but this is a very low frequency list. I have subscribed to the list using a non-Microsoft address to see the outcome. > > The mails does indeed contain 'X-Mailman' headers. > > X-Mailman-Rule-Hits:nonmember-moderation > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation It looks like the message hit the nonmember-moderation rule and was accepted. This can happen in a few ways: First we determine the senders. Assuming the config is default, these are the addresses in From:, the envelope sender, and addresses in Reply-To: and Sender: if any. The only address I can see in the message headers that hasn't been altered by Mailman is the From: and maybe Reply-To: which you have munged to [LISTNAME](a)senderdep.example.com. Anyway that unmunged address and possibly others from the original incoming message will be users of the list with role nonmember. Now each of those (possibly only the one) nonmember(s) is checked for a moderation action. Since the message does not appear to have been held or processed through rules beyond nonmember-moderation, we presumably found a moderation action of accept. This can happen in a few ways., If this list was originally imported from Mailman 2.1 by the 'mailman import21' command, there may be a legacy accept_these_nonmembers attribute for the list. If so, and if a nonmember sender address matches an address or pattern in the list's accept_these_nonmembers, the message will be accepted. Otherwise if the moderation_action for a nonmember sender address is accept the message will be accepted. You need to check the list's accept_these_nonmembers attribute and the non-member address's moderation action. If you have recent Postorius, you can see nonmembers and their options from the 'users' -> Non-members view. In any case, you can do something like mailman shell -l list.example.com Welcome to the GNU Mailman shell The variable 'm' is the list.example.com mailing list >>> m.accept_these_nonmembers returns a possibly empty list Then for the sender addresses >>> memb = m.nonmembers.get_member('sender address') >>> memb.moderation_action This may return <Action.accept: 3> in which case you may want >>> memb.moderation_action = m.default_nonmember_action -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Re: Question about message bounce stats

by Abhilash Raj

> On Aug 30, 2021, at 11:27 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Ruth Ivimey-Cook writes: > >> If Abhilash has a starting point, > > IIRC it was quite primitive, and probably not at the the individual > message level, more like list level. We do keep a bounce score for Member (email, mailinglist pair) that is right now only available in Mailman’s database and is used for the purposes of un-subscriptions or disabling delivery. We haven’t had a chance to expose these values through REST API, but it is something I’d be happy to accept a patch for and isn’t too difficult if someone wants to pick up the task. It might be helpful at some point to expose some of those stats to the list owner or site admin as well in Postorius. > >> and there is acceptance from others to integrate something of this >> sort, then I could possibly help make it happen. > > If you're that interested, I'd say get started, at least on sketching > out requirements. There will probably be some nitpicking about code > style and the like, and there may be delays in integrating stuff due > to the peanut gallery contributing requirements that we decide we want > in the feature, but I don't think there's a problem with the basic > idea. Yep, +1. It would be good to first figure out what more stats do we need/want and if they just need to be exposed through the API or we need to setup some offline setup for calculating those metrics with some mechanism and then expose. > > We won't be putting tracking pixels and the like in outgoing posts, > but as long as it's internal data already generated by normal Mailman > operation, I would be somewhere between very surprised and shocked > (SHOCKED, I tell you!) if it weren't accepted. Yeah, anything that is possible to generate with regular Mailman operation is already possible for a site admin to get from logs with some scripting. So, the idea to expose them in a better UX I guess should be okay. Only thing we might want to consider is how much of that data is exposed to non-server-admins (list owners, mods etc) and the policy enforcement for that if users don’t like the default. -- thanks, Abhilash Raj (maxking)

4 years

Re: rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid

by Kyriakos Terzopoulos

Hi Steve, I'll check runq and let you know. As for the spaces it was just a copy/paste fail from my part since I want to obfuscate the true domain name. *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Wed, 25 Oct 2023 at 20:29, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Kyriakos Terzopoulos writes: > > > No more mail being marked as spam. However I face a (hopefully) new > > problem now. When I mass subscribe the users, they get an initial > > invitation email. However after replying I get this in the exim > > logs, the subsequent mails do not arrive and the users are not > > verified at all: > > > > 2023-10-25 13:36:41 1qvbFh-001kcb-Ig <= myname(a)myproject.eu > > H=localhost (webmail.myproject.eu) [127.0.0.1] P=esmtpa > > A=dovecot_login: myname(a)myproject.eu S=1726 > > id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu > > 2023-10-25 13:36:41 1qvbFh-001kcb-Ig == partners(a)myproject.eu > > < > partners-confirm+6df62cd0f805b2b66b21a43a42ec8ee77487e8ad(a)myproject.eu> > > R=mailman3_router T=mailman3_transport defer (-54): > > retry time not reached for any host for ' myproject.eu' > > It looks like 'myname' has replied to the invitation, and was received > by this MTA (is it Mailman's MTA?). Then delivery to Mailman was > deferred because delivery to ' myproject.eu' has failed, and Exim is > queueing them for future delivery, until the next retry time. Try > using 'runq' then checking the log to see why mail is failing in the > first place. > > I do not understand why there are spaces before the host name in these > lines: > > > id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu > > retry time not reached for any host for ' myproject.eu' > > The first never happens in my Exim instance. (I have no instances of > "retry time not reached" at all in my logs.) That suggests a > misconfiguration, in Exim, in Mailman, or Postorius. You should check > the mailman3_router and the mailman3_transport first because they're > easier. > > Steve > >

1 year, 10 months

Re: About to Install MM3 -- Seeking clarification

by Stephen J. Turnbull

Onyeibo Oku writes: > I am not sure I understand what you mean by apps. Is that Django apps > (./manage.py startapp app)? Do you mean a Django Project instead > (./manage.py startproject app)? An app for my purpose is everything configured via the settings.py used by the Django application created in a wsgi.py file. I guess you would think of them as projects. > What I have here is an active website project (live) done on Django > framework. It runs from a different virtual environment (venv). > > hence: > mailman --> /opt/mailman/venv > website --> /srv/website/venv (has a running uwsgi instance) The venvs isolate the Python code used by each app from the other. But the apps can still have conflicts over ports (this is mentioned in the Django docs), filesystem objects, and other resources. For example, a lot of applications use the /static/ location as a place to keep content that is supplied by your project and doesn't change. This is problematic if two different apps each wants to install a default.css, but they're different. One of the apps is going to look funny. Only the person who configures the apps can guess whether this kind of conflict will arise. Neither Mailman nor Django itself tries to protect you from such conflicts (I don't see how they could, in fact). > > > In whichcase, it doesn't hurt to follow the doc to its logical > > > conclusion? > > > > I don't understand what you mean by logical conclusion. > > > > That is to follow the guide to the end of the page (disregarding > the possibility of conflicts). No, you can't disregard the possibility of conflicts. My understanding from what you've posted so far is that you have an app "website" that is already implemented and running. Most likely that app has configured resources (specifically ports and website locations in particular /static/) that are likely to conflict. You need to manage those conflicts, most likely by changing the ports used by Mailman, Postorius, and Hyperkitty and by mapping a different location such as /mailman/static/ to the /var directory that actually contains the static files managed by "manage.py collectstatic". There may be other possible conflicts, but I can't help you with those because they depend on your website code. Steve

2 years, 10 months

Re: user mail not accepted

by Christian Stalberg

From smtp.log Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) Data: b'DATA' Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) Data: b'QUIT' Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) connection lost Apr 26 00:17:39 2021 (807) Connection lost during _handle_client() Apr 26 00:18:11 2021 (809) <019301d73a31$8e8e54e0$abaafea0$(a)ncboliviapartners.org> smtp to ncpoa(a)lists.ccalternatives.org for 83 recips, completed in 29.13376259803772 seconds Apr 26 00:18:11 2021 (809) <019301d73a31$8e8e54e0$abaafea0$(a)ncboliviapartners.org> post to ncpoa(a)lists.ccalternatives.org from christian(a)ncboliviapartners.org, 5811 bytes Apr 26 00:18:11 2021 (809) <161939626169.810.9530678025639681522(a)zarathustra.ccalternatives.org> smtp to ncpoa(a)lists.ccalternatives.org for 1 recips, completed in 0.0420069694519043 seconds Apr 26 00:18:11 2021 (809) <161939626169.810.9530678025639681522(a)zarathustra.ccalternatives.org> post to ncpoa(a)lists.ccalternatives.org from ncpoa-bounces(a)lists.ccalternatives.org, 869 bytes Apr 26 11:52:22 2021 (819) <161943793957.929.15640398646519288095(a)zarathustra.ccalternatives.org> smtp to ssan(a)lists.ccalternatives.org for 1 recips, completed in 0.22335004806518555 seconds Apr 26 11:52:22 2021 (819) <161943793957.929.15640398646519288095(a)zarathustra.ccalternatives.org> post to ssan(a)lists.ccalternatives.org from ssan-bounces(a)lists.ccalternatives.org, 765 bytes Apr 26 11:52:22 2021 (819) <161943793960.929.13309139087156940549(a)zarathustra.ccalternatives.org> smtp to ssan(a)lists.ccalternatives.org for 2 recips, completed in 0.05862092971801758 seconds Apr 26 11:52:22 2021 (819) <161943793960.929.13309139087156940549(a)zarathustra.ccalternatives.org> post to ssan(a)lists.ccalternatives.org from noreply(a)lists.ccalternatives.org, 810 bytes Apr 26 11:55:22 2021 (819) <161943812108.929.10391982256874011271(a)zarathustra.ccalternatives.org> smtp to ssan(a)lists.ccalternatives.org for 1 recips, completed in 0.1459965705871582 seconds Apr 26 11:55:22 2021 (819) <161943812108.929.10391982256874011271(a)zarathustra.ccalternatives.org> post to ssan(a)lists.ccalternatives.org from ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternatives.o rg, 1526 bytes Apr 26 12:01:30 2021 (817) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Apr 26 12:01:30 2021 (817) Peer: ('127.0.0.1', 38556) Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) handling connection Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'LHLO zarathustra.ccalternatives.org' Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'MAIL FROM:<christian(a)sewagesludgeactionnetwork.com>' Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) sender: christian(a)sewagesludgeactionnetwork.com Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'RCPT TO:<ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternativ es.org>' Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) recip: ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternatives.o rg Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'DATA' Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'QUIT' Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) connection lost Apr 26 12:01:30 2021 (817) Connection lost during _handle_client() Apr 26 12:01:34 2021 (819) <161943849287.814.5890052642238479423(a)zarathustra.ccalternatives.org> smtp to ssan(a)lists.ccalternatives.org for 2 recips, completed in 0.06680631637573242 seconds Apr 26 12:01:34 2021 (819) <161943849287.814.5890052642238479423(a)zarathustra.ccalternatives.org> post to ssan(a)lists.ccalternatives.org from noreply(a)lists.ccalternatives.org, 821 bytes Apr 26 12:01:34 2021 (819) <161943849292.814.6140111398379700592(a)zarathustra.ccalternatives.org> smtp to ssan(a)lists.ccalternatives.org for 1 recips, completed in 0.04269862174987793 seconds Apr 26 12:01:34 2021 (819) <161943849292.814.6140111398379700592(a)zarathustra.ccalternatives.org> post to ssan(a)lists.ccalternatives.org from ssan-request(a)lists.ccalternatives.org, 1335 bytes Message sent that only the user receives: Return-Path: <christian(a)sewagesludgeactionnetwork.com> Delivered-To: ces(a)ecovillage.cc Received: from box.ecovillage.cc ([127.0.0.1]) by box.ecovillage.cc with LMTP id MDucNBythmCTSwAAMoO61A for <ces(a)ecovillage.cc>; Mon, 26 Apr 2021 05:07:56 -0700 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on box.ecovillage.cc X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from * author's domain X-Spam-Score: -1.1 Received: from authenticated-user (box.ecovillage.cc [45.79.28.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by box.ecovillage.cc (Postfix) with ESMTPSA id 6EADF3E8CC for <ssan(a)lists.naturalintelligence.us>; Mon, 26 Apr 2021 05:07:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sewagesludgeactionnetwork.com; s=mail; t=1619438876; bh=1M7F/uIS0bNG6cWjecy/a9QjskrHVwJHkjWRv+ffpM4=; h=From:To:References:In-Reply-To:Subject:Date:From; b=jXOswVZgFeHBB+sjIDqVkNBQqIbfZCj9ZUfpVwl10NQEkGaoxckPHNOKT6x9zIqsW BZ7iZqqi2mWprVQ8LrK48Lp7gvCQ/ipqspMeLt3t+uljzTtryHmV6uJFEAU3hqM33Y nQqX6Z8la8Ko40F9Ayb4h4e/MOfPdA4nadgf5hZzt/DzPFZvzUbG3V8lWcHuyJNA2y SQkhbNubQ6iNEEB0SyBjoOjl3g3LVxjxY+9kMGGmX+1PFfW90CpDDShRmKkkscEWaA NiV0fX6U5LENBBnc6Q9ImLgXuaLdCqlBRBumJBk+eUUr007rpXXVAPck2NvUzGyM2v kNNGlT68hGzEg== From: <christian(a)sewagesludgeactionnetwork.com> To: <ssan(a)lists.naturalintelligence.us> References: In-Reply-To: Subject: How US chemical industry lobbying and cash defeated regulation in Trump era Date: Mon, 26 Apr 2021 05:07:37 -0700 Message-ID: <020501d73a94$cbe17440$63a45cc0$(a)sewagesludgeactionnetwork.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0206_01D73A5A.1F831170" Thread-Index: Adc6h7I/qzBKx1yOT6aPOuipppacoQACatZAAADW1wA= Content-Language: en-us How US chemical industry lobbying and cash defeated regulation in Trump era Industry's congressional allies defeated nearly all PFAS legislation while the Trump EPA killed, watered down or slowalked new rules https://www.theguardian.com/environment/2021/apr/26/us-chemical-companies-lo bbying-donation-defeated-regulation -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, April 26, 2021 2:05 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user mail not accepted On 4/26/21 5:16 AM, Christian Stalberg via Mailman-users wrote: > I have a user whose moderation rule is 'Accept immediately' yet when > they send a message for distribution to the list, they only receive it > and it is not distributed via the list. Logfile entries below. Please > advise. Btw I have another list on this same instance which is running fine. Thank you. > > [26/Apr/2021:12:06:25 +0000] "GET > /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=chr > istian %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1257 "-" "GNU > Mailman REST client v3.3.2" > [26/Apr/2021:12:06:25 +0000] "PATCH > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan.lists.ccalternatives.org > HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "POST > /3.1/members/find?list_id=ssan.lists.ccalternatives.org&subscriber=chr > istian %40sewagesludgeactionnetwork.com HTTP/1.1" 200 1288 "-" "GNU > Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/requests/count?token_owner=mo > derato r HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/lists/ssan(a)lists.ccalternatives.org/held/count HTTP/1.1" 200 73 "-" > "GNU Mailman REST client v3.3.2" > [26/Apr/2021:12:06:26 +0000] "GET > /3.1/members/7186cd45bde34d4fa7e7b5ab36b97272/preferences HTTP/1.1" > 200 295 "-" "GNU Mailman REST client v3.3.2" These entries don't tell anything about a post to the list. They are all from Mailman's REST API relating to Postorius interactions with core. However the absence of messages like Apr 26 07:32:39 2021 (17860) ACCEPT: <message_id> and Apr 26 07:32:41 2021 (17857) HyperKitty archived message <message_id> to https://example.com/archives/list/list_adderss/message/message_id_hash/ assuming you are looking at the correct time span, says there wasn't an accepted list post. Mailman's smtp.log may have more info, but the complete, raw message that the user receives may be more helpful. -- 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, 4 months

Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by alexs＠ecoscentric.com

Mark Sapiro wrote: ... > I thing just dumping and loading the databases and copying mailman.cfg > and the Django settings should do it. Are the domains the same on the > new server? If not there may be issues with that. I'd need to see the > exception and traceback to say more. I am migrating from mailman 3.2.1 & mailman3-web 0+20180916-8 on Debian Buster to mailman 3.3.8 & mailman3-web 0+20200530-2.1 on Debian bookworm, have mailman3 and mailman3-web configured (and running on bookworm) from the initial install. But when I use the mailman3-web 0+20180916-8 database (after stopping mailman3 and mailman3-web) on bookworm, unfortunately migrate fails: # mailman-web showmigrations account [X] 0001_initial [X] 0002_email_max_length admin [X] 0001_initial [X] 0002_logentry_remove_auto_add [X] 0003_logentry_add_action_flag_choices auth [X] 0001_initial [X] 0002_alter_permission_name_max_length [X] 0003_alter_user_email_max_length [X] 0004_alter_user_username_opts [X] 0005_alter_user_last_login_null [X] 0006_require_contenttypes_0002 [X] 0007_alter_validators_add_error_messages [X] 0008_alter_user_username_max_length [X] 0009_alter_user_last_name_max_length [X] 0010_alter_group_name_max_length [X] 0011_update_proxy_permissions [X] 0012_alter_user_first_name_max_length contenttypes [X] 0001_initial [X] 0002_remove_content_type_name ... # mailman-web migrate --plan Planned operations: contenttypes.0001_initial Create model ContentType Alter unique_together for contenttype (1 constraint(s)) auth.0001_initial Create model Permission Create model Group Create model User account.0001_initial Create model EmailAddress Create model EmailConfirmation account.0002_email_max_length Alter field email on emailaddress admin.0001_initial Create model LogEntry admin.0002_logentry_remove_auto_add Alter field action_time on logentry admin.0003_logentry_add_action_flag_choices Alter field action_flag on logentry contenttypes.0002_remove_content_type_name Change Meta options on contenttype Alter field name on contenttype Raw Python operation Remove field name from contenttype ... But the migrate fails at the first operation: # mailman-web migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying contenttypes.0001_initial...Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 239, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (1050, "Table 'django_content_type' already exists") ... Indeed the table django_content_type already exists on 0+20180916-8 . Apart from fields changes, there are an additional 4 tables in mailman3-web 0+20200530-2.1 I managed to import the mailman 3.2.1 database to the mailman 3.3.8 database, and all lists, subscriptions and settings looks fine. So how can I upgrade my existing mailman3-web database?

2 years

Mailman-users search results for query "Postorius"