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

[MM3-users] Docker, Mailman 3, templates and list user accounts

by Henrik Rasmussen

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

9 years, 2 months

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Tue, Jan 30 2018, Mark Sapiro wrote: > The underlying issue is the orange.fr domain is sending DSNs without a > Message-ID: header. Yes. Is a Message-ID header required in a DSN by any RFC? > If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] > section of your config), this log message I have verp_delivery_interval = 10 ... > would contain to=<test-bounces+user=example.com(a)my-domain.org> and you > could identify the bouncing address (user(a)example.com in this case) that > way. Yes, that's my intention, but first of all, mailman must receive the DSN. > Beyond that, there are still other issues, the biggest of which is > currently, Mailman is not processing bounces other than storing them in > the database. See <https://gitlab.com/mailman/mailman/issues/343>. Shouldn't the DSNs be forwarded to the owner of the list? > if a recipient MTA can't create a DSN that has a Message-ID:, would > you trust what else it does? I don't know. The question for me is: does the remote MTA needs a fix (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN without Message-ID should be acceptable)? -- Peter

8 years, 8 months

[MM3-users] Re: Log rotation

by Abhilash Raj

On Tue, Apr 10, 2018, at 4:12 PM, Mark Sapiro wrote: > On 04/10/2018 03:04 PM, Darren Smith wrote: > > > > 1) Has anyone come up with a good log rotation strategy that doesn't > > necessitate a restart of the service? > > I think Abhilash has answered this, but for completeness, here's what I > use on lists.mailman3.org which uses nginx and gunicorn > > Mailman's logs > > /opt/mailman/mailman-bundler/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mailman-bundler/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mailman-bundler/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > > mailman-web log > > /var/log/mailman-web/*.log { > missingok > notifempty > delaycompress > su mailman mailman > } > > > And here's mail.python.org with apache and mod_wsgi > > Mailman's logs > > /opt/mailman/mailman-bundler/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true Oh, I didn't know about the "mailman reopen" command, thanks Mark! -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Elias Rudberg

Hello again, Mark Sapiro wrote: > I'm not certain, but I think it's a Django issue > rather than a Mailman issue. I got a reply about this in the Django forum at https://forum.djangoproject.com/t/getting-error-need-2-values-to-unpack-in-… Quoting from that forum post: "This is not a bug in Django. This would be functioning in the manner that Django is designed and documented at [link]" "The error here is trying to use a reference in a template without having the view ensure that the context being passed is correct." "Both the template and the view should be corrected here. The view should ensure the right data is put into the context, probably under a different name, and the template should render that data from that name." (end of quote from Django forum) So they think it is not a bug in Django. Does it make sense, that "the template and the view should be corrected" as suggested there? (The template in question would be pagination.html but I'm not sure exactly how it should be corrected.) / Elias

2 years, 2 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 15:45, Mark Sapiro <mark(a)msapiro.net> wrote: > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Right. There will eventually be additional recurring tasks for Core too though, such as processing the bounce database for disables and unsubs, pulling messages from NNTP, and possibly others as time goes on. I’ve always thought about handling these as commands that cron would run, much as in Mailman 2, but it would also be possible to implement a runner, or runners, to do those jobs. I can see advantages and disadvantages with either approach. > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Yep, thanks for the bug report. `mailman digests —periodic` seems like the right approach. Cheers, -Barry

9 years, 2 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:40 PM, Mark Sapiro wrote: > On 11/11/20 4:18 PM, Brian Carpenter wrote: >> Some sort of auto-discard procedure after a number of retries? Is it >> possible to detect a message with a null characters and automatically >> discard them? Do such messages make it into the thread table? > > The message has been delivered to the list, but it is not archived. The > list post has an Archived-At: header with a URL, but the message isn't > there at all. The only way to get it archived is to correct the message > defect. Does the problematic message (null character) make it to the hyperkitty_thread table? > Thus, I don't think it's good to just discard the message at that point. > I'm fine with moving out of or not queueing it in the first place in > var/archives/hyperkitty/spool, but I think it should be preserved > somewhere, say in var/archives/hyperkitty/bad, and along with that, some > kind of notice sent to the site admin so bad messages don't just > accumulate without being seen. > Can a message with a null character be repaired with an automatic process? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 11 months

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/5/22 02:37, Odhiambo Washington wrote: > > > > Here again, Google-fu came to the rescue. I added the following line to > > settings_local.py and the warnings were suppressed. > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > I need to understand how this affects everything and how this is likely > to > > impact the functionality of MM3. What is the proper solution for this? > > And should it be django.db.models.BigAutoField or > > django.db.models.AutoField? Which is which? > > > Prior to Django 3.2 Django set default primary keys to 32 bit integers. > In 3.2 Django introduced the possibility to set default primary keys to > 64 bit integers by setting the type to django.db.models.BigAutoField. > > Thus, putting > ``` > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > ``` > in your settings will maintain compatibility with pre 3.2 versions and > existing tables and this is the correct thing to do. > Thank you very much for the clarification. -- 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: Hyperkitty fulltext search performances

by Mark Dadgar

On Oct 4, 2020, at 8:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/4/20 8:07 AM, Brian Carpenter wrote: >> >> On 10/4/20 8:59 AM, Loïc Dachary wrote: >>> After a little digging it turns out the mailman3-web Debian GNU/Linux >>> package I'm using is configured to use Woosh as a haystack backend. >>> And it is not fit for volumes greater than a few hundred mega bytes. I >>> should switch to something else from the list of supported >>> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >>> >> For our servers running Postorius/Hyperkitty, we use Xapian. I believe >> the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For >> our Affinity/Empathy servers, we use Elasticsearch which we are very >> happy with. Elasticsearch does have a higher memory requirement I >> believe than Xapian. > > > Brian is correct about this list. We started with Whoosh, then went to > Elasticsearch and ultimately to Xapian. Each step gave better > performance and a smaller footprint than the one before. +1 I have ~700K posts in my archive and Xapian is FAST. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Philip Colmer

On Tue, 4 Jan 2022 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/4/22 6:45 AM, Philip Colmer wrote: > > > > So ... should the archive be deleted when the list is deleted and it is a > > bug that it isn't? Or is it expected that access to the archive is > "frozen" > > once a list is deleted? > > > It is often desired to have a public archive available after the > corresponding list has been deleted. Even for a private archive, it may > be desirable for site admins to have access. Furthermore, a list might > not even have a HyperKitty archive in the first place. Thus, what to do > about a HyperKitty archive (or prototype archive or ...) when a list is > deleted is an administrative decision and is best left up to the site > admins to do it or not. > > As you note with a private archive, former members no longer have access > when the list is gone, but unless an attempt throws some uncaught > exception, that is not a bug. > Thanks, Mark, for the clarification. Regards Philip

4 years, 9 months

[MM3-users] Re: Exception with processing subscription confirmation email

by Eric Broens

Thanks Mark, We are indeed running mailman core 3.3.2 and using mysql. The data appears indeed to be truncated judging from the missing closing curly bracket (see below). Would it be OK to already extend the data column to VARCHAR(510) before upgrading to mailman core 3.3.3, or will this cause problems with upgrading to a newer version? +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | data | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | {"pre_approved": false, "pre_confirmed": false, "pre_verified": false, "invitation": false, "address_key": "******************@************", "subscriber_key": 1, "user_key": "a44e8b9a34c64775b712f383d438ce1d", "token_owner_key": 1, "send_welcome_message" | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ Best Regards, Eric -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: donderdag 29 april 2021 18:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Exception with processing subscription confirmation email On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfc c27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- 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

Search results for query "sapiro"