Search results for "2021" - Mailman-users

Re: Question about message bounce stats

by Brett Delmage

On Mon, 30 Aug 2021, Ruth Ivimey-Cook wrote: > When I used Mailgun some time back, it had a feature of, for any specific > outgoing mailing, being able to show you stats and other details of which > mails were received ok, which bounced, and which were undeliverable, which I > found helpful to check every so often. Their system also kept track of > long-term trends, eg for addresses that frequently failed. Was mailgun forwarding messages with user-specific trackers embedded in them, or just reporting stats based on mail envelopes? If you are referring to a 'list manager' that is used for one-way communication and specifically tracks individual users, possibly by using a tracking image in the content, you may want to look at phpList.org, which does generates various statisics. phpList is not suitable for a discussion list or many-to-many communications. Brett

3 years, 10 months

Re: Internal Server Error: /hyperkitty/list/my@lists.domain.eu/pop-threads

by Mark Sapiro

On 2/22/21 8:26 AM, Marco Marinello wrote: > Dear Mark, > > thank you for your answer. > I can confirm my Hyperkitty works just fine for archiving messages. I can even confirm Hyperkitty can reach Mailman REST API. > I haven't touched the LOGGING configuration but here you go (can even confirm hyperkitty.log is filled correctly with logs): What I was trying to say is this KeyError at /hyperkitty/list/my(a)lists.domain.eu/pop-threads 'file' exception often occurs in messages sent by Django to site admins and is never actually relates to the real problem and should just be ignored. > In mailman.log, instead, it seems like there's some issue with PostgreSQL > > [2021-02-21 18:57:19 +0000] [11685] [ERROR] Error handling request /3.1/users/user(a)example.com > Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/opt/mailman/venv/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 211, in on_get > okay(response, self._resource_as_json(self._user)) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/helpers.py", line 124, in _resource_as_json > resource = self._resource_as_dict(resource) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 130, in _resource_as_dict > user_id = self.api.from_uuid(user.user_id) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/api.py", line 78, in from_uuid > return uuid.hex > AttributeError: 'NoneType' object has no attribute 'hex' > [21/Feb/2021:18:57:19 +0000] "GET /3.1/users/user(a)example.com HTTP/1.1" 500 0 "-" "-" I think this is the real issue. HyperKitty is trying to get the user information from core for user(a)example.com and this is throwing the AttributeError resulting in the 500. This is most likely some kind of database issue. at this point > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 211, in on_get > okay(response, self._resource_as_json(self._user)) self._user is not None, but at this point > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 130, in _resource_as_dict > user_id = self.api.from_uuid(user.user_id) user.user_id is None. If I were you, I would look at the database. First, I would find the entry in the address table. I.e., select user_id from address where email = 'user(a)example.com'; then the uid select uid from uid where id = <the user_id from above> I suspect there is no uid entry for this id. You might get more information from $ /opt/mailman/mm/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. >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') which I suspect will also throw an exception, but if not >>> usr.id should return the id found by select user_id from address where email = 'user(a)example.com'; and >>> usr.user_id should return the uiud which should not be None -- 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

Re: Rejection Reason for refusing a subscription request

by Abhilash Raj

> On Mar 27, 2021, at 6:03 PM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > 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. I thought I did, the support for specifying reason has been added in Postorius’s master branch. It will be in the next release, 1.3.5 probably. Core has had support for specifying reason when rejecting requests since 3.3.3. > > -- > Brian Carpenter > Harmonylists.com > Emwd.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/ -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: domain owner role

by Abhilash Raj

> On Sep 1, 2021, at 7:52 AM, Rainer Herbst <rainer.herbst(a)aip.de> wrote: > > Dear all, > > recently, I have added one account to a domain as domain owner. I did expect the new owner to see all lists in that domain in Postorius, but he sees no list at all. > > Is this the way it should be? How can I add administrators able to perform administrative tasks on all lists in Postorius? > Domain owner role isn’t currently very useful in Postorius, they can so far only edit the domain templates. If you want to grant the user ability to manage lists in Postorius, you’d have to grant the user superuser privileges which will allow them to manage all the domains. I was thinking there is an open issue for it, but apparently there isn’t one so I opened a new one. https://gitlab.com/mailman/postorius/-/issues/533 -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Re: Mixing Mailman 3 with AWS SES

by Danil Smirnov

Hey Brian! On Thu, Mar 25, 2021 at 10:36 PM Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > On 3/25/21 2:51 PM, Jim Popovitch via Mailman-users wrote: > > Apologies to this list and Danil who has informed me that mailman2.com > > is not theirs. This of course means that there is another stakeholder > > out there somewhere....;) > > Would be nice if Danil could let the list know and in that same > communication, he can explain why he is promoting Mailman 4 when there > is no Mailman 4. We can then move to the discussion of him charitably > giving mailman3.com to the Mailman 3 developers. How about it Danil? > This is a great question. Thank you. No, there are no plans to pass domains I own to you, or any other party (unless you offer a very good price, of course). They are in use of commercial services, which are based on the Mailman 3 open-source software and listed in the directory of Mailman hosting services <https://wiki.list.org/COM/Mailman%20hosting%20services> (just as your company). *Mailman3.com* is Mailman 3 commercial hosting service (that, I think, is perfectly reflected in the domain name). It uses a shared hosting approach, which allows you to get a full-fledged Mailman 3 server for as little as *8.25 EUR* (monthly fee). Mailman3.com has also declared an open-source support initiative to provide a *free Mailman 3 hosting to OSS projects*. (To apply, send the OSS project URL and approximate monthly volume to hostmaster(a)mailman3.com.) *Mailman4.com* is a marketing initiative to emphasize the unique possibility to install *Mailman 3 in AWS* infrastructure with a few clicks to leverage all the features of AWS Marketplace, AWS customer protection, and pay-as-you-go billing scheme. (Being a bit provocative, the initiative was named while taking into consideration that the fourth version of Mailman does not exist yet and is hardly expected soon. After the version released, the appropriate business decision will be undertaken immediately.) With Mailman4.com you get your Mailman 3 server in the dedicated EC2 instance for the same price which you would pay if you deploy it to your own EC2. *Reliable mail relay*, which is carefully groomed to fit into email delivery best practices, is *included for free*. Mailman4.com is especially useful for *educational and evaluation purposes* as it allows to deploy a fully functional Mailman 3 server just in one minute and be charged *from 2 to 4 cents hourly* (depend on Hyperkitty presence). And then cancel it instantly when not needed anymore. For both Mailman3.com and Mailman4.com services it's possible to develop a *custom integration of Mailman Core API with third-party services* via publicly (but securely) exposed endpoints - the option which some of our customers are enjoying already. For example, one might create mailing lists and manage their subscribers list programmatically in order to sync it with some internal user directory. (Performance issues, which occured when a number of users is large, have been discovered and fixed already.) --- The existence of the services, described above, is already bringing benefits to Mailman 3 development community in several areas, i.e. additional paid promotion of the software (e.g to attract more GSoC students), extensive testing in the real world (which is particularly useful for dockerized setup), and contributions to the code. I hope this helps and best luck with *your* Mailman business. With my best regards, Danil Smirnov Mailman3.com proud owner > > -- > Brian Carpenter > Harmonylists.com > Emwd.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/ >

4 years, 3 months

Mailman 3 installation from latest Debian packages

by Matthew Blissett

Hi, I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). The dropdown controls on the UI for Postorius (e.g. "Subscription requests", "Mass operations" and the username button to log out) and the similar controls on Hyperkitty (e.g. "Threads by month") do not work. You can see the latter at http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… I found https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which is running the same version, but presumably not using these Debian packages as the Javascript is slightly different. Could this be a problem with the Debian packaging, or perhaps my configuration -- which is very close to the defaults (i.e. Mailman and Apache configuration generated by dpkg). Has anyone set up a working installation using these packages? Thanks, Matt Blissett PS, I wrote a similar message earlier in the week to a Debian list: https://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/2021-February…

4 years, 4 months

Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Mark Sapiro a écrit le 12/03/2021 à 00:59 : > On 3/11/21 3:10 PM, Gilles Filippini wrote: >> >> Looking at the offending message with 'mailman qfile', it appears it is >> a legitimate one actually, sent from an Android phone. >> >> Couldn't hyperkitty be a bit less strict? > > > Possibly. It looks like this may be > <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by > <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What > HyperKitty version is this? > <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. > > If your HyperKitty is >= 1.3.2, please file a new issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> This is Hyperkitty 1.3.4. I'll file an issue tomorrow. Thanks, _g.

4 years, 3 months

Problems with signed messages from Apple Mail

by Rainer Herbst

Dear all, after upgrading his Mac to MacOS 12.0.1 Monterey, one of our users can not send send signed messages to lists using Apple Mail v. 15.0 (3693.20.0.1.32). mailman3 denys the delivery of the mail with error message: host 172.19.0.4[172.19.0.4] said: 501 Message has defects (in reply to end of DATA command) I.e. mailman does not process the message, but rejects it already in the incoming smtp session. Is that a known issue? We use mailman3 docker installation, version info: GNU Mailman 3.3.4 (Tom Sawyer) Python 3.8.10 (default, May 6 2021, 06:30:44) 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 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years, 7 months

Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 21:32 -0800, Mark Sapiro wrote: > > > Have you added an Alias Domain for your domain? > > After doing that did you run `mailman aliases` or restart mailman to > (re)generate the files. > > postfix_domains postfix_lmtp postfix_vmap > postfix_domains.db postfix_lmtp.db postfix_vmap.db > > > -- > First, thanks for your patience. Two steps forward and one step back, here. I have the interface running and I can create a list which *does* send messages to my test recipients. To answer your question, yes, I did all that, and that generates postfix_domains and postfix_lmtp, but not postfix_vmap. Here's what I got: $more postfix_domains # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-26 22:29:27 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. libertyfp.org libertyfp.org $more postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-26 22:29:27 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @libertyfp.org domain. testlist(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-join(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-leave(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-owner(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-request(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-subscribe(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-unsubscribe(a)libertyfp.org lmtp:[mail.libertyfp.org]:8024 But no postfix_vmap. However, let me ask another question first: When running mailman3, do I need to set up a completely different virtual domain for it to run in? My "real" domain name is libertyfp.org, and I'm trying to make mailman work on that domain, e.g. "testlist(a)libertyfp.org." I'm starting to get the idea that I need to stick a completely different domain in there for the mailinglist. Which I can do -- I've got another two or three domain names to play with. Is it a problem to run the mailinglist on the same domain that the machine sits on for its regular business? A lot of the errors I'm getting seem to be from trying to do regular mail *and* the mailinglist on the same domain. Now that I've installed all this stuff a couple of times, I can easily re-install for a second virtual domain, if that's what I should be doing. But, on to what's not working now... Unfortunately, I seem to have completely screwed the pooch on getting postfix/dovecot to play nicely with respect to *receiving* mail. First, adding "virtual_alias_domains" (and putting libertyfp.org in it) and commenting out "virtual_mailbox_domains" resulted in postfix ignoring all my virtual mailboxes. Mail still worked, but mail is now being sent to /home/<user>/Maildir instead of /home/vmail/libertyfp/<user>/Maildir -- which means that dovecot, which looks in the virtual mailboxes, is now unaware of new mail. I suppose I could link /home/<user>/Maildir to /home/vmail/libertyfp.org/<user>/Maildir, but I suspect there will be problems and it's not a real fix. But.. .a problem for another day. Except... the same thing is happening with the mailinglist. In mailman3: I set up a test list (testlist(a)libertyfp.org) and added two test users (one local and one on a different domain). They added just fine, and both received the welcome message. However, when I replied, both messages bounced with the error that "testlist(a)libertyfp.org" was "user unknown in virtual alias table." No problem, I thought. So I added: testlist(a)libertyfp.org testlist to /etc/postfix/virtual, and testlist libertyfp.org/testlist/Maildir to /etc/postfix/virtual-mailbox, and I added testlist as a user: $ adduser -m testlist So, now mail from my list members goes to /home/testlist/Maildir, but not to the mailinglist. I also have managed to get another *different* warning, and the "there ain't no vmap, newbie" error as well: Dec 26 17:33:11 libertyfp systemd[1]: certbot.service: Consumed 1.041s CPU time. Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: error: unsupported dictionary type: #hash Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: connect from billoblog.com[162.144.108.19] Dec 26 17:33:16 libertyfp postfix/trivial-rewrite[46479]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and relay_domains Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap lookup error for "fplist(a)libertyfp.org" Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: NOQUEUE: reject: RCPT from billoblog.com[162.144.108.19]: 451 4.3.0 <fplist(a)libertyfp.org>: Temporary lookup failure; from=<billo(a)billoblog.com> to=<fplist(a)libertyfp.org> proto=ESMTP helo=<billoblog.com> That "you can't have both virtual_alias_domains" and "relay_domains" seems like it should be a clue. But I don't' know what for. Adding virtual_alias_domains really changed things... Anyway, here's the part of the /etc/postfix/main.cf that I think is likely important. Note that I comments out "virtual_mailbox_domains". myorigin = localhost mydestination = localhost, localhost.$mydomain alias_maps = /etc/aliases (which, by the way, just contains "postmaster: root") home_mailbox= Maildir # add to the end (add ssl support) smtpd_use_tls = yes smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_cert_file = /etc/letsencrypt/live/libertyfp.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/libertyfp.org/privkey.pem smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache # add to the end (add virtual users) # if specify multiple domains, specify comma or space separated #virtual_mailbox_domains = libertyfp.org virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 # mailman3 changes owner_request_special = no always_add_missing_headers = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 virtual_alias_domains = hash:/etc/postfix/domains virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap #hash:/etc/postfix/virtual Here's the postfix maps: /etc/postfix/domains: libertyfp.org # /etc/postfix/virtual: fp145(a)libertyfp.org fp145 mailman(a)libertyfp.org mailman testlist(a)libertyfp.org testlist /etc/postfix/virtual-mailbox: mailman libertyfp.org/mailadmin/Maildir/ fp145@localhost libertyfp.org/fp145/Maildir/ testlist libertyfp.org/testlist/Maildir

3 years, 6 months

Re: Innstall and run Mailman 3 with Postfix in a Docker enviroment

by Gilles Filippini

Hi, kwp.klein(a)gmail.com a écrit le 09/02/2021 à 10:46 : > ## Install Mailman 3 > > The idea is to install Mailman 3 in ad docker container. Also I want to install > Postfix in a container. All the mail which will send and receive should handled > in a docker container. The reason is, that on the server only applications in a > docker environment working. There is no MTA installed. On the server are > Discourse as forum, wikijs, portainer, watchtower, homepage, and the NGINX Proxy > Manager installed. At next I need Mailman 3. > > I don't know how to install and run Postfix for Mailman in a docker environment. I have no experience with postfix, but a working dockerized mailman [1] + exim4 [2] configuration with no post-install in case you're interested. [1] maxking/mailman-core, maxking/mailman-web, postgres [2] pinidh/exim4 _g.

4 years, 4 months

Mailman-users search results for query "2021"