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

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

The only way I've gotten it to work so far is by using the FQN. I can switch back to 127.0.0.1 but that wasn't working. Here's the configuration I have. incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: 127.0.0.1 smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 and the end result: https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 I tried setting the smtp_host to 127.0.0.1 and list.domain.org both result in the same issue. ie: Here's the combinations I've tried: smtp_host: 127.0.0.1 lmtp_host: 127.0.0.1 #fail smtp_host: lists.domain.org lmtp_host: 127.0.0.1 #fail Finally I even tried the exact copy from the documentation: incoming: mailman.mta.postfix.LMTPoutgoing: mailman.mta.deliver.deliverlmtp_host: 127.0.0.1lmtp_port: 8024smtp_host: localhostsmtp_port: 25configuration: python:mailman.config.postfix ## Fail. smtp_host: lists.domain.org lmtp_host: lists.domain.org # success. The error I get if I don't open port 8024 is below and in the gist i linked earlier. May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, dsn=4.4.1, status=deferred (connect to lists.domain.org[198.199.98.177]:8024: Connection refused) The only way I've gotten it to work so far is by binding both the smtp_host and lmtp_host to be lists.domain.org and opening up port 8024. I'd rather not have that port open but I'm open to suggestions on what else to try. Locally on the server: PING lists.domain.org (198.199.98.177) 56(84) bytes of data. 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=3 ttl=64 time=0.069 ms -- Samir Faci On Mon, May 4, 2020 at 9:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 10:04 PM, Samir Faci wrote: > > > > # Where the LMTP server listens for connections. Use 127.0.0.1 instead > of > > # localhost for Postfix integration, because Postfix only consults DNS > > # (e.g. not /etc/hosts). > > lmtp_host: lists.domain.org > > lmtp_port: 8024 > > Why, in spite of the comment, do you have > > lmtp_host: lists.domain.org > > and not > > lmtp_host: 127.0.0.1 > > Note that > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > are the defaults. > > > > So, now it's finally working but here's a question. Does 8024 need to be > > publically accessible from the outside? > > > No. Port 8024 is only for LMTP delivery from Postfix to Mailman. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 10 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Many thanks for your help. I have managed to modify some of the messages after following your instructions. Kind regards, Prasanth On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Thank you for your help. Let me try this. > > Kind regards, > Prasanth > > On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/28/21 6:02 AM, Prasanth Nair wrote: >> > Hello, >> > >> > Does anyone know how to edit an archived email in Mailman3? It is >> possible >> > in Mailman2 ( >> > >> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >> ). >> > Is there any option similar to this in Mailman3? >> >> >> In some sense the process is the same but possibly even simpler in >> Mailman 3. You need to modify the underlying data which requires >> appropriate access to the server. >> >> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >> database. You can get the Message-ID hash from the URL to the archived >> message, e.g. for the message to which I'm replying, the URL is >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >> access, you can do database queries like >> ``` >> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> and >> ``` >> UPDATE hyperkitty_email SET content = '<new content>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> If the message has attachments, they are in the hyperkitty_attachment >> table and can be referenced by `email_id` which is the corresponding >> `id` from the hyperkitty_email entry. >> >> You can also do similar things via `django-admin shell`. E.g. >> ``` >> $ django-admin shell >> Python ... >> (InteractiveConsole) >> >>> from hyperkitty.models.email import Email >> >>> x = >> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >> >>> print(x[0].content) >> ``` >> but this requires some knowledge of HyperKitty's models and Django's ORM. >> >> -- >> 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/ >> >

4 years, 5 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi, I was wrong. It keeps happening. So the base_url didn't fix the issue. And the keys are the same in all configurations. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Fri, 22 Mar 2024 at 09:37, Helio Loureiro <helio(a)loureiro.eng.br> wrote: > Hi Mark, > > Thanks for your response. I found what the issue was. > > I actually misspelled hyperkitty as hyPperkitty on the url. > > So the error on mailman-hyperkitty.cfg was: > > base_url: http://localhost:8000/hypperkitty/ > > I moved to: > > base_url: http://localhost:8000/hyperkitty/ > > and it was solved. > > Problem was the wrong link was getting a generic page from Django instead > of error. And it was failing to do the parsing probably, which was taking > wrongly as key mistake. > Best Regards, > Helio Loureiro > https://helio.loureiro.eng.br > https://github.com/helioloureiro > https://mastodon.social/@helioloureiro > > > On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/20/24 14:25, Helio Loureiro wrote: >> > Hi, >> > >> > I keep receiving a lot of errors like this: >> > >> > --- Logging error --- >> > Traceback (most recent call last): >> ... >> > >> "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", >> > line 55, in unsign >> > raise BadSignature('Signature "%s" does not match' % sig) >> > django.core.signing.BadSignature: Signature >> "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" >> > does not match >> ... >> > >> > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and >> MAILMAN_ARCHIVE_KEY >> > on setting.py are the same. >> >> >> Of those three, the api_key on mailman-hypperkitty.cfg and >> MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django >> thing and has nothing to do with the others. See >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key >> >> If you changed it, that's the issue. If you know what it was previously, >> you could set the previous value in SECRET_KEY_FALLBACKS, see >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks >> >> -- >> 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 helio(a)loureiro.eng.br >> >

1 year, 11 months

[MM3-users] Re: users, users and users (was Re: Re: Cannot request password reset: "The e-mail address is not assigned to any user account")

by Mark Sapiro

On 1/28/22 00:41, IOhannes m zmölnig wrote: > > i'm afraid i still do not fully understand which types of "users" there > are. > > > afaics, there are three different types: > - django users > this is what get's listed under > <https://lists.mailman3.org/admin/auth/user/> Correct. > - mailman accounts > this is what is created when you visit > <https://lists.mailman3.org/accounts/signup/> No. That creates a Django user, not a Mailman user. What you think of as a Mailman account is actually a Django account. > - email addresses > this is what is created when i subscribe to a list *without* having > an account. > e.g. via the "Subscribe" button on > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Mailman core has users and addresses. A user has one or more associated addresses. When you subscribe to a list without having an account in that way, or via email to list-join or list-subscribe or by being mass subscribed by the list admin or by being imported by `mailman import21`, assuming you are previously unknown, this creates a Mailman user with an associated address and subscribes the user or address. Each user has a primary address and zero or more additional linked addresses. The user can be subscribed to a list as a user in which case, delivery if any is to the user's primary address, or can be subscribed as an address. > afaiu, (multiple) "email addresses" can be associated with a single > "mailman account" (but this is strictly optional). Yes, see above. > if an "email address" is first used to subscribe to a list without a > mailman account, and later a mailman account is created with that very > email address, they get automatically associated. > a single "email address" cannot be associated with more than one > "mailman accounts". Based on the above, your "mailman accounts" are actually Django accounts. With that in mind, the above is correct, but there is no real link between Mailman users and Django users. When you are logged in to the web UI you are logged in as a Django user, and Postorius and HyperKitty know that user's email address and can therefore know if it is a list member and know what address to subscribe or unsubscribe as requested. > i think i got this one right (as it seems pretty straightforward). > > what i don't fully grasp yet is the relation between "django users" and > "mailman accounts". As I have said, what you are calling a mailman account is a Django user and not a Mailman user. > intuitively, i would have thought that they are identical. They are, but they are not Mailman core users. > now mark wrote: > > a Django user, which is distinct from a Mailman user. The users you > > added via the web API are Mailman users, but in order to access their > > lists via the web UI they have to `sign up` to create a Django > > account. > > that seems to indicate, that a "django user" is a (strict) superset of a > "mailman account". No. A Django user is the same thing as what you call a mailman account. A Mailman core user is a separate thing entirely. > you (as admin) can create "mailman accounts" via the web API¹, but they > are only expanded to "mailman accounts" if you (as user) go through the > "Sign Up" process. No. An admin can create Mailman users via the Postorius UI. A Django superuser can also create Django users through the Django admin UI. > otoh, if you create an initial "django user" by signing up, you > automatically create a "mailman account". Because they are the same thing. When you go to the Sign-up link on a Postorius or Hyperkitty page you go to https://example.com/accounts/signup/, and that's Django, not Mailman. > so are the two distinct concepts that are just associated via some > common property (e.g. the email address), or is there some intrinsic > relationship between the two (e.g. parent-child inheritance relationship)? They are distinct. Django users have email addresses and Mailman users have email addresses and they can be associated in that way. There is no other link. > so my recent experiment (comparing the output of > <https://lists.example.com/admin/auth/user/> with that of `[u for u in > getUtility(IUserManager).users]`) indicates that they are indeed > distinct objects that *can* be associated with each other. > > could you please clarify this? I hope I have. -- 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: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-26 00:52, schrieb Mark Sapiro: > On 4/25/24 14:01, Thomas Stein wrote: >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >>> >>> I don't know how things are arranged in the Debian/Ubuntu package, >>> but you may have a settings.py which at the end does something like >>> ``` >>> try: >>> from settings_local import * >>> except ImportError: >>> pass >>> ``` >>> If that is the case, adding the above snippet to the end of >>> settings_local.py should work. >> >> Yes, that's the case. I added the snippet in question to >> settings_local.py but this leads to another error: >> >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> >> from settings_local import * >> File "/usr/share/mailman3-web/settings_local.py", line 194, in >> <module> >> x = list(MIDDLEWARE) >> ^^^^^^^^^^ >> NameError: name 'MIDDLEWARE' is not defined >> dpkg: error processing package mailman3-web (--configure): > > Yes. I understand. In your case, MIDDLEWARE is only defined in > settings.py and not in settings_local.py. As I understand it originally > you added > ``` > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to settings.py and you say it didn't help. I don't know why that > wouldn't work as long as there is no setting for MIDDLEWARE in > settings_local.py and you added that after the MIDDLEWARE setting in > settings.py. > When you say it didn't help, do you mean you still get the > > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > > message or something else? I note that the original post in this thread > refers to /etc/mailman3/mailman-web.py which is presumably where the > package ultimately puts the Django settings, and I don't know what > `dpkg --configure` is doing. > > One thing you could try is in settings_local.py, put > ``` > from settings import MIDDLEWARE > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to work around the NameError. After that I get: File "/usr/share/mailman3-web/urls.py", line 20, in <module> from django.conf.urls import include, url ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) dpkg: error processing package mailman3-web (--configure): installed mailman3-web package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: I guess I'll wait for the new package for now. thanks again! t.

1 year, 10 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Gerald Vogt

Hi, are you sure you are both talking about the same setting? You wrote initially: "The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a *non-member* posts to the list" -- it says Hold for moderation" That's for non-members, not for members. That does not apply to users which you have mass subscribed. For those there is the "Default action to take when a member posts to the list". That's the one Mark Sapiro mentioned. Regards, Gerald On 18.11.24 10:59, mark(a)suburbia.org.au wrote: > Hi Mark, > > Thanks for taking the time to reply. > > Mark Sapiro wrote: >> On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > >>> However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. >>> Am I missing something with the expected functionality? >>> A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? >> Actually, it is good practice to set that to Hold for moderation for >> all lists or at least all those that don't require moderator approval >> for subscription to prevent a spammer from subscribing and spamming the >> list. Then, upon approving a member's post you can also set the member's >> moderation action to default processing and upon discarding a spammers >> post, you can also set the spammer's moderation action to Discard. > > I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. > > I'm happy to do more testing, provide other information/logs as desired if that would help? > > cheers, > Mark > _______________________________________________ > 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 vogt(a)spamcop.net

1 year, 4 months

[MM3-users] Re: config.pck from mailman2 has characters that won't import with import21

by Mark Sapiro

On 7/20/24 10:19 PM, Greg Newby wrote: > Hi. I've set up MM3 in a venv successfully and am importing my legacy lists. > > I no longer have a running instance of mailman2, so don't know how I can > change the offending list settings (i.e., in config.pck). > > The problem seems to be a digest footer from the previous incarnation of > the list (list name is edited below, to protect the innocent): That's not the issue. > (venv) mailman@mail:~$ mailman import21 abc(a)lists.abcabcabc.org > /var/lib/mailman/lists/abc/config.pck > Unable to convert mailing list attribute: msg_footer with value > "_______________________________________________ > ${display_name} mailing list -- ${listname} > To unsubscribe send an email to ${short_listname}-leave@${domain} > %(web_page_url)slistinfo/%(_internal_name)s" > Unable to convert mailing list attribute: digest_footer with value > "_______________________________________________ > ${display_name} mailing list -- ${listname} > To unsubscribe send an email to ${short_listname}-leave@${domain} > %(web_page_url)slistinfo/%(_internal_name)s" The above are non-fatal. The importer just won't make list specific templates for those. If you need the footers to be different from the defaults, you will need to create them manually. > Importing members [------------------------------------] 0% > Traceback (most recent call last): > File "/opt/mailman/venv/bin/mailman", line 8, in <module> > sys.exit(main()) > ^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1157, in __call__ > return self.main(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1078, in main > rv = self.invoke(ctx) > ^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py", > line 69, in invoke > return super().invoke(ctx) > ^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1688, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1434, in invoke > return ctx.invoke(self.callback, **ctx.params) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 783, in invoke > return __callback(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/click/decorators.py", line > 33, in new_func > return f(get_current_context(), *args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/commands/cli_import.py", > line 89, in import21 > import_config_pck(mlist, config_dict) > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", > line 578, in import_config_pck > import_roster(mlist, config_dict, members, MemberRole.member) > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", > line 625, in import_roster > _import_roster(mlist, config_dict, iterator, role, action=action) > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", > line 645, in _import_roster > if IBanManager(mlist).is_banned(email): > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", > line 106, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py", > line 103, in is_banned > re.match(ban.email, email, re.IGNORECASE) is not None): > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/__init__.py", line 167, in match > return _compile(pattern, flags).match(string) > ^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile > p = _compiler.compile(pattern, flags) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile > p = _parser.parse(p, flags) > ^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_parser.py", line 979, in parse > p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub > itemsappend(_parse(source, state, verbose, nested + 1, > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse > raise source.error("multiple repeat", > re.error: multiple repeat at position 11 The list's ban_list has an invalid regexp. Do the following in Mailman 3's `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. >>> import pickle >>> from contextlib import ExitStack >>> from mailman.commands.cli_import import _Mailman, _Bouncer >>> from mailman.utilities.modules import hacked_sys_modules >>> with ExitStack() as resources: ... resources.enter_context(hacked_sys_modules('Mailman', _Mailman)) ... resources.enter_context( ... hacked_sys_modules('Mailman.Bouncer', _Bouncer)) ... with open('/path/to/config.pck', 'rb+') as fp: ... data = pickle.load(fp) ... print(data['ban_list']) ... data['ban_list'] = [] ... fp.seek(0) ... pickle.dump(data, fp) ... >>> ``` This will print the ban_list so you can see it and then save the config.pck with an empty ban_list. That config.pck will no longer be usable in Mailman 2.1 because the pickle protocol is too high and the bounce_info items if any will be corrupted, but it should work with import21. Note that all the ExitStack and hacked_sys_modules stuff is only needed if there is bounce_info in the config.pck, but it doesn't hurt in any case. -- 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: config incoming email in my domain cpanel

by tlhackque

You've said you're working with labbrands.com. labbrands.com has address 192.185.51.89 mail.labbrands.com has address 192.185.51.89 www.labbrands.com is an alias for labbrands.com. telnet proves that Exim is running on that IP address. Either you're running it, or hostgator is redirecting the SMTP ports. You added: lists.labbrands.com has address 190.145.27.66 Presumably that's a different machine. So that now needs an MX record, and a firewall routing. And the SPF records ... and spam and virus filters, and all the other stuff you need to setup an independent, public-facing smtp server. But at least you won't have to relay. Good luck. On 03-Aug-17 16:55, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > mailman-users(a)mailman3.org>) escribió: > >> I think you're confused. >> >> You already have mail.labbrands.com set up as the MX record for >> labbrands.com. And it has an A record with the same address as your >> webserver. >> > I'm working with the hostgator mailserver, we are not running a local > mailserver. > > As suggested I added an A record like this: > [image: image.png] > > Is it correct? is it redirecting to my Ip so I can redirect it to my > postfix/mm3 server? > > >> So if you're getting e-mail on that domain, there's another e-mail >> server running on that IP address. You can't have 2 servers on port >> 25. In that case, as has been noted before, you'll need to setup a >> relay in that server, not a firewall redirect. Depending on your MTA, >> you would need to relay to your internal server. And make sure your >> firewall setup allows your MTA to do this. >> >> We can see it's EXIM: >> >> telnet mail.labbrands.com 25 >> Trying 192.185.51.89... >> Connected to mail.labbrands.com (192.185.51.89). >> Escape character is '^]'. >> help >> 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 >> -0500 >> 220-We do not authorize the use of this system to transport unsolicited, >> 220 and/or bulk e-mail. >> 214-Commands supported: >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP >> quit >> 221 gator4137.hostgator.com closing connection >> Connection closed by foreign host. >> >> Or, consolidate all your e-mail to one server - which is a lot easier to >> manage unless you have a really big operation. Postfix is probably the >> right choice, but requires more setup. >> >> Although Mailman3 configuration is not well documented (as you've >> discovered), you may want to get help from someone with more general >> network and mail experience. You're now into territory that is, as >> Simon indicated, not Mailman-specific. >> >> On 03-Aug-17 16:28, Rafael Mora wrote: >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) >> escribió: >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) >>>> escribió: >>>>>> You need to forward port 25 for SMTP mail delivery and if you want the >>>>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >>>>>> for http and/or port 443 for https >>>>>> < >>>>>> >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>>>>>> . >>>>> I mean for incoming mail redirected from my hostgator hosting, because >>>> when >>>>> I suscribe an email address MM3 sends a confirmation email, so I have >> to >>>>> reply to be suscribed to the list. >>>> As I said, for mail delivery you need to forward port 25 to the Mailman >>>> server. >>>> >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local >> centos7 >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. >>> >>> >>>> -- >>>> 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/ >>>> >> -- >> This communication may not represent my employer's views, >> if any, on the matters discussed. >> >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> -- This communication may not represent my employer's views, if any, on the matters discussed.

8 years, 7 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

It seems something is fundamentally wrong with Hyperkitty: From /var/log/mailman3/mailman.log --- 49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 50 <h1>Authorization Required</h1></body></html> (401) 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 52 <h1>Authorization Required</h1></body></html> (401) 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 54 <h1>Authorization Required</h1></body></html> (401) 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> 56 <html><head> 57 <title>503 Service Unavailable</title> 58 </head><body> 59 <h1>Service Unavailable</h1> 60 <p>The server is temporarily unable to service your 61 request due to maintenance downtime or capacity 62 problems. Please try again later.</p> 63 <hr> 64 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> 65 </body></html> 66 (503) 67 Sep 21 21:49:26 2020 (24918) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 68 <html><head> 69 <title>503 Service Unavailable</title> 70 </head><body> 71 <h1>Service Unavailable</h1> 72 <p>The server is temporarily unable to service your 73 request due to maintenance downtime or capacity 74 problems. Please try again later.</p> 75 <hr> 76 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> 77 </body></html> 78 Sep 21 21:49:26 2020 (24918) Traceback (most recent call last): 79 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message 80 url = self._send_message(mlist, msg) 81 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message 82 raise ValueError(result.text) 83 ValueError: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 84 <html><head> 85 <title>503 Service Unavailable</title> 86 </head><body> 87 <h1>Service Unavailable</h1> 88 <p>The server is temporarily unable to service your 89 request due to maintenance downtime or capacity 90 problems. Please try again later.</p> --- Thanks Mohsen -----Original Message----- From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Monday, September 21, 2020 12:24 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] Hi Mark, Thank you Mark and Phil for your help. It seems I got stuck! 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" 2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size 3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, > you can set max_message_size in your list configuration. It defaults > to 40; units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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… _______________________________________________ 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…

5 years, 5 months

[MM3-users] django-allauth 0.59.0 (was: django-allauth failures, but only for some users)

by Jered Floyd

FYI, django-allauth 0.59.0 was released on December 12 and incorporates the patches to work properly with Mailman again. The only other issue is formatting of the login page. As I noted previously, this can be fixed by copying site-packages/allauth/templates/socialaccount/login.html to site-packages/django_mailman3/templates/socialaccount/login.html and changing the first line from: {% extends "socialaccount/base_entrance.html" %} to {% extends "django_mailman3/profile/base.html" %} --Jered ----- On Dec 7, 2023, at 9:57 PM, Jered Floyd jered(a)convivian.com wrote: > You're welcome. Thank you for all your hard work making Mailman 3 happen at all! > > I think django_allauth integration is again stable, but for now I'm pinning > 0.58.2 + this patch. I'll test again once there is another release > notification, but since I rebuild by container image every 2-3 weeks I am > getting exhausted by surprises... > > --Jered > > ----- On Dec 7, 2023, at 7:44 PM, Mark Sapiro mark(a)msapiro.net wrote: > >> On 12/7/23 14:33, Jered Floyd wrote: >>> >>> FYI, The django-allauth author has proposed fixing both of these with an even >>> simpler change, which is now upstream and queued for a future release. >>> >>> --Jered >> >> >> Thank you again for your work on this. I can confirm that the patch >> below fixes my issue with >> https://msapiro.net/accounts/social/connections/ and SITE_ID = 0. >> >> >>> --- a/allauth/socialaccount/adapter.py >>> +++ b/allauth/socialaccount/adapter.py >>> @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object): >>> provider_to_apps = {} >>> >>> # First, populate it with the DB backed apps. >>> - db_apps = SocialApp.objects.on_site(request) >>> + if request: >>> + db_apps = SocialApp.objects.on_site(request) >>> + else: >>> + db_apps = SocialApp.objects.all() >>> if provider: >>> db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider)) >>> if client_id: >> >> -- >> 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 > _______________________________________________ > 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

2 years, 3 months

[MM3-users] Re: Scheduled tasks

by Darren Smith

I will take up any problems with the installation with the creator. However, I was able to find and run some of the scripts this afternoon, and I'm running some of the longer-running ones tonight while the usage is lower. As for bogging down - I mean attempting to click on an email can take a LONG time to render, and we frequently get 504 gateway timeouts (the calls to hyperkitty are timing out). I am trying hard to figure out why this is happening and to try to tune the system. I still suspect that there are some inefficiencies with how the database is being used, or how the database is doing things. I will take a look at qcluster, that was interesting info and hopefully it can help me out. Thanks for your response, -Darren On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/7/18 9:59 AM, Darren Smith wrote: > > All, > > > > I am looking more through the documentation of the Mailman Suite here: > > > > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf > > > > In section 3.2.5 it talks about the scheduled tasks that need to be run > to > > do "specific routine functions" in hyperkitty. > > > > I installed through the easy install script found here: > > > > https://github.com/iomarmochtar/mailman3_ei/ > > > > However, I can't find anything in THAT documentation that talks about > these > > cron jobs, and in fact the Mailman Suite isn't installed through that > > script. > > > That is a third party project. If you have issues with it, you should > take them up with @iomarmochtar. > > > > Can someone point me to any other documentation about the tasks that need > > to be run on a continual basis? > > > The section 3.2.5 you refer to tells you what needs to be set up in > cron. For a list of the jobs tat are run, use > > django-admin runjobs --list > > > . Our hyperkitty installation seems to be > > bogging down more and more, and I am hoping that it will be as simple as > > just running some jobs that haven't been on our radar. > > > what do you mean by 'bogging down'? If you aren't doing so, setting up > qcluster as in section 3.2.3 may help. > > -- > 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/ >

7 years, 9 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

Hi, On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > It's ok now, but still I can't make it send the confirmation email > > This is from mailman.log: > > > [mailman@localhost logs]$ tail -f mailman.log > Aug 01 15:59:18 2017 (2327) lmtp runner started. > Aug 01 15:59:18 2017 (2333) virgin runner started. > Aug 01 15:59:18 2017 (2332) retry runner started. > Aug 01 15:59:18 2017 (2330) pipeline runner started. > Aug 01 15:59:18 2017 (2325) command runner started. > Aug 01 15:59:19 2017 (2328) nntp runner started. > Aug 01 15:59:19 2017 (2326) in runner started. > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > 90 > > > > > What should I do? If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself. To configure Django you need to edit the `settings.py` file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at `mailman-suite/mailman-suite_project/settings.py`. To configure your Django to send emails, have a look at http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required. That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured. Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here. Hope that helps! > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > Why does it say Address already in use? > > > > > > Because you are starting lm tp runner and it's already running. > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > any if necessary. Then do 'mailman start'. > > > > -- > > 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 7 months

[MM3-users] Re: Request for help debugging a hyperkitty connection issue

by Stephen Daniel

Got it in one! I had put "www.LISTDOMAIN.org/archive" in as the base URL in mailman-hyperkitty.cfg. No such host exists. Replaced with "LISTDOMAIN.org/archive" and all is well! Thanks!!! To the contributing community: would there be a way to enhance the logging of this error to include the resource that failed to connect? Thanks. -- Stephen Daniel On Thu, Jan 6, 2022 at 5:15 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:12 PM, Stephen Daniel wrote: > > > > I have two problems. One is with getting list mail out of GCP. I am > > working on that. The issue I don't know how to address is a problem with > > hyperkitty. Nothing is being archived. When I send an email through my > > test list, this message shows up in the mailman log: > > > > Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver > > > > Traceback (most recent call last): > > > > File > > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", > > line 175, in _new_conn > > > > (self._dns_host, self.port), self.timeout, **extra_kw > > > > File > > > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", > > line 73, in create_connection > > > > for res in socket.getaddrinfo(host, port, family, > socket.SOCK_STREAM): > > > > File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo > > > > for res in _socket.getaddrinfo(host, port, family, type, proto, > flags): > > > > socket.gaierror: [Errno -2] Name or service not known > > > > > > This triggers a bunch more tracebacks. > > > > Then I get this: > > > > Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed: > > HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', > > port=443): Max retries exceeded with url: /archives/api/mailman/archive > > (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object > > at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name > > or service not known')) > > > What is your setting for base_url: in mailman-hyperkitty.cfg?. Can you get > > wget -O- xxx > > where xxx is base_url with `api/` appended. This should return an html > page of API documentation. > > If your base_url: seems good and its scheme is `https`, try changing it > to `http`. > > > -- > 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/ >

4 years, 2 months

[MM3-users] Re: new list not working

by Christian

When I ran mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org I did receive a list of subscribers for the new list I created, not just the owner or moderator. Upon closer examination, another of my longtime working lists is also not working. Similar behavior as the new list I created in that I see the message has been archived, but not distributed to the subscribers. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 1:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 13:26, Christian via Mailman-users wrote: > I am only having issues with the new list. > > > > Below are logfile entries > > > > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: > christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: > redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost > during _handle_client() This is the post being delivered to mailman and is expected. > > > Access.log Irrelevant. > Mailman.log > > ++++++++ > > Mar 09 20:57:09 2023 (9400) ACCEPT: > <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> > > Mar 09 13:03:42 2023 (9397) HyperKitty archived message > <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> to > https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalt > ernatives.org/message/PAJ5GDGGK74LWHQINB32BDV22BMR6LRQ/ These are the expected messages (there seems to be a time zone difference) and in the absence of any other error type messages say the message should have been delivered to the eligible recipients. Are there any? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ CTAF4RDJ2CTNCGI7MXFYL3Q5HTGYMZH6/ or the results from ``` mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org ``` > mailmansuite.log not relevant. -- 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/ ZVY3EFBA5WQKYS6E7AS475TNY6C4NJQU/ This message sent to csa(a)web-analysts.net

3 years

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

Unfortunately i need this, as the postfix is listening on all interfaces and we have the policy to enforce TLS only. Nothing special in the logs: Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fbc29b1c4a8> Dec 07 08:14:14 2021 (12303) Connecting to localhost:25 Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients: ['recipient(a)own.domain'], size(msgtext): 5809 Dec 07 08:14:14 2021 (12303) <kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> smtp to v-test@domain for 1 recips, completed in 0.008081912994384766 seconds Dec 07 08:14:14 2021 (12303) <kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> post to v-test@domain from v-test@domain, 5336 bytes Dec 07 08:14:47 2021 (12297) Peer: ('127.0.0.1', 43210) Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) handling connection Dec 07 08:14:47 2021 (12297) b'220 ml01.my.domain GNU Mailman LMTP runner 2.0\r\n' Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) EOF received Dec 07 08:14:47 2021 (12297) Connection lost during _handle_client() Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) connection lost Dec 07 08:15:00 2021 (12297) Peer: ('127.0.0.1', 43516) Dec 07 08:15:00 2021 (12297) ('127.0.0.1', 43516) handling connection Is my mailman version maybe too old for this setting? I'm running GNU Mailman 3.1.1 (Between The Wheels) Thank you. Am Mo., 6. Dez. 2021 um 19:04 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 12/6/21 2:51 AM, Stefan Bauer wrote: > > Need to bring this up again. Django now sends with STARTTLS, but mailman > > itself, does still only drop mails in cleartext. > > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > > > No starttls=1 at all :( > > > > Does the above settings work for anyone? > > > > etc/mailman3/mailman.cfg > > [mta] > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > > > smtp_host: localhost > > smtp_port: 25 > > smtp_user: > > smtp_pass: > > smtp_verify_hostname: false > > smtp_verify_cert: false > > smtp_secure_mode: starttls > > > This should work. What do you see in Mailman's smtp.log if you add > ``` > [logging.smtp] > level: debug > ``` > to mailman.cfg. > > However, do you really need this. It will only affect delivery from > Mailman to Postfix via the loopback interface on the localhost. > > -- > 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/ >

4 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

New output from command 'postconf -n ': [root@localhost ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 html_directory = no inet_interfaces = localhost inet_protocols = all local_recipient_maps = hash:/var/lib/mailman/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES recipient_delimiter = + relay_domains = hash:/var/lib/mailman/var/data/postfix_domains sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 08:16 AM, Rafael Mora wrote: > > This is the content of my /var/log: > > > > > > [root@localhost log]# pwd > > /var/log > > [root@localhost log]# ls > > anaconda grubby messages-20170716 spooler-20170710 > > audit grubby_prune_debug messages-20170723 spooler-20170716 > > boot.log httpd mysqld.log spooler-20170723 > > btmp lastlog php-fpm tallylog > > btmp-20170701 letsencrypt ppp tuned > > chrony maillog rhsm wtmp > > cron maillog-20170702 samba xferlog > > cron-20170702 maillog-20170710 secure xferlog-20170702 > > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > > cron-20170723 mailman secure-20170716 xferlog-20170723 > > dmesg messages secure-20170723 yum.log > > dmesg.old messages-20170702 spooler > > firewalld messages-20170710 spooler-20170702 > > > Your current postfix log is /var/log/maillog. The files like > /var/log/maillog-20170702, etc are older versions rotated by logrotate. > > On 07/23/2017 08:14 AM, Rafael Mora wrote: > > content of the file maillog-20170723 (I didn't find mail.log in > /var/log): > > > > [root@localhost log]# cat maillog-20170723 > > You want to be looking at /var/log/maillog for current messages. > > > ... > > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory > > > Is this where these files are? You should have at least postfix_domains, > postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the > /var/lib/mailman/var/data/ directory. It this the case? > > > output command 'postconf -n': > > > ... > > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp > > > This is missing a / > > > transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp > > > -- > 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

8 years, 7 months

[MM3-users] Re: templates

by Odhiambo Washington

If you don't have any templates in the file system and none in the DB table, then you must go to Jerusalem and pray, because you don't have any and nothing will work the way you want. It's either or! On Thu, May 4, 2023, 21:14 Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. > > > > > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Thursday, May 4, 2023 10:58 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: templates > > On 5/4/23 10:33, Christian via Mailman-users wrote: > > I'm having issues with my lists. For each list I have created a > > template [ list:user:action:subscribe ]which has a prospective > > subscriber have to consent to list rules before they are subscribed. > > This template I created is listed in Postorius for each list. I have > > noticed that there are no other templates listed in Postorius. > Furthermore, there is no 'lists' > > subdirectory under Mailman's var/templates/. > > > When you set a template in Postorius it saves it in the > postorius_emailtemplate table in the database and tells Mailman core to get > the template from Postorius via a URI to a Postorius API. > > -- > 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/ > QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to csa(a)web-analysts.net > > _______________________________________________ > 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 odhiambo(a)gmail.com >

2 years, 10 months

[MM3-users] Re: mailman3 postorius cannot retrieve template at ... (<no authorization>)

by Mark Sapiro

On 10/29/21 3:41 AM, Wolfgang Bock via Mailman-users wrote: > > the question is: postgres - mailman3web-postorius_emailtemplate table vs > mailman3 - templates table > > I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, Core > Python 3.9.2 postgres12 nginx on debian bullseye. > > I created a template via postorius -> lists -> (testliste01) -> templates > -> new template -> [list:member:regular:footer] and > [list:member:digest:footer] > > They are shown in the postgres database mailman3 table templates: > id name context uri username password > 14 list:member:digest:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:digest:footer > 15 list:member:regular:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer > > First there where no templates in the /var/lib/mailman3/templates folder, > which was empty after installation. This is expected. That is one place where you can put custom templates. > Later I created in /var/lib/mailman3/templates theses folders and the files > /list/testliste01.mydomain.de/list:member:digest:footer + > list:member:regular:footer owned by list:list 644 > > A testmail went through but instead of the default footer no footer was > shown. By default Mailman searches for templates first in the var/templates directory and then in the templates directory in the Mailman installation. The details are described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…. However, the default search is only applied if there is matching entry for the template name and context in the `templates` table in the database or if the uri in the entry is a `mailman://` uri. When you create a template in Postorius, that uri becomes something like `https://example.com/mailman3/api/templates/list/<list_id>/<template_name>` which basically says get the template from Postorius, and the template if any in var/templates is ignored. > In the sys.log I found the following error message: > Oct 29 11:28:04 myserver mailman3[33015]: Message: `Cannot retrieve template > at > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer (<no authorization>)` So Mailman is trying to get the Postorius template. What is in the web server logs for this retrieval? > How can I solve this problem? What kind of authorisation is meant? list? > restadmin? > > I read in > https://docs.mailman3.org/en/latest/config-core.html#configure-templates > ... list specific templates invar/templates/lists/LIST-ID/LC/ ... > I guess the LC means Language Code. But in the database table templates no > LC subdirectory is mentioned (in my case must be de). If you delete the Postorius template, The entry in the templates table will be removed and the search will revert to var/templates, etc. > And I read (dont know where) .... The templates created in Postorius are > created in the postorius_emailtemplate table in Mailman`s database and > referenced via URLs like > `https://example.com/mailman3/api/templates/list/<list-id>/<template-name>`. > I.e., they are not stored in the file system. ... > > That`s true. I found in postgres database mailman3web in the table > mailman3web postorius_emailtemplate my > > id name data language created_at modified_at > context identifier > 15 list:member:digest:footer postorius footer digest 1x linefeed > 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list > testliste01.mydomain.de > 16 list:member:regular:footer postorius footer non-digest 1x > linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list > testliste01.mydomain.de > > But my question is how to integrate this into the mailman3-system. The > language isn`t set either. It is integrated. The language isn`t set because you are getting the template from Postorius and Postorius knows the language. On 10/31/21 4:13 AM, Wolfgang Bock via Mailman-users wrote: > regarding my mail before, here an additional information. > > I can show the templates with following command (anonymized): > https://active_domain.de/postorius/api/templates/list/testliste01.active_do… As it should be. > The complete syslog > (edited and reformatted by me) ``` > --- Logging error --- > Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get > contents = protocols.get(actual_uri, **auth) > File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get > response.raise_for_status() > File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status > raise HTTPError(http_error_msg, response=self) > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost/postorius/api/templates/list/testliste01.active_domain.de/… > During handling of the above exception, another exception occurred: > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/__init__.py", line 430, in format > return self._format(record) > File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format > return self._fmt % record.__dict__ > KeyError: `t` > During handling of the above exception, another exception occurred: ``` Your template is malformed. You have $ strings that are not defined as Mailman substitution variables. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Waqas Ahmed Khan

Hi, I have successfully configured Office365 to relay emails from Mailman3. I used the below configuration. change following lines in mailman.cfg: smtp_host: your-domain.com.mail.protection.outlook.com smtp_port: 25 And then configure SMTP Relay Connector in Office365, so it can recognize your server. SMTP relay doesn't use a specific Office 365 mailbox to send email. Option3 of Link: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-s… Could you Please confirm, what should be hardware configuration (ram, processor, disk) to run mailman3 server for medium size organization? This server will have 10-15 lists and some lists having 10k to 20k members. Also what should be DISK SPACE of the server for Archiving emails? Regards, *Waqas Ahmed Khan* p: +923212608044 Skype: waqas-ahmed00 <waqas.ahmed0(a)gmail.com> waqas.ahmed0(a)gmail.com [image: LinkedIn] <http://pk.linkedin.com/pub/waqas-ahmed-khan/15/96a/39a/> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 23, 2020 at 8:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > > Hi, > > > > I have installed mailman3 with postfix. The server is working fine. To > > protect the IPs from blacklisting, I want to relay all emails from > > postfix/mailman to external SMTP servers like O365, Gmail, or our > exchange > > server. > > > I would not recommend using O365 or Gmail as outgoing MTAs. I don't > really know about )365, but I don't think Gmail likes you to send mail > via a gmail server if it is not From: (or maybe envelope from or both) a > gmail or googlemail address. > > > > Could you please confirm is this possible. And how to do its > configuration. > > > It is possible and there are two ways to do it. You can configure this > in Postfix to relay all outgoing mail via some other server. > > > You can configure it in Mailman by setting in the [mta] section of > mailman.cfg > > smtp_host: > smtp_port: > > and presumably for authentication > > smtp_user: > smtp_pass: > > Also see > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > and following for other relevant settings. > > -- > 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/ >

5 years, 8 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

I should clarify a bit. That connection string I mentioned in the previous post is in the docker-compose.yaml file for the docker-mailman containers. For web, it seems the settings.py file for the mailman-web container is configured to parse connection string, but there isn't (I don't think) any provision to set additional options, such as the encoding. So there doesn't appear to be a straightforward way, using the container yaml approach, to pass the 'OPTIONS' for the encoding. It does however look like it is possible to override the whole database connection settings using settings_local.py, but unsure. That would I think be the way to do it, setting the whole database configuration settings per https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project /settings.py#L156 in the settings_local.py file. For core, the connection string seems to accept a tailing "?charset=utf8&use_unicode=1" per https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So for core, maybe just updating the connection string to include "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the recommend encoding... maybe that should be updated? I realize this may be drifting more towards concerning the docker container setup vs. non-containerized core and web. But either way, these seem to be mysql specific caveats that I've certainly missed. Hopefully this helps someone else. Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is recommended, and it needs to be explicitly identified in the database settings for BOTH core and web, and probably somehow at database creation time? Now to see what the best procedure is to put these configuration changes in place, and also update the database? - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, December 9, 2020 9:35 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing On 12/9/20 6:06 PM, matthew(a)alberti.us wrote: > Thanks Mark. Also, just to confirm, should the database connection > string also be updated? In both the core and web configuration, I have > something > like: > > DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb > > Note the trailing UTF-8 encoding stuff isn't there. Should we be > specifying > utf8mb4 there as well? In the mailman.cfg database section, you probably want url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&us mysql+e_unicode=1 I don't know why you would have a DATABASE_URL setting in the web configuration. Exactly where is this? I don't think it would be meaningful in any Django settings. -- 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/

5 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I got this on maillog: [root@localhost log]# cat maillog Jul 24 11:33:13 localhost postfix/postfix-script[2044]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 11:33:13 localhost postfix/postfix-script[2066]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 11:33:13 localhost postfix/postfix-script[2081]: starting the Postfix mai l system Jul 24 11:33:13 localhost postfix/master[2083]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 11:35:29 localhost postfix/postfix-script[2115]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 11:35:29 localhost postfix/postfix-script[2116]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 11:35:29 localhost postfix/postfix-script[2123]: starting the Postfix mai l system Jul 24 11:35:29 localhost postfix/master[2125]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 13:55:31 localhost postfix/postfix-script[2095]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 13:55:31 localhost postfix/postfix-script[2096]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 13:55:31 localhost postfix/postfix-script[2105]: starting the Postfix mai l system Jul 24 13:55:32 localhost postfix/master[2110]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 15:57:26 localhost postfix/postfix-script[2079]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 15:57:26 localhost postfix/postfix-script[2086]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 15:57:26 localhost postfix/postfix-script[2093]: starting the Postfix mai l system Jul 24 15:57:26 localhost postfix/master[2095]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 16:33:01 localhost postfix/postfix-script[1993]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 16:33:01 localhost postfix/postfix-script[1996]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 16:33:01 localhost postfix/postfix-script[2003]: starting the Postfix mai l system Jul 24 16:33:01 localhost postfix/master[2005]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 17:29:21 localhost postfix/postfix-script[2077]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 17:29:21 localhost postfix/postfix-script[2079]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the Postfix mai l system Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version 2.10.1 , configuration /etc/postfix El lun., 24 jul. 2017 a las 17:23, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 02:52 PM, Rafael Mora wrote: > > I did that but I don't have a maillog for today 07.24.2017 > > > The current log is just named 'maillog' the ones with dates are older > logs rotated by logrotate. > > -- > 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

8 years, 7 months

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Mark Sapiro

On 9/8/25 07:22, Sam Darwin via Mailman-users wrote: > How about a feature to include "HTML" in the current Hyperkitty choices of (Text or Markdown) rendering? I don't understand what you envision such a rendering to do. First of all, this setting only affects rendering in HyperKitty thread and message views of archived messages. It has nothing at all to do with messages delivered to list members. Archived messages which contain text/html parts currently render those parts as attachments that can be downloaded. Are you suggesting that "HTML" rendering would render those inline or something else? > A sanitizer must be used to prevent malicious attacks. https://github.com/messense/nh3 . lxml is another package that processes html. > > A sanitizer would be helpful for more aspects. Permit a limited set of markdown so that messages still appear professional. Gitlab/Github don't allow arbitrary fonts or font sizes, right? Mostly remove these tags. > > A way that code blocks could be presented: determine an established list of known codeblock styles. Configure the sanitizer to permit this range of fonts or styling elements. By allowing them through the filter, a code styling is rendered. (It is permitted/allowed to be rendered.) Even better, when the sanitizer recognizes the fonts, it replaces them with an "official" set of codeblock fonts. > > Otherwise, if other font tags are entirely removed, if they are missing, the email client or web ui will decide the font selection, and it will appear "standard". Your reference to email client suggests you are thinking in terms of messages delivered to list members. HyperKitty's rendering mode has nothing to do with that. > In order for both email clients and Hyperkitty to view the same result, the sanitizer should ideally be applied to outgoing emails as well as rendering in the UI. That means this feature would affect more than just Hyperkitty. (i.e. mailman-core). Although, that could be implemented as a separate step, until which time emails would get a full range of HTML, without sanitizing. As far as Mailman core is concerned, Things like this are handled in content filtering. In particular the settings Collapse alternatives and Convert html to plaintext. > In this scheme, ensure outgoing emails are multi-part MIME with plain text and html versions. If the incoming message is multipart/alternative with text/plain and text/html alternatives and content filtering accepts all those MIME types and does not Collapse alternatives, the outgoing message will be the same. If you're suggesting a text/html part outside of a multipart/alternative part should cause Mailman to create a text/plain alternative and convert the text/html part into a multipart/alternative part containing the text/plain and text/html alternatives, that could be done, but I'm not interested in doing it. We already have a mechanism for converting HTML to plain text, but current code replaces the HTML. As far as converting plain text to HTML, the straight forward way to to that is just to wrap it in <pre>..</pre> tags, but there seems to be nothing gained by that. As far as converting urls and email addresses into clickable links, many MUAs already do that. > Some of our users are really in favor of more formatting. > > Others prefer plain text. > > Those who prefer plain text have various arguments that HTML messages will be rendered badly, and won't be legible. All of the settings mentioned are per list, not user option/ > Questions: > > 1. Would "multi-part MIME with plain text and html versions both" solve the problem for users who prefer plain text? If they set their MUA to render the text/plain alternative. > 2. What percentage of email clients that support HTML formatting when sending will also include a plain text rendering of the same content in the outgoing message? Many if not all mainstream ones do or at least have settings to control it, but some do a horrible job. For example if in Yahoo mail one composes in "rich text" and drags and drops or copy/pastes or in some ways even types a link, the generated text/plain alternative doesn't contain the url in any form - see <https://www.grizz.org/wiki/PostingURLsToLists> > 3. Is it usually the responsibility of a receiving mail client to be able to convert HTML to plain text if the user requests it? If a message part is multipart/alternative and the user wants plain text, I think most MUAs will just display the text/plain alternative. If the message is HTML only, I suppose the MUA will convert it somehow. > 4. When mailman-core receives and then sends out a message, can it receive HTML, generate a plain-text version, and then send both? Not currently. It can convert the HTML to plain text using a configured process such as lynx or elinks, but then only the plain text is sent, not both. On the other hand, if the incoming message is multipart/alternative and content filtering is off or appropriately set, the outgoing message will be multipart/alternative. -- 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: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 4 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Allan Hansen

Mark, Will this be part of an upcoming update or micro update to Mailman? Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Mar 31, 2023, at 15:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/31/23 14:17, Andrew Hodgson wrote: >> Hi. >> Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. > > > First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in > ``` > --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 > +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 > @@ -2,13 +2,13 @@ > import os > import sys > > -sys.path.insert(0, '/opt/mailman/mm') > +sys.path.insert(0, '/etc/mailman3') > # The above line is required. The next line doesn't hurt, but it doesn't work > # because the PYTHONPATH environment setting is processed by Python's setup > # and must be in the environment when Python starts to be effective. > -os.environ['PYTHONPATH'] = '/opt/mailman/mm' > +os.environ['PYTHONPATH'] = '/etc/mailman3' > os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' > -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' > +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' > > import django > django.setup() > ``` > Also, look at this > ``` > # If we delete the Django user and there is a Mailman user with no memberships > # shall we delete the Mailman user too. > DELETE_MAILMAN_USER = False > # Shall we delete the Django user if there is a Mailman user with no > # memberships or only if there is no Mailman user. > DELETE_DJANGO_IF_MAILMAN = True > ``` > and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. > > -- > 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 hansen(a)rc.org

2 years, 11 months

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

by Mark Sapiro

On 1/9/22 3:26 AM, Michael Heseltine wrote: >> This isn't your immediate problem, but it is an issue. The above isn't >> too informative. What do you get if you run >> >> /opt/mailman/mm/bin/django-admin qcluster >> >> manually? > > I get the following: > >> # /opt/mailman/mm/bin/django-admin qcluster >> 11:50:41 [Q] INFO Q Cluster autumn-sixteen-tango-march starting. >> 11:50:41 [Q] INFO Process-1:1 ready for work at 3725610 >> 11:50:41 [Q] INFO Process-1:2 ready for work at 3725611 >> 11:50:42 [Q] INFO Process-1:3 ready for work at 3725612 >> 11:50:42 [Q] INFO Process-1:4 ready for work at 3725613 >> 11:50:42 [Q] INFO Process-1:5 monitoring at 3725614 >> 11:50:42 [Q] INFO Process-1 guarding cluster autumn-sixteen-tango-march >> 11:50:42 [Q] INFO Process-1:6 pushing tasks at 3725615 >> 11:50:42 [Q] INFO Q Cluster autumn-sixteen-tango-march running. > > And then nothing until I end the command with Ctrl-C. This is what I would expect. It seems to be working. I'm not sure why it fails when run from systemd. Are you running memcached? systemctl status memcached.service That needs to be installed and running for qcluster. > Sorry, I didn't realize that they were truncated. Here are ( I hope) the full logs from /var/log/syslog: > >> Jan 8 21:24:57 lists systemd[1]: Started GNU Mailman web interfaces. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! WARNING: configuration file should have a valid Python extension. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 209, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.sleep() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 357, in sleep >> Jan 8 21:24:57 lists gunicorn[3707354]: ready = select.select([self.PIPE[0]], [], [], 1.0) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:57 lists gunicorn[3707354]: During handling of the above exception, another exception occurred: >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in <module> >> Jan 8 21:24:57 lists gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 67, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 231, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: super().run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 72, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: Arbiter(self).run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 229, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst.exit_status) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 342, in halt >> Jan 8 21:24:57 lists gunicorn[3707354]: self.stop() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 393, in stop >> Jan 8 21:24:57 lists gunicorn[3707354]: time.sleep(0.1) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Main process exited, code=exited, status=1/FAILURE >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Failed with result 'exit-code'. I'm not sure about this one either. You might want to look at https://stackoverflow.com/questions/24488891/gunicorn-errors-haltserver-hal… or other hits from https://www.google.com/search?q=gunicorn+worker+failed+to+boot Are your files /etc/systemd/system/gunicorn.service /opt/mailman/mm/bin/gunicorn opt/mailman/mm/gunicorn.conf the same as recommended at https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=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, 2 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

Hi Mark! > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 12:19 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > > First, my apologies for not taking note of your MAILMAN_ARCHIVER_FROM > setting in your OP. No worries. I tried to include everything that might be needed for you and the other frequent posters to be able to give me an answer, and all of you respond to a LOT of posts. > On 11/22/22 08:52, Hirayama, Pat wrote: > > Steve wrote: > >> 2. Does settings.py have "from settings_local import *" in it? > > > > Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other > related settings defined at the top of the settings.py file? Or should I update > settings.py based on what is in settings_local.py? > > > Assuming the `from settings_local import *` is at the end of > settings.py, anything defined in settings_local.py will override the > definition in settings.py. There's no need to change settings.py. This is the end of settings.py: # # HyperKitty-specific # # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = False POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' try: from settings_local import * except ImportError: pass I'm assuming that is close enough to the end? <snip> > > The > ``` > ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the > archiving API endpoint was forbidden from IP 172.31.0.1, your > MAILMAN_ARCHIVER_FROM setting may be misconfigured > ``` > message comes from > https://urldefense.com/v3/__https://gitlab.com/mailman/hyperkitty/- > /blob/master/hyperkitty/views/mailman.py*L62__;Iw!!GuAItXPztq0!hLVF14 > B0x45qVgO6PBHbLDw0TH9RiV8rrAVWDBuswab7QFb56LlCxdyihoc- > 2F4ZHdqDTdXzj4YgcLM$ > which only occurs if '172.31.0.1' is not in MAILMAN_ARCHIVER_FROM. Given > that it is in MAILMAN_ARCHIVER_FROM as defined in settings_local.py, the > only thing I can conclude is that the Django settings actually used is > not the settings.py you think it is. > > I don't know offhand even what wsgi service is used in the docker > container or how it is configured, but it needs to set its working > directory to the directory containing settings.py. > So, looking at the Django container, I see this process popping up periodically. I think that means that it is running from the directory specified by "--pythonpath"" (which is where settings.py and settings_local.py are located). I am further assuming that "--settings settings" is ok without a .py extension. 53972 mail 0:00 {django-admin} /usr/local/bin/python /usr/local/bin/django-admin runjobs quarter_hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project/. --settings settings 53978 mail 0:00 {django-admin} /usr/local/bin/python /usr/local/bin/django-admin runjobs minutely --pythonpath /opt/mailman/mailman-suite/mailman-suite_project/. --settings settings > -- > 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: Updating from Ubuntu-20.04 LTE installation

by Abhilash Raj

On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote: > On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > > > 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: > > > It shouldn't be difficult, but I can't give you details because I don't > know exactly how the Debian/Ubuntu package installs things. Also I don't > know whether "current version" refers to the 3.3.1 release or the head > of the https://gitlab.com/mailman/mailman master branch. > > > > Do you think it would be possible, just to replace the code and library > > parts, keeping the database and config files as is? > > > Yes. It should be fairly straightforward. You first need to find where > the Mailman Core package is. You should be able to just replace the > contents of the `mailman` package directory with ours. You may be able > to do this via pip > > pip install --upgrade mailman > > globally or within Mailman's virtualenv if it is installed in a virtualenv. This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages). A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in `/etc/mailman3/` and Mailman Core installed anywhere should just pick that up without any special work. Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume). > However, there are caveats. There are Debian patches at > <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` > patch replaces importlib_resources with importlib.resources because > importlib_resources is not available in Debian. Most of the patches > apply to tests, and for the actual working code, we fixed this > differently as of Mailman 3.3.1, so I don't think you need the Debian > patches. > > > -- > 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)

5 years, 9 months

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

by Jered Floyd

I'll dig at that; thanks. I've just managed to get one of my Google accounts into this "broken" state, although I'm not entirely sure how I did it (or where the broken state is stored). This happened after I tried using the "Sign In" button on a list info page rather than the one in the upper right corner, but that may just be a red herring. I'll report back if I find anything. --Jered ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise 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." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > 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

2 years, 3 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > Finally, I have adapted your init script to get some rudimentary one that I > could use on FreeBSD. > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > have "live" MLs on this server, using mailman-2.1.34. > I am not sure if they can co-exist. I suppose they could, but what might be > the security implication, if any?? I manage more than one server that supports both Mailman 2.1 and Mailman 3 running as user `mailman`. I'm not aware of any security issues. > This is what the init script looks like (rudimentary!!): > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > ### BEGIN INIT INFO > # Provides: GNU Mailman > # Short-Description: Mailman3 Service > # Description: service control for Mailman3 > ### END INIT INFO > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > DESC="GNU Mailman service" > DAEMON=/opt/mailman/mm/bin/mailman > NAME=mailman > USER=mailman3 > GROUP=mailman3 > > # Needed by click > export LANG=en_US.UTF-8 > > # Exit if the package is not installed > [ -x "$DAEMON" ] || exit 0 > > # Load the VERBOSE setting and other rcS variables > #. /lib/init/vars.sh > > # Define LSB log_* functions. > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > # and status_of_proc is working. > #. /lib/lsb/init-functions > > case "$1" in > start) > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > # use --force to remove a stale lock. > /usr/local/bin/sudo -u $USER $DAEMON start --force T don't recommend using --force in init scripts. It *shouldn't* matter because even with --force the master shouldn't break the lock if the pip that set it still exists, but I prefer not to use it. > ;; > stop) > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON stop > ;; > status) > /usr/local/bin/sudo -u $USER $DAEMON status > ;; > reopen) > /usr/local/bin/sudo -u $USER $DAEMON reopen > ;; > restart) > log_daemon_msg "Restarting $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON restart > ;; > *) > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > exit 3 > ;; > esac > > It does start mailman3 for sure, but also complains after a few seconds > with the message: > > (venv) [root@gw /usr/local/etc/rc.d]# > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > DeprecatedWarning: Call to deprecated function __init__(...). API class may > be removed in a future release, use falcon.App instead.* > * **kws)* Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 and 3.0.0a1 and I don't see this warning, but it is only a deprecation warning. It doesn't mean it won't work. > But: > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman ... It seems Mailman core and the rest runner and its workers are all running. > > Assuming that I am using mod_wsgi with Apache, and that I have configured > apache right using > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > .. > should I be able to access the MM3 web UI?? Yes, I think so. > At that point, I am feeling somewhat confused as to what to try next. > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > Jul 25 22:53:16 2020 (40670) Master started > Jul 25 22:53:18 2020 (42036) bounces runner started. > Jul 25 22:53:18 2020 (45205) out runner started. > Jul 25 22:53:19 2020 (41191) archive runner started. > Jul 25 22:53:19 2020 (46670) retry runner started. > Jul 25 22:53:19 2020 (44567) nntp runner started. > Jul 25 22:53:19 2020 (43069) in runner started. > Jul 25 22:53:19 2020 (46960) virgin runner started. > Jul 25 22:53:20 2020 (45720) pipeline runner started. > Jul 25 22:53:20 2020 (47326) digest runner started. > Jul 25 22:53:20 2020 (43755) lmtp runner started. > Jul 25 22:53:20 2020 (45922) rest runner started. > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > http://127.0.0.1:8001 (45922) > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > Jul 25 22:53:21 2020 (42743) command runner started. The above is all fine, but it is just Mailman core. > How do I access the web UI for MM3 now? The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which is at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. Do you have that? If you installed the Apache config literally, the location for Mailman 3 is defined by <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and the URL would be http(s)://your.server/mm3 - have you tried that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Mark Sapiro wrote: > On 1/24/22 15:06, Mark Sapiro wrote: > > On 1/18/22 06:24, Stephan Krinetzki wrote: > > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is > > installed in a venv and deployed using Apache and uwsgi. This works > > quite well so far, only withheld messages cause us a problem: If we > > try to approve them via Postorius, the message is delivered to the > > list immediately, but the success message in Postorius takes a long > > time - on average the process hangs for three minutes until the > > message is no longer displayed. We have already adjusted the timeout > > in gunicorn.cfg, but this does not improve the situation. Are there > > any tips on how we can speed up the REST API? Or is it even a > > configuration error? > > There are two steps in handling the POST for a held message. The first > > step is accepting, rejecting or discarding the message. This is > > happening immediately. > > The second step is handling the poster's moderation action based on the > > choice from the Set member moderation dropdown in the view of the held > > message. This is processed by the code at > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…. > > If no selection has been made, the default value POSTed for > > moderation_choice is no-action and that code is skipped. If it is one > > of the choices Hold for moderation, Reject (with notification), > > Discard (no notification), Accept immediately (bypass other rules) > > or Default processing that is processed. So presumably a selection has > > been made and processing is stuck on getting the member or setting the > > member's moderation action. > > Possibly the logs of your database manager will have information. > > Some additional info. > By gunicorn.cfg, do you mean the file at mailman/config/gunicorn.cfg? If > you are using gunicorn as a wsgi server, that is separate from the > gunicorn serving the REST API and its config doesn't affect the REST > API. The relevant config is mailman/config/gunicorn.cfg?. > Also, I doubt the issue is with the REST API per se, but rather it is in > Mailman core's processing of the particular endpoint and if that is > slow, it is most likely some kind of database issue. Hi Mark, yes, we are using a local copy of the gunicorn.cfg. It is in the home directory of our mailman3 instance (like the mailman.cfg, same directory). We will now look into the postgresql database - maybe there is an index missing or something like that. Thank you for help.

4 years, 1 month

[MM3-users] Re: Creating users via RestAPI / User-Management - a bunch of questions

by Mark Sapiro

On 6/20/25 06:39, Christian Schneider wrote: > Dear Mark and companions, > > somehow I can not cope with the user management... > (I am running a venv-installation, latest stable versions) > > I read this manual: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > and played with the RestAPI calls... > > I know about the fine grained differences between user and member, admin/owner, superuser... > and about the two user databases in PostgreSQL and Django-Framework. I'm not sure what distinction you are making between PostgreSQL and Django-Framework. There are two separate and distinct users, Django users and Mailman core users. Information about both is in the PostgreSQL database. Django users are in the `auth_user` table and Mailman core users are in the `user` table, both in the public schema, although if you split the data into a `mailman` database and a `mailmanweb` database the `auth_user` table is in `mailmanweb` and the `user` table is in `mailman`. > What I stumble upon is the RestAPI calls to create a "working" user (with the ability to login via WebUI). > When I follow the manual (from the url above) I create a user (including password) that appears in the PostgreSQL database. > (And this user is visible on the User-URL (https://example.com/mailman3/users)) > Even when I (via WebUI) set the user as "approved" this user is not able to log in... > I assume this restriction is in accordance to the fact that there is not equivalent Django user. > (There was a mail in the archive of the MM3 user group...stating that one has to use the Django RestAPI to create the appropriate user) The above is correct. The Mailman REST API only deals with Mailman core. Mailman core knows nothing about Django. > When I create the user using the WebUI (https://example.com/accounts/signup/?next=/mailman3/lists/) > the new user is created in the right (complete) way...appearing in the PostgreSQL database and as a user in Django. > How is this sync between the two databases realized? I'm still looking into that, but it isn't the creation of the Django user per se that creates the Mailman user. The process has multiple steps. 1) Sign-up for an account. This creates the Django user and sends an address confirmation email. 2) Click the link in the confirmation email. This takes you to a page with a `Confirm` button to confirm the email address. 3) Click the confirm button. It is not until step 3) that the Mailman user and address records are created. > (The Django user also has the correct status (no staff status / no superuser status / just active status) how is this realized?) Presumably by the sign-up process not setting staff status and superuser status. > As I am not very familiar with python programming (I know Perl/Java/C++ and have an (maybe outdated) concept of OOP), > is there a quick way to implement this kind of sync by copying the register logic from mailman's python action script for registering? I think it must be django-mailman3 that's doing this, but I haven't been able to see how so far. django-mailman3 does override the template for the /accounts/confirm-email page, but this is only to include styling. > Other questions: > Will there be a create_admin_user-script that is callable via CLI (like createsuperuser or create_list)? > (This script ought create a user in PostgreSQL and as Django user) No plans. There are `mailman addmembers` and `mailman admins` commands to add members or admins to a list. Adding an owner or moderator to a list via `mailman admins` will also create a Mailman user for that person if there isn't one already, but it won't create a Django user. > How will a social account provider (like oidc) linkage (in Django) fit in this concept? > Will oidc-accounts be copied to the Django's user database (or PostgreSQL db) or is it an on-the-fly check against the oidc-provider? (I assume second option) > What are the status-flags (staff status/superuser status/active status) of the linked oidc-accounts? (Can I specify the status flags?) I don't offhand know the answers to that, but I think logging in via a social account provider creates a Django user.. > A conceptual thought: > When "user1" (with email user1(a)example.com) is known to django via oidc linkage > and I create "user1" (also with email user1(a)example.com) via RestAPI calls > (following the url https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > do I have a "complete" user then? > I mean a user who is able to login and who can be assigned to a list as admin (e.g.) > (In this case I would not have to care about the Django user database... ;-)) If the user can log in to the web UI with an associated email address, if that address is an admin of a list, the logged in user can admin the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 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/ >

4 years, 2 months

[MM3-users] Re: debian's 3.2.1 mailman package too unreliable in production - Mail held occasionally causes server errors, and unexplained queue/bad messages -

by Mark Sapiro

On 10/20/20 6:30 PM, Alex Schuilenburg via Mailman-users wrote: > We have an issue where a mailing list has had a message sent to it from > a non-member, so the message has been held, but when the list owner or > I attempt to list the held messages for the list we get a Server Error: > "An error occurred while processing your request.". Details of the server error should be in Django's log which I think in the Debian package is named mailmansuite.log. > I see the mail being held in the mailman log with the non-subscriber > reason, and followed the suggestions in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > which worked to look at and discard that held message. The problem > is, there are more and we have over 900 mailing lists > > FYI, we are running:Mailman Core VersionGNU Mailman 3.2.1 (La Villa > Strangiato)Mailman Core API Version3.0Mailman Core Python Version3.7.3 > (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] > > So we are looking at setting up a virtualenv to run the latest mailman3 > 3.3.1 as the 3.2.1 package from debian is looking unstable - barely > usable. Actually, the latest Mailman core is 3.3.2rc2 with the final due by the end of October. While I would never discourage people from installing Mailman from our source distributions, without more understanding of your actual errors, it is difficult to know if that will help. > For example, while poking around I found 641 messages in > queue/bad , but when I inspect them they look fine. If, as mentioned > elsewhere, I rename them to .pck, put them in queue/shunt, and "mailman > unshunt" the mail finally gets delivered. Why work now? Some kind of > transient bug? If they are in queue/bad because of permissions errors, it is not surprising that moving them to .pck files in queue/shunt is successful. > Is 3.3.1 the way to go? > > On that last error, I've now enabled debug and hope to catch why > messages are being dropped into queue/bad instead of being delivered. > Already I have found errors in the mailman log such as: > > PermissionError: [Errno 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.919073+d907eb9512ce11fda515c19d > 723537fc4cb15da2.pck'Oct 20 23:41:35 2020 (9793) Skipping and > preserving unparseable message: > 1603233694.919073+d907eb9512ce11fda515c19d723537fc4cb15da2Oct 20 > 23:41:35 2020 (9787) Uncaught runner exception: [Errno 13] Permission > denied: > '/var/lib/mailman3/queue/archive/1603233694.9209244+a0c1f3aab51d3d202aa > 37911ab453f094b50b450.pck'Oct 20 23:41:35 2020 (9793) Uncaught runner > exception: [Errno 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.9260252+138142eeb15b16b5da16934 > 954d1d3aeb1331198.pck'Oct 20 23:41:35 2020 (9793) Traceback (most > recent call last): File "/usr/lib/python3/dist- > packages/mailman/core/runner.py", line 158, in _one_iteration msg, > msgdata = self.switchboard.dequeue(filebase) File > "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, > in dequeue with open(filename, 'rb') as fp:PermissionError: [Errno > 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.9260252+138142eeb15b16b5da16934 > 954d1d3aeb1331198.pck'Oct 20 23:41:35 2020 (9790) Uncaught runner > exception: [Errno 13] Permission denied: > '/var/lib/mailman3/queue/in/1603233694.9129462+8be9ab12e5dfeab086a1ab8b > 3917550aea313505.pck'Oct 20 23:41:35 2020 (9793) Skipping and > preserving unparseable message: > 1603233694.9260252+138142eeb15b16b5da16934954d1d3aeb1331198Oct 20 > 23:41:35 2020 (9793) Uncaught runner exception: [Errno 13] Permission > denied: > '/var/lib/mailman3/queue/out/1603233694.9269004+5f8572edfb07e0e28b9f0b7 > 928a1184b8c8048ba.pck'Oct 20 23:41:35 2020 (9793) Traceback (most > recent call last): File "/usr/lib/python3/dist- > packages/mailman/core/runner.py", line 158, in _one_iteration msg, > msgdata = self.switchboard.dequeue(filebase) File > "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, > in dequeue with open(filename, 'rb') as fp:PermissionError: [Errno > 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.9269004+5f8572edfb07e0e28b9f0b7 > 928a1184b8c8048ba.pck'Oct 20 23:41:35 2020 (9793) Skipping and > preserving unparseable message: > 1603233694.9269004+5f8572edfb07e0e28b9f0b7928a1184b8c8048ba Were the runners all running as user `list` when the above errors occur. > The mailman3 user, "list", owns and has full rights all the way down: > # ls -ld /var/lib/mailman3/queue/*drwxrwx--- 2 list list 4096 Oct 21 > 01:45 /var/lib/mailman3/queue/archivedrwxrwx--- 2 list list 77824 Oct > 21 00:15 /var/lib/mailman3/queue/baddrwxrwx--- 2 list list 4096 Oct 19 > 10:44 /var/lib/mailman3/queue/bouncesdrwxrwx--- 2 list list 4096 > Oct 5 17:18 /var/lib/mailman3/queue/commanddrwxrwx--- 2 list > list 4096 Oct 21 00:00 /var/lib/mailman3/queue/digestdrwxrwx--- 2 list > list 4096 Oct 21 00:20 /var/lib/mailman3/queue/indrwxrwx--- 2 list > list 4096 Aug 11 18:44 /var/lib/mailman3/queue/nntpdrwxrwx--- 2 list > list 4096 Oct 21 01:45 /var/lib/mailman3/queue/outdrwxrwx--- 2 list > list 4096 Oct 21 01:45 /var/lib/mailman3/queue/pipelinedrwxrwx--- 2 > list list 4096 Aug 11 18:44 /var/lib/mailman3/queue/retrydrwxrwx--- 2 > list list 69632 Oct 21 01:45 /var/lib/mailman3/queue/shuntdrwxrwx--- 2 > list list 4096 Oct 21 00:20 /var/lib/mailman3/queue/virgin > so I'm kinda running out of options why this particular problem is > happening. Any pointers? Or just toss the mailman 3.2.1 debian > package out and go for a virtualenv 3.3.1 mailman? Unexplained permissions errors are often SELinux issues. Is SELinux enabled? If so, have you tried disabling it? -- 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: digests are created but not sent out

by "Jörg M. Schulz"

Arrgh, you got it. There are messages in the shunt directories. But, also in mailman log. Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) Jan 09 12:24:06 2019 (17491) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 324, in _dispose mime = mime_digest.finish() File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish footer = MIMEText(footer_text.encode(self._charset), so the footers may not contain special characters. Will review this one. This is the only thing I hate with python... > Am 09.01.2019 um 18:02 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 1:37 AM, "Jörg M. Schulz" wrote: >> >> Normal, non-digest messages are sent correctly. Administrative messages as well. >> >> Using GNU Mailman 3.2.0 (La Villa Strangiato) >> >> Where could I look for errors / stuck queues? >> >> /var/lib/mailman3/lists >> /var/lib/mailman3/lists/mailman.unswolke.de >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.3.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.2.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.2.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.6.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.4.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.1.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.1.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.3.mmdf > > > When a digest is to be sent by 'mailman digests', the digest.mmdf file > is renamed to digest.x.y.mmdf (x and y are the volume and issue numbers) > and an entry placed in queue/digests to send that digest. The digest > runner then picks up that entry, prepares the digest, queues it in > queue/virgin to be sent to the recipients if any and removes the > digest.x.y.mmdf file. > > Since the digest.x.y.mmdf files are not removed, either the digest > runner is not running at all in which case there will still be entries > in queue/digests or it is encountering an error in processing in which > case there should be messages with tracebacks in Mailman's error log and > probably messages in queue/shunt. > > -- > Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

7 years, 2 months

[MM3-users] Re: new list not working

by Christian

There are no such messages as you describe. After turning on debugging I got this from a test message sent to the new list: Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3499' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: christian(a)naturalintelligence.us Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: redlatinleg(a)lists.ccalternatives.org Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during _handle_client() -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 7:51 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 13:26, Christian via Mailman-users wrote: > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: > christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: > redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost > during _handle_client() > What else is in the smtp.log? There should be messages like <timestamp> (<pid>) <message-id> smtp to redlatinleg(a)lists.ccalternatives.org for nn recips, completed in n.nnn seconds <timestamp> (<pid>) <message-id> post to redlatinleg(a)lists.ccalternatives.org from christian(a)naturalintelligence.us nnn bytes If there aren't, try setting [logging.smtp] level: debug in mailman.cfg, restarting Mailman core and see what you then get in smtp.log. -- 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/ WPMR4JUQOQ6FMT24V3W6WWJQQU4Q6O7E/ This message sent to csa(a)web-analysts.net

3 years

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

by matthew＠alberti.us

Sorry for the double-tap. Apparently https://github.com/maxking/docker-mailman/pull/441 changed the behavior that I said was the default. We might need to see your docker-compose.yaml, with sensitive info removed, to know more about your setup. - Matt Alberti -----Original Message----- From: matthew(a)alberti.us <matthew(a)alberti.us> Sent: Saturday, August 7, 2021 8:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core... # EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens in > /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug > 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 > 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during > _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) > connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- 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/

4 years, 7 months

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

by Onyeibo Oku

Help! Regards Onyeibo On Thu Oct 13, 2022 at 6:03 AM WAT, Onyeibo Oku wrote: > On Wed, 12 Oct 2022 17:52:47 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks Eggert and Sapiro. > > > > > As Eggert suggests, see > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > > follow that. > > I already started out on the above route. Its an adaptation because I > am running Fedora. I had no problem with system-wide installations via > dnf package management. However, some parts of the documentation does > not add up. > > > 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. > > > > I will come to this eventually (assuming that does not break things > later). I aim to get it all working with regular pip packages first. I > have installed mailman core already. > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. > > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? > > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" > > I am lost > > "pip list" within the venv environment confirms that I have "mailman > 3.3.5". What am I missing? > > 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/

3 years, 5 months

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

This isn't doing a lot for my self-esteem. I'm now trying to install mailman-web and mailman-hyperkitty. Running the 'pip install' (as documented here https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-…) is giving me a similar setuptools error to the one I got before, although with a different version number: [SNIPPED successfully downloaded packages] Collecting django-haystack>=2.8.0 (from hyperkitty->mailman-web) Using cached django_haystack-3.3.0.tar.gz (467 kB) Installing build dependencies ... error error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> [2 lines of output] ERROR: Could not find a version that satisfies the requirement setuptools>=61.2 (from versions: none) ERROR: No matching distribution found for setuptools>=61.2 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Running 'pip install setuptools' replies that it's already installed (which is what I expected, because I installed it earlier) Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) I tried clearing pip's cache, but that made no difference. I am running as the mailman user in venv. It seems to be somehow related to the django-haystack package. In fact, running 'pip install django-haystack' results in the same error message. Perhaps I need to take it up with the maintainers of that. -- Henry Hartley Westat RB 2151 -----Original Message----- From: Henry Hartley via Mailman-users <mailman-users(a)mailman3.org> Sent: Friday, June 6, 2025 09:31 To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Trouble Installing Mailman3 CAUTION: External Email * [ This message appears to be from westat.com but the originating sender is external.] >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> >> >> >> The next step in the instructions has me create >> >> /etc/mailman3/mailman.cfg. The first thing in that file is shown as: >> >> >> >> [paths.here] >> >> var_dir: /opt/mailman/mm/var >> >> >> >> Looking in /opt/mailman, there is no mm directory. Should that >> >> have been created, or is that something I need to create myself? >> > >> > You need to create it. I'll update the doc for that too. >> >> Actually, that's wrong. You don't need to create it. The first time you start Mailman core, it will be created. Excellent. Thanks. -- Henry _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://secure-web.cisco.com/1zFhvAPq5v7Gs3kANDBULVLuS95U56cpRwhnFwcvKwwPbI… Archived at: https://secure-web.cisco.com/1FyVIRlyXW9zpUP_wm98qkGB_DRuoOre5YHVvNpUo9unXQ… This message sent to henryhartley(a)westat.com * Please use caution when responding and/or clicking on links as this email originated from outside of Westat.

9 months, 1 week

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:33 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/16/22 22:21, Mark Sapiro wrote: > > > > I suggest you look at ownership and permissions. > > > > ``` > > find /opt/mailman/mm/static/ -not -user mailman > > find /opt/mailman/mm/static/ -not -perm -u+rw > > find /opt/mailman/mm/static/ -type d -not -perm -u+x > > ``` > > and the same on > > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > > > > > >> If the above doesn't reveal anything substantial, then let me know and I > >> can bump up the verbosity. > > > > > > I don't know if --verbosity 3 will reveal anything or not. You could try. > > > Did you see the post at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>? > > Have you tried > ``` > django-admin clear_cache > (venv) mailman@list:~$ /opt/mailman/mm/bin/django-admin clear_cache Cache "default" has been cleared! (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ total 16 drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 . drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 css drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 js (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ total 8 drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/js/ total 8 drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. (venv) mailman@list:~$ So all the css files that were in /opt/mailman/mm/static/CACHE/css/ are gone after running `django-admin clear_cache`. After that, I did run my mailman-post-update script again which created dirfferent files under CACHE/css/ as the date shows (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ total 20 drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 . drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 css drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 js -rw-r--r-- 1 mailman mailman 621 Dec 16 22:46 manifest.json (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ total 176 drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 .. -rw-r--r-- 1 mailman mailman 162923 Dec 16 22:46 output.1d3a3c0dd51d.css -rw-r--r-- 1 mailman mailman 1209 Dec 16 22:46 output.9a7b11621c5a.css -rw-r--r-- 1 mailman mailman 569 Dec 16 22:46 output.e68c4908b3de.css (venv) mailman@list:~$ I then rebooted the system just to be sure everything is restarted. And the PROBLEM IS SOLVED :-) Thank you very much for your time spent in following this up with me to the conclusion. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

When you set DEBUG=False, Django doesn't serve static files because of which you see only text and no styles. http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… If you do set DEBUG=False, you need to serve the static pages somehow. Alternatively in you case, you can remove the part of the `settings.py` which changes the Emailbackend when `DEBUG=False` so that you don't have to worry about serving static files and still send out emails. On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > For testing purpose I turned back to false the DEBUG var and everything > started working fine with HyperKitty > > I don't understand... this is the trace when I click Login from Postorius > to HyperKitty > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > HTTP/1.1" 200 10950 > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > HTTP/1.1" 200 156657 > > > What should I check? > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > > find them: > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > You need to ensure you have a working sass compiler. As I said at > > < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > >, > > See the third bullet under > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > Then you need to run commands like > > > > django-admin collectstatic --clear > > django-admin compress > > > > > > -- > > 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 7 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 11:53 AM, Ken Alker wrote: > > Is the var/messages hierarchy also where all the archived emails are > stored for future viewing via the web interface? No. They are stored in the hyperkitty_email and hyperkitty_attachment tables in the database. >> Also, there is a long thread at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa >> d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be >> relevant. > > I have never used the mailman shell before, but based on the referenced > thread I learned to do this (note that the thread also taught me how to > rewrite it to narrow down to just the list with issues so I didn't > delete held messages in other lists, if my case): > > for verification: > > venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print (f"""\ > ... Sender: {data['_mod_sender']} > ... Subject: {data['_mod_subject']} > ... Date: {data['_mod_hold_date']} > ... Reason: {data['_mod_reason']} > ... """) > ... > and then to delete the two messages: > > (venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.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 sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print(f'request id: {request.id}, deleting') > ... requests.delete_request(request.id) > ... > sbarc-list.lists.netlojix.com > request id: 27, deleting > request id: 28, deleting > >>> > > The result of this, however, was that the web interface still claimed I > had two held messages. I wasn't sure if there was some cron-type > "sweeper" process I had to wait to auto-run or if I had to manually do > something to create an update. I then realized that the sample script > had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered > the script (but it didn't spit out that it deleted anything this time) > and got an error when I did the commit. Was this in the same `mailman shell` interaction or a new one? What was the error? > So, I figured the messages HAD > been delete and the commit wasn't really necessary. When I went back to > the web interface, the number of held messages was at 0 and I no longer > get the original error when clicking on "Held messages", so my issue is > solved. But this does leave me with some educational questions: > > 1) Did I affect something somehow with my "commit", or was there a job > that cleaned things up (if so, what job)? I'm not sure of the sequence of events, but I think you probably looked in Postorius before you quit `mailman shell` and then you quit `mailman shell` with ctrl-D which did an implicit commit. > 2) Is the "commit" even necessary (I saw it in someone else's script in > the thread)? It is necessary to explicitly commit() or quit with ctrl-D to actually update the database. > 3) Is there a way to save a script and then execute it via shell rather > than typing it in every time (it appears from the examples that people > are typing them in every time, which is super tedious; I didn't paste > for fear of doing something damaging, but maybe that would work)? Yes, you can save a script in the bin/ directory in your venv and run it with `mailman shell -r`. See `mailman shell --details`. > 4) Are the request.id's of the messages dynamic/changing, or are they > fixed for life? I thought I'd delete based on exact request.id without > looping but I was afraid maybe they were changing over time and that > this wouldn't be a good idea. Might be nice to know for the future. The request.id is constant for that request object. The request object is fixed for a specific held message request. I.e., a specific held message's request object and its request.id and other attributes are fixed until that request is handled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Sending to mangled 'From' addresses.

by hansen

Thank you, Mark. Yes, the problem is with the mail clients which harvest addresses inappropriately (I never asked them to). I just found the header filter option, which I has been looking for under ’Settings'. Sorry for taking your time. It works great! Yours, Allan > On Jun 1, 2024, at 09:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/31/24 22:23, hansen via Mailman-users wrote: >> Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. > > > DMARC mitigation action ‘Replace From: with list address’ will also place the poster's address in Reply-To: (or Cc: depending on list configuration), so a simple `reply` from a reasonable MUA should go just to the poster. > > >> For example, say the mail client captures my address as >> “Allan Hansen via <listname>” <listaddress> >> then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: >> “Allan Hansen via <listname>” >> and, to make it worse, the actual email address, <listaddress>, is often hidden. > > > If this is the result of a `reply` and not `reply-all` the client is not behaving reasonably. > > >> The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. > > > That is a problem with the client, but I suppose such clients are not uncommon. > >> Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., >> "Allan Hansen via <listname>" > > You could add a header filter on the To header with a regexp like `^.*via <listname>` and the desired action. > >> Should I get onto the other list to request this as an enhancement? > > I don't think that's necessary in this case, as Header filters should do it. > > In general, the best way to request an enhancement is to file an issue with the appropriate GitLab project at `https://gitlab.com/mailman` > > -- > 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 hansen(a)rc.org

1 year, 9 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 6:35 PM, Mark Sapiro wrote: > On 1/14/22 6:11 PM, David Newman wrote: >> On 1/14/22 4:54 PM, Mark Sapiro wrote: >>> >>> It should work. I suspect you need to go to the list's Settings -> >>> Automatic Responses and set `Admin immed notify` to Yes. >> >> >> It's enabled. I think this triggers notifications only for new >> subscription requests, not pending ones. > > > Yes. That will send a single notification at the time of the request > using the `list:admin:action:subscribe.txt` template. Notices of pending > requests are sent by the `mailman notify` command using the > `list:admin:notice:pending.txt` template. > > ... >>> You can test `mailman notify` at any time by running it by hand. >> >> >> Thanks. This still isn't working as intended. I took these steps: >> >> 1. Created the file >> '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' > > > The template name is `list:admin:notice:pending.txt`, not > `list:admin:action:pending.txt`. Thats why it didn't work. Bingo. Thanks -- the template works as intended now. > > ... >> 2. Restarted the mailman3 and mailmanweb services > > > You only needed to restart Mailman core. OK > > > ... >> What I'm trying to do here is replicate a feature from MM2.1, where >> pending notifications had URLs embedded in the message. That's not >> available out of the box in MM3, and if there's a place for feature >> requests I'd be glad to ask that this be made the default. > > > The place for feature requests for Mailman core (which this is) is > https://gitlab.com/mailman/mailman/-/issues, however, this is not > straightforward as Mailman core doesn't know if you even have Postorius > or some other web management UI installed or what the URL to access it > might be. Thus it's not just a simple matter of editing templates. It > would also require a configuration setting for the base URL for the web > admin UI and changes in logic to provide an appropriate replacement > depending on whether or not the base URL was configured. Understood, thanks. Although this distinction is very important for server admins, it's likely not meaningful for many list owners and moderators. For them, MM2.1 sent an email saying "go here" and MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. There is some pending template in use by default, just not one with a URL included. Is this something better handled in the venv and/or Web installation docs? Or should I file a feature request for core, or Postorious or someplace else? Thanks very much! dn > >

4 years, 2 months

[MM3-users] Re: Reply w/Email Clients - From: vs. Reply-To:

by Jay Hamilton-Roth

On Nov 17, 2020, at 5:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/20 2:34 PM, j(a)manygoodideas.com wrote: >> I'm setting up a new list, and a number of new list members are reporting a problem with replying to the thread. Their email clients seem to ignore the Reply-To: field and instead use from From: field. > > > Are you saying that a 'reply' , not 'reply-all' will reply to the From: > only and ignore Reply-To:? If so, the email clients that are doing that > are badly behaved. I can't say they are non-compliant as RFC 5322 > <https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.2> only says: > > The originator fields also provide the information required when > replying to a message. When the "Reply-To:" field is present, it > indicates the address(es) to which the author of the message suggests > that replies be sent. > > > I.e., Reply-To: is only a 'suggestion', but well behaved clients will > follow it. That's exactly what I'm saying. And there's more than a few of these badly behaved clients. >> When they use Reply All, the email is addressed to both the From: and Reply-To:. > > Reply All should reply to the Reply-To:, To: and Cc: addresses and to > From: if there is no Reply-To:. Whether Reply All should include From: > if there is a Reply-To is not well defined. > > >> Reading through previous threads here, I've tried a number of things: >> >> 1) DMARC mitigation action is "Replace From: with list address" >> 2) For Alter Messages - Set "Reply goes to list" >> >> The goal is that we want a reply to go to the list, not the person posting. Since Reply-To seems to be ignored by some clients, I'm hoping there's a way to force the "From" field to become the list address. Thanks in advance for your suggestions! > > If Alter Messages -> Reply goes to list is set to Reply goes to list, > Reply-To: will include the list posting address. What are the clients > that ignore this? Complaints should go to the providers of those. Complaints sent. > > Tf DMARC mitigation action is "Replace From: with list address", that > will happen to messages to which DMARC mitigation action applies. If you > want it to apply to all messages, set DMARC Mitigate unconditionally to > Yes. That fixed it. Thanks again, Mark! > -- > 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/

5 years, 4 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Thanks! Looks resolved however I'm not 100% sure which steps fixed it: My Steps: ``` cat /etc/hosts 127.0.1.1 list.louisvillecommunitygrocery.com list 127.0.0.1 localhost ``` Updated ``` POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' ``` Restarted mailman3 AND mailmanweb service Updated /etc/mailman3/gunicorn.conf adding workers=9 Restarted mailman3 AND mailmanweb service Deleted custom template from Postorious Created new custom template from Postorious Added test user to list User was added with no errors and also received the custom Template. Thanks Mark, Gerald Bonus question: how should I calculate how many workers I should have on my system? Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Wed, Jan 29, 2025 at 2:36 PM <vogt(a)spamcop.net> wrote: > > Sounds somewhat like the problem I have had: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > The problem for me was that I am using gunicorn but did not increase the number of workers… > _______________________________________________ > 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 paul.m.robey(a)gmail.com Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Wed, Jan 29, 2025 at 2:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > > Ok I did install using the > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > I added > > ``` > > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > > ``` > > I hope you didn't add the above literally without replacing > www.example.com with your actual host name. > > It should be > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' > ``` > > > to /etc/mailman3/settings.py and restarted mailman services > > > > However I'm still getting the same error from mailman.log > > > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > > port=8000): Read timed out. (read timeout=5) > > I don't understand why it should still be trying to connect to > localhost:8000. Also, I don't understand why localhost:8000 times out. > What is your setting for localhost in /etc/hosts? it should be > `127.0.0.1`. If it is `::1` that could be the issue. > > > Not sure if I'm editing the correct config file. > > /etc/mailman3/settings.py should be correct. > > -- > 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 paul.m.robey(a)gmail.com

1 year, 1 month

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

Thanks, Mark. I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. The current postfix_vmap has entries like: list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 So, when I try adding entries to a separate vmap file, like: list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com It only goes through normal bounce processing. If I do: list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 Then it goes to the gmail address, and no bounce processing happens. I'm thinking that I can't combine two methods of delivery (LMTP + email address). Do you know if that is correct? Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, October 31, 2024 21:18 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 10/31/24 16:17, Hirayama, Pat wrote: > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://urldefense.com/v3/__https://docs.mailman3.org/projects/mailman/en/l… . Then for example if your list domain is example.com and its alias domain is x.example.com, you could modify one line in the postfix_vmap file for the `listname` mappings from ``` listname-bounces(a)example.com listname-bounces(a)x.example.com ``` to ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` and then run postmap on the file. The problem is any time you create or delete a list or run `mailman aliases` or run `mailman start` with the --generate-alias-file option, the file is regenerated and you will have to edit it again. To avoid that issue, you can create a separate vmap file containing only the ``` listname-bounces(a)example.com listname-bounces(a)x.example.com, person(a)example.com ``` entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry. -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

8 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

content of the file maillog-20170723 (I didn't find mail.log in /var/log): [root@localhost log]# cat maillog-20170723 Jul 17 10:29:19 localhost postfix/postfix-script[1702]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 17 10:29:19 localhost postfix/postfix-script[1760]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 17 10:29:19 localhost postfix/postfix-script[1781]: starting the Postfix mail system Jul 17 10:29:20 localhost postfix/master[1791]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 21 15:19:31 localhost postfix/postfix-script[9273]: refreshing the Postfix mail system Jul 21 15:19:31 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 15:34:54 localhost postfix/postfix-script[9327]: fatal: cannot execute /usr/sbin/postconf! Jul 21 16:30:03 localhost postfix/postfix-script[9471]: refreshing the Postfix mail system Jul 21 16:30:03 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/postfix-script[9528]: refreshing the Postfix mail system Jul 21 16:52:46 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/qmgr[9532]: error: open database /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Jul 21 16:10:47 localhost postfix/postfix-script[2099]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 21 16:10:47 localhost postfix/postfix-script[2105]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 21 16:10:47 localhost postfix/postfix-script[2112]: starting the Postfix mail system Jul 21 16:10:47 localhost postfix/master[2114]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database /var/lib/mailman/var/data/postfix_domains.db: No such file or directory output command 'postconf -n': [root@localhost log]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 html_directory = no inet_interfaces = localhost inet_protocols = all local_recipient_maps = hash:/var/lib/mailman/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES recipient_delimiter = + relay_domains = hash:/var/lib/mailman/var/data/postfix_domains sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop transport_maps = hash:/var/libmailman/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 What's wrong? Thanks El sáb., 22 jul. 2017 a las 22:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/22/2017 05:29 PM, Rafael Mora wrote: > > > > How can I config Mailman/Postfix to send the confirmation email for the > > superuser I created this morning??? > > > What is in Postfix's logs relevant to the attempt to send the mail > (probably /var/log/mail.log)? > > What is the output from 'postconf -n' > > -- > 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

8 years, 7 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

Thank you so much Mark. I appreciate your help! I dropped the list and recreated it, the default value worked for the new list. Using Mailman shell is very helpful. I checked the mailman.log and found the issue. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, September 21, 2020 9:42 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/21/20 9:23 AM, Mohsen Masoudfar wrote: > > 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. > After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" This is <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…> fixed by <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…> in Mailman core 3.2.0. Either upgrade Mailman core or set it via `mailman shell` > 2- I checked the python files and found this file, where, it seems, the default value is defined: > /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 > > I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: > The message is being held because: The message is larger than the 40 KB maximum size Changing that file only affects the default setting for new lists. It doesn't affect any existing list. To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like $ /opt/mailman/mm/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 >>> m.max_message_size 40 >>> m.max_message_size = 0 >>> commit() > 3- I totally agree that the most important issue is the fact that the message vanished with the production list. > I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. > > 4- I checked the folders, under /var/lib/mailman3/queue/, all folders > are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ > out/ pipeline/ retry/ shunt/ virgin/ OK, but what if anything is in Mailman's mailman.log? -- 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…

5 years, 5 months

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Johan Alsina wrote: > Stephen J. Turnbull wrote: > > Hi, i installed mailman3 with virtualenv, all is working fine, the > > admin site works fine, the mailman(postorious) site works fine, but > > when im in hyperkitty the site shows without the css style.. in my > > web browser dev tool it shows like they loaded ok.. > > I think you need to figure out why the dev tool can see the CSS files > > but other environments can't. It sounds exactly like all the other > > Any ideas? :/ > > My static files are loading from > > /static/CACHE/css/output.a0f71925131b.css and > > /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css > > I've run into the "no styles" issue on a number of new hosts where the > > Johan Alsina via Mailman-users writes: > > problems I couldn't diagnose. :-/ > > problem was that somewhere on the path to the CSS files was a > > directory, typically owned by root, without "x" permissions for > > "other" users. That difference across trees is weakly consistent with > > a "somewhere in between" permissions problem. > > Steve > > Hi Steve, thanks for answer, i tried all about permissions and paths and i thins all its ok.. here you can see my paths/permissions.. > General: https://freeimage.host/i/3ok1LDN > Django project: https://freeimage.host/i/3ok1ZxI > Mark Sapiro wrote: > > On 3/17/25 6:46 PM, Johan Alsina via Mailman-users wrote: > > Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. > > Have you run mailman-web collectstatic and mailman-web compress? See > > https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-f... > > If you have, try running them again as mailman-web collectstatic --clear and mailman-web compress. > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > Hi Mark, thanks for the answer. Yes, i tried all variations about collectstatic, clear_cache, etc.. comands with no difference. I dont get any error and the files are collected ok.. > Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. > css files in /static/CACHE not loading: https://freeimage.host/i/3okk6CJ > img files in /static/hyperkitty loading: https://freeimage.host/i/3okkPEv > I tried to move /static/CACHE inside of /static/hyperkitty but when i run collectstatic the files goes again to the default path.. > Thanks in advance.. Sorry, the links about css files and img files are in the wrong order css files in /static/CACHE not loading: https://freeimage.host/i/3okkPEv img files in /static/hyperkitty loading: https://freeimage.host/i/3okk6CJ

1 year

[MM3-users] Re: Apache Conf

by Thomas G

Yes, of course. Nginx and Apache works on the same server. (Nginx is stopped) I would like switch to Apache to add in front of hyperkitty a ldap connection. I need to re-compile nginx for this feature. It's directly available in apache with a module. In fact, a tried directly to integrade LDAP with django ( https://gitlab.com/mailman/postorius/issues/132) without results. Le ven. 19 oct. 2018 à 20:18, Abhilash Raj <maxking(a)asynchronous.in> a écrit : > > > On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > And, you have verified that the files exist at `/opt/mailman/static` on > your host? > > > > > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > > Hi, > > > > Currently, I use a nginx configuration for mailman. It's work > perfectly. > > > > > > > > I tried to do the same with Apache, but the statics files are not > > > > delivered (404). > > > ... > > > > <VirtualHost *:80> > > > > ServerName mailing.ddd.fr > > > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > > > <Location /static/> > > > > Alias "/opt/mailman/static/" > > > > </Location> > > > > > > > > <Location /> > > > > ProxyPass http://localhost:8000/ > > > > ProxyPassReverse http://localhost:8000/ > > > > ProxyPreserveHost On > > > > </Location> > > > > </VirtualHost>/ > > > > > > > > > In Apache, location > > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > > appropriate for resources in the file system. > > > > > > Try > > > > > > Alias /static/ /opt/mailman/static/ > > > > > > not within a location block. > > > > > > -- > > > 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) >

7 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I´m getting this: (env) [mailman@localhost etc]$ mailman stop Shutting down Mailman's master runner (env) [mailman@localhost etc]$ mailman start Starting Mailman's master runner (env) [mailman@localhost etc]$ Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_s erver sock.bind(sa) OSError: [Errno 98] Address already in use During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 198, in main runner.run() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/lmtp.py ", line 242, in run self.lmtp.start() File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py" , line 55, in start raise self._thread_exception File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py" , line 35, in _run ssl=self.ssl_context)) File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in run_until _complete return future.result() File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1047, in create_s erver % (sa, err.strerror.lower())) OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 8024 ): address already in use Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 194, in main runner = make_runner(*args.runner, once=args.once) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 94, in make_runner return runner_class(name, slice) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/rest.py ", line 53, in __init__ self._server = make_server() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/rest/wsgiapp.py ", line 234, in make_server handler_class=AdminWebServiceWSGIRequestHandler) File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 153, in make_se rver server = server_class((host, port), handler_class) File "/usr/local/lib/python3.6/socketserver.py", line 453, in __init__ self.server_bind() File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 50, in server_b ind HTTPServer.server_bind(self) File "/usr/local/lib/python3.6/http/server.py", line 136, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/local/lib/python3.6/socketserver.py", line 467, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address already in use Why does it say Address already in use? El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 12:52 PM, Rafael Mora wrote: > > I made a change for test purpose on the mailman.cfg file and I got this: > > > > > > (env) [mailman@localhost etc]$ mailman restart > > Restarting the Mailman runners > > PID unreadable in: /var/lib/mailman/var/etc/var/master.pid > > [Errno 2] No such file or directory: > > '/var/lib/mailman/var/etc/var/master.pid' > > Is the master even running? > > > > How do I solve this? > > > Try > > mailman stop > mailman start > > -- > 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

8 years, 7 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, my first post was to optimistic - the user tested some other combinations and when he tries to send a signed HTML mail, the server again refuses to accept it with "Diagnostic-Code: smtp; 501 Message has defects". The user suggested that the problem is caused by a line containing only "-- " somewhere in the text, but I can not confirm this. Please find enclosed the refused mail (anonymized). Regards Rainer On Mi, 20 Apr 2022 10:51:38 +0200 Rainer Herbst <rainer.herbst(a)aip.de> wrote: > Dear all, > > as the original poster, I have asked the user to send a test mail >through our mailman3 system (docker image > maxking/mailman-core:0.4.2) and the mail passed. > > The user is now on Apple Mail 16, maybe that does the trick. Please >find enclosed the anonymizied mail source. > > Best regards and thanks for caring even if the problems seems to >affect only a small number of users! > Rainer > > On Fr, 15 Apr 2022 09:03:41 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >> On 4/14/22 21:33, Stephen J. Turnbull wrote: >>> >>> Whether we *want* to do that depends on how much trouble that causes >>> for our main constituency (list and site admins), and whether we can >>> provide discoverable documentation of the problem. My take is that >>> this seems to be an extremely rare problem, and at least some MUAs >>>are >>> able to read the message, so we should let it through. >> >>First, we are not silently dropping this message. We are rejecting it >>at LMTP time so the sender should be notified. >> >> Then the broader question is should we accept all messages with >>defects, almost all of which are spam, or only certain defects and >>which ones. >> >> I note that Apple has now released Mail 16 so maybe they've fixed >>this. My macs are still on Big Sur, so I can't test this. >> >> >> -- >> 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/ >> > > Viele Grüße > > Rainer Herbst > Leiter IT-Service > Phone: +49 331 7499-257 > e-mail: rainer.herbst(a)aip.de > https://www.aip.de > > ----------------------------------------------------------------------------------------------- > Leibniz-Institut für Astrophysik Potsdam (AIP) > An der Sternwarte 16, 14482 Potsdam > > Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach > Stiftung bürgerlichen Rechts > Stiftungsverzeichnis Brandenburg: 26 742-00/7026 > ----------------------------------------------------------------------------------------------- Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

3 years, 11 months

[MM3-users] Re: Change the default value for the General Archive Policy

by Markus Grandpré

Dear Mr Sapiro, many thanks for your reply. When I create a mailing list without an archive, I’ve noticed that the default value under "Settings > Archiving > Archive policy" is always set to "Public archives". I was wondering if it's possible to change the default to "Do not archive this list" instead. Additionally, in an earlier email, you mentioned that a more convenient way to set default values would be introduced in an upcoming version. Could you please let me know the current status of that development? Many thanks in advance. Best regards, Markus Am 6/23/25 um 19:53 schrieb Mark Sapiro: > On 6/23/25 08:03, Markus Grandpré wrote: >> Dear list, >> >> currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public >> archives". I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? >> In Debian 12 I find in </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: > ... >> but have no idea how to change the settings here. Your help is very appreciated. > Are you creating the list in Postorius. If so, you have a choice for list style. Currently those choices are: > ``` > Announce only mailing list style. > Ordinary discussion mailing list style. > Discussion mailing list style with private archives. > ``` > There is currently no style for a list without archives, but you can implement one. See the thread at https:// > lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/Q6QVDWCY… for hints on how to > do this with a plugin. > > Alternatively, you can do it with a patch like: > ``` > --- a/src/mailman/styles/default.py > +++ b/src/mailman/styles/default.py > @@ -18,6 +18,7 @@ > """Application of list styles to new and existing lists.""" > > from mailman.core.i18n import _ > +from mailman.interfaces.archiver import ArchivePolicy > from mailman.interfaces.styles import IStyle > from mailman.styles.base import ( > Announcement, > @@ -91,3 +92,25 @@ class PrivateDefaultStyle( > Private.apply(self, mailing_list) > Discussion.apply(self, mailing_list) > Moderation.apply(self, mailing_list) > + > + > +@public > +@implementer(IStyle) > +class PublicNoArchiveStyle( > + > + Identity, BasicOperation, Bounces, Public, Discussion, Moderation): > + > + """The legacy default style with no archives.""" > + > + name = 'legacy-default-no-archive' > + description = _('Ordinary discussion mailing list style with no archive.') > + > + def apply(self, mailing_list): > + """See `IStyle`.""" > + Identity.apply(self, mailing_list) > + BasicOperation.apply(self, mailing_list) > + Bounces.apply(self, mailing_list) > + Public.apply(self, mailing_list) > + Discussion.apply(self, mailing_list) > + Moderation.apply(self, mailing_list) > + mailing_list.archive_policy = ArchivePolicy.never > ``` > If you are creating lists from the command line `mailman create`, there is a --style-name option to specify the style. > -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

8 months, 3 weeks

[MM3-users] Re: hyperkitty failed to create a thread

by Danil Smirnov

Hi guys, I've updated my containers (though can't confirm for sure the fix is in there; but I see that the 'latest' tag of 'mailman-web' has been rebuilt in the last night). Could you advise how to rebuild the failing threads please? I've done index update with 'django-admin update_index' command but it seems irrelevant to the issue, I still have all those messages separated: https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ Thank you very much! Danil сб, 16 февр. 2019 г. в 18:46, Abhilash Raj <maxking(a)asynchronous.in>: > > > On Thu, Feb 14, 2019, at 11:51 AM, Danil Smirnov wrote: > > Thank you very much for the quick fix, Mark and Abhilash! > > > > Abhilash, could you include the fix into the "latest" version of > > mailman-web container please? > > They are nightly builds, if the fix was merged and the CI went through, > they should > already be in there. > > > > > Btw I wasn't able to find a changelog of Mailman docker images anywhere > and > > 'Releases' page in Github is quite outdated too... Is there any other > > place I should check? > > I have admittedly been too busy to write release notes, but the recent > releases > have seen not too much changes other than version bumps for the included > Mailman packages. > > > > > Danil > > > > вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > > > > > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > > > > > What could be a reason of HyperKitty failing to create a thread from > > > > chained emails? > > > > > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > > > > > "Openvpn and Network mapping" discussion displayed as five threads > > > instead > > > > of only one... > > > > > > > > Any ideas how to improve HyperKitty ability to detect threaded > messages? > > > > > > > > > Thanks for the report. > > > > > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > > > will fix this. > > > > > > -- > > > 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) >

7 years, 1 month

[MM3-users] Re: [ERROR] Error handling request List archivers

by Shashikanth Komandoor

Thank you Mark for guiding me to the benefit of putting the list and so I have added the list. Along with the [archiver.hyperkitty], [mta] and [database], few lines of my mailman.cfg look like below: *[webservice]workers = 4timeout = 900* The above block of webservice is added yesterday for testing or trail as I am getting the above issue. And there is no line that is calling *gunicorn* in my mailman.cfg. Apart from that I tried to locate and see the content of the gunicorn.cfg file 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 <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.graceful_timeout = 30* Please confirm the time I have to change is *graceful_timeout *in *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I have never used or never known about this *gunicorn* but still running the service in production. Please help me and also suggest if I could provide you any more data from giving resolution. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#m_5710631741815235215_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 3:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:13 AM, Shashikanth Komandoor wrote: > > > Never mind please I am sending to you only instead of group as I am > sending you the production content along with the mail. > > I don't see anything there that can't be posted to the > mailman-users(a)mailman3.org list. If your concern is revealing the > support-tnvc.lsmgr.nic.in list id, just replace it with <list-id> or > list.example.com or similar. > > Messages sent to me personally rather than the list suffer many > problems. They are my absolute last priority, and I am only one person, > the collective knowledge of the list is greater. Also, at times I am off > line for several days or longer. > > Finally, there is no opportunity for other members of the community to > benefit from an off-list exchange. > > > When I am trying to browse one of my lists, I am getting "[ERROR] > > Error handling request /3.1/lists/support-tnvc.lsmgr.nic.in/archivers > > <http://support-tnvc.lsmgr.nic.in/archivers>" in the mailman.log and the > > full error message is in attachment. > > Try increasing your gunicorn worker timeout from the default 30 seconds. > I.e., add > > timeout = 90 > > to your gunicorn.cfg and restart gunicorn. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 years, 7 months

[MM3-users] Re: Pb with archive display

by Pierre Malard

Thanks Mark, Effectively we had a problem with the value of « api_key » which were in pseudo value. I fixed that with the value of « MAILMAN_ARCHIVER_KEY ». Unfortunately we still don't have any archives... Here are the logs retrieved from the mailman.log logs: May 05 15:59:42 2022 (579075) Exception in the HyperKitty archiver: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} raise ValueError(result.text) ValueError: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} And in mailman-web.log: WARNING 2022-05-05 13:58:52,996 579167 hyperkitty.views.mailman Could not archive the email with message-id '<C7E61653-D399-466A-BEC3-CE61D567E870(a)teledetection.fr>': character with byte sequence 0xe2 0x80 0x99 in encoding "UTF8" has no equivalent in encoding "LATIN1" Is it a way? I don't understand the message about LATIN1. It seems to me that UTF-8 was the encoding retained in Mailman. > Le 4 mai 2022 à 15:39, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 5/4/22 05:45, Pierre Malard via Mailman-users wrote: >> On the other hand Mailman3 does not seem to take into account the display of the archives. The contributions are indeed in the directory "/var/lib/mailman3/archives/hyperkitty/spool" but HyperKitty does not take them into account when displayed on the Web interface. >> Is this normal? > > No. The messages are in /var/lib/mailman3/archives/hyperkitty/spool because delivery to HyperKitty failed. There should be messages in Mailman's var/logs/mailman about the failures. > > The setting for api_key in mailman-hyperkitty.cfg must match the setting for MAILMAN_ARCHIVER_KEY in your Django settings. Also, the setting for base_url in mailman-hyperkitty.cfg must be good. If you append `/api` to that url, the result should return a page of documentation of HyperKitty's REST API. > > Also see this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > -- > 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/ -- Pierre Malard «Le courage, c'est de chercher la vérité et de la dire, c'est de ne pas subir la loi du mensonge triomphant qui passe et de ne pas faire écho de notre âme, de notre bouche et de nos mains aux applaudissements imbéciles et aux huées fanatiques.» Jean Jaures - "Discours de jeunesse" - 1903 ("`-/")_.-'"``-._ . . `; -._ )-;-,_`) (v_,)' _ )`-.\ ``-' _.- _..-_/ / ((.' ((,.-' ((,/ πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 10 months

[MM3-users] Re: Upgrade path

by David Krantz

Hi. Getting back to this... Some log of what I'm doing. * First git fetch; git pull on all parts. Started new envs to simplify rollback etc. * activate the new 3.5 venv. ( I run the commands one at a time, but this is more compact in text form:) > cd git/mailman; python setup.py build; python setup.py install > cd ../mailman-hyperkitty; python setup.py build; python setup.py install > deactivate activate 2.7 venv, then > cd ../mailmanclient; python setup.py build; python setup.py install > cd ../django-mailman3; python setup.py build; python setup.py install > cd ../postorius; python setup.py build; python setup.py install > cd ../hyperkitty; python setup.py build; python setup.py install So far no errors. Just warnings. Backups: * deployment directory (as user with rw in directory) > tar -cvzf backup.tgz deployment_directory * postgres databases (as user with postgres-priv) > pg_dump maiman | gzip -9 > mailman.bak.gz > pg_dump mailmanweb | gzip -9 > mailmanweb.bak.gz Create new .wsgi-file based on mailman-suite (I used the kludge in the script to get the python path correct) Change apache2.conf to point to new venv and new wsgi-version Updated the mailman3wrapper.sh I use for init to start the service. I could not get hyperkitty interface to run so I deactivated it and set mailman as index instead. It complains that a column is missing, but I cannot get the migrate script to run so I decided that I do not need the archiver as I currently don't use it. So I will have to get back to this and either remove the archiver completely or get it to run. So the line with ^$ in urls.py now is url(r'^$', RedirectView.as_view(url=reverse_lazy('list_index'))), instead, and the line "hyperkitty," is commented in the django application list. cheers. // David On Tue, Aug 8, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/08/2017 04:42 AM, David Krantz wrote: >> >> What is the rekommended way to upgrade to the newest version? (newest >> _usable_ version, of course)? Is it docker-only with a migration from >> the current solution to a docker based? If so, any ideas or pointers >> on how to go about this? > > > You may find this wiki article helpful <https://wiki.list.org/x/17891998>. > > I started with bundler on both this (lists.mailman3.org) and the > mail.python.org installs, but have been updating from the heads of the > various gitlab branches since very early on. > > At the moment, these installations are somewhat ahead of the 3.1 > release, but I am not updating as the latest core has dropped Python 3.4 > support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu > 14.04) servers. (I will probably install 3.6 from source at some point.) > > Please feel free to ask here if you have more specific questions. > > -- > 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/

8 years, 5 months

[MM3-users] Re: Held messages not delivered after approval

by Krinetzki, Stephan

Hi Mark, >That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely >caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. You are my hero! After "patching" the outgoing.py file with the error messages I got Aug 06 09:52:51 2025 (443278) Cannot connect to SMTP server 127.0.0.1 on port 25: HTTPSConnectionPool(host='lists.example.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/hpc-admintreffen-info.lists.example.com/list:member:regular:footer (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)'))) And was shocked. Why is there an SSL Certificate Error? Why can't python requests verify the certificate? So I googled a bit and found, that we can fix this be editing the cacert.pem of certifi. I did, but the error was still there. So I checked my https VHost (Apache btw) and there was a wrong chain in it. Oof. An error, that a browser does not see, but any ssl client. I fixed it and boom - everything works again. Thank you again and thank you Stephen for trying to resolve the problem 😊 -- Stephan Krinetzki IT Center Gruppe: Anwendungsbetrieb und Cloud Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24866 Fax: +49 241 80-22134 krinetzki(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 5, 2025 6:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Held messages not delivered after approval On 8/5/25 02:06, Krinetzki, Stephan wrote: > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost > on port 25 > > The last error is a very often in the mailman.log: That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. Bottom line - check that all sub-directories and files in Mailman's var/templates/ directory are searchable and readable by the Mailman user. -- 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 krinetzki(a)itc.rwth-aachen.de

7 months, 2 weeks

[Test] Baseline

by Playground for testing

I'm going to try a few config changes. This post is just to establish a baseline. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years

[Test] Re: Baseline followup

by Playground for testing

On 03/20/2016 01:22 PM, Playground for testing wrote: > I'm going to try a few config changes. > > This post is just to establish a baseline. I have forced SSL - can I still post? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years

[Test] Re: setting up the mailman-users@mailman3.org list

by Barry Warsaw

On Mar 24, 2016, at 02:35 PM, Mark Sapiro wrote: >[1] Steve has an issue trying to add a second address, but I am unable >to duplicate that. FWIW, I was able to add a second email address. -Barry

9 years, 11 months

[Test] Re: mailman-users@mailman3.org

by Barry Warsaw

On Apr 04, 2016, at 07:38 PM, Mark Sapiro wrote: >Things that need to be fixed soon in core are confirmation required for >email unsubscribe <https://gitlab.com/mailman/mailman/issues/213> and >DMARC mitigations, but I think we can open it up and announce it. Yes, let's do. I'll work on #213 asap. It shouldn't be a ton of work since all the workflow infrastructure exists and unsub workflow is easier than sub workflow. >If no one objects, I'll do that tomorrow. \o/ -Barry

9 years, 11 months

[MM3-users]Re: [Mailman-Announce] New Mailman 3 users list

by Barry Warsaw

On Apr 05, 2016, at 12:13 PM, Mark Sapiro wrote: >I'm happy to announce a new list for Mailman 3 users and others >interested in Mailman 3. Thanks Mark, this is *awesome*. -Barry

9 years, 11 months

[MM3-users]Re: [Mailman-Announce] New Mailman 3 users list

by Adam McGreggor

> On Apr 05, 2016, at 12:13 PM, Mark Sapiro wrote: > Thanks Mark, this is *awesome*. 👍🏼

9 years, 11 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 13, 2016, at 10:11 PM, Mark Sapiro wrote: >However, please correct me if I'm wrong, but there does not appear to be >a way in Postorius to set a list's mime_is_default_digest attribute. I think that's a legacy attribute that should probably go away. It's only defined as a column in the database and set in the default style, but it's not defined in the IMailingList interface or actually *used* anywhere. Cheers, -Barry

9 years, 10 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Barry Warsaw

On May 28, 2016, at 11:06 AM, Mark Sapiro wrote: >There is also mailman.client which provides Python bindings for the REST >API. This is Python 2. Isn't mailman.client bilingual? It should work with Python 3.x and Python 2.y for some versions of x and y. Cheers, -Barry

9 years, 9 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by John Griessen

On 06/18/2016 02:10 PM, Mark Sapiro wrote: > I think in the > long run, you'd be better off with Mailman 3. Is it time to install version 3? Is that going to work with different rewrite rules behind nginx? Will it cure my problem with moderation and nginx and https? Thanks, John Griessen

9 years, 8 months

[MM3-users] Re: [MM3-users]Installation documentation.

by Barry Warsaw

On Jul 03, 2016, at 04:52 PM, Mark Sapiro wrote: >I have now done production installations of Mailman 3 on this server >(lists.mailman3.org) and mail.python.org. > >I've attempted to document this experience at ><https://wiki.list.org/x/17891998>. > >Suggestions for improvement and/or direct edits on the wiki are welcome. This is very useful information Mark, thanks. I added a link to this page from the release notes page: https://wiki.list.org/Mailman3 Let's continue discussion of the lmtp.py patch, or any other thoughts you have on how to better support parallel MM2 and MM3 installations on the same Postfix server. Cheers, -Barry

9 years, 8 months

[MM3-users] Re: Mm3 - new adventure

by SP2L

Hello Mark. On 14/03/17 18:29, Mark Sapiro wrote: > mailman-bundler is out of date and deprecated. You might find > <https://wiki.list.org/x/17891998> of interest. I appreciate prompt response, indeed. Will follow your suggestion verbatim - thank you. I read this too: http://docs.mailman3.org/en/latest/#documentation And yes, I ran: bin/mailman-post-update python manage.py migrate and some more. Best regards -- Tom - SP2L ------------------------------------ It is nice to be important. But it is more important to be nice!

9 years

[MM3-users] Re: Auth question

by David Krantz

On Sun, Mar 26, 2017 at 5:58 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > All of this is fixed in the current GitLab branches. See the login page > at <https://lists.mailman3.org/accounts/login/?next=/mailman3/lists/> > for example. > > You really need to upgrade. Please see > <https://wiki.list.org/x/17891998> for a discussion of how you can do that. When starting this as the recipe seems reasonable I find that I have no reliable source for git links for the parts. Some of the git links I find are marked with "do not use" so it is a bit hard having confidence in selecting one of the others. Cheers // David

8 years, 11 months

[MM3-users] Re: Moving mm2 mail archives to mm3

by Tom Browder

On Thu, Jul 20, 2017 at 15:36 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/20/2017 01:20 PM, Tom Browder wrote: > > Is there any way to move my old mm2 archives to mm3? ... Thanks, Mark! -Tom >

8 years, 7 months

[MM3-users] Re: MM3 statistics

by Stephen J. Turnbull

Mark Sapiro writes: > On 07/20/2017 01:22 PM, Tom Browder wrote: > > Are there any plugins or programs for mm3 statistics? > > > None that I'm aware of. Systers is working on some extensions (this really needs to change the database schema, so plugins aren't really appropriate), but they're very specific to their operation, and to some extent tied into organization-specific extensions. Most detailed statistics are concerned with subscriptions and unsubscriptions. If you can be more specific about the statistics you want, I can compare to the Systers' implementation. Steve

8 years, 7 months

[MM3-users] Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 10:59 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > @gazorg beat you to it. See > <https://gitlab.com/mailman/mailman/issues/407> and feel free to comment > there. Well, that is me or at least my standard handle at gmail and similar. :-) I should set a footer in my email. Or find a better shortname. // David

8 years, 5 months

[MM3-users] Re: confirm mail rejected

by tlhackque

On 02-Oct-17 13:28, Mark Sapiro wrote: > > I'll be working on a fix. My inclination is to change all the regexp > -confirm and -bounces table entries from, e.g., > /^list-bounces(a)example\.com$/ to /^list-bounces(+.*)?(a)example\.com$/ > Er, if you want it to work: /^list-bounces(a)example\.com$/ to /^list-bounces(\+.*)?(a)example\.com$/ ^------- .

8 years, 5 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Simon

Am 08.10.2017 um 01:48 schrieb Mark Sapiro: > $ bin/mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > The variable 'm' is the list(a)example.com mailing list > m.max_message_size = nn > commit() Thanks. Worked wonderfully. S

8 years, 5 months

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

by Pierre Abbat

On Wednesday, October 25, 2017 3:22:15 PM EDT Mark Sapiro wrote: > See this thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/ > B66VJVCQZOI24GIY5TR2RDZMVTR3HDBJ/> Thanks! So they switched Alfred for Nestor and I applied the patch and recovered the scepter. root@lists:/# mailman info GNU Mailman 3.1.0 (Between The Wheels) Python 3.5.2 (default, Sep 14 2017, 22:51:06) [GCC 5.4.0 20160609] config file: /var/etc/mailman.cfg db url: sqlite://///var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Pierre -- When a barnacle settles down, its brain disintegrates. Já não percebe nada, já não percebe nada.

8 years, 4 months

[MM3-users] Re: changing secrets on a prod instance

by Barry Warsaw

On Oct 25, 2017, at 19:46, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/25/2017 03:53 PM, Dmitry Makovey wrote: >> >> as soon as I've changed REST API creds mailman-core started throwing >> errors about "Unauthorized" Rest requests. > > You need to set them in mailman.cfg > [webservice] > admin_user: new value > admin_pass: new_value Also, don’t forget to restart Mailman after you’ve edited the config file. -Barry

8 years, 4 months

[MM3-users] Re: Message shows up individually but not in the thread

by Marvin Gülker

Am 04. November 2017 um 14:02 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/04/2017 01:52 PM, Marvin Gülker wrote: > > > > Don't name it or it happens. This new thread post[1] never reached the > > front page. Can Hyperkitty be forced somehow to rebuild its entire > > internal structure, ideally by reading all mails in again? > > > django-admin update_index > > (It can take a while) Thanks! -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 4 months

[MM3-users] Re: list of subscribers

by Peter Münster

On Fri, Feb 02 2018, Mark Sapiro wrote: >> Where on the web interface is it possible to see the list of subscribers >> of a mailing list please? > > The short answer is it's a tab on the list's settings page, but you have > to be a list or site admin to even see the tab. Yes, the question is rather: where can *normal* members (or moderators) can see the subscriber list? -- Peter

8 years, 1 month

[MM3-users] Re: list of subscribers

by Peter Münster

On Fri, Feb 02 2018, Mark Sapiro wrote: >> Yes, the question is rather: where can *normal* members (or moderators) >> can see the subscriber list? > > Currently, they can't. If you think they should be able to, you can file > an issue at <https://gitlab.com/mailman/postorius/issues/new>. Thanks. Done. It seems, that even the owner of the list cannot get the full names of the subscribers, only the email addresses. Is there any other possibility for the owner (or the site admin) to get the subscriber list with full names (perhaps with some Python scripting)? TIA for any help, -- Peter

8 years, 1 month

[MM3-users] Re: Message Personalization: embed User name in header/footer

by Johannes Winter

Am Sun, 6 May 2018 07:26:45 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 5/6/18 7:16 AM, Asaf Ohayon wrote: > > Thanks, > > I understand those features are not available (yet) on Postorius > > > We're working on getting template editing in Postorius for release > later this month. > Cool! I hope you also fix this issue https://gitlab.com/mailman/mailman/issues/409 while doing do? Best, Johannes

7 years, 10 months

[MM3-users] Re: GDPR - save subscriptions confirmation emails

by Stephen J. Turnbull

Mark Sapiro writes: > I think the best thing is to implement logging. With a blockchain! "Blockchain" is a joke, of course, but I think there would need to be some way to verifiably construct an audit trail. Maybe the OTK is enough?

7 years, 9 months

[MM3-users] Re: GDPR - save subscriptions confirmation emails

by contact＠maadix.net

El 04/06/18 a las 05:52, Mark Sapiro escribió: > Of course, you might be able to get your MTA to save all mail to the > LIST-confirm address to a separate mailbox in addition to delivering it > to Mailman. Ye , this is the best solution. That's what I finally did. Thank you very much Mark. Maddish -- Maadix *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

7 years, 9 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Joe Steeve

On Tue, 2018-07-17 at 22:04 -0700, Mark Sapiro wrote: > You would need to stop Mailman core and all Django processes including > cron jobs and WSGI processes to ensure nothing is accessing the SQLite > database, update the database section in mailman.cfg and the DATABASES > settings in your Django settings, use SQLite tools to dump the relevant > database(s) and PostgreSQL tools to create and load them, and finally > restart Mailman core and all Django processes. Fantastic. I'll give it a shot and update. -- Joe Steeve HiPro IT Solutions Private Limited http://www.hipro.co.in/

7 years, 8 months

[MM3-users] Re: footer message

by Abhijith PA

Hi. On Wednesday 29 August 2018 08:53 AM, Mark Sapiro wrote: > On 08/28/2018 06:46 PM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> Is there any way to enable footer for some lists at the same time >> disable for lists. I maintain an mailman3 instance and some of the lists >> in it need the footer message well some not. > > You can make list specific templates for list:member:regular:footer > and/or list:member:digest:footer. If the template is empty, no footer > will be added. If I understand correctly, temp@lists.example.com:member:regular:footer file need to created for /temp mailinglist/ ? --abhijith

7 years, 6 months

[MM3-users] Re: Stability issues

by Michael Schultheiss

Mark Sapiro wrote: > When it is unresponsive what is the state of the 'rest' runner and is it > listening on localhost:8001? I believe it's still listening on localhost:8001. I'll add some additional checks to our monitoring system to help us track down process crashes. > > What do you do to 'fix' it? To "fix" it, we restart mailman core with our systemd service script. -- ------------------------------------------------------------- Michael Schultheiss, RHCSA, RHCE OIT Administration Sr. Unix Systems Engineer Ivy Tech Community College schultmc(a)ivytech.edu

7 years, 6 months

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Mark Sapiro wrote: > On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > > 2) How do I change the default for existing lists > > Postorius -> Settings -> Digest Sorry, I was unclear here. I was aware of changing the size in the web interface, but what I meant was changing the Digest Size Threshold value for all lists using REST API. Is that possible? -- Henrik Rasmussen

7 years, 5 months

[MM3-users] Re: About the link destination of the logo image of the homepage

by Stephen J. Turnbull

Mark Sapiro writes: > > In the Wikipedia English version, the following address is > > introduced as mailman's website. > > > > www.gnu.org/software/mailman/ > > It probably should be <http://www.list.org/>, but that's up to wikipedia. Having "official" home pages point to GNU is a Stallmaniac thing. We probably shouldn't mess with it.

7 years, 5 months

[MM3-users] Re: MM3 vs. Sympa

by Tom Browder

On Sat, Oct 20, 2018 at 12:12 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/20/18 7:55 AM, Tom Browder wrote: > > > > Before I go, I would appreciate anyone giving me a good reason to stay with > > MM (besides excellent support and a welcoming community—one which is a ... > Mailman is implemented in Python, not Perl ;) Thanks for the reply, Mark (but I am a Perl user at heart!). -Tom

7 years, 5 months

[MM3-users] Re: Mailman3-Web lots of database queries

by Stefan Tatschner

On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > No. This is not normal. This is apparently coming from Django qcluster. > At least it is qcluster that uses the django_q_ormq table, but these > repeated queries are not normal, at least I don't see them in the sites > I administer. These calls are normal, since qcluster polls the database at a high rate: https://django-q.readthedocs.io/en/latest/configure.html#poll Fortunately this setting can be reduced, but yeah, polling happens though. Stefan

7 years, 3 months

[MM3-users] Re: Button unsubscribe

by Ángel

On 2018-12-07 at 10:17 -0800, Mark Sapiro wrote: > Finally, one-click unsubscribe without confirmation is dangerous. > People > forward list messages to others and even reply to the list without > removing the one-click unsubscribe link and then wonder why they get > removed from the list. At least with confirmation, they only wonder > why they got a confirmation request. Not to mention that some antispam/antivirus on common providers will click the message links, thus autounsubscribing the client even before the email reaches its inbox...

7 years, 3 months

[MM3-users] Re: Mailman3 via Docker and NGINX

by brian＠emwd.com

Mark Sapiro wrote: > They could be in a conf.d file, but in this case they are in > sites-available/020-mailman.conf and symlinked from sites-enabled/020-mailman.conf. I am not sure what you mean. What documentation recommends using sites-enabled/020-mailman.conf or is this your own custom setup you have for lists.mailman3.org? I am using Docker which has nothing that references the use of such file paths/directories.

7 years, 3 months

[MM3-users] Re: no mails to list members

by Thomas Stein

On Thursday, 3 January 2019 20:58:19 CET Mark Sapiro wrote: > On 1/3/19 7:43 AM, Thomas Stein wrote: > > > > Just saw the message is in /var/lib/mailman3/queue/shunt. What messages are going there? Something > > wrong with my setup? > > > Look in Mailman's mailman.log for an error message and Traceback along > with the shunting message which will describe the exception that caused > the shunting. Thanks for your answer. So the the file in queue/shunt contains information too? I will have a look. cheers t.

7 years, 2 months

[MM3-users] Re: Separating Lists by Domain

by brian＠emwd.com

So who manages Postorius? Is that a whole separate application from Mailman 3? Is there a way we can get whoever the developer is to update it where we can separate lists by domain the way Hyperkitty does? Mark Sapiro refers to this in the following post: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Thanks, Brian

7 years, 2 months

[MM3-users] Re: Separating Lists by Domain

by Stephen J. Turnbull

Abhilash Raj writes: > > Is there a way we can get [Postorius updated] where we can > > separate lists by domain the way Hyperkitty does? Mark Sapiro > > refers to this in the following post: > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at > https://gitlab.com/mailman/postorius/issues Is this feature GSoC-able, or too small? Steve

7 years, 2 months

[MM3-users] Re: Avoiding the List name in TO or CC headers

by mail＠nickwynja.com

Mark Sapiro wrote: >No. It is placed in Cc: to facilitate replies to the list. To not do this you would need to modify mailman/handlers/cook_headers.py. I've raised an issue with a proposal to add this feature as an option: https://gitlab.com/mailman/mailman/issues/531 -- Nick Wynja

7 years, 2 months

[MM3-users] Re: Update a member's display_name

by Nick Wynja

On 01/17/19 at 14:43, Mark Sapiro <mark(a)msapiro.net> wrote: > > So there is no member display_name per se. The display_name is the > display_name of the associated IUser or IAddress, and these are global. > > The bottom line is there is not a way to update just a single instance > of "member" of a list rather than the site-wide user or address? I see; understood. Thanks for explaining.

7 years, 2 months

[MM3-users] Re: Strange error in uwsgi-error.log

by brian＠emwd.com

Mark Sapiro wrote: > This looks like <https://gitlab.com/mailman/hyperkitty/issues/211> Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors. Brian

7 years, 1 month

[MM3-users] Re: Tracking from gravatar

by worik

On 15/02/19 3:51 PM, Mark Sapiro wrote: > You can disable them by setting > > GRAVATAR_SECURE_URL = '' > > in your local settings. See > <https://github.com/twaddington/django-gravatar> Where do I make that setting? There is nothing like it in any of my files. 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)

7 years, 1 month

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > If you post an issue at <https://gitlab.com/mailman/mailman/issues>, > one of our GSOC aspirants may pick it up. Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-) -Ralph

6 years, 11 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Stephen J. Turnbull

Ralph Seichter writes: > * Mark Sapiro: > > > If you post an issue at <https://gitlab.com/mailman/mailman/issues>, > > one of our GSOC aspirants may pick it up. > > Done, although I wonder if any GSOC participant would want to write > documentation instead of code... ;-) For their actual, Google-supported, project, Google explicitly excludes documentation. But for our purposes, they do need a qualifying commit to demonstrate they've figured out how to get changes through our process and into merge requests, a purely adminstrative qualification. Doc patches are easy to write and get approved quickly! :-) Steve

6 years, 11 months

[MM3-users] Re: Delete archive of mailing list

by Torge Riedel

Am 24.03.19 um 16:36 schrieb Mark Sapiro: > On 3/24/19 5:18 AM, Torge Riedel wrote: >> Is there a (non-) official way to delete the archive? I want a clean >> environment for the later user to test mailman3. > > See <https://gitlab.com/mailman/hyperkitty/issues/3> for a suggestion of > commands to run via 'django shell'. > Thanks, I did a manual clean up of database.

6 years, 11 months

[MM3-users] Re: Disable user registration

by Torge Riedel

Am 28.03.19 um 18:47 schrieb Mark Sapiro: > On 3/28/19 10:41 AM, Abhilash Raj wrote: >> Nothing yet, I have some ideas though. Opened a ticket here[1]. >> >> >> [1]: https://gitlab.com/mailman/django-mailman3/issues/ > Or https://gitlab.com/mailman/django-mailman3/issues/23 to get to the > specific issue. > Thank you, I've left a comment to describe my scenario.

6 years, 11 months

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > and what are the Content-Types of all the subparts? According to "attachment.htm" in "Held Messages", the content type (PDF document) is "<meta http-equiv="Content-Type" content="text/html; charset=utf-8">" > Presumably, this list was imported from MM 2.1, and the same filtering > would have applied there. That's right > I'll post a follow-up with how to change pass_types via mailman shell > when I work it out. Look forward to that, thanks. -- Henrik Rasmussen

6 years, 10 months

[MM3-users] WSGI: gunicorn and uwsgi

by andrew.bernard＠gmail.com

Using the Ubuntu 19 packages for all the mailman suite, uwsgi is the Python WSGI server included. I have now switched over to a full build from current source from gitlab, following Mark Sapiro's excellent instructions. It would appear that the current code has the use of gunicorn built in. Is gunicorn the preferred way now to run the mailman Django apps? Is it worth spending time converting everything to use uwsgi, or should I go with the flow and use gunicorn? What are the advantages of gunicorn over uwsgi?

6 years, 9 months

[MM3-users] Re: Postorius performance with over 1000 pending users

by Nick

On 06/08/19 at 18:06, Mark Sapiro <mark(a)msapiro.net> wrote: > mailman shell -l your.list.id > util = getUtility(IPendings) > for token, data in util.find(mlist=m, pend_type='subscription'): > util.confirm(token, expunge=True) Thanks! In trying to learn more about preventing spam registrations, what methods does Postorius successfully employ to reduce spam signups through the "anonymous_subscribe" form?

6 years, 9 months

[MM3-users] Re: howto reallow a banned email ?

by Nicolas Pettiaux

Le 2019-06-19 6:48, Mark Sapiro a écrit : > On 6/18/19 9:40 PM, Nicolas Pettiaux wrote: >> much thanks. I use mailman 2 interface (and will switch soon to 3) > > This list is for Mailman 3. > > The appropriate list for Mailman 2 questions is > mailman-users(a)python.org > <https://mail.python.org/mailman/listinfo/mailman-users>. much thanks. Sorry !

6 years, 9 months

[MM3-users] Re: Confirmation for subscriptions

by Andrew Bernard

Hi Mark, Happens for any user subscribing by web or email. Setting to 'Moderate' works fine. Andrew On Mon, 24 Jun 2019 at 04:06, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/23/19 7:24 AM, andrew.bernard(a)gmail.com wrote: > > Suddenly stopped working. For all the lists I have created, suddenly the > confirm setting is ignored for subscriptions and users are subscribed right > away. > > > I assume you are looking at the Postorius List Settings -> Subscription > Policy. That should reflect the setting in core. > > How are these users requesting subscription/being subscribed? > > >

6 years, 8 months

[MM3-users] Re: How to see post headers

by Andrew Bernard

Gzip file. Sorry for my casual mistake. Andrew On 13/7/19 11:01 am, Mark Sapiro wrote: > It's not a zip file, it's a gzip file. What are you trying to open it with? >

6 years, 8 months

[MM3-users] Re: Delete a single email or thread from hyperkitty archive

by Andrew Bernard

On 16/07/2019 9:22 am, Mark Sapiro wrote: > You are looking at a thread view. To see a message view, follow the > "Permalink for this message" link at the bottom of the message (the > chain-link icon to the right of the up/down votes and the "A' icons). > > Or you can go to the URL in the Archived-At: header in the email message > received from the list. Ah! Thanks Mark. Solved. Andrew

6 years, 8 months

[MM3-users] Re: Hyperkitty reply indent

by Andrew Bernard

On Thu, 18 Jul 2019 at 09:18, Mark Sapiro <mark(a)msapiro.net> wrote: > I thought that demographic didn't use email either, not to mention email > lists. (Maybe that's why the default phone email clients all suck.) > Yeah. And now they tell me they want an app on the phone for the list. Of Android mail clients, I recently found K9 Mail. The lists look good in that program. Andrew

6 years, 8 months

[MM3-users] Re: Show diplay_name in a list

by Joel Lord

On 9/29/19 5:59 PM, Mark Sapiro wrote: >> Any idea what I was missing there? > Often, member.display_name doesn't exist or is "None". This seems to also be the problem that I submitted a while back (6 months ago?) that the notification to the moderator of subscription requests, which should include both display name and email address of the requestor, only has the email address. We've been trying to track the problem down in code but it keeps going deeper and deeper... -- Joel Lord Web Administrator, Alpha Psi Omega Grand Cast etc... etc... etc...

6 years, 5 months

[MM3-users] Re: Search problem in 3.2.1?

by Mark Dadgar

On Oct 23, 2019, at 7:48 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > I haven't tried Xapian. On mail.python.org, I dont recall how many total > messages there were at the time I switched from Whoosh to ElasticSearch, > but a full index rebuild with Whoosh would take several hours, whereas > ElasticSearch took about 10 minutes. ElasticSearch has been indexing for ~36 hours now. /var/lib/elasticsearch is currently 5.5GB. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 4 months

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Tue, Jan 30 2018, Mark Sapiro wrote: > Mailman is not processing bounces other than storing them in the > database. See <https://gitlab.com/mailman/mailman/issues/343>. Hi, It seems, that the content (the body) of the bounce-message is not stored. How could I please get and see the content? TIA for any hints, -- Peter

6 years, 3 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Am 11. Dezember 2019 um 11:48 Uhr -0800 schrieb Mark Sapiro: >I get a Forbidden status on that URL. Oops. cp copied the file permissions and I didn't check. Should work now. -- Blog: https://mg.guelker.eu

6 years, 3 months

[MM3-users] Re: *** SPAM *** Re: bounces with empty message-id

by Peter Münster

On Wed, Dec 11 2019, Mark Sapiro wrote: > You need to tweek your MTA to copy -bounces mail to you or just send > them to you since they aren't processed anyway. Thanks, it was much simpler, than I guessed: virtual_alias_domains takes precedence over relay_recipient_maps, so I only needed to add some lines to /etc/postfix/virtual. -- Peter

6 years, 3 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail

by Torge Riedel

Am 18.01.20 um 19:45 schrieb Mark Sapiro: > The best way to report a bug, feature request, issue, etc is to use the > trackers at gitlab.com. In the case of Mailman core, this is > <https://gitlab.com/mailman/mailman/issues> Hi Mark, just opened a new issue: https://gitlab.com/mailman/mailman/issues/670 Best regards Torge

6 years, 2 months

[MM3-users] Re: Mass subscribe gives HTTP Error 500 when using custom template

by Jeffrey D

Mark Sapiro wrote: > On 1/28/20 6:15 AM, Jeffrey D wrote: > > What is your setting in settings(_local).py for > POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > It should be the base URL for connecting to Postorius. I.e., if you > normally connect to Postorius via https://www.example.com/postorius, it > should be https://www.example.com Thanks, changing the POSTORIUS_TEMPLATE_BASE_URL fixing the issue.

6 years, 1 month

[MM3-users] Re: Your Dashboard

by Stephen J. Turnbull

Mark Sapiro writes: > There's no overall dashboard per se. The message actually refers to > whatever web UI you use to manage the list. The default template > for this message is non-specific because it comes from Mailman > core, and core doesn't know if you are using Postorius or some > other web management system or non at all, and even if it were to > assume Postorius, it doesn't know the URL. IMO, we should fix this, similar to the way we deal with archives (provide a callback API so the webmin(s) can tell us where it is (they are)). WDYT? Steve

6 years, 1 month

[MM3-users] Re: Uncaught runner exception

by Stephen J. Turnbull

Mark Sapiro writes: > Whether this is something you did wrong s/wrong/accidentally/ :-) > or an issue with whatever init/systemd scripts run these things, I > can't say. Maybe there's a way we can check the account running mailman, sort of a runtime check_perms. I doubt suid is a good idea, but maybe a warning? Steve

5 years, 11 months

[MM3-users] Re: Different Mail Domain Cause Key Error

by Brian Carpenter

On 4/21/20 4:53 PM, Mark Sapiro wrote: > The issue is the FILTER_VHOST = True setting is broken. Thanks Mark. I was wondering how this would turn out using the FILTER_VHOST setting. Unfortunately we have to have this setting turned on. Maybe I can get the client to agree to use the web domain as part of their list address. Appreciate your help as always! Stay healthy. -- 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, 10 months

[MM3-users] Re: Can't open PID file after start.

by Torge Riedel

Am 22.04.20 um 17:13 schrieb Mark Sapiro: > It's normal and just info. The key is "yet?" The [Service] section in > Mailman's systemd service file references /opt/mailman/var/master.pid as > PIDFile and systemd looks for it before Mailman has created it. Hi Mark, thanks for your answer. Best Torge

5 years, 10 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gilles Filippini

Mark Sapiro a écrit le 23/04/2020 à 20:02 : > On 4/23/20 10:27 AM, Gilles Filippini wrote: >> >> You'll have also to remove the compiled files from the __pycache__ >> directory: > > > This is not necessary. If the .py file is newer than the .pyc file in > the __pycache__ directory, the interpreter will use the .py file and if > it has permission will rewrite the .pyc file. Indeed, if it has permission. When testing in user space it does not have permission. These files are owned by root. _g.

5 years, 10 months

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

(venv-3.6) [root@empire mailman]# django-admin createsuperuser No Django settings specified. Unknown command: 'createsuperuser' Type 'django-admin help' for usage. (venv-3.6) [root@empire mailman]# django-admin help Type 'django-admin help <subcommand>' for help on a specific subcommand. Available subcommands: [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate runserver sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). On 4/28/20 3:35 PM, Mark Sapiro wrote: > django-admin createsuperuser

5 years, 10 months

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

Good morning mark, still not working. Not sure what the issue is. (venv-3.6) [root@empire mailman-suite_project]# django-admin --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --setting settings createsuperuser No Django settings specified. Unknown command: '--pythonpath' Type 'django-admin help' for usage. (venv-3.6) [root@empire mailman-suite_project]# Ralf On 4/28/20 4:23 PM, Mark Sapiro wrote: > On 4/28/20 1:18 PM, Ralf Wiegand wrote: >> Mark - I have a hard time following this. >> >> /path/to/where/your/settings/are located >> >> what settings? what do I am looking for? > Based on the traceback from another post: > > --pythonpath /opt/mailman/mailman-suite/mailman-suite_project > --settings settings.py >

5 years, 10 months

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

hey Mark, that worked. Thank YOU. Got one step ahead. So after creating a admin account and logging in via the GUI, I get this error message: IntegrityError at /accounts/login/ UNIQUE constraint failed: account_emailaddress.email Request Method: POST Request URL: http://192.168.0.27:8000/accounts/login/ Django Version: 2.2.12 Exception Type: IntegrityError Exception Value: UNIQUE constraint failed: account_emailaddress.email Exception Location: /opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/sqlite3/base.py in execute, line 383 Python Executable: /opt/mailman/venv-3.6/bin/python Python Version: 3.6.8 What does this mean? Thx, ralf On 4/29/20 10:19 AM, Mark Sapiro wrote: > django-admin createsuperuser \ > --pythonpath /opt/mailman/mailman-suite/mailman-suite_project \ > --settings settings

5 years, 10 months

[MM3-users] Re: Installation Wooes

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 5/2/20 12:51 AM, Samir Faci wrote: >> A few questions about an Ubuntu install. >> >> i'm getting this behavior: >> AttributeError: module 'time' has no attribute 'clock' >> I'm on python 3.8.2 >It time.clock() went away in Python 3.8. Mailman versions older than >3.3.0 are not compatible with Python 3.8. You need to upgrade Mailman core. I think this is a bug in Ubuntu 20.04. Python3 package is: Python3 3.8.2-0ubuntu2 https://packages.ubuntu.com/search?suite=focal&keywords=python3 Mailman3 is: 3.2.2-1 https://packages.ubuntu.com/search?suite=focal&keywords=mailman3 Andrew.

5 years, 10 months

[MM3-users] Re: Handling of Mail from non-subscribers

by Peter Adebahr

On 5/9/20 1:55 AM, Mark Sapiro wrote: >> "Hold for moderation" has been set. > > Set in "Default action to take when a non-member posts to the list"? yep > > If that is the case, find the non-member in Users -> Non-Members and it does'nt show up there, "list has no nonmembers"

5 years, 10 months

[MM3-users] Re: Handling of Mail from non-subscribers

by Peter Adebahr

On 5/9/20 4:39 AM, Mark Sapiro wrote: > > The fix is to patch your Mailman installation with the changes at > <https://gitlab.com/mailman/mailman/-/merge_requests/552/diffs?commit_id=ea0…>. > As Ubuntu's version is 3.2.2, not 3.3, the full patch did no apply cleanly, but > > x = random.random() + right_now % 1.0 + time.clock() % 1.0 > to > x = random.random() + right_now % 1.0 + time.process_time() % 1.0 > > in mailman/utilities/uid.py. > this was the solution :)))))))))) Great support, Mark - Thank you very much! Best regards, Peter

5 years, 10 months

[MM3-users] Re: Weird hourly indexing error

by Brian Carpenter

On 5/13/20 3:24 PM, Mark Sapiro wrote: > DigitalOcean also hosts the server that supports all the @python.org > email including hundreds of Mailman 2 and 3 lists. You can also get a > credit with DigitalOcean by following the link at the bottom of > <https://mail.python.org/mailman/listinfo/>. How can I get the Mailman developers to promote my Mailman hosting services? -- 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, 10 months

[MM3-users] Re: Github auth deprecated API

by Quanah Gibson-Mount

--On Thursday, May 14, 2020 9:41 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > It is fixed in the django-allauth GitHub repository by > <https://github.com/pennersr/django-allauth/pull/2458> > > You can apply the patch from that PR to your django-allauth installation > to fix this. tyvm! --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 10 months

[MM3-users] Re: New releases

by Danil Smirnov

On Tue, 9 Jun 2020 at 19:01, Mark Sapiro <mark(a)msapiro.net> wrote: > I'm not sure about the above error. > > 'sassc -t compressed {infile} {outfile}' > > is defined in `settings` COMPRESS_PRECOMPILERS, but it is a command to > be run as part of `django-admin compress`, not a module to be imported. > > Possibly running `django-admin compress` before starting Hyperkitty > would have avoided this. > Well, if I run "./manage.py compress" in the mailman-web container, I'm getting CommandError: Offline compression is disabled. Set COMPRESS_OFFLINE or use the --force to override. Danil

5 years, 9 months

[MM3-users] Re: New releases

by Danil Smirnov

On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > Do you have settings like > > > COMPRESS_PRECOMPILERS = ( > > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > > ) > I have COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) > > COMPRESS_OFFLINE = True > > COMPRESS_ENABLED = True > These two are commented out. Danil

5 years, 9 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 10, 2020, at 11:33 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > I suspect the issue here is the 'weirdness' is in the Subject: rather > than the message body. The script we were using only looked at the body. [snip] > There's probably a reply there somewhere that has the Subject: but > didn't quote the bad stuff in the body. That fixed it. It took a couple of passes with various multiples of zero-width spaces, but the archive finally completely indexed. Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

[MM3-users] Re: manage.py runjobs hourly

by Mark Dadgar

On Jun 11, 2020, at 1:33 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > Those messages depend on system load. Sometimes you'll see bunches of > them and sometimes (at least on mail.python.org which is the most busy > server I am involved with) you won't see any for up to a week or longer. > > Run > > django-admin qifno > > to get the current django q stats. Roger that. Ignore, it is. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 16, 2020, at 12:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > This looks like another manifestation of the issue reported at > https://gitlab.com/mailman/django-mailman3/-/issues/35 and > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > If you are running django-mailman3 1.3.3 and haven't upgraded to > django-mailman3 1.3.4, see the above list post for a workaround. I am running whatever the current ubuntu packages are (for the moment - my Postgres migrations was in preparation to move to something more current). I will try the cache clear and see what happens. Thanks, Mark. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 6:13 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > I don't know about the failure. That probably is due to the version > mismatch. The malformation is my fault. There should be an empty line > following the last line. > > You didn't say what your HyperKitty version is, but here's a patch > against 1.3.0. If this doesn't work, you could just try patching it by hand. OK, the patch against 1.3.0 appears to be working. Thank you. > I'm going fishing tomorrow so I won't be here much longer. > Enjoy the fishing! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 8 months

[MM3-users] Re: Creating new lists

by Gilles Filippini

Mark Sapiro a écrit le 19/07/2020 à 16:44 : > On 7/19/20 7:19 AM, Gilles Filippini wrote: >> Brian Carpenter a écrit le 19/07/2020 à 15:58 : >>> >>> I believe you need to grant them superuser status in order to create >>> lists. That can be accomplish via the Django admin panel: > ...> >> It works. Thanks! But then what is the purpose of being a domain owner? > > Domain owners should be able to create lists in their domains, but > that's not available yet. See > <https://gitlab.com/mailman/postorius/-/issues/291>. Thanks! _g.

5 years, 8 months

[MM3-users] Re: Announce Only List

by Quanah Gibson-Mount

--On Friday, August 14, 2020 2:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Or leave everyone's moderation action at list default and post with an > Approved: <password> (pseodo)header. See > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/d > ocs/approved.html>. For the OpenLDAP announce list, we set it so emergency moderation is in effect, no one is allowed to post to it without specific approval. ;) --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 7 months

[MM3-users] Re: Problem with list creation

by Stephen J. Turnbull

Mark Sapiro writes: > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > We increased timeout in mailman.cfg This looks like the issue in Shashikanth's post, too: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… They are also creating more than 1000 lists. Do we know why these timeouts are happening? (Search for "list creation times out" returns no results in either core or Postorius issues.)

5 years, 6 months

[MM3-users] Re: Template path

by Seth Seeger

> On Sep 17, 2020, at 12:54 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Something appears to be trying to connect to REST on port 8000 I found this (older) email: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… that does say that the POSTORIUS_TEMPLATE_BASE_URL should be “http://mailman-web:8000” Seth

5 years, 6 months

[MM3-users] Re: Office365 posts shunted (authres.core.SyntaxError)

by Stephen J. Turnbull

Mark Sapiro writes: > I think that's fine. Also, you should look at > <https://gitlab.com/mailman/mailman/-/issues/765>. I agree with Mark. I was pretty sure something like that would work, but I haven't looked at the code in a while, so didn't know exactly where to patch. I'll take a look at it tomorrow, and see if I can spot any edge cases, but that's probably as simple as it looks. Steve

5 years, 6 months

[MM3-users] Re: Unable to remove non-member

by Brian Carpenter

On 9/29/20 12:40 AM, Mark Sapiro wrote: > Is that all it said? The code says it is > > The user could not be removed: <error message> > > Where <error message> is the relevant HTTP error. It says: The user could not be removed: Nothing comes after the colon. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Unable to remove non-member

by Brian Carpenter

On 9/29/20 1:18 PM, Mark Sapiro wrote: > I see the issue. when mailmanclient processes the delete request from > Postorius it calls the REST API DELETE method with the URL > lists/<listname>/<role>/<address> and the address is `quoted` with > urllib.parse.quote_plus, co in this case, the URL becomes > lists/<listname>/nonmember/z_email%2Fdomain.org.za(a)domain.org.za > > This is all fine except the REST API doesn't call > urllib.parse.unquote_plus to change the %2F back to slash. This is now > reported at<https://gitlab.com/mailman/mailman/-/issues/774>. Thanks Mark! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Brian Carpenter

On 9/30/20 11:52 AM, Mark Sapiro wrote: >> 2. I would find the postorius UI much easier to cope with if the >> default template was 'populated' into the UI wherever it was non-blank, >> rather than the UI starting off as if no templates were defined at all. Our Affinity admin interface does that: Affinity Template -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:08:58 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Since you are running the command as user `mailman`, the file must be > readable by that user. Is it? > ls -hl members.txt: -rw-rw-r--. 1 mailman mailman 78 Oct 14 16:15 members.txt See file permissions and ownership above. Unless mailman3 expects a certain Selinux context. -- Onyeibo

5 years, 5 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:08:58 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > > Since you are running the command as user `mailman`, the file must be > readable by that user. Is it? > This question inspired me to run mailman3 directly. It worked! However, I had to execute mailman3 from: /usr/libexec/mailman3/mailman rather than: /usr/bin/mailman3 (or just, ... mailman3). What is the recommended way to run mailman3 please?

5 years, 5 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Stephen J. Turnbull

Mark Sapiro writes: > In my case, the `mailman` command I run invokes a bash file that looks like > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman \ > -C "/opt/mailman/mm/mailman.cfg" \ > $@ IIRC shell scripts have a race condition, although I don't recall the conditions under which it's exploitable. Perhaps SELinux is sensitive to that. I don't really see how we can take responsibility for such issues except to document it as one user's experience.

5 years, 5 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/19/20 10:23 PM, Mark Sapiro wrote: > And the import21 created the user and address records for this user. Does the same thing for a new subscriber as well. So there is no pathway to change a real name that is associated with an email address. None. Zilch. Mailman 2 made this so easy and Mailman 3 made it impossible. I will let someone else file the bug report. You don't really think that this is an issue which means it will be years before it is addressed. So I will save me some time. I will learn to live with it. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: mailman import21

by Brian Carpenter

On 10/11/20 11:40 AM, Mark Sapiro wrote: > As I said, (msg|digest)_(header|footer) are MM 2.1 list attributes, not > templates. Those, and I think only those, are converted to > var/templates/lists/listname/lc/ templates by import21. I forgot to say thank you for the above information. That makes sense of what I am seeing with imports. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Member Issue Discovered

by Mark Dadgar

On Oct 20, 2020, at 8:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > 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. That was by design!? As an admin, that was so irritating. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: migration from 2.1 - owners and moderators

by Alex Schuilenburg

On 24/10/2020 19:29, Mark Sapiro wrote: > Those are Django tasks and don't affect this. You also need to run > `mailman digests --periodic` to send periodic digests (see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>) > and `mailman notify` to send periodic moderator notices (see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>). Thanks for reminding me I need to upgrade :-) 3.2.1 Does not have "notify" I'll wager that the sporadic notification messages are down to this version, so upgrading just bumped up my todo. -- Alex

5 years, 4 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Stephen J. Turnbull

Mark Sapiro writes: > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. Shouldn't Postorius's setup.py be checking for this? Steve

5 years, 4 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 5:05 PM, Mark Sapiro wrote: > Why do you keep bringing this up? The current design of Mailman core > does not remove the user when the user unsubscribes from a list, even if > it is their only subscription. We know you don't like this behavior, but > there are reasons for it. > > On the other hand, when a user removes their account, the circumstance > is different and we do remove the user's information in this case > because that's what the user asked for. Just clarifying Mark. I was surprised by your answer that's all. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Torge Riedel

Am 28.10.20 um 20:09 schrieb Mark Sapiro: > What does your systemd mailman.service script contain for ExecReload? ExecReload=/opt/mailman/core/bin/mailman.sh restart > What crons run at the time of the anomalous timestamps? I checked that and came to the idea, that there might by a reboot of the machine at that time. Maybe it is caused by start mailman & postfix at the same time or not in the "correct" order (postfix first, then mailman)? Kind regards Torge

5 years, 4 months

[MM3-users] Re: Django errors after deleting a thread

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: On 11/24/20 12:45 PM, peter(a)chubb.wattle.id.au wrote: >> E.g. Internal Server Error: >> /hyperkitty/list/list@domain/top-threads Mark> This should resolve itself eventually if you are running the Mark> Django periodic jobs, but to fix it you can manually run Mark> your_django_admin_command runjob recent_threads_cache Mark> which is a daily job which refreshes the recent threads cache. That did it. BTW thankyou *very* much for being so responsive on this mailing list. It's much appreciated. Peter C

5 years, 3 months

[MM3-users] Re: Mailmansuite.log Entries

by Brian Carpenter

On 12/1/20 8:22 PM, Mark Sapiro wrote: > Those come from the HyperKitty sync_mailman job which is run by > hyperkitty_import if you don't specify --no-sync-mailman, but is also > one of the Django daily jobs. Ok but those number are the same for thousands of entries and apparently are being logged for weeks. That can't be good. How does one fix this? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

[MM3-users] Re: Moderated Signup with "info" box?

by Brian Carpenter

On 12/7/20 11:15 PM, Mark Sapiro wrote: > On 12/7/20 7:55 PM, Brian Carpenter wrote: >> Thank you for the clarification. I did not know that. Is that made clear >> in the documentation? > > See > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. > > Thanks Mark! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

[MM3-users] Re: troubleshooting hyperkitty

by Morris Jones

On 12/10/2020 8:21 AM, Mark Sapiro wrote: BTW, is archiving enabled for the list? See Postorius -> Settings -> Archiving. Good thought, it's set to "Public archives" But there's something ominous just below that setting, a headline that says "Active archivers" with no value beside it. Mojo -- Morris Jones, Monrovia, CA [1]BridgeMojo [2]Old Town Sidewalk Astronomers [3]Mojo's Blog References 1. http://bridgemojo.com/ 2. http://otastro.org/ 3. http://mojo.whiteoaks.com/

5 years, 3 months

[MM3-users] Re: required cron entries?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [201231 19:28]: > On 12/31/20 2:49 AM, Andreas Barth wrote: > > Looking in the source code, there is a ./cron/crontab.in.in however > > references to scripts in port_me/ directory. > > That's all old Mailman 2.1 stuff. ignore it. Can we replace that by a mailman3 cron tab? (I'm happy to write that as merge request if useful, but I assume that should be done rather by opening a bug report and using gitlabs features and not inline per mail) Andi

5 years, 2 months

[MM3-users] Re: required cron entries?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210102 01:07]: > I think the real solution is to just remove the mailman/cron directory > and at least some of the mailman/port_me/ files. The cron/crontab.in.in > file is just a distraction. Well, or replace it with just a README.rst pointing to the web page (having something called "cron" in the source tree doesn't sound like a mistake to me). Regards, Andi

5 years, 2 months

[MM3-users] Re: required cron entries?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210102 00:40]: > Do you mean you have messages in the shunt queue that were shunted > because of this error? yes (but my mail was just "I have the rare case where it isn't spam" :) ) > If so, just running Mailman's `mailman unshunt` command should reprocess > and deliver those. Yes, thanks, that's what I already understood from your last mail and did (after removing duplicates). Thanks for all for your great help. Andi

5 years, 2 months

[MM3-users] Re: Header Filter madness

by Brian Carpenter

Mark Sapiro wrote: > > What's in the X-Mailman-Rule-* headers of the post that should be > but > isn't held? > Are there other header filter rules besides the one that doesn't work? This is what the client provided me: X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-listname.listdomain.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header

5 years, 2 months

[MM3-users] Re: How to approve moderated messages via email?

by Brian Carpenter

Thanks Mark. On 1/22/21 3:45 PM, Mark Sapiro wrote: > On 1/22/21 11:16 AM, Brian Carpenter wrote: >> What is the protocol to approve moderated messages via email? I hope I >> asking the question correctly. >> > > You can't. See <https://gitlab.com/mailman/mailman/-/issues/169> > -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Module Not Found Error after update

by Brian Carpenter

On 2/4/21 11:46 AM, Mark Sapiro wrote: > You need django-mailman3 1.3.5 > > > While all are not required in this case, when you upgrade like this with > pip, you should upgrade all of django-mailman3, hyperkitty, mailman, > mailmanclient, mailman-hyperkitty and postorius. Thanks Mark. Perhaps Abhilash can include that in the instructions on the following page for future releases: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I will make a note of this in my own personal documentation and the Debian 10 How-to guide that I am currently working on. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Sync list members

by Brian Carpenter

On 2/7/21 6:13 PM, Mark Sapiro wrote: > On 2/7/21 2:44 PM, Brian Carpenter wrote: >> Hello, >> >> Outside of using the REST API, are there any other ways to sync a >> Mailman 3 roster with a file that contains list members? > > If I understand correctly what you mean, see the `mailman syncmembers > --help`. > Thanks Mark. That is EXACTLY what I was needing. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Postorius upgrade issue

by Joel Lord

Well, for a change that was an easy fix... Thanks! On 2/8/2021 6:47 PM, Mark Sapiro wrote: > On 2/8/21 3:38 PM, Joel Lord wrote: >> So I tried to do this after upgrading, fortunately only from 1 point >> release back, and I get "ModuleNotFoundError: No module named >> 'paintstore'" from the collectstatic. > > > Do you still have 'paintstore' in INSTALLED_APPS in your Django settings? > -- Joel Lord

5 years, 1 month

[MM3-users] Re: Moderator Approval Subscription template

by Brian Carpenter

On 2/8/21 9:27 PM, Mark Sapiro wrote: > That is an issue because the expanded template is filled and wrapped at > column 70 with mailman.utilities.string.wrap(). > > However, you can avoid wrapping the URL by preceding it in the template > with a space. Something like Mark, you are a beautiful person. Thank you. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Reason for Shunting

by Brian Carpenter

On 2/9/21 5:25 PM, Mark Sapiro wrote: > On 2/9/21 2:03 PM, Brian Carpenter wrote: >> Is there a way to determine why a message keeps ending up in the shunt >> queue? >> > > Look in mailman.log for the `SHUNTING` message and the traceback that > immediately preceeds it. Thanks Mark. The reason was: Feb 09 16:40:11 2021 (2614) Uncaught runner exception: Multiple rows were found for one_or_none() sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Feb 09 16:40:11 2021 (2614) SHUNTING: 1612906811.2642436+cd8e97a66b6d0c2b73c2adde71a4914108c3e673 I have no idea what that means. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Problems with web interface after upgrade

by Victoriano Giralt

De: Mark Sapiro <mark(a)msapiro.net> > On 2/9/21 11:11 AM, Brian Carpenter wrote: >> >> So I am pretty sure you are going to need to install something like Dart >> Sass. Perhaps the following thread might be helpful: :-( Thanks Brian > Or, on recent Debian/Ubuntu at least, just > ``` > apt install sassc > ``` Thanks Mark! It's CentOS7, but sassc was already installed and has -t as short for --style. Mailman+Postorius+Hyperkitty were humming smoothly until I did the upgrade. We need another idea ... -- Victoriano Giralt Sent from mobile device

5 years, 1 month

[MM3-users] Re: Moderation Action Changed After Import

by Brian Carpenter

On 2/12/21 3:14 PM, Mark Sapiro wrote: > It seems you imported to an existing list with import21. This is > probably not a good idea. > > Those members who were moderated members of the MM 2.1 list will have > their moderation action set to Hold, Reject or Discard based on the 2.1 > list setting. I don't understand. Does not the import21 script require the Mailman 3 list to be created first? The Mailman 3 list was new with no members when I ran the import script. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Moderation Action Changed After Import

by Brian Carpenter

On 2/12/21 5:38 PM, Mark Sapiro wrote: > However, to address your concern, As far as I know, import21 is doing > the right thing. If you want to send me the config.pck you imported, I > can try to verify that. Thanks Mark. I will get that off to you sometime tomorrow. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 8:15 PM, Mark Sapiro wrote: > I agree and appreciate that Brian is very supportive. In my initial > reply, it was not clear to me that Brian had referred you here which is > the only reason I pointed out that he was your primary line of support. It really didn't matter as the question by Tom was clearly related to Mailman 3 and not to Affinity. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Imported Digest Settings

by Brian Carpenter

On 2/16/21 6:13 PM, Mark Sapiro wrote: > On 2/16/21 2:28 PM, Brian Carpenter wrote: >> The beginning of my OP stated I was using Mailman 3.3.3. > Then please get me a copy of the complete raw digest message so I can > try to find the underlying issue. > Not sure how to do that. Do you mean have the list member forward their garbled digest message to me? Is that what you need? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: archiving problem & updates

by Brian Carpenter

On 2/19/21 1:13 PM, Mark Sapiro wrote: > I'm not sure what causes Request Entity Too Large, but I suspect it is a > very large message body. You can examine the messages in > var/archives/hyperkitty/spool/ with Mailman's `bin/mailman qfile` > command, but I suspect the problem is caused by the largest of the > files. You can just move it aside, and that should allow archiving to > resume. I believe that is a NGINX error message. The following link has more information: https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-l… -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 00:39, Mark Sapiro ha scritto: > On 2/28/21 3:34 PM, blackout69 wrote: > > > What happened to the posts that were sent and not delivered. are they in > Mailman's var/queue/shunt/ queue? Are there errors reported in Mailman's > mailman.log? No errors in my mailman.log After restarting the mailman3 and mailman3-web services, the posts arrived regularly. -- blackout69

5 years

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 01:22, Mark Sapiro ha scritto: > On 2/28/21 4:00 PM, blackout69 wrote: > So the posts must have been in one of Mailman's queues (maybe `in` or > `pipeline`, not `out` unless the messages were successfully archived > before the restart) and the corresponding runner was hung or gone. There > should be some indication in mailman.log if a runner died. mailman.log does not report anything about the dead runner. However I would like to know where I find the status of the various runners (in, pipeline and out)Thank you -- blackout69

5 years

[MM3-users] Re: Domain ownership issues

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> This is still very much a work in progress. Currently domain Mark> owners can (I think) create domain specific templates, but they Mark> can't create lists in their domains. So is there any way to delegate list creation? Or does the site owner always have to do it? Peter C

5 years

[MM3-users] Re: statistics monitoring for Mailman3

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/11/21 7:03 PM, Mohsen Masoudfar wrote: > > Hi, > > > > I am wondering if there is a monitoring application available for > > Mailman3 to display statistics about the number of emails send > > for each maillist. There was a Systers "dashboard" project, but it was mostly aimed at subscribers. Statistics were mentioned, but I don't recall if they were implemented in a systematic way. Steve

5 years

[MM3-users] Re: Five Year Old Issue

by Brian Carpenter

On 3/14/21 9:25 PM, Mark Sapiro wrote: > On 3/14/21 5:51 PM, Brian Carpenter wrote: >> So this means the fix will show up in the next stable release? > > Yes, the fix is committed to gitlab and will be in the next release of > Mailman core to PyPI. > > Thanks Mark! That should make one of my clients very happy. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: statistics monitoring for Mailman3

by Seth Seeger

On Mon, Mar 15, 2021, at 11:32 AM, Seth Seeger wrote: > > > On Mar 12, 2021, at 12:10 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > You inspired me. See <https://www.msapiro.net/scripts/smtp_report>. > > I get the following error: > > File "./smtp_report", line 44 > print(f' {lname}: {tot}') > ^ > SyntaxError: invalid syntax > > I'm running python3 (3.5.3), and I'm afraid I don't know enough python > to know what's wrong. My wife fixed it! f-strings don't show up until Python 3.6. She rewrote the two print statements as: print(' ' + lname + ': ' + str(tot)) Seth

5 years

[MM3-users] Re: CC header

by Brian Carpenter

On 3/18/21 3:02 PM, Mark Sapiro wrote: > Yes. Header filters can be set on any header. You specify the header to > match on and the regexp to match with. The header can be anything, even > say `x-never-heard-of` in which case the match will be against any > `X-Never-Heard-Of:` (case insensitive) header that happens to be in the > message Thanks Mark. That is good to know. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

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

by Jens Günther

I did have the first setting, yes. The second one no, but activated it now, no change. Am 20.03.21 um 00:00 schrieb Mark Sapiro: > I don't use uwsgi so I can't advise on its configuration, but do you have > > USE_X_FORWARDED_HOST = True > SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') > > in your Django settings?

5 years

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

by Jens Günther

Mh, actually I don't know, what you mean. I only do have one config-file and that's the one I posted :-( ((Probably I should update the suite to 3.3.3 before continuing to figure out what's wrong. I just thought before installing everything to run with the stable one provided by Debian, seems that it wasn't the best idea :-) )) Am 20.03.21 um 02:25 schrieb Mark Sapiro: > > How about the actual uwsgi config. Maybe something like /etc/uwsgi.ini > > See https://uwsgi-docs.readthedocs.io/en/latest/Configuration.html > >

5 years

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Brian Carpenter

On 3/27/21 6:42 PM, Mark Sapiro wrote: > Ooops, Abhilash is correct. I have a bad habit of focusing on what's in > the body of a post and sometimes missing relevant info in the subject. > Sorry. Ok, can you or Abhilash reply to my previous questions. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >``` >msg["Message-ID"] = "<%s>" % re.sub('[ <>\r\n]', '', self.message_id) >``` Thanks that did the trick. Will this need to go in the upstream release or is there any way I could re-import those messages into the database with a newer version of the import command from the original mbox from 2.1 to fix this? Thanks. Andrew.

4 years, 10 months

[MM3-users] Sad news - Brian Carpenter

by smorytko＠gmail.com

https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. Rest in peace Brian. Steve Morytko

4 years, 10 months

[MM3-users] Re: Sad news - Brian Carpenter

by Mark Dadgar

On May 12, 2021, at 12:45 PM, smorytko(a)gmail.com wrote: > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. > > Rest in peace Brian. That’s awful. Brian was a great help to me in setting up a solid MM3 installation after my mess of a self-install and he’s been a constant source of assistance on this list. RIP Brian. 😞 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

[MM3-users] Sad news - Brian Carpenter

by blackout69

Il 12/05/21 21:45, smorytko(a)gmail.com ha scritto: > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. > Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. > Rest in peace Brian. I knew Brian from this list. I read his posts with great interest because I considered him a person of great competence and seriousness. We will miss him very much. Rest in peace Brian. 😞 -- blackout69

4 years, 10 months

[MM3-users] Re: OS upgrade - anything to take care of?

by Torge Riedel

Am 13.05.21 um 21:06 schrieb Mark Sapiro: > On the other hand, if the symlinks in the venv are to things like > /usr/bin/python3 and /usr/lib/python3 which used to point to 3.6 > versions and after upgrade point to 3.8 versions, it should just work. Hi, yes, that is the case on the machine I already upgraded. But I looked to all directories in venv and saw some "non-symlinked" python 3.6 stuff. So I will go the "new venv" approach Andrew mentioned. Just to be safe. Kind regards Torge

4 years, 10 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Dadgar

On May 18, 2021, at 7:58 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > In case you haven't done it, I think just deleting one of the addresses > (the non-primary one) in Django's Email Addresses section will solve > your issue. Yes, it did! Thanks for the help, as always. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

[MM3-users] Re: Bounce counter visibility for List Admins

by Mark Dadgar

On May 19, 2021, at 8:41 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In the next release of Mailman core (3.3.5), lists will have a > `bounce_notify_owner_on_bounce_increment` setting which if True, will > send to the list admins a notice including the triggering DSN when a > user's bounce score is incremented. This setting will also be exposed in > Postorius 1.3.5. That’s great news. This is a pain point for me as well. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

[MM3-users] Getting connection timed out

by blackout69

Il 23/05/21 01:21, Mark Sapiro ha scritto: > Can you successfully telnet to port 25 on mail.simail.it from the > Mailman server? No > If you can connect (via telnet) to port 25 on mail.simail.it from the > Mailman server, then I'd suggest stopping and restarting Postfix. if i try from the mail server i get telnet mail.simail.it 25 Trying 217.27.113.30... telnet: Unable to connect to remote host: Connection timed out while if I try from my computer telnet mail.simail.it 25 Trying 217.27.113.30... Connected to mail.simail.it. Escape character is '^]'. 220 mail.simail.it ESMTP ready. quit 221 mail.simail.it closing connection Connection closed by foreign host. -- blackout69

4 years, 9 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > As far as I know, none of this has ever been migrated to Mailman 3. It has been migrated to Mailman 3, there were at least two related GSoC projects, and the repo was on GitHub, but it's not at the same URL now. Not sure if they've stopped using it, I haven't mentored there for four or five years. Let me look around. Steve

4 years, 9 months

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

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210623 15:34]: > We would need to see the email itself in order to begin to > understand if this is a Mailman issue or some issue withe the mail > as received by Mailman. > > Assuming the prototype archiver is enabled, you should be able to > find the messages in Mailman's var/archives/prototype/LIST/new/ > directory. 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? Andi

4 years, 8 months

[MM3-users] Re: Is it possible to grant all users the ability to Create List

by Stephen J. Turnbull

Mark Sapiro writes: > It would be simple enough to create a new @staff_required decorator > which would require staff or superuser status and replace the > @superuser_required decorator on the list_new() function with > @staff_required. Then any user with `staff` status could create lists. This simple scheme would allow them to create lists on any domain, right? Probably would not want to enable it on multi-domain sites. Steve

4 years, 8 months

[MM3-users] Re: Postorius no connection to REST API

by Guillermo Hernandez (Oldno7)

On 10/8/21 4:24, Mark Sapiro wrote: > It appears from the rest of your post(s) that you are actually using > mod_wsgi and (hopefully) not running uwsgi at all. You're completely right, as always. My apologies for the noise --

4 years, 7 months

[MM3-users] Re: Installation -- error on mailman-web migrate

by Mark Dale

> On 9/16/21 8:11 PM, Mark Sapiro wrote: > Actually, upon reflection, the paths in the doc will work as var_dir only affects Mailman core and the settings.py file is for Django. What's missing is that you would need to create the directories `/opt/mailman/web/` and `/opt/mailman/web/logs` manually. > > Thanks. And done. root@mx:/opt/mailman# mkdir web root@mx:/opt/mailman# mkdir web/logs root@mx:/opt/mailman# chown -R mailman:mailman web

4 years, 6 months

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

by Guillermo Hernandez (Oldno7)

On 18/9/21 20:27, Mark Sapiro wrote: > from mailman.interfaces.action import Action > def moderar(mlist, member): > memb = mlist.members.get_member(member) > if not memb: > print('{} is not a list member.'.format(member)) > return > memb.moderation_action = Action.hold > print('{} moderation_action set to hold.'.format(member)) That completely did it. The problem about finding the module was completely gone when I made a soft link in the same directory where mailman command is (in /usr/local/bin, for your info). Thank you very, very much.

4 years, 6 months

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

by Guillermo Hernandez (Oldno7)

On 18/9/21 22:59, Mark Sapiro wrote: > On 9/18/21 11:56 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Just a one more silly question: >> >> Where do I can find the diferent values that memb.moderation_action >> can take? (I want to prepare the "unhold" script too) > > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/act… > Thanks: It's perfect

4 years, 6 months

Search results for query "sapiro"