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

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

by Mark Sapiro

On 08/09/2017 02:35 PM, Abhilash Raj wrote: > Hi, > > On Wed, 9 Aug 2017 13:42:20 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> # Send periodic digests. >>> # I like 03:30 so they go overnight, but since we're 'global' and on UTC, >>> # maybe 07:30 is good. >>> 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > well? It's only that one and whether it's needed or not depends on list configuration. The list has attributes digest_send_periodic and digest_size_threshold. When a post is received it is added to the list's digest mbox, and if that causes the size of the mbox to reach digest_size_threshold K bytes, a digest is sent. Additionally, if digest_send_periodic is true, a digest is sent periodically whether or not it has reached digest_size_threshold. However, the sending of periodic digests depends on cron running something periodically to actually trigger the sending. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Disable "confirmation emails"

by Mark Sapiro

On 09/18/2018 01:46 PM, Hagen Bauer wrote: > > even after a lot of google search I could not find a way to disable the > Confirmation Mails like > .... > The results of your email command are provided below. > > - Original message details: > ....... > > Is there a way to do this? I have users who would be irritated and I > dont want them to recieve this Where are you seeing these? There were changes in this area in Mailman core v. 3.2.0 and I think these now should only be sent in response to mail to the -request address that contains a command other than (un)subscribe or confirm. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Disable response to the list request address

by Mark Sapiro

On 2/4/20 11:03 PM, Dieter Leupold via Mailman-users wrote: > Hi all, > > a short question (MM3.1.1): is it possible to avoid responses when > someone sends emails to the request-address (xxx-request(a)lists.xxxx.com) > of a mailinglist? > Thanks for your information! It is not currently possible. What responses are you trying to avoid? If you are interested in not responding to spam sent to the -request address, we could possibly implement a setting to not respond to messages that contain no valid commands and/or messages exceeding some maximum size. You could file an issue requesting this at <https://gitlab.com/mailman/mailman/issues>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 4/23/20 12:11 PM, Gelpi Andrea wrote: > > > I can confirm that the fix works. > > Thank You so much. Thank you for testing and reporting. Note I have just made one minor change to the fix. Where I had in the added code > if (MailDomain.objects.get( > mail_domain=domain.mail_host).site.name == web_host): I now have > if (MailDomain.objects.get( > mail_domain=domain.mail_host).site.domain == web_host): The issue is site.name is the domain's display name whereas the domain name is site.domain. This only matters if you have given the site a display name different from the domain name in Django. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Unable to remove non-member

by Mark Sapiro

On 9/28/20 6:43 AM, Brian Carpenter wrote: > Hi Everyone, > > I ran across a strange issue today. A client reported the inability to > remove a non-member in the following format: > > z_email/domain.org.za(a)domain.org.za > > The reported error from Postorius was: > > "The user could not be removed" Is that all it said? The code says it is The user could not be removed: <error message> Where <error message> is the relevant HTTP error. > I used https://verifalia.com/validate-email to validate the email > address and it is syntactically correct. Mailman core thinks it's OK too as does RFC5322. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: List Digest - Subject line

by Mark Sapiro

On 5/12/21 1:44 PM, smorytko(a)gmail.com wrote: > Steve, > > Right you are! Yahoo! Mail apparently disassociates the header information from the text body so I can only see it in the Today's Topics summary, while GMail does not and offers it in both locations. One thing you can try is have your Yahoo users subscribe to the plain text rather than the MIME digest. Generally, at least with good MUAs, MIME is preferred because it preserves non-text parts and allows replying to an individual message as opposed to the digest, but clearly Yahoo is not one of those MUAs and Yahoo users will probably find plain text digests preferable. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Mailman3 subscribe over command line

by Mark Sapiro

On 9/17/21 1:46 AM, tibor.molnar(a)waltoninstitute.ie wrote: > If I try using this command the following error occurs: > >>>> from mailman.testing.documentation import cli >>>> command = cli('mailman.commands.cli_addmembers.addmembers') > Traceback (most recent call last): ... > ModuleNotFoundError: No module named 'mailman.commands.cli_addmembers' What Mailman version is this? The add_members mailman subcommand was added in 3.3.2 and didn't exist before that. In Mailman 3.3.1 and prior, you need to use the members subcommand with the -a/--add option. Also note that mailman.testing.documentation.cli is only intended to be used for tests and not production. See https://click.palletsprojects.com/en/8.0.x/testing/#testing-click-applicati… -- 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: How to change rest APi password

by Mark Sapiro

On 10/25/21 11:05 AM, bob B wrote: > This is probably s stupid question but I have been searching for an answer. > > How do you set a different rest api password? > > The instructions say : > The credentials are set in the [webservice] section of the configuration using the admin_user and admin_pass properties. But what is that referring to? > > I am running docker, so is this in the docker.yaml file (I tried it there it did not work) or in the Django config file or someplace else? It's in mailman.cfg. Where that file is in the docker container, I don't know. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/7/22 12:56 AM, Stephen J. Turnbull wrote: > Thanks to Guillermo for the heads-up. > > As far as I can tell, neither of these functions is used in the > Mailman suite itself. That doesn't mean they aren't used in one of > our dependencies, but it does mean that we can't do much about what's > installed on your host. You should upgrade if you are using Django 3 > or 4. (Not sure we support Django 4.) We will keep a watch on this. I just upgraded from Django 3.2.11 to 3.2.14 on mail.python.org and lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Lost messages - was: Re: Do you struggle with message rejected. AUP#CDRBL while using mailman with your ISP email relay?

by Mark Sapiro

On 4/18/25 9:37 AM, Michael Richardson wrote: > > My problem, on lists.sandelman.ca aka lists.tcpdump.org, is messages that > appear to have been processed by my MTA (according to postfix logs), but > which are never delivered, nor held. Lost somewhere in mailman3 queue. > Sometimes they show up after a host reboot. It seems that maybe not all the runners are running. What's in Mailman's various var/queue/* directories? What's in Mailman's var/logs/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

Search results for query "sapiro"