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

[MM3-users] spam filtering (was: Re: list of subscribers)

by Peter Münster

On Sun, Feb 04 2018, Mark Sapiro wrote: > This would seem to be specific to your use case. I think in general what > we would want to display is the display_name from the list's member record. Ok, I see. Now I know, how to generate such list (email + full name) as site administrator, so it's ok for me. > We tried to send your copy of your post to you, but your MTA called it spam. > > Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: > to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, > delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host > mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of > DATA command)) IMO, spam filtering should be done at user level, every user should be free to filter what he likes, not the MTA. Perhaps I should do it like you, and manage my own email relay host? I've tried to subscribe with an address at orange.fr but it does not seem to work, probably the same problem as with free.fr... -- Peter

8 years, 8 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

Do you have something like this[1] in your settings.py file? [1]: https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… `EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'` `This is a dummy email backend which will basically only print the email to stdout, which seems to happen in your uwsgi-error.log. If you do, please comment it out and see if that solves your issue.` `Abhilash` On Sat, Mar 28, 2020, at 5:38 PM, Ralph Seichter wrote: > * Mark Sapiro: > > > What is the complete log message from uwsgi-error.log? > > I'll attach a typical log file to this message. It shows startup > messages followed by a recorded confirmation email. User name and > domain are obfuscated, but other than that the log is unchanged. > > -Ralph > > > _______________________________________________ > 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/ > > > *Attachments:* > * uwsgi-error.log -- thanks, Abhilash Raj (maxking)

6 years, 6 months

[MM3-users] Re: How to delete user completely?

by William Oliver

On Fri, 2022-01-21 at 16:50 -0800, Mark Sapiro wrote: > On 1/21/22 4:32 PM, William Oliver wrote: > > I have installed mailman3 and it's up and running great. However, > > I > > noticed that, during a mass subscribe, I mis-typed an address, e.g. > > name(a)domain.ned rather than name(a)domain.net. I found how to > > unsubscribe > > the bad address, but I haven't found a "delete" option under Users > > or > > anywhere else. How to I purge a user from the users list? > > You need to do it via REST or `mailman shell`. In mailman shell, > ``` > >>> um = getUtility(IUserManager) > >>> usr = um.get_user('user(a)example.com') > >>> um.delete_user(usr) > >>> commit() > ``` > > > As a related question, in docs.mailman.org, I can find a list > > member's > > manual, but I can't seem to find an admin manual. Is there one? > > > No, not per se. > Thanks! billo

4 years, 8 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 11:04 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > The `django-admin` command that is being run doesn't itself point to > your settings. In my case, I run django-admin via a wrapper that contains > ``` > #!/bin/bash > . /opt/mailman/mm/venv/bin/activate > cd /opt/mailman/mm > export PYTHONPATH=/opt/mailman/mm > export DJANGO_SETTINGS_MODULE=settings > django-admin $@ > ``` > The critical things are the exports of PYTHONPATH and > DJANGO_SETTINGS_MODULE. The former is the path to where your settings > module lives and the latter is its name without the .py extension. OK, making progress: mark@mail:/usr/local/bin$ !! ./mm3-admin shell Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email >>> emails = Email.objects.all() >>> for email in emails: ... if email.content.find('\u200b'*5) >= 0: ... print('Found in ml {}, hash {}'.format( ... email.mailinglist.name, ... email.message_id_hash)) ... ./mm3-admin: line 6: 702058 Killed django-admin $@ Now what? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 4 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by M. Ede

Am 11.09.25 um 20:38 schrieb Mark Sapiro: > On 9/11/25 10:03, Stephen J. Turnbull wrote: >> >> I don't think Mark was suggesting that would help with the >> SPOOFED_UNAUTH problem. I read his mail as saying that it needs to be >> fixed because it breaks anonymous_list. > > Exactly. Issue is now reported at https://gitlab.com/mailman/mailman/-/ > issues/1241 > In my tests, I sent an email via an anonymized list from an external list member who signed his emails with DKIM. The email sent via the anonymized list still contained the DKIM header with the following information: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1757947718; x=1758552518; i=medebb(a)gmx.de; bh=vcgwKHYW2uGBjO0+fBhuE4cVWQCtMNWYPsAtoVGcSpU=; h=X-UI-Sender-Class:Message-ID:Date:MIME-Version:To:From:Subject: Content-Type:Content-Transfer-Encoding:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=efMRr8yABy1/lYtU+rDbUup/kNJlirY6jaBCCMRbu1mHZG+6aa5jwk2+p7xSs2An WI4aVD5Dm5LsUjEz6VIFn7mYF6yy2h7DFoFFKaysbE4SEx8z1Vz23Ob0K9KnOlUgK fX7C+WS1Cr4rg0arSWN/OhRMHZUYwUv6q9Kk7FQcM+92UepNNsgnYNtI9NmGryL36 Ui536gOGLLqg7tpS/RkRYSvSYonHgvnsS2kM5VFdC8Ikyb6RC1Xzy5Nj3pO8xFy// 2xABTzbMuA3jnSTQ5PxlLUT7gg4c8c9WvW18+IAUIJKvedyfWgZnGRUxtDbiFKrDF sbX47CSb1jW6b3UPOg== This means that both the domain and the email address of the original sender are included. Don't all DKIM headers also have to be removed from anonymized lists?

1 year, 1 month

[MM3-users] Re: Shunt Error Mail?

by Pete Ashdown

On 3/2/21 4:09 PM, Mark Sapiro wrote: > On 3/2/21 2:52 PM, Pete Ashdown wrote: >> I have a number of list managers with subscribers who are confused as to >> why their messages are silently disappearing. I've read the archives on >> how to decipher why a message was shunted, but this is not workable at >> scale. Is sending an error email back to the sender a consideration? > Why are messages being shunted? Each shunted message has thrown some > kind of uncaught exception which is logged with a traceback in Mailman's > mailman.log. > > These should be due to bugs that should get fixed or possibly malformed > messages which are almost always spam. > > In short, under normal circumstances messages should not be shunted at > all and when they are it is something the site admins need to address. > It is normally not something the sender of the message can do anything > about. This is good to know. I was concerned that shunting could happen due to HTML or message content (ie: not size).

5 years, 7 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Torsten R.

Mark Sapiro wrote: > The issue is not related to message content. > One possibility is that there is an incompatibility between > mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause > this. What are your versions? Understood, just wanted to mention that as I read it in another thread about the 401. Hyperkitty is 1.3.4 and mailman-hyperkitty is 1.2.0 > What is your setting in mailman-hyperkitty.cfg for base_url: base_url is set to https://www.fqdn.tld/mailman/hyperkitty > if you append api/ to that and do something like > curl base_url/api/ > it should return a page of documentation of the API. If that is the > case, the issue is almost certainly communicating the api key between > mailman-hyperkitty and HyperKitty I get some information back when appending /api/ to that URL mentioned above about REST API and some formats and endpoints. So, from your words it looks like there is some issue in the communication between mailman-hyperkitty and HyperKitty. Is there some place I could/should start looking or some log I should be examining (maybe some loglevel to be increased as well)?

4 years, 6 months

[MM3-users] Re: A few more MM3 questions

by Marc SCHAEFER

Re, On Wed, May 29, 2024 at 09:23:07AM -0400, Mark Sapiro wrote: > > 2) I imported a list and all messages get a footer of: > > %(web_page_url)slistinfo/%(_internal_name)s > > which I guess changed between MM2 and MM3; however when I > > look at that list configuration in the web interface of MM3, > > I see no templates defined, nor any clue where this is > > configured: where may I change this? > > import21 creates these templates in (I think in your case) > /var/lib/mailman3/templates. Yes, I used import21, and there are files there, and they contain the "web_page_url" that is the cause of the problem. May I just modify those files, and is there any way to see, in the web GUI, where those files are referenced? In the database itself, the template table is empty (as seen in the GUI) and I did not see the text "web_page_url" in a dump of the database, so I have some issues to understand how this is used by Mailman (except direct file access to /var/lib/mailman3/templates?)

2 years, 4 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 1:20 PM, Mark Sapiro wrote: > On 7/7/22 12:44 PM, David Newman wrote: >> >> However, pip now throws a warning when looking at package info: >> >> (venv) mailman@somehost:/home/dnewman$ pip show mailman-web >> WARNING: Ignoring invalid distribution -jango >> (/opt/mailman/venv/lib/python3.9/site-packages) >> ... > > What does > ``` > ls -la /opt/mailman/venv/lib/python3.9/site-packages/-jango* > ``` > show? I suspect you have some spurious stuff there. The timestamps might > give a clue as to how it got there. > > If it shows anything, > ``` > rm -rf /opt/mailman/venv/lib/python3.9/site-packages/-jango* > ``` > will probably fix it. That was my first thought too. But there's nothing in that directory beginning with a hyphen, not even with the -a switch. The Django directories are as follows: django Django-3.2.14.dist-info django_allauth-0.47.0.dist-info django_appconf-1.0.5.dist-info django_compressor-3.0.dist-info django_extensions django_extensions-3.1.5.dist-info django_gravatar django_gravatar2-1.4.4.dist-info django_haystack-3.1.1.dist-info django_mailman3 django_mailman3-1.3.7.dist-info django_picklefield-3.0.1.dist-info django_q django_q-1.3.9.dist-info djangorestframework-3.13.1.dist-info dn

4 years, 3 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Gilles Filippini a écrit le 12/03/2021 à 01:41 : > Mark Sapiro a écrit le 12/03/2021 à 00:59 : >> On 3/11/21 3:10 PM, Gilles Filippini wrote: >>> >>> Looking at the offending message with 'mailman qfile', it appears it is >>> a legitimate one actually, sent from an Android phone. >>> >>> Couldn't hyperkitty be a bit less strict? >> >> >> Possibly. It looks like this may be >> <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What >> HyperKitty version is this? >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. >> >> If your HyperKitty is >= 1.3.2, please file a new issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> > > This is Hyperkitty 1.3.4. > I'll file an issue tomorrow. Here it is: https://gitlab.com/mailman/hyperkitty/-/issues/346 Thanks, _g.

5 years, 7 months

Search results for query "sapiro"