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

[MM3-users] Re: user mail not accepted

by Christian Stalberg

My apologies. I did not confirm that what I did already sent you was the message received by the user. The mailing list address is ssan(a)lists.naturalintelligence.us and it seems as though this became an alias for this single user christian(a)sewagesludgeactionnetwork.com . > What I wanted to see was not the message sent to the list, but the message received by the one user from the list. If you are saying this message is that, it didn't come from any Mailman list. > > > 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-compan > ies-lo > bbying-donation-defeated-regulation > > -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, April 26, 2021 5:54 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user mail not accepted On 4/26/21 5:41 PM, Christian Stalberg via Mailman-users wrote: > No. there was no response received by the user a la "results of your > email commands" > message. Simply the original email sent to the list. I would still like to see the complete raw message as received by the user. That's the only thing that can tell me how it got to that user and provide clues as to why it didn't go to the other list members. -- 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

[MM3-users] Re: sass error

by Alexander Klotz

Am 19.04.18 um 16:41 schrieb Mark Sapiro: > On 04/19/2018 02:41 AM, Alexander Klotz wrote: >> Hi everybody, >> >> we tried to make a fresh installation out of the current version >> following the readme.md - we encounter the following error trying to do >> so. As mentioned elsewhere, 'sass' has been replaced by 'sassc', >> however, maybe somewhere there is still a reference to it that may have >> been overlooked? The answer to a similar error posted to this list in >> August 2017 unfortunately didn't help either. > > > What do you have in your Django settings for COMPRESS_PRECOMPILERS? > > Do you actually have sass or sassc installed? > Hi Mark, the error was indeed in our local django setting, it still said "sass" on there - sorry and thanks! Regards, Alex

7 years, 4 months

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 4:18 PM, Mark Sapiro wrote: >> Ok. I guess first I've got to figure out where the database lives. >> I've not been hacking on mm3, just using it. > > What's in the [database] section of your mailman.cfg? and the DATABASES > definition of your Django local settings. > > The database is managed by some database manager. If it is Postgres or > MySQL/MariaDB, there are actual database servers. If it is the default > SQLite, it's probably Mailman's var/data/mailman.db Ok, I will dig into it in the coming days. (and I will take a lot of notes this time) Thank you for the pointers. I'll come back on this if I need further help figuring it out. As always, I appreciate your time. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 1 month

[MM3-users] Re: uncaught bounce messages

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > On 10/23/21 4:23 PM, David Bremner wrote: >>> 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. > > > I don't think it's a flufl.bounce issue. I think it's a Mailman 3.2.1 > issue - https://gitlab.com/mailman/mailman/-/issues/622 which is fixed > in Mailman 3.3.0 Oh great, I just upgraded to Mailman 3.3.0, so I'll see what happens. I did notice a bunch (10 or 20?) of subscribers being disabled for being over the bounce threshhold right after the upgrade, I wonder if that is related. d

3 years, 10 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, As you know, we can edit the individual messages using the message_id_hash. Is there any possibility that we can edit the original message which then updates all of the threads it has (for example, if someone already replied to the original message)? Or do we need to edit each message manually? Kind regards, Prasanth On Wed, 29 Sept 2021 at 15:46, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Many thanks for your help. I have managed to modify some of the messages > after following your instructions. > > Kind regards, > Prasanth > > On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> > wrote: > >> Hi Mark, >> >> Thank you for your help. Let me try this. >> >> Kind regards, >> Prasanth >> >> On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 9/28/21 6:02 AM, Prasanth Nair wrote: >>> > Hello, >>> > >>> > Does anyone know how to edit an archived email in Mailman3? It is >>> possible >>> > in Mailman2 ( >>> > >>> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >>> ). >>> > Is there any option similar to this in Mailman3? >>> >>> >>> In some sense the process is the same but possibly even simpler in >>> Mailman 3. You need to modify the underlying data which requires >>> appropriate access to the server. >>> >>> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >>> database. You can get the Message-ID hash from the URL to the archived >>> message, e.g. for the message to which I'm replying, the URL is >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >>> access, you can do database queries like >>> ``` >>> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >>> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >>> ``` >>> and >>> ``` >>> UPDATE hyperkitty_email SET content = '<new content>' WHERE >>> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >>> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >>> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >>> ``` >>> If the message has attachments, they are in the hyperkitty_attachment >>> table and can be referenced by `email_id` which is the corresponding >>> `id` from the hyperkitty_email entry. >>> >>> You can also do similar things via `django-admin shell`. E.g. >>> ``` >>> $ django-admin shell >>> Python ... >>> (InteractiveConsole) >>> >>> from hyperkitty.models.email import Email >>> >>> x = >>> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >>> >>> print(x[0].content) >>> ``` >>> but this requires some knowledge of HyperKitty's models and Django's ORM. >>> >>> -- >>> 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, 11 months

[MM3-users] Re: Auth question

by David Krantz

On Mon, Apr 10, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in > production.py or wherever, you have set > > MAILMAN_ARCHIVER_KEY = 'arch_secret' > > in mailman_hyperkitty.conf you set > > [general] > ... > api_key: arch_secret > > No quotes around the api_key value. Ok, I'll try that. Thought that I had, but probably not just that combination then. Also: Found a bug in Hyperkitty, or at least in my setup: Private lists are visible in the "By Name" dialog in the archives when not logged in. The actual content is not visible, but the activity statistics is displayed (although there is none as the login for archiving as of yet does not work). Hopefully this will correct itself when the communication mailman3-hyperkitty gets active. cheers // David

8 years, 4 months

[MM3-users] Re: Auth question

by David Krantz

On Mon, Apr 10, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in > production.py or wherever, you have set > > MAILMAN_ARCHIVER_KEY = 'arch_secret' > > in mailman_hyperkitty.conf you set > > [general] > ... > api_key: arch_secret > > No quotes around the api_key value. Ok, I'll try that. Thought that I had, but probably not just that combination then. Also: Found a bug in Hyperkitty, or at least in my setup: Private lists are visible in the "By Name" dialog in the archives when not logged in. The actual content is not visible, but the activity statistics is displayed (although there is none as the login for archiving as of yet does not work). Hopefully this will correct itself when the communication mailman3-hyperkitty gets active. cheers // David

8 years, 4 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 6:19 PM, Mark Sapiro wrote: > If you have it, look through the mailman.log for entries around the last > time the connections started to be refused. See if there are entries > about the runner exiting. Also, just before you restarted, there will be > several runner caught SIGTERM. Stopping. and runner exiting. messages. > If lmtp runner is among those, it was still running when you restarted. So lmtp runner was NOT running when I restarted mailman core, however I saw no error messages in the mailman.log at the time of the first instance of the connection refused message. -- 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, 2 months

[MM3-users] Re: aborted connection

by Sandor Dibuz

On 2/19/22 20:46, Mark Sapiro wrote: > On 2/19/22 05:23, Sandor Dibuz wrote: >> >> Feb 19 14:15:18 localhost mariadbd[28859]: 2022-02-19 14:15:18 22154 >> [Warning] Aborted connection 22154 to db: 'mailman3' user: 'mailman3' >> host: 'localhost' (Got an error reading communication packets) > > You may be correct in your assumption that these are harmless. I would > try to correlate them with access and error logs from the web/wsgi > server to get more information. It's the mailman quarterly cron job: # 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 And I have no gateway enabled for any of them. Will have to find out what mailman exactly does. And change MariaDB to verbose logging. Sanyi

3 years, 6 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Odhiambo Washington

The nomenclature aside, if you follow the above link, you should have a running MM3 without much ado, seeing as even your version of PostgreSQL is less than 15, where a little nudging is required :) On Thu, Jul 4, 2024 at 12:38 AM Keith Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > Odhiambo, Yes, trying to. > > Mark, I'll review your suggestions. > > Thanks. > > On Wed, Jul 3, 2024, 12:52 Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > > > > > --------------------------------------------------------------------------- > > > First issue:Postfix v3.5.8 on RHEL 8. > > > The below is from journalctl -xe: > > > > > > --------------------------------------------------------------------------- > > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > > directory > > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > > directory > > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > > directory > > > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > > specified in the mailman.cfg file. > > > How do I find out how to populate the postfix_domains.db files, and > > > the postfix_lmtp.db file? > > > > > > The `mailman aliases` command generates the postfix_domains and > > postfix_lmtp files and calls the configured postmap_command (default > > /usr/sbin/postmap) to create the .db files. `mailman start` also > > generates these files by default. > > > > > > > > > > --------------------------------------------------------------------------- > > > Second issue: Postgresql authentication. > > > PostgreSQL v10.23. > > > > > > --------------------------------------------------------------------------- > > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > > same complex password in the mailman3 config file: > > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > > > > I don't think you should have two /mailman3 at the end > > > > the form is `postgresql://user:password@host:port/database_name` The > > default port is 5432. > > > > -- > > 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 keith1christian(a)gmail.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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

Search results for query "sapiro"