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

[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, 8 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.

9 months, 3 weeks

[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, 8 months

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

11 months, 1 week

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

1 year, 4 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Eggert Ehmke

Hello Mark, I am also using MySql/MariaDb, I followed your suggestion. This would uninstall a lot of other packages, is that safe? I did not continue. $ pip uninstall psycopg2_binary Found existing installation: psycopg2-binary 2.9.6 Uninstalling psycopg2-binary-2.9.6: Would remove: /opt/mailman/venv/lib/python3.11/site-packages/psycopg2/* /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary-2.9.6.dist-info/* /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libcom_err-2abe824b.so.2.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libcrypto-2cd0ac56.so.1.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libgssapi_krb5-497db0c6.so.2.2 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libk5crypto- b1f99d5c.so.3.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkeyutils- dfe70bd6.so.1.5 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5- fcafa220.so.3.3 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5support- d0bcff84.so.0.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ liblber-69811697.so.2.0.200 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libldap- e7812872.so.2.0.200 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libpcre-9513aab5.so.1.2.0 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libpq-227f62f1.so.5.15 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libsasl2-883649fd.so.3.0.0 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libselinux-0922c95c.so.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libssl-0331cfe8.so.1.1 Proceed (Y/n)? n Regards, Eggert Am Donnerstag, 19. Oktober 2023, 20:31:08 CEST schrieb Mark Sapiro: > On 10/19/23 05:02, Wikinaut wrote: > > (venv) mailman-web migrate > > > Traceback (most recent call last): > ... > > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/django/contrib/postgre > > s/search.py", line 1, in <module>> > > import psycopg2 > > > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", > > line 51, in <module>> > > from psycopg2._psycopg import ( # noqa > > > > SystemError: initialization of _psycopg raised unreported exception > > Since you are using MySql and not PostgreSQL, in your venv do > ``` > pip uninstall psycopg2_binary > ```

1 year, 6 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/ >> >

3 years, 3 months

[MM3-users] Mailman Suite release announcement

by Abhilash Raj

Hi All, I am pleased to announce new releases for Mailman Suite, including - Mailman Core 3.3.0 (Tom Swayer) - Mailmanclient 3.3.0 - django-mailman3 1.3.0 - Postorius 1.3.0 - Hyperkitty 1.3.0 This is a feature release and also includes a bunch of bugfixes. I am really really thankful to a lot of contributors who have helped out with this release. It is really nice to see Mailman 3 gaining more users and contributors. Python 3.5 is the minimum supported version, but all the releases have been tested to work with Python 3.5-3.7. This is the last release to support Python 3.5 since it has been in security only maintenance mode for a while now. Some of the highlights of this release includes: Mailman Core 3.3.0 - Support for ARC signing. Thanks to Gene Shuman and Stephen Turnbull. - Many many improvements to "mailman import21" command. Thanks to Mark Sapiro. - Addition of French templates. Thanks to Stéphane Parunakian. - A better and more scalable REST API server using Gunicorn. - Support for SMTPS/STARTTLS. Thanks to J08ny. A full copy of change log is available at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html Postorius 1.3.0 - Many more settings for MailingList configuration exposed, including preferred language, digest related settings. - Support for FILTER_VHOST to filter MailingLists based on the serving domain. Thanks to Nate Coraor. - Ability to write MailingList info in Markdown to render info in HTML instead of Plaintext. A full copy of change log is available at: https://postorius.readthedocs.io/en/latest/news.html Hyperkitty 1.3.0 - Unread messages, when logged in, are more easily recognizable with blue envelope icon. - Improved thread view with colored background for quoted parts of messages. - Improved readability on small screens by removing the indentation in thread view. A full copy of the change log is available at: https://hyperkitty.readthedocs.io/en/latest/news.html All the packages are available to download from PyPi (https://pypi.org) https://pypi.org/project/postorius/ https://pypi.org/project/hyperkitty/ https://pypi.org/project/django-mailman3/ https://pypi.org/project/mailman/ https://pypi.org/project/mailmanclient/ -- thanks, Abhilash Raj (maxking)

5 years, 8 months

[MM3-users] Re: Moderate mails from owner

by Abhilash Raj

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 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. > > Are my deductions correct? And if so, could this be the explanation of the > issue detailed in this thread? > > Apologies if I'm barking up entirely the wrong tree, Malcolm. > > -- > Malcolm Austen <malcolm.austen(a)weald.org.uk> > _______________________________________________ > 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)

6 years, 1 month

[MM3-users] Re: Mailman3 on FreeBSD

by Abhilash Raj

On Sat, 12 Aug 2017 18:10:49 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/12/2017 04:51 PM, Barry Warsaw wrote: > > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> > > wrote: > >> > >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however > >> I don't see any indication as to what I should put in this file > >> and if it was in /usr/local/etc/mailman.cfg then how would mailman > >> find it? > > > > It wouldn’t by default. Right now Mailman does not search > > for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult > > change to add. I’m not sure whether that would makes sense as a > > general default or not. I’m not up on the FreeBSD conventions and > > standards here; can you explain why /usr/local/etc is preferred > > over /etc on that distro? > > > I was hoping Abhilash would chime in here, because I think John is > using the docker image and there's probably a specific path for > mailman.cfg. As per his first message, I think John is using the prod setup from the documentaion[1]. I don't have anything much to add on top of what Barry mentioned, it looks like something is wrong with the Python install and missing Sqlite3 module. The documentation does mention the paths where Core looks for configuration file and anything else can be specified using -C or MAILMAN_CONFIG_FILE environment variable. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > As far as what goes in it, it could even be empty if you want to > accept all the defaults, but you probably want at least > > [mailman] > site_owner: real_person(a)example.com > > I expect if you do > > find -name mailman.cfg > > in your installation, you'll find at least examples. > thanks, Abhilash

7 years, 9 months

Search results for query "sapiro"