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

[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, 10 months

[MM3-users] Re: Problems with New MM3 Installation

by Abhilash Raj

On Tue, May 11, 2021, at 8:43 PM, Mark Sapiro wrote: > On 5/11/21 7:46 PM, Jeff wrote: > > > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > > > 1) some emails that arrived before I got the archive working are still sitting in: > > > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > > > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > > > /usr/local/mailman3/mm/var/queue/shunt > > > > What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > > > 3) Similar to above, some messages are in: > > > > /usr/local/mailman3/mm/var/queue/bad > > > > How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > > > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. Using the full external URL should work. Core doesn’t speak uwsgi protocol so the uwsgi:// URL won’t actually work. I am starting to think it was a very bad idea to use uwsgi in the official docs :( -- thanks, Abhilash Raj (maxking)

4 years

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

by Brian Carpenter

On 2/26/21 10:00 PM, Stephen J. Turnbull wrote: > Thank you for going to the trouble of making your guide easily > available to and usable by the community. You're welcome Steve. > Yes, and we try to document them all, written by different people at > different times. I don't think that's an unreasonable approach given > the wide variety of situations of our site admins, but I'm sure a lot > of "greenfield" installations will appreciate your thorough, "from > parts manifest to assembled working system", approach. I agree. I just know there are probably a lot of folks who just want a working and current Mailman 3 server and are not picky over the actual server environment. Mailman 3 is really dependent upon being connected to a number of services: web server, database server and MTA for instance. Then you add in all of the required Python modules, and you have a really complicated system that has a lot of moving parts. I intend to explore other OS for installing MM3 and to document that process as well. I will not document the process of using package managers (apt/yum) etc to install Mailman 3 itself because I think it is very problematic having older versions of Mailman 3 set up. Mark Sapiro put it very well when he said: > Mailman 3 is still relatively young and there are many important > features and fixes in the current releases that aren't in the > Debian/Ubuntu packages. I hoping a guide such as mine will move folks away from using a Debian repo for Mailman installations. > Yes, it has been a problem. At this point I'm pretty sure :^þ that > mailman.readthedocs.io is the official guide, but that hasn't been > well-known in the past and there are a lot of mirrors and unofficial > guides like yours (but not as thorough). And there's a lot of stuff > on the Wiki that requires effort to integrate because it was > originally written in reply to a particular user's questions. See that is something I am very interested in fixing and cleaning up but I need help in knowing how to work with something like Readthedocs.io. > Sphinx is pretty much the gold standard for Python documentation. It > looks nice. The markup is reStructuredText, which is a powerful, > Markup-like language with a few features that Markup didn't have last > I looked, and it's extensible by Python programmers. It's also used > in marking up Python docstrings. So you can see why we'd choose it. > But if you're *not* an experienced Python programmer, none of those > are advantages. Exactly! > > > I am just trying to understand how can we lower the barrier for > > > community members to help contribute to existing docs instead of > > > them having to create new ones. Specifically around installation, > > > since that tends to get stale often when depedent packages change > > > or a new dependency is added that breaks the installation. > > @Abhilash: For non-Python programmers, it's not *that* hard, but there > is a hurdle at the beginning. So lift me up and throw me over that hurdle. > I think the best thing to do is to advertise that we're always looking > for doc contributions, and that if somebody's not familiar with reST, > they shouldn't let that stop them. Of course we'll help them with > markup, and if necessary we'll do it. "Raises hand here" -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Default values for lists in Mailman 3

by Markus Grandpré

Dear Mark, dear list, in Menu "Mass Operations / Mass Subscription" I have set the default value for checkbox "Invitation" in file </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on Debian 12) as you had suggested: invitation = forms.BooleanField( label=_('Invitation'), initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' 'be sent an invitation to join the list and will be subscribed ' 'upon acceptance thereof.' ), widget=forms.CheckboxInput(), ) However, administrators of mailing lists on our Mailman3 demo system report that the invitation is still sent, even if they have deactivated the sending of the invitation via the “Invitation” checkbox. What have I done wrong? Best regards, Markus Am 20.09.24 um 09:05 schrieb Markus Grandpré: > Thank you very much for your answer. > > Best regards, > Markus > > Am 19.09.24 um 22:03 schrieb Mark Sapiro: >> On 9/19/24 05:46, Markus Grandpré wrote: >>> Dear list, >>> >>> I would like to activate the invitation setting for all lists as >>> default. In Mailman 2.1 I have done this in the file </etc/mailman/ >>> mm_cfg.py>: >>> >>> >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> >>> >>> How can I do this in Mailman 3? >> >> There is a draft merge request at https://gitlab.com/mailman/ >> postorius/-/merge_requests/930 which implements a framework for >> setting Postorius defaults and creates a setting to set the default >> for pre- verified on the mass subscription page. Once merged, this can >> easily be extended to provide a default for Invitation. >> >> In the mean time, you can only do this by patching src/postorius/ >> forms/ list_forms.py like >> ``` >> --- a/src/postorius/forms/list_forms.py >> +++ b/src/postorius/forms/list_forms.py >> @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): >> >> invitation = forms.BooleanField( >> label=_('Invitation'), >> - initial=False, >> + initial=True, >> required=False, >> help_text=_( >> 'If checked, the other checkboxes are ignored and the >> users will ' >> ``` >>> Can I also transfer other default values like: >>> >>> ... >>> DEFAULT_SERVER_LANGUAGE = 'en' >>> DEFAULT_SEND_REMINDERS = 1 >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> DEFAULT_PRIVATE_ROSTER = 2 >>> DEFAULT_ARCHIVE = Off >>> DEFAULT_ARCHIVE_PRIVATE = 1 >>> ... >>> >>> from the very same configuration file to Mailman 3? Is there a >>> documentation of the default values for lists in Mailman 3? >> >> This is done by creating a list style with the desired defaults. See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/ >> styles/ docs/styles.html for documentation of styles and see https:// >> gitlab.com/ mailman/example-mailman-plugin for an example of creating >> a plugin in Mailman core to make a persistent style. >> >> There is no specific doc for the list settings. You need to look at >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/ >> base.py for the various settings and https://gitlab.com/mailman/ >> mailman/-/blob/master/src/mailman/styles/default.py to see which >> default classes are applied for various styles. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

7 months, 2 weeks

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

by Abhilash Raj

On Wed, Jun 10, 2020, at 3:33 PM, Allan Hansen wrote: > All, > > This disconnect between Mailman Core and Django and Postorius is, by > far, the weakest and, for subscribers, most confusing aspect of MM3 > (once it has been installed, which is extremely hard and confusing). The disconnect was intentional to make sure that we are fully able to leverage the power of Django's ability to run multiple dis-connected applications in a single Site and Account system. And Mailman Core was intentionally designed to not be an account management system so it can be kept simple. The disconnect however has caused more confusion than has helped, which we acknowledge. But this disconnect doesn't exist all that much right now, barring any bugs. We synchronize most of the state from Postorius down to Mailman Core including, any additional addresses that you add, primary address etc. Display Names don't trigger an update in Core, but it isn't that hard to do if you open a ticket. > > In a true account-centric system, you set up a web account and from > there manage your emails and, for each email, your subscriptions. > Subscription options would be hierarchical: account/email/list, with > lower levels inheriting/overriding settings from/the level above. You are able to sign in via web and manage your email and subscriptions. The preferences also work exactly how you described above where the lower level override the default and/or upper level settings. > > That’s really what I had expected when I pushed for us to move our 50 > email lists to MM3 and I was very excited about the prospect, > as it would solve a lot of system/subscriber management issues I had > managing MM2. > > Alas, I was very surprised that that’s not how MM3 works. Some things > got harder, even, such as the inability to change subscription > addresses, which should have been a showstopper from the start! > I still hope that MMxx OOTB will get there, but I guess it’ll be along > haul. Would we be talking about MM4 to be released 20 years from now? As a Subscriber, you are able to do switch emails in subscriptions from your options page. The URL to which is displayed in the List's Summary page when you are logged in. Yes, it requires an approval if the list's settings are set to moderate but that is going to be fixed, see this issue[1]. It is quite simple IMO to fix this one, if someone wants to take this up. [1]: https://gitlab.com/mailman/postorius/-/issues/425 Are you asking about switching emails as an administrator for your subscribers? > Some dedicated and skilled developers are currently investing heavily > in a replacement for Postorius, but I really believe that any work is > better spent transforming Mailman Core etc. into a true account-based > system. Then, and only then, will it make sense to build new and better > interfaces on top, as, without a healthy core, such interface will > currently may have to inherit the confusion and disconnect that > currently is so aggravating. I don't know if we want to add account management to Core, but User management is missing from Postorius, that is true. We punted on it and delegated that part to Django's admin interface. Long long time ago, I remember seeing that there was a User's tab for managing users, but that has since changed I think. If you and some others on this list would like to propose an RFC here[2], it would be a great help for me. What I am basically looking for is what kind of "User management" are administrators looking for. It doesn't have to be too detailed but a single line example would be: - As a Admin, I would like to delete a User completely from my system, including all their addresses and subscription - Also, it would be good to delete their account but retain their subscriptions - As a Admin, I would like to update User's attributes in the system like: - Manually verify their email address - Manually update their Name - As a User, I would like to delete my own account and all the subscriptions. Maybe this could be a starting point, but something like this can be added to Postorius. [2]: https://gitlab.com/mailman/postorius/-/issues/new As for the question in this thread, you are able to delete the User from Django's admin page and that would delete all the related EmailAddress for them. Deleting an Email address doesn't delete the User, since the relationship exists that User owns Emails. There is currently no way to delete all the subscriptions for a User though. > The above is not meant to aggravate the MM3 development team, for which > I have utmost respect and gratitude, and which I admire for their > tireless support given over decades to the community of admins. > Software development is devilishly hard and time consuming. And thank you for posting what you think is an important enhancement to Postorius. We don't have a very strict process to choose what new features to work on, so email like this do help us prioritize. Other users could also help by upvoting or just adding "+1" to the bugs/feature enhancements that affects them the most so we can fix them sooner rather than later. I would be more than happy if more people participated in just being able to prioritize features, all the work really happens in the open on Gitlab. As administrators of some 'open source' lists, the needs of us as admins are somewhat different from what would be in a closed organization and ability to kick someone completely out of the system is something never I had to do since folks are supposed to manage their own subscriptions. We do ban people from sending emails if they've been spamming, but that is a different thing, they are still able to login into Postorius AFAIK. > Yours, > > Allan Hansen > hansen(a)rc.org > > > > > > Begin forwarded message: > > > > From: Mark Sapiro <mark(a)msapiro.net> > > Subject: [MM3-users] Re: Removing a mail addresses and users > > Date: June 10, 2020 at 12:46:01 PDT > > To: mailman-users(a)mailman3.org > > > > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > >> Hello. > >> > >> I tried to remove random email address signing ups (which I signed up > >> while testing) via admin panel. After removing I tried to sign up again, > >> but I am getting, > >> > >> 'A user is already registered with this e-mail address' > > > > You removed the user's subscription from the list, but you didn't remove > > the user from the system. > > > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > > User's have addresses and a user or one of the user's addresses can > > belong to a list with one or more roles (non-member, member, moderator > > or owner) > > > > > >> Combing through the database, I found auth_user table in mailman3web db > >> still contain those mail address. How to wipe email address entirely > >> from the db so I can signup again without the 'forget password' method > > > > There are a couple of things. If you log in to the web UI as a django > > superuser, you can go to the django admin UI -> Users section and delete > > the User, but I think that will only delete the web user and not delete > > the user from Mailman core. > > > > You can also log in to the web UI as the user and go to > > <https://lists.mailman3.org/user-profile/delete>, but that again only > > deletes the web user, and if you could do that, you could just subscribe > > once you're logged in, so I assume that's what you want to avoid. > > > > I don't think there is a way for a user as opposed to a site admin to > > delete her user record from Mailman core and even for a site admin, > > there's no way in Postorius to delete a user from core. It has to be > > done via REST > > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > > or `mailman shell`. > > > > -- > > 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/ > > _______________________________________________ > 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, 11 months

[MM3-users] Re: No e-mail distribution after import of archive

by Markus Grandpré

Dear Mr Odhiambo, thank you very much for your reply. In mailman.log I see: Nov 12 09:46:02 2024 (698086) ACCEPT: <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de HTTP/1.1" 200 486 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de/config HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/users/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/addresses/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 436 "-" "GNU Mailman REST client v3.3.5" [12/Nov/2024:09:46:03 +0100] "GET /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" Nov 12 09:46:03 2024 (698083) HyperKitty archived message <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> to https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_te… In smtp.log I found: Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO mailman-app-test.kim.uni-konstanz.de' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: markus.grandpre(a)uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: Import_mm3_testliste(a)mailman-test.uni-konstanz.de Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost during _handle_client() I have no idea why there is a "connection lost". What do you think? How can I increase the log level? With kind regards, Markus Am 12.11.24 um 09:38 schrieb Odhiambo Washington: > On Tue, Nov 12, 2024 at 10:34 AM Markus Grandpré < > markus.grandpre(a)uni-konstanz.de> wrote: > >> Dear Mr. Sapiro, >> >> on our test system we noticed the problem that after importing a mailing >> list archive from a Mailman system v2.1 into a Mailman system v3.3.8, >> e-mails are no longer distributed via this mailing list. E-mails that >> are written to the list find their way into the archive, but they are >> not sent to any member of the list. >> >> Before the archive was imported, writing an e-mail to the list and >> distributing this e-mail via the list was not a problem. Unfortunately, >> we cannot find any indication of this issue in the log of the mailman >> system v3.3.8. Please help us to further analyze and solve this problem, >> as we are planning to import 188 archives into our new productive >> mailman system v3.3.8 during the next months. >> > > Archives are imported into HyperKitty and should not in any way interfere > with Mailman Core. > From what I learnt recently, you can even import an archive into HyperKitty > without having a ML in Core associated with it. > So my starting point would be to look at mailman.log and see what goes in > there. I could even up the debugging level if need be. > For now, is there anything abnormal in mailman.log or smtp.log? > > > > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

6 months

[MM3-users] Re: share directories between postfix and mailman 3

by Thomas Schachtner

Mark Sapiro wrote: > On 1/22/24 13:05, Thomas Schachtner via Mailman-users wrote: >> Hi there, >> >> But that's not the full deal. Postfix needs access to some hashed >> configuration files containing the transport maps and the domains of >> the mailman installation, and mailman needs the contents of the >> postfix configuration file. > > Why do you think Mailman needs the contents of the postfix > configuration file.. I don't think so. I thought so, as mailman does not start if there's not /etc/postfix/main.cf file is there. The following messages are logged: Jan 23 21:20:35 mailman mailman3[491404]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Jan 23 21:20:35 mailman mailman3[491404]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted If /etc/postfix/main.cf is there, mailman is starting perfectly fine. But in another anwer I learned that mailman might not need the contents of that file but rather change it (although I did not see any changes). > >> As a quick and dirty solution, I've established a process which >> periodically copies the /var/lib/mailman3 directory from the mailman >> box to the postfix box using rsync. > > It appears you are using the Debian/Ubuntu package or at least have > configured `layout: fhs` in the `[mailman]` section of mailman.cfg. > This is OK, but in any case, all Postfix needs is > /var/lib/mailman3/data/*. Thanks for this information. I already thought so, but I was not sure. Yes, I am using the Debian package. I also found the line with 'layout', but it reads 'layout: debian'. They write: "You should not change this variable" > >> But I would like to have a more professional solution, like a >> directly shared directory between both. >> I did not yet find any suggestions on how to achieve this. Are there >> any best practices recommendations? >> I already tried sharing the directories using sshfs, but that did not >> work. >> >> I connected the remote directory >> postfix.example.com:/var/lib/mailman3 to my local directory >> /var/lib/mailman3 using >> >> sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 > > > I would suggest the opposite. I.e. on the postfix machine > ``` > sshfs user@mailman_machine:/var/lib/mailman3/data /var/lib/mailman3/data > ``` There are two reasons why I would like to do it the other way around: (1) I would like to make all changes on the mailman3 box and change as little as possible on the postfix server and (2) mailman is running on a system which does not have a fixed IP address. Mounting the file system from there can become complicated, as the IP address can change on a daily basis... >> This seemed to work pretty fine, as all files and directories seemed >> to be available, but when starting mailman 3, the following error >> message was shown: >> FileExistsError: A race condition might have happened. >> /var/lib/mailman3 actually exists and is not a directory. >> >> Any idea why this message is shown? > > Possibly because the uid and gid of /var/lib/mailman3 on the postfix > machine do not map to the appropriate Mailman uid and gid on the > mailman machine. You refer to the uid and gid of the "list" user? They are both 38 (uid and gid) on both machines. > >> So, is it a bad idea to use sshfs? > > > If you do it the other way, it might work. > I try to work around the changing IP address challenge then. Thanks! Tom

1 year, 3 months

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/6/24 1:33 AM, Odhiambo Washington wrote: > > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > >> Odhiambo Washington writes: > >> > >> > The odd thing is that the HOWTO that he followed never involves the > >> > manipulation of any urls.py at all - it's not even mentioned at any > >> > point. So obviously the issue is caused by something else and I > >> > suspect something within Apache needs to be re-evaluated in the > >> > guide. > > > The HOWTO installs mailman-web which contains a urls.py. > > >> > >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" > >> URI paths. It is quite unclear to me how this works at all with > >> either the > >> > >> path('mailman3/', include('postorius.urls')), > >> path('archives/', include('hyperkitty.urls')), > >> path('postorius/', include('postorius.urls')), > >> path('hyperkitty/', include('hyperkitty.urls')), > >> > >> version of urls.py or the reverse order version > >> > >> path('postorius/', include('postorius.urls')), > >> path('hyperkitty/', include('hyperkitty.urls')), > >> path('mailman3/', include('postorius.urls')), > >> path('archives/', include('hyperkitty.urls')), > > > This is an issue with Django. I'm not sure of the exact mechanism, but > consider the first of the above two sets. If you go to the mailman3/ URL > that gets redirected to the postorius/ URL. I.e. two paths that > ultimately reference the same thing wind up considering the second path > as the canonical path and redirecting the first path to the second. > > I was not initially aware of this when I added the postorius/ and > hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of > making either set of paths work, and I added those paths after the > mailman3/ and archives/ paths, and this version got released as > mailman-web 0.0.8. That caused the recommended Apache config to fail > because now the mailman3/ and archives/ paths were redirected to the > postorius/ and hyperkitty/ URLs which are not in the recommended Apache > config. > > I have since reordered the paths in mailman_web/urls.py, but that > version isn't yet released. Thus the issue. See > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for some background. > > > > My thinking then is that the documentation at > > > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > > needs to be fixed by adding the missing bits, > > > What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will > fix the issue. > Hi Mark, Thank you for making it much clearer. Is it possible that an Apache directive like below will fix everything (albeit discreetly with sysadmins driving blindly)? ProxyPass "/" "http://127.0.0.1:8000/" As was suggested by Mr. Turnbull (and previously by you on another thread)? It will be simpler, but leaves almost everyone (except the Devs) blind to the fact there exists a urls.py somewhere that determines the mappings? Maybe a note about it in the documentation will help? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

I'm able to reproduce this and will look into it -- what version of django-allauth are you using? (And what is the expected behavior for that endpoint?) --Jered ----- On Dec 6, 2023, at 7:57 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 14:49, Jered Floyd wrote: >> >> The difference in behavior was using social login buttons for an existing >> account vs. creating a new account. >> >> This is another damn django-allauth regression, starting in 0.57.0. It seem to >> be this commit that is to blame: >> https://github.com/pennersr/django-allauth/commit/be779dfee5a328a3a42edc2c9… >> >> In allauth/socialaccount/models.py:lookup(self):285 there is an attempt to look >> up the social account as one that already exists. If that fails, this commit >> calls self.account.get_provider() without passing the request object, which >> leads to the eventual error. >> >> I believe this is a django-allauth bug, and have submitted a pull request to fix >> it here: >> https://github.com/pennersr/django-allauth/pull/3548 > > Thanks for all your work on this. It is much appreciated. However, your > patch doesn't fix my issue with the URL > https://example.com/accounts/social/connections/ which still produces > the following: > ``` > ERROR 2023-12-07 00:05:55,032 169452 django.request Internal Server > Error: /accounts/social/connections/ > Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", > line 55, in inner > response = get_response(request) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/base.py", > line 220, in _get_response > response = response.render() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", > line 114, in render > self.content = self.rendered_content > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", > line 92, in rendered_content > return template.render(context, self._request) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/backends/django.py", > line 61, in render > return self.template.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 175, in render > return self._render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 167, in _render > return self.nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", > line 157, in render > return compiled_parent._render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 167, in _render > return self.nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", > line 157, in render > return compiled_parent._render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 167, in _render > return self.nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", > line 157, in render > return compiled_parent._render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 167, in _render > return self.nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", > line 63, in render > result = block.nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", > line 63, in render > result = block.nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", > line 321, in render > return nodelist.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in render > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 1005, in <listcomp> > return SafeString("".join([node.render_annotated(context) for node > in self])) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", > line 238, in render > nodelist.append(node.render_annotated(context)) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 966, in render_annotated > return self.render(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", > line 539, in render > values = {key: val.resolve(context) for key, val in > self.extra_context.items()} > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", > line 539, in <dictcomp> > values = {key: val.resolve(context) for key, val in > self.extra_context.items()} > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 715, in resolve > obj = self.var.resolve(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 847, in resolve > value = self._resolve_lookup(context) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", > line 914, in _resolve_lookup > current = current() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", > line 147, in get_provider_account > return self.get_provider().wrap_account(self) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", > line 141, in get_provider > provider = self._provider = adapter.get_provider( > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", > line 204, in get_provider > app = self.get_app(request, provider=provider) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", > line 284, in get_app > apps = self.list_apps(request, provider=provider, client_id=client_id) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", > line 231, in list_apps > db_apps = SocialApp.objects.on_site(request) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", > line 27, in on_site > site = get_current_site(request) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", > line 16, in get_current_site > return Site.objects.get_current(request) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/models.py", > line 63, in get_current > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: You're using the Django > "sites framework" without having set the SITE_ID setting. Create a site > in your database and set the SITE_ID setting or pass a request to > Site.objects.get_current() to fix this error. > ``` > > -- > 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 jered(a)convivian.com

1 year, 5 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Abhilash Raj

On Thu, Sep 30, 2021, at 2:20 AM, Odhiambo Washington wrote: > On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> >> >> > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> >> wrote: >> > >> > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> > >> >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: >> >>> 1. Confirmation emails to Users has wrong domain name (example.com!) >> >>> <https://docs.mailman3.org/en/latest/faq.html#id1> >> >>> < >> >> >> https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… >> >>> >> >>> >> >>> This happens when your reverse (SSL) proxy isn’t setting up the correct >> >>> headers when proxying requests. Fix this by setting the right >> >>> proxy_set_header directives: >> >> ... >> >>> How is this supposed to be mitigated in Apache when using WSGI? >> >>> >> >>> My config: >> >>> >> >>> WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman >> >>> user=mailman group=mailman >> >>> WSGIPythonHome "/usr/local" >> >>> WSGIProcessGroup hyperkitty >> >> >> >> >> >> You are using mod_wsgi and not proxying at all, so this is not relevant >> >> in your case. >> >> >> >> Are you actually seeing this issue? If so, it might be related to >> >> >> >> >> https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… >> >> >> > >> > My issue is related to this, but the documentation referred to is not for >> > the faint-hearted! >> > I can't make head or tails of it. >> >> Click on “Domain” in Postorius from the top bar, which should take you to >> the Domains page. >> >> For your domain (in the “Mail Host” column), see the corresponding “Web >> Host” column, it should look something like: >> >> lists.mailman3.org (lists.mailman3.org) >> (Edit) >> SITE_ID = 1 >> > > Mine looks different, slightly. But there is no example.com at all. > > [image: Abhilash.png] > > > >> >> on a new-ish version of Postorius. >> > > I have the newest versions of everything, having installed only yesterday. > > >> >> If it doesn’t show the right values and instead shows “example.com” for >> you, click on the “Edit” link, which will take >> you to a page that will allow you to edit both the values. >> > > It shows the right values, but with "SITE_ID = 2". In my settings_local.py > I have SITE_ID = 1. > I suppose the example.com is the one tied to SITE_ID = 1 and that is what I > have in my settings_local.py. That is most likely what is happening. > Should I edit my settings_local.py? Yes, please update it to have SITE_ID = 2 to correspond to the site you want and restart. > > I am still confused. > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' :-) > _______________________________________________ > 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)

3 years, 7 months

Search results for query "sapiro"