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

[MM3-users] Re: Using MySQL via unix socket

by Torge Riedel

Am 02.02.19 um 19:06 schrieb Mark Sapiro: > On 2/2/19 5:31 AM, Torge Riedel wrote: >> A call to >> >> mysql -umailman -p >> >> successfully uses the socket on the machine and logs in. > > Yet you haven't specified -S or --socket > > >> I tried >> >> mysql+pymysql://mailman:mailmanpass@127.0.0.1/mailman3?charset=utf8&use_unicode=1&unix_socket=/var/run/mysqld/mysqld.sock >> >> >> as the connection string but it says that mysql server is not available. >> Which is the same if remove the "unix_socket" parameter. I have found >> this parameter when searching the net, but I'm not sure if it is supported. > > I think it should be, but the actual connection is via the the > sqlalchemy create_engine() function. It appears this should be passed to > the pymysql Connection() function per > <https://docs.sqlalchemy.org/en/rel_1_2/core/engines.html#custom-dbapi-args> > > What happens if in a Python 3 session, you do > > from pymysql import connect > conn = connect('127.0.0.1', > user='mailman', > password='mailmanpass', > database='mailman3', > charset='utf8', > use_unicode=1, > unix_socket='/var/run/mysqld/mysqld.sock') > > As I understand it, that's what sqlalchemy should be doing with your > database url. In my testing, the above works with or without the > unix_socket= argument, so I suspect something else is wrong in your case. > Hi, thanks a lot for your answer. Yes, sounds valid that something else is (or was) wrong in my environment. I'm new to docker containers and might have overseen something. I now managed it a different way: I used rinetd on the host to redirect connections from docker host ip of a bridged network to 127.0.0.1 to make MySQL accessible in the docker container. This works and avoids mapping the mysqld.sock file into the container. Thanks again Torge

6 years, 5 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sun, 2021-12-26 at 16:47 -0800, Mark Sapiro wrote: > On 12/26/21 3:06 PM, William Oliver wrote: > > > > When running mailman3, do I need to set up a completely different > > virtual domain for it to run in? > > No. > > > > My "real" domain name is > > libertyfp.org, and I'm trying to make mailman work on that domain, > > e.g. > > "testlist(a)libertyfp.org." I'm starting to get the idea that I need > > to > > stick a completely different domain in there for the mailinglist. > > No. > > DNS or anywhere outside your server. > > Have you actually set an alias domain in Postorius for the > libertyfp.org > domain. It doesn't matter what name it is as long as it isn't > a real domain. A good choice is x.libertyfp.org. Have you set that > or > things like > > testlist(a)libertyfp.org testlist(a)x.libertyfp.org > testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org > testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org > ... [snip] Ah. I misunderstood you. I thought you meant that I had to tweak *postfix* to get this done. It's not that you weren't clear, it's that when I read the mailman3 instructions, I got the impression that *mailman* would set the alias domain automatically, so I was dead set on munging postfix. This makes more sense, and I can back out of some of the changes I made in postfix, which for the last couple of rounds was mostly flailing about randomly -- I've heard that's often not a good admin strategy. So.. if I need to do it myself, can you point me to what file I need to create/modify in the /opt/mailman/mm tree to set up the alias? Thanks! billo

3 years, 6 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: >> On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> >> wrote: >> >> > However, this is apparently not relevant because both the Member and >> > Non-Member actions are Hold. Thus, the post should be held unless it >> has >> > an Approved: header with the list's moderator_password attribute if >> > there is one, or it matches a Header filter rule with an accept >> action. >> >> At the risk of getting this really wrong - I have only limited MM3 >> knowledge - I will ask what is, I fancy, a closely related question ... >> >> My only experience of MM3 is with Ancestry's 'RootsWeb' installation. >> From >> the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't >> find >> anything to identify Postorius which is the only interface I have to the >> system. >> >> From symptoms seen and described by others, I have deduced that the >> Postorius admin-per-user moderation options of "Default processing" and >> "List default" mean that a user may be set (by default on the rootsweb >> system!) to use the system default moderation settings rather than the >> list default settings. > > "Default Processing" means the default pipeline defined in Thanks, I will do some (more!) reading. > List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This > pipeline is > system wide and is defined in source code, so it can't be customized by > site administrator. Unfortunately, that is not available to list-owners on the system concerned. Ancestry must have removed it. Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

6 years, 3 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 16:44 -0800, Mark Sapiro escribió: > On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > > very significant date for me (it is my wedding anniversary) and I'm 90% > > sure that I dedicated time to Weblate after that date... > > With respect to Mailman core, all I'm doing is downloading the .po for > Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po > from the Mailman core 3.3.3 package on PyPI and they are identical. > > If there are translated strings on weblate that are different from that, > they don't show up in the downloaded > <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>;. And you are very right and I have fallen as a newbee ... and first of all I apologise for the noise. I've been doing diffs with files downloaded from Weblate and those installed on the server by pip. As I should have done from the start. Mailman core and hyperkitty show no differences. Postorius shows a bunch and django_mailman3 just a couple. I leave for others a more detailed check of the strings between downloaded .po files and Weblate online strings, it's too late here. > > And I too want to help. It would be a help to me if you can give me > examples of specific strings whose weblate translation differs from > what's in the distributed .po files. And you have helped me, making me thing twice and stop moaning and going for the facts. Apologetic-thankful-big-mouth-shut-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 4 months

[MM3-users] Re: Disabled by bounce

by Stephen J. Turnbull

On 2/2/23 04:54, Danil Smirnov wrote: > > Isn't this a bug? Eye of the beholder. I will argue it's a doc bug. > > We are now showing users' bounce scores on the Members > > page and this would be misleading. If you mean the member's own page, yes, confusion is a problem. If you mean it's the Members page that the admins see, documentation and education is the answer, IMO. > > Is it difficult from internals > > perspective to have the bounce score reset immediately? Mark Sapiro writes: > Yes, it is not difficult, but it's a lot of processing. It would require > something like a task runner task to periodically look at each row in > the member table and if the bounce score is > 0, find the associated > list's bounce_info_stale_after and if last_bounce_received + > bounce_info_stale_after < now, reset the score. Aside: In programming, all problems are solved by another level of indirection. In databases, all problems are solved by another index. :-) You'd still need a runner, but it would be a simple "update these rows to zero", I guess. About the education and documentation for subscribers: I would argue that we can document the bounce score as a "recent highwater mark", since delivery isn't disabled yet. That's useful information for those with ears to hear it. That is, if you see "0" 95% of the time, occasionally "1", and today it's "2", maybe you wanna have a talk with your postmaster? On the other hand, if we reset immediately, I bet most users will rarely see anything greater than 0 because most visits are triggered by list posting, Admins would be similar, except that they might see correlations with remote domains, or if there was a wave across domains it might be a symptom of getting registered on an RBL or two.

2 years, 5 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Dadgar

On May 18, 2021, at 5:34 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/18/21 4:06 PM, Mark Dadgar wrote: >> I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. >> >> Any ideas what’s going on here? > ... >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login >> emailaddress = EmailAddress.objects.get_for_user(user, email) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user >> ret = self.get(user=user, email__iexact=email) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method >> return getattr(self.get_queryset(), name)(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get >> raise self.model.MultipleObjectsReturned( >> >> Exception Type: MultipleObjectsReturned at /accounts/login/ >> Exception Value: get() returned more than one EmailAddress -- it returned 2! >> Request information: >> USER: AnonymousUser > > > Go to the Django admin users page - something like > http(s)://example.com/admin/auth/user/ - and search for the email > address. This search is case-insensitive and I'm guessing it will find > two users differing in case. > > In any event, django allauth is trying to find this user and is finding > multiple EmailAddress.objects for this address or username. I had actually done this but checked the Users section and had overlooked the Email Addresses section. It was as you suggested - duplicate emails differing only in case. Given that there was only one user account, how does this happen? List subscription without associated user account creation with slightly different case? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 1 month

[MM3-users] Re: Importing archive from mm21

by Lars Bjørndal

On Mon, Nov 27, 2023 at 01:26:03PM -0800, Mark Sapiro wrote: > On 11/27/23 13:01, Lars Bjørndal wrote: > > I imported an archive from a list created in September 2013 with the > > following command: > > > > mailman-web hyperkitty_import -l annonsering(a)hodr.no --since 2013-09-01 <mbox file> > > > If it's a new list with no current archive, I typically don't use --since. > If there might be messages in the archive, I normally use something like > `--since 1970-01-01` just to be sure I get everything. There was some new messages in the archive prior to the import. > > No errors reported. > > > And this should have imported all messages with Date: header dates >= > 2013-09-01 plus any without Date: headers. > > > I then did > > > > mailman-web update_index_one_list annonsering(a)hodr.no > > > > No, when I go to https://hodr.no/archives/list/annonsering@hodr.no/, I > > cannot choose mails earlier than January 2023. > > > > What's the problem, do you think? > > The messages are there. I went to > https://hodr.no/archives/list/annonsering@hodr.no/ and only saw messages > from 2023, but then I went to > https://hodr.no/archives/list/annonsering@hodr.no/latest?count=200&page=2 > and started seeing all the messages even at > https://hodr.no/archives/list/annonsering@hodr.no/. > > What do you see now? Now, all messages are visible. > I also note your pages seem to be missing the styling as the references to > the styles, etc at https://hodr.no/static/* all return 404. Thank you. I had `Alias /mailman3/static /opt/mailman3/web/static` instead of `Alias /static /opt/mailman3/web/static`. As I'm blind, I didn't notice that missed icons/styling. > Is the issue fixed for you now? I don't understand what caused the issue. Tyank you, the issue is fixed. Lars

1 year, 7 months

[MM3-users] Re: Implicit destination

by David Krantz

On Mon, Aug 27, 2018 at 2:50 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > That is not the issue. Sending the held message notice to a spammer, if > it reaches the spammer, is probably inconsequential. The issue is that > virtually always in spam the sender address is either undeliverable or > is the address of an innocent 3rd party. Sending these notices to > innocent 3rd parties is called backscatter and is a bad thing. > > To avoid this backscatter, you can set the list's > respond_to_post_requests attribute to False. There are two problems > here. One is this setting is not currently exposed in Postorius, and the > other is this will also stop desired held message notices such as those > from list members. Aha. That was a simple solution although with a bad consequence. Will it stop moderation mails to the moderator as well? I'll try. Otherwise it will not be a problem in my case. The lists where I have this problem are more of function addresses for a number of persons (like a board or workgroup) so they accept posts from non-members. I use mailman as a simple forward gets legit mail caught in the receivers spam filters and might cause more black-list problems. You are of course entirely correct in that backscatter is the real problem, I should have thought of that. The thing in the spam I've received lately is somewhat sophisticated: the senders have correct (albeit strange) domains and correct SPF records so they try to seem legit although the senders are located in unexpected parts of the world. I just checked one example, in that case the MX pointed to the sender IP, the SPF was very sloppy (~all) and everything looked correct except for the fact that we usually do not receive mail from Ukraine and the cryptocurrency scam in the body. It almost got caught in the spam filter, but not quite. cheers // David

6 years, 10 months

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

by Roland Giesler

On 2024/07/25 20:50, Mark Sapiro wrote: > On 7/24/24 06:35, Roland Giesler via Mailman-users wrote: >> I have managed thus far to get things working on my new install, but >> I need to use a secure logon to send mail from an external MTA. I >> have set up: >> >> /etc/mailman/mailman.cfg: >> >> smtp_host: box2.gtahardware.co.za >> smtp_port: 465 >> smtp_user: roland(a)giesler.za.net >> smtp_pass: <hidden> >> smtp_secure_mode: smtps >> smtp_verify_cert: no >> smtp_verify_hostname: no > > This looks OK, but > >> I'll get a cert installed later, for now just want to get it going. > > The `no` values for smtp_verify_cert and smtp_verify_hostname may be > part of your issue. After re-reading the documentation I realised that and changed it to "yes" for both since box2.gtahardware.co.za has valid certs. > > ... >> "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", >> line 125, in _send >> self.connection.sendmail(from_email, recipients, >> message.as_bytes(linesep='\r\n')) >> File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail >> raise SMTPRecipientsRefused(senderrs) >> smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, >> b'4.7.1 <roland(a)giesler.za.net>: Relay access denied')} >> >> However, the mailserver is in daily use and accept logon all the >> time. I believe I'm missing something that should be installed to >> make SMTPS (SSL) work, but what? > > It is the mail server at box2.gtahardware.co.za that is refusing to > relay this message. I think this issue needs to be resolved in that > MTA's configuration. Indeed that is so, but that box is in daily use by a few different users and they authenticate and send email without any problems. I'm checking out the link you shared in my other thread now.

11 months

[MM3-users] Re: Template path

by Seth Seeger

> On Sep 17, 2020, at 12:54 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> I followed previous emails on this list which told me to set POSTORIUS_TEMPLATE_BASE_URL in /opt/mailman/web/settings_local.py, but that doesn’t seem to make any difference. (I set it to a different value and the error message didn’t change. I also tried setting it in /opt/mailman/core/settings_local.py to no effect. After each change, I restarted mailman-web and mailman-core containers.) > > > How did you create the template? In Postorius or by manually creating a > file somewhere? If by creating a file, POSTORIUS_TEMPLATE_BASE_URL is > not relevant, but ensure that the file is findable and readable by Mailman. I created the template in Postorius. >> From within mailman-web and mailman-core containers, I can reach “mailman-web:8000”. >> >> In the webpage, I see: Mailman REST API not available. Please start Mailman core. > > > The REST APT is normally exposed on port 8001, not 8000 (See `port` in > `mailman conf -s webservice`. Yes, it’s 8001: [webservice] hostname: 172.19.199.2 [webservice] port: 8001 > What is your setting for MAILMAN_REST_API_URL? does the port match? I’m not overriding it: ./postorius/mailman-web/settings.py:MAILMAN_REST_API_URL = os.environ.get('MAILMAN_REST_URL', 'http://mailman-core:8001') > >> In /opt/mailman/core/var/logs/mailman.log, I get: >> >> [17/Sep/2020:16:23:29 +0000] "GET /3.1/lists/xxx.example.com HTTP/1.1" 200 416 "-" "GNU Mailman REST client v3.3.1" > > It appears you are connecting to the REST API, but ... > ... >> urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) > > > Something appears to be trying to connect to REST on port 8000 Is this a red herring? Is something else wrong? Setting POSTORIUS_TEMPLATE_BASE_URL in settings_local.py doesn’t seem to make any difference. Having set the POSTORIUS_TEMPLATE_BASE_URL, I deleted the template and recreated it. Now, when I approve a pending subscription it goes through, but the welcome email is blank. Seth

4 years, 9 months

Search results for query "sapiro"