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

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

by Mark Sapiro

On 6/2/21 12:48 AM, klillipuu(a)gmail.com wrote: > Hello All! > > I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. > So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). > I also mention, that hyperkitty is a pretty old version - 1.1.4. > The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. > Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? It would be good to upgrade. Current HyperKitty/Postorius/Django is Python3 which will remove your dependency on Python 2.7. Also, there have been many performance improvements in more recent versions which may solve your issue. Your gateway timeout issue is a uwsgi time limit. You can increase that in your uwsgi configuration. > Extra information: > * I have also noticed some memory violation issues which has caused by uwsgi. > * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Are these coincident with the gateway timeouts or do they occur at different times? -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/14/24 08:42, jkoral(a)luc.edu wrote: > joetest(a)listservnew.luc.edu is the list, but in postfix_lmtp, it is showing up as joetest(a)luc.edu. Where can I change that? I tried changing the domain and site, but it still has not changed. The list has a mail_host attribute which is set when the list is created. Presumably, you created the list as `joetest(a)luc.edu`. You have to change the mail_host attribute of the list, but it may be easier to just delete it and create a new joetest(a)listservnew.luc.edu list. Then you can ignore everything below. To change the mail_host for the list you can do a database query or use `mailman shell`. The database query is ``` UPDATE mailinglist SET mail_host = 'listservnew.luc.edu' where list_name = 'joetest'; ``` The `mailman shell interaction is ``` $ mailman shell -l joetest(a)luc.edu 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(a)example.com mailing list >>> m.mail_host = 'listservnew.luc.edu' >>> commit() ``` If you do either of the above to change the mail host, you probably need to do `mailman aliases` to regenerate the files for Postfix. -- 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: new list not working

by Mark Sapiro

On 3/9/23 15:49, Christian via Mailman-users wrote: > Mail.log > > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from > box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: > client=box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: > header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; > from=<christian(a)naturalintelligence.us> > to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP > helo=<box.ecovillage.cc> > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: > message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: > from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from > box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: > to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces(a)lists.ccalternatives.org? Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Moving existing lists to a new domain

by Mark Sapiro

On 9/18/24 10:13, Jeremy Stanley wrote: > > Since all the lists for the given domain will be moving to the same > unused new domain on the existing server, and can move at the same > time, I suppose this could be done through (offline if necessary) > backend database update queries. Yes. For the mailing list, the only changes needed are to the mailinglist table; A query like ``` UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = 'old_domain'; ``` would do, but this leaves the question of list_id. According to RFC 2919, section 4, the list_id should not change, but this is problematic in that if it isn't changed, a Postorius URL like https://example.com/mailman3/lists/list_name@new.domain will retrieve the list, but https://example.com/mailman3/lists/list_name.new.domain will not work. It would need to be https://example.com/mailman3/lists/list_name.old.domain so to reduce confusion, it may be better to update the list_id values A query like the following after the above should do it ``` UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE mail_host = 'new_domain'; ``` For HyperKitty, similar changes need to be made to the hyperkitty_mailinglist table. The `name` column entries need to be changed from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column entries need to be changed from `listname.old.domain` to `listname.new.domain` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/28/20 10:20 AM, Shashikanth Komandoor wrote: > > I tried for the command to know if any entry in the "address" table for > which 'id' is not an integer. > > But unfortunately, I could not get any command or idea how to find that. > > But out of my extra talent, I tried the below commands which, I thought, > may print the records which contain a non integer id value. ... > select id,email from address where id NOT BETWEEN 1 AND 84203; > id | email > ----+-------(0 rows) > mailman=# select id,email from address where id NOT BETWEEN 1 AND 84202; > id | emai> -------+-----------------------------> 84203 | user(a)exampl.com > > *1 and 84203 are the minimum and maximum values of the id:* > > Please see the above outputs and suggest if anything possible or please let > me know the command what should I run to find a non integer id value. > The above looks qood to determine if there is a non-integer value. > I also doubt this error as if my REST API is contacting postgresql in a > delayed manner. If possible, can you say what optimal setting I can do at > Postgresql so that faster responses would be given to REST API. I'm out of ideas. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Docker-Setup: example.com in test mails

by Mark Sapiro

On 3/28/22 00:04, Bjoern Franke via Mailman-users wrote: > > Thanks for your reply. It seems the probes were triggered by some > rejected example.com mails and I have no idea where the example.com > mails are coming from. I think what you are seeing must be some kind of spam. If not if you could post the complete raw message of one of these probes or probe bounces, I'll look further. > Some users also reported they got some "unsubscribed due to bounces" > messages but the bounce.log contained only entries for them 7 days ago. And were they unsubscribed? In general, unsubscription does not occur until some time after bounces are recorded. At some point, bounce score reaches threshold and a probe is sent. The probe may not bounce for days if the bounce is some downstream timeout. When the probe bounce is received, the user's delivery is disabled by bounce. This starts a process where the user is sent a warning at intervals until a limit is reached and the user is finally removed. The default settings are: bounce_you_are_disabled_warnings = 3 bounce_you_are_disabled_warnings_interval = timedelta(days=7) which means the user is sent 3 warnings, one immediately, one after 7 days and one after 14 days until finally being unsubscribed after 21 days. An entry 7 days ago could be a bounce of a warning message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Mark Sapiro

On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > --------------------------------------------------------------------------- > First issue:Postfix v3.5.8 on RHEL 8. > The below is from journalctl -xe: > --------------------------------------------------------------------------- > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > directory > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > directory > > I manually created the var_dir: /opt/mailman3/mm/var directory > specified in the mailman.cfg file. > How do I find out how to populate the postfix_domains.db files, and > the postfix_lmtp.db file? The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. > --------------------------------------------------------------------------- > Second issue: Postgresql authentication. > PostgreSQL v10.23. > --------------------------------------------------------------------------- > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > same complex password in the mailman3 config file: > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 I don't think you should have two /mailman3 at the end the form is `postgresql://user:password@host:port/database_name` The default port is 5432. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Dropdown problem in postorius due to bootstrap

by Mark Sapiro

On 7/9/24 1:18 PM, Greg Newby wrote: > (My first post) > > As has been observed, the Ubuntu 24.04 LTS packaging for native Mailman3 > can be challenging. I've been solving all kinds of issues, and I'm writing > here about something I've so far been unable to solve. Are you using the Debian/Ubuntu packages? If so, this may be a Debian issue. See https://wiki.list.org/x/12812344 ... > I've dug deeply into this. The relevant <script> is bootstrap.min.js. > Postorius (via django) is using version 5.3.1 via package libjs-bootstrap5: > > ** This is what django is using: > /usr/share/bootstrap-html/js/bootstrap.bundle.min.js -- version 5.3.1, > linked to: > /usr/share/javascript/bootstrap5/js/bootstrap.bundle.min.js > > /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js The Gnu Mailman project's postorius ships with postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js version 5.1.3 ... > By temporarily replacing > /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js > I have tried moving back to 4.6.1 (from libjs-bootstrap4). I have also > retrieved the latest 5.3.1 from the CDN, which is slightly different but > doesn't change the error: > https://cdn.jsdelivr.net/npm/bootstrap@5.3.1/dist/js/bootstrap.bundle.min.js Try using the ones from https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/static/pos… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Moderation of posts via email is not working in mailman 3

by Shashikanth Komandoor

Thank you Mark Sapiro for your response. After going through the discussion at the link you provided, I understood as of now, it is not possible to moderate the posts through the mails in Mailman 3. But since the user is getting the "confirm" attachment to the mail, the users are getting confused. Is there any work around to achieve this? or Is there any way to remove that "confirm" attachment so that users would not get an idea of confirming via email? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 30, 2020 at 2:46 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/29/20 12:24 AM, Shashikanth Komandoor wrote: > > > > Is there any bug or limitation in mailman 3 or if I am doing > > any wrong at the server side? Please suggest. > > > > This is a known issue in Mailman 3. See > <https://gitlab.com/mailman/mailman/-/issues/169>. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 5 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: > I'm trying to set up mailman3 on two hosts, one of which runs core + > exim, the other runs postorius (&possibly hyperkitty). > > I have I think got core set up correctly, and postorius is sort of > usable, but anything in the web ui that talks to core ends up with a > white screen. > > I think what is happening is a postorius URL ends up with the core (or > perhaps no) hostname, and as there's nothing there to answer it fails. What are your Django settings for MAILMAN_REST_API_URL, MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with the [webservice] settings for hostname, port, use_https, admin_user and admin_pass in mailman.cfg in core and is the port open to the outside on the core machine? > I've checked the settings and I don't think I have misconfigured > postorius. Is it possible that the bad url is being passed from core to > postorius in some way and reused without changing the host? > > In the config at present, both hosts are visible to the browser, and > each host can communicate with the other. > > Any ideas on how to pin down the problem better? Do you see REST requests from the Postorius machine in core's mailman.log and access.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Search results for query "sapiro"