• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

Recent content by Jan

  1. J

    Issue mailman3 web-interface: Link missing in mail, 404 when clicking "manage list" in plesk

    Hei, thanks for your message. To be more specific, I try to outline my view on <IfModule mod_proxy_uwsgi.c>. Trivially, there are two possibilities: The module is not loaded. Then postorious cannot be served and links result in http-404 This was the situation on my machine. I did not disable...
  2. J

    Resolved Mailman3: Backup-Restore triggers welcome mail and takes a long time

    Thanks! I'm going to check it next time when restoring a backup. ... hoping that it might take some years before needing to so ;-). Regards, Jan
  3. J

    Issue mailman3 web-interface: Link missing in mail, 404 when clicking "manage list" in plesk

    Hi @Mikhail_S., thanks for your answer. Regarding: I was referring to <IfModule mod_proxy_uwsgi.c> - Sorry for the confusion. IMHO this directive does not make sense. Effectively, it causes the server to answer calls to lists... with http-404 instead of http-500. This was misleading for me...
  4. J

    Issue mailman3: host and web-host not aligned with custom domain name

    Is: In the mailman3-configuration example.com / localhost is encoded at various places: /etc/mailman3/mailman.cfg: site_owner: /etc/mailman3/mailman-web.py: EMAILNAME postorious / django3 Web-Host List (https://<domain>/mailman3/admin/sites/site/): example.com Should: 1. and 2. should be...
  5. J

    Issue mailman3 web-interface: Link missing in mail, 404 when clicking "manage list" in plesk

    Edit: To be more specific: Apparently, apache2 is serving the hosts lists.luehr.tech and generating a http-404 /etc/apache2/plesk.conf.d/server.conf is the only apache2-configuration defining a vhost for lists.* - it looks like this: Listen 127.0.0.1:7082 http <VirtualHost 127.0.0.1:7080...
  6. J

    Issue mailman3 web-interface: Link missing in mail, 404 when clicking "manage list" in plesk

    Thanks for your feedback. Regarding 1) I don't recall any configuratiuon changes to this server. The server was basically a Debian 12 clean-install running a backup restore of a Debian 10 host. I didn't do anything else. I could if all configuration files are generated correctly - esp. w.r.t...
  7. J

    Issue apache2 proxy target - wrong ip-address

    Updated: Your idea made the server running, again. Yet, it - IMHO - it is a bug in plesk that restoring the backup resulted in a broken webserver-configuration.
  8. J

    Issue mailman3 web-interface: Link missing in mail, 404 when clicking "manage list" in plesk

    Hi, I'm using mailman3 on plesk and noticed two issues regarding the web-ui When opening the overview of all mailing-lists for a subscription, plesk has a "Manage the list" button for each list in the table. Clicking that button opens a new browser-window to - for example -...
  9. J

    Resolved Mailman3: Backup-Restore triggers welcome mail and takes a long time

    Hi, I've restored a backup from plesk. The backup was restored on a new server to upgrade to Debian 12. Restoring the backup, I noticed: It takes a long time to restore a backup. During that time, neither RAM nor all CPU cores were used. Watching ps, I noticed at a couple of processes were...
  10. J

    Question The future of mailing list management?

    Hi, many thanks for integrating mailman3 into plesk. I migrated the old data via plesk / backup-restore All lists and subscribe were apparently migrated by doing so. Only a few problems remain. I think it is better to address any backup/restore problems in a dedicated thread. Regards, Jan
  11. J

    Issue apache2 proxy target - wrong ip-address

    Hi, thanks, that sounds reasonable. Do you know where I can change the settings? Thanks, Jan
  12. J

    Issue apache2 proxy target - wrong ip-address

    Hi folks, I just went to Debian 12 (formerly Debian 10) by restoring a plesk update in my new server. It appears like there's a problem with sites proxying to apache2. This results in http-500 for end-users nginx logs jluehr.de, request: "GET /favicon.ico HTTP/2.0", upstream...
  13. J

    Question The future of mailing list management?

    Hello, many thanks for including mailman3 in Plesk! I haven't had the time to check the support, yet, but I'm thinking about doing so in the next weeks. Some questions remain neverletheless. What is a good strategy to migrate a Debian 10 server (including mailman2) to Debian 12 with mailman 3...
  14. J

    Question The future of mailing list management?

    @AYamshanov Thanks for the heads-up!
  15. J

    Question The future of mailing list management?

    Hei, thanks for your help. One remark: Well, I don't think so - there's been a swing towards distribution independent packaging based on pip, docker, snap (mailman is not using snap, though). IIRC, Pip is recommended for deploying mailman3 these days. Running a virtual env is probably...
Back
Top