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

[MM3-users] Re: Error while running mailman-web compilemessages

by Prasanth Nair

Thanks Steve. On Wed, 20 Jul 2022 at 15:39, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/20/22 06:16, Prasanth Nair wrote: > > Hello, > > > > I'm in the process of installing a Mailman3 server. I get the following > > error messages when I run the command 'mailman-web compilemessages'. It > was > > working fine before and noticed this recently. Can someone suggest a > > solution to solve this issue, please? > > > This is a bug in the Arabic localization in django-extensions 3.2.0. See > https://github.com/django-extensions/django-extensions/issues/1744 > > If you aren't concerned about Arabic, just ignore those messages. > > > > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 1 month

[MM3-users] Re: mailman findmember runs very slow

by Wong, Wesley

Thanks for the fix, Mark. I tested the fix and query times are now under 2 s. wesley ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, July 13, 2024 4:36 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: mailman findmember runs very slow Wong, Wesley wrote: > Hi, I am noticing a performance issue with Mailman 3 when using the "mailman findmember" CLI command to search for email address or name. A fix has now been committed for the next release. See https://gitlab.com/mailman/mailman/-/merge_requests/1239<https://gitlab.com/mailman/mailman/-/merge_requests/1239> -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to wesley.wong(a)anderson.ucla.edu

1 year, 1 month

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 6/15/20 8:47 AM, rongxinliu(a)cs50.harvard.edu wrote: > > We tried deleting this mailing list and recreating a new one, but no luck. We also tried restarting mailman, and the issue persists. When looking at the mailman.log, messages sent to this problematic mailing list are accepted and archived successfully without a noticeable issue. > > In the smtp.log, also no errors are found except one line "Connection lost during _handle_client()", but this is true for all other mailing lists. Yes, that's normal. ... > However, the mailing list having issue will just stop at: > ....... > Jun 15 14:04:29 2020 (23) Connection lost during _handle_client() There are a couple of things. The post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… includes the log message: Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 This is strange as it says that Mailman is trying to connect to hostname `postfix`. Is this actually a legitimate host name on the Mailman server that Mailman can connect to? However, it doesn't seem that this is the issue as that name comes from the smtp_host setting in the [mta] section of the configuration and is global so if it were wrong, it would affect all lists. The fact that there is nothing after "Connection lost during _handle_client()" message means only that the message wasn't successfully delivered. A database issue seems unlikely. Set [logging.smtp] level: debug in mailman.cfg and see if the increased logging helps. It seems to me that the most likely issue is a list member whose address in an smtp RCPT TO command causes some issue with the MTA. Does the MTA actually see a connect and commands for the delivery attempt. I'm also confused by > The out-runner keeps creating new .pck and .bak files endlessly whenever an email gets sent to this mailing list. Mailman should create a .pck in the out queue. Then the out runner processes it and renames it as a .bak during processing for recovery purposes and when done processing removes the .bak. If in the process it encounters retryable errors for one or more recipients, it will remove the successful and perm failure recips from the metadata and queue the message in the retry queue. It should never be just requeueing the message in the out queue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: External MTA incoming mail: configuration

by Mark Sapiro

On 7/30/24 11:18, Roland Giesler via Mailman-users wrote: > > Now, lists.fast.za.net is the mailman server. The docs say that mailman > passes these on to the MTA. However, the MTA (postfix) on > box2.gtahardware.co.za has the following setting in it main.cf: The docs are badly worded. "but also will be passed to the MTA to identify the Mailman host." means passed manually in the MTA's configuration. > virtual_transport=lmtp:[127.0.0.1]:10025 You should not be using virtual_transport. You should be using transport_maps. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > If I reply to a signup confirmation email for example, the mail is > received and processed by box2.gtahardware.co.za, and it is not passed > on to the mailman server. It appears you have a situation where the MX for the Mailman domains is not the Mailman server. You need to configure the MTA on box2.gtahardware.co.za to relay Mailman's mail to the mailman server. You can to this by configuring that MTA to use transport_maps, etc as if it were the Mailman server. In order to get Mailman's generated files on the other server, you need to create a process to do that. When Mailman makes changes by adding or deleting lists or when it is started, it updates the postfix_lmtp and postfix_domains files and calls a command (normally postmap) to update the corresponding .db files. The command can be set by setting `postmap_command` in the `[postfix]` section in mailman.cfg. You can set this to a process which accepts a file name argument and then runs postmap on the file and rsyncs the file and it's .db to the other server. > So what is meant by "but also will be passed to the MTA to identify the > Mailman host" in the docs? As I said, that's badly worded it means 'passed manually to the MTA's config'. > If I change the config of the MTA (postfix) to be > "virtual_transport=lmtp:[lists.fast.za.net]:8024", I assume the incoming > mail will be forwarded, but how does postfix know that only the mailman > emails should be forwarded and not all the other mail that the server at > box2.gtahardware.co.za receives? Using transport_maps you can forward only list mail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: mailman import21 passwords

by Mark Sapiro

On 9/16/24 18:18, Sam Darwin via Mailman-users wrote: > >> inherently not secure > > The passwords were good enough for mailman2. If a mailman2 instance has been in production for 20 years and users aren't complaining about security, maybe it's not a show stopper There are regular complaints dating back at least to <https://bugs.launchpad.net/mailman/+bug/265179> about passwords mailed in the clear. > The point is to make the upgrade seamless. That means... being able to say that everyone gets to keep their user account and password. To be able to easily tell the users "Your account is still the same. Just log in. Change your password when you like." But is it "the same"? What about an import of two lists with members which are the same person, but with possibly separate email addresses and/or passwords? Do we really want to create multiple Django users, or let the user create one Django user with multiple addresses? > In the current context, passwords are associated with django accounts rather than mailman-core accounts. So this is about creating django users. > >> creating a django user is "expensive". "poor performance" > > I didn't follow what that means. What is expensive? What is poor performance? I pointed to <https://mail.python.org/archives/list/mailman-developers@python.org/thread/…> which discusses the performance issue as a reason for dropping the import of MM 2.1 passwords. > Creating new django accounts en masse would be a one-time operation. It doesn't matter if it's slow, or expensive, since it only happens once. While probably not typical, mail.python.org currently has (still) 209 MM 2.1 lists with 40261 unique member addresses. Creating 40261 Django users, even just one time would probably be painful. > And it would be optional. With the --django-accounts flag. Or another separate script. Then you can tell users "Your account is the same as before. A transparent upgrade. Just log in". I really don't understand why telling the user that she has an account and she can just log in with one of the N MM 2.1 passwords she had on the N MM 2.1 lists or get a reset email if she doesn't know or remember the password(s) is any easier for the user than telling her to go to ... and sign up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Message Personalization: embed User name in header/footer‏

by Asaf Ohayon

Thanks I edit the file mailman/core/var/templates/site/en/list:member:generic:footer.txt : _______________________________________________ Thanks $user_name $display_name mailing list $fqdn_listname https://mailman.sysbind.biz/lists/$fqdn_listname/ FOOTER All the variables are expanded correctly when i recieve the email, but $user_name remains unexpanded Is there any option to enable in order for $user_name to be available ? ‫בתאריך יום א׳, 6 במאי 2018 ב-17:27 מאת ‪Mark Sapiro‬‏ <‪mark(a)msapiro.net ‬‏>:‬ > On 5/6/18 7:16 AM, Asaf Ohayon wrote: > > Thanks, > > I understand those features are not available (yet) on Postorius > We're working on getting template editing in Postorius for release later > this month. > -- > 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/ -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

7 years, 4 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 1:28 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > <snip> > > However, those are from cron jobs and say nothing about the wsgi process > that runs the web UI and the hyperkitty api. > OK, I see uwsgi running in process table. PID USER TIME COMMAND 1 mail 0:13 uwsgi --ini uwsgi.ini 7 mail 1h11 uwsgi --ini uwsgi.ini There is only one uwsgi.ini file, and it is in the same directory as settings.py, settings_local.py and wsgi.py I'll see if I can find some logs for uwsgi that might provide some more insight. Thanks! -p > -- > 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 Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

2 years, 9 months

[MM3-users] Re: urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Mark Sapiro

On 1/18/22 4:20 AM, Axel Rau wrote: > > While selecting a list in the browser, I’m getting: > - - - > Traceback (most recent call last): > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch > return handler(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get > 'hyperkitty' in archivers and # noqa: W504 > File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ > self[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ > return self._get(key) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get > return self.rest_data[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} The above seems to be from Django's log. What's in Mailman core's mailman.log? > Question: Am I missing aliases in my nginx.conf? > I just have: > - - - > location / { > uwsgi_pass unix:///tmp/uwsgi.sock; > include /usr/local/etc/nginx/uwsgi_params; > } > > location /static { > alias /usr/local/mailman3/static; > } > > location /static/favicon.ico { > alias /usr/local/mailman3/static/postorius/img/favicon.ico; > } > - - - I don't use uwsgi so I'm not sure, but I think the above is OK. This list's host uses gunicorn and has location / { proxy_pass http://127.0.0.1:8000/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } The only locations beyond what you have above are for /robots.txt and /favicon.ico -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[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, 1 month

[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, 4 months

Search results for query "sapiro"