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

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/30/20 11:24 AM, Odhiambo Washington wrote: > This works - I mean changes the error message to > > [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] > /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) I'm not sure why you are getting this warning, and it's non-fatal, but you can get rid of it by pip install cmarkgfm in your virtualenv. > [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client > 197.232.81.246:63962] AH01630: client denied by server configuration: > /var/spool/mailman-web, referer: > http://mm3-lists.my.server/mm3/mailman3/lists/ > > There is NO /var/spool/mailman-web anywhere. It has not been created. > You mentioned that it should be created automatically, IIRC. No. I think I told you that the references to /var/spool/mailman-web/static in your Apache config should be changed to /opt/mailman/mm/static and that directory would be created/populated by mailman-post-update. I think you still have Alias /static "/var/spool/mailman-web/static" in your Apache config and it needs to be Alias /static "/opt/mailman/mm/static" That may be my fault as when I recently edited <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>, I missed that line. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. ``` Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is ``` Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Mark Sapiro

On 3/18/19 2:19 PM, Ralph Seichter wrote: > Hello list. > > I have read [1] and [2], but I am not quite sure what the recommended > method is to completely disable message headers/footers and subject > modifications for *all* lists tied to a specific domain. Being new to > Mailman 3, I was actually surprised that there are no configuration > switches in the Web UI's settings for mailing lists that allow me to get > rid of unwanted message decorations. It's still a work in progress. You can do it via list settings except for one issue [1]. See that issue and also the post referenced in it's description [2]. To not modify the Subject for a list, on the list's Settings -> List Identity tab, set 'Subject prefix' empty. To not add headers and or footers, you need empty templates for them. These could be created via the list's Templates form except until [1] is fixed, you can't make empty templates. You can use the method in [2] to create empty var/templates/domains/DOMAIN.NAME/LC/list:member:generic:footer.txt and var/templates/domains/DOMAIN.NAME/LC/list:member:generic:header.txt files for the domain and language. Then as long as no list specific templates are created for lists in that domain, no headers or footers will be added. [1] <https://gitlab.com/mailman/postorius/issues/331> [2] <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/22/20 12:20 AM, r.woithe(a)callassoftware.com wrote: > Hello, > this is the complete email we get every night: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs > job().execute() > File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 36, in execute > sync_with_mailman() > File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 146, in sync_with_mailman > sender.set_mailman_id() > File "/usr/lib/python3/dist-packages/hyperkitty/models/sender.py", line 55, in set_mailman_id > mm_user = client.get_user(self.address) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 320, in get_user > response, content = self._connection.call( > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1948, in request > (response, content) = self._request( > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1621, in _request > (response, content) = self._conn_request( > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1560, in _conn_request > response = conn.getresponse() > File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse > raise ResponseNotReady(self.__state) > http.client.ResponseNotReady: Request-started > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > START TRACEBACK: > END TRACEBACK OK. So python2.7 in the Subject: is not relevant. The issue is probably a timeout in mailmanclient's REST request. See <https://wiki.list.org/x/17892072> for info on how to increase it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: hyperkitty_import Unicode Errors - Drop all Archives and Start Over?

by Mark Sapiro

On 5/16/23 08:49, Dave Hall via Mailman-users wrote: > > What I would really like to do is to drop all of the previous archives and > start fresh. Looking at the table list for the database, It would appear > that all of the archive content is stored in the tables with names that > start with 'hyperkitty_' I'm wondering if I could just wipe the content of > these tables, or exclude them from a backup, and then start fresh. It is correct that all the HyperKitty tables start with `hyperkitty_`. I *think* it would be safe to just drop the content of these tables, but I won't guarantee that there aren't `django_mailman3_` tables with foreign keys into the hyperkitty tables. As a superuser logged in to hyperkitty, you should see a Delete Archive button at the top level overview for a list. It would be safer to delete the archives that way. > Alternatively, if I restore the exiting archives to the new database with > the correct unicode settings, could I re-run the hyperkitty-import tool and > get it to pick up all of the messages it skipped due to the unicode problem? This will work too. You will need to specify the --since option to hyperkitty_import because the default for `since` is the date of the newest message in the archive. The import will not reimport a message whose Message-ID: is already in the archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Remove old bounces in bouncedir

by Mark Sapiro

On 3/10/22 00:31, Stephan Krinetzki wrote: > Mark Sapiro wrote: > >> If you are referring to messages in Mailman's bounces queue, if these >> are not processed and removed within 15 minutes of arrival, Mailman's >> bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > ``` > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > ``` > > The process it self is there > > ``` > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > ``` I don't understand what's happening. If the bounces runner is processing it's queue, those .pck files should be processed and deleted. Are there errors in /opt/mailman/var/logs/mailman? If you examine (some of) those files with `mailman qfile` do you see anything strange? Is there an ownership/permissions issue? Sometimes people run Mailman or some Mailman command as `root` and things get owned by root and then when Mailman is later run as `mailman` it can't delete or maybe even read them. >> If you are referring to bounce messages in the message store >> (var/messages/), there have been issues with those not being removed, >> but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. Is the size of the /opt/mailman/var/messages directory very big? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: mailman break DKIM signature by modifying body

by Mark Sapiro

On 6/5/23 07:06, Peter Münster wrote: > Hi, > > I'm using mailman 3.3.8. > > Some messages with attachments from Google users get rejected by spam > filters because of invalid DKIM signatures. > > It seems, that mailman alters some lines in the body. Here an example: > > Original message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2031 > > --000000000000f846c505fc494b7a-- > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > Altered message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2032 > > --000000000000f846c505fc494b7a-- > > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > An empty line is added, and the spaces after the semicolons are removed. > > Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. > > What could I do please, to prevent such modifications of the body? Changes like those above are due to Python's stdlib email module. Short of actually modifying the email module, there's nothing you can do to prevent them. Instead, you should be DKIM signing your outgoing mail and perhaps applying Mailman's DMARC mitigations if DMARC is an issue. If you are DKIM signing your outgoing mail and mail is being rejected because of prior invalid signatures, you can remove those by adding `remove_dkim_headers: yes` to the [mta] section of mailman.cfg. Also, ARC signing <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…> may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 7/4/20 9:03 AM, tom(a)gather.coop wrote: > > So I hope there is not an expectation that the rDNS domain match the email sender domain. If so I'm toast. Is it just sort of a smell test to see if the server looks legitimate? Probably part of your confusion is the ambiguity of the term `sender` which can refer to any of: - the actual individual sending the original mail (the From: header) - the envelope sender (the listname-bounces@listdomain address in the case of list mail) - the sending server. In the case of FCrDNS we're talking about the server (MTA) delivering the message to the recipient MX. I.e., that server's IP should have a PTR to its name and its name should have a A (or AAAA in the case of IPv6) record with the same IP. That's what FCrDNS implies. Quoting from <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>: "... the requirement is the forward and reverse lookup for the sending relay have to match, it does not have to be related to the from-field or sending domain of messages it relays." It is also good if the name by which the MTA identifies itself (the myhostname setting in Postfix) is the same as the server's name. Quoting from the same article: "Some e-mail mail transfer agents will perform FCrDNS verification on the domain name given on the SMTP HELO and EHLO commands. This can violate RFC 2821 and so e-mail is usually not rejected by default." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Mark Sapiro

On 4/17/19 8:10 AM, Abhilash Raj wrote: > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: >>> >>> Which version of Hyperkitty are you using? >>> >>> Did you upgrade the version of Hyperkitty when you migrated to the >>> new host? >> >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple >> releases), so it's hyperkitty 1.1.4. >> >> I didn't upgrade anything with the move. > > I am not sure where does Debian packaged version store it's fulltext index, but > I am assuming the move somehow makes Hyperkitty not be able to read the > index. I think this is a known incompatibility between the Python 2.7 and Python 3 versions of Whoosh. From the tracebacks, the current HyperKitty is running under Python 2.7. If the prior server was running HyperKitty with Python 3, that would explain this. > Can you try removing and re-building the entire index? I don't know again > the right command for Django there, but the hyperkitty command you want > to run is called `rebuild_index`. For source package, something like: > > $ python manage.py rebuild_index > > Do note that this will take a lot of time if you have a big archive. If this is the incompatibility, rebuilding the index will fix 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, 2 months

[MM3-users] Re: How to remove global ban using API?

by Mark Sapiro

On 5/15/19 9:46 AM, Nathan Dixon wrote: > > I can create the ban fine by the following: > > from mailmanclient import Client > client = Client(URI,apiuser,apipass) > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") This is apparently a typo - missing ')' - in the re as you have it correct below. > However, I cannot seem to be able to remove it using the api: >>>> client.bans[0].delete() ... >>>> client.bans.remove(str(client.bans[0])) ... >>>> > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") All of the above work for me with both API 3.0 and 3.1 in a non-docker install of the current GitLab HEADs > And also, when I now try and go into the mailman-core docker image to use > the mailman.interfaces.bans, it will not let me see the global bans: > >>>> from mailman.interfaces.bans import IBanManager >>>> global_bans = IBanManager(None) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: ('Could not adapt', None, <InterfaceClass > mailman.interfaces.bans.IBanManager>) I don't see this either. > I have opened an issue in Gitlab for this as I feel it may be a bug related > to regex and global bans (there was a similar one for list banned > addresses): https://gitlab.com/mailman/mailman/issues/598 I also commented on the GitLab issue. I think this must be an issue with the docker images. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Search results for query "sapiro"