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

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Mark Sapiro

On 5/6/20 10:54 AM, Thomas Drillich wrote: > Hello, > > I tried to setup exim4 + mailman3 but it seems to stuck at lmtp delivery of mailman3. > Could you give me a hint, to detect the reason of failure ? ... > # /etc/exim4/conf.d/transport/55_mm3_transport > mailman3_transport: > driver = smtp > protocol = lmtp > allow_localhost > hosts = localhost > port = MM3_LMTP_PORT > rcpt_include_affixes = true Have you defined MM3_LMTP_PORT and is it the same value as the lmtp_port: setting in the [mta] section of mailman.cfg - default 8024? And is Mailman core and particularly its lmtp runner running and is it listening on the relevant port? Is there more information about "all hosts for 'listen.td3.eu' have been failing for a long time" in exim's logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/3/21 1:06 AM, Kimmo L wrote: > Thanks for the quick replay! > If its not a big trouble, could you kindly give me some advice/guide how upgrade my Hyperkitty/Postorius/Django from python2 to python3. > I would be very grateful. It depends heavily on how Mailman was installed to begin with, but essentially you just upgrade the various components to the latest versions using pip. Some things you need to be aware of are at https://docs.mailman3.org/en/latest/upgrade-3.2.html > These segfaulting alerts appers the same time when i see "ERROR reincarnated worker Process-1:53 after death" entry in uwsgi-error.log. > So it seems that they are dependent on each other. It could very well be an out of memory issue and upgrading may solve 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, 11 months

[MM3-users] Re: "Unsubscribe all" button

by Mark Sapiro

On 10/20/22 17:32, Philippe B wrote: > Would it be possible to add a confirmation screen after you click on it? Like: WARNING! Clicking "Confirm" will empty the list of all its existing members, regardless of what was entered on the previous screen. That operation cannot be reversed. Are you absolutely sure that you want no one to be on your list anymore? There is a confirmation screen although it is not as strongly worded as you suggest. See https://gitlab.com/mailman/postorius/-/issues/545 for a discussion of this. There are screenshots there showing revised button labels and rearranging the cancel/remove buttons on the confirmation page. These changes have not been implemented as yet because I didn't think there was a clear direction. Please look at that issue and comment there. -- 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: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/18/23 11:19 AM, bryan.kartzman(a)yu.edu wrote: > And they do have the same thread_id as well: > > select a.id, b.starting_email_id, a.message_id_hash, b.thread_id > from hyperkitty_email a,hyperkitty_thread b > where a.message_id_hash = b.thread_id > and a.id = b.starting_email_id > and a.id in (1365,1366) ; > > id | starting_email_id | message_id_hash | thread_id > ------+-------------------+----------------------------------+---------------------------------- > 1365 | 1365 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 > 1366 | 1366 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 > (2 rows) This is interesting. There are two entries in the hyperkitty_email table for the same message. Are the other fields, particularly `content`, for these ids in the hyperkitty_email table the same? If so, I'd be inclined to ``` delete from hyperkitty_email where id = 1366; delete from hyperkitty_thread where starting_email_id = 1366; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Only Recent archive tab works after mailman upgrade

by Mark Sapiro

On 8/4/24 23:39, zoltan(a)circle-interactive.co.uk wrote: > Hi, > > since I upgraded mailman to 3.3.9 (python 3.11.2) > I have an odd issue on lists' archive page. > Apparently only the Recent tab works. > If I switch to Active or Popular I see the change in the url but page content does not refresh. > I can not see any errors in browser console and in logs so I am quite clueless how to debug further :( Mailman core has nothing to do with this. Did you upgrade HyperKitty, and if so, from what to what? See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/templates/hy… - I don't know why this wouldn't be working in your case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Setup Mailman 3 using Apache/Mod_WSGI

by Mark Sapiro

On 08/03/2017 07:16 PM, Stephen J. Turnbull wrote: > > On the other hand, you need to tell WSGI where > the Django project (mailman-suite_project?) lives. I use a different > syntax: > > WSGIDaemonProcess site python-path=/home/django/project user=django group=django display-name=django And on the apache/MM3/mod_wsgi site I support, I have WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman group=mailman python-path=/opt/mailman/mailman-bundler/venv/lib/python2.7/site-packages home=/opt/mailman/mailman-bundler/var I also have WSGIScriptAlias /mm3 /opt/mailman/mailman-bundler/bin/mailman-web.wsgi <Directory "/opt/mailman/mailman-bundler/bin"> <Files mailman-web.wsgi> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> Which is essentially what the OP has with the addition of WSGIProcessGroup mailman-web -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: change preferred language of list

by Mark Sapiro

On 6/20/19 3:38 PM, mailman3(a)malevil.cc wrote: > ok, thats good, but however, list and mailman are set to "de" but still the english template is used... There does seem to be an issue. I set the preferred_language of a list to 'de' and subscribed an address. The address was sent a confirmation request in German, but upon response, the subsequent "The results of your email commands" message and the list welcome message were in English. The "The results of your email commands" message was in English because it is built dynamically by the command runner and while the messages are i18n'd, there is as yet no German message catalog. However the list welcome message should have used the German template. This appears to be a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 12:05 PM, Brian Carpenter wrote: > On one of my mailman 3 servers, I am having a problem with Postfix > failing to deliver email to Mailman. I keep seeing this in the mail.log: > > status=deferred (connect to 127.0.0.1[127.0.0.1]:8024: Connection refused) > > What is causing this and how can I fix it? > Do you have lmtp_host: 127.0.0.1 lmtp_port: 8024 in the [mta] section of mailman.cfg? (these are the defaults) $ /opt/mailman/mm/bin/mailman conf|grep lmtp [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 Is Mailman's lmtp runner listening on port 8024? $ sudo netstat -lntp|grep python tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 1867/python tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 1199/python tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 1871/python Is there some firewall issue blocking access to the port even from localhost? -- 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: Moderation Action Changed After Import

by Mark Sapiro

On 2/12/21 11:26 AM, Brian Carpenter wrote: > I migrated a Mailman 2 list using import21 and the list's config.pck > into a Mailman 3 list. The list owner reported back that about 98% of > the list members had their moderation setting changed to Reject (with > notification). He said the previous moderation was the list's default > which was hold for moderation. Is such a thing possible with an import > job? Is this perhaps a bug that has been reported previously? > It seems you imported to an existing list with import21. This is probably not a good idea. Those members who were moderated members of the MM 2.1 list will have their moderation action set to Hold, Reject or Discard based on the 2.1 list setting. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: remove non members from a list

by Mark Sapiro

On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to remove all non members from a list. I know I can do it via > Postorius, but it has to be done one at a time. (you can delete ALL > suscribers but not all non members...) > > Anyone has a python recipe to do this? $ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> for nonmember in m.members.nonmembers: ... nonmember.unsubscribe() ... >>> commit() -- 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

Search results for query "sapiro"