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

[MM3-users] Re: Domain in welcome message

by Mark Sapiro

On 02/19/2017 02:05 PM, Maadix wrote: > Hi, > I'm having problems with customizing welcome message > > It's working fine for > var/templates/site/en/welcome.txt > > but not for domains or lists , so maybe I'm doing something worng > > I'm using a subdomain as mail_host which is different from the URL Host. > > I've been trying all these combination, with no success: > > var/templates/domains/sub.example.com/en/welcome.txt > var/templates/lists/listname.sub.example.com/en/welcome.txt > var/templates/lists/listname(a)sub.example.com/en/welcome.txt > > I'm running mailman-bundler version 3.0.0 Templating has changed for MM 3.1, and I don't have a 3.0 platform available for testing, but as far as I can recall, the paths var/templates/domains/sub.example.com/en/welcome.txt and var/templates/lists/listname.sub.example.com/en/welcome.txt should be valid for domain and list specific templates and the precedence should be (high to low) list, domain, site, default. I don't know why it isn't working for you. -- 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: leaving Sympa for MM3

by Mark Sapiro

On 2/20/20 3:12 PM, rance.hall(a)esu10.org wrote: > > Now for the question/hard part. Migrating list archives. > > In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. > > I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this? It shouldn't be hard. HyperKitty has a function to import archive mbox files. It would be a simple matter to use Python's mailbox module to convert your archive. Something like import mailbox md = mailbox.Maildir('path/to/maildir/directory', create=False) mb = mailbox.mbox('path/to/mbox', create=True) for msg in md: mb.add(msg) mb.close() md.close() Then just run hyperkitty_import to import the mbox. run something like django-admin hyperkitty_import --help for details. Note that if there are already archived messages you need to specify --since to import older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: New releases

by Mark Sapiro

On 9/11/20 8:19 PM, brylon(a)oit.rutgers.edu wrote: > I already have ruby-sass installed and the compress command used to work as expected prior to my upgrading to the latest core, postorius, hyperkitty versions using pip in my venv. > > Does It matter at all when performing the Django-admin commands whether I've activated the venv or not? I think I've tried running them both activated and deactivated to no avail, but any other suggestions? I don't think that's the issue here, but the venv should be active when you run the Django-admin commands. Looking more closely at the error, I see it says ``` File "/opt/mailman/mm/venv/lib/python3.6/site-packages/compressor/base.py", line 282, in precompile mod = import_module(mod_name) ... ModuleNotFoundError: No module named 'sass -t compressed {infile} {outfile}' ``` Thus it appears that compressor is trying to import 'sass -t compressed {infile} {outfile}' as a module instead of executing it as a command. What version of compressor is this? It is working for me on 4 sites with django_compressor-2.4, django_compressor-2.3 and django_compressor-2.2. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: spanish localization

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 2:55 PM, Jens Günther wrote: > > When I want to get to Mailman Starting Page now I need to Enter the > following URL: https://mailman.xyz.de/mailman3/ to be directly > redirected as expected to > https://mailman.xyz.de/mailman3/postorius/lists/ -> works. > > Problem: When leave out the slash at the end and I ONLY enter the > following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly > redirected to a page, taht does not exist: > https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Huh? that is the same URL as the one above that you say works. Do you mean https://mailman.xyz.de/mailman/postorius/lists without the slash or what. > Where can I change this misbehaviour? In Apache-conf everything seems as > it'S in the docs, for the vHost I do not have any other custom settings. What is the exact content of your RedirectMatch or ReweriteRule or whatebver you are using? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/7/21 11:54 PM, Kimmo L wrote: > Hi! > > Thanks for the support and help! > But so far i havent been successful with upgrading my postorius, hyperkitty and django pip packages from python2.7 to python3.5 or higher. As i understand, it was installed 2018 and has not been updated (because it has been working without any problem). Perhaps we can help with that. How are these installed now? What issues are you having when trying to upgrade. > Maybe the easiest way is to create a new deployment and somehow transfer data from old server to new one ? It's up to you which way to go. If you create a new deployment, I recommend following https://docs.mailman3.org/en/latest/install/virtualenv.html. You might also consider Xapian as the search engine - see https://docs.mailman3.org/en/latest/config-web.html#enable-full-text-search… and https://github.com/notanumber/xapian-haystack/tree/master Transferring the data is easy as long as the database is compatible - just dump and load, plus copy some files from Mailman's var/ directory. -- 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: multiple sites on a mailman3 server question

by Mark Sapiro

On 12/29/21 8:48 AM, William Oliver wrote: > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. If you are following https://docs.mailman3.org/en/latest/install/virtualenv.html you have ``` location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ``` in your nginx config and everything goes to uwsgi. What you want is to put those proxy directives in only the mailman locations as at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and then configure your document root so other locations are served from there. -- 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: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`

by Mark Sapiro

On 12/22/23 10:34 AM, Wikinaut wrote: > Wheras my older lists handled these format apparently correctly, I now cannot add any more > > "Givenname Familyname" <mailaddress> ; or > Givenname Familyname <mailaddress> > > In any of these cases, only the part <mailaddress> is added. > > Is this strange behaviour know? > What can be done to have the correct function back to working again? There haven't been any changes to this. The issue is almost certainly that when subscribing "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> if there is no Mailman user/address for <mailaddress>, one will be created with display name `Givenname Familyname`, but if there is an existing user/address for <mailaddress>, its display name won't be changed. In this case, you can find the user at https://www.example.com/mailman3/users, click the user's Manage button and update its display name. -- 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: Legit login attempts yield, "An error occurred while processing your request."

by Mark Sapiro

On 8/14/24 3:18 PM, Greg Newby wrote: > > My primary question is: *How can I find out what's causing this*? > > I've looked in all the MM and web logfiles, by "tail -f" while generating > the error, and nothing is logged there. Apache logs shows something like > this: > > x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ > HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" > "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log. > I've come across this error while trying to do authentication-related > activities that worked before the reboot: Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0. -- 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

Search results for query "sapiro"