Search results for "2021" - Mailman-users

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 ^[^#] :-)

4 years, 5 months

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

by Stefan Bauer

So i fixed it by myself, just think about it again. ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ Note the trailing slash at the end. After removing it, the webinterface is up again. But i have no idea, why this is NOW a problem and was not in the past. Maybe something has changed in the way, apache is handling this now. Anyway, problem solved for me. Am Mo., 25. Okt. 2021 um 10:45 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com >: > 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) > > After enabling Debug, i see in the browser the following: > > > Page not found (404) > Request Method: GET > Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ > > Using the URLconf defined in urls, Django tried these URL patterns, in > this order: > > ^$ > ^postorius/ > ^hyperkitty/ > ^user-profile/delete$ [name='mm_user_account_delete'] > ^user-profile/$ [name='mm_user_profile'] > ^accounts/ > ^admin/ > > The current path, /postorius/lists/, 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. > > My apache configuration is very simply: > > # more /etc/apache2/conf-enabled/mailman3.conf > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > I dont see where the path gets traversed in the wrong way. Any help is > greatly appreciated. > > thank you. > > Stefan >

3 years, 8 months

Re: at the finish line of mailman3 docker, but can't sign in.

by John Covici

I am finding some missing documentation in the section on configuring mailman-web, it refers to a file https://asynchronous.in/docker-mailman/web/ which does not exist. On Sat, 31 Jul 2021 21:21:24 -0400, John Covici wrote: > > OK, thanks a lot -- if anyone here can help with proper config for > those, that would be great. I do have a web server, but its apache > rather than mginx and I am not sure how to properly translate. Also, > doing a separate container for an mta which would just talk to > mailman would get around the sendmail situation I have, although > there may be a decent way to do that as well. I guess the hard part > is to tie the multiple containers together. > > > On Sat, 31 Jul 2021 17:56:15 -0400, > Abhilash Raj wrote: > > > > > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > > I have a couple of questions about the container, if its OK. > > > > Sure it is :) > > > > > > > > First, it says to run you create the directory > > > /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the > > > git clone. What directory should the git clone be in? > > > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > > > A couple of more questions -- is there a way to install the web server > > > and the mta in the container, this way I could make the whole thing > > > be independent of my host configs? > > > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > > > > On Fri, 30 Jul 2021 16:04:48 -0400, > > > bob B wrote: > > > > > > > > is this the info you need for the container version > > > > > > > > [root@..... docker-mailman]# docker ps > > > > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > > > > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > > > > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > > > > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > > > > > > > > > > for smtp host > > > > ------------ > > > > cat /opt/mailman/web/settings_local.py > > > > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > > ALLOWED_HOSTS = ['*'] > > > > DEBUG = True > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > > > EMAIL_HOST = 'smtp.example.com' > > > > EMAIL_PORT = 25 > > > > --------------------------- > > > > cat /opt/mailman/core/mailman-extra.cfg > > > > # mailman-extra.cfg > > > > > > > > [mta] > > > > incoming: mailman.mta.postfix.LMTP > > > > outgoing: mailman.mta.deliver.deliver > > > > # mailman-core hostname or IP from the Postfix server > > > > lmtp_host: localhost > > > > lmtp_port: 8024 > > > > # Postfix server's hostname or IP from mailman-core > > > > smtp_host: smtp.example.com > > > > smtp_port: 25 > > > > configuration: /etc/postfix-mailman.cfg > > > > [mailman] > > > > # This address is the "site owner" address. Certain messages which must be > > > > # delivered to a human, but which can't be delivered to a list owner (e.g. a > > > > # bounce from a list owner), will be sent to this address. It should point to > > > > # a human. > > > > site_owner: my_real_email_is_in_the_file.com > > > > __________________________________ > > > > > > > > My docker most machine /etc/postfix/main.cf has > > > > > > > > transport_maps = > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > local_recipient_maps = > > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > > relay_domains = > > > > regexp:/opt/mailman/core/var/data/postfix_domains > > > > > > > > > > > > # Support the default VERP delimiter. > > > > recipient_delimiter = + > > > > unknown_local_recipient_reject_code = 550 > > > > owner_request_special = no > > > > > > > > ------------------------------ > > > > > > > > > > > > > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > > > > > > > > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > > > > _______________________________________________ > > > > 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/ > > > > > > > > > > -- > > > Your life is like a penny. You're going to lose it. The question is: > > > How do > > > you spend it? > > > > > > John Covici wb2una > > > covici(a)ccs.covici.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) > > > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.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/ -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

3 years, 11 months

Re: Mailing list welcome message won't update

by Stephen J. Turnbull

via Mailman-users writes: > Now I have: > > -rwxr--r-- 1 list list 0 Oct 10 2018 list:member:generic:footer.txt* > -rwxr--r-- 1 list list 0 Mar 30 2021 list:member:regular:footer* > -rwxr--r-- 1 list list 507 Jan 9 01:35 list:user:notice:welcome* > -rwxr--r-- 1 list list 506 Jan 15 04:45 list:user:notice:welcome.txt* LGTM, not sure why the issue persists. Have you checked that group and world have 'x' (directory search) permissions on every directory in the path to these files? (This is unlikely to be the problem but it's easy to check.) And it shouldn't matter but those files themselves don't need 'x' (execute) permission. Pretty sure the existence of the .bk file has nothing to do with this problem. Evidently you don't need it this time, but in the future you needn't hesitate to keep backups around if they would be useful. Steve

5 months, 3 weeks

Cannot request password reset: "The e-mail address is not assigned to any user account"

by dave＠aasv.org

I have set up Mailman Core Version GNU Mailman 3.3.5 with Mailman Core API Version 3.1 (Python 3.8.10) using the version 0.40 Docker images. I was able to get things set up and tested by requesting a password reset for the MAILMAN_ADMIN_USER specified in the docker.yaml. Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). Using the MAILMAN_ADMIN_USER I can sign in, view the list of all the users, see their Addresses (one each) and Subscriptions, but even after toggling off "Verified" for the staff email address, clicking Update, then turning Verified back on and updating again, I still can't reset the password for that email address from the "forgot pasword" screen. Even tried adding that email address as another list owner. I have not made any API calls specific to adding users because the API documentation says, "Since her email address is not yet known to Mailman, a user is created for her." This does seem to have happened; GET 127.0.0.1:8001/3.1/users does show everyone's display name and unique user_id strings. I have tried using the API to PATCH a temporary password to the user but that didn't fix the inability to reset. The encrypted password does show in the /users/ data reported by the API (where previously there had been none), and a POST to users/<user_id>/login with that password return the 204 status shown to indicate success (instead of 403)... but I can't log in using Postorious with this user's email address and password. I also tried PATCHing the cleartext_password to /users/<email_address> and wasn't able to login or reset after that either. According to the API, each of the users -- webadmin where I can reset the password and staff where I can't -- does have a single address. (In the following, I redacted the API username and password ; changed email addresses, and IP address. And the display name, but left the timestamps and user_ids ) $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "webadmin(a)example.com", "original_email": "webadmin(a)example.com", "registered_on": "2021-11-25T04:20:33.408184", "self_link": "http://1.2.3.4:8001/3.1/addresses/webadmin@example.com", "verified_on": "2021-11-25T04:20:33.960577", "user": "http://1.2.3.4:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9", "http_etag": "\"394c07148f3fd0479cc582358b63b919fd988e36\""}], "http_etag": "\"a6621373598d299c32aa946fef7e32167d796bf3\""} $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/73235926306843ccb41f288d0464240a/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "staff(a)example.com", "original_email": "staff(a)example.com", "registered_on": "2021-12-15T02:25:24.055741", "self_link": "http://1.2.3.4:8001/3.1/addresses/staff@example.com", "display_name": "Staff Member", "verified_on": "2021-12-15T02:40:04.941153", "user": "http://1.2.3.4:8001/3.1/users/73235926306843ccb41f288d0464240a", "http_etag": "\"f24ba7ca9d71a7f814dc41d70c48ce947c1324be\""}], "http_etag": "\"e8d5b9f3ce0abbc7bbf51c03c69367f82679f93e\""} I am probably missing something, but this second query seems to confirm that the address "staff(a)example.com" is assigned to the user 73235926306843ccb41f288d0464240a and so shouldn't I should be able to request a password reset for "staff(a)example.com"? I've tried tailing all the log files I can find while attempting the reset and am not seeing any error messages, but I don't know exactly where to look. Thank you for any suggestions for what to try next! Dave

3 years, 5 months

Re: Error on timeout vs retry values

by Abhilash Raj

> On Aug 24, 2021, at 1:00 PM, Andrew Hodgson <andrew(a)hodgson.io> wrote: > > Hi. > > I just received the same error this evening when rebuilding Mailman3 on a new Debian 11 instal. There is a later version of Django on the new install. > > I got the original settings from the Mailman-Suite Gitlab project. I have made the modification but does this need to be made in that Gitlab project as well as that is where a lot of folks are getting their base Settings.py from? I have just updated the mailman-suite gitlab project with this change. https://gitlab.com/mailman/mailman-suite/-/commit/7f5dfd4992d4c454327233453… > > Thanks. > Andrew. > > -----Original Message----- > From: Robert Moody <robert(a)kneedrag.org> > Sent: 18 July 2021 22:35 > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Error on timeout vs retry values > > Thank you, that's fixed it. > > On 19/07/21 7:28 am, Abhilash Raj wrote: >> >> On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >>> Hi everyone, >>> >>> I have recently setup a new mailman3 service using the venv method. >>> Everything is functionally working however I keep getting an error >>> sent to the mailman email every min which I can not seem to figure out why. >>> >>> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: >>> UserWarning: Retry and timeout are misconfigured. Set retry larger >>> than timeout, >>> failure to do so will cause the tasks to be retriggered >>> before completion. >>> See >>> https://django-q.readthedocs.io/en/latest/configure.html#retry for details. >>> See >>> https://django-q.readthedocs.io/en/latest/configure.html#retry >>> for details.""" >>> >>> I have edited the timeout and retry values in the >>> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file >>> and restarted both mailman and mailman-web however this still keeps repeating. >> You shouldn't edit files in `site-packages` directory as they are part >> of the package itself and could cause issues. >> >> What you want to do is override it in your settings.py (or >> settings_local.py) file for Django. I am not sure which guide you >> followed to install Mailman, but it should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). >> >> It should look something like this >> >> >> https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web >> .settings.mailman.Q_CLUSTER >> >> Just the value of retry should be just > than timeout as the error >> says, so not necessarily same values, but so far 300 and 360 has been >> working good for us and I haven't seen any report to increase them. >> >> >>> Any ideas? >>> >>> Regards, >>> >>> Robert >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> _______________________________________________ >>> 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/ > _______________________________________________ > 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)

3 years, 10 months

Re: Confirmation emails to Users has wrong domain name (example.com!)

by Mark Sapiro

On 10/3/21 12:47 AM, Odhiambo Washington wrote: > On Sat, Oct 2, 2021 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> The SITE_ID setting affects the domain displayed at the top left of >> HyperKitty pages. Is this the correct domain? >> > > No. Mine is showing example.com OK. If I understand correctly, the subject of this thread notwithstanding, your only issue is the domain example.com displayed on the upper left of Hyperkitty web pages, and when you go to the domains view in Postorius, you see your domain with SITE_ID = 2. You said you edited settings_local.py to set SITE_ID = 2. Did you restart Apache after this? ``` touch /usr/local/mailman/etc/wsgi.py ``` should be sufficient to reload Django without restarting Apache. Have you done one of these things? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Mailman3 upgrades

by Caballero, Danny (Dan)

Thanks. I agree some kind of 'include' directive would be helpful so that customizations can be done without either getting clobbered by an update or inadvertently breaking the template as a result. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Thursday, October 21, 2021 6:46 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Mailman3 upgrades Caballero, Danny (Dan) writes: > Thank you! Yes, it was my fault. I have some customization in > base.html. Mailman devs don't consider that "fault", that's just life with software. There must be an XKCD for this, right? > I'll need to track those changes across updates. Yes. There ought to be a way around this. Maybe if we put those "load" instructions in little snippets that you can "include" in base.html and other templates that people might customize, and then we update the snippets? Steve

3 years, 8 months

missing graphics in Postorius

by David Newman

After installing MM3 on Debian 10 using the venv docs, no graphics appear in the admin or list pages, just broken links. The mailmanweb log has lines like this: ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. which is odd because there is the line for "localhost" in settings.py, and /etc/hosts correctly ties this to 127.0.0.1. There are entries like this in /var/log/nginx/error.log saying the files just aren't there: 2021/12/06 22:00:30 [error] 18123#18123: *65 open() "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" failed (2: No such file or directory), client: x.x.x.x, server: somehost.example.com, request: "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: "somehost.example.com", referrer: "https://somehost.example.com/mailman/lists/" (I've obfuscated names and addresses here, but "somehost.example.com" refers to a valid FQDN in the log.) I thought I'd followed all the venv docs, but the /opt/mailman/web/static/postorius directory doesn't exist. Did I miss something? Thanks. dn

3 years, 7 months

Re: how to become member of mailman-users list

by Shashikanth Komandoor

Thank you Steve for your response. On Tue, Aug 31, 2021 at 6:46 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Shashikanth Komandoor writes: > > > One of my colleagues is trying to become a member of the > > mailman-users list but she is not able to become so even after sending > > multiple emails to the list. > > Your colleague needs to either sign up via Postorius at > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > or send mail to mailman-users-subscribe(a)mailman3.org to subscribe. > She then needs to respond to the mail that the system sends her by > visiting the URL in that mail. > > Without a subscription, mail to the list will be discarded silently, I > believe. > > Once her subscription is active, her first post will be held for > moderation. After that, help posts will be unmoderated. > > Steve > -- Thanks & Regards, Shashi Kanth.K 9052671936

3 years, 10 months

Mailman-users search results for query "2021"