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

[MM3-users] Re: changing the main template for subscriptions and more

by Mark Sapiro

On 2/1/22 12:40, Paul Paulchen wrote: > Hi Mark, > > thanks for your advice. Unfortunately we need some more clues. > First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman I do not know what the file layout is in the Docker container, so I can't verify paths. > Our version: > Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > > We put an example footer.txt into the templates folder as you mentioned: > mailman3_core => var/templates/sites/de/list:member:regular:footer.txt > Mailman user can read them As I said, I can't give you an absolute path. If you can run `mailman info` in the container, that will show the location of mailman.cfg which may help Installing the template as you have should work if it's the correct path. > Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt The default templates are in the mailman/templates/ directory where the mailman/ directory is where all the Mailman core software is. Hopefully someone familiar with Docker and the Mailman Docker container can provide better information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: unwanted chunked delivery

by Mark Sapiro

On 1/7/22 11:04 AM, mm3-omf(a)sh.werbittewas.de wrote: > debian-dist mailman3 3.3.3-1. > > every post to this list will be chunked into one delivery with 60 > recipients and one delivery with 21 recipients. > > we've searched a bit and found a config-option "max_recipients" for > bulk-transfers, but we haven't set it and (as we understand the > explaination for this option) then there should be no limit in one > transfer to the MTA. If you haven't set max_recipients, you get the default which is 500. To set it unlimited you set it to 0 > nevertheless, we've tried to set it to a high value, but even this > doesn't change anything in behaviour. Right, because chunking isn't arbitrary. Chunking is done by recipient domain. The addresses are placed in `buckets` by TLD. All `.com` goes in one bucket; `.net` and `.org` in another; `.edu`, `.us` and `.ca` in a third, and all the rest in a fourth. Then the buckets are chunked with the maximum chunk determined by max_recipients. In your case, 60 recipients are in one bucket and 21 in another. The buckets are defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L29 and the work is done at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L56 My question is why is this important to you? See the FAQ article at https://wiki.list.org/x/4030582 (which is for Mailman 2.1 so it talks about SMTP_MAX_RCPTS which is what max_recipients used to be called) which suggests a much smaller number. -- 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: Installing mailman 3

by Rafael Mora

I think you have to open a new issue to modify the website for the mailman-suite git clone, it should be: git clone https://gitlab.com/mailman/mailman-suite.git El vie., 21 jul. 2017 a las 14:07, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Installing mailman-suite for web ui. I did this: > > (env) [mailman@localhost ~]$ git clone > https://gitlab.com/mailman/mailman-suite/ > Cloning into 'mailman-suite'... > error: RPC failed; result=22, HTTP code = 404 > fatal: The remote end hung up unexpectedly > > > but it returned an error, what should I do?? > > Thanks > > > > > > > > El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 10:29 AM, Rafael Mora wrote: >> > Can we modify the docs? >> > >> > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) >> > escribió: >> >> >> >> However, that said, the doc is wrong. The lines should be added to >> >> main.cf, not master.cf. See >> >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. >> >> >> That's what the above issue and associated MR are for. >> >> -- >> 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 >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- Atentamente / Best Regards Ing. Rafael Mora

9 years, 1 month

[MM3-users] Re: Template path

by Mark Sapiro

On 9/17/20 9:33 AM, Seth Seeger wrote: > Hello everyone, > > I’m running Mailman from Docker containers, without much customization. (Postorius 1.3.3, Core 3.3.1, API 3.1, Python 3.8.5). I’ve created a list:user:notice:welcome template, and when I try to confirm a subscription, I get an error. > > I followed previous emails on this list which told me to set POSTORIUS_TEMPLATE_BASE_URL in /opt/mailman/web/settings_local.py, but that doesn’t seem to make any difference. (I set it to a different value and the error message didn’t change. I also tried setting it in /opt/mailman/core/settings_local.py to no effect. After each change, I restarted mailman-web and mailman-core containers.) How did you create the template? In Postorius or by manually creating a file somewhere? If by creating a file, POSTORIUS_TEMPLATE_BASE_URL is not relevant, but ensure that the file is findable and readable by Mailman. > From within mailman-web and mailman-core containers, I can reach “mailman-web:8000”. > > In the webpage, I see: Mailman REST API not available. Please start Mailman core. The REST APT is normally exposed on port 8001, not 8000 (See `port` in `mailman conf -s webservice`. What is your setting for MAILMAN_REST_API_URL? does the port match? > In /opt/mailman/core/var/logs/mailman.log, I get: > > [17/Sep/2020:16:23:29 +0000] "GET /3.1/lists/xxx.example.com HTTP/1.1" 200 416 "-" "GNU Mailman REST client v3.3.1" It appears you are connecting to the REST API, but ... ... > urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) Something appears to be trying to connect to REST on port 8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: "held for moderation" - alias domain details sought

by Mark Sapiro

On 11/1/24 11:14, Jeremy Stanley wrote: > On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: >> Hi friends. I've viewed this old thread: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> and documentation here: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… >> (and the Postfix docs it links to). Those documents don't seem to guide my >> situation, or maybe I just need a more specific example. The alias domain discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has nothing to do with what you are doing. >> The problem is that when messages are delivered to the alias domain, they >> are held for moderation. I.e., mail to the alias domain like >> testlist(a)domain.tld is held for moderation, but mail from the same >> subscribed, non-moderated user to testlist(a)lists.domain.tld is posted >> immediately without moderation. > [...] > > I manage a similar setup (though with Exim instead of Postfix), and > when migrating from Mailman v2 to v3 kept the same basic settings > which seemed to work: notably, under Message Acceptance I set the > alias addresses for the list in the Acceptable aliases field. If > memory serves, not doing that caused messages addressed to those > aliases to be unconditionally held for moderation. This is the correct solution. Just add `testlist(a)domain.tld` to the acceptable aliases setting of the `testlist(a)lists.domain.tld` list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 02:14 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users (< > mailman-users(a)mailman3.org>) escribió: > >> You've said you're working with labbrands.com. >> >> labbrands.com has address 192.185.51.89 >> mail.labbrands.com has address 192.185.51.89 >> www.labbrands.com is an alias for labbrands.com. >> >> telnet proves that Exim is running on that IP address. Either you're >> running it, or hostgator is redirecting the SMTP ports. >> >> You added: >> lists.labbrands.com has address 190.145.27.66 >> >> Presumably that's a different machine. >> >> So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > [image: image.png] > > Is it correct??? Your screen shot, along with the excessive quoting, only caused your post to be "too big". All the screen shot says is you have two MX records. The higher priority, 0, is mail.labbrands.com and the lower priority , 1, is lists.labbrands.com. What this means is mail to the domain will be delivered to mail.labbrands.com unless that server is somehow unreachable in which case lists.labbrands.com will be tried. This is probably not what you want. I hate to say this at this point, but you are on a cPanel host. cPanel provides a functional Mailman 2.1 service. You might save yourself a lot of grief by just using that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: django request error

by Mark Sapiro

On 10/13/21 3:38 AM, eggert--- via Mailman-users wrote: > What's strange, my mailman-web is referred to by > https://lists.tdl/mailman3/ > this show the message as above: > This page either doesn't exist, or it moved somewhere else. > The links in that page refer to urls like: > https://lists.tld/mailman/postorius/lists/ > This URL does not exist, of course. Where is the mailman3 replaced by mailman? All my config files refer to mailman3. How have you installed Mailman? We usually use links like https://example.com/mailman3 and https://example.com/archives in docs for Postorius and HyperKitty respectively. These are the ones in urlpatterns in mailman-web/urls.py We have also used https://example.com/postorius and https://example.com/hyperkitty as alternatives. To enable these, you need to add ``` url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ``` to the definition of urlpatterns in urls.py so it becomes something like ``` urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), ] However, that doesn't explain why your `mailman3` URLs get munged to `mailman`. That is apparently a uWSGI thing, and since I've never used uWSGI, only gunicorn and mod_wsgi, I can't help with that other than to suggest that you might have neglected to restart uWSGI after removing the trailing slash. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Mailman and Postfix Conflicting Information

by Mark Sapiro

On 2/6/26 09:00, dap1--- via Mailman-users wrote: > I've been going in circles between mailman and postfix trying to get things working. My current condition is that either mailman is putting incoming mail in the bit bucket or postfix is not sending incoming mail to mailman. What does your mail.log say? There should be an entry like ... postfix/lmtp ... to=<lllllllllll(a)gmail.com>, relay=127.0.0.1[127.0.0.1]:8024 ... for mail to the list. > According to the postfix forum my mailman configuration is messed up but it was auto generated by the installer. Supposedly these entries should not be in /opt/mailman/mm/var/data/postfix_lmtp or rather transport_maps and/or local_recipient_maps. > > # Aliases which are visible only in the @gmail.com domain. > lllllllllll(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-bounces(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-confirm(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-join(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-leave(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-owner(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-request(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-subscribe(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-unsubscribe(a)gmail.com lmtp:[127.0.0.1]:8024 > > And relay_domains shouldn't have this entry either in /opt/mailman/mm/var/data/postfix_domains in relay_domains: > > gmail.com gmail.com > > Clearly my postfix configuration is messed up but since this was all auto generated I don't know what to do. I think the Postfix people are confused by the fact that your list domain is gmail.com and expect gmail.com mail to be delivered to Google, not Mailman. What you post above seems OK to me for what you are trying to do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases

by Mark Sapiro

On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 > .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe@lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscribe@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no whitespace.ce in the last line and I made a > new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 1/25/21 11:42 PM, David Partain via Mailman-users wrote: > Hi Gordon (and Mark)! > > I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: > > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.mysql', > 'NAME': 'mailman3web', > 'USER': 'mailman3web', > 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', > 'HOST': 'localhost', > 'PORT': '', > 'OPTIONS': { > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > 'charset': 'utf8mb4', > }, > } > } > > and restarted stuff, but I cannot tell that it has changed anything. That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. If this is the case, it would have been retried and produced the same error with each new post, and after you made the above change, it would have been archived and the errors stopped. > Do I need to do something with the database itself (which is somewhat outside my comfort zone...) to make this work? Are you saying you are still seeing these errors? If so, it may be a different error. What is the exact error message? We don't need all the Django stuff, just the part equivalent to > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\xF0\x9F\xA4\xA3\xF0\x9F...' for > column mailman3web.hyperkitty_email.content at row 1") from the OP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Search results for query "sapiro"