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

[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 ?

5 years, 8 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.

3 years, 8 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

5 years, 5 months

[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

2 years, 11 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

8 years, 2 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.

2 years, 3 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

6 years, 1 month

[MM3-users] Re: To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues

by Odhiambo Washington

On Sun, Jun 9, 2024 at 1:03 AM Ron <admin(a)bclug.ca> wrote: > On 2024-06-08 14:48, Mark Sapiro wrote: > > > The "PermissionError: [Errno 13] Permission denied: '//var/templates'" > > is what it says. It is trying to create the absolute path /var/templates > > and user mailman3 doesn't have permission to create a templates/ > > directory in /var. > > > > I'm not sure why this is. It should be trying > > /opt/mailman3/mm/var/templates. What does > > > I experienced the fun of having /var being where mailman3 tried to > create files & folders. > > Some combo of the following worked for me: > > > mailman3.service > Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" > > > /etc/mailman3/mailman.cfg > [paths.here] > var_dir: /opt/mailman/mm/var > You see, you are mixing /opt/mailman with /opt/mailman3. WHY? > I explicitly set many / most of the other vars in that section too (i.e. > lock_dir was one that also caused issues). > > > > This might be the Wrong Way, but it solved issues similar to the ones > being discussed. > If you followed the virtualenv installation method as documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html, then everything should be pointed to the home of the MM3 user you created at the step - https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u…. Then you wouldn't even need to get mixed up with paths and setting unnecessary environment variables. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 4 months

[MM3-users] Re: Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?

by Odhiambo Washington

On Wed, Dec 20, 2023 at 11:28 AM Pierre Malard via Mailman-users < mailman-users(a)mailman3.org> wrote: > Le 20 déc. 2023 à 09:14, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > > On December 20, 2023 7:20:17 AM GMT, Pierre Malard via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Ok, don’t throw any more away! > >> > >> If you really don't recommend the Debian packaged solution, I just have > one question: > >> Why have you included it in the Debian "main" repositories for so long? > > > > We have no control over what's in Debian repositories. Maintenance and > distribution of the Debian packages is done by Debian. > > > > We would love it if all the downstream distributions included up to date > and bug free Mailman packages. The problem is when people encounter > difficulty with a downstream package, we are often unable to help because > we don't know the details of that package. > > Ok Mark, > > Sorry, I thought that the creation of the repository depended directly on > you or, at least, on someone from the team. Obviously this is not really > the case and I will address the person in charge: Jonas Meurer I presume? > Still, the packages will always be lagging. With virtualenv, you have a container that only relies on very minimal apps from the base OS (python3-dev python3-venv sassc lynx), the MTA, the web server, and the DB backend and is mostly self-contained, besides the fact that you also get to run the latest code. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 10 months

[MM3-users] Re: High memory usage

by Philip Colmer

Thanks, Stephen. I think that the reason Prasanth & I wanted to check with this list first was to see if anyone was seeing similar behaviour. Our servers are *only* running Mailman 3 and associated packages like PostgreSQL and Postfix. Regards Philip On Wed, 16 Feb 2022 at 09:35, Stephen Daniel <swd(a)pobox.com> wrote: > I'm not an expert, and you might be better served by posting this question > in one of the communities that serves sysadmins; however, my reading says > that the oom-killer is invoked when the system cannot allocate more virtual > memory, not more physical memory. The graph in your screenshot is physical > memory usage. > > The first thing I would try is increasing the size of your swap > partition. That adds to the amount of available virtual memory, without > the need for actually buying more RAM. If you really need more RAM the > result will be that the system stays up, oom-killer stays quiet, but > performance is bad and the "si" and "so" columns in vmstat get into the > triple digits or higher. > > On Wed, Feb 16, 2022 at 3:18 AM Philip Colmer <philip.colmer(a)linaro.org> > wrote: > >> Thank you for the replies from Mark and Stephen. >> >> One of the reasons why Prasanth & I are concerned with this specific >> system >> is because the first time memory usage crept up, it got to the point where >> oomkiller stepped in and, as is usual for that particular mechanism, one >> of >> the processes it killed was sshd, thus removing access to the system :(. I >> know that oomkiller can be tuned to stop it killing processes like sshd >> but >> it will, nevertheless, start killing *some* processes if it sees an out of >> memory situation. >> >> So, as Prasanth said, we doubled the memory available and stuck an alarm >> on >> it to trigger when usage exceeded 85% for 5 minutes. I've saved a >> screenshot of the monitored memory usage over the last couple of weeks: >> >> https://1drv.ms/u/s!Aq7dn8GDGLdCodsU-pybJBdckxWU1A?e=BJY1UA >> >> (It is stored on OneDrive in case you don't recognise the URL format) >> >> We changed the server on 4th February to the larger memory size. On 11th >> Feb, it triggered the alarm and we rebooted the server. Memory usage is >> starting to climb again, albeit not at the pace that it was previously. >> >> What is particularly curious for us is that we have four Mailman 3 >> servers. >> Two of them are single domain and two are hosting two domains. This server >> is one of the servers hosting two domains, but it is also the ONLY one of >> the four servers exhibiting this memory pattern. By comparison, the memory >> usage for the other server hosting two domains looks like this: >> >> https://1drv.ms/u/s!Aq7dn8GDGLdCodsVyEufkeQqit_cGA?e=ifrJHs >> >> The biggest difference we are aware of with the "problematic" server is >> that some of the list archives are quite large by comparison with our >> other >> servers. The largest is 15K messages, then 2K then 1K. The other three >> servers have lists with relatively small archives by comparison (double or >> triple digits at worst). >> >> Finally, and just FYI, we're using PostgreSQL for the database and Xapian >> for the indexing engine. >> >> Regards >> >> Philip >> >> On Tue, 15 Feb 2022 at 16:36, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> > On 2/15/22 08:11, Stephen Daniel wrote: >> > > TL;DR: quite likely your system has plenty of memory and is operating >> > > normally. >> > ... >> > > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair < >> prasanth.nair(a)linaro.org> >> > > wrote: >> > > >> > >> Hi, >> > >> >> > >> We are having an issue with high memory usage on our Mailman3 server. >> > >> Initially, our server had 16GB RAM and the memory usage went up from >> 5% >> > to >> > >> 92% within a week. So, we increased the memory capacity to 32GB RAM >> and >> > we >> > >> can see that the memory usage is going up in the same pattern. >> > >> >> > >> Any idea why it is happening? or any suggestions? >> > >> > >> > Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM >> 3 >> > lists with 16 GB of ram and no swap. >> > >> > The server that supports this list and also the www.list.org web site >> > has 4 GB of ram and no swap. >> > >> > -- >> > 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/ >> > >> _______________________________________________ >> 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, 8 months

Search results for query "sapiro"