Search results for "Postorius" - Mailman-users

Re: Recipient address rejected: User unknown in local recipient table

by Mohsen Masoudfar

Thanks you so much Mark, I appreciate your help! Yes, I did: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: newlistserv.aaas.org lmtp_port: 8024 smtp_host: newlistserv.aaas.org smtp_port: 25 configuration: python:mailman.config.postfix # postconf recipient_delimiter recipient_delimiter = + # postconf owner_request_special owner_request_special = no in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp transport_maps = hash:/opt/mailman/var/data/postfix_lmtp virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess. I restarted the whole stack and added a new list. In postfix logs I see: Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_vmap.db: No such file or directory I touched the /opt/mailman/var/data/postfix_vmap, but it did not help neither. In addition, I found out this : On my old mailman2 I have a setting in postfix main.cf: alias_maps = dbm:/usr/local/mailman/data/aliases the file /usr/local/mailman/data/aliases says in its first line: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE This makes a lot of sense to me. The point is I am missing any similar settings on postfix on mailman3. Maybe local_recipient_maps do that, but as I mentioned the DB file is older than the text file. The result is that the list (which is actually a postfix user) is unknown to postfix completely. Now what is missing here? It appears that postorius can talk to postfix to send welcome messages out, but Postfix is not aware about the User that Postorius has created and exists in SQLite DB. So rejects any email addressed to that one. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, April 15, 2020 10:09 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Recipient address rejected: User unknown in local recipient table [EXTERNAL EMAIL] On 4/15/20 3:47 PM, Mohsen Masoudfar wrote: > I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . > Or probably this is related to a postfix setting? Have you configured Mailman core and Postfix per <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.r…>? -- 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, 9 months

Re: Link to account

by Lars Bjørndal

Thanks a lot! After further consideration, I will stay with the defaults, e.g. have accounts, archive etc at the same level as mailman3. Lars On Wed, Apr 12, 2023 at 08:32:27AM -0700, Mark Sapiro wrote: > On 4/11/23 23:08, Lars Bjørndal wrote: > > > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. > > > Try this. > > In urls.py > ``` > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), > permanent=True), > ), > path('mailman3/archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('mailman3/accounts/', include('allauth.urls')), > path('mailman3/admin/', admin.site.urls), > path('mailman3/', include('postorius.urls')), > ] > ``` > > In apache > ``` > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3/archives" > "http://127.0.0.1:8000/mailman3/archives" > ProxyPass "/mailman3/accounts" > "http://127.0.0.1:8000/mailman3/accounts" > ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" > ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > </IfModule> > ``` > > -- > 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 lars(a)lamasti.net

2 years, 9 months

Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Mark Sapiro: > What is the complete log message from uwsgi-error.log? I'll attach a typical log file to this message. It shows startup messages followed by a recorded confirmation email. User name and domain are obfuscated, but other than that the log is unchanged. -Ralph *** Starting uWSGI 2.0.18 (64bit) on [Sat Mar 28 20:55:36 2020] *** compiled with version: 9.3.0 on 26 March 2020 13:58:28 os: Linux-5.5.13-gentoo #1 SMP Thu Mar 26 10:24:38 CET 2020 nodename: wedjat machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 8 current working directory: /var/lib/mailman detected binary path: /var/lib/mailman/venv/bin/uwsgi chdir() to /var/lib/mailman/suite/ your processes number limit is 256427 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 127.0.0.1:8002 fd 8 Python version: 3.8.2 (default, Feb 26 2020, 08:14:41) [GCC 9.2.0] Python main interpreter initialized at 0x56443febc210 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x56443febc210 pid: 21912 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 21912) spawned uWSGI worker 1 (pid: 21916, cores: 2) 19:55:38 [Q] INFO Q Cluster pizza-illinois-golf-magnesium starting. 19:55:38 [Q] INFO Process-1:1 ready for work at 21921 19:55:38 [Q] INFO Process-1:2 ready for work at 21922 19:55:38 [Q] INFO Process-1:3 ready for work at 21923 19:55:38 [Q] INFO Process-1:4 ready for work at 21924 19:55:38 [Q] INFO Process-1:5 ready for work at 21925 19:55:38 [Q] INFO Process-1:6 ready for work at 21926 19:55:38 [Q] INFO Process-1:7 ready for work at 21927 19:55:38 [Q] INFO Process-1:8 ready for work at 21928 19:55:38 [Q] INFO Process-1:9 monitoring at 21929 19:55:38 [Q] INFO Process-1 guarding cluster pizza-illinois-golf-magnesium 19:55:38 [Q] INFO Process-1:10 pushing tasks at 21930 19:55:38 [Q] INFO Q Cluster pizza-illinois-golf-magnesium running. Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [lists.domain.tld] Please Confirm Your E-mail Address From: postmaster(a)domain.tld To: OBFUSCATED(a)gmail.com Date: Sat, 28 Mar 2020 20:08:15 -0000 Message-ID: <158542609570.21916.15168402908994348907(a)wedjat.domain.tld> Hello from lists.domain.tld! You're receiving this e-mail because user OBFUSCATED has given yours as an e-mail address to connect their account. To confirm this is correct, go to https://lists.domain.tld/accounts/confirm-email/Mg:1jIHkd:x8NSjzCkP5ifX6V39… Thank you from lists.domain.tld! lists.domain.tld -------------------------------------------------------------------------------

5 years, 9 months

Can't Start Mailman3 Core on Fresh Install

by Stephen J. Turnbull

Mail Person writes: > Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using > MySQL as the backend. After installing using the mailman3-full > package and configuring it, I'm getting the following error when > trying to start the mailman3 service: > Jul 21 04:28:44 eps mailman3[81963]: > sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) > (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using > password: YES)") I would guess that the password doesn't match. This can happen because some configuration is done with Python modules (.py files, the configuration is Python code) where strings are *delimited* by quote marks (which are not part of the value) and some (.cfg files) are .ini-style, where all values are read as strings, and so quote marks become part of the value. The web database (mostly user information) and the mailing list database are separate (because not all Mailman installations use Postorius and HyperKitty). Are you sure you have the right user and password for the mailing list database configured in mailman.cfg? Other reasons would be in this reference: > Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: > http://sqlalche.me/e/e3q8) > I'm not sure why the access issue is happening. Mailman3-web is > running fine and I can see the site at mailman3/postorius/lists > (but it says Page Not Found). "Page not found" is probably a consequence of the same access error. You can probably see it in the database logs.

3 years, 6 months

Re: Response for Admins only

by Stephen J Turnbull

2023-05-08 14:18 に Michael Schaarschmidt さんは書きました: > I’m an administrator of a MM3 with a lot of lists, which are generated and maintained through > the rest api. For testing reasons I am looking for a way to send a test mail with a ping to a list > in MM3 from a mail address of an administrator to get a pong from the MM3 - or even better >- get a response with the status of the list like number of recipients, number of mails waiting > for moderation, etc. > Does exist a solution for such a purpose? No. Parsing email robustly is really hard, and for many installations there would be the problem of dealing with authentication. That's why we created the REST API for administration. We will not be creating admin-oriented email interfaces, although we will continue to maintain the user-oriented subscribe/unsubscribe/owner/request mailboxes, as well as the bounces mailbox for internal use. Any information about Mailman configuration, membership, or status that is available through the web interface (Postorius) is available through the REST API. The only exceptions are related to web authentication, for which Postorius (and HyperKitty) maintain a small auxiliary database of users. Unfortunately there isn't an enumeration of endpoints available from the REST API itself, so you'll have to look at the code in mailman/src/mailman/rest to find the endpoints you want. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

2 years, 8 months

Re: [Mailman-Users] Mailman 3 Ready?

by Stephen J. Turnbull

Allan Hansen writes: > What is the best, easiest, guaranteed-to-work way to get this > Mailman 3 up and running (OS, add-ons, options, etc.). When I tried > myself, I saw a lot of options that I really did not really care to > have because I did not know the consequences of each. I’m an > application programmer, not a systems programmer. It's email, there are no guarantees. I hate to say that, but that's the way it is. In particular, I'm concerned about the "iRedMail" integration, which may be a complete wildcard from my point of view. With respect to the relevant iRedMail components, I can say that Mailman 3 is perfectly happy with Postfix as MTA (it's the recommended configuration, although I use Exim4 for historical reasons), and I've been satisfied with a small-scale set of lists (about 10 active ones, with at most 20 subscribers total) using Apache+mod_swgi to host Postorius and HyperKitty. The problem would be if your friend (is that the Frank in the CC? hi, Frank!) really really wants to manage Mailman 3 through iRedAdmin -- that will get messy I suspect, and pragmatically speaking, we can't support it, we don't have the cycles. So he'd be on his own, especially since the iRedMail folks have their own bespoke mailing list manager. I would recommend avoiding iRedAdmin integration, and just using Postorius since the subscribers and non-site-admin moderators (if any) will need to use Postorius anyway. Ignoring the iRedAdmin issue, the absolute simplest is 1. Install any Linux distribution with a Docker package. 2. Install the distribution's Docker package. 3. Download and install Mailman Project's Mailman 3 container. 4. Upgrade the container manually (ie, download and reinstall) as appropriate. For reference, what I would recommend to my friends, who would give me hands-on access in emergencies: 1. Install the Debian distribution. (What I use.) 2. Pin the Mailman 3 packages to "experimental". The idea would be to get Mailman 3 upgrades as fast as possible, even at the risk of packaging issues. (My experience with default-to-experimental system for several years was that this happened at most once a year, and the three or four cases all got fixed within days.) 3. Install the Mailman 3 packages. 4. Adjust any dependencies that need non-"stable" versions. 5. Upgrade via apt or whatever occasionally. 6. When Mailman 3 is working well, downgrade the pins to a more stable level. Since you do have such a friend, there's probably a similar process that works for his distribution-of-choice. > The problem is that my MacOS users are getting tripped up by the > mangling, as it is hidden by the mail clients. I have instructed > them to remove previous recipients regularly from the list of such, > if they contain the ‘via list’ string. But they don’t read my > emails, and we see many embarrassing email ssent to the lists that > are meant for one-on-one communication. I guess we could provide a setting where reply-to goes *only* to author, instead of to author *and* list as we currently recommend. But that is going to make you (or list owners) the focus of user ire because their intended replies to list go only to author. What do you think? tl;dr The rest is me blowing off steam. :-) > The fact that the mangling will continue is a disappointment. It's a disappointment to the sane people at the IETF, too, including the rep from Yahoo!, who's a very smart lady (I may be biased, she gave me a kitten once. ;-) Yahoo! is violating the original concept (DMARC "p=reject" was supposed to be used *only* for "transactional" mail, i.e., direct private communication between a business and its clients), but I see her point: when you've had a hundred million or so address books hacked and sold to spammers, and the spammers are sending literally millions of "recommendation from a friend" spams per hour for days on end, you use the tools to hand. > I’m inclined to tell all my AOL and Yahoo users and others in the same > boat to find another email service. I know the feeling. I'm lucky in that respect: the Ministry of Education prohibits use of yahoo mailboxes at Japanese universities. (Which is a WTF of a different kind: yahoo.co.jp is a franchise, not controlled by yahoo.com, and doesn't use p=reject at least at the time MoE issued that policy.) Mail is just hard. It was designed for a "friendly network of users", not for today's rather hostile open Internet, and even if they had envisioned this in the 70s when the message format and SMTP mail transmission protocol were designed, the fundamental problem is that pretty much everyone has a genuine need, even if only occasional, to receive messages from untrusted and even unknown senders.

6 years, 1 month

Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

On 6/25/22 13:22, denis.bitouze(a)univ-littoral.fr wrote: > Mark Sapiro wrote: > >> They seem so to me, but in any case, if you look at Postorius -> >> Settings -> Message Acceptance -> Default action to take when a >> (non-)member posts to the list, they are described there in much more >> detail. > > OK: not easy to figure out. A tooltip on the corresponding buttons would > be helpful. Agreed. See https://gitlab.com/mailman/postorius/-/issues/551 >>> BTW, no clue about an automatic banishment of emails from discarded >>> messages? >> >> In the pop-up dialog from clicking the subject of a held post you can >> set the sender's moderation status when discarding the post. > > Sorry but I can only see: > > - “--- Set member moderation ---” (non selectable, I guess) > - “Hold for moderation” > - “Reject (with notification)” > - “Discard (no notification)” > - “Accept immediately (bypass other rules)” > - “Default processing” > > and cannot see how I can at the same time “Discard (no notification)” > and “Banish the email of the post's sender”. If you select “Discard (no notification)” from that dropdown and then click Discard, the current message will be discarded and future messages from that sender will be automatically discarded. Is that not what you want? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: Welcome message issue

by Mark Sapiro

On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Eggert Ehmke

This makes it even stranger. Removing the trailing / did not help in my case, but replacing the mailman3 for mailman in the ProxyPass line did. Would be really nice to solve this problem at the root. Am Montag, 25. Oktober 2021, 18:09:21 CEST schrieb Mark Sapiro: > On 10/25/21 1:45 AM, Stefan Bauer wrote: > > Dear Users, > > > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > > web-interface via > > > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > > > I receive > > > > Not Found: /mailman//postorius/lists/ > > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated > > 2821 > > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on > > core > > 1) > > > > Where does the wrong path come from (mailman vs. mailman3) > > See the thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U > SXUYZYB5KIXT37APMCOAUZLKBRPARTL/ > > ... > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > Others have found that removing the trailing slash from > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > to make it > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > > fixes the issue.

4 years, 2 months

User account issue after importing data from Mailman 2.x server

by dgoldsmith＠sans.org

We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. I just started looking at a user and a list in both the Postorius and Django admin web UIs and found: - in Postorius: - list exists, has 20K plus subscribed members and has 3 list owners - user exists and is subscribed to this list - in Django: - in HyperKitty section - in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators) - in the Emails page, there are 149K plus entries - in the Profiles page, there are 147 entries - in the Accounts->Email addresses page, there are only 155 entries - in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Thanks, David Goldsmith

1 year, 3 months

Mailman-users search results for query "Postorius"