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

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by John Hein

Mark Sapiro wrote at 19:18 -0700 on May 12, 2016: > On 5/12/16 3:46 PM, John wrote: > > But mm 2 had: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > multipart/digest <--- this is the part that's gone in mm3 > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > > So was that removal intentional, a bug or ?? > > > I'm sorry. I missed the point of your OP. I think it's a bug. > > The doctest at > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, > the part just after "The MIME digest has lots of good stuff, all > contained in the multipart." is clearly missing the multipart/digest part. > > It appears that this got lost in the refactoring of the MM2 code for > MM3. Please file an issue at > <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me > (msapiro), but it any case, I'll work on fixing it. https://gitlab.com/mailman/mailman/issues/234 Thanks.

9 years

[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

7 years, 9 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

7 years, 3 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

7 years, 1 month

[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

9 months, 3 weeks

[MM3-users] Re: How to remove global ban using API?

by Nathan Dixon

For those who are interested. To be able to use global_bans = IBanManager(None) and not get the following error: Traceback (most recent call last): File "<stdin>", line 1, in <module>TypeError: ('Could not adapt', None, <InterfaceClass mailman.interfaces.bans.IBanManager>) You need to use: mailman shell Not a standard python3 session. To actually update the global bans not via the API, which has some limitations at the moment (see the issue on Gitlab), I have done the following workaround (later I will put in checks for an existing ban to do an update instead, or a delete then create of the new ban): 1) I create a python script within the docker container within the existing PYTHONPATH that will be the module that runs when I want to create or update my ban (in this case under /usr/bin/) #!/bin/env python def create_valid_domains_ban(valid_domains_regex): from mailman.interfaces.bans import IBanManager global_bans = IBanManager(None) global_bans.ban(valid_domains_regex) print(list(global_bans.bans)[0].email) 2) I can then invoke this as a mailman module from the server using docker exec mailman-core mailman shell -r create_valid_domains_ban $valid_domains_regex On Wed, 15 May 2019 at 21:21, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/19 9:46 AM, Nathan Dixon wrote: > > > > I can create the ban fine by the following: > > > > from mailmanclient import Client > > client = Client(URI,apiuser,apipass) > > > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") > > > This is apparently a typo - missing ')' - in the re as you have it > correct below. > > > > However, I cannot seem to be able to remove it using the api: > >>>> client.bans[0].delete() > ... > >>>> client.bans.remove(str(client.bans[0])) > ... > >>>> > > > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") > > > All of the above work for me with both API 3.0 and 3.1 in a non-docker > install of the current GitLab HEADs > > > > And also, when I now try and go into the mailman-core docker image to use > > the mailman.interfaces.bans, it will not let me see the global bans: > > > >>>> from mailman.interfaces.bans import IBanManager > >>>> global_bans = IBanManager(None) > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > TypeError: ('Could not adapt', None, <InterfaceClass > > mailman.interfaces.bans.IBanManager>) > > > I don't see this either. > > > > I have opened an issue in Gitlab for this as I feel it may be a bug > related > > to regex and global bans (there was a similar one for list banned > > addresses): https://gitlab.com/mailman/mailman/issues/598 > > > I also commented on the GitLab issue. I think this must be an issue with > the docker images. > > -- > 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/ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

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

7 years, 9 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

4 years, 6 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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 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

4 years, 7 months

Search results for query "sapiro"