Mailman disappeared

Discussion in 'ISPConfig 3 Priority Support' started by Turgut Kalfaoglu, Apr 22, 2025.

  1. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    my mailman was working fine as http://lists.kalfaoglu.net/mailman/admin/listname
    However, all of a sudden it gives 404, and accessing the lists.kalfaoglu.net only redirects me to kalfaoglu.net, our home page.
    I checked the apache configs, and I have this in mailman.conf:
    # more mailman.conf
    <VirtualHost *:80>
    ServerName lists.kalfaoglu.net
    DocumentRoot /var/lib/mailman
    # Serve static files for Mailman
    Alias /pipermail/ /var/lib/mailman/archives/public/
    etc
    I do NOT have a 'web site' in ispconfig called lists.kalfaoglu.net - -- I thought I did! but I can't find it anywhere now.
    Any ideas how to resurrect the mailman and why did it disappear without me doing anything about it?
    Many thanks, -t
     
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    Did you update the system/ISPConfig? IIRC mailman is no longer supported on current ISPConfig systems due to incompatibility
     
  3. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    No I did not touch it for days.
     
  4. pyte

    pyte Well-Known Member HowtoForge Supporter

    What version of mailman are you using? Is the service running? Any usefull information in the logs?
     
  5. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    Yes mailman is running fine, just its web interface is not available right now. it seems the apache configuration somehow got screwed up..

    # systemctl status mailman.service
    ● mailman.service - GNU Mailman service
    Loaded: loaded (/etc/systemd/system/mailman.service; enabled; preset: disabled)
    Active: active (running) since Sat 2025-04-19 23:47:14 +03; 2 days ago
    Main PID: 3730 (python2.7)
    Tasks: 17 (limit: 483848)
    Memory: 424.5M
    CPU: 2min 17.171s
    CGroup: /system.slice/mailman.service
    ├─3730 /usr/local/python2/opt/python2.7/bin/python2.7 /usr/local/mailman/bin/mailmanctl start
    (etc)
    from mailman-config:
    print 'Mailman version: %s' % '2.1.39'
     
  6. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    I think I know what happened. A customer created a new site and they picked ipv4/ipv6 specific IP addresses. That tends to bomb my system.
    I'll try to find what the latest sites added were and edit their confs. How can I prevent clients/resellers from assigning IP addresses?
     
  7. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    FIXED - it was indeed that. I just need to stop customers from assigning an IP. even if one IP is assigned to a site, instead of '*' for ipv4 and blank for ipv6, it bombs the whole apache.
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, you should indeed disable it again so that customers can not select an IP anymore. That's why you can only choose * by default in ISPConfig.

    Disable the checkbox "HTTP NameVirtualHost" in the settings of all IP addresses and ensure that "Enable IP wildcard (*)" under System > Server config > Web is enabled.
     
    Turgut Kalfaoglu likes this.
  9. Turgut Kalfaoglu

    Turgut Kalfaoglu Member HowtoForge Supporter

    Wonderful, thank you very much.
     

Share This Page