Search results for "Postorius" - Mailman-users

Re: User cannot reset password

by Mark Sapiro

On 8/11/24 11:27, Greg Newby wrote: > > 1. Will the new (Django) and imported (Postorius) usernames automatically > be matched to the same email address? > > The goal is for someone to use the web-based front end to manage their > migrated subscriptions. Yes, The user creates an account with one of their MM 2.1 email addresses and adds any other MM 2.1 addresses to that account. That account will be associated with all their list subscriptions. > 2. How can I customize the email that went to users who selected "Forgot > password?" ( > > You are receiving this email because you, or someone else, tried to access > an account with email > > > I didn't find that string in the source code. It comes from Django-allauth. See allauth/templates/account/email/unknown_account_message.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

multiple sites on a mailman3 server question

by William Oliver

So, I have successfully installed mailman3 and it's working great. However, the way it works now, if someone goes to the domain website, he or she will get the mailman page. I'd prefer that it work something like: My www.example.com goes to a home page lists.example.com goes to the mailman3 page mail.example.com goes to a roundcube page I'm using nginx, and this is the first time I've set up an nginx server (I have traditionally done apache), and I'm still figuring out the syntax. My sites-available file is below, for the domain emergenus.com. The behavior I'm getting is that if I go to mail.emergenus.com, it still redirects to mail.emergenus.com/mailman3/lists, but gives a 404 page not found. If I go to lists.emergenus.com, it redirects to lists.emergenus.com/mailman3/lists and gives the nice postorius page, and works fine. So, I'm trying to figure out how to stop that redirect. When I look at my nginx access.log file for mail.emergenus.com, I see: 174.212.104.153 - - [28/Dec/2021:21:03:21 -0500] "GET /mailman3/lists/ HTTP/1.1" 404 188 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36" Aha! says I. My ip address is 203.159.80.234, not 174.212.104.153. Thus, uwsgi (I think) is sneaking in there and taking over regardless of what I'm trying to do. Is there a way to tell mailman to only take over for lists.emergenus.com and not for www.emergenus.com or mail.emergenus.com? Here's my uwsgi.ini (without then env= PYTHONPATH change discussed in another thread: # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log Here's my /etc/nginx/sites-enabled/emergenus.com looks like: server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name emergenus.com, mail.emergenus.com, www.emergenus.com; location /{ try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.emergenus.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } listen 443 ssl ; listen [::]:443 ssl ; location /static/ { alias /opt/mailman/web/static/; } ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = mail.emergenus.com) { # return 301 https://$host$request_uri; return 301 https://mail.emergenus.com; } # managed by Certbot if ($host = www.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.emergenus.com lists.emergenus.com mail.emergenus.com emergenus.com; return 404; # managed by Certbot } Thanks billo

2 years, 10 months

Debug=False breaks Django/MM3-Login-page

by Stefan Bauer

Hi folks, I'm trying to hide the custom 404 error messages from Django. ------------------------- Page not found (404) Request Method: GET Request URL: http://......./non-existent-2008020390 Using the URLconf defined in mailman_web.urls, Django tried these URL patterns, in this order: mailman3/ archives/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] accounts/ admin/ postorius/ hyperkitty/ The current path, non-existent-2008020390, didn’t match any of these. You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. ----------------------------- Switching DEBUG=True (currently set in settings.py) to false does indeed hide additional debugging output, but following pages are not accessible anymore (Server Error). user-profile/ accounts/logout/ hyperkitty/ Switching back to DEBUG=True brings back accessibility. This is Mailman Core-Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] any help is greatly appreciated. Thank you. Stefan

1 month, 1 week

Re: Problems with New MM3 Installation

by Abhilash Raj

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

3 years, 6 months

Re: List creation error

by Odhiambo Washington

On Wed, 6 Jan 2021 at 21:17, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > Odhiambo Washington wrote: > > On Wed, 6 Jan 2021 at 15:36, Andreas Barth aba(a)ayous.org wrote: > > > > > > Odhiambo Washington (odhiambo(a)gmail.com) [210106 12:12]:PS: I could > probably have caused the error with some weird operation I > > > did: > > > Initially when postorius comes up, it has the domain - example.com > > > http://example.com. I am not sure > > > where it gets this. > > > > > > > > > example.com is the default domain from django. Renaming that via the > > > django (e.g. mailman3/admin/sites/site/1/change/ ) worked for me quite > > > well (without touching anything in the database by hand). > > > Hi Andi, > > I could be missing something still... > > > > At what juncture during the installation do you do this renaming? > > Where is this directory? On my setup, I have no such directory - but I > > could be missing something in the install process, maybe.. > > > > root@debian10:/opt/mailman# pwd > > /opt/mailmanroot@debian10:/opt/mailman# find . -type d -name sites > > > ./mm/venv/lib/python3.7/site-packages/jedi/third_party/django-stubs/django-stubs/contrib/sites > > ./mm/venv/lib/python3.7/site-packages/django/contrib/sites > > Do you find anything amiss with this HOWTO - > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ?? I > > find > > the guide rather straight and clear. > > That is my work in progress and thank you for the compliment. > > It's the one I am following - almost to the letter - except for the fact > > that I am using Apache+mod_wsgi+MySQL+Exim instead. > > I have configs in place by the time I run 'mailman info' portion. But > then > > again, when I run this command, I don't like what it prints because I see > > some reference to sqlite. > > Can you paste what the mailman info output is and the contents of your > mailman.cfg file? > My mailman.cfg file is below: [mailman] site_owner: odhiambo(a)gmail.com layout: here [paths.here] var_dir: /opt/mailman/mm/var [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:XXXXXXX@localhost /mailmansuite?charset=utf8&use_unicode=1 [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [archiver.prototype] enable: yes [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost smtp_host: localhost lmtp_port: 8024 smtp_port: 25 configuration: python:mailman.config.exim4 [shell] use_ipython: yes The output of `mailman info` is: mailman@debian10:~$ python3 -m venv /opt/mailman/mm/venv mailman@debian10:~$ source /opt/mailman/mm/venv/bin/activate (venv) mailman@debian10:~$ mailman info GNU Mailman 3.3.2 (Tom Sawyer) Python 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] config file: /opt/mailman/var/etc/mailman.cfg db url: sqlite:////opt/mailman/var/data/mailman.db *<=== I wonder why it's even referring to sqlite...* devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass > > As it is, I believe my problem lies elsewhere, not possible to solve with > > your rename option. > > To get rid of example.com, I log into Django, create a new site using the > main list domain and note the site id. I then edit the settings_local.py > file and change the SITE_ID setting to the new site id of the main list > domain. You will need to restart mailman and qcluster I believe after > making that change. > I hope you will document this additional step of how to get rid of example.com. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

3 years, 10 months

Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Held messages page not rendering the message

by peter＠chubb.wattle.id.au

>>>>> "mike-mailman" == mike-mailman <mike-mailman(a)earth.li> writes: mike-mailman> Hi When the list moderator goes to the held_messages mike-mailman> page, they correctly get a list of the held messages and mike-mailman> can accept/reject/discard them mike-mailman> However, clicking on the individual message to read it mike-mailman> doesn't work - it does nothing visible at all. From mike-mailman> debug I can see it requests mike-mailman> /mailman3/postorius/api/list/<list>/held_message/1/ mike-mailman> which returns correctly (and the body includes the mike-mailman> message as expected) - but it never renders it If you installed from the Debain/Ubuntu packages, this is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033072 The fix is to get your web server to pick the correct location for Jquery,js --- se the bug fix. To confirm, turn on the developer tools in your browser and look in the javascript console. Peter C

1 year, 8 months

Re: Installing mailman 3

by Rafael Mora

I did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > 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

7 years, 4 months

Re: Emergency moderation and clearing out a lot of held messages

by Caballero, Danny (Dan)

I don't understand. We have a single database configured for everything. I don't recall reading anything in the set-up documentation about using more than 1 database for Mailman3. Let me know if I'm missing something! -- Dan Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Friday, November 11, 2022, 7:01 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Emergency moderation and clearing out a lot of held messages I don't have a helpful suggestion yet but would like to clarify: Dan Caballero writes: > "2022-11-09T18:37:49.106105Z 19100868 [Note] Aborted connection > 19100868 to db: 'mailman3_prod' user: 'mailman' host: '10.6.5.187' > (Got an error reading communication packets)" db: mailman3_prod is the core database, not the Django (Postorius and Hyperkitty, or mailman-web), is that correct?

2 years

Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

2 years, 8 months

Mailman-users search results for query "Postorius"