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

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Since I made all the mailman3 enviroment wide server open (not using > venv) I already executed the migration doing a > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > Being mailman3 the user who runs all of mailman3 related stuff > > I had problems doing the migrate part, showing an error of lacking > perms. I solved it running the migration under root (I know it could be > trouble after, but...) It would be much better to identify the problem files/directories and adjust their ownership. It is possible that running stuff as root in the past left things owned by root causing the issue. > > After that the compress part showed errors... but the postorius web > maintenance was working well except for the CSRF error verification. I > will trace the compress errors and will try to find the problem later. Do you have `COMPRESS_ENABLED = True` in your settings? If that's not the issue, it may be in the settings for COMPRESS_PRECOMPILERS -- 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: Debian Package Install - Ownership and Permissions

by Mark Sapiro

On 4/7/23 14:58, Dave Hall via Mailman-users wrote: > On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 4/7/23 13:43, Odhiambo Washington wrote: >>> On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < >>> as2020+github(a)fam.tuwien.ac.at> wrote: >>>> >>>> I am running MM2 und 3 in parallel without problems, I do have a >>>> special MTA setup though (Sendmail). Can't speak for Postfix etc.. >>>> >>> >>> Your setup can handle list1(a)domain1.name via MM2 and MM3, >> simultaneously, >>> right? :-) >> >> It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` >> simultaneously on the same server, but what is the MTA going to do with >> incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to >> both MM2 and MM3, but I don't see any practical use case for this. >> >> I run Exim4 on my servers so I can comment from this perspective. Exim > had a concept of 'routers' which are stacked and processed in order of > appearance. There is a router for MM2 and one for MM3 that pick off > incoming mail based on whether the email address matches a list name. WIth > this setup, you could have the same list name in both MM2 and MM3, but it > would go to whichever router appears first and the second one would never > see it. So I have the MM3 router first, and as I migrate my lists from > MM3 the email for those lists no longer gets to MM2. And mail.python.org which currently has 189 Mailman 3 lists and 223 Mailman 2.1 lists does something very similar in it's Postfix configuration and also prefers Mailman 3. However, maybe I misunderstood Odiambo's question about simultaneous support for a Mailman 2.1 and Mailman 3 list of the same name. We could certainly have that on mail.python.org, and even have both MM 2.1 and MM 3 web UIs for those lists, but as soon as the MM 3 list is created during migration, mail is only delivered to the MM 3 list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Starting from scratch

by Mark Sapiro

On 04/09/2018 10:01 AM, Benjamin Ragheb wrote: > > The two alternatives I am weighing right now are: > > 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. > > 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) > > Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. > > Which is the least crazy option? If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install. There is a 3rd option. See <https://packages.debian.org/stretch-backports/mailman3-full> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Rerun emails in the queue/bad

by Mark Sapiro

On 11/20/18 8:20 AM, Kaleb White wrote: > How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks. There should be error messages in the 'mailman' log for each preserved file. These would be like 'Skipping and preserving unparseable message: ....psv' 'Unpickling .bak exception: <error msg> Preserving file: ....psv' '.bak file max count, preserving file: ....psv' The first of these indicates an error in retrieving the message from it's original queue. The others have to do with how message loss is avoided. When a .pck file in a queue is processed, it is read and renamed to a .bak. Then if processing is interrupted by a crash, upon restart the .bak file will be processed. The second error above indicates a problem in unpickling the .bak and the third says the same .bak has already been tried too many times. You may be able to examine the files by pointing 'mailman qfile' at them. If that fails, either 'cat' or 'strings' may produce something useful. If they appear to be good, you can reprocess them by renaming to .pck, moving to queue/shunt and running 'mailman unshunt'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Mark Sapiro

On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > /usr/local/lib/python3.7/site-packages/mailman # ls templates/es > domain:admin:notice:new-list.txt list:member:regular:header.txt > help.txt list:user:action:invite.txt > list:admin:action:post.txt list:user:action:subscribe.txt > list:admin:action:subscribe.txt list:user:action:unsubscribe.txt > list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt > list:admin:notice:disable.txt list:user:notice:hold.txt > list:admin:notice:removal.txt list:user:notice:no-more-today.txt > list:admin:notice:subscribe.txt list:user:notice:post.txt > list:admin:notice:unrecognized.txt list:user:notice:probe.txt > list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt > list:member:digest:header.txt list:user:notice:rejected.txt > list:member:digest:masthead.txt list:user:notice:warning.txt > list:member:generic:footer.txt list:user:notice:welcome.txt > > But mailman isn't aware of them (I restarted the server). May I have to > execute some process as "compilemessages" to mailman be capable to use > them? Now mailman is using the "en" templates for sure. Does Mailman have permission to search the templates/es directory and read the templates? Are there overriding templates in Mailman's var/templates/ directory? Are you sure your tests access the templates in a Spanish language context? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mailman 3 Social Auth Configuration

by Mark Sapiro

On 10/12/2016 08:09 PM, emonical(a)misfitlabs.org wrote: > > I am a new Mailman 3 user and have just gotten an environment configured using the Mailman bundler. The setup is almost complete, but, there's still Persona authorization. Mailman bundler installs the latest releases from PyPI, but those are behind the latest development branches. > I was reading the your setup here from (https://wiki.list.org/DOC/Mailman%203%20installation%20experience) and was wondering if someone might have some insight as to how to remove the Persona log in to keep it locked down entirely to localized user registration. With the latest gitlab branches, you will have Django Allauth. This includes login by verified email and password, and if you choose to not use any of the supported Oauth2 providers, that will be the only method. To do this without waiting for the Mailman 3.1 release and an updated bundler, you will need to install the latest master branches from <https://gitlab.com/groups/mailman> for Mailman, Postorius, HyperKitty, MailmanClient, django-mailman3 and HyperKitty - Mailman plugin. The wiki article <https://gitlab.com/groups/mailman> will give some insight into the process, but it isn't fully current. I will be updating it. Meanwhile, ask your specific questions here and we will try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 6 months

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

by Mark Sapiro

On 6/8/21 10:50 PM, Kimmo L wrote: > Okay, i will try to explain the overall situation as far as I can understand: > Its a CentOS 7 host without any virtualenv. Mailman_suite_project git repo has been cloned to the host and after that some packages have been installed with the help of pip: > > # pip2 install django==1.10 postorius==1.1.0 hyperkitty whoosh xapian-haystack > # pip3.5 install mailman mailman-hyperkitty For current Mailman the minimum Python version is 3.6 and all components are Python 3. Nothing is Python 2. You should be installing the latest versions of everything. Do not install Django explicitly with pip. It will be installed as a dependency of Postorius and Hyperkitty. If you are going to use Xapian, you don't need whoosh. Also, you need to install Xapian itself, either from source or with yum if there is a yum package. > And now Im in trouble, what would be the right steps from here. I'm not that competent to use pip, so im confused - should i install python36 packages and try to upgrade pip2 and pip3 mailman packages after that or should i install these pip2 packages with pip3 and remove from pip2 list? There are no pip2 packages. Everything is Python >=3.6. -- 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: [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by Mark Sapiro

On 2/28/21 10:17 AM, blackout69 wrote: > Hello everybody,I received this error message and from that moment the > maiilan3 has stopped working.I restarted the following services mailman3 > and mailman3-web and everything started working fine.Can you tell me > what is the problem my django server has encountered? It looks to me like a race condition of some kind or possibly an incompletely deleted thread. Have you deleted any threads? I'm curious as to how you happen to be going to <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> as opposed to <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. I know that ULS and similar ones are in HyperKitty's urls.py, but I don't see them exposed on any pages. Anyway, when you say "from that moment the maiilan3 has stopped working." (sic) exactly what stopped working. Did core stop delivering messages? Did Postorius stop working. If so, this all may be related to some underlying database issue or something like that that was fixed by the restarts. I don't see how this HyperKitty error could affect Postorius or Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/5/22 08:56, Allan Hansen wrote: > Thank you, Mark, as always. > > We upgraded to the latest versions: > > Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] > > Also, I don't have any umbrella lists. I need more information about this. As far as I know, this can only happen with messages that are cross posted to multiple lists and held for moderator approval on more than one list. This should have been fixed in Mailman 3.3.6 by <https://gitlab.com/mailman/mailman/-/merge_requests/932>. This should never happen with a post that is delivered to members without being held. Also, I think when this happens to a delivered post, the post in the archive will also have the content lost message. I would like to get as much information as possible about the circumstances when this happens. In particular, was the post held for moderation, was it posted to multiple lists, for how many lists was the content lost. Also, it may help to see the full raw message with the content lost notice. (If there are privacy concerns you can send these to me off list) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Replace "visit your dashboard" with URL link, like in Mailman 2.

by Mark Sapiro

On 5/8/23 09:52, Mark London via Mailman-users wrote: > Has anybody attempted to change the format of the emails that are sent > to the owner of a mailing list, to include a URL, instead of stating > "visit your dashboard"? The former is the behavior of Mailman 2. Many users, e.g. Jens Günther whose replied to this thread, have made custom templates to do this. > Is there any reason why this can't be done? If nobody has tried to do > so yet, I'll give it a try myself, as I'm familiar with django. Thanks. See https://gitlab.com/mailman/mailman/-/issues/901 and https://gitlab.com/mailman/mailman/-/issues/1055 Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for some documentation of templates, but note that you don't need to set URI's via REST, You can place list specific templates in Mailman's var/templates/lists/<list-id>/<lc>/ directory, domain specific templates in var/templates/domains/<domain-name>/<lc>/ and sitewide templates in var/templates/domain/site/<lc>/ or you can create list and/or domain specific templates via Postorius but see https://gitlab.com/mailman/postorius/-/issues/366 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Search results for query "sapiro"