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

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

Oh wow.. so that was special. Sorry for the massive logs and back and forth. It turns out all I was missing was that I needed to re-run sudo mailman aliases before restarting the service. I have a different set of issues right now but I need to debug that a bit more to figure out what is going on. Thanks for all the help Mark, much appreciated. -- Samir Faci On Mon, May 4, 2020 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/20 11:07 AM, Samir Faci wrote: > > The only way I've gotten it to work so far is by using the FQN. I can > > switch back to 127.0.0.1 but that wasn't working. > > > > Here's the configuration I have. > > > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > smtp_host: 127.0.0.1 > > smtp_port: 25 > > smtp_user: > > smtp_pass: > > > > lmtp_host: 127.0.0.1 > > lmtp_port: 8024 > > > > > > > > and the end result: > > > > https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 > > which includes > > May 4 17:50:09 lists postfix/lmtp[2600677]: connect to > lists.domain.org[198.199.98.177]:8024: Connection refused > > So the question is, why is Postfix trying to connect to > lists.domain.org[198.199.98.177] and not to localhost[127.0.0.1] > > > > > smtp_host: 127.0.0.1 > > lmtp_host: 127.0.0.1 > > > > #fail > > > But it should work. > > > > smtp_host: lists.domain.org > > lmtp_host: lists.domain.org > > > > # success. > > > And this should not be necessary. > > > > The error I get if I don't open port 8024 is below and in the gist i > linked > > earlier. > > > > May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< > > testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, > > dsn=4.4.1, status=deferred (connect to lists.domain.org > [198.199.98.177]:8024: > > Connection refused) > > > This is what is expected if port 8024 is not open and you are connecting > to lists.domain.org. > > > > The only way I've gotten it to work so far is by binding both the > smtp_host > > and lmtp_host to be lists.domain.org and opening up port 8024. > > > > I'd rather not have that port open but I'm open to suggestions on what > else > > to try. > > > You need to get Postfix to use localhost[127.0.0.1] and not > lists.domain.org[198.199.98.177]. > > One issue is when you change > > lmtp_host: lists.domain.org > > to > > lmtp_host: 127.0.0.1 > > you need to run `mailman aliases` to change the settings in > var/data/postfix_lmtp. I think if you go back to > > smtp_host: 127.0.0.1 > lmtp_host: 127.0.0.1 > > and run `mailman aliases`, restart mailman and reload Postfix, it should > all work without opening port 8024 and probably without needing to put > 198.199.98.177 explicitly in mynetworks in Postfix. > > I suspect you will have issues with mail not being accepted or treated > as spam by some recipient ISPs however. See > <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS> > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

6 years, 5 months

[MM3-users] Re: Tracking from gravatar

by Abhilash Raj

On Mon, Feb 18, 2019, at 7:16 PM, worik wrote: > On 15/02/19 3:51 PM, Mark Sapiro wrote: > > You can disable them by setting > > > > GRAVATAR_SECURE_URL = '' > > > > in your local settings. See > > <https://github.com/twaddington/django-gravatar> > > Where do I make that setting? There is nothing like it in any of my files. This should go in your Django's settings.py (or settings_local.py) depending on how you installed Mailman. > Worik > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > 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)

7 years, 7 months

[MM3-users] Re: Welcome Message

by brian＠emwd.com

Mark Sapiro wrote: > Can you do bin/mailman shell? > > That would be even better. bin/mailman shell -bash: bin/mailman: No such file or directory Apparently not. Again this is the Docker version. Would love to have the Docker maintainer help out here. > If you're installing via pip you must have Python 3. Your tracebacks show a Python 3 > library in /usr/lib/python3.6/ /usr/lib/python3.6 -bash: /usr/lib/python3.6: No such file or directory I am installing it via pip on a Ubuntu server which is a different server from this template problem. Sorry about the confusion. The one where I need the templates to work is on a Centos server that used Docker to install it. I simply do not know how to get a python3 prompt when it has been setup via Docker. I will be requesting some assistance for the Ubuntu server once I get this template issue resolved. Brian

7 years, 6 months

[MM3-users] Re: Hyperkitty Authorization Required

by Andrew Bernard

Hi Mark, Thanks. But that is not the problem. It's hyperkitty background processes that show the error in the logs. I was probably not clear in my statement of the problem. I was testing it by typing in URL's. Sorry! I solved it by searching these archives. There was a post in January regarding the same issue, and the solution turned out to be replacing the given api keys with new ones, and all it all just works. Why that should be is a mystery to me, but now at least two people have found this. I would have thought a key is just a key. Andrew > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Friday, 7 June 2019 1:22 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty Authorization Required > You have to be logged in to post from HyperKitty. You can't post > anonymously.

7 years, 4 months

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Wolfgang Bock

Am 15.11.2019 um 02:21 schrieb Mark Sapiro: > Your Apache config needs to define separate a VirtualHost for each > domain, either by IP address or ServerName, and each VirtualHost points > to its own SSL certificates. Thanks for your info, that did it. I had to include the text of the apache.conf in all my apache-config-files for my virtual-domains. >> If I set use_https to yes in mailman.cfg I get on the website for all lists: >> >> postorius: Something went wrong >> Mailman REST API not available. Please start Mailman core. >> >> >> Does your setting in settings(_local).py for MAILMAN_REST_API_URL have >> an https scheme? That doesn't solve the problem. I changed that in mailman-web.py (MAILMAN_REST_API_URL = https://localhost:8001) and after that in mailman.cfg (use_https: yes). But got the same errormessage on postorius website. Regards Wolfgang

6 years, 11 months

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Abhilash Raj

> On Mar 27, 2021, at 6:03 PM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 3/27/21 6:42 PM, Mark Sapiro wrote: >> Ooops, Abhilash is correct. I have a bad habit of focusing on what's in >> the body of a post and sometimes missing relevant info in the subject. >> Sorry. > > Ok, can you or Abhilash reply to my previous questions. I thought I did, the support for specifying reason has been added in Postorius’s master branch. It will be in the next release, 1.3.5 probably. Core has had support for specifying reason when rejecting requests since 3.3.3. > > -- > Brian Carpenter > Harmonylists.com > Emwd.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)

5 years, 6 months

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/8/21 6:44 AM, rrosner5(a)gmail.com wrote: > > I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. Please see <https://wiki.list.org/x/12812344>. > I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. > > I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. > Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: > > /usr/share/mailman3-web/manage.py mmclient > Python 3.7.3 (default, Jan 22 2021, 20:04:44) > [GCC 8.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> client.system > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect > raise socket_err > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect > sock.connect((self.host, self.port)) > ConnectionRefusedError: [Errno 111] Connection refused The REST API is apparently not listening on the host/port this is trying to connest to. > An excerpt from /var/log/mailman3/web/mailman-web.log: > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ > command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute > settings.INSTALLED_APPS > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ > self._setup(name) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup > self._wrapped = Settings(settings_module) > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ > mod = importlib.import_module(self.SETTINGS_MODULE) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/share/mailman3-web/settings.py", line 486, in <module> > from settings_local import * > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 724, in exec_module > File "<frozen importlib._bootstrap_external>", line 859, in get_code > File "<frozen importlib._bootstrap_external>", line 916, in get_data > PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' > [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds > > not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. What is executing the manage.py command to start Django. Is it user list? > The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are > [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed > [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 > [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully > [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations > [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2' I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Message shows up individually but not in the thread

by Marvin Gülker

Am 04. November 2017 um 10:51 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > There is a possibly related issues at > <https://gitlab.com/mailman/hyperkitty/issues/151> and some older ones > at <https://gitlab.com/mailman/hyperkitty/issues/131> and > <https://gitlab.com/mailman/hyperkitty/issues/149>. > > I'm sorry I can't offer more help than that at this point. Okay. I'll have an eye on the problem and see whether I can make out any pattern on messages not appearing. I'm not (yet?) seeing the other symptoms described in #151, but our mailinglists are usually rather quiet until some burst of discussion arises. There have not been any newer posts than the linked ones yet. The mails all went out properly via email. It's a problem related to Hyperkitty thus. Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 11 months

[MM3-users] Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

3 years, 2 months

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Mark

>> On 12/17/24 13:35, Mark wrote: >> ... if I subscribe with an address that has never been used before, I >> receive an email that requires me to confirm the subscription. >> >> The subscription is also held in the administrator's "Subscription >> requests: Pending confirmation". >> >> This happens when subscribing by both email and the web UI. >> >> Ideally, as the Policy is set as "Open", the subscription of any new >> email address should be added automatically. > On 2024-12-18 00:00, Mark Sapiro wrote: > It is not the subscription that requires confirmation. It is the user's > email address. Even though the list's subscribe policy is open, a > previously unknown email address has to be confirmed. Thank you Mark. Your explanation is very much appreciated. Best, Mark

1 year, 10 months

Search results for query "sapiro"