Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 17:06, Mark Sapiro wrote: > On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >> A mail was sent to root on the localhost with the following content: >> >> Return-Path: <root(a)giesler.za.net> >> X-Original-To: root@localhost >> Delivered-To: root@localhost >> Received: from mailman.fast.za.net (localhost [IPv6:::1]) >> by mailman.localdomain (Postfix) with ESMTP id 2174A120A5B >> for <root@localhost>; Sun, 28 Jul 2024 13:11:03 +0000 (UTC) >> Content-Type: text/plain; charset="utf-8" >> MIME-Version: 1.0 >> Content-Transfer-Encoding: quoted-printable >> Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: >> /accounts/login/ >> From: root(a)giesler.za.net >> To: root@localhost >> Date: Sun, 28 Jul 2024 13:11:03 -0000 >> Message-ID: <172217226313.2150.10895652368679013629(a)mailman.fast.za.net> >> >> Internal Server Error: /accounts/login/ >> >> SMTPRecipientsRefused at /accounts/login/ >> {'roland(a)giesler.za.net': (454, b'4.7.1 <roland(a)giesler.za.net>: >> Relay acce= >> ss denied')} > > This is mail from django-allauth, not from Mailman. Your settings in > mailman.cfg do not affect how this mail is sent. See > https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend for > the Django settings for this. These settings from the Django docs look like the ones in mailman.cfg. Do I have to set them somewhere else too? SMTP backend¶ <https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend> /class/|backends.smtp.||EmailBackend|(/host=None/,/port=None/,/username=None/,/password=None/,/use_tls=None/,/fail_silently=False/,/use_ssl=None/,/timeout=None/,/ssl_keyfile=None/,/ssl_certfile=None/,/**kwargs/)¶ <https://docs.djangoproject.com/en/5.0/topics/email/#django.core.mail.backen…> This is the default backend. Email will be sent through a SMTP server. The value for each argument is retrieved from the matching setting if the argument is|None|: * |host|:|EMAIL_HOST| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST> * |port|:|EMAIL_PORT| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_PORT> * |username|:|EMAIL_HOST_USER| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST_…> * |password|:|EMAIL_HOST_PASSWORD| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST_…> * |use_tls|:|EMAIL_USE_TLS| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T…> * |use_ssl|:|EMAIL_USE_SSL| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S…> * |timeout|:|EMAIL_TIMEOUT| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO…> * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K…> * |ssl_certfile|:|EMAIL_SSL_CERTFILE| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C…> The SMTP backend is the default configuration inherited by Django. If you want to specify it explicitly, put the following in your settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" If unspecified, the default|timeout|will be the one provided by|socket.getdefaulttimeout()| <https://docs.python.org/3/library/socket.html#socket.getdefaulttimeout>, which defaults to|None|(no timeout).

1 year, 8 months

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Stephen J. Turnbull wrote: > Johan Alsina via Mailman-users writes: > > Hi, i installed mailman3 with virtualenv, all is working fine, the > > admin site works fine, the mailman(postorious) site works fine, but > > when im in hyperkitty the site shows without the css style.. in my > > web browser dev tool it shows like they loaded ok.. > > I think you need to figure out why the dev tool can see the CSS files > but other environments can't. It sounds exactly like all the other > problems I couldn't diagnose. :-/ > > Any ideas? :/ > > My static files are loading from > > /static/CACHE/css/output.a0f71925131b.css and > > /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css > > I've run into the "no styles" issue on a number of new hosts where the > problem was that somewhere on the path to the CSS files was a > directory, typically owned by root, without "x" permissions for > "other" users. That difference across trees is weakly consistent with > a "somewhere in between" permissions problem. > Steve Hi Steve, thanks for answer, i tried all about permissions and paths and i thins all its ok.. here you can see my paths/permissions.. General: https://freeimage.host/i/3ok1LDN Django project: https://freeimage.host/i/3ok1ZxI Mark Sapiro wrote: > On 3/17/25 6:46 PM, Johan Alsina via Mailman-users wrote: > > Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. > > Have you run mailman-web collectstatic and mailman-web compress? See > https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-f... > If you have, try running them again as mailman-web collectstatic --clear and mailman-web compress. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Hi Mark, thanks for the answer. Yes, i tried all variations about collectstatic, clear_cache, etc.. comands with no difference. I dont get any error and the files are collected ok.. Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. css files in /static/CACHE not loading: https://freeimage.host/i/3okk6CJ img files in /static/hyperkitty loading: https://freeimage.host/i/3okkPEv I tried to move /static/CACHE inside of /static/hyperkitty but when i run collectstatic the files goes again to the default path.. Thanks in advance..

1 year

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/27/26 07:17, Ibiam Chihurumnaya via Mailman-users wrote: > > Currently running Mailman 3.3.10 and I followed the instructions from https://docs.mailman3.org/en/latest/install/virtualenv.html# to install. > > OK. > > I get something else when I do it differently - how I've been doing it so far -. > > 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. > > from mailmanclient import Client > > from mailmanclient import Client > > client = Client('http://localhost:8001/3.1', '**', '**') > > sg = client.domains[0] > > sy = sg.get_lists()[-1] > > sy > > <List 'systems-logs(a)lists.sugarlabs.org'> > > sy.settings > > {'acceptable_aliases': [], ... > > OK. You are using Mailman Client which is a bunch of Python bindings for > Mailman core's REST API and which is intended for use by HyperKitty, > Postorius and Django-Mailman3 to communicate with Mailman core via its > REST API. Yes, the major reason I did this was because I wrote some helper scripts to do some things like create and delete a list, which the only domain in the mailing list selected. I'm assuming any other way to communicate with the rest API would automatically select the only domain that exists. It also seems to give more granular control over lists and members. Can mailman directly provide most of this functionality? > If you are using mailman shell you already have direct access to all > of Mailman core. Using Mailman Client is just adding overhead to things > you could do directly. > If you really want to use Mailman Client, rather than invoking mailman shell and all it brings that you don't use, you could just invoke your > venv's python, e.g., > $ /opt/mailman/venv/bin/python > or if your venv is active, just > (venv) $ python > and then import Client and continue as above. Makes sense, thank you! > > Yes, but like I've mentioned in another thread, I don't have access to the web UI because > > I can't get a confirmation link. > > You can always confirm your address manually > UPDATE account_emailaddress SET verified = 't' where email = 'your_address'; That worked, thank you! > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

The REST API documentation is a bit informal. As someone who is not familiar with mailman, and who doesn't know python, they are a bit of a slog. One day it would be nice to augment the documentation with a formal and complete reference document. Something like this one <https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_REST_API_R…>. A formal reference manual needs a complete listing of every type of object, all possible operations on each object, and all required and optional parameters. Since creating a formal document like that is probably out of scope, at a minimum it would be good to specify that boolean values are passed as JSON strings, not JSON booleans. It might be worth seeing if the code can be enhanced to allow the boolean values to be sent in using JSON booleans as well as JSON strings. Thanks again for the prompt response! -- Stephen On Tue, Jan 18, 2022 at 4:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 10:53 AM, Stephen Daniel wrote: > > 2nd follow-up. Apologies for spamming this list. > > > > I went wandering through the code as suggested by the traceback. I > > discovered that thee "as_boolean" routine is expecting a string argument > > but getting a boolean argument. > > > > So, If I send the booleans as strings, with values "true" or "false", all > > is well. > > This is not what the API documentation suggests I should do. Can someone > > either fix the documentation or the code? > > > Those snippets in the documentation are doctests. That code is actually > executed by unit testing and passes. In all those snippets, dump_json is > passing the second argument as `data` to > mailman.testing.documentation.dump_json() which in turn calls > mailman.testing.documentation.call_http() which calls > mailman.testing.helpers.call_api() which ultimately calls > requests.request() with the same `data` argument. > > So basically, the issue is the difference between how requests.request() > handles that `data` dictionary in creating the POST data and whatever > you are doing. > > Possibly we could add some caveat to > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> > > or possibly elsewhere. Do you have a suggestion as to what? > > > -- > 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/ >

4 years, 2 months

[MM3-users] Re: digest summary heavily cluttered with hrml code

by Mohsen Masoudfar

Hi Mark, Thanks again for your help! Yes, I meant "Today's Topic". I checked the link you sent, but could not see the solution to the issue. You mentioned: " They are in order of priority, list based, address based and global" Is this in descending or ascending priority? If I set it at list level, does it overwrite the member setting (address based?? )? I set them along with "Delivery mode" at the member level and saved it, but when I get back to it, it still shows "Regular" and other fields like: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings are empty, even though I set them and saved. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 14, 2020 12:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: digest summary heavily cluttered with hrml code [EXTERNAL EMAIL] On 10/14/20 8:46 AM, Mohsen Masoudfar wrote: > Hi, > > I am running Mailman 3.1.1 on Ubuntu 18.04. > > The user complains that the digest summary is cluttered with HTML code. What does 'summary' mean in this context? Are you referring to the 'Today's Topics:' list or the messages themselves? Is this perhaps <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…>? > I thought, I may fix it by: > Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. There are actually 3 sets of user preferences. They are in order of priority, list based, address based and global. You can see these if you are logged in to the web UI as the user and go to 'Mailman settings' in the pull down at the top right. There are issues in Postorius if a user is a member of a list with more than one role - see <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…>. > Question 1: How may I be sure that the value is set, if it is set? Examine the settings with `mailman shell` > Question 2: How may set it for all members of the list? Create a `mailman shell` script. > Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Again, `mailman shell`, but this is low level and requires some knowledge of Mailman internals. -- 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, 5 months

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/14/2018 03:04 AM, Aymeric Mansoux wrote: > > So far so good, however, for some reasons, a couple of our lists have started to accumulate held messages that cannot be manipulated via the REST API. Regardless if we use the web interface or mailmanclient, it ends up with: > > Mar 14 10:58:32 2018 (24287) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3.5/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.5/dist-packages/falcon/api.py", line 244, in __call__ > responder(req, resp, **params) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 70, in _make_resource > resource = super()._make_resource(request_id) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 39, in _make_resource > results = requests.get_request(request_id) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.5/json/__init__.py", line 319, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.5/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) > Mar 14 10:58:32 2018 (24287) 127.0.0.1 - - "GET /3.1/lists/xx(a)xx.xx/held HTTP/1.1" 500 59 > > Is there a way to manipulate/see/remove these mails differently? Right now this prevent moderation of any held messages (note: some lists do not suffer from this and the held panel or mailmanclient works perfectly fine). We've seen this issue before with a different underlying cause. See <https://gitlab.com/mailman/mailman/issues/256>. There are a couple of problems here. The serious problem is if there is a held message which somehow throws an exception in processing in mailman/rest/post_moderation.py, that totally breaks the Postorius held messages view for that list. We need to fix that. Also it would be good to see the problem message. Here are some things you can do in 'mailman shell' (aka mailman withlist). It is not clear what might not work, but you can try mailman shell -l list@domain which will respond Welcome to the GNU Mailman shell The variable 'm' is the list@domain mailing list >>> Then you should be able to do at the >>> prompts: >>> req_db = IListRequests(m) >>> reqs = list(req_db.held_requests) reqs is now a list of the held requests and you can do something like >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... or since req_db.held_requests is a generator >>> for req in rdb.held_requests: ... print('{}: {}'.format(req.id, req.request_type)) ... either of which will produce a list like 1: RequestType.held_message with the IDs and types of each request. You can handle these requests with something like >>> from mailman.app.moderator import handle_message >>> handle_message(m, 1, Action.defer) where the second argument is the ID of the message and the action is one of Action.defer, Action.hold, Action.discard, Action.reject or Action.accept, the first two of which do nothing, but the others will do the indicated action. You can see the actual messages like this >>> msg_db = getUtility(IMessageStore) then >>> key = req[0].key >>> msg_db.get_message_by_id(key) which will return the actual held message that is in this case index 0 in the list of held_requests. You may have to do >>> commit() when done, although if you don't do abort(), just exiting with control-D should do a commit(). I hope you find this helpful, and if you do determine the content of the offending message(s), it will be helpful if you post that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Receiving Email from ListName-bounce@Domain for Unsubcribe

by Marin Sok

Hi Mark, Yes, the notification email for unsubscribe from the list from test1-bounces@doamin. Agree with you that it should come from LIST-owner address. Fo example test1-owner@domain. Should I try to modify the code in file notifications.py in line 137. Screenshot. def send_goodbye_message(mlist, address, language): """Send a goodbye message to a subscriber. Prepending to the standard goodbye message template is the mailing list's goodbye message, if there is one. :param mlist: the mailing list :type mlist: IMailingList :param address: The address to respond to :type address: string :param language: the language of the response :type language: ILanguage """ goodbye_message = wrap(expand(getUtility(ITemplateLoader).get( 'list:user:notice:goodbye', mlist, language=language.code), mlist, dict( user_email=address, # For backward compatibility. user_address=address, fqdn_listname=mlist.fqdn_listname, list_name=mlist.display_name, list_requests=mlist.request_address, ))) with _.using(language.code): msg = UserNotification( address, mlist.bounces_address, _('You have been unsubscribed from the ${mlist.display_name} ' 'mailing list'), goodbye_message, language) msg.send(mlist, verp=as_boolean(config.mta.verp_personalized_deliveries)) Thanks, Marin <http:\\probonoweek.lalawlibrary.org> [http://www.lalawlibrary.org/sigimages/logo-sig.png] Marin Sok IT Director P 213.785.2556 | F 213.680.1727 http://www.lalawlibrary.org/<http://www.lalawlibrary.org/> | MSok(a)lalawlibrary.org Access to Information = Access to Justice <http://probonoweek.lalawlibrary.org/> Follow us: [http://www.lalawlibrary.org/sigimages/facebook.png] <http://facebook.com/LALAWLIBRARY> [http://www.lalawlibrary.org/sigimages/twitter.png] <http://twitter.com/LALAWLIBRARY> [cid:SocialLink_Instagram_32x32_dc37fa34-8ab4-41db-9940-9cb519436518.png] <https://www.instagram.com/lalawlibrary> ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, February 16, 2026 10:54 AM To: Stephen J. Turnbull <steve(a)turnbull.jp>; Marin Sok <MSok(a)lalawlibrary.org> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Receiving Email from ListName-bounce@Domain for Unsubcribe [You don't often get email from mark(a)msapiro.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] On 2/16/26 10:09, Stephen J. Turnbull wrote: > > Do you mean the notification email from the list is From > test1-bounces@domain? Are you sure it is from "test1-bounces@domain"? > It should be from "test1-owner@domain". Most notifications to users > come from the "LIST-owner" address. Actually, in this case it is From: the list bounces address. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/notificati…<https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/notificati…>>. There are other user notices From: the list bounces as well. See <https://gitlab.com/mailman/mailman/-/issues/1260<https://gitlab.com/mailman/mailman/-/issues/1260>>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: SocialLink_Instagram_32x32_dc37fa34-8ab4-41db-9940-9cb519436518.png Replaced multipart/alternative part with first alternative.

1 month, 3 weeks

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Mark, RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. I ran mailman aliases and the first try got can't read main.cf. I granted read-only access to other on the file, the next mailman aliases command ran without errors, but I don't know if it did anything or not, e.g. nothing in postfix_domains or the lmtp files. How can I verify that "mailman aliases" worked? Thanks, ---------- Keith On Wed, Jul 3, 2024 at 2:52 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > 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 keith1christian(a)gmail.com

1 year, 9 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Shashikanth Komandoor

Thank you Mark for your response. I understood that gunicorn is a front end that is used like web server like nginx. But I don't think I am using it instead I am using the httpd to redirect requests to postorius. And I am starting the mailman-suite with the command "python manage.py runserver 0.0.0.0:8000 --insecure &". Hope this does not use gunicorn (which of course I don't know what it is until now). Please correct me if any point I am mentioning is wrong. So, in this case, do you think configuring gunicorn as below would work: *calling gunicorn.cfg in mailman.cfg as below * *[webservice]* *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* *and content of gunicorn.cfg as below* *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.* *workers = 4graceful_timeout = 90* Also what is the difference between timeout and graceful_timeout ? Please help me if I can increase the management better. Any guide is also helpful for me. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 4:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:21 AM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Never mind please I am sending to you only instead of group as I am > > sending you the production content along with the mail. > > > See my other reply. > > > > I have configured the workers count as 4 and timeout as 900 in > > mailman.cfg under [webservice]. This is FYI. > > You can't configure Mailman's REST gunicorn workers directly in the > [webservice] section of mailman.cfg. The only thing you can configure > there is: > > configuration: /path/to/gunicorn.cfg > > That file, which is separate from your web server gunicorn.cfg, is where > you put things like > > [gunicorn] > timeout = 900 > > It also will not work to put a gunicorn section in mailman.cfg. It must > be in a separate file pointed to by webservice.configuration. > > Increasing the number of workers won't help this issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 8 months

[MM3-users] Re: Mailman 3 Privacy Policies, GDPR, etc and social logins

by Jered Floyd

This was what I was using as well, but it failed to meet their requirements for some ineffable reason. I had a few back-and-forths with someone for whom English was not their first language, and got them to accept a slightly modified version that I posted at https://www.convivian.com/mailman-privacy.html Now, the latest is that I have a new message noting that apps requesting user data (e.g. email address) must be linked to Business Profiles (text below). Django-allauth is cool, but I think it's not going to be long for this world and we'll just have to do internal auth. Disappointing from a workflow perspective, but I'm happy to dissuade subscribers to not use Facebook. Regards, --Jered P.S. The fresh hell from Facebook: You are receiving this message because Mailman List Manager is not connected to a verified Meta Business Account. On Feb 1, 2023 Meta began requiring business verification for apps that request access to data from users (for some apps this is called advanced access). Learn more about this requirement. [https://developers.facebook.com/blog/post/2023/02/01/developer-platform-req…] Here’s what a person with full control of your Business Account needs to do by Feb 2, 2024 to maintain access: Connect the app to a Business Account, if you haven't already. Complete business verification for the Business Account. Business Accounts connect your Facebook Pages, Instagram accounts and the people who work on them, so you can manage them all in one place. ----- On Sep 19, 2023, at 5:00 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 9/19/23 6:22 AM, Jered Floyd wrote: >> >> This is a bit of a headache. Do we have a draft of a community Privacy Policy >> for a vanilla Mailman 3 install that meets Facebook's requirements? Is this >> going to be a constantly unraveling thread of future GDPR and Right to Be >> Forgotten troubles, since there doesn't seem to be an easy way to scrub a >> subscriber from Hyperkitty archives if they request so? How have others >> addressed this situation? > > > I use https://www.list.org/privacy.html which appears to satisfy Facebook. > > -- > 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 jered(a)convivian.com

2 years, 6 months

Search results for query "sapiro"