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

[MM3-users] Add old email address

by Stephen J. Turnbull

Quanah Gibson-Mount writes: > We've recently migrated our project's email lists from mailman2 to > mailman3. Given the project has been around for a few decades, many people > have used different email addresesses over the years, some of which they no > longer have access to. However, it would be useful to still be able to > associate those emails with a given account. Is there a way that I can do > this as an administrator of the mailman3 system? You can certainly add extra addresses to a Mailman 3 user (I don't know offhand whether/how an admin can do it through Postorius, but the core database certainly has that facility and the REST API allows it). However, this doesn't have the same semantics as in Mailman 2 because Mailman 2 doesn't have users at all. So as an admin how do you know which addresses correspond to particular users? More generally, what do you mean by "associate with an account", and why do you want to do it? Normally I would not ask the latter question, it's your business why you want to do it. But here I'm trying to get at what semantics you want. If I were going to do this for the kind of purposes I can imagine, it would be a matter of informing the users that this feature is available, and I'd ask the users to do it if they care. It seems you have some project goal in mind though. Steve

5 years, 1 month

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by bob B

Thanks, so if do not do a cronjob how often would mailman send out digests? is it daily or ????? it sounds like it is daily, But is that setup in the Docker Environment, it appears not to be? if not how do I set that up in the Docker environment? I thought docker mailman cron jobs run from the "docker-web" container in the file "/opt/mailman-web/uwsgi.ini" but the "docker-web" container can not run the command "mailman" command Do I do this in cron in the "docker-core" container or do I run it from cron on my docker host as an entry like 0 1 *** 'docker exec -it mailman-core mailman digests --list list(a)example.com --periodic'

3 years

[MM3-users] Re: Mailman 3 on Fedora - Core only ?

by Mark Sapiro

On 6/13/20 2:17 AM, Lars Bjørndal wrote: > I'm about to set up a new list, and want to try out Mailman3. > > The only component available in Fedora, is the Mailman core package. I find that strange as <https://lists.fedoraproject.org/> is Mailman 3 and the core developer who did most of the HyperKitty development works or did work for Fedora. > With the /usr/libexec/mailman3/mailman command, I was able to create a > list, and add a member throug the sub commands create and members. > > How can I read out the list configuration from here, and change > settings? Do I then need to install/use other components, or is there > other possibilities, e.g. using the shell command? You can do anything through `mailman shell`, but it can be cumbersome. You can also do most things via the REST API <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>, but that too is cumbersome if doing it, e.g., with `curl`. > If I get a message that needs moderation, can I do the decision from cli, > or how do I do that? You should be able to do it via a reply to LIST-confirm+<token>@example.com, but this currently doesn't work. See <https://gitlab.com/mailman/mailman/-/issues/169>. To do it in `mailman shell` is something like: $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.app.moderator import handle_message >>> from mailman.interfaces.action import Action >>> action = Action.discard # to discard >>> action = Action.reject # to reject >>> action = Action.accept # to accept immediately >>> action = Action.defer # to continue with subsequent tests >>> rq = IListRequests(m) >>> rq.held_requests <generator object ListRequests.held_requests at 0x7f5431dda048> >>> list(rq.held_requests) [] >>> # when you have requests this is a list of (id, type) tuples >>> # type is 1 for message, 2 for subscription and 3 for unsubscription >>> id = 'integer request id from above' >>> handle_message(m, id, action, comment='reason if rejecting') This is obviously not practical, but you could make a script to accept the token that you know and an action and maybe a comment to do the actual handling. -- 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: Add old email address

by Quanah Gibson-Mount

--On Friday, March 13, 2020 4:18 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > You can certainly add extra addresses to a Mailman 3 user (I don't > know offhand whether/how an admin can do it through Postorius, but the > core database certainly has that facility and the REST API allows it). I was able to resolve this via the Django admin interface. > However, this doesn't have the same semantics as in Mailman 2 because > Mailman 2 doesn't have users at all. So as an admin how do you know > which addresses correspond to particular users? More generally, what > do you mean by "associate with an account", and why do you want to do > it? > > Normally I would not ask the latter question, it's your business why > you want to do it. But here I'm trying to get at what semantics you > want. If I were going to do this for the kind of purposes I can > imagine, it would be a matter of informing the users that this feature > is available, and I'd ask the users to do it if they care. It seems > you have some project goal in mind though. Because I've been a member of the project for close to 20 years, and the email addresses I've had over that time have changed in relation to the jobs I've had. Same deal for other long time members of the project. By adding addresses I no longer have to my account and marking them verified, I can easily associate nearly 20 years of postings that I've made with myself when I look at the archives. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 1 month

[MM3-users] Re: Hyperkitty using wrong email address in archive view

by Mark Sapiro

On 5/16/23 01:42, peter(a)chubb.wattle.id.au wrote: > Hi Folks, > I notice that for people with multiple email addresses, the email > address that appears as the 'FROM' address in the hyperkitty > archive is not the primary address, nor is it the address that the > email actually came from, but the address that was created first. > (Hyperkitty version 1.3.7) Where exactly do you see this address? Normally, if the From: header of the mail contains a display name, it is that name which is displayed as the author of the email. The display is only an address if the From: header of the mail had no display name or if it had a display name which was an email address as in From: user(a)example.com <user(a)example.com> > When I click on that from address in the archive view, I see all > the email addresses for the user -- these do not match up with the > ones in the django admin screen from .../admin/account/emailaddress/ Because they are not the Django user's email addresses, they are the Mailman user's email addresses. > When I see 'User profile for Fred Frog' > it shows obsolete addresses (not subscribed, not in the Django > profile for the user). Again these are the Mailman user's addresses. The Mailman users are listed at the Users tab on the top Postorius nav bar. > How can I as administrator get rid of bogus addresses? Or do I > have to ask each user to do this? The user can do it at https://example.com/accounts/email/ but the admin can't do it from Postorius. A site admin can do it via REST or `mailman shell`. > and how can I ensure that the email address displayed in the > archive is the primary address, not some address that no longer > works? Again, where do you see this? You may want to download that thread and see what that shows as the From: header of the email. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Dealing with confirmation requests for unsubscribes

by Mark Sapiro

On 11/18/20 7:41 AM, Brian Carpenter wrote: > Hello List, > > I ran into the following issue for some mailman 3 lists that I am hosting: > > https://gitlab.com/mailman/mailman/-/issues/768 > > Since there is no way for a list owner to deal with a moderation request > for an unsubscription task, I assume I need to do something via the > command line. This is where I need some help with. How do I deal with > these moderation requests that are unable to be reviewed in an admin gui > (Postorius/Affinity)? mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the test.msapiro.net mailing list This >>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', token_owner=TokenOwner.moderator)) will return something like [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', 'list_id': 'list.example.com', 'email': 'user(a)example.com', 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': 'moderator'})] What you want is the token, in this case 'a8df55f557b5718505280d2613937e25a3109252' Then do >>> ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') which will return (None, <TokenOwner.no_one: 0>, None) and finally: >>> commit() > I do recommend removing such choices for Postorius for Member policy. I > will be doing this for Affinity until issue 768 is resolved. The correct thing to do is fix <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly will do that rather than remove the moderate and confirm then moderate unsubscription policies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Configuring ARC with multiple domains in Mailman3

by Stephen J. Turnbull

Lance A. Brown writes: > I'm working on setting up MailMan 3 on an Ubuntu 24.04 LTS server. > I've got everything running and working with docker-mailman. Now > I'm looking at configuring ARC and am a bit lost. > > How is ARC configured in a mailman3 with multiple domains? It shouldn't be. It should be configured in your MTAs. Mailman can't do SPF, and it can't make the decision to distribute or not based on ARC validation without a preexisting ARC-Authentication-Results field from your host. Neither of those is fatal, but implementing in the MTA is preferable. ARC was originally added as a proof of concept. But I have to admit setting it up in Mailman is easier than doing it in the MTA, it's not as easy as throwing a switch in Postfix or Amavis (although it should be!) > Do I set it up to use the hostname of the server Mailman is running > on? That's arbitrary. Here's the theory of ARC: 1. I saw it come in. ARC (all the way back) was valid as of last hop. Here are current SPF and DKIM results. Trust me! 2. It wasn't Evil when it came in and I didn't do anything Evil to it. Trust me! 3. Here's my signatures. Validate them! So the question is, "why do other systems trust you, and what identity do you want your trustworthiness to bind to?" Could be an organizational reputation you already have, in which case you might want to use that domain. One of your Mailman domains (eg, the one with the widest distribution) might serve as a representative. Or none of the above has a reputation to the general public, and you need to build it from scratch. In that case, the host name is as good a place as any to start I guess. Note, I have no experience inside the big email providers who are generally the important consumers of ARC, so you should take the advice above as a place to start thinking, rather than authoritative. Unfortunately they tend to be very close-mouthed about how they evaluate messages or sites, and their published advice amounts to "follow best practices such as DKIM signing and ARC". Note that as far as I know Mailman's ARC implementation doesn't do anything except implement validation and signing. Some other part of the process needs to decide what to do about a broken ARC chain or other authentication failures, but I don't see a way to do it in current Mailman -- the decision to reject, hold, or distribute takes place before ARC handlers are invoked as far as I can tell.

2 months, 2 weeks

[MM3-users] Re: Problem with languages

by Jens Günther

Hey, thanks for the quick reply. Am 19.03.21 um 15:44 schrieb Andreas Barth: > * Jens Günther (jens.guenther(a)posteo.de) [210319 15:29]: >> But for some reason I do have a mixed setup in languages now. Some >> strings are in English, some are in German. The settings I changed >> are: > > which package version do you use? I do use the ones from buster, yes, so it's running mailman3-version 3.2.1 > > Actually I would recommend using the packages from bullseye for > mailman3. This should work with e.g. some pinning. You think it's ok to install from testing? I have already the bullseye-package with a lower preference then the stable ones, so I could do so, advertises version 3.3.3 there ... but always try to stick with stable packages :-) never know. With the backports I often do go along, but never know what testing does, when you start with a mixed system... If so, do you know how to do to install all needed dependencies correctly!? 'apt install mailman3-full -t bullseye' shouldn't be all of it, no!? > > (I'm thinking if we should try to get mailman3 into stable-backports, > because that might be actually useful.) > > Also, translations had been the reason for some discussions lately, so > this is still some work-in-progress. (Also on the git version I'm > using, there are more texts in English than I'd wish for.) What I hear is that this is a common issue and I probably should get along with it for now!? > > Andi > _______________________________________________ > 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, 1 month

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/6/25 14:40, via Mailman-users wrote: >> Is your login a member of the list? > > It's supposed to be – when I click „Manage subscription” in the very same thread, it reveals that I'm subscribed. This is why I can't subscribe again. Yet I still can't post from HyperKitty, however I can by e-mail. > > However, when I checked the member list, I also found my address as a „nonmember” (besides being listed as „member” too). I removed myself as „nonmember”, but I still can't post to the list from HyperKitty. What response do you get when you click `reply` on a message? and what when you click `Start a new thread`. Do you get an error immediately or do you get a composition dialog and only get an error when you click `Send`. What do the errors look like? What do you see in Django's logs when you do this? What HyperKitty version is this and is it installed from PyPI or is it a downstream package? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 3 days

[MM3-users] Re: Issues with @gmail.com addresses

by Stephen J. Turnbull

Peter Münster writes: > Probably related: Even without any setting in "Alter Messages", > messages with attachment from Gmail are altered, so that DKIM > signatures are invalidated: I think they do this on purpose. Gmail is producing invalid MIME[1]. As you're supposed to do on the internet, Python's email module is accepting it because even though it's technically invalid, it's clear what the intended semantics are. Then as you're supposed to do on the internet, Python produces valid MIME when it reconstructs the message. I don't know about those other whitespace issues; probably those could be preserved. > Just an idea: you could add to the message object a field like > "orig-body", that keeps the unmodified body. You could, but that would mean tripling or quadrupling the size of many message objects (I've seen PNGs encoded in quoted-pair!) And you'd have to do it for all message objects in the Mailman queues, because Mailman does this conversion as soon as the message arrives, before it knows enough about the message to know if it's really necessary. Then you'd need some kind of API for callers to tell the Email package when to do this, and then when to use it instead of the parsed version in constructing the outgoing message. I think it's much simpler to just do what Google wants you to do, and mutilate the From field of Gmail authors. FWIW, if I were going to try to deal with this, I would probably do it differently, adding these peculiarities to the list of things Email considers to be "message defects", and then have a "reproduce defects" flag for the reassemble functions. That would also fix some other things that people sometimes dislike, like Mailman choosing to fold headers in a different place from the orginal. Footnotes: [1] I'm not going to read the RFCs now to make sure, but the thing is that the newlines on either side of the divider are parsed as part of the divider, not as line separators. So if you have two dividers in a row, there needs to be two newlines (at least) between them, one for the end of the first divider, one for the beginning of the second.

1 year, 7 months

[MM3-users] Re: Customise Postorius templates?

by Abhilash Raj

> On Feb 1, 2022, at 11:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/1/22 09:47, Duane Raymond wrote: >> Hi, >> I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying >> venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html >> to >> var/templates/lists/summary.html >> As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. > > > The var/templates directory has a specific structure and is only for custom list specific, domain specific and sitewide templates used for notifications from Mailman core. It has nothing to do with Postorius or HyperKitty templates. > > >> Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!) > > > I don't know about a `best` way, but the way I do this is to keep all local mods as patches to the base and apply those patches as part of the upgrade process. The best way to do this would be utilize Django’s template loader. See here[1] for the documentation on how you can do this. You want to put the path where you are putting the templates under `DIRS` option of the `TEMPLATES` section. Do make sure that you are keeping the directory structure correct so that Django can discover them. Like, Hyperkitty’s base.html should be in `/custom/path/hyperkitty/base.html`, where `/custom/path` is what you’ve setup in DIRS setting above. One important point to note here is that we can’t promise to not break your custom template in future, because the values passed in the template’s context is not a public or stable API. So, it is technically possible for us to remove/change the variables that are being passed. In practice, I can’t remember when was the last time I removed a variable, so this would work better than patching since you are doing “radical customisation”, which Mark isn’t. [1]: https://docs.djangoproject.com/en/4.0/howto/overriding-templates/ -- thanks, Abhilash Raj (maxking)

3 years, 2 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Seth Seeger

Bob, I am running with Docker, and here is my cron line: 0 5 * * * /usr/bin/docker exec -u mailman mailman-core mailman digests -p The "-u mailman" is important - you should use it 100% of the time, unless you specifically need root access. -i mean interactive, and -t requests a tty, neither of which you need here. Seth > On Apr 13, 2022, at 3:54 PM, bob B via Mailman-users <mailman-users(a)mailman3.org> wrote: > > Thanks, so if do not do a cronjob how often would mailman send out digests? is it daily or ????? it sounds like it is daily, But is that setup in the Docker Environment, it appears not to be? if not how do I set that up in the Docker environment? > > I thought docker mailman cron jobs run from the "docker-web" container in the file "/opt/mailman-web/uwsgi.ini" but the "docker-web" container can not run the command "mailman" command > > Do I do this in cron in the "docker-core" container or do I run it from cron on my docker host as an entry like > > 0 1 *** 'docker exec -it mailman-core mailman digests --list list(a)example.com --periodic' > _______________________________________________ > 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/

3 years

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

by marcus.granath＠gmail.com

Thank you @Mark Sapiro for you quick reply. So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: Settings -> Message Acceptance "Default action to take when a member posts to the list": "Hold for moderation" "Default action to take when a non-member posts to thelist": "Hold for moderation" Members -> Administration options -> Moderation: "List default" BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? How will they then be able to send messages, or what do I misunderstand here? Also, how do I create a "non-member" user "no-reply(a)abc.com"? Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there?

4 years

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Henrik Rasmussen

Thank you Mark. I browsed the Django Admin web interface (https://[list server]/admin) (which is actually partly in Danish for some reason) and found that in "Accounts" > "E-mail address" it is possible to uncheck "Verified", but it doesn't seem to do anything. When that user logs in again, the "Verified" check box is re-checked, but no confirmation request mail was sent to the user. Also in the Django Admin web interface under Authorization -> Users it is possible to add "account | email confirmation | Can change email confirmation" to the user's rights, but I am not sure what those do. I suppose it is to add the right to do the above mentioned. If removing the "Verified" does not make the user reconfirm, what is it for then (just trying to understand)?

6 years, 11 months

[MM3-users] Re: Do you struggle with message rejected. AUP#CDRBL while using mailman with your ISP email relay?

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > Curiously: If you DKIM sign your emails, does your ISP also co-sign > them? Is your ISP relay server published in your domain's SPF > records as an allowed sender for your domain? These are both good points. AWS SES actually prohibts DYI DKIM- signing and insists on doing it themselves (not sure why, but it suggests that there may be folks out there who dislike multiple signatures). Also, check if your ISP participates in ARC (Authenticated Received Chain, RFC 8617). You can do that yourself (best in your MTA so you can do SPF as well as DKIM validation, but Mailman provides a proof of concept option that will check DKIM and ARC-seal your message), but it may be more effective if your ISP does. Steve -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 week

[MM3-users] Re: Hyperkitty Archives - Sidebar years/months

by Abhilash Raj

On Thu, Jun 20, 2019, at 3:52 AM, Andrew Bernard wrote: > I am importing 25 years worth of archives from a list I am migrating. I > seem to be able to get messages in from a converted Listserv archive > format munged to a proper mbox format, and they turn up quite nicely in > the all threads view. But with this many years of archives, it would be > good to get the side bar panel to update. It does not at present. > I don't exactly get what does do you mean by side bar panel to update? Do you mean on the left or right? What do you see and what do you expect to see? > How do I fix this? > > Running the usual django-admin commands has no effect, but at least they > don't fail. > > Andrew > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Re: The future is here?

by Stephen J. Turnbull

Jonathan M writes: > On 6 Jan 2021, at 04:25, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > > But do be aware that you probably do have > > to make a choice between a quagmire of options and mandating a > > particular stack (or small set of them) for simplicity. > > > It would be good if Mailman could do what Discourse do here. Discourse is a different kettle of fish. They concentrate on the much more straightforward (from a network and interapp communication configuration standpoint) web service because that's what their users expect. Mail is a lot more baroque from that standpoint. We shouldn't hope to successfully "encourage" hosts to do things our way. Eg, I run Exim4 because that's what I've always done and because I'm familiar with its spam-filtering, performance-tuning, and security controls: I'm not going to switch to Postfix just because that's the most common configuration. Similar considerations apply to webserver and RDBMS (for other people; I'm comfortable with Apache and PostgreSQL). It's not just a matter of "tweaking the expert options". As far as I can see, the best we can do is what Abhilash has already done: provide a full turnkey system in a container or a Vagrant-style VM. But that has its issues, too. If somebody wants to prove me wrong, feel free. But my assessment is that there are much better uses of core developer time than chasing a one-size-fits-all configuration. A suite of scripts or better yet Ansible (etc) roles is a better fit for Mailman's audience, I think. Steve

4 years, 3 months

[MM3-users] Re: Dealing with confirmation requests for unsubscribes

by Brian Carpenter

On 11/18/20 6:17 PM, Mark Sapiro wrote: > On 11/18/20 7:41 AM, Brian Carpenter wrote: >> Hello List, >> >> I ran into the following issue for some mailman 3 lists that I am hosting: >> >> https://gitlab.com/mailman/mailman/-/issues/768 >> >> Since there is no way for a list owner to deal with a moderation request >> for an unsubscription task, I assume I need to do something via the >> command line. This is where I need some help with. How do I deal with >> these moderation requests that are unable to be reviewed in an admin gui >> (Postorius/Affinity)? > > mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the test.msapiro.net mailing list > > This > >>>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', > token_owner=TokenOwner.moderator)) > > will return something like > > [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', > 'list_id': 'list.example.com', 'email': 'user(a)example.com', > 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': > 'moderator'})] > > What you want is the token, in this case > 'a8df55f557b5718505280d2613937e25a3109252' > > Then do > > ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') > > which will return > > (None, <TokenOwner.no_one: 0>, None) > > and finally: > >>>> commit() > > >> I do recommend removing such choices for Postorius for Member policy. I >> will be doing this for Affinity until issue 768 is resolved. > The correct thing to do is fix > <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly > will do that rather than remove the moderate and confirm then moderate > unsubscription policies. > > Worked like a charm Mark. Thank you! I forget you guys have a slower process than I when it comes to implementing gui changes. For me, once you have fixed that issue (768), it will be easy for me to reintroduce those two policies for unsubscribing. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Stephen J. Turnbull

Michael Heseltine writes: > > Do you have all of these apache modules enabled, proxy.conf, > > proxy_http.load and proxy.load, in particular proxy_http.load? > > Well, mostly: > > > # a2enmod proxy_http.load > > Considering dependency proxy for proxy_http: > > Module proxy already enabled > > Module proxy_http already enabled > > # a2enmod proxy.load > > Module proxy already enabled > > # a2enmod proxy.conf > > ERROR: Module proxy.conf does not exist! In my Debian configuration that module is needed because it contains the necessary directives to enable proxying. Do you have a "ProxyRequests On" and appropriate <Proxy> blocks elsewhere in your configuration? Is it possible that you have a location control in the <Proxy> block that blocks http proxying for Mailman's URL? (I agree that this doesn't make sense given the "protocol not found" error, but I can't see how this is a Mailman- side problem, either.) Is it possible you have an ftp or other non-http proxy and shut off the http proxy for security's sake? Is it possible that the mod_proxy_http.load file is corrupt (or empty)? The a2*mod scripts do a thorough job of examining the file system, but don't check runtime functionality as far as I can see (but the last time I needed Perl I let Jeff Friedl do it for me, a loong time ago :-). The bottom line, though, is that that error message has to do with the internal configuration of Apache, and as far as I can see it has nothing to do with Mailman itself. Steve

3 years, 3 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Odhiambo Washington

On Wed, Dec 28, 2022 at 10:49 PM Mohsen Masoudfar <mmasoudf(a)aaas.org> wrote: > Thank you Mark for your help. > I see fedora under Django administration: Home > Social Accounts > Social > Accounts as a provider listed, but we do not use it and I would like to > remove it. So far I did not find a way to delete it. We do not need Hyper > Kitty either, because we do not archive any emails. > I appreciate if you could point me how I may delete Fedora as a provider. > > Thanks > Mohsen > Hi Mohsen, Edit your settings.py or settings_local.py and comment out everything to do with fedora :-) Under the Django Administration, I do not see it at all in my setup. By Django Admistration I mean https://site.name/admin/socialaccount/socialapp/ . If it's configured in there, you can just go to it's settings and remove your site from the "chosen sites" -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Outgoing STMP services? IP reputations?

by Seth Seeger

Hello everyone, Forgive me if this is the wrong list. I’m curious to hear what users are doing for MM3 hosting and what you are using for outgoing services. I am hosting a Mailman3 installation for a community that I am part of, and we have 6 lists which generated 136,000 outgoing emails last month. I’m currently hosting this on a 2-core 4GB RAM EC2 (t3a.medium) instance at Amazon. I went with Amazon because their outgoing email relay (SES) is free for the first 62,000 emails/month. (I didn’t do my homework - I thought that would be plenty!) I’d much rather be hosting on Linode, since their setup is waaaaay simpler and easier to understand. I went with an SMTP service so that I wouldn’t have to deal with managing an IP address reputation…. (Any other SMTP relay service besides the Amazon SES/hosting would cost >$80/month.) Do you use an SMTP relay service? Do you just send directly from your VM’s IP address? Do you have trouble with getting black listed? What have you done about your IP address reputation? Is DKIM and SPF enough to get past an IP address without an established reputation? Thank you! Seth

5 years

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/19/20 6:11 PM, Brian Carpenter wrote: > > No one set their preferred address here at all. The first incident was > an imported list member who was not a registered user. And the import21 created the user and address records for this user. > They wanted their > real name changed to something else. The list owner tried to figured out > how to do that, found no way to do it, figured out it was just easier to > unsubscribe them, and resubscribed them to the list using a different > name. The old name showed up again. This is a bug and please fix it > soon. If you feel this is a bug that needs to be fixed, file an issue or issues reporting it. > This has nothing to do with being subscribed to other lists. In your particular instance that's true. > I can > probably come up with a workaround using Affinity (one of the benefits > of moving away from Postorius) but I can't imagine this not being a > serious issue as Mailman 3/Postorius is more widely adopted. File an issue at https://gitlab.com/mailman/postorius/-/issues asking for the ability to change the display name associated with an address and/or an issue at <https://gitlab.com/mailman/mailman/-/issues> requesting that adding an address with a display_name as a member, non-member, moderator or owner of a list override an existing display_name for that address. I don't think you can do this in affinity because I don't think there is currently a REST endpoint to do it. You can do it easily in mailman shell, but that doesn't help the user or list admin. -- 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: Gmail/Fetchmail in Mailman3?

by Mark Sapiro

On 06/23/2018 10:49 PM, Bill Christensen wrote: > On 6/23/18 5:01 PM, Mark Sapiro wrote: >> >> Delivery to Mailman is different in Mailman 3. What are you currently >> doing with Fetchmail? > the general syntax we're using is: > > poll imap.gmail.com protocol IMAP username "<list address>" > there with password "<password>" is "mailman" here nofetchall keep ssl > sslcertck sslcertpath /path/to/share/ssl/certs > mda "/path/to/mail/mailman post <listname>" set daemon 900 >> >> If you are doing something like getting the mail from google and >> delivering it via SMTP to an MTA on the Mailman server, that should >> still work for MM 3. > I think that's what the above is doing. Right? No. what the above is doing is piping the mail to "/path/to/mail/mailman post <listname>" That is what won't work for Mailman 3. I am not familiar with Fetchmail configuration, but what you need to do is forward the mail via LMTP to localhost:8024 with recipient listname@domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 6/10/19 6:21 PM, andrew.bernard(a)gmail.com wrote: > is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it? What documentation there is is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > Anything I try to do such as the following fails: > > $ mailman shell > Welcome to the GNU Mailman shell > >>>> command('mailman shell --details') > Traceback (most recent call last): > File "<console>", line 1, in <module> > NameError: name 'command' is not defined >>>> You could just do `mailman shell --details` at a command prompt. Perhaps you saw the `command('mailman shell --details')` line in the docs at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> in any case, that requires two things to precede it. The first is part of the doctest infrastructure and is not evident in the docs. that step is from mailman.testing.documentation import cli The second step is in the docs and is command = cli('mailman.commands.cli_withlist.shell') If you do those two steps within `mailman shell`, then the step command('mailman shell --details') will work, but as I said, this is just the same as doing `mailman shell --details` at a command prompt. Beyond that, actually doing stuff within `mailman shell` requires some knowledge of Mailman interfaces, methods and objects as well as Python. Some of this is covered throughout the documentation at <https://mailman.readthedocs.io/en/latest/> but some can only be found in the source code itself. That said, all the interfaces and a few other useful functions are imported for you in `mailman shell` interactive mode. do `dir()` to see what these are. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Disable deletion of list in Postorious

by Stephen J. Turnbull

Julian Kippels writes: > I would like to configure Postorious in a way to disable the > functionality to delete a list. Is there a way to do this? You would have to patch the code. There are four levels to this: 1. You can hide the delete button on the list owner's view of the list page. (Someone who knows the URL can still invoke the callback.) 2. You can remove the delete callback from the list view code. (Someone with access to the REST API can still use that.) 3. You can remove the delete callback from the REST API. (This probably is enough, although it's possible that the 'mailman' command line utility could still do it -- I haven't checked.) 4. You can remove the delete function entirely. Depending on why you want to do this, 1 might be sufficient. I think it is unlikely that we would implement a configuration option for this. It's generally our philosophy that if you don't trust someone not to do such things, you shouldn't make them a list owner. If an owner wants to disable their list, there are several ways to do it (spam controls, emergency moderation, mass unsubscribe). But you could ask.

4 weeks, 1 day

[MM3-users] Re: Dealing with email bounces from web signups

by Mark Sapiro

On 3/16/22 12:07, Andrew Hodgson wrote: > > What I would ideally like is if we get a bounce from one of these confirmation mails we delete the user from the database but that is probably a future request. We don't get too many of these, around 20-30 a week. Since you are already directing these to a mailbox, you could do a couple of things. You could instead pipe them to a command or via cron run a command which reads the mailbox. In either case, this command could use flufl.bounce <https://pypi.org/project/flufl.bounce/> to extract the bounced address from the email message and then do whatever your current process does to remove the user. > What are other people doing with these messages? I basically do nothing. The issue of more concern to me is when the subscription uses a deliverable address. The owner of that address receives this unwanted confirmation email which is bad enough, but then sometimes reports it as spam to her ISP which affects my server's reputation. But, so far, I don't do anything about that either. -- 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: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 0:44): > On 4/6/25 14:40, via Mailman-users wrote: > >> Is your login a member of the list? > > > > It's supposed to be – when I click „Manage subscription” in the very > same thread, it reveals that I'm subscribed. This is why I can't subscribe > again. Yet I still can't post from HyperKitty, however I can by e-mail. > > > > However, when I checked the member list, I also found my address as a > „nonmember” (besides being listed as „member” too). I removed myself as > „nonmember”, but I still can't post to the list from HyperKitty. > > > What response do you get when you click `reply` on a message? and what > when you click `Start a new thread`. Do you get an error immediately or > do you get a composition dialog and only get an error when you click > `Send`. What do the errors look like? > I get a composition dialog and can type my message, but when I click send, I get the error message: „This list is moderated, please subscribe to it before posting.”. Upon reply, a red rectangle appears to enclose this message. Upon trying to create a new thread, a white page loads which only contains this error message. What do you see in Django's logs when you do this? > I don't know where to look – I don't see anything outstanding, only a few HTTP requests appear in mailman.log on mailman side and uwsgi.log on web side. None of these indicate any error. What HyperKitty version is this and is it installed from PyPI or is it a > downstream package? Version 1.3.12. It is installed through pip with the virtualenv method.

2 weeks, 3 days

[MM3-users] (no subject)

by Lars Bjørndal

I'm about to set up a new list, and want to try out Mailman3. The only component available in Fedora, is the Mailman core package. With the /usr/libexec/mailman3/mailman command, I was able to create a list, and add a member throug the sub commands create and members. How can I read out the list configuration from here, and change settings? Do I then need to install/use other components, or is there other possibilities, e.g. using the shell command? If I get a message that needs moderation, can I do the decision from cli, or how do I do that? Thanks Lars

4 years, 10 months

[MM3-users] Dealing with confirmation requests for unsubscribes

by Brian Carpenter

Hello List, I ran into the following issue for some mailman 3 lists that I am hosting: https://gitlab.com/mailman/mailman/-/issues/768 Since there is no way for a list owner to deal with a moderation request for an unsubscription task, I assume I need to do something via the command line. This is where I need some help with. How do I deal with these moderation requests that are unable to be reviewed in an admin gui (Postorius/Affinity)? I do recommend removing such choices for Postorius for Member policy. I will be doing this for Affinity until issue 768 is resolved. Thanks! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 2:01 PM, Mark Sapiro wrote: > > This has nothing to do with outlook.com per se. It only has to do with > the length of the log message. Further, I do not think there are > actually newlines in these log messages. I think that is just an > artifact of how you are viewing the log. Actually, I am incorrect. Sorry for any confusion. I agree that the long lines are folded in the log and the script needs updating. I will do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] mailman info traceback (Ubuntu Xenial)

by Pierre Abbat

I'm trying to set up a mailing list server using Mailman. I created a server running Ubuntu Xenial and installed, then removed, the Mailman in the repo, which is 1:2.1.20-1ubuntu0.1. Then I installed pip and ran "pip3 install mailman" and "mailman info" and got an error with traceback. I then tried installing sass and Django following the instructions (I have no idea about sass and Django), then uninstalled and reinstalled Mailman, and tried "mailman info" again. Here is the result: root@lists:/# mailman info Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/usr/local/lib/python3.5/dist-packages/alembic/command.py", line 504, in stamp script.run_env() File "/usr/local/lib/python3.5/dist-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/local/lib/python3.5/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/usr/local/lib/python3.5/dist-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 665, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/usr/local/lib/python3.5/dist-packages/mailman/database/alembic/ env.py", line 38, in <module> @public File "/usr/local/lib/python3.5/dist-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' What am I doing wrong, and how do I fix it? Pierre -- .i toljundi do .ibabo mi'afra tu'a do .ibabo damba do .ibabo do jinga .icu'u la ma'atman.

7 years, 5 months

[MM3-users] Re: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 2:01 PM, Mark Sapiro wrote: > > This has nothing to do with outlook.com per se. It only has to do with > the length of the log message. Further, I do not think there are > actually newlines in these log messages. I think that is just an > artifact of how you are viewing the log. Actually, I'm wrong again. It does have to do with outlook.com. It is because the Message-ID: header in the original message is folded as in Message-ID: <crlf> <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Python is updated

by Mark Sapiro

On 4/27/23 12:18 PM, Lars Bjørndal wrote: > > No. But the traceback is: > > Traceback (most recent call last): ... > File "/opt/mailman3/venv/lib64/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 669, in import_dbapi > import psycopg2 > File "/opt/mailman3/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception > > Do I need to upgrade the database? If so, how do I do that? This appears to be an issue with psycopg2 itself. What happens if you activate your venv and do python -c 'import psycopg2' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: The future is here?

by Jonathan M

On 6 Jan 2021, at 04:25, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > But do be aware that you probably do have > to make a choice between a quagmire of options and mandating a > particular stack (or small set of them) for simplicity. It would be good if Mailman could do what Discourse do here. You can install it any number of ways but they push you towards one installation option. This makes it easier for and instils confidence in less technical people, and makes it easier for the developers to provide support. At the same time, it’s possible for an expert to choose different options. Have a look at: https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md Best wishes Jonathan

4 years, 3 months

[MM3-users] Re: Can "Pre Verified" set to yes by default?

by Stephen J. Turnbull

Alan So writes: > Instead, if the core team believe that the feature is useful and is > willing to incorporate the feature to the main branch, I think that > it is a better way of handling it. For some reason, admins always feel that way. ;-) We feel the opposite way. :-) Let me explain why. This is a *really big* ask. *Every* configurable element of every screen has some sort of default, and somebody somewhere probably wants to be able to customize it. As my mentor on another project used to ask, "Why do all the defaults suck?" The answer seems to be, "well, they just do." For somebody, somewhere, anyway. The problem isn't writing the code, I doubt it would be difficult to come up with boilerplate to allow sitewide configuration of all the defaults for all actions. The problem is thinking about the admin's user interface for this. Sure, we could put some kind of mechanism in settings.py, but how do we document all the configurable defaults? How do admins discover them except by asking on mailman-users? And changing that much code would probably be pretty tedious. > The change is also supposed to be more aligned with the design. I don't understand what that's suppposed to mean. If you do it, you're changing a default, that's all. There's no real design here. It's just a question of the greatest good for the greatest number, which is an empirical question. You have a different answer for your site than most Mailman sites (which are open subscription and normally the admin has no real-world connection to subscribers, so verification of address is needed). Your request is perfectly reasonable, but similar requests for site configurations of every other default would be just as reasonable -- which implies a lot more work for us than you're willing to do for your list admins. Am I missing something? Steve

2 years, 4 months

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 20:25:44 CEST schrieb Mark Sapiro: > On 10/13/22 10:55, Eggert Ehmke wrote: > >> It shouldn't have been necessary to apply any patch. The head of the > >> GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > > > > strange, I still had the line with the (not working) > > from mistune.scanner import escape_html, escape_url > > > > maybe because the migration step was not working at that time? > > It should have nothing to do with migrations. The command > ``` > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > ``` > run as the mailman user with your venv active should have set the > content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > to be the same as > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer. > py, but it didn't. I wonder what else didn't get upgraded? Clearly it did do > something because mistune was upgraded. In the meantime I run pip install --upgrade --force-reinstall git+https://gitlab.com/mailman/hyperkitty@master and that installed the correct renderer.py. Should I do this with all packages? > If you run `pip freeze` in your active venv,, what versions do you see > for the things you upgraded? Do they look for example like > ``` > HyperKitty @ > git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a28 > fd7803 ``` Yes that version is installed.

2 years, 6 months

[MM3-users] Mailing lists sometimes do not honor moderation_action of non-members

by Alan So

We notice that sometimes mailing lists do not honor moderation_action of non-members. Instead, it follows the default action of the lists. It looks like we can sometimes fix the issue by adding/removing the non-members or adding/removing them as owner in certain order but we are not sure about exactly what we have to do. So, it looks like that it is not caused by the list configuration. We have already verified from the web UI, mailman client and the DB table member that moderation_action of the corresponding non-members are set correctly. Any clues for us to provide further information to troubleshoot the issue and any recommended workaround to get around the issue? Thanks a lot.

5 years, 5 months

[MM3-users] Hyperkitty_import.py Error

by Brian Carpenter

I am trying to import some old archives (going back to 2003) into a Mailman 3 list. The import job is terminating very early in the process with the following error: IndexError: string index out of range 1. Is there a way to fix a mbox file that is generating this type of error? 2. If a message is causing this error, is there a way to import the rest of the mbox file by importing messages after a certain date within the mbox file? I know the --since flag should be able to do that but I am unsure what the date/time format should be. 3. The --no-sync--mailman flag indicates the possibility of doing batch imports. What are batch imports and how do you do them? Thanks! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 2:38 PM, Mark Sapiro wrote: > On 3/15/21 2:01 PM, Mark Sapiro wrote: >> >> This has nothing to do with outlook.com per se. It only has to do with >> the length of the log message. Further, I do not think there are >> actually newlines in these log messages. I think that is just an >> artifact of how you are viewing the log. > > > Actually, I'm wrong again. It does have to do with outlook.com. It is > because the Message-ID: header in the original message is folded as in > > Message-ID: <crlf> > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> Sorry for the premature send. I'm having a bad time with this thread. :-( I meant to say It does have to do with outlook.com. It is because the Message-ID: header in the original message is folded as in > Message-ID: <crlf> > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> and the added <crlf><space> actually gets included in the log message. Anyway I have updated the script at <https://www.msapiro.net/scripts/smtp_report>. My update is much simpler than the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, but I have tested it, and it works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Simon Hanna

On 05/22/2018 02:12 PM, Henrik Rasmussen wrote: > Thank you Mark. > > I browsed the Django Admin web interface (https://[list server]/admin) (which is actually partly in Danish for some reason) and found that in "Accounts" > "E-mail address" it is possible to uncheck "Verified", but it doesn't seem to do anything. When that user logs in again, the "Verified" check box is re-checked, but no confirmation request mail was sent to the user. > > Also in the Django Admin web interface under Authorization -> Users it is possible to add "account | email confirmation | Can change email confirmation" to the user's rights, but I am not sure what those do. I suppose it is to add the right to do the above mentioned. > > If removing the "Verified" does not make the user reconfirm, what is it for then (just trying to understand)? That is part of allauth. My guess is that the confirmation is overridden by Mailman's setting for the email before allauth get's a chance to reconfirm it. The second thing is relating to the django admin. If you give people staff privileges (in the admin under Users), you can theoretically fine-grain control what they are allowed to change using the admin.

6 years, 11 months

[MM3-users] Re: Customise Postorius templates?

by Duane Raymond

On Mon, 7 Feb 2022 at 00:56, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Feb 1, 2022, at 11:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 2/1/22 09:47, Duane Raymond wrote: > >> Hi, > >> I'm looking to do some radical customisation of the Postorius (and > Hyperkitty) templates over the next 6 ish months and was wondering if there > is a 'best practice' way to do this that will survive updates to MM3. I've > searched around and not found much and also tested copying > >> > venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html > >> to > >> var/templates/lists/summary.html > >> As suggested in some posts - but it didn't seem to pick up the > customisation - only customisations in the venv path worked - and they get > overwritten on update. > The best way to do this would be utilize Django’s template loader. See > here[1] for the documentation on how you can do this. You want to put the > path where you are putting the templates under `DIRS` option of the > `TEMPLATES` section. > > Do make sure that you are keeping the directory structure correct so that > Django can discover them. Like, Hyperkitty’s base.html should be in > `/custom/path/hyperkitty/base.html`, where `/custom/path` is what you’ve > setup in DIRS setting above. > This looks promising! I've not got it working yet, but this is what I've tried: 1. Created folder 'custom' in the mm root (in my case: /opt/mailman/mm/) 2. Copied the files and folders from postorius/templates/postorius/* and hyperkitty/templates/hyperkitty/* to the custom/ folder (not the full postorius/templates/postorius/ match, just evening in the second postorius/ dirrectory) 3. Recursive update of permissions of the custom/ folder and files to be mailman 4. Updated /opt/mailman/mm/settings.py by changing "'DIRS': []" to "'DIRS': [BASE_DIR, '/custom/']" in the "TEMPLATES =" section 5. Edited the original AND copied postorius/lists/summary.html to have a small change in the footer of each so I know what version it is serving 6. Restarted: gunicorn qcluster mailman nginx and cleared browser cache 7. Reloaded the 'info' page of a few lists to see which version ti was serving Variants: I've also changed the DIRS value to the hard-coded path: /opt/mailman/mm/custom Result: it is still serving the default/original Postorius template vs the custom one. Any suggestions for things I should do to make it use the /custom/ folder instead? Any recompiling or other actions beyond just restarting? (I probably don't need to restart qcluster and maybe not even mailman core for this to take effect but I do it just in case!) Cheers, Duane

3 years, 2 months

[MM3-users] Re: MM3 does not receive gmail-Members!

by Mark Sapiro

On 4/24/23 1:58 PM, Paul Brenner wrote: > Hallo > I need help! > My MM3 sends mails via a list. However, no mails arrive at all gmail > recipients. > These mails also do not end up in the spam or junk folders. > What do I have to do? If you have access to the outgoing MTA logs, what do they show about mail to these gmail recipients? Without access to these logs, you can set Process Bounces and Notify owner on bounce increment both to Yes in Postorius -> Bounce Processing and you should receive notices when mail is reported as undeliverable. These notices or the log entries should give a reason for non-delivery. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Sorry to repeat a question, but how do I permanently delete messages, again?

by William Oliver

I askled this question some months ago, but for the life of me cannot find the response (though there is one). I want to purge some specific emails from the list archives. A user posted what he thought was a personal message to the list, and is embarrased by it, so I told him I couldn't delete emails that were already downloaded onto client machines, but I can delete it so that new users won't be able to see it. But... I can't figure out how to do it. I asked this once before, some months ago, and as I remember there is a command line way of doing it, but not a GUI way. But i can't remember what it was. Thanks! billo

2 years, 9 months

[MM3-users] Re: Newbie hyperkitty question

by Mark Sapiro

On 1/11/22 8:27 AM, Stephen Daniel wrote: > Mailman users -- > > I am setting up a new mailman3 installation, and this is my first > experience with the suite. All of the software is up and running, but I > cannot tell if hyperkitty is actually running. In Postorius, in the list's `info` view can you click the Archives button and see archived messages? That's HyperKitty. If the messages aren't there with the hyperkitty archiving option enabled, check `mailman.log` for why. Also do messages from the list have an Archived-At: header? > When I look at my test mailing list, two archive options are available, > hyperkitty and "prototype", and both are enabled. I can see that my email > is being archived, but I think "prototype" is what is doing the archiving. > I see that a test message will end up in > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > and nowhere else. This suggests that "prototype" is archiving, but > hyperkitty is not. No this says the prototype archiver is working. It says nothing about Hyperkitty. > So, this opens up a raft of questions on hyperkitty: David Newman has answered some of this, but ... > - How do I tell if hyperkitty is actually running? It doesn't actually run. it is a Django web UI and a web API that serves things on request. > - Does hyperkitty have a web-UI for admins or users? How would I access > it? See above. > - I can not find any documentation on hyperkitty, other than > installation instructions and change logs. Does documentation exist? No, not really. > - How do I set policies on how long archives are kept? > - Assuming I want to back up my archives, what do I need to back up? Messages are kept forever unless you do something to delete them. HyperKitty's messages are stored in the database configured in the DATABASES setting in your Django settings. How you backup the database depends on the database manager. You already found the prototype archiver's messages. -- 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: Mailman messages are getting a TAG in some email clients.....how????

by Mark Sapiro

On 9/12/23 8:51 AM, bob B via Mailman-users wrote: > So I know about the setting "Anonymous list" but regardless of that setting some email clients put the list name in [] when it displays messages in your inbox. Does anyone know how email clients are doing this? I have users who email clients do not do this, and was wondering if it is a setting in their client or just not possible. This looks like Mailman adding 'Subject prefix', so all list mail will have this prefix added to the Subject:. So the question isn't how mail clients are adding it, but rather why do some mail clients suppress it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/14/2018 03:04 AM, Aymeric Mansoux wrote: > > So far so good, however, for some reasons, a couple of our lists have started to accumulate held messages that cannot be manipulated via the REST API. Regardless if we use the web interface or mailmanclient, it ends up with: > > Mar 14 10:58:32 2018 (24287) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3.5/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.5/dist-packages/falcon/api.py", line 244, in __call__ > responder(req, resp, **params) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 70, in _make_resource > resource = super()._make_resource(request_id) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 39, in _make_resource > results = requests.get_request(request_id) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.5/json/__init__.py", line 319, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.5/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) > Mar 14 10:58:32 2018 (24287) 127.0.0.1 - - "GET /3.1/lists/xx(a)xx.xx/held HTTP/1.1" 500 59 > > Is there a way to manipulate/see/remove these mails differently? Right now this prevent moderation of any held messages (note: some lists do not suffer from this and the held panel or mailmanclient works perfectly fine). We've seen this issue before with a different underlying cause. See <https://gitlab.com/mailman/mailman/issues/256>. There are a couple of problems here. The serious problem is if there is a held message which somehow throws an exception in processing in mailman/rest/post_moderation.py, that totally breaks the Postorius held messages view for that list. We need to fix that. Also it would be good to see the problem message. Here are some things you can do in 'mailman shell' (aka mailman withlist). It is not clear what might not work, but you can try mailman shell -l list@domain which will respond Welcome to the GNU Mailman shell The variable 'm' is the list@domain mailing list >>> Then you should be able to do at the >>> prompts: >>> req_db = IListRequests(m) >>> reqs = list(req_db.held_requests) reqs is now a list of the held requests and you can do something like >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... or since req_db.held_requests is a generator >>> for req in rdb.held_requests: ... print('{}: {}'.format(req.id, req.request_type)) ... either of which will produce a list like 1: RequestType.held_message with the IDs and types of each request. You can handle these requests with something like >>> from mailman.app.moderator import handle_message >>> handle_message(m, 1, Action.defer) where the second argument is the ID of the message and the action is one of Action.defer, Action.hold, Action.discard, Action.reject or Action.accept, the first two of which do nothing, but the others will do the indicated action. You can see the actual messages like this >>> msg_db = getUtility(IMessageStore) then >>> key = req[0].key >>> msg_db.get_message_by_id(key) which will return the actual held message that is in this case index 0 in the list of held_requests. You may have to do >>> commit() when done, although if you don't do abort(), just exiting with control-D should do a commit(). I hope you find this helpful, and if you do determine the content of the offending message(s), it will be helpful if you post that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Can "Pre Verified" set to yes by default?

by Stephen J. Turnbull

Alan So writes: > However, some of our departmental staff sometimes forget to check > the box "Pre Verified" when they refresh (actually delete all and > subscribe all) list of members during term's start. [...] > Is this possible to add default setting of Pre Verified during > mass-subscription (for example settings.py) such that we can help > them a bit? I don't know if there's a way to do this in settings.py, but I suspect not. Maybe Mark knows a way. However, you can find .../site-packages/postorius/forms/list_forms.py (not sure exactly where that is in your instance but I guess you probably do), and find this code (AFAICT this is the unique instance of 'Pre Verified' in the whole Postorius code base) in that file: pre_verified = forms.BooleanField( label=_('Pre Verified'), initial=False, required=False, help_text=_( 'If checked, users will not have to verify that their ' 'email address is valid.'), widget=forms.CheckboxInput() ) Then just edit the line initial=False, to initial=True, Note that this will get overwritten if you upgrade (or reinstall) Postorius, and you'll have to do it again. But it will save you a ton of grief until that happens. Also note that if there *is* a way to do this in settings.py, it is *safe* to do that later without reverting the change to list_forms.py, and the settings.py setting will continue to work after any upgrade or reinstall. So you can patch list_forms.py now without worrying it will get you into trouble later. Steve

2 years, 4 months

[MM3-users] Re: Is there a way to see all the list's held messages

by Mark Sapiro

On 10/11/22 07:04, bob B via Mailman-users wrote: > I run mailman but do not admin the lists. Is there a way for me to see all the held messages for all the lists? There are various things you can do depending on what you want. Does 'I run mailman' mean you are an admin of the server on which it is installed? If so, you can do this in `mailman shell`, but what do you want to see? I.e., just a summary by list of subject, sender and hold reason or also the message content. Also, the Django superuser has full admin access to all the lists and again depending on what you want, that may suffice. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] How do you remove the Hold on all non-member forwarded emails?

by Sean Westfall

Hi Mailman3 users, I have recently started using mailman3 and it's a wonderful piece of software. But I am having trouble using one of its configurations. I configured my mailmain3 instance to accept all non-member emails, as I want all emails that are sent to the mailman client to go to all subscribers without having it held for moderation -- I did this by setting this setting: https://i.imgur.com/PGzaD0k.png Action to take for postings from non-members for which no explicit action is defined. (Details for generic_nonmember_action) -> "Accept" But this doesn't work for forwarded emails. Even if the email address that is being forwarded from is included in the "List of non-member addresses whose postings should be automatically accepted." I noticed that all emails that are forwarded to the mailing list are always held for moderation -- though this isn't the case for email that are sent to the mailing list directly. But I want it so that emails that are even forwarded to my mailman mailing list don't get held in moderation. How do I set mailman to do this? I was thinking if there is no way to configure this easily then I might have to do this from the code, which means I might have to ask on the developer mailing list -- or I have to go with an entirely different solution (using something other than mailman3). I hope someone here is willing to help, and in either case thanks for anyone that is willing enough to read this. Sincerely,

1 year, 10 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Stephen J. Turnbull

gordon(a)dickens.com writes: > How do I uninstall the Debian version and then reinstall with the > venv and web instructions so that all of my mailing lists and > configuration data are preserved? tar czf /tmp/mailmandata.tar.gz $PATH_TO_MAILMAN_DATA Not sure where Debian puts it but I would guess /var/lib/mailman. You can also try apt-get --dry-run remove ... but I think that provides output at too coarse a level (packages, not files). Generally apt is pretty good about not removing files that are not in the package, though. > I may elect to go that route if I can preserve all of my mailing > list and data and you think that would be a quicker route to a > solution. Is there a simple way to do this? Then you can do apt-get remove $MAILMAN_PACKAGES with confidence. Do not do apt-get purge ..., of course (although I suspect even that will leave your archives and mailing lists). We still generally recommend installing from source, or possibly using the docker containers that Abhilash provides (usually quite promptly after a release). First, you're not dependent on a distro for new features, and Mailman 3 is still by no means feature-complete. (On the other hand, the distros are good about providing security upgrades, and often the easiest route for them is a version bump). Second, if you put stuff where we tell you to, we know where it is when you ask for advice. I'm a Debian user, but I don't use their packages for Mailman itself. Steve

3 years, 3 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Stephen J. Turnbull

Mark Sapiro writes: > I say you have to understand what you want Postfix to do and configure > it appropriately. I would recommend going to a Postfix list as Mark suggested. Postfix configuration is complex, and they're more likely to know the best way to do exactly what you say you want to do. I myself can't help with Postfix details, I'm an Exim user. But my list of "need to know" stuff is generic, just the answers would be very different with Exim or Sendmail or qmail! > I would need much more information in order to know how your Postfix > should be configured, In particular, whoever answers your questions will need to know: 1. Why are you using virtual domains for email? This doesn't need to have great detail. Mostly: - are you supporting multiple organizations with their own domains, OR - is this for some purpose of your own, OR - did you just copy the virtual domain lines from some example configuration? In the last case, you might try not even mentioning that you're using virtual domains. (That's only if you treat this as a "new install". If you're going to send them your current configs, they'll see your virtual domain stuff and want to know "why?" You may as well tell them.) They may tell you that you can do everything you want without them! Or they may tell you that virtual domains are the best way to do that, and you can be confident about it. In the last case you could also try just deleting and seeing if your system works, as you suggested to Mark earlier. But that could also break everything related to mail on that host. 2. Who is receiving mail via Dovecot, and via what domain(s)? The "who" is generic (eg, "users and web applications using IMAP clients"), but the domains should be specific. If not inconvenient, it is easiest if you give real names for the domains. If there are privacy, security, or intellectual property concerns with the domain names, you'll need to find out the conventions used by the Postfix community for dealing with that. If you do redact your domain names in your explanation in the initial contact, make sure you explain exactly how you did that, or you will confuse everybody and have an unpleasant experience. 3. What domain does Mailman use to receive mail? Is Mailman the only thing that receives mail on that domain? What else, if anything, needs to received mail addressed to that domain? 4. What domains other than those handled by Mailman and Dovecot, if any, are processed by your Postfix MTA? 5. What other things, if any, besides Mailman and Dovecot directly receive mail processed by your Postfix MTA? Anything downstream from Mailman and Dovecot doesn't need to be mentioned. If there are still problems with downstream recipients once Mailman and Dovecot are receiving mail correctly, direct those issues to us and to Dovecot, as appropriate. You should check the channel FAQ to see whether they want your configuration in your first contact, or not. Even if they do, you might be better off to treat this as a "new install" rather than "it's broken, help me fix it". In contacting the Postfix channel, explain "I want to ..." based on the answers to those questions. Then your question is "how do I configure mail so that Dovecot domains and users get mail, Mailman domains, lists, and administrators get mail, and any other mail handled by Postfix goes to the right place (as defined by questions 4 and 5)?" Steve

4 years, 9 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mohsen Masoudfar

Thank you Mark for your help. I see fedora under Django administration: Home > Social Accounts > Social Accounts as a provider listed, but we do not use it and I would like to remove it. So far I did not find a way to delete it. We do not need Hyper Kitty either, because we do not archive any emails. I appreciate if you could point me how I may delete Fedora as a provider. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, December 27, 2022 4:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdjango-al… -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org

2 years, 3 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/6/25 16:00, MegaBrutal via Mailman-users wrote: > Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 0:44): > >> What response do you get when you click `reply` on a message? and what >> when you click `Start a new thread`. Do you get an error immediately or >> do you get a composition dialog and only get an error when you click >> `Send`. What do the errors look like? >> > > I get a composition dialog and can type my message, but when I click send, > I get the error message: „This list is moderated, please subscribe to it > before posting.”. Upon reply, a red rectangle appears to enclose this > message. Upon trying to create a new thread, a white page loads which only > contains this error message. In that composition dialog below the text box, it should say ``` This message will be sent as: user(a)example.com Link another address If you aren't a current list member, sending this message will subscribe you. ``` What the error is saying is it is checking if the sender is subscribed to the list and it finds that it is not subscribed. It wants to subscribe the sender but the list's subscription policy is "moderate" or "confirm_then_moderate" and it doesn't want to bypass moderation so it issues the error. Is the address I have shown as user(a)example.com what you expect and it it a list member? What if you click that address (it's a link) and chose another subscribed address. > What do you see in Django's logs when you do this? >> > > I don't know where to look – I don't see anything outstanding, only a few > HTTP requests appear in mailman.log on mailman side and uwsgi.log on web > side. None of these indicate any error. If you configured your settings.py per https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… your Django log which is where HyperKitty logs is at /opt/mailman/web/logs/mailmanweb.log. However, I don't think there will be anything useful there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 3 days

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 12:30, Wikinaut wrote: > Now I wanted to start uwsgi, after having setup everything as documented but I got in the error log this: > > ModuleNotFoundError: No module named 'allauth.account.middleware' As it says at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… "Note either downgrade django-allauth or update MIDDLEWARE, but not both." Now you have added 'allauth.account.middleware.AccountMiddleware' to MIDDLEWARE and downgraded django-allauth<0.56. You can either do ``` pip install --upgrade django-allauth ``` or remove ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` from /etc/mailman3/settings.py. Either will do, but DO NOT DO BOTH. -- 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] Can "Pre Verified" set to yes by default?

by Alan So

We are a university with many departments & colleges owning their own mailing lists and they manage their members lists by themselves. The current (ours is 1.3.6) Postorius have a default of "Pre Verified" as "No" when doing mass subscription by the list admin. It sounds sensible if most people subscribe to the lists by themselves normally. But in our case, our departmental staff normally maintain their list of members and do not want their members need to do anything before they can be reachable from lists. However, some of our departmental staff sometimes forget to check the box "Pre Verified" when they refresh (actually delete all and subscribe all) list of members during term's start. This often lead to issue especially if the list they maintained have thousands of members. Our normal way to help them is to remove the list and create the list again so that the departmental staff do not need to discard the pending members one by one. This is already the best scenario if they know that it is the root cause. Since subscribing thousands of members normally will not have the normal UI page coming back (due to timeout), they often do not know that it is the cause of issue. If they repeat the steps to subscribe the members again, they will just not be able to get the job done but also make the system busier and they never know that it's already in the pending list. Is this possible to add default setting of Pre Verified during mass-subscription (for example settings.py) such that we can help them a bit? Thanks.

2 years, 4 months

[MM3-users] Re: Turn off social logins?

by Abhilash Raj

This is kind of a top-post, because I am not sure which message should my reply quote. Please excuse that part. My thinking on this topic resonates with what Steve said, I don't think we should be forcing the Mailman Administrators to handle username passwords. Dare I say that most social auth providers have more incentive and money to keep their database secure than Mailman Administrators. Having said that, it doesn't have to be either or between "social logins enabled by default" and "I don't want to see a Facebook button". I have actually thought about this before, but never have been able to get to it. I opened an issue too but can't find it right now. Anyway, so the idea is that most social providers need some soft of configuration from the Admin. Today, we enable them by default, but they don't work by default. I think we could make both sides happy if we were to just not show the social providers that aren't configured. What do others think? Only two providers that I know of in Mailman's default list, which don't need any configuration, are Fedora and OpenID. I am happy to remove OpenID from default since I have never been able to actually get that to work. I am okay with removing Fedora too, which is a special case in Mailman 3 because of fedoralists.org being the first customer for Mailman 3 and Hyperkitty. I don't have cycles to do that myself right now, so I would encourage people to step up to tackle this. I would obviously help them out with any Python, Mailman or Django related questions they might have. Now, about the ease of being able to disable social logins, I think it should be possible to disable social logins with just a boolean flag in settings. Why haven't we done it yet? We didn't need to. What we provided was a **sample configuration**, with a huge emphasis on sample. We weren't maintaining it as an official set of configurations, but just something that one could use as a starting point. But that obviously didn't happen since people just downloaded and used it, some of which is ofc my own fault since the official docs doesn't say that what precisely you should be worried about changing from the sample. The beauty (and ugliness) of Django's settings.py is that it is Python. We can disable social login if your CPU heats up[1], or if the stock price of the company goes below (or above? :P) a threshold, or heck, if the network firewall detects a packet heading out to their servers. How Django's configuration works has been left kind-of open by the Django devs themselves, making every downstream project handle their own use case separately. We chose to just go with what was provided out of box, but that doesn't mean we can't do any better. We can do ini-style configs, it gets a tad bit complicated when there are unknown Python data structures that can't easily be represented in ini-style. We could do YAML, which supports more complicated data structures (nested maps and lists). OR, we could do JSON, but I find that less human readable. Next topic, people worrying about customizing settings in settings_local.py and worrying about not getting newer updates. Isn't this how rest of the packaging and configuration world works? If you customize the `/etc/postfix/main.cf` you don't get the updates to default config (apt asks you, but you will choose not to update with your custom settings, right?) when you upgrade your postfix package from Debian and you need to pull in any new settings that package supports manually. I have been (silently) working[2] on making the `mailman_suite` project a Python package (mailman3-web), like the Debian Maintainers did. That would be the right place to put whatever configuration logic we want to expose to our users. We can move to a model where you'd import all the settings from `mailman3_web.settings.base` and then customize all the fields that you do care about. But there will be downsides to it, like us updating a setting that changes the behavior of an already working site, and we can sure document those changes in release notes in big bold letters, but I still worry there will be people running `pip install -U` without thinking what does that even mean. I don't know what should we do? What do other people managing configurations do? Maybe Debian Maintainers can chime in here? [1]: https://xkcd.com/1172/ [2]: https://gitlab.com/maxking/mailman-suite/commits/master On Fri, Feb 15, 2019, at 8:43 AM, Mark Sapiro wrote: > On 2/14/19 11:10 PM, Stephen J. Turnbull wrote: > > Torge Riedel writes: > > > > > - there is a way to do this now via settings_local.py, but feels > > > a little bit risky if default configuration changes on update of > > > mailman > > > > This should not be true. If it is, we need to fix that. Will check. > > > It is more or less true. The issue is that unlike mm_cfg.py and > Defaults.py in Mailman 2.1, the recommended way to set up Django in > Mailman 3 is to point Django at settings.py for the default config, and > the last thing in settings.py is > > try: > from settings_local import * > except ImportError: > pass > > Thus,the only way settings_local.py can change something like > INSTALLED_APPS is to redefine INSTALLED_APPS in it's entirety which > leads to the possibility of INSTALLED_APPS changing in settings.py and > those changes not being picked up in settings_local.py. > > The way around this is to remove the import of settings_local from > settings.py and then put > > from settings import * > > at the beginning of settings_local.py and then point Django at > settings_local rather than settings. > > Then you can do things like > > try: > INSTALLED_APPS.remove('allauth.socialaccount.providers.google') > except ValueError: > pass > > in settings_local.py except there are still issues because, e.g., > INSTALLED_APPS is defined as a tuple (immutable) and not a list in > settings.py. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 04:00, andrea.janna.unipd(a)gmail.com wrote: > > Yes it's mailman gatenews that triggers mariadbd "[Warning] Aborted connection" log entries. > I don't use this feature so as a workaround I set a large gatenews_every interval in mailman.cfg. > > [nntp] > gatenews_every: 1000000m Or you can do as Danil does <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and put ``` [runner.nntp] start: no ``` in mailman.cfg. However, it is unclear what in gatenews would do this. Assuming you have no lists for which gateway_to_mail is true, all gatenews will do is ``` def process_lists(glock): list_manager = getUtility(IListManager) for mlist in list_manager.mailing_lists: glock.refresh() listname = mlist.fqdn_listname if not mlist.gateway_to_mail: continue ``` The database operations involved in this are things Mailman core is doing all the time, presumably without issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Syncing Real Name between user account and membership

by Andreas Barth

* Abhilash Raj (maxking(a)asynchronous.in) [201219 06:28]: > I am just wondering if Core's API should do this (probably not by > default, but with a bool parameter that P can use every time), or > should we iterate over all addresses and PATCH the display names in > them (would be slower, with multiple API requests). > > I am leaning towards the first option. What do you think? I agree to that. Also, I'm just trying to do a small sync script for the moment (using mailman release 3.3.2) for user in client.users: if not user.display_name: continue for address in user.addresses: if address.display_name == user.display_name: continue address.display_name = user.display_name address.save() and getting the response urllib.error.HTTPError: HTTP Error 405: Also the server side log doesn't tell me more: [19/Dec/2020:14:00:00 +0100] "PATCH /3.1/addresses/aba(a)ayous.org HTTP/1.1" 405 0 "-" "GNU Mailman REST client v3.3.2" Any hint what I'm doing wrong here? Regards, Andi

4 years, 4 months

[MM3-users] Re: Templates

by David Krantz

Still two problems: 1. I do not know how to force a cache invalidation on a template. So only way to change is to set a new name on the file and change the uri there. Unpractical. No, restarts do not work. 2. the $user_delivered_to and $user_email do not expand for some reason. Known problem? Cheers // David On Sat, Sep 23, 2017 at 3:52 PM, David Krantz <gazorg(a)gmail.com> wrote: > Hi. > > Ok, checking the source helped. So I answer my own question: > >> mailman shell > Welcome to the GNU Mailman shell >>>> tm = getUtility(ITemplateManager) >>>> tm.set('list:member:regular:footer','mymaillist.example.com','file:///my_absolute_path/list:member:mymaillist.example.com:footer.txt') >>>> commit() > > // David > > > On Sat, Sep 23, 2017 at 1:17 PM, David Krantz <gazorg(a)gmail.com> wrote: >> Hi. >> >> How do I set a template for one specific list? I want one list to have >> a special footer template. >> >> I have tried updating the database (template table) without effect so >> apparently the database is not used for templates or some kind of >> fallback is used to set it to the generic footer. Of course I also >> tried to restart mailman after that operation to try to rule out any >> caching-related problem. >> >> I want to use a file://-path as that is the least painful way of doing >> it. I also would like a solution to place a file in a special >> location. My current templates are in a >> >> .../var/templates/site/en/ >> >> structure with names like list:member:generic:footer.txt >> >> Cheers >> // David

7 years, 7 months

[MM3-users] Do i need a mailman-hyperkitty.cfg file?

by Bill Oliver

While trying to set up my new mailman installation in Ubuntu 22.04, which doesn't quite work yet, I decided to compare my config files with my Ubuntu 24.04 LTS installation, which does seem to work to the degree I've tested it. I noticed this little snippet in the settings.py file: # Set this to match the api_key setting in # /opt/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). MAILMAN_ARCHIVER_KEY = 'Secret_Hyperkitty_API_Key' Aha, I thought. I should have changed that. Then I noticed that I didn't even have a mailman-hyperkitty.cfg file, and I can't find mention of it in the venv instructions. I *have* installed mailman- hyperkitty during the "pip install mailman-web mailman-hyperkitty" step. I did a "find" on /opt/mailman, and it doesn't seem the file is there at all. Do I need this file? I found a template here: https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… Do I need to copy and paste that in my installation? Thanks! billo

5 months, 3 weeks

[MM3-users] Re: mailman changeaddress: Address already exists; can't change

by Mark Sapiro

On 10/10/24 8:58 AM, joelbrownstein(a)computer.org wrote: > Hi, > > We migrated ~100 lists from mailman2 to mailman3 (very nice!) including > 6000 distinct email addresses ("subscribers"). > > I would like to run the mailman changeaddress command to do a global change of email for a member that moved. But they have other subscriptions using their new email, so both the old and new address are migrated to mailman3 as distinct "members", which prevents the mailman changeaddress from making the change with error: > > $ mailman changeaddress "EMAIL_1" "EMAIL_2" > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address "EMAIL_2" already exists; can't change. There is a major difference between MM 2.1 and MM 3 in this respect. In MM 2.1, a list member is an email address that bears no relation to any other member of this or any other list. In MM 3, there is a user which corresponds to a person which has one or more email addresses which can be members of lists with various roles. What happened here is importing the MM 2.1 lists created a user for EMAIL_1 and subscribed it to some lists an created a separate user for EMAIL_2 subscribed the other lists. You can't change EMAIL_1 to EMAIL_2 because EMAIL_2 is already a separate user. There are two ways to deal with this. You can use `mailman findmember EMAIL_1` to list all of EMAIL_1's memberships and edit that to make a shell script that will do `echo EMAIL_2|mailman addmembers -f - LISTNAME> to add EMAIL_2 to all of EMAIL_1's lists and then do `mailman delmambers -m EMAIL_1 --fromall` You could do direct database manipulation. First get the id and user_id of the address table entries for email = EMAIL_1 and EMAIL_2. If we call them aid_1, uid_1, aid_2 and uid_2, do ``` UPDATE member SET address_id = aid_2, user_id = uid_2 WHERE address_id = aid_1; ``` Caveat: I haven't done this. I think it should work, but no guarantees. Backup the database first in case of problems. After doing either of the above, there will still be a user with address = EMAIL_1, but that user should have no subscriptions. You can delete that user via Postorius and if desired the remaining user with address EMAIL_2 could add EMAIL_1 as another address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Paul Arenson

Hmmm ...email sent twice is not getting through, so I will post directly. Thank you Mark. I found my solution. Simplifies things. People do not have to even think about subscribing….. When I consider that most of my subscribers from my current announcement only lists on Mailerlite and dadamail will already have their addresses mass-added by me, I do not really need to worry about the two kinds of signups at all that much. Since they will be coming from my website, where I have news and current affairs content, all I need to do is link to the discussion tied to the article in question. And then let them comment/reply. I can manually post a comment if they are newcomers or if they are old timers with a new address not yet registered. LIke this: 1) Do not list on list of lists. No reason to have it as everyone will come from my site. 2) Make an open archive. 3) Link from website article to the corresponding topic to discuss it. 4) Majority of readers are already subscribers to old announcement list on mailerlite. So they will assume all they have to do is reply. 5) When they, or anyone, click on the article at https://www.tokyoprogressive.org/remembering-the-tsushima-maru-disaster-75-… they get taken to the discussion topic at https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… 6) They click REPLY to add a comment and their email sends. 7) If their email address is registered, the comment gets through. 9) If not (non subscriber or old subscriber with new address), I make sure it is a legitimate message and add them as a subscriber. They get a notice automatically telling them how to post. OPTIONAL STEP I probably do not need to bother about adding their names to the signup for Hyperkitty but I could optionally add them to https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… with a temporary password. They get a note to confirm. Or probably just enough to send them a note suggesting they might want to sign up to be able to use the archives to post. My list is probably not going to benefit from stressing over the different ways to register. How does that sound? I tested with a test address and it seems to work. I just need to add a note to my website remniding them to add their name to the end of their post as it does not automaically add their email if I have to approve. paul

5 years, 7 months

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 17:24, Mark Sapiro wrote: > On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 16/9/21 16:40, Mark Sapiro wrote: >>> >>> Are you asking what the equivalent MM 3 scripts would be? >>> >> More or less: I'm asking for a general direction here. I think I >> cannot use tthe "withlist" method as before, inside a python script, >> and I'm not sure how to do it. > > > You can run scripts via withlist in Mailman 3 similarly to Mailman 2. > See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > First, thanks for the prompt response, Mark. Maybe I'm a little bit ofuscated, but I readed this doc many times when I was searching how to do it... but I cannot imagine how to do a shell or a python script, using the needed parameters, that sets hold on a member of a list. I'll try to do some tests tomorrow. As said, thanks.

3 years, 7 months

[MM3-users] Re: Python is updated

by turnbull

2023-04-28 05:10 に Odhiambo Washington さんは書きました: > This is too complicated. Please be a little more helpful. As is, it's ambiguous. If you mean *too complicated* because there's a simpler way, explain. If you mean "too complicated* because you didn't understand, be more specific. If you mean "too complicated* because you think Mailman should provide a utility to do it to make life easier for typical admisn, we'll happily reply "file an RFE, patches welcome". ;-) if you mean *too complicated* because email sux[tm], boy, do *we* have stories! :-) And if you were just ranting, add a smiley. Email does suck, and sometimes you need to rant among the fellowship. :-) TBH, it looked pretty clean to me; it's just a long *very* precise checklist -- I'm saving it, although Mark will probably turn it into a FAQ before I do anything with it. But I'm not going to insist on that POV, I've been doing Mailman since 1997 so I'm not exactly tuned in to the typical admin POV any more. A bit warped, maybe. :-D

1 year, 11 months

[MM3-users] Re: Active archivers and archiving and thread question.

by Mark Sapiro

On 3/30/22 11:21, bob B via Mailman-users wrote: > Digging into the mailman3 world, and want to check my logic... > > We normally don't use archives, so I have "archive policy" set to "Do not archive this list" for our lists. However, the "archives" button is still there on the list info page, and if users go into it, they don't see anything, But they can click "start a new thread" which sends a message to the list, but since archiving is turned off, that message does not show up there. > Am I understanding that correctly? > > if I have "Active archivers" disabled, that hides that area from the users, correct? You need to have hyperkitty unchecked in Active archivers to prevent the Archive button from appearing on the info page. Archive policy = Do not archive this list will prevent HyperKitty from creating an archive for that list. If there is one at, e.g., https://example.com/archives/list/list@example.com/ you can delete it and Archive policy = Do not archive this list will keep it from being recreated. > Any reason why these are separated? why have an active archiver, if archiving is turned off -OR- archives are turned on, but no active archiver? They probably shouldn't be completely independent. If Archive policy = Do not archive this list, that should probably deactivate any Active archivers for the list, but arguably, one might want to temporarily stop archiving and then restart it without having to remember which archivers were active. At a minimum, setting Archive policy = Do not archive this list should probably remove the Archive button from the info 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

[MM3-users] Re: moving list from mm3 -> mm3

by Stephen J. Turnbull

Jens Günther writes: > Thanks for this advice. I did read the doc and figured out, that > PUT and PATCH for my concerns should be the right way to do it: I'm not real sure about the semantics of those verbs, but I imagine Barry did it right. > So my main question is now: does anybody know of a possibility with > this command to extract only writable attributes!? If you mean doing this so you can PUT all of those at once, I'm pretty sure it doesn't work that way. PUT creates or replaces a whole object. If there's an existing value with read-only attributes, that's not going to work. It may be possible to specify multiple values to PATCH, but that's beyond my knowledge. > Getting the config: > curl -u restadmin:restpass > localhost:8001/3.1/lists/listname.domain/config | jq > listname.domain Do you need to use curl (or anything other than Python 3) to do your work for some reason? Life is a lot easier if you use mailmanclient. > -> one has to be careful when deleting attributes, at the end of an > array, there must not be a "," (!) :-) Yeah, JSON objects are not Python dicts, no, nope, everybody's been burned before. ;-) > Just tried getting all the members: > curl -u restadmin:restpass > localhost:8001/3.1/lists/listname.domain/roster/member | jq > > listname.domain.members > > But putting them back seems to be a different thing: > curl -u restadmin:restpass -d @listname.domain.members -H "Content-Type: > application/json" -X PUT > localhost:8001/3.1/lists/listname.domain/roster/members Do you mean the difference between roster/member and roster/members? Not sure why the would be, would have to look at the source. Happy new year! Steve

1 year, 3 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Lars Schimmer

On 01/03/2021 13:15, Brian Carpenter wrote: > On 3/1/21 3:10 AM, Lars Schimmer wrote: >> If it should be a gold standard, it should mention the default setup >> of a standard debian system (which is exim4, btw) and not assuming a >> special setup debian system. > > So why don't you write up your own how-to for your so-call ''standard > debian system". Remember this is a forum for Mailman 3, not a forum for > the users of a "standard debian system". So far your comments are not > helpful at all. Install debian apt-get install mailman3-full should be the default standard way to intall on a debian way, which whould be supported. If software works around this for years, it is not really helpful for the users of the software itself. Reminds me of hugin, just doing source releases and keep the work on users to compile and make it useable. I do appreciate the mailman3 work, and I do see the less ressources. But if the debian packages only appear after I wrote the maintainers to release a mm3 package for debian (the most used package format AFAIK), it looks like someone neglect those systems. Also, if someone writes "the perfect standard way to install a softeare on debian" and neglecting the default setup of debian, it seems like it doesn't care about debian and the way people do use it at all. The default way people do setup debian is exim4 e.g. and using packages, not software beside package system and provoking failures with poackage system while using those non packages. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 1 month

[MM3-users] Re: New domain cannot set set host

by Alain D D Williams

On Wed, Nov 27, 2024 at 08:18:34PM +0000, Alain Williams wrote: > I have created a new domain - via postorius > > I want to set the 'Web Host' to be the same as the new domain but I cannot see > that domain in the drop down list. Even if I save it and then edit the domain I > still cannot see it. > > I went into mailman3-web/settings.py and added it to ALLOWED_HOSTS - no joy. > > I can see the domain in table mailman3.domain and mailman3web.django_mailman3_maildomain > > But it is not in table mailman3web.django_site > > Please how do I do this ? This is what I ended up doing using mysql - not hearing of a better way of so doing (fake domain names): use mailman3web; insert into django_site (domain,name)values('maillists.co.uk','UK maillist'); -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

4 months, 3 weeks

[MM3-users] Re: disable body transcoding

by Stephen J. Turnbull

Markus Schaaf writes: > It's not about patching. Call it what you like, but here's the story. We use somebody else's software (the Python standard library 'email' package) for operations at any level below "whole message", and it seems 'email' doesn't do what you want it to do. That implies we need code that takes over functions that are already in the package. If you want to do it, a merge request will be welcome. But it still involves changing code maintained by somebody else, and it will still require us to maintain it for some time (years), it will still likely will cause problems for users when some component is upgraded, and somebody will have to shepherd it through the Python contribution process to get things back in sync (which is what will take years, because it will not be accepted for any current versions of Python, so we will have to support it until we stop supporting Python 3.10). If someone else doesn't do it, it goes in the priority queue. I don't know how high the priority will be. Steve

3 years, 7 months

[MM3-users] Newbie hyperkitty question

by Stephen Daniel

Mailman users -- I am setting up a new mailman3 installation, and this is my first experience with the suite. All of the software is up and running, but I cannot tell if hyperkitty is actually running. When I look at my test mailing list, two archive options are available, hyperkitty and "prototype", and both are enabled. I can see that my email is being archived, but I think "prototype" is what is doing the archiving. I see that a test message will end up in /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... and nowhere else. This suggests that "prototype" is archiving, but hyperkitty is not. So, this opens up a raft of questions on hyperkitty: - How do I tell if hyperkitty is actually running? - Does hyperkitty have a web-UI for admins or users? How would I access it? - I can not find any documentation on hyperkitty, other than installation instructions and change logs. Does documentation exist? - How do I set policies on how long archives are kept? - Assuming I want to back up my archives, what do I need to back up? Thanks for your help! -- Stephen Daniel

3 years, 3 months

[MM3-users] Re: how to integrate subscription into static jekyll website

by Abhilash Raj

On Wed, Oct 17, 2018, at 10:39 AM, Hagen Bauer wrote: > Hi, > > I am running a static website with jekyll and I want to integrate a form > that executes a subription rest api call to mailman. > > From my first investigation this seems to be a bad idea from a security > perspective (rest api needs managaer access). > I agree, you should never be exposing your Mailman Core's API to Internet, because it is an administrative API. To be able to do that entirely in front-end, you may even have to expose the password in front, which is definitely not a good idea. > Is there a secure way to do this? Any other ideas? One thing you could do is have `mailto:listname-join@domain.com` URL in your site, that your subscribers can use to send an email to subscribe. You might be able to embed our web frontend in an Iframe or something, I don't have any experience doing that or am not even sure if that'll work. -- thanks, Abhilash Raj (maxking)

6 years, 6 months

[MM3-users] Re: Upgrading packages

by Mark Sapiro

On 10/13/22 10:55, Eggert Ehmke wrote: >> >> It shouldn't have been necessary to apply any patch. The head of the >> GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > > strange, I still had the line with the (not working) > from mistune.scanner import escape_html, escape_url > > maybe because the migration step was not working at that time? It should have nothing to do with migrations. The command ``` pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master ``` run as the mailman user with your venv active should have set the content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to be the same as https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer…, but it didn't. I wonder what else didn't get upgraded? Clearly it did do something because mistune was upgraded. If you run `pip freeze` in your active venv,, what versions do you see for the things you upgraded? Do they look for example like ``` HyperKitty @ git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a2… ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: how to integrate subscription into static jekyll website

by Abhilash Raj

On Wed, Oct 17, 2018, at 11:09 PM, Hagen Bauer wrote: > Has anybody tried to hide the direct api access behind a nginx reverse > proxy url? That would still need authentication right? Even behind nginx proxy. Where do you plan to keep that secret when using a static website? > > > On 10/18/18 1:19 AM, Abhilash Raj wrote: > > On Wed, Oct 17, 2018, at 10:39 AM, Hagen Bauer wrote: > >> Hi, > >> > >> I am running a static website with jekyll and I want to integrate a form > >> that executes a subription rest api call to mailman. > >> > >> From my first investigation this seems to be a bad idea from a security > >> perspective (rest api needs managaer access). > >> > > > > I agree, you should never be exposing your Mailman Core's API to Internet, because it is an administrative API. > > > > To be able to do that entirely in front-end, you may even have to expose the password in front, which is definitely not a good idea. > > > >> Is there a secure way to do this? Any other ideas? > > > > One thing you could do is have `mailto:listname-join@domain.com` URL in your site, that your subscribers can use to send an email to subscribe. > > > > You might be able to embed our web frontend in an Iframe or something, I don't have any experience doing that or am not even sure if that'll work. > > > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

6 years, 6 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by andrea.janna.unipd＠gmail.com

> However, it is unclear what in gatenews would do this. Assuming you have > no lists for which gateway_to_mail is true, all gatenews will do is > def process_lists(glock): > list_manager = getUtility(IListManager) > for mlist in list_manager.mailing_lists: > glock.refresh() > listname = mlist.fqdn_listname > if not mlist.gateway_to_mail: > continue > > The database operations involved in this are things Mailman core is > doing all the time, presumably without issues. I have no lists with "Gateway to news" option set to yes in the web interface. From the database debug log I guess that mailman gatenews abruptly terminates the database connections. For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry. 70759 Connect mailman3web@localhost on mailman3web using Socket 70759 Query SET sql_mode='STRICT_TRANS_TABLES' ... 240131 18:54:34 70759 Quit There is a "Quit" at the end. While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end.

1 year, 2 months

[MM3-users] Re: Message IDs

by Stephen J. Turnbull

Philip Colmer writes: > I'm not sure that the message ID identifies the author, does it? It does not identify any person. According to RFC 822 and all successors, it is an "author field", so third parties such as mailing lists should keep their hands off. The agent that causes a message to be sent is the "author", and it's up to them. While I am not the authoritative spokesperson for Mailman, I'm pretty good at channeling the core group, and I'm confident that the Mailman developers do not consider Mailman's role to be "authorship", even though Mailman may do things like delete attachments or HTML alternative parts, convert HTML-only messages to text/plain, and decorate messages with tags in Subject and headers and footers on the body. There are good reasons for Mailman adopting this posture. In particular, while Google does an execrable job of handling the poster's own duplicates, eliminating duplicates via mailing lists is an important use case for "Message-ID" for everybody except us list admins, who desperately want access to both copies. > I think that what Mailman 3 is doing is similar to forwarding the > email. If I forward an email, again the headers change: There are two kinds of forwards. In one, you simply *resend* the original. (This function is sometimes called "bounce", not to be confused with a refused and returned message.) In that case, the Message-ID should stay the same so that tools can identify the message. In the other, you *attach* the message to a new message. MUAs allow you to add your own text, most folks do (they're citing the message as support for something they want to say), and since they can't read your mind, the MUA or the MTA will treat it as a new message and assign a new Message-ID. On the other hand, Mailman has no intention of adding (or usually subtracting) content any more than the mailman does when they put a postmark on the envelope, so we do not consider Mailman to be an author. The idea that mailing lists should "take authorship" of posts comes up often, in many different contexts. It's almost always the case the issue that is raised is caused by other human or software agents' misbehavior. > > The IETF has addressed the issue of non-identical but equivalent > > messages with the Resent-Message-ID field (and in general the whole > > suite of Resent-* fields. > > Mailman doesn't appear to be adding that header. Would that be an > acceptable solution instead of the one I suggested above? I doubt it solves anything. I'm sure Google uses Message-ID to deduplicate. That's one of the things Message-ID is *for*, Google just does it in a way that creates maximum breakage, including for their own users. > I appreciate your view that Google is broken. I'm just trying to find > an acceptable solution to the end-user perception of "I've sent an > email to the list but I haven't received a copy back". That is going > to be a big issue/headache for us. I feel for you, but do you think that's a bigger headache than if Mailman is hacked to change the Message-ID and every CC'd subscriber starts receiving duplicates? Do you really want to punish people who use competent MUAs because others use a horrible one? Google is not just broken "in my view," it's logically broken. *Somebody* among your subscribers is going to be annoyed by whatever you do to deal with this. Note that changing Message-ID and setting all subscribers to "no dupes" is not a 100% solution to this; it means that filtering on List-* headers breaks because Mailman doesn't even send them the message, and the subscribers don't get serial numbers, tags, and footers in posts they're cc'd on. "It's broken *all the way down*." If I ever get invited on "The New Abnormal", GMail will get my FTG for this. Steve

3 years, 6 months

[MM3-users] Do you struggle with message rejected. AUP#CDRBL while using mailman with your ISP email relay?

by Philip Bondi

Hello to all: mailman3 is phenomenal upgrade from mailman2. Very nice. Thank you to the team. In our family, we use mailman to provide redundancy on important financial emails. In this manner, emails from banks, government, ecommerce or other important providers are distributed to multiple family members. And we can ask family members if they paid the credit card bill, received their delivery, saw their tax liability or refund notification, etc. Does anyone else use mailman for such a purpose? Do you struggle with "message rejected. AUP#CDRBL" while using mailman with your ISP email relay? For example, when receiving email from a Bank or the Government of Canada on a mailman2 list, sometimes my ISP would not relay the email and I would get message rejected. AUP#CDRBL On mailman2, I mitigated by stripping headers, wrapping message and DKIM signing. Here is a mailman2 message that is stripped, wrapped and signed. https://freeimage.host/i/30O5EXe Do you have this problem with your ISP with certain senders? What are your mitigation strategies on mailman3?

1 week

[MM3-users] Re: Mailman 3 localization

by Simon Hanna

> Thanks for the reply, Simon! We were thinking of using plain .po-files > too, however, we couldn't find the matching "src" folder in our > installation, do you have any more details where it or the .po-files > may also be located? What component are you talking about? For Postorius and Hyperkitty you should be able to create the files needed according to this https://docs.djangoproject.com/en/2.0/topics/i18n/translation/#message-files First run "django-admin makemessages -l de" to create the .po files and after editing "django-admin compilemessages -l de" to compile them. You should be fine doing that in your production django-project. Otherwise you can clone the frontend projects and run the commands inside the project folders. (src/postorius or hyperkitty/). I know the second option works, since that's what I'm doing (I'm deploying from the git heads) but doing that in the production projects (where manage.py is located) should generate the same files. It might generate files for dependencies as well... As for core, I only know how to translate the templates. I have no idea how the messages included in the source code should be translated.

6 years, 9 months

[MM3-users] Re: Turn off social logins?

by worik

On 10/02/19 6:20 PM, worik wrote: > How do I turn off the social logins? > > I looked in the admin manual but > > They are not working, but I absolutely do not want them for now. Maybe > one day, but my users will be allergic to even the hint.... > > Worik > A gentleman suggested offlist that... > Hi, > > You can apply in your settings.py: > > INSTALLED_APPS = ( > 'hyperkitty', > ....... > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > # 'django_mailman3.lib.auth.fedora', > # 'allauth.socialaccount.providers.openid', > # 'allauth.socialaccount.providers.github', > # 'allauth.socialaccount.providers.gitlab', > # 'allauth.socialaccount.providers.google', > # #'allauth.socialaccount.providers.facebook', > # 'allauth.socialaccount.providers.twitter', > # 'allauth.socialaccount.providers.stackexchange', > ) > > Do not comment 'allauth.socialaccount', but comment the providers > 'allauth.socialaccount.providers.google'. This worked perfectly. I am not sure why I still want to have allauth.socialaccount but I am happy for now W -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] Fix, kind of, of 'Internal Server Error'

by Alain D D Williams

I was getting several thousand error messages a day complaining about this. I would also find that the web interface would time-out/die - going away to make a cup of tea was the only things to do -- ie just wait. I am getting far fewer of these today after I tweaked by robots.txt. The problem was search engines (and maybe AI monsters) crawling the site and over loading it. The machine has 1.5GB of RAM & plenty of fast (SSD) swap. It copes well enough except when the crawlers come in. So, 2 fixes: Crawl-delay: 10 Do not visit more frequently than every 10 seconds. Google ignores this as it expects you to waste time on their search console. Disallow: /mailman3/ Do not visit at all. However if you do this then archives will not be indexed. All that I can say is: works for me, I have 1% of the errors that I had previously. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

3 months

[MM3-users] Re: The future is here?

by Abhilash Raj

On Thu, Jan 7, 2021, at 8:18 PM, Stephen J. Turnbull wrote: > Jonathan M writes: > > On 6 Jan 2021, at 04:25, Stephen J. Turnbull > <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > > > > But do be aware that you probably do have > > > to make a choice between a quagmire of options and mandating a > > > particular stack (or small set of them) for simplicity. > > > > > > It would be good if Mailman could do what Discourse do here. > > Discourse is a different kettle of fish. They concentrate on the much > more straightforward (from a network and interapp communication > configuration standpoint) web service because that's what their users > expect. Mail is a lot more baroque from that standpoint. > > We shouldn't hope to successfully "encourage" hosts to do things our > way. Eg, I run Exim4 because that's what I've always done and because > I'm familiar with its spam-filtering, performance-tuning, and security > controls: I'm not going to switch to Postfix just because that's the > most common configuration. Similar considerations apply to webserver > and RDBMS (for other people; I'm comfortable with Apache and > PostgreSQL). It's not just a matter of "tweaking the expert options". > > As far as I can see, the best we can do is what Abhilash has already > done: provide a full turnkey system in a container or a Vagrant-style > VM. But that has its issues, too. The containers are a good way to get Mailman Running, but it does require some additional setup including web servers and mta. There is scope for a lot of improvement in the container setup to be more "turnkey" and my time has been split between maintaining Mailman itself and $work that container setup hasn't gotten much attention beyond version updates for new releases. If someone familiar with Containers would like to help out, there are open issues[1] that could make lives of some people installing a bit easy. [1]: https://github.com/maxking/docker-mailman/issues > > If somebody wants to prove me wrong, feel free. But my assessment is > that there are much better uses of core developer time than chasing a > one-size-fits-all configuration. A suite of scripts or better yet > Ansible (etc) roles is a better fit for Mailman's audience, I think. > > Steve > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 3 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by maszap＠tin.it

Hi My mail.log Jul 13 01:15:12 gamelia postfix/smtpd[1973]: connect from localhost[127.0.0.1] Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia postfix/smtpd[1973]: 276C0C202B7: client=localhost[127.0.0.1] Jul 13 01:15:12 gamelia postfix/cleanup[1975]: 276C0C202B7: message-id=<20200712231512.1546.30031(a)mail.pratico.work> Jul 13 01:15:12 gamelia opendkim[726]: 276C0C202B7: DKIM-Signature field added (s=mail2020, d=pratico.work) Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: from=<admin(a)pratico.work>, size=586, nrcpt=2 (queue active) Jul 13 01:15:12 gamelia postfix/smtpd[1973]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Jul 13 01:15:12 gamelia postfix/smtpd[1978]: connect from localhost[127.0.0.1] Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia postfix/smtpd[1978]: C3A57C20D52: client=localhost[127.0.0.1] Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia postfix/cleanup[1975]: C3A57C20D52: message-id=<20200712231512.1546.30031(a)mail.pratico.work> Jul 13 01:15:12 gamelia opendkim[726]: C3A57C20D52: DKIM-Signature field added (s=mail2020, d=pratico.work) Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: from=<admin(a)pratico.work>, size=1610, nrcpt=2 (queue active) Jul 13 01:15:12 gamelia postfix/smtpd[1978]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains Jul 13 01:15:12 gamelia amavis[1566]: (01566-01) Passed CLEAN {RelayedInbound}, [127.0.0.1]:36322 <admin(a)pratico.work> -> <admin(a)pratico.work>,<info@pratico$ Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<admin(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, $ Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<info(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, d$ Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: removed Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Connect from local Jul 13 01:15:12 gamelia dovecot: lmtp(admin(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored $ Jul 13 01:15:12 gamelia dovecot: lmtp(info(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg:2>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored$ Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<admin(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.0$ Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<info(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.01$ Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: removed Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Disconnect from local: Client has quit the connection (state=READY) Jul 13 01:15:16 gamelia dovecot: imap-login: Login: user=<admin(a)pratico.work>, method=PLAIN, rip=173.249.18.220, lip=173.249.18.220, mpid=1983, TLS, session$ Jul 13 01:15:16 gamelia dovecot: imap(admin(a)pratico.work)<1983><IiFCv0aqJoyt+RLc>: Logged out in=297 out=5915 deleted=0 expunged=0 trashed=0 hdr_count=11 hd$ sudo mailman conf -s logging.smtp [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes

4 years, 9 months

[MM3-users] Re: Change Base URI for Mailman 3.1

by Abhilash Raj

Hi, On Thu, Sep 21, 2017, at 08:22 AM, Dmitry Makovey wrote: > I'm tinkering with docker container of mailman 3.1 however I'm trying to > utilize existing nginx server thus I need to map "/mailman" to > mailman-web docker container vs default "/" mapping. Where do I > configure base URI for mailman-web ? There are two ways to do this, 1. This works right now with existing images on my test server but is an ugly hack (as-per uwsgi docs[1]). Your Nginx configuration would look something like this: location /mailman3/ { # First attempt to serve request as file, then uwsgi_pass 172.19.199.3:8080; include uwsgi_params; uwsgi_read_timeout 300; uwsgi_param SCRIPT_NAME /mailman3; uwsgi_modifier1 30; } SCRIPT_NAME *should* work by itself acc to uwsgi specs, but "uwsgi_modifier1 30" makes it work with some magic I haven't yet dug up on. 2. The correct way to do it would be to modify the uwsgi configuration to "mount" the wsgi application at a particular url prefix. uwsgi would then take care of re-writing the urls based on SCRIPT_NAME variable. mount = /mailman3=wsgi.py ; rewrite SCRIPT_NAME and PATH_INFO accordingly manage-script-name = true This the relevant configuration required in `uwsgi.ini`[2] for it to work. The only problem right now is there is no way to change uwsgi.ini script easily without tinkering with the image itself. There is an issue open to fix this problem though[3]. Lastly, a 3rd option would involve changing the urls.py[4] to make Django do the work instead of uwsgi or nginx. It would require you to change the file and re-build the image yourself. I wouldn't suggest doing that though. Hope that helps! thanks, Abhilash [1]: http://uwsgi-docs.readthedocs.io/en/latest/Nginx.html#hosting-multiple-apps… [2]: https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/uwsgi… [3]: https://github.com/maxking/docker-mailman/issues/62 [4]: https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/urls.… -- Abhilash Raj maxking(a)asynchronous.in

7 years, 7 months

[MM3-users] Re: Mailman import of 2000 lists

by Abhilash Raj

On Thu, Oct 7, 2021, at 11:23 AM, dancab(a)caltech.edu wrote: > I'm working on importing nearly 2000 lists and have been doing some > testing prior to migrating from Mailman2. > > I'm using the mailman create command via for loop. It takes quite a > while to do all the work including updating MySQL and re-generating the > LMTP files for each list. As the number of lists increases the process > gets slower. > > Do you have any recommendations for speeding up this process? I am > running the system in AWS using EFS for storage of the LMTP files. There isn't a way to disable creation of LMTP files, but if this instance you are running on isn't live, then you can configure Mailman with NullMTA so it won't try to generate LMTP files. [mta] # NullMTA is just implementing the interface and thus satisfying Mailman # without doing anything fancy outgoing: mailman.mta.null.NullMTA You need to add ^ to mailman.cfg, commenting out the _real_ outgoing MTA configuration. Once you are done with the migration, you can configure the right MTA and run `mailman aliases` command to generate them. -- thanks, Abhilash Raj (maxking)

3 years, 6 months

[MM3-users] About to Install MM3 -- Seeking clarification

by Onyeibo Oku

Good Morning Everyone, I installed and managed mailman 2 for about two years. I am now ready to try Mailman 3. The documentation for version 2 was lucid and this forum was quite helpful in the past. Now I'd like to proceed with installating MM3 but I doubt my understanding of the docs. It seems to assume that users will know what to do. Okay, don't laugh! I just want to be sure what I am doing. Does the following sequence resemble the proper steps? 1. Download the source from a git repo (I understood that one) 2. Create a virtual environment (venv perhaps ... not stated explicitly) 3. activate the virtual environment 4. from the git project root, run: ./mailman start I know, its stupid. I had to ask. It would really build my confidence someone would confirm the above steps or counter then with something very explicit. What about process ownership? Do I need to have a unix mailman user? What else do I need to get mailman up and running before proceeding to configuration. Ahaa! I perused the config docs a bit. Where can I find the .cfg file? I hope these questions are not too annoying. Regards Onyeibo

2 years, 6 months

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Mark Sapiro

On 10/28/24 18:33, Bill Oliver wrote: > > Aha, I thought. I should have changed that. Then I noticed that I > didn't even have a mailman-hyperkitty.cfg file, and I can't find > mention of it in the venv instructions. I *have* installed mailman- > hyperkitty during the "pip install mailman-web mailman-hyperkitty" > step. I did a "find" on /opt/mailman, and it doesn't seem the file is > there at all. > > Do I need this file? Yes. See the last part of the section at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it says in part `And, create the /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: ...` > I found a template here: > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… > > > Do I need to copy and paste that in my installation? It, or something as mentioned in the above doc needs to be at the location defined in the `configuration:` setting in the `[archiver.hyperkitty]` section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Hyperkitty_import.py Error

by Mark Sapiro

On 2/7/21 10:03 AM, Brian Carpenter wrote: > I am trying to import some old archives (going back to 2003) into a > Mailman 3 list. The import job is terminating very early in the process > with the following error: > > IndexError: string index out of range > > 1. Is there a way to fix a mbox file that is generating this type of error? Yes, but you need to understand what message is causing the error and why. The full traceback from the error can help. So can the script at <https://www.msapiro.net/scripts/check_hk_import>. > 2. If a message is causing this error, is there a way to import the rest > of the mbox file by importing messages after a certain date within the > mbox file? I know the --since flag should be able to do that but I am > unsure what the date/time format should be. There are things you can do. The --since date syntax is very flexible. It uses dateutil.parser.parse. See <https://dateutil.readthedocs.io/en/stable/parser.html#module-dateutil.parser> You can also just make a new mbox which deletes the messages up to and including the offending one or just delete/fix the offending message. hyperkitty_import won't re-import message that are already in the archive, and without a --since option won't import messages older than the newest in the existing archive. > 3. The --no-sync--mailman flag indicates the possibility of doing batch > imports. What are batch imports and how do you do them? Batch imports means running hyperkitty_import multiple times wiuth multiple mbox inputs (batches). It is only necessary to run the sync_mailman job once after all the imports are done (even if importing to multiple lists). I.e. specify --no-sync--mailman on all but the last import, or on all and then run sync_mailman after done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Outgoing STMP services? IP reputations?

by Torge Riedel

Am 03.04.20 um 21:03 schrieb Seth Seeger: > Do you use an SMTP relay service? > Do you just send directly from your VM’s IP address? > Do you have trouble with getting black listed? > What have you done about your IP address reputation? > Is DKIM and SPF enough to get past an IP address without an established reputation? Hi Seth, I am maintaining a mailman3 installation where just few mails are processed per week. It is hosted on its own VM with postfix as SMTP service with DKIM and SPF, so mails are sent from the VM's IP address. I had several issues when starting the mail services with lots of mails getting refused and poor reputation. But looking at the logs most of the well-known mail hosters give information why they deny mails from your server and what can be done to fix it. It is then "just" work to do and some mails to admins to white list your IP oder reset reputation for your IP. After 5 days all went well. I propose to test your mail setup with online tools, there are a lot of them around in the net and they are free. Kind regards Torge

5 years

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Eggert Ehmke

Hello Onyeibo, nobody is laughing here! If your server runs a Debian/Ubuntu like OS, this guide is really helpful: https://docs.mailman3.org/en/latest/install/virtualenv.html[1] I used it to set up my mailman3, and it worked quite well. If you have Apache instead of Nginx (like me), you must do some modifications for that. Cheers, Eggert Am Mittwoch, 12. Oktober 2022, 10:24:29 CEST schrieb Onyeibo Oku: > Good Morning Everyone, > > I installed and managed mailman 2 for about two years. I am now > ready to try Mailman 3. The documentation for version 2 was lucid and > this forum was quite helpful in the past. > > Now I'd like to proceed with installating MM3 but I doubt my > understanding of the docs. It seems to assume that users will know what > to do. > > Okay, don't laugh! I just want to be sure what I am doing. Does the > following sequence resemble the proper steps? > > > 1. Download the source from a git repo (I understood that one) > 2. Create a virtual environment (venv perhaps ... not stated explicitly) > 3. activate the virtual environment > 4. from the git project root, run: ./mailman start > > I know, its stupid. I had to ask. It would really build my confidence > someone would confirm the above steps or counter then with something > very explicit. What about process ownership? Do I need to have a unix > mailman user? What else do I need to get mailman up and running > before proceeding to configuration. Ahaa! I perused the config docs a > bit. Where can I find the .cfg file? > > I hope these questions are not too annoying. > > Regards > Onyeibo > _______________________________________________ > 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/ -------- [1] https://docs.mailman3.org/en/latest/install/virtualenv.html

2 years, 6 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 05/18/2018 03:50 AM, Henrik Rasmussen wrote: > > What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. Setting the policy to Confirm or Confirm, then Moderate will do that as long as admins don't use the mass subscribe feature without a confirmed request from the user. > Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Manually. I.e.post a request to the list with a deadline for response and remove those that don't respond. Or, post to the list that everyone will need to resubscribe and then remove everyone. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Discard all mail with the subject "The resutls of your email commands"

by Mark Sapiro

On 9/25/20 1:16 AM, w.schoener(a)alp.dillingen.de wrote: > Hello, > I am using mailman 3.2.1 for several mailing lists. My colleagues want me to stop all mails with the subject "The results of your email commands". > I found some contributions here, but nowhere a solution for this question. > Does anybody has any suggestion? > Maybe I could try to handle this outside of mailman, but then I would have to pass this task on to someone I dont know .... :-( > Thanks for all hints. :-) Doing it in the MTA, even though you don't want to, may be best as, with postfix for example, you can do it with header_checks. To do it in Mailman 3, patch mailman/runners/command.py and comment out or remove the last line ``` reply.send(mlist) ``` Are you really sure you want to do this at all. It means for example that one can't get a response to a `help` or the new `who` command among others sent to the -request address. -- 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: Problem with languages

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210319 15:58]: > You think it's ok to install from testing? I have already the > bullseye-package with a lower preference then the stable ones, so I > could do so, advertises version 3.3.3 there ... but always try to > stick with stable packages :-) never know. With the backports I > often do go along, but never know what testing does, when you start > with a mixed system... Well, I personally wouldn't be so afraid, but that might come from the fact that I know the debian ecosystem way too well :) If all in all the stable package works for you, I would always recommend to stick with the stable version. If not, the testing version could be an option. As disclaimer, I'm using the version from git, but I decided so because I expected that I need to change code and that's easier from the git version. Other people here have other recommendations (i.e. always recommend to work with the git versions), but that's the usual differences. In the end, please just use what fits best for you. > If so, do you know how to do to install all needed dependencies > correctly!? 'apt install mailman3-full -t bullseye' shouldn't be all > of it, no!? Without having it tried myself, that should do the trick. > >Also, translations had been the reason for some discussions lately, so > >this is still some work-in-progress. (Also on the git version I'm > >using, there are more texts in English than I'd wish for.) > > What I hear is that this is a common issue and I probably should get > along with it for now!? Well, let's say: some important fixes had been made in the git tree recently (but I forgot if before or after the latest release), so situation should improve sooner or later. mailman3 is under active development, which has both the advantage and disadvantage that things are changing. Andi

4 years, 1 month

[MM3-users] Re: How do you remove the Hold on all non-member forwarded emails?

by Mark Sapiro

On 5/26/23 12:38 PM, Sean Westfall wrote: > > But I am having trouble using one of its configurations. I configured my mailmain3 instance to accept all non-member emails, as I want all emails that are sent to the mailman client to go to all subscribers without having it held for moderation -- I did this by setting this setting: > > https://i.imgur.com/PGzaD0k.png > > Action to take for postings from non-members for which no explicit action is defined. (Details for generic_nonmember_action) -> "Accept" That screen shot and language is from Mailman 2.1, not Mailman 3. > But this doesn't work for forwarded emails. Even if the email address that is being forwarded from is included in the "List of non-member addresses whose postings should be automatically accepted." > > I noticed that all emails that are forwarded to the mailing list are always held for moderation -- though this isn't the case for email that are sent to the mailing list directly. But I want it so that emails that are even forwarded to my mailman mailing list don't get held in moderation. > > How do I set mailman to do this? I was thinking if there is no way to configure this easily then I might have to do this from the code, which means I might have to ask on the developer mailing list -- or I have to go with an entirely different solution (using something other than mailman3). Please clarify whether you are using Mailman 2.1 or Mailman 3. There should be no difference between a message sent directly vs. a forwarded message. What is the reason given for why the message is held? Also, the appropriate list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Mailman messages are getting a TAG in some email clients.....how????

by Guillermo Hernandez (Oldno7)

El 12/9/23 a las 19:43, Mark Sapiro escribió: > On 9/12/23 8:51 AM, bob B via Mailman-users wrote: >> So I know about the setting "Anonymous list" but regardless of that >> setting some email clients put the list name in [] when it displays >> messages in your inbox. Does anyone know how email clients are doing >> this? I have users who email clients do not do this, and was >> wondering if it is a setting in their client or just not possible. > > > This looks like Mailman adding 'Subject prefix', so all list mail will > have this prefix added to the Subject:. So the question isn't how mail > clients are adding it, but rather why do some mail clients suppress it. I think the simple answer is that some mobile mail clients don't show the subject line by default, you have to click to show it explicitely. That users just don't see that. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

1 year, 7 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mohsen Masoudfar

Sorry, I found it! Thanks Mohsen -----Original Message----- From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, December 28, 2022 2:49 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] Thank you Mark for your help. I see fedora under Django administration: Home > Social Accounts > Social Accounts as a provider listed, but we do not use it and I would like to remove it. So far I did not find a way to delete it. We do not need Hyper Kitty either, because we do not archive any emails. I appreciate if you could point me how I may delete Fedora as a provider. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, December 27, 2022 4:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdjango-al… -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org

2 years, 3 months

[MM3-users] Re: Customise Postorius templates?

by Abhilash Raj

> On Feb 7, 2022, at 4:35 AM, Duane Raymond <duane(a)fairsay.com> wrote: > > On Mon, 7 Feb 2022 at 00:56, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >>> On Feb 1, 2022, at 11:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> On 2/1/22 09:47, Duane Raymond wrote: >>>> Hi, >>>> I'm looking to do some radical customisation of the Postorius (and >> Hyperkitty) templates over the next 6 ish months and was wondering if there >> is a 'best practice' way to do this that will survive updates to MM3. I've >> searched around and not found much and also tested copying >>>> >> venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html >>>> to >>>> var/templates/lists/summary.html >>>> As suggested in some posts - but it didn't seem to pick up the >> customisation - only customisations in the venv path worked - and they get >> overwritten on update. > > >> The best way to do this would be utilize Django’s template loader. See >> here[1] for the documentation on how you can do this. You want to put the >> path where you are putting the templates under `DIRS` option of the >> `TEMPLATES` section. >> >> Do make sure that you are keeping the directory structure correct so that >> Django can discover them. Like, Hyperkitty’s base.html should be in >> `/custom/path/hyperkitty/base.html`, where `/custom/path` is what you’ve >> setup in DIRS setting above. >> > I hadn’t tried it when I sent email, but when I tried it locally on Postorius, it seems to work for me. > This looks promising! I've not got it working yet, but this is what I've > tried: > > 1. Created folder 'custom' in the mm root (in my case: /opt/mailman/mm/) > 2. Copied the files and folders from postorius/templates/postorius/* and > hyperkitty/templates/hyperkitty/* to the custom/ folder (not the > full postorius/templates/postorius/ match, just evening in the > second postorius/ dirrectory) Note that you want to copy from “src/postorius/templates” directory to your "/opt/mailman/mm/custom” directory. It is important that you retain the “postorius” and “hyperkitty” directories. Here is what I have in my settings.py: - 'DIRS': [], + 'DIRS': ['/Users/maxking/Documents/mm3/postorius/example_project/templates’], And here is the structure of the templates directory you are seeing above: $ tree /Users/maxking/Documents/mm3/postorius/example_project/templates /Users/maxking/Documents/mm3/postorius/example_project/templates └── postorius └── lists └── summary.html Note that I am only overriding the Summary page here. > 3. Recursive update of permissions of the custom/ folder and files to be > mailman > 4. Updated /opt/mailman/mm/settings.py by changing "'DIRS': []" > to "'DIRS': [BASE_DIR, '/custom/']" in the "TEMPLATES =" section Note that you don’t want [“BASE_DIR”, “/custom/“] here, the comma is the wrong value here. The docs I mentioned have a “/“. Although, it is possible that even “/“ since that needs BASE_DIR to be a Path datatype and not string. Easiest thing with least surprise would be to use the full path, atleast to ensure that template discovery works as expected. > 5. Edited the original AND copied postorius/lists/summary.html to have a > small change in the footer of each so I know what version it is serving Since I was running a dev server, it doesn’t need restart, but simply restarting gunicorn should should do it. You don’t need to restart anything else. > 6. Restarted: gunicorn qcluster mailman nginx and cleared browser cache > 7. Reloaded the 'info' page of a few lists to see which version ti was > serving > > Variants: I've also changed the DIRS value to the hard-coded path: > /opt/mailman/mm/custom > > Result: it is still serving the default/original Postorius template vs the > custom one. > > Any suggestions for things I should do to make it use the /custom/ folder > instead? Any recompiling or other actions beyond just restarting? (I > probably don't need to restart qcluster and maybe not even mailman core for > this to take effect but I do it just in case!) Hope that helps. -- thanks, Abhilash Raj (maxking)

3 years, 2 months

[MM3-users] Re: Python is updated

by Stephen J Turnbull

Odhiambo Washington writes: > Imagine you were running PHP code and you automatically upgraded > from PHP7 to PHP8! Chances are high that all your PHP applications > will be broken in the process. You ALWAYS need to review all the > software for compatibility (with your code & configs) before you do > an upgrade. My pattern is different. I have the advantage that my usages are seasonal, eg, Mediawiki is online October 1 to January 15. Especially with PHP applications, I generally just do it and let it break. A lot of the major apps (Mediawiki!) are quite secure. But minor ones and 3rd party extensions ... there are so many ways to shoot yourself in the foot in all the inject-code-from-the-console P-languages, and PHP has a worse record than most. Staying up to date is worthwhile to me. So PHP and Mediawiki I update in early September, test the features we use, fix things up, and ready to go October 1. Few businesses can do that. Universities and ski areas, I guess. :-) But if you can do it, it may be a reasonable workflow. Steve -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

1 year, 11 months

[MM3-users] Re: Mailman issues after re-boot

by Stephen J. Turnbull

paulrubin37(a)gmail.com writes: > I went the through the rest of the install got the login screen and > after logging in I get this: > > Forbidden (403) > CSRF verification failed. Request aborted. This is a webserver vulnerability mitigation, and I'm seeing the same HTTP statis on mailman3.org when I go to moderate these lists. I suspect a Django bug (or barely possible, change in Django's configuration that we need to update to). But I don't know for sure what's going on there. Pretty sure it's nothing you did wrong though. > Looking at the PostgreSQL db, the user table has certainly been > emptied the only user is mailman. Is that 'user' table in the 'mailman' database? Or is that Postgres's own user table? If the latter, mailman is probably the only user authenticated by Postgres (for other users including the 'postgres' database superuser, Postgres delegates to Unix login authentication). Since you can't get to Django for the moment, if you activate the venv and type "mailman lists", do you see all your lists? If you then type "mailman members LIST" for some list, do you see all the members? > The UID, address and mailing list tables seem to contain many > records. I am not sure how much to restore of the original DB? > Short of doing a diff on two backup file do you have any insight? Why do you think that your database has been corrupted? Does Postgres complain about inconsistencies? You would hope that you lost only transactions in progress at the time of the crash, and the database is internally consistent. If it has been corrupted, you probably should restore the whole thing from the backup, but that would lose any changes committed to the database between the backup and the crash. If any of the mailman information commands above seem to give wrong information, or worse errors, then you probably need to restore the whole thing. But I suspect the database is intact.

1 year, 6 months

[MM3-users] Re: Syncing Real Name between user account and membership

by Abhilash Raj

On Sat, Dec 19, 2020, at 6:55 PM, Andreas Barth wrote: > * Abhilash Raj (maxking(a)asynchronous.in) [201219 06:28]: > > I am just wondering if Core's API should do this (probably not by > > default, but with a bool parameter that P can use every time), or > > should we iterate over all addresses and PATCH the display names in > > them (would be slower, with multiple API requests). > > > > I am leaning towards the first option. What do you think? > > I agree to that. > > > > Also, I'm just trying to do a small sync script for the moment (using > mailman release 3.3.2) > for user in client.users: > if not user.display_name: continue > for address in user.addresses: > if address.display_name == user.display_name: continue > address.display_name = user.display_name > address.save() > and getting the response > urllib.error.HTTPError: HTTP Error 405: > > Also the server side log doesn't tell me more: > [19/Dec/2020:14:00:00 +0100] "PATCH /3.1/addresses/aba(a)ayous.org > HTTP/1.1" 405 0 "-" "GNU Mailman REST client v3.3.2" > > Any hint what I'm doing wrong here? Currently released versions doesn't allow updating Address's display_name (which is the only editable attribute, hence 405 PATCH method not allowed error). This is something that I fixed 3 days back, so it will only be available by next release. You can iterate over the Users and their addresses in `mailman shell` as well: ``` >>> from mailman.interfaces.usermanager import IUserManager >>> from zope.component import getUtility >>> user_manager = getUtility(IUserManager) >>> for user in user_manager.users: ... for address in user.addresses: ... address.display_name = user.display_name ... >>> commit() ``` This should do the same thing you mentioned above I think. > > > Regards, > Andi > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/23/22 07:41, Josef Dietl wrote: >> >> The issue here is accessing the hyperkitty API. The base URL for these >> accesses is configured in mailman-hyperkitty.cfg. From what I see here, >> that is something like `http(s)://host.example.com/hyperkitty/` If you >> append `api/` to that base URL and go there in a web browser do you get >> a page of documentation of the HyperKitty API? If so, then figure out >> why it works from a web browser and not when Mailman core does it. If >> you get the 403, figure out why. This is probably an nginx issue. > > Seems like an nginx issue indeed. However, I'm an apache guy, trying to re-educate myself on nginx. > OK, here's the result of changing mailman-hyperkitty.cfg from `http(s)://host.example.com/hyperkitty/` to `http(s)://host.example.com/hyperkitty/api/` Do not make this change in mailman-hyperkitty.cfg. That will produce 404's for sure. This was only a suggestion to try from a browser. > Yes, if I open things from the web browser, I do get the HyperKitty API doc. OK. That means you can access HyperKitty's API from a browser at `http(s)://host.example.com/hyperkitty/api/`. This is the same thing Mailman core is doing if `base_url` is set to `http(s)://host.example.com/hyperkitty/`, so what's the difference between Mailman core's access via mailman-hyperkitty and your's via the web browser. For further diagnosis, you might try `wget -O- http(s)://host.example.com/hyperkitty/api/` on the Mailman server. > With what follows below, I guess it's a timeout: Processing a message takes longer than rendering a HTML document. > > Jan 22 20:26:27 2022 (149435) ACCEPT: > <AM0PR04MB4785365CA1BB735884E149CEC25C9(a)AM0PR04MB4785.eurprd04.prod.outlook.com> > Jan 22 20:26:28 2022 (149439) HyperKitty failure on https://[FQDN]/hyperkitty/api/api/mailman/urls: Do not include the api/ in base_url. That was just for testing with a web browser or wget/curl. -- 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: SMTPNotSupportedError when requesting new password

by Odhiambo Washington

On Wed, Dec 21, 2022 at 4:04 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > I get this error when a user tries to use the "forgot password" function > in hyperkitty. > Obviously the exception is thrown when the send_mail function is called in > > /opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py > > > In settings.py I have: > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = 'valid email' > EMAIL_HOST_PASSWORD = 'valid password' > > What can I do to debug further? > Is it necessary to have the authentication details when communicating with localhost? Most MTAs do not require ASMTP on port 25 because that port is meant for MTA-to-MTA communication usually. If you must use authentication, please configure it on a different port (like 587) and ensure you only advertise for ASMTP on that port. For now, just comment out the EMAIL_HOST_USER and EMAIL_HOST_PASSWORD and restart whatever needs to be restarted and all shall be okay. I suspect that you do not advertise AUTH to localhost, and neither do you (or should you) enforce auth on port 25. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: how to integrate subscription into static jekyll website

by Hagen Bauer

Has anybody tried to hide the direct api access behind a nginx reverse proxy url? On 10/18/18 1:19 AM, Abhilash Raj wrote: > On Wed, Oct 17, 2018, at 10:39 AM, Hagen Bauer wrote: >> Hi, >> >> I am running a static website with jekyll and I want to integrate a form >> that executes a subription rest api call to mailman. >> >> From my first investigation this seems to be a bad idea from a security >> perspective (rest api needs managaer access). >> > > I agree, you should never be exposing your Mailman Core's API to Internet, because it is an administrative API. > > To be able to do that entirely in front-end, you may even have to expose the password in front, which is definitely not a good idea. > >> Is there a secure way to do this? Any other ideas? > > One thing you could do is have `mailto:listname-join@domain.com` URL in your site, that your subscribers can use to send an email to subscribe. > > You might be able to embed our web frontend in an Iframe or something, I don't have any experience doing that or am not even sure if that'll work. >

6 years, 6 months

[MM3-users] Re: Newbie hyperkitty question

by Stephen Daniel

Thanks. Very helpful. On Tue, Jan 11, 2022 at 2:03 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/11/22 8:27 AM, Stephen Daniel wrote: > > Mailman users -- > > > > I am setting up a new mailman3 installation, and this is my first > > experience with the suite. All of the software is up and running, but I > > cannot tell if hyperkitty is actually running. > > > In Postorius, in the list's `info` view can you click the Archives > button and see archived messages? That's HyperKitty. > > If the messages aren't there with the hyperkitty archiving option > enabled, check `mailman.log` for why. > > Also do messages from the list have an Archived-At: header? > > > > When I look at my test mailing list, two archive options are available, > > hyperkitty and "prototype", and both are enabled. I can see that my > email > > is being archived, but I think "prototype" is what is doing the > archiving. > > I see that a test message will end up in > > > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > > and nowhere else. This suggests that "prototype" is archiving, but > > hyperkitty is not. > > > No this says the prototype archiver is working. It says nothing about > Hyperkitty. > > > > So, this opens up a raft of questions on hyperkitty: > > > David Newman has answered some of this, but ... > > > > - How do I tell if hyperkitty is actually running? > > > It doesn't actually run. it is a Django web UI and a web API that serves > things on request. > > > > - Does hyperkitty have a web-UI for admins or users? How would I > access > > it? > > See above. > > > > - I can not find any documentation on hyperkitty, other than > > installation instructions and change logs. Does documentation exist? > > No, not really. > > > > - How do I set policies on how long archives are kept? > > - Assuming I want to back up my archives, what do I need to back up? > > > Messages are kept forever unless you do something to delete them. > HyperKitty's messages are stored in the database configured in the > DATABASES setting in your Django settings. How you backup the database > depends on the database manager. You already found the prototype > archiver's messages. > > > -- > 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/ >

3 years, 3 months

[MM3-users] Re: A short link to this page -- TinyURL

by Simon Hanna

On 03/11/2018 04:56 PM, John Griessen wrote: > The wiki page has a convenient TinyURL. > > Is it feasible to make TinyURLs for archived list threads such as: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Yes, and it's rather easy to do. You would have to do minimal modifications to Hyperkitty to get it. Here is an open issue about that https://gitlab.com/mailman/hyperkitty/issues/60 Gitlab is having an issue with the comments, but in short you would have to do the following: Each object has a pk which is an integer by default. You would add a view with a url like "/archives/shortlink/<int>" and make the view fetch the message and redirect to the existing view. You will probably also want to include the ability of getting these links by changing the templates to include this link. I would recommend either replacing the exiting permalink or adding a new shortlink option. If you of course want something other than integers, you would have to implement a little more... I'm not sure if it is an option to include that in hyperkitty by default, or if you would have to do the modifications yourself. The issue is rather old and I'm not sure what the outcome of the discussion was...

7 years, 1 month

[MM3-users] Re: Dump/restore users (with passwords) via API

by Abhilash Raj

On Tue, Sep 18, 2018, at 9:19 AM, Dmitry Makovey wrote: > On 09/17/2018 12:39 PM, Abhilash Raj wrote: > > On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: > >> We are trying to dump/restore users using API calls and it seems > >> that API allows us to dump password hashes (a good thing), but then > >> API does not allow to insert users back using saved password hashes > >> - only cleartext passwords. > > > > I'd say that is intentional. You don't want people to be setting up > > hashes as passwords. > > > >> Aside from create_user is there any other way to create > >> users/change their password? > > > > Not that I know of, not using the API atleast. You could potentially > > use the low level API that inserts records in the database or use SQL > > to dump and restore that data. > > > > What do you use the Core's user/password for? Currently, the user > > passwords are basically just a carry-over from Mailman2 and there > > shouldn't be any use for it. I have been considering removing that > > completely have Postorius do all the authentication/authorization. > > > > Email based authentication should rely on more reliable identities > > like email signatures, intead of having to send cleartext passwords > > over email. > > I think I am asking about the username/password auth for postorious and > how to dump/restore it. At present we have no tools for dump/restoring > users so that's what we're trying to build. Ah, why not take a database dump? There are a few specific tables that you can dump to get everything? We don't have a way to do that because we do not actually do not handle auth ourselves, but instead delegate it to allauth library. You may have to dig into internals of that to be able to fetch/restore users/passwords. -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marc SCHAEFER

Hello, On Mon, May 27, 2024 at 06:00:15AM -0000, marcus--- via Mailman-users wrote: > Thank you for your solution. I assumed that Debian actually creates the most > important packages and configurations with the installation via the packages. Here is how I automatically install and migrate data (still testing, seems to work quite well so far) on Debian bookworm. A few things are missing from the script for clarity (it gets munin & logcheck monitoring, notably). It assumes a few things in a templates/ directory. I have a few aliases (such as services_*), but you get the idea. Some stuff could be configured via debconf preseeding, but I didn't do it that way. #! /bin/bash set -e services_install postfix (while read line do case $line in *=*) postconf -e "$line";; *) echo "TOSSING: $line" >&2;; esac done) <<EOF myhostname = $lists mydestination = $lists mynetworks = 127.0.0.0/8 inet_protocols = ipv4 inet_interfaces = all transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains EOF services_do restart postfix djangoauth=($(egrep '^djangosuperuser\s' templates/passwords/pw)) psqlauth=($(egrep '^psql\s' templates/passwords/pw)) rm -f templates/passwords/pw services_install dbconfig-pgsql cat > /etc/dbconfig-common/mailman3.conf <<EOF dbc_install='true' dbc_upgrade='true' dbc_remove='false' dbc_dbtype='pgsql' dbc_dbuser='${psqlauth[1]}' dbc_dbpass='${psqlauth[2]}' dbc_dbserver='ds-services-psql' dbc_dbname='mailman' dbc_dbadmin='postgres' EOF sed < /etc/dbconfig-common/mailman3.conf \ > /etc/dbconfig-common/mailman3-web.conf \ "s/^dbc_dbname=.*/dbc_dbname='mailmanweb'/" chmod 600 /etc/dbconfig-common/mailman3.conf \ /etc/dbconfig-common/mailman3-web.conf services_install mailman3-full mailman3-web sed --in-place "s/^site_owner: .*/site_owner: ${djangoauth[1]}/" \ /etc/mailman3/mailman.cfg # work-around: SQLAlchemy no longer supports "postgres" sed --in-place "s%^url: postgres://%url: postgresql://%" \ /etc/mailman3/mailman.cfg sed --in-place "s/.*'Mailman Suite Admin', 'root@localhost').*/('Mailman Suite Admin', '${djangoauth[1]}'),/;s/^EMAILNAME\s*=.*/EMAILNAME = '$lists'/" /etc/mailman3/mailman-web.py # aliases mailman <-> postfix mkdir -p /var/lib/mailman3/data chown list:list /var/lib/mailman3/data for i in postfix_lmtp postfix_lmtp postfix_domains do touch /var/lib/mailman3/data/$i postmap /var/lib/mailman3/data/$i done chown list:list /var/lib/mailman3/data/postfix_* services_do restart postfix service_enable postfix services_install apache2 ln -s /etc/mailman3/apache.conf /etc/apache2/conf-available/mailman3.conf a2enconf mailman3 a2enmod proxy_uwsgi service_enable apache2 services_do restart apache2 service_enable mailman3-web services_do restart mailman3-web # fix example.com PGPASSWORD=${psqlauth[2]} psql -h ds-services-psql -U ${psqlauth[1]} mailmanweb -c "UPDATE django_site SET domain = '$lists', name = '$lists' WHERE id = 1" # workaround required? #chgrp list /var/lib/mailman3/locks/ #chmod g+rwx /var/lib/mailman3/locks/ chgrp list /var/log/mailman3/*.log mailman-wrapper info env DJANGO_SUPERUSER_PASSWORD=${djangoauth[3]} \ DJANGO_SUPERUSER_USERNAME=${djangoauth[2]} \ DJANGO_SUPERUSER_EMAIL=${djangoauth[1]} \ mailman-web createsuperuser --noinput \ || echo "django super user already exists in DB, ignored" services_do restart mailman3 if [ 0 = 0 ]; then # permissions on ~user are restrictive mkdir /tmp/mailman cp -a templates/lists /tmp/mailman/lists # to be generated with: scripts/get_ml.sh for i in /tmp/mailman/lists/*.pck do l=${i/*\/} l=${l/.pck} mailman-wrapper remove $l@$lists || echo "list $l does not yet exist, ignoring rm" mailman-wrapper create $l@$lists mailman-wrapper import21 --charset iso8859-1 $l@$lists $i done # not doing that yet if [ 0 = 1 ]; then for i in /tmp/mailman/lists/*.members do l=${i/*\/} l=${l/.members} mailman-wrapper --no-welcome-msg addmembers $i $l@$lists done else echo schaefer(a)horus.ch | mailman-wrapper addmembers - $l@$lists fi for i in /tmp/mailman/lists/*.mbox do l=${i/*\/} l=${l/.mbox} /usr/share/mailman3-web/manage.py hyperkitty_import \ -l $l@$lists $i done rm -rf /tmp/mailman /usr/share/mailman3-web/manage.py update_index else # simple test mailman-wrapper create --notify --owner schaefer(a)alphanet.ch mailman-admins@$lists echo schaefer(a)horus.ch | mailman-wrapper addmembers - mailman-admins@$lists fi

10 months, 4 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I read the doc and it says that when the DEBUG var is set to False we should do these commands: django-admin collectstatic --pythonpath example_project --settings settings django-admin compress --pythonpath example_project --settings settings I did the first one and got this: (env2) [mailman@localhost mailman-suite]$ pwd /var/lib/mailman/mailman-suite (env2) [mailman@localhost mailman-suite]$ django-admin collectstatic --pythonpath mailman-suite_project --settings settings You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/var/lib/mailman/mailman-suite/mailman-suite_project/static', 345 unmodified. why it did not copy the files??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

7 years, 8 months

[MM3-users] Re: auto-away notices as bounces

by Stephen J. Turnbull

Andreas Barth writes: > * Stephen J. Turnbull (stephenjturnbull(a)gmail.com) [210824 19:31]: > > [I]t's possible that Mailman had nothing to do with it. > Well, the mail adress got disabled, and the user got warning mails > ("Your subscription for list mailing list has been disabled"). > [...] > Please note that individualsation was enabled, OK. But all you told us was the user got disabled or unsubscribed. > so all mails are sent out with per-subscriber mail envelope > address, which then makes bounce detection quite straight-forward. We can identify the subscription easily, but there are still complexities. Is it a hard bounce, or a soft bounce, in particular, but it could also be spam or a rogue autoresponder. > They are sent to the bounce address (more specifically > list-bounces+user=domain@listdomain where user@domain is subscribed > to the list). OK. > I didn't get them as list owner, so no. You have to request that unparseable bounces be sent to owner in the list configuration. It defaults off because most owners wouldn't know what to do with them, although maybe we should default on and provide an explanation of how to forward them to us for future versions, or turn off the forwarding. > > This decision isn't something Mailman should be doing because it > > depends on context and guessing what the subscriber wants. > > Really, this is an owner problem, not a Mailman problem. > > What should I do different as owner? The user was set to disabled > without any manual intervention from me as list owner. As I wrote before, you can set up your lists with a large number of bounces allowed so that their accounts don't get disabled for the period of anticipated absence. You can set the list to send bounce mail that isn't parseable as a standard delivery status notifications (DSN) to you. In this case it would probably have saved everybody a bit of annoyance. Finally, you can filter on that header either using the standard Mailman header filtering[1], or better yet, in the MTA as you suggest: > > It's not obvious what *we* should do. > > My proposal would be to ignore messages sent to the bounce address > with the 'Auto-Submitted: auto-replied (vacation)' header. I'm > thinking about doing that change on the MTA level, Filtering in the MTA the right thing to do. You can already filter and discard such messages in Mailman using the "header filtering" capabilities, I think. But as always, this kind of filtering is far more efficient at the MTA because the MTA is doing a lot of it anyway at most sites. It's also not easy to be sure we get it right. The 'Auto-Submitted' field is standard (RFC 3834), but unfortunately "Auto-Submitted: auto-replied" is the RFC-3834-recommended format for DSNs, ie, bounce messages. We do parse standard DSNs for soft vs. hard bounces, so we can identify standard DSNs but unparsable DSNs still show up occasionally, which are not distinguishable from vacation messages using Auto-Submitted. Relying on the string "(vacation)", which is a comment, would suck for us. We would inevitably get requests for translations into a few dozen languages and additions of "(out of office)" etc, etc, all for a few users / providers (I can't recall hearing of this problem until you brought it up, although it seems like a plausible bug at providers). > but I believe it would be more appropriate at the mailman level. I don't see a good reason to have a standard feature for this in Mailman, because (1) based on the Auto-Submitted field as defined in the standard we can't distinguish "vacation" from a DSN, (2) the comment is arbitrary which would impose a maintenance burden on us as variants and translations appear in that comment, and (3) both Mailman and MTAs already provide sufficiently configurable header filtering. > Sorry, I meant "disabled". A contributing fact was for sure that the > users mail setup sent out the vacation mail on any incoming mail, not > only the first, and also on mails with precendence list. I adressed > that already to the user (because I believe it's a bug), RFC 3834 which specifically calls for efforts to not spam from auto- responder users. > (Especially as the mail provider is gmx, this is *the* largest > webmail provider in Germany, so both the probability of fixes is > rather low, and the probability of happening with users users is > not too low.) That's important to you, and other admins in Germany, and I sympathize. But for us there's no guarantee that other providers will use exactly that format, or won't allow users to specify the comment (even worse). So I respectfully ask you to use the filtering capabilities you already have available to you. Steve Footnotes: [1] I should check this, as filtering probably takes place differently for bounce messages and the rest of Mailman. If we don't already have filtering on bounce messages, I would support adding it to the chain for bounce messages, with the same UI but allowing it to have a different set of filtering rules from ordinary posts and email commands for configuring subscripts.

3 years, 7 months

[MM3-users] REST API Question: possible to change user preferred email?

by Nathan Dixon

Hi, We are in need of being able to change a user's email address via the REST API. After looking through the documentation and code, I can't see a way to do this in a simple way. Although the documentation seems to show that if a user changes their preferred address, it will track throughout all their subscriptions. See: https://gitlab.com/mailman/mailman/blob/master/src/mailman/rest/docs/member… "When Gwen changes her preferred address, her subscription automatically tracks the new address." The only way I can see to do this via the REST API would be to do the following long winded way: *1. Create a new address:* POST to http://<api_url>/3.1/users/<$OldEmail>/addresses $postData: {email = "$NewEmail"} *2. Verify the new address:* POST to http://<api_url>/3.1/addresses/<$NewEmail>/verify $postData: { } *3. Get all the memberships for the old email address* $memberships = GET to http://<api_url>/3.1/addresses/<$OldEmail>/memberships *4. Change users email for each membership individually* foreach ($membership in $memberships) { PATCH to http://<api_url>/3.1/members/<$membership.member_id> $pathData: { address = $NewEmail } } *5. Delete Old Address* DELETE to http://<api_url>/3.1/addresses/<$OldEmail> Am I missing something (as in there is a way to do a single PATCH request somewhere)? Or is this the only way to update someone's email address with these 5 steps? Thanks, Nathan Dixon

6 years, 1 month

[MM3-users] Re: Installing Mailman for the first time

by Jim Berg, Jr.

I am not so sure what I am doing. Is there someone who does this for a fee? Jim Berg > On Mar 24, 2023, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/24/23 16:43, comprepair_jimberg--- via Mailman-users wrote: >> I am running Debian 11 Server and wanting to install Mailman 3 >> Will this work for what I am trying to do? >> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > > Yes, but <https://docs.mailman3.org/en/latest/install/virtualenv.html> is our current recommendation. > >> If not is there a shorter list of steps to accomplish what I am trying to do? > > The above may not be shorter. There are a lot of steps no matter how you do it. > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to comprepair_jimberg(a)icloud.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years

[MM3-users] Mailman/Django-allauth integration with Yahoo

by Дилян Палаузов

Hello, Has anybody managed to use the Django-Allauth Yahoo provider to authenticate towards Mailman3? I have integrated mailman3/django-allauth/gmail — it works. I want in the same way to integrate mailman3 with yahoo mail. As advised at https://docs.allauth.org/en/latest/socialaccount/providers/yahoo.html , in yahoo I register an application with redirect URL https://l.bapha.be/mm3/accounts/yahoo/login/callback/ , then I add credentials under mm3/admin/socialaccount/socialapp/: client ID and Private Key. I append in settings.py:INSTALLED_APPS = [… 'allauth.socialaccount.providers.yahoo' ]. After I do all of this, I eventually visit /mm3/accounts/login/?next=/mm3/postorius/lists/at.l.bapha.be/, click on Yahoo: “Sign In Via Yahoo . You are about to sign in using a third-party account from Yahoo.” → [Continue]. Now at https://login.yahoo.com I enter user name and password. Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: Messages: Confirmation of email address sent to ...(a)yahoo.com Menu: Entrance \r\n New registration Confirm your email address: We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I have indeed received an email, which states: New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. Any idea what can I improve? In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? Greetings Дилян

8 months, 2 weeks

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/26/19 3:07 PM, Mark Sapiro wrote: > > You could modify the above to write the list to a file and then wrap the > whole thing in a shell script which would make the list and then do > something like > > for f in `find var/messages -type f`;do > n=`cut -d / -f5 <<<$f` > for keep in `cat list` ;do > k=0 > if [ $n == $keep ] ;then > k=1 > break > fi > done > if [ $k -eq 0 ]; then > rm $f > fi > done Actually, I thought about it a bit more, and I decided that arcane shell script was a bit obscure and it would be easier to just do it in Python. Plus, you can properly delete the message that way. A complete script for `mailman shell` is like import os msg_ids = {} lm = getUtility(IListManager) ms = getUtility(IMessageStore) for mlist in lm.mailing_lists: requestdb = IListRequests(mlist) for rq in requestdb.held_requests: key, msgdata = requestdb.get_request(rq.id) if msgdata['_request_type'] != 'held_message': continue msg = ms.get_message_by_id(key) msg_ids[(msg['Message-ID-Hash'])] = True for root, dirs, files in os.walk('path/to/var/messages'): for file in files: if not msg_ids.get(file, False): msg = ms.get_message_by_hash(file) ms.delete_message(msg['Message-ID']) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Digest Formatting

by Stephen J. Turnbull

Apollinaris Schöll writes: > yes, yes, yes full ack. Thats what I am doing. But its extremely > hard to convince users to change what they have done for a long > time. Yes, I sympathize with you. > > However, if that's an option, most email clients provide a way to > > "burst" the digest into individual messages, which will then be > > threaded in the normal way for that client. This provides the user > > with the "download all the recent messages periodically" benefits of > > the digest, as well as the threading capability of the client. > > Can you list clients that can do that? I’d like to have options to > recommend if users insist on digest. Not offhand. Besides Emacs-based clients (which all can do it, but I doubt you're going to be recommending those ;-), the ones I'm familiar with are the text-based ones like mutt and mh, and open-source implementations like Thunderbird (burst requires an add-on). Gmail does *not* seem to handle bursting, although Google Groups provides digests. Outlook 2011 had a "burst" filter that automatically burst all incoming digests, not sure if you could do it on-demand at mail reading time, and I don't know about Outlook365. There doesn't seem to be a built-in feature for handling digests in Apple Mail, but there are plug-ins.

4 years, 5 months

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

by Ruth Ivimey-Cook

Marcus, I'm with you in not understanding Mark's instructions -- I think there is a typo somewhere :-) To create a non-member user in Mailman, Go to the List Settings page in Postorius, select Non-members from the User menu, and add a user there. Of course, that does nothing for your email system, which must also be configured. I would very strongly encourage you to have the no-reply address be 'real' in the sense that the email system will agree it is valid and deliverable, or some recipient email servers will refuse to accept email from that address, either. The right thing is for email to that address accepted as normal and then immediately discarded. You could send back a message "this address is not monitored" but there is an issue with spam backscattering which makes that less good than it first seems. Regards, Ruth On 06/04/2021 10:00, marcus.granath(a)gmail.com wrote: > Thank you @Mark Sapiro for you quick reply. > > So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: > > Settings -> Message Acceptance > > "Default action to take when a member posts to the list": "Hold for moderation" > "Default action to take when a non-member posts to thelist": "Hold for moderation" > > Members -> Administration options -> Moderation: "List default" > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? > > Also, how do I create a "non-member" user "no-reply(a)abc.com"? > Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there? > _______________________________________________ > 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/ -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years

[MM3-users] Re: Sorry to repeat a question, but how do I permanently delete messages, again?

by Tim Cutts

It can be done in the GUI. See this historical thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> T > On 8 Jul 2022, at 13:48, William Oliver <billo(a)billoblog.com> wrote: > > > I askled this question some months ago, but for the life of me cannot > find the response (though there is one). I want to purge some > specific emails from the list archives. A user posted what he thought > was a personal message to the list, and is embarrased by it, so I told > him I couldn't delete emails that were already downloaded onto client > machines, but I can delete it so that new users won't be able to see > it. > > But... I can't figure out how to do it. > > I asked this once before, some months ago, and as I remember there is a > command line way of doing it, but not a GUI way. But i can't remember > what it was. > > Thanks! > > billo > _______________________________________________ > 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/

2 years, 9 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly. Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense. On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung(a)afilias.info> wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/31/2018 07:04 AM, Ryan McClung wrote: >> > Scratch that. Ran with the corrected script and getting the following: >> > [root@mailman3(stg) archives]# mailman lists >> > No matching mailing lists found >> > >> > Any thoughts? >> >> This >> >> > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ >> afilias.info "${DIR}"/config.pck; >> >> is still wrong. The list name for mailman create needs to be fully >> qualified as in >> >> > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman >> import21 ${DIR}(a)afilias.info ${DIR}/config.pck; >> >> (Do you look at the output from your script?) >> >> -- >> 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/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

6 years, 8 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Stephen J. Turnbull

Stefan Bauer writes: > Collapse alterantives: YES > Convert html to plaintext: NO These options probably delete any plaintext and leave HTML as it is. > Thunderbird is showing the mail "correct". Outlook does show the > attachments as attachments. Note that they're not attachments as defined by MIME, they're labeled "inline" in the Content-Disposition header. The obvious thing for the MUA to do is to display non-HTML inline parts in order vertically, then the HTML part(s), then more non-HTML inline parts, and so on. A Sufficiently Smart MUA can probably make things a bit more attractive. Outlook just doesn't bother at all. :-( If you must cater to Outlook, the obvious way to handle it is to configure to delete HTML parts unless they are the only text part, and in that case convert HTML to plain text. IIRC that's Collapse alternatives: YES Convert html to plaintext: YES If you can legally do so, you can also configure the header and footer to be completely empty (not even white space). But that second option is only useful when you want to remove "ugly" attachment buttons, and can't be used when the footer text is needed. Before you ask the obvious question: It would be possible to try to do "reasonably user-friendly" handling in Mailman by editing the HTML part instead of adding MIME parts, but I myself won't do this because it almost certainly would result in mangled, at least partially unreadable mail in some cases. In particular, if you need to have the footer displayed for legal reasons, this could make it undisplayable even by competent MUAs like Thunderbird. It would also probably be ugly. I'm not willing to deal with the likely user complaints, nor do I like the risks it would impose on list or site administrators under some laws. This could be done as a plugin, and if somebody wants to contribute one (and preferably offer support) I would probably support adding it as a contrib feature (that is, if the code is of a certain minimal quality). Steve

2 years, 2 months

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 10/31/19 2:21 AM, Alan So wrote: > We notice that sometimes mailing lists do not honor moderation_action of non-members. Instead, it follows the default action of the lists. It looks like we can sometimes fix the issue by adding/removing the non-members or adding/removing them as owner in certain order but we are not sure about exactly what we have to do. So, it looks like that it is not caused by the list configuration. We have already verified from the web UI, mailman client and the DB table member that moderation_action of the corresponding non-members are set correctly. Any clues for us to provide further information to troubleshoot the issue and any recommended workaround to get around the issue? Thanks a lot. Reasons why a post From: a non-member would not be treated according to that non-members moderation_action include the following: If any address in any of the places configured in mailman -> sender_headers (default = From: header, envelope sender, Reply-To: header, Sender: header) is that of a member, that member's moderation_action will apply. If any of the addresses above matches an address or pattern in one of the lists *_these_nonmembers attributes that action will apply rather than the corresponding non-member's moderation_action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

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

by Rafael Mora

El jue., 3 ago. 2017 a las 15:12, Simon HANNA (<simon.hanna(a)serve-me.info>) escribió: > > > > > > >Should I configure my private Centos7 server with subdomain > >lists.labbrands.com? > That's what I suggested > Ok, Thanks Simon I will do it as suggested by you > >Doing so how do I redirect the email to the private Centos where > >postfix > >and MM3 are installed? > This really doesn't have anything to do with mailman. There are tons of > tutorials out there. > Generally you should try to find answers yourself and only ask when you > couldn't find anything. People are motivated to answer if they find > questions interesting and think they might learn something themselves. If > they think the question can be easily answered using a Google search, they > are generally less inclined to respond... > You guys have implemented MM3 before me and I think your experience is more valuable than a google search and believe me I've search on google about this, so If you know a site/forum where is explained please send the link. Thanks againa Simon > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > 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

7 years, 8 months

[MM3-users] Re: sending messages in response to posts from non-members

by Mark Sapiro

On 2/26/22 04:26, David Bremner wrote: > > I'd like to turn off the "bounce messages" sent by mailman to > non-members. My reasoning is that most such posts are spammers, and > often use forged return-paths / From's, so I end of sending steady > stream of backscatter to amazon.com etc... > > Is this configurable (without postorius) somehow? What exactly do you want? Do you want to discard without notice any nonmember posts or do you want to hold them but not send a notice of the hold to the poster? For the former, you want to set the list's default_nonmember_action to discard. For the latter you want to set the list's respond_to_post_requests to False. To make either of these settings the default for new lists, you'd need to patch mailman/styles/base.py. To set them for all lists you could do the following in `mailman shell` ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager).mailing_lists: ... # Pick the appropriate one of the following. ... mlist.default_nonmember_action = Action.discard ... mlist.respond_to_post_requests = False ... >>> commit() ``` -- 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: statistics monitoring for Mailman3

by Mark Sapiro

On 3/15/21 12:39 PM, Mohsen Masoudfar wrote: > Hi Mark, > > Thanks again for the nice Python script. There is an issue with outlook.com. They add a '^M' (carriage Return) before msgid!! > Here is part of the log that shows that. This is not in every log, though. I updated the get_log_data function (please see below), I believe it is not the smartest solution, but it seems to be working for me. Does the script with your change produce a different result than the original? This has nothing to do with outlook.com per se. It only has to do with the length of the log message. Further, I do not think there are actually newlines in these log messages. I think that is just an artifact of how you are viewing the log. > Mar 14 12:53:21 2021 (11701) > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds I suspect if you do ``` grep namprd20.prod.outlook.com /path/to/var/logs/smtp.log ``` The result will be lines like ``` > Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds ``` whereas if they are really split, the result would be ``` > <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-01-30 12:08:10 -0800 (-0800), Mark Sapiro wrote: [...] > Domains can be created via Postorius or via the Mailman Core REST API that > postorius uses or implicitly by the `mailman create` command when creating a > list in a new domain. However, none of this can create a new site. You can > do this through the Django admin site at sites/site/add/. > > See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you > can use to do this programmatically. Thanks, I'm still doing my best to wrap my brain around how Django uses database migrations to create sites (seems like a very strange use of a migration, I'm only accustomed to seeing them applied for database schema updates). Once I work out how to script site creation, I'm still not completely finding the explanations I need for how to map them to domains in Mailman though. The Mailman documentation about domains says "Domains are how Mailman interacts with email host names and web host names" but doesn't actually go on to say (that I can find anywhere) how it actually associates them. I can see in the API docs that a POST to the domains endpoint will create a new domain with a specific mail_host FQDN, but there's some association somewhere of that to a web host (Django site), right? How is that set or manipulated through the API? Or is that something which has to be set directly in Django's data structures instead? To recap, on creation of a mailing list server I want to populate it automatically with multiple lists on different domains and have dynamic SITE_ID=0 domain guessing performed so that the correct site name and list filtering is performed depending on which domain name is used in a URL the client requests. I believe I need to have the automation perform the following steps: 1. Instantiate the Mailman installation and run initial migrations with SITE_ID=1 in order to avoid the problem mentioned in the docs about not using SITE_ID=0 until the tables have been populated, then switch the settings.py to use SITE_ID=0 once done. 2. Create the individual sites I need in Django (Mailman web hosts) by creating and applying database migrations. 3. Create the individual domains I need in Mailman (Mailman mail hosts) through its REST API. 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond to what web hosts. As I said, I'm still trying to understand how to make step 2 happen (Django has a steep learning curve for me), but beyond that I'm unsure how to do step 4 at all. I can do all of this through the WebUI of course, and have confirmed that it works as expected when I do, I'm just trying to work out the automation so that our other sysadmins don't have to perform these steps by hand the next time we need to rebuild the server. Thanks again for all the help so far, and for any additional insight anyone may have into how I can correct my mental model of all this. -- Jeremy Stanley

2 years, 2 months

[MM3-users] Re: Customise Postorius templates?

by Mark Sapiro

On 2/1/22 09:47, Duane Raymond wrote: > Hi, > > I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying > venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html > to > var/templates/lists/summary.html > > As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. The var/templates directory has a specific structure and is only for custom list specific, domain specific and sitewide templates used for notifications from Mailman core. It has nothing to do with Postorius or HyperKitty templates. > Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!) I don't know about a `best` way, but the way I do this is to keep all local mods as patches to the base and apply those patches as part of the upgrade process. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Change digest frequency and default threshold

by Henrik Rasmussen

When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. 1) How do I set another default for Digest Size Threshold for new lists. 2) How do I change the default for existing lists When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. How do I change this setting, both on a single list and the default for new lists? Henrik Rasmussen

6 years, 7 months

[MM3-users] Turn off social logins?

by worik

How do I turn off the social logins? I looked in the admin manual but They are not working, but I absolutely do not want them for now. Maybe one day, but my users will be allergic to even the hint.... Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] Tracking from gravatar

by worik

Privacy badger reports one tracker (for which it disables cookies) on my Mailman installation. It is: secure.gravatar.com What is this for and how do I get rid of it? I looked at the site and it seems like some sort of take a avatar any where. I do not want that on the lists I am managing for this group of users. cheers Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] installation choices for mm3

by John Griessen

I've been reading https://wiki.list.org/DOC/Mailman%203%20installation%20experience and see that a virtual is recommended, which is not something I have done yet, and wonder if just putting the mm3 on a different server is easier? I have a server, mail1.cibolo.us that has postfix, postgresql, dovecot, mm2, nsd on it. Another server has just web pages and nsd doing backup DNS for mail1.cibolo.us DNS server. I could do a straight debian install of mailman3-full on the 2nd server and keep it simple, let debian setup a blank database installation, right? Has anyone seen a good write up on how to do that on a debian server step by step?

5 years, 11 months

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Alan So

Are there any pointer of documentation that I can clear all _these_nonmembers settings by updating the databases directly or using mailman shell? I am not so familiar with mailman shell though. We expect list owners use moderation_action only for members and non-members. We are using and so the import21 did not do this correctly. mailman 3.2.0

5 years, 5 months

[MM3-users] Your Dashboard

by Torge Riedel

Hi, everytime I receive a mail for moderation it says: At your convenience, visit your dashboard to approve or deny the request. So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. If it is already there, where do I find it? If not, do others also find such a dashboard helpful? Best regards Torge

5 years, 2 months

[MM3-users] How to configure a mailing list?

by Patrick Ben Koetter

Greetings, I do have mailman 3 installed via virtualenv and it is up an running. Now I'd like to create a mailing list, but I can't find any instructions how I should do this. Is there a resource online I missed? If not, can anyone on this list tell me how to do it preferrably using a command line tool? TIA p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 1 month

[MM3-users] Re: installation

by Christian Stalberg

Continuing to work through installing mailman3 on Ubuntu 20.04.1 LTS / apache 2.4.41 / postfix 3.4.13. I am at https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl ight=compilemessages#final-setup-instructions What do I do now about this? (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# python manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /opt/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: y CommandError: Collecting static files cancelled. (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# Thank you! ~Christian

4 years, 5 months

[MM3-users] where do I find the text of a bounce email ?

by Per Jessen

All, I am trying to figure why a particular outbound message was bounced, so I'm looking for the text of the NDR that was sent - where do I find that ? Fyi, the outbound message was accepted by the first relay, and then presumably later bounced by the actual recipient server (Office365). Any and all hints much appreciated. -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

4 years, 1 month

[MM3-users] Re: migration

by Stephen J. Turnbull

Dave McGuire writes: > > https://www.djangoproject.com/ > > I'll get to reading. Thanks! It's not clear to me that you need to do a ton of Django wrangling, though. The migrations are run automatically when you issue the commands to upgrade, and are in the RDBMS backend, not the Django ORM. The work you have to do "by hand" (DB dump/restore) is also on the backend RDBMS end. You may have to do some fiddling with Django modules, especially middleware, but that's all Mailman-specific and reasonably well explained in our docs. (That's my opinion, and YMMV, so don't hesitate to ask!) Steve

3 years, 8 months

[MM3-users] remove non members from a list

by Guillermo Hernandez (Oldno7)

Hi all: I need to remove all non members from a list. I know I can do it via Postorius, but it has to be done one at a time. (you can delete ALL suscribers but not all non members...) Anyone has a python recipe to do this? I've been searching and googling but I cannot find the way of doing it safely. And via DDBB there are more than one table involved and I'd rather not mess it all... Thanks in advance

3 years, 8 months

[MM3-users] Re: can't get mail into mailman3 in docker

by bob B

so I added "- MTA=postfix" to the yaml file ****************** services: mailman-core: . environment: - MTA=postfix .. ****************** docker loks do not shoe a postscript error now ****************** Postgres is up - continuing Using Postfix configuration Found configuration file at /opt/mailman/mailman-extra.cfg ****************** BUT I still get this on the hosts mail log ************************ [127.0.0.1]:8024, delay=0.16, delays=0.08/0.04/0.04/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting) **************************** I thought that setting would fixed it (thanks Matthew) but apparently not Not sure what do do next? should I blow it all away and re install? What is that procedure?

3 years, 8 months

[MM3-users] Mailman import of 2000 lists

by dancab＠caltech.edu

I'm working on importing nearly 2000 lists and have been doing some testing prior to migrating from Mailman2. I'm using the mailman create command via for loop. It takes quite a while to do all the work including updating MySQL and re-generating the LMTP files for each list. As the number of lists increases the process gets slower. Do you have any recommendations for speeding up this process? I am running the system in AWS using EFS for storage of the LMTP files. Thanks! -- Dan Caballero Caltech

3 years, 6 months

[MM3-users] Templates do not work

by Eggert Ehmke

I created some templates in Postorius to get personalized notifications when there are moderator requests. The notifications I get seem to be the standard texts. When I look into mailman/ mm/var/templates the directory is empty. Nevertheless, the templates I create in Postorius seem to be stored (where?), they just do not work.

2 years, 11 months

[MM3-users] Help understanding why some users don't receive emails

by Stephen Daniel

Mailman3 people --- I'm a novice at running mailman, so any advice would be appreciated. I manage a few small lists using a mailman3 server. A few of my users complain they do not receive emails. Looking at one user in particular, I see in /var/log/syslog that postfix is sending the email. There is nothing in bounce.log. They are the only user who uses that particular email domain (embarqmail.com ). Is there anything I can do to debug why they do not get the emails? Or is this up to them and their email provider? Thanks! -- Steve Daniel

2 years, 7 months

[MM3-users] Re: Is there a way to see all the list's held messages

by Martin Lorenz

Mark Sapiro wrote: > On 10/11/22 07:04, bob B via Mailman-users wrote: [...] > run mailman' mean you are an admin of the server on which it is > installed? If so, you can do this in mailman shell, but what do you in my case: yes > want to see? I.e., just a summary by list of subject, sender and hold > reason how would I do this? Additional question: how would I set/change the owner of a number of lists identifyable by a regular expression?

2 years, 6 months

[MM3-users] Re: Weird startup problem after upgrade

by Mark Sapiro

On 12/3/22 00:03, Odhiambo Washington wrote: > On Fri, Dec 2, 2022 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> How do you start it manually? `mailman start` or `systemctl start >> mailman3`? > > > systemctl start mailman3 Presumably you do this as `root` or via `sudo` so I don't understand what would be different between doing it manually vs. via systemd at startup. I can't explain that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Where do I find the bounced messages?

by Sörös Zoltán

Greetings, I am running several lists under mailman3. I am getting notifications about users being put on nomail because of their bounces - but I can find no way to actually see the bounced messages. Do mailman3 store the received bounces? Where? Is there any setting to forward these bounces to the list owner? Thanks in advance -- Sörös Zoltán E-mail: beer(a)filmjus.hu http://www.filmjus.hu/~beer/

2 years, 4 months

[MM3-users] Re: Installing Mailman for the first time

by Mark Sapiro

On 3/24/23 16:43, comprepair_jimberg--- via Mailman-users wrote: > I am running Debian 11 Server and wanting to install Mailman 3 > > Will this work for what I am trying to do? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 Yes, but <https://docs.mailman3.org/en/latest/install/virtualenv.html> is our current recommendation. > If not is there a shorter list of steps to accomplish what I am trying to do? The above may not be shorter. There are a lot of steps no matter how you do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] MM3 does not receive gmail-Members!

by Paul Brenner

Hallo I need help! My MM3 sends mails via a list. However, no mails arrive at all gmail recipients. These mails also do not end up in the spam or junk folders. What do I have to do? Regards Paul

1 year, 11 months

[MM3-users] Re: How do you remove the Hold on all non-member forwarded emails?

by Sean Westfall

I had no idea this was mailman 2.1, maybe that's the reason why. I will try to do this with mailman3, and see if the same issue occurs.

1 year, 10 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Tom Smyth

Reviving this super old thread b/c it has good Google page rank for "mailman 3 see bounce emails"... Could this please be added as a config option so we don't have to patch the server code? Seems like a very useful feature for debugging odd bounce behaviors such as I'm doing right now. Thanks for considering! -- Tom Smyth (he/him)

1 year, 9 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Mark Sapiro

On 7/1/23 7:02 AM, Tom Smyth wrote: > > Could this please be added as a config option so we don't have to patch the > server code? Seems like a very useful feature for debugging odd bounce > behaviors such as I'm doing right now. Starting with Mailman core 3.3.5, bounce DSNs are included in the admin notices. See https://gitlab.com/mailman/mailman/-/issues/737 -- 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: Issues with @gmail.com addresses

by Jeremy Stanley

On 2023-09-09 17:34:04 +0900 (+0900), Stephen J. Turnbull wrote: [...] > Do you know if the whole spammy mail is needed to trigger the > overly sensitive sites, or if just From: and Subject: can do it? Honestly it's hard to say, as with any of the black-box spam identification heuristics the large freemail providers employ. Probably included subjects and addresses could trigger them, but I expect they have a lower chance of doing so. Volume of notifications is the other thing to consider (so the batching idea you mentioned might be a help there). -- Jeremy Stanley

1 year, 7 months

[MM3-users] Mailman messages are getting a TAG in some email clients.....how????

by bob B

So I know about the setting "Anonymous list" but regardless of that setting some email clients put the list name in [] when it displays messages in your inbox. Does anyone know how email clients are doing this? I have users who email clients do not do this, and was wondering if it is a setting in their client or just not possible. Here is a link to an image showing the tag for a list called TEST6 https://imgur.com/a/7VyJtsD

1 year, 7 months

[MM3-users] Re: LDAP user email verification

by Abhilash Raj

On 9/15/23 02:54, Tony Deshields wrote: > I'm running the docker-mailman setup with LDAP integrated. My users that authenticate against LDAP are still required to verify their email address however, I do not want this functionality. I was looking for guidance on possibly configuring it so my LDAP users do not have to verify their email address. AFAIK, there isn't any existing configuration that would allow you to do this, but it really depends on how have you setup the LDAP authentication. IMO, the auth backend used is the best place to -- thanks, Abhilash Raj (maxking)

1 year, 7 months

[MM3-users] First time mailman installation

by roland＠giesler.za.net

I have installed mailman3 on Ubuntu including postorius & hyperkitty (from the packages). I have questions now which are not quite clear to me from the docs: 1. How do I specify my mail server details (which is my own server running postfix, etc) 2. How do I create new lists from the postorius UI, or can I only do that in the config files or the command line console for mailman3? thanks!

9 months

[MM3-users] Re: how to integrate subscription into static jekyll website

by Hagen Bauer

On 10/18/18 6:42 PM, Abhilash Raj wrote: > > > On Wed, Oct 17, 2018, at 11:09 PM, Hagen Bauer wrote: >> Has anybody tried to hide the direct api access behind a nginx reverse >> proxy url? > > That would still need authentication right? Even behind nginx proxy. > > Where do you plan to keep that secret when using a static website? on the Webseite I would have a url like this mailmanserver.tld/subcsribe/user(a)mail.com And within the nginx proxy configuration on the server this would translate to localhost:80xx/"mailman-restapi-with-credentials"user(a)mail.com So the public does not see the credentials. And if my nginx host config is hacked I have a problem anyway. > >> >> >> On 10/18/18 1:19 AM, Abhilash Raj wrote: >>> On Wed, Oct 17, 2018, at 10:39 AM, Hagen Bauer wrote: >>>> Hi, >>>> >>>> I am running a static website with jekyll and I want to integrate a form >>>> that executes a subription rest api call to mailman. >>>> >>>> From my first investigation this seems to be a bad idea from a security >>>> perspective (rest api needs managaer access). >>>> >>> >>> I agree, you should never be exposing your Mailman Core's API to Internet, because it is an administrative API. >>> >>> To be able to do that entirely in front-end, you may even have to expose the password in front, which is definitely not a good idea. >>> >>>> Is there a secure way to do this? Any other ideas? >>> >>> One thing you could do is have `mailto:listname-join@domain.com` URL in your site, that your subscribers can use to send an email to subscribe. >>> >>> You might be able to embed our web frontend in an Iframe or something, I don't have any experience doing that or am not even sure if that'll work. >>> >> _______________________________________________ >> 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/ > >

6 years, 6 months

[MM3-users] How do I specify the TCP port number for Postgresql?

by kjohnson＠eclypse.org

The mailman.cfg file on the system I am working on includes this line: url: postgres://mailman3:mailman3:@localhost/mailman3 This works fine as long as the postgresql server is at the default port number of 5432. How do I specify a different TCP port number? My guess is that a change to this line is needed, but unfortunately, it is not obvious to me how to make that change, and I have been unable to find this information in the mailman3 documentation or in a previous mailing list post. Feel free to point me at the documentation or post that I have overlooked. Thanks, Ken

1 year, 9 months

[MM3-users] Re: Templates

by Mark Sapiro

On 09/23/2017 07:36 AM, David Krantz wrote: > Still two problems: > > 1. I do not know how to force a cache invalidation on a template. So > only way to change is to set a new name on the file and change the uri > there. Unpractical. No, restarts do not work. Have you tried restarting/reloading whatever dbm (MySQL, PostgreSQL, ?) you are using? > 2. the $user_delivered_to and $user_email do not expand for some > reason. Known problem? These require that the list delivery be personalized. See <http://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/outgoing.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/12/22 01:24, Onyeibo Oku wrote: > > Good Morning Everyone, > > I installed and managed mailman 2 for about two years. I am now > ready to try Mailman 3. The documentation for version 2 was lucid and > this forum was quite helpful in the past. > > Now I'd like to proceed with installating MM3 but I doubt my > understanding of the docs. It seems to assume that users will know what > to do. > > Okay, don't laugh! I just want to be sure what I am doing. Does the > following sequence resemble the proper steps? As Eggert says, we aren't laughing ... > 1. Download the source from a git repo (I understood that one) > 2. Create a virtual environment (venv perhaps ... not stated explicitly) > 3. activate the virtual environment > 4. from the git project root, run: ./mailman start Step 4 is premature. More below. > I know, its stupid. I had to ask. Not stupid ... > It would really build my confidence > someone would confirm the above steps or counter then with something > very explicit. What about process ownership? Do I need to have a unix > mailman user? What else do I need to get mailman up and running > before proceeding to configuration. Ahaa! I perused the config docs a > bit. Where can I find the .cfg file? As Eggert suggests, see https://docs.mailman3.org/en/latest/install/virtualenv.html and follow that. You don't need to download the source from GitLab. Following that doc will get the latest releases from PyPI via pip. Those are still somewhat out of date - we really should make new releases - so if you want the latest from GitLab, there are a couple of ways to do it. Perhaps the easiest is to just run the various `pip install` commands as documented and then upgrade Mailman core in your venv with ``` pip install --upgrade git+https://gitlab.com/mailman/mailman@master ``` and update the various mailman web packages with ``` pip install --upgrade git+https://gitlab.com/mailman/xxx@master ``` where xxx is mailman-web, mailman-hyperkitty, django-mailman3, postorius, hyperkitty. I.e., run it 5 times, once for each value of xxx. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: installation

by Mark Sapiro

On 11/21/20 5:40 PM, Christian Stalberg via Mailman-users wrote: > What do I do now about this? > > (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# > python manage.py collectstatic > > You have requested to collect static files at the destination > location as specified in your settings: > > /opt/mailman/mailman-suite/mailman-suite_project/static > > This will overwrite existing files! > Are you sure you want to do this? > > Type 'yes' to continue, or 'no' to cancel: y > CommandError: Collecting static files cancelled. > (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# y != yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/30/21 6:23 AM, Lucia Moreno wrote: > Hi Mark, > > We are facing the same issue. My postgres database is growing too fast and > I would need to do some creaning of old archives dated from 2001 and keep > only the last, lets say... 5 years. > > Could you please help us with the development of such a script? I have no > experience in python. The attached script is a rough idea. It assumes your Mailman is installed in a virtualenv at /opt/mailman/mm/venv and the django settings module is /opt/mailman/mm/settings.py. The pruned messages will be in a mbox at /opt/mailman/pruned.mbox. The age of messages to prune is defined by the days=365*5 argument in CUTOFF = datetime.datetime.today() - datetime.timedelta(days=365*5) All these things may need adjustment for your purpose. There is also a commented bit showing how you could do just one list. It's probably good to do just one list at a time since it's not clear how useful the pruned.mbox will be if it contains messages from multiple lists. I.e., run it for one list and move the pruned.mbox aside before doing the next list. Note that I've tested that this works, but it's possible that it will leave HyperKitty in a bad state. Backup your database before running this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 04:57 PM, Rafael Mora wrote: > Should Sign Up ?? Log In?? Yes. > El vie., 21 jul. 2017 a las 18:56, Rafael Mora (<rafael.mora.guti(a)gmail.com>) > escribió: > >> Nice! Up and running! >> >> How do I start using mailman? what are the steps?? What do you want to do with Mailman? This is the key question. There is some list subscriber documentation at <http://docs.list.org/en/latest/userguide.html>. You can create domains and lists via Postorius or via the core's bin/mailman commands ('bin/mailman --help' for a list). -- 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: Turn off social logins?

by Stephen J. Turnbull

Note: I've changed the order of sentences from Torge's post to fit my responses. Torge Riedel writes: > I do agree, same here on my side. Lot's of my users are very > "sensitive" to social media and don't want see them here. This is the first I've heard of this. Obviously it's fairly widespread; *please* speak up if anyone have similar issues that we haven't addressed. AFAIK all of the currently active Mailman developers believe that social auth is a GoodThang[tm], so we're unlikely to DTRT as you see it without your help. > I need to migrate from mailman2 to mailman3 and was wondering why > social accounts are enabled by default By default Mailman 3 is social media: you have a profile, you can be searched in the indicies of the archives, and so on. The large auth providers provide more secure authentication, and a lot of convenience for users who have such accounts already. They also take some administrative burden off the list and site managers when people lose their passwords and forget what their subscription address is, and similar scenarios. Clearly, these are not universally-valued features, but I think that they justify the current defaults. > and are difficult to disable. They're easy enough to disable (easy to recognize and just add a hash character in front), since you have to edit settings_local.py to install anyway. If you're using a packaged version and the package configuration utility doesn't handle it, there's nothing we can do about it. The distro will have to deal with that. It should be better documented, I imagine (haven't checked yet). > I propose something like an additional setting listing the enabled > social accounts. Do you mean in the Postorius administration interface? If so, do you want it by-site, by-domain, or by-list? ("You" is everybody who wants to disable social auth, not just Torge!) If you mean in settings_local.py, I suggested something similar earlier. It's not obvious it would be easy to do (sometimes these things are order-dependent, though that's bad practice). > And if the admin is setting this to an empty value in the > settings_local.py everything is disabled Because the settings are a Python module, this is the way settings_local.py works anyway. That's why Mark suggested editing INSTALLED_APPS.

6 years, 2 months

[MM3-users] Re: sass error

by Mark Sapiro

On 04/19/2018 02:41 AM, Alexander Klotz wrote: > Hi everybody, > > we tried to make a fresh installation out of the current version > following the readme.md - we encounter the following error trying to do > so. As mentioned elsewhere, 'sass' has been replaced by 'sassc', > however, maybe somewhere there is still a reference to it that may have > been overlooked? The answer to a similar error posted to this list in > August 2017 unfortunately didn't help either. What do you have in your Django settings for COMPRESS_PRECOMPILERS? Do you actually have sass or sassc installed? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Henrik Rasmussen

In regards to GDPR*) I am wondering if there is any ways I can require my current and future subscribers, members and list administrators to accept registration. I am also concerned that new lists are created with a subscription policy "Confirm" as default, rather than at least "Moderate", which can cause people to be subscribed by others against there will. Also, regardless of this setting, administrators can subscribe people without their knowledge. Away from Gravatar, mentioned in another post, what implications do GDPR have on Mailman? *) http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX%… Henrik Rasmussen

6 years, 11 months

[MM3-users] Re: changing adverstised status

by Simon Hanna

On 8/22/18 10:27 AM, Alexander Klotz wrote: > Hi there, > > we are trying to set a once public list to private but have trouble > doing so. In Postorius this doesn't seem to work - you can change > "show list on index page" via the settings, but the value isn't saved. > Is there a way to set advertised = False to a specific list via the > shell? What do you mean it isn't saved? Are you getting an error? Is it just being overwritten to True? I use the rest api, using it you can do the following: ./manage.py mmclient lists = client.lists l = <choose your list> l.settings['advertised'] = False l.settings.save()

6 years, 8 months

[MM3-users] Re: MASS mailing list import - 900 ezmlm lists to Mailman

by grant＠horizonsunlimited.com

Thanks for the thoughts! It might be easiest to simply go to the currently supported cPanel version of Mailman installed on the server is 2.1.39. In theory - and we all know what that means - when they upgrade to 3, there will be a script to do the conversion, and I think if what I read is correct, there already is, but in this case it would be up to the server admins to do it, not me :) So - if someone thinks they can do the ezmlm to Mailman 2.1.39, talk to me, let's see what we can work out. Gates foundation huh... I'll have a look! :) Thanks!

2 years

[MM3-users] Re: postfix virtual domain and mailman 3

by Mark Sapiro

On 12/25/19 1:53 PM, work(a)andrefincato.info wrote: > > question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. > > is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so > > ``` > virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap > ``` I think the above should work for you. As far as `dump_json` is not an available module goes, the docs reference a lot of helper functions that are described at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/docs/documentati…>. These need to be imported. I.e., for dump_json ``` from mailman.testing.documentation import dump_json ``` But, if you are just trying to set an alias_domain for the domain and you have Postorius, you can do that via Postorius. If not Postorius you can use `mailman shell`, For example ``` $ mailman shell Welcome to the GNU Mailman shell >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = 'x.example.com' >>> ``` Then you need to do `mailman aliases` to create/update the maps. -- 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] Mailman do not honor non-members moderation setting sometimes

by Alan So

Some of our users reported that their list do not honor the nonmembers moderation setting sometimes. We were not able to repeat the issue consistently earlier. Luckily, we found the following way to repeat the issue: 1) Create a new list with user(a)example.com as owner. (Ordinary disussion mailing list style) 2) Change the list Settings -> Message Acceptance -> Default action to take when a non-member posts to the list: Discard 3) Add a non-member user(a)example.com and change the moderation setting to Hold for Moderation 4) Send an email to the list using user(a)example.com. The message is discarded instead of being held. The above can also be repeated with the list setting Default action to take when a non-member posts to the list: Accept immediately. The message sent from user(a)example.com is accepted instead of being held. So, it looks like that the non-members moderation setting is ignored for this case. Further study indicate that the issue did not happen if the owner is set to user(a)example.com *after* adding the non-member. It looks like that we can avoid the issue during list creation. However, the issue can also be triggered through other ways such as adding the non-member as member and remove. There are also ways to resolve the issue by removing all corresponding member, non-member, owner setting and add them back in the following order: non-member, owner. However, it does not always work and so I do not go into the detail at this moment to complicate the issue.

4 years, 10 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/31/2018 07:04 AM, Ryan McClung wrote: > Scratch that. Ran with the corrected script and getting the following: > [root@mailman3(stg) archives]# mailman lists > No matching mailing lists found > > Any thoughts? This > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@afilias.info "${DIR}"/config.pck; is still wrong. The list name for mailman create needs to be fully qualified as in > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman import21 ${DIR}(a)afilias.info ${DIR}/config.pck; (Do you look at the output from your script?) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 10:37, Eggert Ehmke via Mailman-users wrote: > Hello Steve, > I really would appreciate to get some help on the withlist command. I really like to program python, but this interface is not at all intuitive. I also find it strange to do administrative tasks in a programming language. In this special case, I believe it should be possible to work on the display names in Postorius in the member settings. You can update user display names in Postorius via the Users tab at the top of the page, but it would be a tedious, one at a time process, and I don't think you can modify address display names in Postorius and those are the ones `mailman members` displays. I just posted a mailman shell (aka withlist) interaction at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Try that. > I also find it strange to do administrative tasks in a programming language. Understood, but there are a couple of things at work here. One is that this particular task is a one-off the correct the result of a bug, but perhaps more significantly, mailman developers (at least me) are comfortable with `withlist` (it's been around since MM 2.1) and if I can do it that way, it reduces the motivation to make something more friendly for the normal admin. Unfortunately doing things easily that way requires a lot of specialized knowledge of Mailman internals, so most admins need help with it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Mailman3 Setup

by Mark Sapiro

On 6/11/22 06:02, George R. Kasica wrote: > Mark: > > These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. I virtualenv is not a "container", at least in the sense of a Docker container. It is just a way of isolating an environment from various OS things and vice versa. You do not need to install in a virtualenv. You can follow the procedure for installing in a virtualenv and just omit the bits about creating and activating the virtualenv However, if you do not install in a virtualenv, you are vulnerable to OS package updates breaking things. For example, installation of Mailman core installs SQLAlchemy <1.4 because Mailman core is not currently compatible with SQLAlchemy >=1.4. If an OS package upgrade installs SQLAlchemy >=1.4, that will break your Mailman installation. > If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? You actually don't need to remove anything because whatever is installed in the virtualenv will be what's used when the virtualenv is active. However, any Mailman specific stuff installed systemwide will not be used and is just wasted space and could be uninstalled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Emergency Moderation

by Stephen J. Turnbull

Brian Carpenter writes: > Can I add this through a mailman core update via pip? Eventually .... This depends on when Abhilash gets enough content and a little bit of time to do a new release. Getting meta: You've been asking for very recent features fairly frequently. I understand that everybody feels better with released code, but to be honest, we do not have a deep quality assurance process. The test suite is voluminous and quite comprehensive, but that's not the same as having a proper beta process, mandatory reviewing, etc etc. It's not obvious to me that we can do a better QA for you than you can do for yourself. With that in mind, have you considered building your own from source, on a branch from a moderately recent tag, and cherry-picking only commits for features you really want right now? I admit I don't know how appropriate that is in our tree (I just build from master all the time), but I think that Abhilash is probably pretty careful to pull complete branches so that this should work. If it looks to you like the patches are a little "ragged around the edges", we can work on the process and try to make it more amenable to such cherry-picking for people like you who need some of the most recent commits ASAP, but don't want to accept the whole "bleeding edge". This also would be useful for your Affinity etc development, I think. (Of course maybe that's what you're talking about, but "emergency moderation" is a pretty common need in production.) Steve

4 years, 10 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > So it's even weirder – however, I'm really not sure if this is the address > HyperKitty is checking for, as I have 3 attached to my account! > How may I know which one it's trying to use? If you go to https://example.com/user-profile/ what Primary email and Other emails do you see? Do you see all three? And if you go to https://example.com/mailman3/users and click Manage for your address, do you see all 3 under Addresses? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 2 days

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 3:06 PM, William Oliver wrote: > > When running mailman3, do I need to set up a completely different > virtual domain for it to run in? No. > My "real" domain name is > libertyfp.org, and I'm trying to make mailman work on that domain, e.g. > "testlist(a)libertyfp.org." I'm starting to get the idea that I need to > stick a completely different domain in there for the mailinglist. No. However, in Postfix, libertyfp.org is a virtual_mailbox_domain so you have to use an alias domain in Mailman. An alias domain is not a real domain. It is only known to Mailman and Postfix. It is not exposed in DNS or anywhere outside your server. Have you actually set an alias domain in Postorius for the libertyfp.org domain. It doesn't matter what name it is as long as it isn't a real domain. A good choice is x.libertyfp.org. Have you set that or something similar? If you do and run `mailman aliases` you should get things like testlist(a)libertyfp.org testlist(a)x.libertyfp.org testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org ... in postfix_vmap and things like testlist(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 ... in postfix_lmtp > Which I can do -- I've got another two or three domain names to play > with. Is it a problem to run the mailinglist on the same domain that > the machine sits on for its regular business? A lot of the errors I'm > getting seem to be from trying to do regular mail *and* the mailinglist > on the same domain. > > Now that I've installed all this stuff a couple of times, I can easily > re-install for a second virtual domain, if that's what I should be > doing. > > But, on to what's not working now... > > Unfortunately, I seem to have completely screwed the pooch on getting > postfix/dovecot to play nicely with respect to *receiving* mail. > > First, adding "virtual_alias_domains" (and putting libertyfp.org in it) > and commenting out "virtual_mailbox_domains" resulted in postfix > ignoring all my virtual mailboxes. Don't do that. Leave libertyfp.org as a virtual_mailbox_domain and don't set it as a virtual_alias_domain. I think that should work., but you may need to add hash:hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_mailbox_maps instead of virtual_alias_maps. ... > # mailman3 changes > > owner_request_special = no > always_add_missing_headers = yes > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp You shouldn't need to add hash:/opt/mailman/mm/var/data/postfix_lmtp to local_recipient_maps, but it probably doesn't hurt. > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > default_destination_recipient_limit = 30 > default_destination_concurrency_limit = 15 > virtual_alias_domains = hash:/etc/postfix/domains You don't want virtual_alias_domains. > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > #hash:/etc/postfix/virtual Everything you've posted so far says you haven't set an alias domain in Mailman for the libertyfp.org domain. Please be sure you have. -- 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: Welcome Message

by Mark Sapiro

On April 16, 2019 7:09:08 PM CDT, brian(a)emwd.com wrote: >I don't know how do that with a Docker Installation of Mailman. I >believe Python 3 is part of the container. Its not installed natively >on the server. Can you do bin/mailman shell? That would be even better. >I really am starting to hate Mailman 3. Nothing is easy with this >application. I have installed it using Docker, via Ubuntu's repos, and >now I am doing an installation of it from Source (via PiP) and there >are hurdles everywhere. If you're installing via pip you must have Python 3. Your tracebacks show a Python 3 library in /usr/lib/python3.6/ -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 years

[MM3-users] Re: Migration from 2.1 to 3

by brunol＠agro.uba.ar

> What do you mean by constantly appearing? Do you mean endlessly repeating or that they just repeat a number of times equal to the number of expected recipients of the post? Sorry, I meant endlessly repeating. This is a piece from debug after sending an email to the list from a recipient that does not need moderation: Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de264a8> Dec 27 11:41:10 2019 (11468) [BounceRunner] starting oneloop Dec 27 11:41:10 2019 (11468) [BounceRunner] ending oneloop: 0 Dec 27 11:41:10 2019 (11473) Cannot connect to SMTP server 127.0.0.1 on port 25 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.0510046+6fe6039c1b0b65672aade3bfced1aca2fe8afa16 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26e10> Dec 27 11:41:10 2019 (11470) [IncomingRunner] starting oneloop Dec 27 11:41:10 2019 (11470) [IncomingRunner] ending oneloop: 0 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26f28> Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.6512213+13fe7854257bb1a494f797f480cb10733bd440ac Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3dd44390> Dec 27 11:41:10 2019 (11469) [CommandRunner] starting oneloop Dec 27 11:41:10 2019 (11469) [CommandRunner] ending oneloop: 0 This is endlessly repeating with different filebase

5 years, 3 months

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

by Simon HANNA

> >Should I configure my private Centos7 server with subdomain >lists.labbrands.com? That's what I suggested >Doing so how do I redirect the email to the private Centos where >postfix >and MM3 are installed? This really doesn't have anything to do with mailman. There are tons of tutorials out there. Generally you should try to find answers yourself and only ask when you couldn't find anything. People are motivated to answer if they find questions interesting and think they might learn something themselves. If they think the question can be easily answered using a Google search, they are generally less inclined to respond... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

7 years, 8 months

[MM3-users] Updating from Ubuntu-20.04 LTE installation

by Peter Adebahr

Hi Mark, thank you for the fast solution of our subscription problem - which brings me to the next step: Our installation was done by "apt-get install" in Ubuntu 20, thus still running MM 3.2.2 (and python 3.8.2). Do you have any advise, how to upgrade from there to your current version? I know this might be a bit dangerous, but with today's VMs the risk is much less than it used to be: Do you think it would be possible, just to replace the code and library parts, keeping the database and config files as is? If not, what would you do when you have to keep the system running (except for maintenance time, of course)? Thank you again and and have a nice relaxed weekend Peter

4 years, 11 months

[MM3-users] Re: MM3 generates long lines?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210623 16:21]: > On 6/23/21 7:10 AM, Andreas Barth wrote: > >One question, in order to ease debugging, can I forcefully activate > >the prototype archiver from the global configuration, or do I need to > >do that on a per-list basis? > > You need > > [archiver.prototype] > enable: yes > > in mailman.cfg. I'm not sure if that's enough for existing lists. > You may need to activate the archiver per list. Thanks Mark, that's what I did. After the restart I needed to activate it on a per-list basis. However, I'd prefer to be able to do that on global basis. Not a big issue, but still thought it worth asking. Andi

3 years, 10 months

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

by Rafael Mora

Hi, I've found the MX records on my cpanel but how do I redirect the emails going to my list to my private server? I still don't get it. What if I just suscribe the members and then send the email to the suscribers the thing is that the email has to be received by mailman in order to resend it to the list suscribers right? Thanks. El mié., 2 ago. 2017 a las 13:07, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi, > > On Wed, Aug 2, 2017, at 10:57 AM, Rafael Mora wrote: > > Hello, > > > > I created a test list called: testlist1(a)labbrands.com > > > > How do I do in order to redirect the incoming emails to that direction to > > my server with MM3 ?? > > You typically need to change the DNS records for you domain to redirect > emails to your server. Particularly, MX Records are which relate to > Emails. > > I am not sure about how to do that with cPanel, but I think their > docs/support might help with DNS settings. > > > > > Thanks > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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

7 years, 8 months

[MM3-users] Re: Verification links to localhost

by Lars Bjørndal

Hi, and than you for your quick reply! You wrote: > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1]lars(a)lamasti.net> wrote: > > The verification link I get back when trying to add an account, referes > to localhost, e.g. > > To confirm this is correct, go to [2]https://localhost:8000/accounts/ > confirm-email/Mw:1... > > Where do I change that? > > > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings? I don't have this variable anywhere in /etc/mailman3. However, I found it here: ./venv/lib/python3.10/site-packages/mailman_web/settings/mailman.py:POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' In which config file should that variable be set, and how do I set it so that mailman can works for multiple domains? Thank you. Lars

2 years, 2 months

[MM3-users] Mailman3 OOM and high CPU usage

by Stephen J. Turnbull

Prasanth Nair writes: > Our Mailman3 server crashes with OOM and high CPU usage. As soon as we > start the mailmanweb service (uwsgi process), the system crashes. It was > working fine, but this issue started recently. We haven't changed any > recently. > > Any idea how to fix this? You're not giving us anything to work with, except "get more memory for the server". > or any suggestions? By "system crashes" do you the Mailman system, or does it take the OS with it? By "no changes" do you mean no change to Mailman, or do you mean *nobody* has touched *anything* on the system recently (no new applications, no upgrades of existing applications or system daemons, etc)? Tell us system resource limits. Limited CPU should not cause a crash, and I'm not aware of reports that CPU was a limiting factor in a Mailman problem. But a Mailman 3 system needs at least 2GB of memory to function properly unless you're really crafty about configuring it, and 4GB to be really comfortable. Do you have swap enabled? If not, 2GB-4GB of swap should get you past the crash, although if there really is that much memory pressure performance will probably be terrible. Check mailman.log, mailmanweb.log, error.log (usually in .../mailman/var/logs). I don't know what you're looking for, so start by looking at many pages of logs when mailman was working normally. Then look at the recent ones when it started crashing, and just report "anything that looks different". Check memory usage and CPU load just before starting mailmanweb. Steve

2 weeks, 4 days

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. ``` Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is ``` Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Mailman3 not delivering list mail

by Mark Sapiro

On 10/1/20 9:27 AM, Gordon Dickens wrote: > It appears that my mailman3 installation has stopped delivering list > mail and that all of the list mail is stuck in > /var/lib/mailman3/queue/bad. > How do I resolve this situation?Â Can I just remove the files with "rm > *" in the /var/lib/mailman3/queue/bad directory?Â Please let me know > what I should do to get things working again. There should be messages in mailman.log like `Uncaught runner exception:` followed by an exception and traceback and possibly `Skipping and preserving unparseable message:` or `SHUNTING FAILED, preserving original entry:`. What do these messages say? -- 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: Changing subscription address

by Abhilash Raj

> On Mar 18, 2021, at 8:29 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Thank you for your comments, Allan! > > Allan Hansen writes: > >> On 3/15/21, 21:28 , "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >>> In the 'Mailman Settings' screen, List-based Preferences' tab, > >> You may mean the 'Subscriptions' tab. > > I did mean the 'List-Based Preferences' tab. The 'Subscriptions' tab > is non-functional. It's in some sense aesthetically more pleasing > than 'List-Based Preferences', but you have to do extra, unnecessary > work to get anything done from the 'Subscriptions' tab. It may make > sense to just get rid of the current 'Subscriptions' tab and rename > 'List-based Preferences' to 'Subscriptions'. +1 We can do that. I don’t think I’ve ever used the subscriptions tab myself to do anything. > > The only functionality of 'Subscriptions' over 'List-based > Preferences' is that it lists you once for each role and address > (member, non-member, moderator, owner) that you have for that list. > This is possibly more confusing than helpful for non-owners. > Moderators get informed of their role every time they need to do > something. And it's possible to be both a member and a non-member of > a list, which is pretty confusing. Yeah, technically you can be subscribed to a list with all possible roles at the same time. > >> Under 'User profile for <name>', under the 'E-mail Addresses', add >> button to ensure that 'Primary E-mail' is used for all lists. > > If you define "ensure" strictly, this would be a fair amount of work > because it would require overriding the normal "cascade" of > preferences, and incidentally a way to turn off that override. I'd > rather not make the implementation so complicated. > > There does need to be a way to revert each option to inherit, and > there currently doesn't seem to be one. The 'Preferences' interface I > described in the previous post doesn't provide it either. I will > think about that. The implementation of this isn’t very difficult, but the UX of this is something I don’t know how to implement in that page to be very honest. > It should be normally unnecessary to use the 'Preferences' interface, > because the default subscription should be "use primary address". For > people using the current versions of Mailman 3, who are already have a > bunch of subscriptions with the same *explicit* address, I think it is > good enough. But if there's demand for a "revert all to use primary > address" button, that would be easy enough to add. We do already have ability to switch from an explicit address to Primary Address subscription. I would imagine it would be more than just a button, but more like a dropdown to choose an email or primary address and switch all subscriptions to that. > Here's why I think such a button would be unnecessary in future > versions of Mailman. What should happen if you subscribe by an > address not already known to Mailman without creating an account in > Postorius is > > 1. Mailman registers the address. > 2. Mailman creates a User object to "own" that address, and makes > that address the primary address for the User. > 3. Mailman creates a subscription which links the User (not the > address) to the mailing list so that the primary address is used. > > For addresses already known to Mailman, Mailman should look up the > User registered to that address, and if the subscription address is > the primary address, set "use primary address" for the subscription. This is how Core actually does work[1] if you subscribe via Email and you already have a primary address. It will lookup a user using the address and if the address is the primary address of the user, it will subscribe the primary address. However, if it isn’t the primary address, and this is a new address, it will subscribe the address instead of user because the address isn’t verified at this point and hence can’t be a primary address. We could extend the subscription workflow to add an additional step to set this address as primary and subscribe the primary address. Postorius has the full ability to define its own workflow because REST API provides full expression capability and doesn’t enforce anything. Previous versions didn’t had support for subscribing as Primary Address, but that has since changed and is the default one in the dropdown. This is for authenticated subscription, the anonymous subscribe works similar to email -join command. Mass-subscribe is probably working the same way. [1]: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/eml_m… > > In this scheme, as far as I can see, your user doesn't need to do > anything with the account until she wants to change the address. At > that point she needs to activate the account: > > - visit her personal options page in Postorius > - request a password reset (she doesn't have one yet, so she can't log > in) > - click the special link > - set a password or link a social media account, and > - finally change the address. > > Note that this is the bare minimum of work for her. She has to prove > she can read mail at that address. Anything less, and *anybody* can > change her subscriptions. We could omit requiring a new password, > but it's not a lot of work once you've got to this point, while the > "request, wait for email, click link, do work" dance is pretty > annoying. Why make someone do it again next time? > > This is problematic if she's already lost access to the old address, > of course, but in that case you're probably going to have to intervene > anyway. > > I don't think Postorius requires her to do anything else, but if she > wants to she can update her profile at that point. > > I have to check the code, and probably also ask Barry and the other > folks who designed the current subscription mechanism in case there's > some fatal flaw in the scheme above. But I think that should do what > almost all "one address" users want, and it's probably what the > majority of people who have multiple addresses and use different ones > for different purposes want most of the time, too. Like mentioned above, it should be possible to do what you suggest. I am getting into the implementation details here, but the Subscription workflow would need an additional flag that would verify an address and use the flag to determine if it should subscribe the address or addresses’s user if an address is provided to the workflow. > > Note to self of possible problems: (1) The primary address is where > you would send administrative mail to the account holder and that > might not be an appropriate address for the default subscription. > (2) This is a pretty radical change from the current situation, so it > might need to be an option for the list or domain owner. > >> And, indeed, new subscriptions should default to 'Use Primary.' > > I agree. I'm astonished that there are situations where they don't, > to be quite honest. That's the whole point of having accounts in the > first place -- having *one* source of information about the user > rather than spreading it out over a bunch of lists. > >> Is that possible now? > > It is already the default for someone who subscribes by logging in to > Postorius. I assume that it is *not* the default for someone who > subscribes by email or mass subscription, otherwise you wouldn't have > the problem. > >> Does a member have to have an account for me to set it up thus for >> them? > > Yes. The primary address is an attribute of the account. > Subscriptions can't know anything about a primary address unless there > is an account. However, it should be possible to make this default > for an account that hasn't been activated yet, such as in a mass > subscription. Primary Address is also an attribute of the Mailman User, so it should be possible for an admin to set that for a user if the user doesn’t have an account. When they sign up, they’d be able to manage and update accordingly. I have started working on designing a User management page[2] in Core which should make it easy for superuser to manage several things about a User, including the ones that don’t have an account in Postorius to manage their own. The list os “tasks” an admin can do isn’t decided, but please feel free to write comments there about things you’d like to be able to do as a server admin. [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 > > Regards, > Steve > > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] funding MM3 development

by Stephen J. Turnbull

John Griessen writes: > Maybe this non-profit foundation could help MM3? It's helping > pcb-rnd now... It seems like well documented to do lists are what > they like to fund --> "I am announcing a great news that is going > to change pcb-rnd development, advancing it to the next level: with > the help of NLnet, through the NGI0 PET fund, main pcb-rnd feature > development is fully covered for a long time financially." Thank you for the suggestion, and the reference to the fund. I've made a note of it. Things is, right now funding isn't a problem, it's much more people. We have always gotten all the Google Summer of Code students we ask for, for example, but this year we ended up bailing out of GSoC for lack of mentoring time. None of the core people are in a position to do more work if we got paid. If there are consultants out there who use Mailman, are somewhat familiar with its internals or are experienced Python programmers (preferably with knowledge of zope components like Interface), and would be able to provide time for money but not without pay, feel free to speak up, maybe there's a deal to be made, if you can contribute enough time to make the pitch. But soliciting money, soliciting bids, etc, all takes time for the Mailman core devs who have very little right now, and honestly, it's not work we enjoy. Even mentoring new devs (even if they'll probably disappear as some GSoC interns do :-), which several of us do enjoy, isn't really in the cards right now. Steve

5 years, 1 month

[MM3-users] Re: REST API Question: possible to change user preferred email?

by Abhilash Raj

On Fri, Mar 15, 2019, at 10:59 AM, Nathan Dixon wrote: > Hi, > We are in need of being able to change a user's email address via the REST > API. After looking through the documentation and code, I can't see a way to > do this in a simple way. > > Although the documentation seems to show that if a user changes their > preferred address, it will track throughout all their subscriptions. It depends on how are you actually using Mailman. Postorius today subscribes people using their addresses, so the method you mentioned below is the correct way to change addresses. If you think you are going to do this more frequently, you could subscribe users with their user_ids and then when you need to change their memberships, you just update their preferred_address. See [1] here for how to join a mailing list using user_ids. Note that this isn't available today using Postorius (our Web UI), but I'd be happy to work with you if you want to contribute it. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.h… > > See: > https://gitlab.com/mailman/mailman/blob/master/src/mailman/rest/docs/member… > "When Gwen changes her preferred address, her subscription automatically > tracks the new address." > > The only way I can see to do this via the REST API would be to do the > following long winded way: > > *1. Create a new address:* > POST to http://<api_url>/3.1/users/<$OldEmail>/addresses > $postData: {email = "$NewEmail"} > > *2. Verify the new address:* > POST to http://<api_url>/3.1/addresses/<$NewEmail>/verify > $postData: { } > > *3. Get all the memberships for the old email address* > $memberships = GET to http://<api_url>/3.1/addresses/<$OldEmail>/memberships > > *4. Change users email for each membership individually* > foreach ($membership in $memberships) { > PATCH to http://<api_url>/3.1/members/<$membership.member_id> > $pathData: { address = $NewEmail } > } > > *5. Delete Old Address* > DELETE to http://<api_url>/3.1/addresses/<$OldEmail> > > Am I missing something (as in there is a way to do a single PATCH request > somewhere)? Or is this the only way to update someone's email address with > these 5 steps? > > Thanks, > Nathan Dixon > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 4:16 PM, maszap(a)tin.it wrote: > Hi > My mail.log > > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: 276C0C202B7: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: 276C0C202B7: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: 276C0C202B7: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: from=<admin(a)pratico.work>, size=586, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: C3A57C20D52: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: C3A57C20D52: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: C3A57C20D52: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: from=<admin(a)pratico.work>, size=1610, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia amavis[1566]: (01566-01) Passed CLEAN {RelayedInbound}, [127.0.0.1]:36322 <admin(a)pratico.work> -> <admin(a)pratico.work>,<info@pratico$ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<admin(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, $ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<info(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, d$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Connect from local > Jul 13 01:15:12 gamelia dovecot: lmtp(admin(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored $ > Jul 13 01:15:12 gamelia dovecot: lmtp(info(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg:2>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<admin(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.0$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<info(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.01$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Disconnect from local: Client has quit the connection (state=READY) > Jul 13 01:15:16 gamelia dovecot: imap-login: Login: user=<admin(a)pratico.work>, method=PLAIN, rip=173.249.18.220, lip=173.249.18.220, mpid=1983, TLS, session$ > Jul 13 01:15:16 gamelia dovecot: imap(admin(a)pratico.work)<1983><IiFCv0aqJoyt+RLc>: Logged out in=297 out=5915 deleted=0 expunged=0 trashed=0 hdr_count=11 hd$ The issue here is the message is being delivered to Dovecot via LMTP rather than to Mailman via LMTP. See this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > sudo mailman conf -s logging.smtp > > [logging.smtp] datefmt: %b %d %H:%M:%S %Y > [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds > [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg > [logging.smtp] format: %(asctime)s (%(process)d) %(message)s > [logging.smtp] level: info > [logging.smtp] path: smtp.log > [logging.smtp] propagate: no > [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures > [logging.smtp] success: $msgid post to $listname from $sender, $size bytes With these settings, posts should be logged. They aren't because no mail is delivered to Mailman at all. The Mail that local users receive doesn't come from the list. It comes from Dovecot. -- 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: config incoming email in my domain cpanel

by Abhilash Raj

Hi, On Wed, Aug 2, 2017, at 10:57 AM, Rafael Mora wrote: > Hello, > > I created a test list called: testlist1(a)labbrands.com > > How do I do in order to redirect the incoming emails to that direction to > my server with MM3 ?? You typically need to change the DNS records for you domain to redirect emails to your server. Particularly, MX Records are which relate to Emails. I am not sure about how to do that with cPanel, but I think their docs/support might help with DNS settings. > > Thanks > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 8 months

[MM3-users] There are currently no mailing lists!?

by Christian

I recently upgraded Debian 10 'buster' and when I logged in to Postorius in the browser I got the ' Mailman REST API not available. Please start Mailman core' message. So I started it up from the command line doing 'sudo -u mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded Starting Mailman's master runner Generating MTA alias maps mailman@lists: Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists' in my browser I get the message ' There are currently no mailing lists.' Meanwhile their archives exist. Are the lists actually gone or ? What am I doing wrong/what's going on here please? Thank you in advance. One more thing...I am running mailman core version GNU Mailman 3.3.5, Core API Version 3.1, and Core Python Version 3.7.3.

9 months

[MM3-users] Re: Outgoing STMP services? IP reputations?

by Brian Carpenter

On 4/3/20 3:03 PM, Seth Seeger wrote: > Hello everyone, > > Forgive me if this is the wrong list. > > I’m curious to hear what users are doing for MM3 hosting and what you are using for outgoing services. > > I am hosting a Mailman3 installation for a community that I am part of, and we have 6 lists which generated 136,000 outgoing emails last month. I’m currently hosting this on a 2-core 4GB RAM EC2 (t3a.medium) instance at Amazon. I went with Amazon because their outgoing email relay (SES) is free for the first 62,000 emails/month. (I didn’t do my homework - I thought that would be plenty!) I’d much rather be hosting on Linode, since their setup is waaaaay simpler and easier to understand. > > I went with an SMTP service so that I wouldn’t have to deal with managing an IP address reputation…. (Any other SMTP relay service besides the Amazon SES/hosting would cost >$80/month.) > > Do you use an SMTP relay service? > Do you just send directly from your VM’s IP address? > Do you have trouble with getting black listed? > What have you done about your IP address reputation? > Is DKIM and SPF enough to get past an IP address without an established reputation? > > Thank you! > Seth > _______________________________________________ > 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/ Hey Seth, We run our Mailman 3 servers on Linode's platform. IP reputation is something we deal with all the time due to our Mailman 2/3 hosting service. I don't find it a pain at all. IP reputation can grow quickly as long as your lists are not generating a high number of bounces. We have found a high bounce rate is very bad for IP rep. There are some ISPs that will block new IP addresses that start suddenly sending out mail but we find it is easy to get off of those type of block lists. The general recommendation is to start slow with mail volume but I know that can be hard in some circumstances. For our clients SPF/DKIM has been enough and we make sure all of our lists are running some sort of DMARC mitigation. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/20/20 11:19 PM, Mark Sapiro wrote: > On 10/20/20 6:54 AM, Brian Carpenter wrote: >> Respectively, I think you are asking the wrong question here. The real >> question is why isn't a display_name being removed when a list >> subscriber is unsubscribed. > > I'd like to understand the real requirement. It seems to me that this > issue has come up because a list admin wanted to change the display name > shown in the membership roster for a user. Since there is currently no > UI to do this, the list admin tried to do it by unsubscribing and > resubscribing the user. That didn't work which led to this > "unsubscribing a user should remove the user's information" thread, but > the real issue is the lack of a UI for changing display names. It seems > if that UI existed and was available, the "unsubscribing a user should > remove the user's information" issue would never have been raised. There are two real requirements. One is to be able to do something as easy as changing a name for a list member. I did a lot of testing with the relationship between a name used for a subscription versus a name used for registering via the U.I. (Postorius/Django) and it is very confusing. I still am having a very difficult time understanding the logic presented here for the way Mailman 3 handles user information. The second requirement is ALL data should be removed if someone unsubscribes from a list that is just a list member of a single list. I feel very strongly about that. I don't really care for the reasoning behind why the data is retained. I just think it should be removed for a list member who has no need for an account that manages multiple email address and is subscribed to multiple lists. I host many single lists. So it is very important to me, and as an advocate for my clients, I will state very clearly how important it is to me (and my clients) regards of other user scenarios out there (looking at you Mr. Turnbull). I care about my own. > So perhaps what we should be talking about is UIs for changing user > information, what they would look like and who should be able to change > what. That is a start and I thought I brought that up. We also need a separate conversation on the retention of data apparently. > Note that I personally am a member of many lists, an admin of multiple > lists and a site admin for multiple mailman installations. I am well > aware of the frustrations of list admins who wind up just doing it > because it's way easier than instruction some users as to how to do it > themselves. However, I don't think that is necessarily sufficient reason > to hand over control of global, non-list specific user information to > the admin of one particular list that the user happens to be a member of. I never asked for global control for list owners. You have made that almost a necessity with the multiple email address per user account feature that you brought in. I don't think List owners should have global control but server owners certainly do. But the rightful avoidance of such control for List owners, I think has resulted in a wrongful limiting of what they can do currently. I so disagree with S. Turnbull's disparaging comments that I think we ought to be designing for List owners primarily and not list members/users when it comes to user interfaces. From what I see, it is mostly server and list owners that are interacting with this (mailman-user) list and not list members/users. In my experience, I never hear from list members. Just list owners. Whatever issue list owners have with their own list members are easily handled by them when it comes to Mailman 2. Not so much with Mailman 3. > > Even in mailman 2.1, while a list admin could go to a user's options > page for the list and change things, the "change globally" check boxes > only worked for the user, not for the list admin. > -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] requiring questionnaire from new users

by Stephen J. Turnbull

Ethan Furman writes: > Is there a way to require new users to answer a questionnaire when > they subscribe? You could have it in the Postorius signup page template itself (see discussion below), but there currently is no way in Mailman to communicate that information to the moderator. Without modifying Mailman, you could have a separate signup page that invokes a Python program that notifies the admins and collects arbitrary data, as well as passing the normal subscription information to Mailman core for the normal address validation and moderator approval process. I have not done this myself, but a number of organizations have reported successfully creating alternative signup mechanisms (I haven't heard of this one). Such a signup page is the approach I'd recommend if the questions you have in mind would get free-form responses. Unfortunately, I do not believe the questionnaire responses could be displayed in the normal list admin interface without patching both Postorius and Mailman core, so this communication would have to be outside the normal procedure (but you would still use Postorius/core for the email validation and moderator approval steps). Perhaps one of the other devs has an idea about integrating it with the normal interface without patching. > I suspect that one of the lists I manage is getting a lot of > subscribers who don't understand what that particular list is for, > and having to answer a question or two would allow me to direct > them to better resources. I'm not sure how you want this to work. I guess you're getting this suspicion because new posters are posting a lot of off-topic stuff? So you want to have a subscription process where the moderators approve all subscriptions, and they would see the questionnaire responses in the subscription approval request? Not sure how well a simple questionnaire would capture this problem (see below), but it could help a lot, too. An alternative that doesn't inform the moderators is to modify the signup page template to (1) require the user check off the description of the list point by point (like a TOS notice, this is obviously not an improvement from the well-informed subscriber's point of view, though) and (2) provide links to commonly suggested alternative resources in the page template (these might be useful even to well-informed subscribers). The page templates are standard Django, so I'm sure that there's some facility for this. For example, if you were talking about python-dev, you could have Do you want to participate in implementation-focused discussions about work in progress to improve the Python language and its standard library? ( ) yes ( ) no If you answered 'yes', welcome! Do note that the focus is narrowly on implementation, and Python provides <a>many other venues</a> for new <a>ideas</a> and special interests like <a>distribution</a> and <a>documentation</a>. If you answered 'no', consider others of our <a>many lists</a> and our <a>Discourse channels</a>. - Do you want to discuss the best way to write a program in Python? ( ) yes ( ) no If you answered 'yes', <a>python-list</a> is probably a better venue for that. - Do you have a bug to report? ( ) yes ( ) no If you answered 'yes', please report it on the <a>issue tracker</a>. Discussion will take place there in any case, and you can attach a patch there if you have one. - Do you want to discuss a new idea to include in the Python language or standard library? ( ) yes ( ) no If you answered 'yes' but don't have a complete patch yet, <a>python-ideas</a> is probably a better venue for you. If you do have a patch, you should post it as a merge request on <a>GitHub</a>, too. This approach could get REALLY tedious (core-mentorship, scads of SIGs, etc). I think you'd have to add your own Javascript if you wanted to hide each recommendation until the new subscriber checks 'yes', but that would alleviate the annoyance quite a bit, I think. The only hitch is that I'm not sure Postorius wouldn't glitch on the extra information from the page, but even if so, that can probably be dealt with (a form without a submit button?) Regards, Steve

3 years, 8 months

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

by Stephen J. Turnbull

Kimmo L writes: > But i have one small question more about hyperkitty. I have one > list, which is quite heavy loaded and contains a lot of data. I'm not sure what you mean by "heavily loaded" (I guess the HyperKitty processes are using a lot of CPU?) or "a lot of data" (number of posts? MB?) However, 5-10 minutes to "open" the list (what do you mean by "open"? display the top page?) is not acceptable. Beyond that, it's hard to diagnose with the information you've given, as HyperKitty has a number of options that affect performance. You can help us by doing a little research: searching in the archives for this list and in mailman-developers(a)python.org for "HyperKitty performance", "HyperKitty slow", and "HyperKitty speed", and doing the same in the HyperKitty issue tracker at https://gitlab.com/mailman/hyperkitty. Also, some configuration options that are known to affect performance of some HyperKitty operations: 1. The search engine. IIRC, Xapian is known to be relativeli fast, Whoosh is relatively slow. 2. Configuration of caching (redis). 3. Configuration of queues. When you come back with more details, you should provide full configurations for your HyperKitty installation, and tell us what your web stack (webserver, any additional Django middleware) is. Note: You may post entire configuration files here, but you should redact sensitive information since this list is publicly archived. If you're not sure how to do that, or what is sensitive, you can negotiate sending them directly to one or more of the other developers -- I'm not very useful, I've already told you everything I know because my HyperKitty is small and just works. ;-) Steve

3 years, 10 months

[MM3-users] Re: sending messages in response to posts from non-members

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > On 2/26/22 04:26, David Bremner wrote: >> >> I'd like to turn off the "bounce messages" sent by mailman to >> non-members. My reasoning is that most such posts are spammers, and >> often use forged return-paths / From's, so I end of sending steady >> stream of backscatter to amazon.com etc... >> >> Is this configurable (without postorius) somehow? > > What exactly do you want? Do you want to discard without notice any > nonmember posts or do you want to hold them but not send a notice of the > hold to the poster? It was the latter, and your suggestion for existing lists seems to have worked. Thanks, David

3 years, 1 month

[MM3-users] template head/footer questions.

by bob B

I migrated from mailman 2 to mailman3 and had head/footer questions. In the mailman 3 GUI see the templates section, so where do those files get edited/stored? I added a footer to a list via the GUI, but I do not see it in: /var/templates/lists/[listNAME]/en I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. Bottom line, I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? is this directory leftover from migrating from mailman 2 to 3? I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option.

3 years

[MM3-users] Re: Hyperkitty

by Mark Sapiro

On 1/30/23 11:58, Onyeibo wrote: >> 2. Your MM3 log files - do they say anything? >> > Nothing! No new errors. It is very strange and frustrating Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/? Do messages received from the list have an Archived-At: header:? Do messages received from the list have a List-Archive: header:? If the first answer is yes, the mailman_hyperkitty archive_message method is failing. If the second answer is no, the mailman_hyperkitty permalink method is failing. If the second answer is no, the mailman_hyperkitty list_url method is failing. All of these failures log errors to the mailman.archiver log which by default is written to mailman.log. If by chance there is an Archived-At: header, what is it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: sass error

by Alexander Klotz

Am 19.04.18 um 16:41 schrieb Mark Sapiro: > On 04/19/2018 02:41 AM, Alexander Klotz wrote: >> Hi everybody, >> >> we tried to make a fresh installation out of the current version >> following the readme.md - we encounter the following error trying to do >> so. As mentioned elsewhere, 'sass' has been replaced by 'sassc', >> however, maybe somewhere there is still a reference to it that may have >> been overlooked? The answer to a similar error posted to this list in >> August 2017 unfortunately didn't help either. > > > What do you have in your Django settings for COMPRESS_PRECOMPILERS? > > Do you actually have sass or sassc installed? > Hi Mark, the error was indeed in our local django setting, it still said "sass" on there - sorry and thanks! Regards, Alex

7 years

[MM3-users] Re: automation of mailman3 core startup

by Mark Sapiro

On 5/27/20 7:41 AM, Ralf Wiegand wrote: > |Question: The above assumes that the user mailman will run the mailman3 > core application. So the user "mailman" has all the correct > permissions. The issue I have is to automate this part, so at start up > mailman3 will be running, at shutdown, being shutdown properly. There is a sample systemd script at <https://wiki.list.org /DOC/Mailman%203%20installation%20experience?action=AttachFile&do=view&target=systemd_mailman.txt> and a sample init script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> Both of these refer to /opt/mailman/mm/bin/mailman a sample of which is at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> -- 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: Patch/kludge suggestion and a question on adding accepted addresses

by David Krantz

On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: > On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>I'd suggest adding a catch for AttributeError similar to the one for >>KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my >>immediate problem at least. I run the version from git with the tag >>263711b3b7988c7c474e3b8952dc7e0f02f04fa2 > > Can you file a bug and attach either the problematic message or the traceback? Will do. I have lost the message (I was too quick in removing it), but I of course still have the stacktrace. And I have a patch for my kludge. > Did you talk to your MTA's SMTP port, to Mailman's LMTP port, or some other > process? It matters because LMTP is the way messages get from the upstream > SMTP daemon (e.g. Postfix, Exim) into Mailman, and the LMTP server rejects any > messages that don't have a Message-ID. It was to the SMTP port of the MTA. I can try to recreate it although I have better filters now so it might be difficult to get passed to mailman. >>I have another question: In the old mailman you could add accepted >>senders without adding them to the list. Is that possible in Mailman >>3/Postorius? > > You do this by creating a "nonmember" subscription for the sender, and then > setting that member's moderation_action to Action.accept. Okay. I see no way of doing that in my instance of Postorius but in this case it is okay to do it in the command prompt. cheers, // David

7 years, 11 months

[MM3-users] Re: Turn off social logins?

by Torge Riedel

Am 12.02.19 um 17:11 schrieb Stephen J. Turnbull: > Note: I've changed the order of sentences from Torge's post to fit my > responses. > > Torge Riedel writes: > > > I do agree, same here on my side. Lot's of my users are very > > "sensitive" to social media and don't want see them here. > > This is the first I've heard of this. Obviously it's fairly > widespread; *please* speak up if anyone have similar issues that we > haven't addressed. AFAIK all of the currently active Mailman > developers believe that social auth is a GoodThang[tm], so we're > unlikely to DTRT as you see it without your help. Well most of my users are 60+ so social media is some kind of a thing from hell for them ;-) I don't want to blame it, but to ensure acceptance in my scenario it is required to hide them somehow. > > > I need to migrate from mailman2 to mailman3 and was wondering why > > social accounts are enabled by default > > By default Mailman 3 is social media: you have a profile, you can be > searched in the indicies of the archives, and so on. The large auth > providers provide more secure authentication, and a lot of convenience > for users who have such accounts already. They also take some > administrative burden off the list and site managers when people lose > their passwords and forget what their subscription address is, and > similar scenarios. Clearly, these are not universally-valued > features, but I think that they justify the current defaults. Yes, this was a bit unprecise. For my feeling it is better to enable one after another, but it is ok for me to do it the other way. > > > and are difficult to disable. > > They're easy enough to disable (easy to recognize and just add a hash > character in front), since you have to edit settings_local.py to > install anyway. If you're using a packaged version and the package > configuration utility doesn't handle it, there's nothing we can do > about it. The distro will have to deal with that. > > It should be better documented, I imagine (haven't checked yet). > > > I propose something like an additional setting listing the enabled > > social accounts. > > Do you mean in the Postorius administration interface? If so, do you > want it by-site, by-domain, or by-list? ("You" is everybody who wants > to disable social auth, not just Torge!) > > If you mean in settings_local.py, I suggested something similar > earlier. It's not obvious it would be easy to do (sometimes these > things are order-dependent, though that's bad practice). Having the configuration in the UI would be the best solution. So not everything needs to be done by me. A first approach is the mentioned setting, which can be set to an empty value to overwrite the default. Without the risk to break something else. Just to repeat. > > > And if the admin is setting this to an empty value in the > > settings_local.py everything is disabled > > Because the settings are a Python module, this is the way > settings_local.py works anyway. That's why Mark suggested editing > INSTALLED_APPS. > > Thanks so far for going into the discussion.

6 years, 2 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Mark Sapiro

On 7/23/20 12:38 AM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > I understood that gunicorn is a front end that is used like web server like > nginx. > > But I don't think I am using it instead I am using the httpd to redirect > requests to postorius. Steve has addressed this. > So, in this case, do you think configuring gunicorn as below would work: You do need to configure gunicorn timeout to solve your issue. > *calling gunicorn.cfg in mailman.cfg as below * > > *[webservice]* > *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* Do NOT do this. Make your own gunicorn.cfg outside of /var/lib/mailman/mailman/src/mailman/ and point to that. Otherwise any upgrade will reverse your changes. > > *and content of gunicorn.cfg as below* > > (venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg > [gunicorn] > # All the options that can be put here are available at > # http://docs.gunicorn.org/en/stable/settings.html#settings > # No of seconds to wait before killing the worker processes. > > workers = 4 > graceful_timeout = 90 > > Also what is the difference between timeout and graceful_timeout ? graceful_timeout is not what you want. It addresses something different. As it says in the comment, all the gunicorn settings are described at <http://docs.gunicorn.org/en/stable/settings.html#settings>. timeout and graceful_timeout are near the bottom of that page at <https://docs.gunicorn.org/en/stable/settings.html#timeout> and <https://docs.gunicorn.org/en/stable/settings.html#graceful-timeout>. -- 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: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 10:22 AM, Nathanael Schneider wrote: > > I then created a completely new List which did not exists in mm2.1, > subscribed two addresses and sent myself an EMail. That one worked as > intended. I then deleted the whole broken list and created it cleanly, > added the same two people, sent an email and nothing. This seems strange. If I understand, you are essentially saying the two lists are the same. I.e., you created a completely new List which did not exists in mm2.1, and that one worked. Then you deleted the whole broken list and created it cleanly ... What was different between this cleanly created list and the completely new List? > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net The fact that these are the only messages says that the attempt to send that message via smtp raised no exception as exceptions would have been logged, yet you say there's nothing in the maillog so there was no connect to Postfix. What are your settings for smtp_host: and smtp_port: in the [mta] section of mailman.cfg? ... > I have no clue what to do with this. I then turned the debug module > loglevel to debug. Also nothing useful. Just an endless list of > > [...] > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop > May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 > May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: > 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd > May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic > May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction > May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit > May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 > May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: > 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > [...] > > Which also tells me nothing I can understand. It says the message in queue entry 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled but gets requeued as 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which presumably is handled and requeued again ... > I have no clue what's > going wrong. (I've turned on debugging both on the original member list > and the reduced member list. Both hang on the first delivery they do). > If I restart mailman, the message gets correctly shunted as it is > interrupted mid-delivery. My maillogs don't register any activity beside > the listpost. Any ideas what I need to do to figure out what's not > working here or where the culprit could be? Not sure if it is related to > the mailinglist being in mailman2.1 before. I have no real understanding of why this isn't working. I don't think it's likely that it has to do with the mailing list being imported from MM 2.1, but I suppose it could be. How did you create and import the list? When you say you deleted the whole broken list and created it cleanly, what did you actually do? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I'm logging with the mailman user and it says that it sent a confirmation email to my email account, but I don't see any activity in postfix with 'tail -f /var/log/maillog' command What do you suggest??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

7 years, 8 months

[MM3-users] Re: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:47, bob B via Mailman-users wrote: > Mark, > > Thanks, So how do I check the version of mailman-hyperkitty? I thought that was the HyperKitty version 1.3.5. that was displayed in the web interface, but I assume that mailman-hyperkitty is something different? Yes. mailman-hyperkitty is a shim between Mailman core and HyperKitty. Your mail message has `` File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message` ``` The fact that it is line 154 says it is 1.1.0. You need to upgrade mailman-hyperkitty. I don't know how to do that in your Docker container. If you can run pip ``` pip install --upgrade mailman-hyperkitty ``` should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Search results for query "dO"