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

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by David Partain

> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: > > 1. Am I correct in assuming that I can just use my favorite editor > > (vi) to remove the offending characters from the file? > No. The file is a Python pickle and you can't edit it. You would need > to get the message and the metadata from the pickle (you could at least > view it with the `mailman qfile` command), edit the message and then > re-pickle the message and metadata. And, in my impatience, I tried it before receiving your response and now I seem to have done silliness in my database :( New error in mailman-web.log: AttributeError: 'NoneType' object has no attribute 'subject' Sigh. Stupid me. If you have suggestions on fixing that... Right now, my plan is simply to remove the first message in the queue (since I assume it'll be the "broken" one) and it'll just not be in the archive. Life's hard. Even if I unpack 'em to edit, I'll find mail in, for example, in base64, and I'm not going to fix the mail by decoding, editing, re-encoding, ... Nope. > > 3. Can I do something to make hyperkitty go through the spool? > > > > I don't know what you mean. Sorry I wasn't clear. I simply meant, "Is there a way to start hyperkitty going through the spool manually?" It sounds like, though, that I don't need to do that if it's going to happen that often anyway. Cheers, David

4 years, 4 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/22/21 7:29 PM, Mark Sapiro wrote: > On 12/22/21 6:20 PM, David Newman wrote: >> >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > This looks like a uwsgi issue as discussed at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > although that's with apache and not nginx so it may not be. If I'm reading the thread correctly, it's Apache workarounds to an underlying Debian issue, so I agree it may not apply with nginx. > > >> Adding a stanza for 'location /mailman/' to the nginx config above >> clears the 404 error, but Postorius returns "Page not found" with no >> entry in the web or MM3 logs, and a 200 OK in the Nginx logs. >> >> I think the URL is supposed to go to the list page in Postorius. How >> to configure this so that list owners and moderators get a valid URL >> for list management? > > > I'm not sure what the solution is in this case, but a workaround would > be to add > > url(r'^mailman/', include('postorius.urls')), > > to the urlpatterns list in urls.py. There are 260 files named 'urls.py' under /opt/mailman, mostly for socialaccount stuff. Where does that change go? All files? Or just this one: /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py Or somewhere else? Thanks again. dn

3 years, 6 months

[MM3-users] Re: Non-ascii characters missing from Pipermail archive txt and gz downloads

by Mark Dale

Hi Ruth, Apologies for the late response. I posted my message to the MM3 list in error and have since reposted it to the MM2 list. However, thank you for taking the trouble to reply. The problem lies outside the choice of editor as both files are being viewed in the same editor -- with one correct and the other not. Mark Sapiro has explained (on the MM2 list) what is causing the problem. Armed with that information I just have to now find a way .... Regards, Mark -------- Original Message -------- From: Ruth Ivimey-Cook [mailto:ruth@ivimey.org] Sent: Friday, April 9, 2021, 15:24 UTC To: mark(a)postmark.io, Mailman users Subject: [MM3-users] Non-ascii characters missing from Pipermail archive txt and gz downloads > Hi Mark > > I'm not sure, but I think the problems are to do with the program you are using to view the txt file. > > A modern mail reader understands the Content-type: header and will adjust its character processing accordingly, but a .txt file has no default character encoding, so any text editor will have to "use its best judgement". Some will default to utf-8, because that is compatible with 7-bit ASCII (NOT Latin1) while others will just put characters out and hope for the best (esentially leaving the result to the encoding of the font). > > In theory, a UTF-encoded text file can begin with the "BOM" marker, a sequence of characters which is supposed to indicate which variety of Unicode is in use, but this is rarely present, especially for UTF-8. > > Try looking at your text file with a UTF-8 capable text editor **and ensure that you tell the editor to use the UTF-8 encoding**. I expect it will look ok then. > > > Hope this helps, > > Ruth > > > On 09/04/2021 13:52, Mark Dale via Mailman-users wrote: >> Mailman 2.1.34 >> Debian 10 >> Postfix >> >> Hi >> >> I'm hoping someone can shine a light on character encoding issue I've encountered. >> >> A plain-text email with non-ascii characters in the body gets posted to the list. >> >> As per Mark Sapiro's guide I've captured the incoming message to file. >> >> - https://www.mail-archive.com/mailman-users@python.org/msg73469.html >> >> The message is received by Mailman with the non-ascii characters displaying correctly. >> >> The header of that message has: >> >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 >> Thunderbird/78.9.0 >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=utf-8 >> Content-Language: en-AU >> Content-Transfer-Encoding: 8bit >> >> In the list's mbox file and archive webpage, the message displays the non-ascii characters correctly. >> >> In the archive's downloaded .txt (and also .gz) file, the non-ascii characters are missing and displayed as "?". >> >> I've copied the message text in below, from both the correct one from the email and the erroneous .txt file. Hopefully they won't get scrambled up when I send this. >> >> Any advice on getting the non-ascii characters written into the archive .txt file would be gratefully received. >> >> Thanks, >> Mark >> >> >> === Message text as okay in mbox and as shown on the archive webpage === >> >> If one goes by the definition of veḷippaṭai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi āmpal does not conform to that definition since in the case of aruvi āmpal in Patiṟṟuppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression aṭai aṭuppu aṟiyā is already there to clarify that āmpal is a number and not a flower. Thus, aruvi simply provides information in addition to aṭai aṭuppu aṟiyā that āmpal is not a flower. The modern commentator Aruḷampalavaṉār also does not call it veḷippaṭai. >> >> === >> >> === Message text with missing characters in te archive's txt and gz downloads == >> >> If one goes by the definition of ve?ippa?ai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi ?mpal does not conform to that definition since in the case of aruvi ?mpal in Pati??uppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression a?ai a?uppu a?iy? is already there to clarify that ?mpal is a number and not a flower. Thus, aruvi simply provides information in addition to a?ai a?uppu a?iy? that ?mpal is not a flower. The modern commentator Aru?ampalava??r also does not call it ve?ippa?ai. >> >> === >> _______________________________________________ >> 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, 2 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/26/21 2:00 AM, Andrew Hodgson wrote: > >> Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [...] >Thanks for the traceback. The issue appears to be with folded headers that should either be unfolded before storing in HyperKitty's database or upon retrieval for this process. This is probably because of outlook.com folding Message-ID: headers. See >https://gitlab.com/mailman/mailman/-/issues/844 for one manifestation of this. >I think if you replace the >``` > msg["Message-ID"] = "<%s>" % self.message_id ``` line at 178 in /opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py >with >``` > msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') ``` it will avoid this issue. I tried this but get the same error, hope I did the modification correctly. [2021-04-30 19:56:31 +0000] [22104] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters Thanks. Andrew.

4 years, 2 months

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Abhilash Raj

Excerpts from Simon Liebold via Mailman-users's message of May 29, 2017 2:16 pm: > Am 28.05.2017 um 22:24 schrieb Mark Sapiro: >> 'Delete this message' is in the 'message' view. "Delete this thread" is >> in the 'thread' view. > > Now found the message view. Thanks. > >> HyperKitty requires Django<1.11. The comment in the requirements in >> setup.py implies this is only a django-haystack requirement >> >> "Django>=1.8", >> # Don't upgrade to 1.11 until django-haystack supports it: >> # https://github.com/django-haystack/django-haystack/pull/1499 >> "Django<1.11", >> >> but since it works for me with Django 1.10, you might want to try that. > > OK, I was still running an RC version. Silly me. > >> In particular, this looks like Django 1.11 bug >> <https://code.djangoproject.com/ticket/27975>. > > Which was closed in the release version that I initially upgraded to > (1.11.1). > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > You may have to do `python manage.py makemigrations` after adding a new INSTALLED_APPLICATIONS and before running `python manage.py migrate` Hope that helps! -- thanks, Abhilash Raj

8 years, 1 month

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gelpi Andrea

Il 23/04/20 19:02, Mark Sapiro ha scritto: > On 4/23/20 2:48 AM, Gelpi Andrea wrote: >> >> I saw the change in the file. >> >> As I'm not a programmer How can I test your fix? >> >> My system was installed via Debian 10 stable repository. >> >> I upgrade with testing repository postorius, django and mailmanclinet >> >> Postorius V 1.3.2 >> Django V. 2.2.12 >> Django filters V 2.1.0 >> Djanog mailman V 1.3.2 >> mailmanclient V 3.3.0 > > > I don't know where the Debian package puts things, but you have to find > the location of postorius/views/list.py. Something like > > locate views/list.py > > should find it. Then you need to download > <https://gitlab.com/mailman/postorius/-/merge_requests/500.diff> and > edit it to remove the first 15 lines so the first remaining line is the > > diff --git a/src/postorius/views/list.py b/src/postorius/views/list.py > > line. Then make a backup copy of postorius/views/list.py and run the command > > patch postorius/views/list.py path/to/500.diff > > where postorius/views/list.py is actually the full path to > postorius/views/list.py and 500.diff is the edited file you downloaded. > > Then restart uWSGI. If anything goes wrong, restore your backup copy of > postorius/views/list.py and restart uWSGI. > > I can confirm that the fix works. Thank You so much. -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalita' spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 2 months

[MM3-users] Re: Verification emails 'helo' rejected

by Thomas Ward

On 10/16/24 13:52, Mark Sapiro wrote: > On 10/14/24 12:42, Greg Newby via Mailman-users wrote: >> >> Here are the corresponding logfile entries from mailmanweb.log: >> smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 >> <mail>: >> Helo command rejected: need fully-qualified hostname')} >> >> and from mail.log: >> Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from >> localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need >> fully-qualified hostname; from=<root(a)lists.domain.tld> >> to=<root@localhost> >> proto=ESMTP helo=<mail> >> >> lists.domain.tld is the domain for Mailman3. I don't know why it's >> trying >> to send email from root@. > > > I think the mail.log entry is for the DSN for the failure. The issue > is the HELO/EHLO command. Try the following in your venv > ``` > (venv) ...:~$ python > Python 3... > Type "help", "copyright", "credits" or "license" for more information. > >>> import socket > >>> socket.getfqdn() > ``` > If that returns `localhost`, that's the issue. I think you can fix it > by putting a fully qualified domain name in /etc/hostname. > This is actually a postfix misconfiguration. By default, Postfix uses the `myhostname` variable to define your HELO/EHLO. In your /etc/postfix/main.cf change your `myhostname` to be an FQDN. If your mail server's FQDN is actually mail.example.com on the rDNS and forward DNS side, then set this in /etc/postfix/main.cf: myhostname = mail.example.com Then restart your Postfix. That will solve your issue. Thomas

8 months, 2 weeks

[MM3-users] Re: MM3+Python3.11

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/6/23 03:38, Odhiambo Washington wrote: > > Has MM3 been tested with Python3.11? > > Yes, but not with uWSGI which is not part of Mailman per se. > Oh. I can easily switch between uWSGI, Gunicorn, or mod_wsgi. > I updated a Debian VM to Python3.11, installed MM3 and migrated the > > configs. However, I am unable to get past the following error: > > > ... > > > Traceback (most recent call last): > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/wsgi.py", > line > > 10, in <module> > > from django.core.wsgi import get_wsgi_application > > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", > > line 1, in <module> > > from django.utils.version import get_version > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/django/utils/version.py", > > line 1, in <module> > > import datetime > > File "/usr/lib/python3.11/datetime.py", line 12, in <module> > > import math as _math > > ModuleNotFoundError: No module named 'math' > > unable to load app 0 (mountpoint='') (callable not found or import error) > > > This error says /usr/lib/python3.11/datetime.py can't import math. math > is part of the python 3.11 standard library > <https://docs.python.org/3/library/math.html>. There is something wrong > with your Python 3.11 installation. > So I will redo the venv by invoking the python binaries explicitly, in case I have conflicts. Thanks. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 months

[MM3-users] Re: Apple Mail encoding again

by tlhackque

On 21-Apr-22 13:09, Mark Sapiro wrote: > On 4/21/22 04:53, tlhackque via Mailman-users wrote: >> >> Note that MailMan is encapsulating a multipart/signed message in a >> multipart/mixed in order to append it's footer, and reports that it >> removed the signature part of the multipart/signed. This makes the >> signed message format invalid. So at least, MM3 needs to handle >> signed messages better: either include the signature or remove the >> signature headers (an unwrapping exercise to convert the message to >> unsigned)... Note that this can be recursive where a signed message >> contains a message/rfc822 part that contains a signed message, that.... > > This was an issue with Mailman's content filtering for the > mailmanusers(a)mailman3.org list. Pass types was: > > multipart > message/rfc822 > text > application/pgp-signature > > So the application/x-pkcs7-signature part was removed. I have just > updated Pass types to: > > multipart > message/rfc822 > text > application/pgp-signature > application/x-pkcs7-signature > > to not remove application/x-pkcs7-signature parts going forward. > That's what I expected to be behind the behavior. Thanks for fixing it on this list. But as I noted, it would be better if the application/*signature parts were automagically passed when a multipart/signed is present. Ideally those that correspond to the multipart/signed, but it's probably less work to allow them anywhere. I've seen variations of this misconfiguration on a number of lists, all of whose administrators had to learn by experience. Seems like a good case for Mailman becoming smart enough to do the right thing...

3 years, 2 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/27 22:58, Odhiambo Washington via Mailman-users wrote: > On Sat, Jul 27, 2024 at 11:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 7/27/24 13:05, Odhiambo Washington via Mailman-users wrote: >>> ASMTP works on the premise of "we can relay mail for you if we can >>> authenticate you with certain credentials" >>> Adding the IP to "hosts we can relay mail for" negates the need to >>> authenticate, IMHO. >>> So I am still waiting for how MM3 does ASMTP. Does it? >> >> If by ASMTP, you mean SMTP AUTH, Mailman does it if smtp_user: and >> smtp_pass: are provided in mailman.cfg. >> >> >> I agree that an authenticated user should be able to submit mail to be >> relayed. Just guessing here, but perhaps the issue is the OP is >> submitting to the deprecated port 465 instead of 587. >> > Port 465 is not quite depreciated. It's the decision of the Admin to decide > to listen on/and accept SMTP AUTH on which port. > On the servers I run, and based on Exim as the MTA, I accept SMTP AUTH On > ports 465, 587 and 2525 (this is meant to subvert some ISPs!). > But let's await Roland's response. The server runs power-mailinabox, which uses Postfix indeed. All my mail, and quite a few others' mail is sent from the using SMTP-Auth on port 465. Actually, this message is sent via that server too. So it's clear to me that MM3 is not authenticating for some reason. > >

11 months, 1 week

Search results for query "sapiro"