Search results for "Postorius" - Mailman-users

Re: Spam from non list members

by Sam Darwin

You configured postfix/exim directly to do rspamd filtering, or you configured mailman to do it? If the latter case (mailman), is it possible that affects acceptance logic? What if you remove rspamd and spam detection from the pipeline? [ that is mere speculation though ] Have you installed the latest versions of mm3, postorius, hyperkitty?

2 months, 2 weeks

Question: as Admin, I disabled the self-registration via settings.py. What is the correct method to register a few new users now?

by Wikinaut

Disabled by line ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' (via https://gitlab.com/mailman/django-mailman3/-/merge_requests/129 ) When I want to register a few new users, I need to comment this line and restart mailmanweb. Question: is there a better method for admins to register a few new persons to Hyperkitty/Postorius so that they can act as owners and moderators of some of the lists?

2 months

Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Wikinaut

Do you have a programmatic way to delete n ( n > 20) such entries in Postorius, e.g. via a python script + REST to loop through all lists and perhaps to exclude a few based on a small condition (like a text found in old template and/or list name)? This would be very helpful.

1 month, 2 weeks

Re: Some doc updates from Fedora install experience

by tlhackque

On 26-Jun-17 15:31, Abhilash Raj wrote: > Excerpts from tlhackque--- via Mailman-users's message of June 24, > 2017 4:21 am: >> I had to read code to discover that the web UI (Postorious) server >> address doesn't exist in any config file. > > That is True, there is no stright forward way for Mailman Core to know > who is > using the API and where is the Web UI working. I *think* "Web Host" is > used to > generate emails, but that can't always be completely accurate because > there is > no easy way to know what is the "root" url for Postorius and > Hyperkitty. Generally, the default configurations place it at > "/postorius/" and > "/hyperkitty/", but there are installations where it is placed at > "/mailman3/" > and "/archives/". > It would be helpful for API users to "register" with Mailman, so that API clients can figure out how to direct users to their web pages. There has to be a directory somewhere, and Mailman is the central character. It doesn't have to be one place. Perhaps something like "get( '/lists/config/admin_ui') and get('/lists/config/subscriber_ui") - which could return something like: [ {"type":"gui", "name":"postorius", "uri":"https://www.example.net/mailman3/"}, {"type":"cli","name":"mailmanclient","uri":"domain://my.socket.example.net:1234"},{"type":"gui","name":"mailmanx","uri":"file:///usr/sbin/mailman-Tk"}, ...] (Where the order indicates preference). Speaking of which, without this knowledge, how can Mailman provide the personalized "to unsubscribe, visit your account at "...." customizations"? I see that there are URLs for headers/footers, but we seem to have lost the ability to insert the URL for the GUI managing your list/account into personalized e-mails... >> >> To bind it to something other than localhost, you put the desired ip >> address & port on the >> >> `python manage.py runserver` command line (in mailman-suite_project. > > Ok, so you should never use this in production. AGREEED > This command starts a > "development" server which is only supposed to be used in the development > environment. My development environment is a VM for Mailman, and other VMs for the mail server. And if I try to run a web browser on the Mailman VM, it takes over the machine and even so is unresponsive. So I needed to make the UI visible on the network where my PC is. I do understand the issues, and there are firewalls protecting the environment. > For any production use, in general for any python web app, we use a > wsgi server which interfaces between Django and a "real" web server > like Nginx > or Apache. I would recommend using uwsgi. This[1] and [2] might be of > help. > AGREE. I know that I will have to do this eventually. But my immediate goal is to see if it's possible to get my application talking to Mailman V3 - it's a 1-user environment. So I needed an evaluation environment with the absolute minimum setup costs. If things work out, I'll do the right thing. If not, I can't afford to have spent a week or so untangling nested webservers talking to each-other with frameworks, a half-dozen passwords and config files. This was the quickest path I could find to an 'almost out-of-the-box' evaluation and prototyping environment...and pretty much the only "step-by-step" instructions that I could find. I'd have tried "step-by-step" for production if (a) I could find it and (b) I could configure it with less than a couple of days of study :-( I decided to document this in case it helps someone else. I strongly agree that it's not production, and not for all users. > There is some configuration over here[3] that might help you get it > running. You > would have to change some parameters in the configuration though. > >> >> It must be an IP address - it doesn't resolve DNS names. The port is >> appended to the IP address with a ':'. >> >> So, in venv 2.7 >> `cd mailman-suite_project && python manage.py runserver >> 10.0.0.11:8000` will work. >> >> There are all sorts of issues if your network is at all public, but >> in my >> case, a multi-machine walled garden, with no local web browser, it >> allowed >> bootstrapping to continue. > > It is not supposed to be public and should only be used for development. > Agree, agree, agree. >> >> The runserver command also takes --ipv6 (or -6) to bind to an IPv6 >> address, >> --nothreading and --noreload also exist (but i haven't tracked down >> whethere >> they're useful') > > There are a whole lot of other optins available to `python manage.py` > command > which you can find in the documentation for Django. Truth be told, I had no idea that 'runserver" had anything to do with Django. I was just following instructions to get something out of the box and onto the wire. FWIW, 'python manage.py --help' and 'python manage.py help runserver' are semi-intructive. I still have no clue what an "auto-reloader" is, but the help does say that --noreload won't use it :-) It's clear that a lot of work has gone into this release -- but it's also quite frustrating for people who just want to explore using it to get through the setup effort. I've made some progress. > -- > thanks, > Abhilash Raj

8 years, 4 months

Re: Confusing mailman user model

by Gilles Filippini

Gilles Filippini a écrit le 19/07/2020 à 19:10 : > Gilles Filippini a écrit le 19/07/2020 à 18:00 : >> Mark Sapiro a écrit le 19/07/2020 à 17:30 : >>> On 7/19/20 8:10 AM, Gilles Filippini wrote: >>>> Hi, >>>> >>>> I'm trying to understand the Mailman user model, and I'm confused about >>>> the respective roles of tables 'auth_user' and 'user'. >>> >>> >>> auth_user is a Django auth table. These are the users listed in the >>> Django admin web UI. >>> >>> user is Mailman core's users. >>> >>> >>>> Both have an 'id' column referred to as 'user_id' when used as a foreign >>>> key. But there seems to be no relation at all between them as they use >>>> different ids for the same user. >>> >>> >>> Right, they are unrelated. >>> >>> >>>> Our mailman server was migrated from mailman2 to mailman3 about 1.5 year >>>> ago, and there is an inconsistency I'd like to fix: >>>> 2 of our users have a registered Mailman account with their respective >>>> email addresses in table 'auth_user', but these very same addresses in >>>> the 'address' table are linked to another old admin account in the >>>> 'user' table. >>> >>> Their Mailman account is the 'old' one. the auth_user account is a >>> Django account >>>> >>>> Then if add one of these addresses as a domain owner, it it the old >>>> admin address which is selected instead. How could I fix that? >>> >>> >>> That's because domain owner in a Mailman thing and involvs the Mailman >>> user. You could delete the Django users via the Django admin UI and then >>> re-register them via Postorius. That *might* work. >> >> When login into postorius, it is the Django account that is used, right? >> Then how is the mailman account retrieved from there? It seems UUIDs are >> used in the process, but I fail understanding how, so far. Wouldn't it >> be safe to retrieve the new Mailman account associated to these Django >> users, and link there emails from 'address' table' to them? > > Reading the mailman-web source code I understand now that the mailman > account is retrieved from the Django account email address. Then both > users are tied to the same old mailman admin account, and deleting then > registering them again won't change anything on this aspect. > > Would this work? > 1- For both addresses, update their record in table 'address' to set > 'user_id' to null > 2- On their next login to Mailman-web, a new mailman account would be > created and associated with their own email address. Done that, and it worked. Thanks, _g.

5 years, 3 months

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

by denis.bitouze＠univ-littoral.fr

Hi, at a page of the form .../postorius/lists/mylist/held_messages, it is possible to: - Accept - Reject - Ignore messages to be moderated. I didn't find any documentation about the difference between (the purpose of) “Reject” and “Ignore”. Since the list I'm currently moderating suffers from a lot of spammers, I wonder if there is a way to at the same time: - remove the spam from the moderation list (“Reject”? “Ignore”?), - add the emails from the removed spams to the list of banished emails (since copying-pasting each mail to be banished is a pain). Thanks in advance!

3 years, 4 months

Django: An error occurred while processing your request.

by Florian Sukup

Hi, I running Debian bookworm and have installed mailman3-full (+ postfix). I am new to mailman3 (using mailman2 now) and about exploring how to migrate. I had 3 sites or domains: example.com and two real ones. When I received emails from postorius, then it came from example.com which is nonsense as I worked with the real lists. So I deleted example.com. When I call https://.../mailman3/admin or any of the lists, the result is: Server error An error occurred while processing your request. How can I get out of it? This is only a test environment, so no heart attack. Thank you for any help. Florian.

5 months, 1 week

Re: templates

by Christian

Okay I sent a test message this morning and subscribers are reporting they did not receive it. The smtp.log shows 'smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds' (see below) I alone received it however and it is listed in the archive. Below is the excerpt from smtp.log. Two of my 5 lists are exhibiting this behavior, while 2 other lists are working normally. Please advise. Thank you. root@zarathustra:/opt/mailman/mm/var/logs# vi smtp.log May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) recip: degrowcali-bounces+vortexanthony=hotmail.com(a)lists.ccalternatives.org May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'DATA' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'QUIT' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) connection lost May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) Connection lost during _handle_client() May 05 08:11:35 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:11:35 2023 (768) Peer: ('127.0.0.1', 60312) May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) handling connection May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'MAIL FROM:<> SIZE=9885 BODY=8BITMIME' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) sender: <> May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'RCPT TO:<degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org>' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) recip: degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'DATA' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'QUIT' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) connection lost May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) Connection lost during _handle_client() May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> post to degrowcali(a)lists.ccalternatives.org from christian(a)degrowthcalifornia.org, 5012 bytes May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.011698722839355469 seconds May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org, 11445 bytes May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.00799560546875 seconds May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+62749dfe16f9d39e2cd0c3e94754723efbe8169d(a)lists.ccalternat ives.org, 11400 bytes May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.008965730667114258 seconds May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org, 11426 bytes May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39046) May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'MAIL FROM:<> SIZE=15076 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'RCPT TO:<degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) recip: degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) connection lost May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) Connection lost during _handle_client() May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39050) May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'MAIL FROM:<> SIZE=15049 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'RCPT TO:<degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) recip: degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) connection lost -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 12:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 11:15, Christian via Mailman-users 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 > mailto:var/templates/lists/redlatinleg@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. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U HWOG6S57FM2SIQWHEPWM3CDUSAMLOOP/ (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ NZ7G3JMYXFTQNVJ2DYGJ6PETEQT55SKB/ Without further information, I can't say more than that. -- Mark Sapiro <mailto:mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailto:mailman-users@mailman3.org To unsubscribe send an email to mailto:mailman-users-leave@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/ GJNYZK3DK4UZYAILV7JZ62PPVPDPKNOZ/ This message sent to mailto:csa@web-analysts.net

2 years, 5 months

Changing Mailman's "from" domain - redux

by roger＠reasonal.com

(this is a posting directly into this web ui as mails to this list just vanish without a trace) -- Anyone? Anyone? With reference to the original mail here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… It seems that the "From" domain field is set by Postorius, but I can't find anything in its documentation on how to change it. I've done obvious things like change the boxes hostname to what I want, have fiddled around in the various Postfix settings for mydomain, etc etc. But all admin messages, listserver replies etc come from the partial domain "blah.blah", not "listman.blah.blah". Any ideas welcome.

6 years, 5 months

MM3 gateway errors and frequent reboot needs

by hansen＠rc.org

We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? Please advise. PS: My old MM2 installation could (and did) run without any help. Not so with MM3.

5 years, 6 months

Mailman-users search results for query "Postorius"