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

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 7 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 7 months

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Odhiambo Washington

On Sun, 2 Aug 2020 at 23:56, Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/2/20 12:42 PM, Odhiambo Washington wrote: > >> > >> It is currently linked from the first paragraph at > >> <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. > >> > > > > I followed the steps outlined in the subject document and got mailman3 > > running. > > However, what is missing in that document is the process of setting up a > > webserver for accessing the MM3 UI. > > I have spent two days trying to figure out that aspect and discovered a > few > > things (I could be wrong in what I think): > > > Which document are you talking about? If you mean > < > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… > >, > that talks about the Debian/Upuntu package installation and that package > is quite behind the current releases. > That same document. The Ubuntu package is updated to the latest. > I thought that after mush back and forth with you following > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you > got Mailman 3 up and running, so why would you now be trying to install > the Debian/Ubuntu package? > I was trying to help the other poster :-) > > If you have issues with the > < > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… > > > document, you should contact its author. See > <https://wiki.list.org/x/12812344>. > I just thought that since it was being discussed here (and because you linked it to your document), we could still discuss it here. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 4 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Allan Hansen

Marcus, One of the MM3 bugs is the inability of list moderators to see the list of members of the list they are moderating. This in spite of MM3 having an option to allow moderators to see the list's members. The bug has been reported. My own moderators regularly request their lists and I have to log in to the server directly and use the mailman core API to get the list and then used mailx to send it to them. Yours, Allan On 4/7/21, 11:58 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 4/7/21 1:32 AM, Marcus Granath wrote: > > Sorry, but actually I can not find any "Users dropdown" to select "Non-Members" at any Postorius in my web interface. :-( It's one of the various tabs across the top of the page. What Postorius version is this? Seversal versions back, I think it was called `members` rather than `users`. In current Postorius, the tabs are Info Subscription requests Held messages Users Templates Settings Mass operations Ban List Header filters Delete As I said, `Users` used to be `Members` and `Templates` was added at some point, but that's the general idea. > Maybe, could it be that I am actually not the admin of the mailman3 server, I'm "just" the admin of my mailman-list - so just admin for my mailman-list and not for the mailman server? As Steve said, the list admin should see all those. -- 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/

4 years, 8 months

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Wed, Feb 15, 2023 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 05:22, Odhiambo Washington wrote: > > > > 1. Where is this template that the system used and can I edit it? > > > /opt/mailman/mm/venv/lib/<python_version>/site-packages/mailman/templates/en/list:user:action:subscribe.txt > > You can edit it, but your edits will be overwritten if you upgrade. > I will not touch that. > > 2. Why is it not using the template I created? > > Is the template you placed in > /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > named list:user:action:subscribe.txt and does Mailman have permission to > read it? > Yes. [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/ kictanet.lists.kictanet.or.ke/en/ total 48 drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > Did you try to create a template in Postorius? If you did, that one will > take precedence. > Not at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: customized welcome message

by Nils

Forget the previous message. Thank you very much for your help, Mark. I looked at the configuration files once more, and changing POSTORIUS_TEMPLATE_BASE_URL in mailman-web.py fixed the issue for me. Kind regards On 12/7/23 23:09, Nils wrote: > On 12/7/23 22:40, Mark Sapiro wrote: >> How and to what did you set the URL for the template? What does the >> database query >> >> SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; >> >> show? > http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD > > This value can't work. Now it makes sense that it gets redirected and > the use of localhost also explains why it didn't show in any of the > virtual hosts log files that I was checking until it was redirected. > > However, I didn't set that value. I edited the template at > postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can > just select a template type and then I get one textarea input field > for the content. > The value in the database is set automatically, when I create a > template in postorius (and is also automatically removed when I delete > a template there). I can't edit this value without manually changing > it in the database. > >> This is very old. Current Postorius is 1.3.10. 1.2.4 is from February >> 2019. The Debian/Ubuntu packages are out of date. We recommend >> installing via the doc at >> https://docs.mailman3.org/en/latest/install/virtualenv.html > > The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) > very soon. The Debian/Ubuntu packages sure have their downsides but > once they work, they update automatically and require very little > maintenance.

2 years

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 3:13 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > > > I went with the apache/uswgi configuration. The site is up and running, > but if I click Postorius, it gets redirected to > https://mysite.com/postorius/lists and I get not found error message. > > > > The same goes for Lists and Archives. > > Compare your urls.py to > < > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. > > Some of the `path` settings are probably not in the same order as in > that file. The > > ``` > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > ``` > settings should come after the > ``` > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > ``` > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones > or you can add > ``` > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ``` > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the manipulation of any urls.py at all - it's not even mentioned at any point. So obviously the issue is caused by something else and I suspect something within Apache needs to be re-evaluated in the guide. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021 at 11:00, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users > wrote: >> >> But... here is a thing that I can not understand: If the source >> (the .po >> file) is from november 7th, it doesn't matter how many times you >> recompile it: the result will be the same. > > Correct, but the point is if you download the latest > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 > file > in the distribution, you will find they are identical, so it it > appears > that the weblate translation hasn't changed since that time. > > If there are issues in this mailman.po, they exist in weblate too and > need to be fixed there. > > Also note that the translations on weblate only affect strings in the > core code. The Mailman core templates are not currently translated in > weblate and there are currently no Spanish language templates. One > would > need to create Spanish translations of all the templates in > <<https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en>> > and submit a merge request to add them to a mailman/templates/es/ > directory. You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core. Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them. For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… The english .po file is considered as reference in Weblate and used for source string. Abhilash

4 years, 10 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hi Mark, On Sat, Jul 09, 2022 at 12:05:32PM -0700, Mark Sapiro wrote: > If the original post was the message delivered to > users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or > another recognizer parsed those addresses from the message body. For now I've configured a copy of all mails to -bounces addresses, so if/when it happens again I can inspect the actual email that triggered it. In case anyone else ever wants to do that, this is one way to do it on Exim: # This goes in your "routers" section. # Add a router, before every other router that you would want to # tap messages for. traffic_tap: unseen no_expn no_verify transport = local_copy_outgoing driver = accept # "mm_domains" is a list of domain names for mailman, e.g. # "lists.example.com"; it's set as part of the usual Mailman install on # Debian. domains = +mm_domains # Only do this for bounce addresses. So between this and the above, this # router will only happen for *-bounces*@your-mailman. local_part_suffix = -bounces : -bounces+* # This goes in your "transports" section. # Add a transport for taking a local copy. Mail to Mailman is "outgoing" as it # is delivered by LMTP over a socket. But the name is not important. local_copy_outgoing: driver = appendfile # Simply store it all in a maildir. If you're expecting a lot of # messages then you'll want a directory structure by date and/or # recipient or something. directory = /var/mail/archive/.outgoing/ delivery_date_add envelope_to_add return_path_add # If not on Debian then your exim probably runs as a different user/.group. group = Debian-exim user = Debian-exim mode = 0660 maildir_format = true create_directory = true Cheers, Andy

3 years, 5 months

[MM3-users] Re: Auth question

by Simon Hanna

On 03/31/2017 08:10 AM, David Krantz wrote: > On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> We're really working on getting a consistent, workable installation >> story and even getting some packaged solutions. I know we're not yet >> there, but we're here to help when people run into problems. > The site now works, but not the / url for the site. I get this error > in the mailman-web.log (with a very long stacktrace before it) > > NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. > 'hyperkitty.views.index.index' is not a valid view function or pattern > name. > > I think that would correspond to this line in urls.py > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), Yes, that's the culprit. Replace it with the following: url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), You can also update whatever guide you were using... > but this corresponds exactly to what the example config says and I > know of no other name for hyperkitty. Probably it is dependent upon > understanding the url dispatching in Django but that takes some time > to read up on. The interesting thing is that /archives works so it is > just this redirect that has problems. I can probably get apache to do > the redirect instead but that is not the most elegant solution. > > Then I of course have things to do on getting social logins to work. I > currently get "DoesNotExist: SocialApp matching query does not exist." > if trying to connect an account to google (which I started with). Not > a showstopper as passwords do work. Did you follow django-allauth's guide on setting them up?

8 years, 8 months

Search results for query "sapiro"