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

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

by Mark Sapiro

On 2/10/25 12:09, Lieuallen, Thomas Otis via Mailman-users wrote: > > 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 The setting is actually `cache_lifetime` in the `[mailman]` section of mailman.cfg, however when a file is cached, it's lifetime is saved in the database and won't be changed by changing that setting. > Without further information or direction, I’m tempted to just remove those cache files and move on with life. Removing them is OK, but a database entry will still exist pointing to them and attempt to retrieve them will return `Cache content lost`. The way to properly remove them is in Mailman shell ``` $ mailman shell 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. >>> cm = getUtility(ICacheManager) >>> cm.clear() >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Link another address

by Mark Sapiro

On 5/18/20 5:13 PM, Brian Carpenter wrote: > I am thinking about incorporating the following Postorius/Django account feature into Affinity: > > Other emails: (no other email) Link another address > > However I cannot think of a serious real-world need for this. What are the developers' reasoning behind this? Was this feature highly demanded by Mailman 3 users? Just trying to find out what I am missing here. In mailman 2.1 there was no concept of user. There were only lists and list members and list members were just email addresses that had no connection to other list members even if they happened to have the same email address. In mailman 3 we have users. Users can have multiple addresses. a user or a particular user's address can be a regular member and an owner of one list, a moderator of another list and a non-member of a third list. Some other address of that user can be a digest member of the first list. All of these addresses and roles can belong to a single user and be managed from that user's one account. Sure, each address can be separate with it's own login, but isn't it more convenient if they are all linked under one login if they all belong to one individual. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Hyperkitty "All Threads" results in error

by Mark Sapiro

On 10/14/20 11:12 AM, Mark Dadgar wrote: >> On Oct 4, 2020, at 10:34 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >> >> So I have been wrestling with this problem for a while now. Most times, but not every time, when someone clicks on the All Threads link in hyperkitty, a 500 error is generated. Does this happen on all lists, only some lists or only one list? >> I googled it, obviously, and at first I thought it was related to this issue, but that has not proven to be the case: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… What did you google? This query gets a lot of stuff with some hints, but nothing definitive. django render raises VariableDoesNotExist("Failed lookup for key " One thing I noted at <https://askbot.org/en/question/3095/django-error-variabledoesnotexist-faile…> was models out of date - run python manage.py syncdb and python manage.py migrate You could try that. Note that your django admin command might be something other than `python manage.py`. Also note syncdb has been removed from Django >=1.9. Currently, the above becomes `makemigrations` followed by `migrate`. I also suggest running the django admin commands `collectstatic --clear --noinput` and `compress` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On 3/26/21 11:31 AM, Brian Carpenter wrote: > I keep seeing bounces being recorded in logs/bounce.log that have no > corresponding entry in Postfix's mail.log. For instance one address had > registered about 2 dozen bounces in the past week in bounce.log and yet > every single entry for this address in mail.log has a status=sent. What > am I missing here? They are being bounced by a downstream MTA. If you want to know why, you have a few choices. You can mail the address yourself and hopefully get a DSN back. You can install this patch: ``` > diff --git a/src/mailman/runners/lmtp.py b/src/mailman/runners/lmtp.py > index 6a0bdcf5e..eca474089 100644 > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -217,6 +217,8 @@ class LMTPHandler: > slog.debug('%s subaddress: %s, queue: %s', > message_id, canonical_subaddress, queue) > status.append('250 Ok') > + if queue == 'bounces': > + config.switchboards['bad'].enqueue(msg, msgdata) > except Exception: > slog.exception('Queue detection: %s', msg['message-id']) > config.db.abort() ``` which will add all received bounces as queue files in Mailman's var/queue/bad. At some point, we need to implement the attachment of the bounce DSN to the notices sent to the admin, but that isn't done yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

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

by Mark Sapiro

On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote: > Running Mailman 3.3.10 > > I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look. Are old ones being delivered and new ones added or the same ones just being renamed? I suspect the latter and I suspect the issue in that case is probably due to the OUT runner trying to access a template file like list:member:{regular|generic}:{header|footer}.txt and not having permission. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though. The files are python pickles and `strings` shows lots of stuff. The ! may be something in the pickle that's not part of the email address. The way to examine these files is with the `mailman qfile` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: footer template priority

by Mark Sapiro

On 6/19/25 12:06, Sam Darwin via Mailman-users wrote: > It seems templates can be configured in the filesystem or via postorius. When I place a footer template in the filesystem it worked fine. Then without adjusting any configuration, without removing that, I tried to use the postorius control panel to add a footer template, which ends up in the database, both the core and web databases. > > But emails stop getting sent out. Emails were posted into Hyperkitty, but not mailed out via postfix. This is a known issue when header and/or footer templates are not accessible. > I checked on the server for "queued emails" and did not find those either, in postfix or mailman. Mysterious. The phenomenon is repeatable on this server. Add a footer template, emails stop. The mails should be in Mailman's var/queue/out queue. Since the issue only occurs in your case when you have a Postorius template, I suspect the issue is in your setting for POSTORIUS_TEMPLATE_BASE_URL. When you have the Postorius template set, what does the database query ``` SELECT uri FROM template WHERE name = 'list:member:regular:footer' and context = 'your.list.id'; ``` return for the uri? is it retrievable? The initial part of the uri up to but not including `/mailman3/api/...` comes from the POSTORIUS_TEMPLATE_BASE_URL setting -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 days, 19 hours

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 12:58 PM, brian(a)emwd.com wrote: > > I have this in the apache2.conf file: > > ServerName localhost > > I can access the apache default page when using the following: > > curl http://localhost.com OK, so you can get to Apache, but can you proxy to uwsgi? Try curl http://localhost/mailman3/hyperkitty/api/mailman/archive or curl http://mailman3-lists.com/mailman3/hyperkitty/api/mailman/archive >> Set base_url in mailman-hyperkitty.cfg to use an acceptable host name >> instead of localhost or adjust your apache config to accept localhost. > > Isn't ServerName enough? It should be. The error is apparently elsewhere. > This error also appears in the apache log file when new posts are sent to the list: > > [Thu Apr 11 19:55:38.755750 2019] [:error] [pid 21370:tid 139988922513152] (32)Broken pipe: [client ::1:49574] sending data to httpd-UDS:0 failed The broken pipe is apparently from the exception in mailman-hyperkitty and the 'sending data to httpd-UDS:0 failed' is I think a normal response from uwsgi under this circumstance. I don't know what the issue is, but it is something in the Apache/uwsgi configuration. I note that the client in the above error is an IPv6 loopback address. That may be significant. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Mark Sapiro

On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > Prasanth Nair writes: > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec can't > > encode character '\ufffd' in position 252: ordinal not in range(128).* ... > > I ran the check_hk_import script before migrating and it was not > > giving any error. > > In order to catch this kind of error, the check script would have to > pretty much do the import but throw it away. The check_hk_import script <https://www.msapiro.net/scripts/check_hk_import> is designed to detect and report conditions which would cause the django hyperkitty_import process to abort and stop processing the mbox. It doesn't catch errors like the above, but these are non-fatal and just cause the offending message to be skipped. As Steve says, the Message-ID was reported so find it in the mbox and if you want it in the archive, extract it from the mbox, fix it and then just rerun the import with just that message as input[1] and a --since=1970-01-01 option. Note the issue could be in a header, but also could be in a body part implicitly or explicitly declared as charset="us-ascii". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: question about recommended postfix configuration

by Mark Sapiro

On 10/02/2017 05:37 AM, Marc Sluiter wrote: > > I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert. Neither am I ;) > This is recommended: > > transport_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = > regexp:/opt/mailman/core/var/data/postfix_domains > > This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost. On mail.python.org which is a complex Postfix environment with both Mailman 2 and Mailman 3 lists in the @python.org domain, for Mailman 3 I have just transport_maps and relay_domains as recommended (but as hash tables) I don't have anything for Mailman in local_recipient_maps, but python.org is in virtual_alias_domains (not in virtual_mailbox_domains). I think it could be either, and virtual_alias_maps (or virtual_mailbox_maps) does not require anything for Mailman because transport_maps handles it. I think the bottom line here is the list domain must be in one of mydestination or virtual_*_domains. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: including a template failed

by Mark Sapiro

On 9/23/20 3:03 PM, Wolfgang Bock via Mailman-users wrote: > > Dear Mark, > > Q: Can you get > https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li > sts.domain-03.de/list:member:regular:footer on the Mailman machine? > > A: No > > Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? > > A: > was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' > > Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Can you get https://localhost/mailman3/postorius/api/templates/list/mylist.lists.domain… on the Mailman machine? > Now another problem occurs: > > Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool ... 'localhost' doesn't match either of > 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', > 'domain-04.de', 'www.domain-04.de'"))) The 'HTTPSConnectionPool' message has nothing to do with the 'Cannot connect' issue. > Port 25 entry results from the manual regarding the postfix configuration: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht > ml > > e.g.: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com > smtp_port: 25 And I wonder why it's trying to connect to localhost when smtp_host is mail.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Search results for query "sapiro"