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

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 10:02 AM, brian(a)emwd.com wrote: > I followed Kelly's guide and ran into some issues but were able to resolve most of them. It seems I have one out standing issue: Hyperkitty. When I post to a list, I am getting the following in the /var/log/mailman3/mailman.log: > > Apr 11 14:01:15 2019 (1334) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF/$ > <html><head> > <title>503 Service Unavailable</title> > </head><body> > <h1>Service Unavailable</h1> > <p>The server is temporarily unable to service your > request due to maintenance downtime or capacity > problems. Please try again later.</p> > <hr> > <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> > </body></html> > (503) ... > Everything else works fine. Postfix is receiving and delivery mail to Mailman3. List members are receiving the posts. I can access the list on Hyperkitty just no archived messages. What URL do you use to access HyperKitty. The problem URL above, http://localhost/mailman3/hyperkitty/api/mailman/archive is based on the base_url setting in mailman-hyperkitty.cfg which in your case is http://localhost/mailman3/hyperkitty/, byt the web server listening on localhost:80 is returning the Service Unavailable. It probably doesn't like the IP or name 'localhost'. Set base_url in mailman-hyperkitty.cfg to use an acceptable host name instead of localhost or adjust your apache config to accept localhost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/11/22 09:37, Stanisław Findeisen via Mailman-users wrote: > Dear Experts > > What is the best way to go about reconciling GNU Mailman3-made message modifications (like message footers or subject prefixes) with sender-made DKIM signatures? I am aware of the "DMARC mitigations" tab in the list settings, not bad, but it looks that "replace From: with list address" doesn't help (of course), whereas wrapping the message in an outer message often looks ugly. Is there a better way?... > > BTW I would like to point out that broken DKIM signature can be a problem even with an easy DMARC policy; for example ProtonMail will display this flashy red warning: https://protonmail.com/support/knowledge-base/email-has-failed-its-domains-… in its webmail. (I guess nothing can be done about it except "DMARC Mitigate unconditionally"). ProtonMail is broken - see https://www.rfc-editor.org/rfc/rfc6376.html#section-6.1 That said, BCP recommends removing the signatures that the MLM will break https://www.rfc-editor.org/rfc/rfc6377.html#section-5.7 Mailman implements this with the mailman.cfg setting ``` [mta] remove_dkim_headers: yes ``` Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your valid DKIM signature and no prior Authentication-Results:. ARC <https://www.rfc-editor.org/rfc/rfc8617.html> is intended to address this while preserving prior authentication results and is supported by Mailman, but is not accepted by all receivers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 5/7/19 1:54 AM, Henrik Rasmussen wrote: > Do I have to make a commit or something? Even m.accept_these_nonmembers.remove removes the member from the list, it is right back when I return to the Mailman shell: > >> bash-4.3# mailman shell -l [LISTNAME].lists.example.com >> Welcome to the GNU Mailman shell >> The variable 'm' is the [LISTNAME].lists.example.com mailing list >>>>> m.accept_these_nonmembers >> ['listadmin(a)senderdep.example.com'] >>>>> m.accept_these_nonmembers.remove('listadmin(a)senderdep.example.com') >>>>> m.accept_these_nonmembers >> [] >> quit() There are potentially two issues here. First, the entire interaction is in the context of a database transaction and quit() exits without committing the transaction. abort() will also abandon the changes but not exit. commit() will commit the changes and not exit, and control-D will implicitly commit and exit. Thus, you need to exit with control-D or commit() before quit(). However, there is another potential issue and that is the one described at <https://stackoverflow.com/questions/37310770/sqlalchemy-committing-pickle-t…>. What this says is the way the *_these_nonmembers attributes are defined in the SQLAlchemy data model results in changes due to mutating the list (which .remove() does) aren't recognized. See <https://gitlab.com/mailman/mailman/merge_requests/505>. I think in your case, if you just do m.accept_these_nonmembers = [] commit() and then look at m.accept_these_nonmembers again which will show you what's in the database, you'll see that you have what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

by Mark Sapiro

On 12/4/19 6:15 AM, actionmystique(a)gmail.com wrote: > Ubuntu 20.04 > mailman3 3.2.2-1 > python3-django-hyperkitty 1.3.0-1ubuntu1 > > According to [Hyperkitty Asynchronous tasks paragraph](https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks), we can start a qcluster systemd service file: ... > [Service] > ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings > User=<user> > Group=<group> > Restart=always Did you replace <django_project_path>, <user> and <group> with appropriate values? ... > Starting it works fine: ... > However, the service fails after a few seconds: > ``` > # systemctl status qcluster > ● qcluster.service - HyperKitty async tasks runner > Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) > Active: failed (Result: exit-code) since Wed 2019-12-04 15:09:48 CET; 1min 1s ago > Process: 1055961 ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings (code=exited, status=1/FAILURE) > Main PID: 1055961 (code=exited, status=1/FAILURE) It appears you haven't replaced <django_project_path> with the actual path to the directory containing your Django settings.py file Also, <user> and <group> should be those of the Mailman user, probably 'list' in Debian/Ubuntu packages. ... > Also, another doc paragraph [Running the task queue (required)](http://docs.mailman3.org/en/latest/config-web.html#running-the-t…) talks about another required command "python manage.py qcluster"; so which one is it? They should be the same thing. Usually manage.py is just configured to run the django-admin command for the particular project. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/19/20 4:09 AM, Alan So wrote: > It is exactly the file I used to test (listname and list server munged). I can send you the full header personally if you want. I did a similar test. I used this message exactly ``` From: mark(a)msapiro.net To: list(a)example.com CC: "ABC DEF (XYZ)" <ktso(a)cuhk.edu.hk> Subject: testing please ignore Message-ID: <sfhifdgdfdsjHHIHIo987sd(a)98vD9FVhdv.8shy65FGvsd> Hello ``` and I posted it to the list via `mailman inject`, and the message I received back from the list with some headers removed was: ``` From: mark(a)msapiro.net To: list(a)example.com Message-ID: <sfhifdgdfdsjHHIHIo987sd(a)98vD9FVhdv.8shy65FGvsd> Message-ID-Hash: NUQVMF52CDRIRH4RXEM2VV7MU3HYXASG X-Message-ID-Hash: NUQVMF52CDRIRH4RXEM2VV7MU3HYXASG Date: Tue, 19 May 2020 17:24:34 -0700 CC: "ABC DEF (XYZ)" <ktso(a)cuhk.edu.hk> X-Mailman-Version: 3.3.2b1 Precedence: list Subject: [List] testing please ignore List-Id: <list.example.com> Archived-At: <https://msapiro.net/archives/list/list@example.com/message/NUQVMF52CDRIRH4R…> List-Archive: <https://msapiro.net/archives/list/list@example.com/> List-Help: <mailto:list-request@example.com?subject=help> List-Post: <mailto:list@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello _______________________________________________ List mailing list -- list(a)example.com To unsubscribe send an email to list-leave(a)example.com ``` Note that the Folded CC: header in the received message is exactly the same as in the original message. Are you looking at the raw message received from the list or some MUA's rendering of it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Problem updating mailman

by Mark Sapiro

On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't remember consciously > installing that because it was never in the guide I followed (which is your > own writeup). > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > + '[' False == False ']' > + mkdir -p /opt/mailman/mm/static > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > --verbosity 0 > + /opt/mailman/mm/bin/django-admin compress > CommandError: An error occurred during rendering > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > */bin/sh: sass: not found* You can't just uninstall rubygem-sass. You have to replace it. Here's one recipe for Ubuntu cd /usr/local/lib # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the # appropriate version. wget https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5… sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz sudo chmod -R o-w dart-sass sudo ln -s dart-sass/sass /usr/local/bin/sass rm dart-sass-1.32.5-linux-x64.tar.gz Then you should see the command sass --version prints 1.32.5 Then, because dart-sass doesn't recognize the short form -t option for --style, you have to edit your settings(_local).py and change COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) to COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass --style compressed {infile} {outfile}'), ('text/x-sass', 'sass --style compressed {infile} {outfile}'), ) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Mark Sapiro

On 4/13/22 10:04, bob B via Mailman-users wrote: > > So to confirm my assumptions/findings: > Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent > Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... Correct. > So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? > > If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? To send digests periodically regardless of size, you need to run `mailman digests --periodic` on the schedule you want. This will send the accumulated digest if any for every list that is configured to Send Digest Periodically. Normally, this is run daily via cron. If you want a different schedule for different lists you need to run `mailman digests --list list(a)example.com --periodic` per list on its own schedule. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: possible backscatter attack using Mailman3 servers

by Mark Sapiro

On 1/3/25 16:18, David Newman wrote: > Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing > about 20-30 entries per day in the Postfix queue where it appears a > Gmail user signs up for a mailing list that requires confirmation, and > Gmail responds that the user is too busy to handle requests. > > There are no publicly advertised email lists on this server, and I don't > ever see anything in the Mailman logs indicating the user ever tried > signing up. This is an attack mail bombing the user. The requests that result in the can come via web or email. Mailman's logging of subscribes has been missing most events through Mailman 3.3.10. See https://gitlab.com/mailman/mailman/-/issues/1143 which will be fixed in 3.3.11, but subscribes waiting user confirmation still won't be logged. However, the message with subject "Please Confirm Your Email Address" comes from Django allauth so it isn't actually Mailman sending it but rather Django allauth as a result of a request to sign up for a Django account at https://mail.example3.com/accounts/signup/. You can probably find that request in your web server logs, and you may find the user and/or email in the Django admin UI. Since django-mailman3 1.3.6, you can disable these signups by putting ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in your Django settings, but then your users won't be able to sign up for web accounts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 10/02/2017 05:25 AM, Henrik Rasmussen wrote: >> The bottom line is at this point, <https://bugs.python.org/issue27321> >> no longer affects Postorius, but it still affects message delivery. I >> have opened <https://gitlab.com/mailman/mailman/issues/406> about >> defending against that and also the UnicodeEncodeError you included in >> your OP. > > Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? There is no user or list admin workaround, but the defense is a fairly simple patch. See the MR at <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit at <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. The commit changes 7 files, but only two are needed. The rests are tests or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't necessary. The only changes you need are those to mailman/email/message.py and mailman/mta/connection.py. >> No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command >> is 'bin/show_qfiles'. > > I much be in the wrong place because when I do a 'docker exec -it mailman-core bash' and do a 'mailman --help' I don't see a 'queue' argument. The only bin/mailman I have inside the mailman-core container is /usr/local/bin/mailman, which is the same command. My bad. The name is 'qfile', not 'queue'. Sorry about that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: Archive import fails: "IndexError: list index out of range"

by Mark Sapiro

On 1/7/23 23:04, Stephen J. Turnbull wrote: > Johannes Rohr writes: > > > IndexError: list index out of range > > That isn't the problem, it's the earlier failure, I think: > > > File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, > > in get_msg_id > > token, value = get_dot_atom_text(value) > > File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, > > in get_dot_atom_text > > raise errors.HeaderParseError("expected atom at a start of " > > email.errors.HeaderParseError: expected atom at a start of dot-atom-text > > but found '@localhost>' > > It appears that HyperKitty is trying to find a domain name (the common > use for "dot_atom_text" in mail headers in a Message-ID), but is > finding "@localhost>" instead. Actually, this occurs after the message has been converted to an email.message with policy=policy.default. Getting the Message-ID attempts to parse it and in this case, the dot_atom_text it's looking for is the 'local part' which doesn't exist. I.e. <xxx@localhost> would be OK, but <@localhost> is not. > First I would try the check_hk_import script which is provided with > HyperKitty. HyperKitty's contrib/check_hk_import script didn't find this issue. The GitLab branch was updated yesterday, but that update is not yet released. An up to date script which does find this issue is at <https://www.msapiro.net/scripts/check_hk_import>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Search results for query "sapiro"