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

[MM3-users] Re: Cron of Mailman notify is not working

by Mark Sapiro

On 1/28/20 3:03 AM, Shashikanth Komandoor wrote: > Hello, > > With your help, I was able to setup mailman 3.3 on my RHEL 7.5 > machine and running well and good. > > For daily notification I have added the below line in the crontab: > > 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify > > But this cron job is not working while I was able to run the same > command manually at my CLI. Into exactly what crontab did you put it? That is the correct line if you put it in the mailman user's crontab, but if you put it in a system crontag, e.g./etc/cron.d/mailman, it needs a 'user_name' argument between the date/time fields and the commands. E.g., 00 08 * * * mailman /var/lib/mailman/venv3/bin/mailman notify although the Mailman user may not be 'mailman' in your case. You should see some errors from cron in /var/log/syslog at 08:00 that would give you a hint. -- 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: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/23/20 7:02 AM, Brian Carpenter wrote: > On 9/23/20 7:33 AM, r.woithe(a)callassoftware.com wrote: >> Thank u for the hint ! >> The only one is that Ubuntu uses uWSGI and not gunicorn. >> I set the para socket-timeout = XXX. >> I hope thats the right parameter. >> _________________________________________ > > I think Mailman 3 core still has its own gunicorn process that it runs. > Brian is correct. The REST API does not use the web server and uWSGI is not involved. Since Mailman core 3.3.0, the REST API is served by Gunicorn processes that have nothing to do with the web server. The time limit for these processes needs to be set as described at <https://wiki.list.org/x/17892072>. Prior to 3.3.0, the REST API used the standard library wsgiref module which doesn't have timeouts. Since you said you have Mailman core 3.2.2, this may not be a REST timeout at all. -- 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: MIMEDefang to fix footers

by Mark Sapiro

On 11/13/20 9:51 AM, Ryan Morash wrote: > Does anyone know how to use MIMEDefang to fix the footer as attachment issue when using Mailman3? I've seen several guides/scripts referring to its use with Mailman2, but I'm unsure of how they would match with Mailman 3. I don't use MIMEDefang and don't specifically recommend it, but I have looked at <https://stuff.mit.edu/~jik/software/mailman_mimedefang/>, and it seems that the only Mailman specific things involved in the installation and configuration of this script are the addition of the "MAILMAN_MIMEDEFANG" lines as the first and last lines of the footer template. The only thing Mailman 3 specific in that is how to edit the footer template. This can be done on a per-list basis via Postorius since 1.2.0 or more directly in Mailman core by setting URIs, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or by creating templates in Mailman's var/templates directory, see <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…>. -- 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: mailman3-web language preference and translation settings

by Mark Sapiro

On 12/6/23 15:54, Nils wrote: > Thanks for your help, Mark. I've already tried that and it gave me this > message: > > # sudo -u www-data python3 /usr/bin/django-admin compilemessages > --pythonpath /usr/share/mailman3-web --settings settings > CommandError: This script should be run from the Django Git checkout or > your project or app tree, or with the settings module specified. > > I'm working on ubuntu and I don't have (venv)$ The other commands (migrate, collectstatic and compress) worked fine. Kind regards I don't know why this fails like that, particularly since the same thing works for migrate, collectstatic and compress. The only thing I can think of is you may need to cd to the directory containing django/ django_mailman3/ postorius/ and /hyperkitty before doing the above. This may be something like /usr/lib/python3.x/site-packages. If that doesn't work, since I think you are using the Debian/Ubuntu package, I suggest you try Debian for 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: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/18/20 4:15 AM, tlhackque via Mailman-users wrote: >> > I considered including the regex in each message, but that seemed > redundant - and potentially long. Thus the pointer. Perhaps number the > rules for each list, and use that index? The ROWID would seem to be a > candidate for the number. The number would be the `position` value from the headermatch table for the matched rule, but that's unreliable as the rules can be reordered (or the particular rule even deleted) between the rule being applied to a message and subsequently looking for the rule. ... > I may have some details wrong - I found mm3 not ready for my needs and > am thus out of date - but I hope the high level approach that I outlined > is useful. It seems to me that this is a great deal of additional implementation to solve a non-existent problem. -- 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: MM2 to MM3 Archives Loading

by Mark Sapiro

On 11/22/24 13:46, Joshua Bushe wrote: > Both "Hide Inactive" and "Hide Private" are unchecked. I can view the lists without any issues, but when I click on a specific list, I see three loading icons. On the left side, there's an "All Threads" option, which lets me view all the archives for the list. > > My question is: why don’t the list appear in the "list overview"? I'm still confused. You say "I can view the lists without any issues", but then you say 'why don’t the list appear in the "list overview"?' By "list overview" I thought you meant a page like https://lists.mailman3.org/archives/, but now I think you see your lists on that page and the page you call "list overview" is one like https://lists.mailman3.org/archives/list/dummy@mailman3.org/. If your question is why don't you see a list of threads on that page, it only shows threads with posts in the last 30 days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 12/31/24 06:07, monochromec via Mailman-users wrote: > Further RCA reveals the fact that the archiver runner tries to archive the same message over and over again - hence the overhead during pipeline processing. The total # of attempts reaches well into five digits for a single message. This is not directly related to the pipeline runner issues but they may have the same underlying cause. All the pipeline runner does is put the message in the archive queue. It's the archive runner that is doing all these retries. However, the pipeline runner in processing the rfc_2369.py handler is also communicating with hyperkitty to get the values for the List-Archive: and Archived-At: headers. You need to focus on the communication between mailman_hyperkitty and HyperKitty. If there are significant delays there, it could explain your pipeline runner issue. Btw, I see https://gitlab.com/mailman/mailman/-/issues/1189 is also from you. I wondered at the time why you were trying to increase the number of pipeline runners which is not something that would normally be required. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: Linking to a forum thread from a (news) website.

by Mark Sapiro

On 9/25/19 2:29 AM, Paul Arenson wrote: > SOLUTION > I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. ... > QUESTION > Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? Re: has nothing to do with it. Replies are not threaded by subject. Replies are threaded by In-Reply-To: and References: headers in the reply. These headers are generated by the sending MUA (mail client) when replying to a message. If you send a 'new' message without those headers, it will be a new thread regardless of whether or not the Subject: matches with or without the Re:. Also, there are broken MUAs that don't properly generate In-Reply-To: and References: headers and replies from these MUAs will never be properly threaded. -- 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: Cannot start lmtp runner due to error while attempting to bind on address ('127.0.0.1', 8024): address already in use

by Mark Sapiro

On 12/2/19 5:04 AM, actionmystique(a)gmail.com wrote: > > Of course the port is already in use: it is used by dovecot. > ``` > tcp6 0 0 ::1:8024 :::* LISTEN 0 1317360 129620/dovecot > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 0 1316324 129620/dovecot > ``` > I must be missing something. What is Dovecot listening for on the lmtp port? If this is Postfix communicating with Dovecot as the LDA or for address verification and using TCP port 8024, you have at least two choices. You can have Postfix/Dovecot communicate via a unix socket instead or you can configure Mailman to use a different port. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> which says in part: lmtp_port is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using 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

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/30/24 10:46, andrea.janna.unipd(a)gmail.com wrote: > Same issue at my site. > I'm using mailman3 3.3.8 shipped with Debian 12. Then your first line of support should be Debian. See <https://wiki.list.org/x/12812344> > To debug the problem I stopped apache, cron, postfix and mailman3-web services. > But I still get the mariadb aborted connection warnings every 5 minutes. The only thing that runs every 5 minutes is `mailman gatenews`. The issue may be with that. You could try running it manually via ``` _MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews ``` ... > The regular mailman log doesn't show anything and I'm not sure about how to enable an appropriate debug log for mailman. Mailman has a number of virtual logs, most of which are written to the file mailman.log. You can enable debug level for those with ``` [logging.template] level:debug ``` See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for more info on logging. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Search results for query "sapiro"