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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did this: (env) [mailman@localhost mailman-suite_project]$ pip install Django Requirement already satisfied: Django in /var/lib/mailman/env/lib/python3.6/site-packages Requirement already satisfied: pytz in /var/lib/mailman/env/lib/python3.6/site-packages (from Django) Does Django is already installed?? with python3.6 ??? El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: Hyperkitty download mbox

by Mark Sapiro

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: > > [2021-04-26 08:53:12 +0000] [28181] [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 > 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 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. Please try it and report. > I do still have the original mbox files for the imported lists which were on Mailman 2.1. The other thing is when downloading these mbox files I noticed they aren't the raw messages as we had in Mailman 2.1 but modified with headers stripped and email addresses modified. Is there any way to get the raw mbox back as in the option we had in Mailman 2.1? Not from HyperKitty. It doesn't store the raw messages anywhere, but if you enable the prototype archiver for a list, the raw messages will be stored in maildir format in var/archives/prototype/list(a)example.com/ for each enabled list. Messages imported with hyperkitty_import won't be there, but all posts to the list, at least since enabling the prototype archiver, will be. -- 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: Issues with international characters (replaced by ?) when mail is send as text/html

by Mark Sapiro

On 1/11/22 7:08 AM, Michal Soltys wrote: > Hi, > > I have noticed that any mail send with text/html, e.g. with following > headers: > > Content-Language: en-US-large > Content-Type: text/html; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > is slightly transformed by mailman3 - the body is put into its own part, > but all the international letters are replaced by question marks. The body being put in its own part is because of message decoration. In order to add the list's message header and/or footer the message is recast as multipart/mixed and the header and/or footer are added as separate MIME parts. See https://wiki.list.org/x/4030707 for an explanation of why this is done for non-plain text messages. > Having searched the list I tried: > > 1) adding following to mailman.cfg: > > [language.master] > description: English (USA) > charset: utf-8 > enabled: yes > > [language.en] > description: English (USA) utf8 > charset: utf-8 > enabled: yes I would have expected that to work. > 2) changing preferred language of a mailing list to something else via > shell, e.g.: > > m.preferred_language = 'pl' That should be m.preferred_language = getUtility(ILanguageManager).get('pl') > > 3) changed default_language to 'pl' in mailman.cfg I would have expected any of those things to work, but I can see that they don't. I'm looking into why. > 4) Ensured all relevant glibc locales are generated (not sure if that > matters though in this case) > > > None of this seems to have any positive result - all mails, whether > under 'pl' or 'en' setting still get all non-ascii chars replaced with > question marks (in html case, probably(?) in any case where it becomes > multipart). > > Any ideas what to do so html mails are passed without filtering out > their characters ? Do I have to recreate all mailing lists under new > [language.en/master] settings ? No, this is a bug. It has to do with message decoration (adding of headers and footers). You can probably avoid this issue by setting the list's filter_content and convert_html_to_plaintext to True. I am looking at why this occurs and fixing it. -- 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

[MM3-users] Re: Any good ideas on how to troubleshoot django allauth

by Mark Sapiro

David Krantz wrote: > > I found a solution that so far seems to work. The culprit was that the > machine had python-openssl and python3-openssl installed. After > removing them I have so far not seen any error. It turns out that unbeknown to me I had the same issue. I manage MM 3 installations at lists.mailman3.org and mail.python.org/mm3. I support django-allauth OAuth2 authentication using GitHub, GitLab, Google and Facebook on both. On lists.mailman3.org everything was working fine. On mail.python.org/mm3 all OAuth2 login attempts produced a 500 server error and a traceback in the mailman-web log similar to > ERROR 2017-04-23 18:51:39,501 base 3673 139978913507072 Internal Server Error: /mm3/accounts/google/login/callback/ > Traceback (most recent call last): > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.13-py2.7.egg/django/core/handlers/base.py", line 149, in get_response > response = self.process_exception_by_middleware(e, request) > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.13-py2.7.egg/django/core/handlers/base.py", line 147, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/django_allauth-0.27.0-py2.7.egg/allauth/socialaccount/providers/oauth2/views.py", line 62, in view > return self.dispatch(request, *args, **kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/django_allauth-0.27.0-py2.7.egg/allauth/socialaccount/providers/oauth2/views.py", line 120, in dispatch > access_token = client.get_access_token(request.GET['code']) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/django_allauth-0.27.0-py2.7.egg/allauth/socialaccount/providers/oauth2/client.py", line 74, in get_access_token > auth=auth) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/api.py", line 56, in request > return session.request(method=method, url=url, **kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/sessions.py", line 488, in request > resp = self.send(prep, **send_kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/sessions.py", line 609, in send > r = adapter.send(request, **kwargs) > File "/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages/requests/adapters.py", line 497, in send > raise SSLError(e, request=request) > SSLError: bad handshake: SysCallError(0, None) I only discovered this because I saw the ERROR entries in the log while looking for something else. In any case, it turned out that python-openssl was installed on mail.python.org and not on lists.mailman3.org. Removing it from mail.python.org allowed OAuth2 logins to work. We'll see if its removal broke something else that depended on it :( -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Mark Sapiro

On 9/21/20 10:49 AM, peterbw(a)gmail.com wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com > cc: listserv(a)lists.test.org; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com > cc: listserv(a)lists.test.org, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org, "Williams, Peter" <peters_real_address(a)example.com> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com cc: other_user(a)gmail.com; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com and other_user(a)gmail.com receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 6:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 21:25, Odhiambo Washington wrote: > > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> See > >> > >> > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > >> for mitigation. > > > > > > What is the danger of replacing my settings.py with this one, seeing as > it > > differs in a number of ways with mine? > > > If your's works, don't do it. The danger is the differences might be > significant and break things. Also, that one is for HyperKitty only and > doesn't include Postorius settings. > So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: Internal Server Error: /hyperkitty/list/my@lists.domain.eu/pop-threads

by Mark Sapiro

On 2/21/21 3:09 AM, Marco Marinello wrote: > Dear all, > > I've setup my own instance of Hyperkitty working as archiver of a Mailman 3 server. > It works fine but, sometimes, I get an email of a Django error: > > Internal Server Error: /hyperkitty/list/my(a)lists.domain.eu/pop-threads > > KeyError at /hyperkitty/list/my(a)lists.domain.eu/pop-threads > 'file' The above is not the issue. It results from Django trying to look up a log file in the LOGGING configuration. > Request Method: GET > Django Version: 2.2.12 > Python Executable: /usr/bin/python3 > Python Version: 3.7.3 > Traceback: > > File "/usr/local/lib/python3.7/dist-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/local/lib/python3.7/dist-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/local/lib/python3.7/dist-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/local/lib/python3.7/dist-packages/hyperkitty/lib/view_helpers.py" in inner > 129. if not is_mlist_authorized(request, mlist): > > File "/usr/local/lib/python3.7/dist-packages/hyperkitty/lib/view_helpers.py" in is_mlist_authorized > 146. if mlist.list_id in get_subscriptions(request.user): > > File "/usr/local/lib/python3.7/dist-packages/django_mailman3/lib/mailman.py" in get_subscriptions > 130. _get_value, 60, version=2) # 1 minute > > File "/usr/local/lib/python3.7/dist-packages/django/core/cache/backends/base.py" in get_or_set > 167. default = default() > > File "/usr/local/lib/python3.7/dist-packages/django_mailman3/lib/mailman.py" in _get_value > 122. for member in mm_user.subscriptions > > File "/usr/local/lib/python3.7/dist-packages/mailmanclient/restobjects/user.py" in subscriptions > 66. 'members/find', data={'subscriber': address}) > > File "/usr/local/lib/python3.7/dist-packages/mailmanclient/restbase/connection.py" in call > 112. error_msg, response, None) > > During handling of the above exception (HTTP Error 500: <html> > <head> > <title>Internal Server Error</title> > </head> > <body> > <h1><p>Internal Server Error</p></h1> > > </body> > </html> What's happening is HyperKitty is trying to determine if the request comes from a list member, and that throws an exception resulting in the 500. What's in Mailman core's mailman.log? Is Mailman core's REST API even accessible from this HyperKitty instance. If not, you can't support private archives and will probably have other issues? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mark Sapiro

On 4/13/23 07:25, Mohsen Masoudfar wrote: > I am observing the following error message in the logs for one specific list: > > = = = > relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) > = = = This is non-compliant. Various parts of RFC6376, e.g. sections 5.6 and 6.1 clearly anticipate that a message can contain multiple DKIM-Signature: headers. > As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: Is email-smtp.us-east-1.amazonaws.com the outgoing MTA for Mailman. I.e the value reported by `mailman conf -k smtp_host` or perhaps smtp_host is a local MTA which is configured to relay via email-smtp.us-east-1.amazonaws.com? In what log is that message? Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. > > = = = > To distribute messages with valid DKIM signatures, I set > remove_dkim_headers: yes > in /etc/mailman3/mailman.cf > = = = > > Here are my questions: > 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. This setting will remove all DKIM headers from the message as Mailman receives it. Then, it depends on how and how many DKIM signatures are added to the outgoing mail. > 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? No, there is no such option. The fact that this happens for only one list is very strange. I would need more information to understand why. Do these messages get queued in Mailman's retry queue? If so, if you examine one such message with `mailman qfile`, what are the complete headers from that message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: One-click unsubscribe?

by Mark Sapiro

On 2/4/25 20:24, Jered Floyd wrote: > > I'm having a lot of problems with GMail delivery due to lack of "one-click unsubscribe" -- however that is quantified, which is not clear. See the footer of this message which contains To unsubscribe send an email to mailman-users-leave(a)mailman3.org This is produced by To unsubscribe send an email to ${short_listname}-leave@${domain} in the template which is also in the default template. This seems sufficient for Google, as I don't see mail bounced for this reason. You might try adding a link to Postorius. You can't really link to an immediate unsubscribe as that requires the user be logged in (and the user may not even have an account) and it also required POST data, but for Mailman >= 3.3.10, you could add To unsubscribe send an email to ${short_listname}-leave@${domain} or go to $mailinglist_url This requires the domain have a base_url set. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> and this is not yet exposed in Postorius. See https://gitlab.com/mailman/postorius/-/issues/594 > In particular, there is an issue with the fact that Google ignores dots in email addresses. So I have many (MANY!) subscribers who try to use the List-Unsubscribe header target, but because they are subscribed as "idiotsubscriber(a)gmail.com" rather than "idiot.subscriber(a)gmail.com" (which they have since changed their sender to) they get a reject that they are not subscribed. These people are also far too unobservant to read the footer of every message that reads "You are subscribed as idiotsubscriber(a)gmail.com". > > Is there any way to provide personalized List-Unsubscribe header links, or have Mailman ignore dots in gmail.com addresses... or... anything? I'm finding reported spam percentages in the Google Postmaster Dashboard exceeding 0.1%, which causes massive delivery blocking to GMail-based subscribers. The List-Unsubscribe: header is added in the handler pipeline by mailman/handlers/rfc_2369.py. At his point in the process the message is still generic so the header can't be personalized. The mailman/handlers/decorate.py handler can add personalized content so could modify the List-Unsubscribe: header to add the recipient's email address except at least at present this won't work because emails to listname-leave or listname-request with a leave or unsubscribe command currently only look at the sender of the email for the address to unsubscribe. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 4 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them: [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 Should I run any command to activate the CACHE dir? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

Search results for query "sapiro"