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

[MM3-users] Re: New domain cannot set set host

by Mark Sapiro

On 11/28/24 10:19 AM, Alain D D Williams wrote: > On Wed, Nov 27, 2024 at 12:42:41PM -0800, Mark Sapiro wrote: >> On 11/27/24 12:18 PM, Alain D D Williams wrote: >>> >>> But it is not in table mailman3web.django_site >>> >>> Please how do I do this ? >> >> Add the domain as a site in the Django web admin UI. > > I did not see this y/day and created the entry in table django_site using SQL. > This might be the cause of the other problems that we have been talking about. It's not likely that this is the cause. > I must admit to finding django daunting -- something that I know nothing about; > I ran "mailman-web --help" and was non the wiser. > > I found the following which did not help either: > > https://docs.mailman3.org/en/latest/django-primer.html Yes, Django can be daunting. It is certainly possible to implement alternatives to Postorius and HyperKitty that use some lighter weight, non-Django framework, and it was always our hope that someone would do this and contribute it. A few years ago, EMWD did implement alternatives using PHP, but at least in part due to the untimely death of EMWD's principal, those remain proprietary. That said, if you follow the installation doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you shouldn't need much Django knowledge beyond that and https://docs.mailman3.org/en/latest/django-primer.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Moving/cloning mailman3

by Mark Sapiro

On 10/18/2017 08:56 AM, Dmitry Makovey wrote: > Hi, > > I am drawing a blank looking for documentation for mailman3 migrations. > How can one dump existing settings for mailman and import it into > another instance? The Mailman 3 command 'mailman import21' is what does this <http://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.ht…>, however there are issues in that not all 2.1 settings are imported at all or correctly and in at least one case on an announce only list, the membership wasn't imported. I intend to work on this, but haven't got as far as even documenting the problems, much less coming up with fixes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:03 PM, Stephen J. Turnbull wrote: > > Lynx is not used in stripping. Do you have the HTML-to-text > conversion option on? If so I can imagine that lack of Lynx would > fall back to stripping (but that would be a bug, of course, and we'd > want to fix it). If convert_html_to_plaintext is True and html_to_plain_text_command fails for any of several reasons including the command not existing, the HTML part is left in the message. > How about spamming the "mailman" (ie, administrator's) list? I think > Mailman 3 still has that? Nope. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: MM3 not starting afte an upgrade -addendum

by Mark Sapiro

On 7/27/20 12:38 AM, Gelpi Andrea wrote: > To solve the problem I had to remove VHOST parameter from config file. > I remember that Vhost was mandatory for my configuration when I set it > up two month ago. > So I don't understand why now I had to remove it to have MM3 working. Are you talking about FILTER_VHOST in your Django settings(_local).py or something else. If something else, I don't know what. If FILTER_VHOST, It has nothing to do with Mailman core. There is this issue with Postorius <https://gitlab.com/mailman/postorius/-/issues/394> which is fixed in Postorius 1.3.3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Mailman3 not delivering list mail

by Mark Sapiro

On 10/1/20 9:27 AM, Gordon Dickens wrote: > It appears that my mailman3 installation has stopped delivering list > mail and that all of the list mail is stuck in > /var/lib/mailman3/queue/bad. > How do I resolve this situation?Â Can I just remove the files with "rm > *" in the /var/lib/mailman3/queue/bad directory?Â Please let me know > what I should do to get things working again. There should be messages in mailman.log like `Uncaught runner exception:` followed by an exception and traceback and possibly `Skipping and preserving unparseable message:` or `SHUNTING FAILED, preserving original entry:`. What do these messages say? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Mark Sapiro

On 8/23/24 8:31 PM, Ken Alker wrote: > We have been experiencing a strange anomaly. We are running a small-ish list. When a particular subscriber to the list sends an email to the list, a couple of dozen (or more) of the recipient's of the message end up with their bounce scores incrementing. The notices of bounce score incrementing, assuming Notify owner on bounce increment is Yes, should contain the bounce DSN. What does it say the reason is? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Mark Sapiro

On 8/30/24 11:00, Ken Alker wrote: > > Unfortunately, now when I respond to list emails (with the re-written From address) my (very old) email client (I still use Mulberry!) defaults to responding to the sender instead of the list, as it had before. I'm hoping this is a nuance of my client and isn't something the other members are going to have to grapple with. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Unable to ban users via mailman-shell

by Mark Sapiro

On 4/13/25 07:53, Mihai Moldovan wrote: > > That might be a bug in mailman 3.3.8, though, and indeed, there is > https://gitlab.com/mailman/mailman/-/issues/1062 which might be partly > relevant. While it is generally a fix for use_ipython: true (which I > don't use), it might have also fixed the banner issue for the > non-ipython case. This was added in Mailman 3.3.1 by https://gitlab.com/mailman/mailman/-/merge_requests/587 The fix for https://gitlab.com/mailman/mailman/-/issues/1062 doesn't affect this if you aren't using ipython. Do you have a setting for `banner` in the `[shell]` section of your mailman.cfg? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/28/25 21:50, Mark wrote: > > Yes, I thought so too. I also tried 0d -- which wrote the expiry date > the same as the created date (to the second). > > # /etc/mailman3/mailman.cfg > [mailman] > cache_life: 0d > > But, just as with writing in a past date, it didn't solve the problem. > I also spun up a brand new server to thrash it out there, but no joy > there either. This is a different issue. See https://gitlab.com/mailman/mailman/-/issues/1231 The template is not removed from the cache until the next run of the task runner which defaults to running every hour. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Which crontab?

by Mark Sapiro

On 11/05/2017 09:18 PM, Pierre Abbat wrote: > > /etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, > my laptop, and my new Mailman box. ALL files in /etc (except links, which are > lrwxrwxrwx and I didn't check what they point to) are owned by root.root or > owned by root.<other> and not group writable, except one, the directory /etc/ > mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are > you saying that Mailman should be able to change its own config file? It looks like your Mailman user is 'list'. That is the user that should be running mailman commands. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

Search results for query "sapiro"