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

[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, 8 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

5 years

[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, 3 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, 6 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, 1 month

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 3:33 PM, Allan Hansen wrote: > > Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. I think you misunderstand what Mailman Core currently is. I think Mailman Core's concept of User is exactly what you are talking about when you ask for a "true account-based system". The problem is that Mailman Core was intentionally designed without any web UI and a RESTful API for separate web based UIs or whatever to use to communicate with it. Then the people who developed the web based management UI (Postorius) and archive UI (HyperKitty) chose to develop those within a Django framework and Django has its own concept of User separate from Mailman Core and that is where the disconnect occurs. It's not that Mailman Core lacks what you want. It's that Django doesn't use it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Mailman3 don't work if aliases are enabled

by Mark Sapiro

On 10/9/20 3:37 PM, Massimo Zappalà wrote: > > If I try to uncomment the last two rows in main.cf > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > The aliases and email messeges works fine but the mailman3's mailinglist don't work. > > How can I solve this? I'm not certain about this. The Postfix log entries for the failed delivery to Mailman may help, but I think you deed to configure an alias domain or domains for your list domain(s). The alias domain is not a real domain and is not in DNS. it is any unused domain name and will be known only to Postfix. I typically use x.example.com where example.com is the real list domain. You can set the alias domain for the real domain in the domains view in Postorius. Then you need to add `hash:/var/lib/mailman3/data/postfix_vmap` to your main.cf virtual_alias_maps setting and run Mailman's `mailman aliases` command to generate the proper /var/lib/mailman3/data/postfix_* files. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. You may also need to set relay_domains = hash:/var/lib/mailman3/data/postfix_domains -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Set domain inactive / archive import from other domain.

by Mark Sapiro

On 09/15/2018 07:15 AM, Johannes Winter wrote: > > we've migrated a list from another domain and would like to keep the > archives. Hyperkitty doesn't recognize the emails in the mbox archive > during import due to the other domain name. I don't understand the problem. I just ran a test where I imported a mbox containing 3 messages which were not even list posts and in which I had changed all the domain names to 'example.com'. I.e., in the mbox I imported, the headers containing domain names looked like From root(a)example.com Sun Aug 26 09:12:06 2018 Return-Path: <root(a)example.com> Delivered-To: root(a)example.com Received: by example.com (Postfix, from userid 0) From: Anacron <root(a)example.com> To: root(a)example.com Message-Id: <20180826161158.F154D34010C(a)example.com> X-msapiro-MailScanner-From: root(a)example.com and the 3 messages were all added to the archive. Why do you think the domain name is an issue? Perhaps the issue is there is already one or more messages in the archive and the messages you are importing are older. If you don't specify --since to hyperkitty_import it won't import messages older than the newest message in the existing archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: non-member moderation: list default vs default processing

by Mark Sapiro

On 5/21/21 3:58 PM, dancab(a)caltech.edu wrote: > > Each time this problem has come up I've had to change the moderation setting from "List Default" to "Default Processing". > But I've also noticed that some non-members were imported and already have "Default Processing" configured. > > Can you help me understand what determines this setting in Mailman3? > > It seems this would be something addressed via the mailman import21 option I've been using to import the lists. It depends in part on the version of Mailman core as `mailman import21` has had some changes, but here's how it should work. Regexps in MM 2.1 *_these_nonmembers are imported into the corresponding MM 3 *_these_nonmembers. Addresses in MM 2.1 *_these_nonmembers are imported into MM 3 as non-members with their moderation_action set to `defer`, `hold`, 'reject` or `discard` according to which *_these_nonmembers they came from. `accept` maps to `defer` and the others to the same. Prior to Mailman 3.3.0, `accept` mapped to `accept` but `defer` is better. This can get very convoluted if the same address is both a member and in *_these_nonmembers, but in both MM 2.1 and MM 3, the member takes precedence. Is this not what you are seeing? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: How to store additional information about lists?

by Mark Sapiro

On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > There won't be a membership adapter in Systers Mailman if there isn't > one in GNU Mailman, because they used the stock user database and > added fields to the User record to implement their membership > extensions. > > Membership adapter is a Mailman 2 feature that allowed use of an > external membership database (such as a corporate LDAP system). I > thought it was ported to Mailman 3 but maybe not. Actually, it's not quite that simple. Mailman 2.1 defines a MemberAdaptor class, the methods of which are used for everything to do with list members and memberships and are all documented in the base definition in Mailman/MemberAdaptor.py and all raise `NotImplementedError`. Also included in Mailman 2.1 is Mailman/OldStyleMemberships.py which subclasses MemberAdaptor and actually implements the methods, storing the data in the same config.pck pickle as the list settings. Various people have implemented various other MemberAdaptor classes for various purposes. https://bugs.launchpad.net/mailman/+bug/558106 contains several revisions of one using LDAP for the (read only) membership data. The Mailman 3 analog of this is the IMember interface defined in mailman/interfaces/member.py and implemented in mailman/model/member.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Search results for query "sapiro"