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

[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

4 years, 5 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, 9 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, 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, 11 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, 9 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

4 years, 1 month

[MM3-users] Re: Internal Server Errors in mailmanweb.log

by Washington Odhiambo

On Thu, Dec 25, 2025 at 12:07 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/18/25 03:07, Washington Odhiambo via Mailman-users wrote: > > I keep seeing several errors like the below in my mailmanweb.log and not > > sure what the causa is. > > What is your HyperKitty version? If it is 1.3.12 from PyPI and not the > latest from gitlab, See > https://gitlab.com/mailman/hyperkitty/-/issues/529 and > https://gitlab.com/mailman/hyperkitty/-/merge_requests/660 for a patch > to fix this. > It is version 1.3.12. Patch applied. Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 months, 1 week

[MM3-users] Re: Is there a "global" max_message_size?

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > Mailman's lmtp runner which implements the server that receives mail via > LMTP uses the aiosmtpd.lmtp.LMTP class to implement the server. This has > a default size limit of 33554432 bytes (32 MB) and that's where the "552 > Error: Too much mail data" comes from. Ah - fantastic! I had tried a fairly crude trawl through the mailman-core container files (not knowing what exactly to look for really), but failed to come up with anything. > There is also the message_size_limit setting in postfix. Presumably > you've changed that because it defaults to 10240000 bytes (about 10 MB). Yes I fortunately did remember to set this to a very high value (way higher than 32MB) during testing. Thanks so much for the explanation Mark, very much appreciated. Stephen

5 years, 9 months

[MM3-users] Re: Moderated Signup with "info" box?

by Brian Carpenter

On 12/7/20 10:13 PM, Mark Sapiro wrote: > On 12/7/20 8:01 AM, Brian Carpenter wrote: >> Keep in mind that Mailman 3's REST API is only accessible locally. So to >> access Mailman 3's REST API from another server is not remotely >> possible. (see what I did there?) > > The REST API is only accessible locally by default. It is certainly > possible to configure the webservice section of mailman.cfg to be able > to access it remotely - if you do this, be sure not to use the default > admin_pass. There is also an authenticating REST proxy project called > lemme (possibly abandoned) at <https://gitlab.com/mailman/lemme>. Thank you for the clarification. I did not know that. Is that made clear in the documentation? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] Re: Sanity check of upgrade procedure

by David Newman

On 10/26/22 6:14 PM, Mark Sapiro wrote: > >> Attempting uninstall: mailman-web >> Found existing installation: mailman-web 0.0.6.dev9+gc606169 >> Uninstalling mailman-web-0.0.6.dev9+gc606169: >> Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 >> ERROR: Could not install packages due to an OSError: [Errno 13] >> Permission denied: 'WHEEL' >> Check the permissions. >> >> The command also said I needed to upgrade pip. Doing that produced a >> similar error. >> >> How to resolve this error? Thanks again. > > Was the venv initially created as the `mailman` user? Maybe > > sudo chown mailman:mailman /path/to/venv > > will fix it. Yup, that was it. Some Django directories were owned by root. The installation ran clean after running 'chown -R mailman:mailman' on those directories. Thanks! dn

3 years, 5 months

Search results for query "sapiro"