I've (supposedly) got mailman installed. and I have a list created. but I notice some oddities. 1) though I have NOWHERE required https - only https access works to the mailman web interface - http access just gets 404 pages. and I've looked though mm_cfg.py, mailman.conf in http and cant see anywhere that https would be required. also I set [email protected] as the mailing list email address. I setup a mailbox [email protected]. however emails to the box generate bounces from postfix: --snip-- This is the mail system at host ns9.cdbsystems.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <[email protected]> (expanded from <[email protected]>): unknown user: "macmenders" Reporting-MTA: dns; ns9.cdbsystems.com X-Postfix-Queue --snip--' for some reason postfix is mapping [email protected] to [email protected]. and there is infact no such user. any idea whats going on? thanks till
I've been trying to suss out the problems and have observed the following: my server name is ns9.cdbsystems.com mm_cfg.py contains: snip-- #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'ns9.cdbsystems.com' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'ns9.cdbsystems.com' #------------------------------------------------------------- # Required when setting any of its arguments. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) snip-- now my mailing list is macmenders and admin email is [email protected] accoding to the welcome emails I post to [email protected] but posting to this gives errors: snip-- The mail system <[email protected]> (expanded from <[email protected]>): unknown user: "macmenders" snip-- now I note that in /etc/mailman we have aliases and virtual-mailman and virtual-mailman contains: --snip-- # STANZA START: macmenders # CREATED: Tue Aug 4 15:50:03 2015 [email protected] macmenders [email protected] macmenders-admin [email protected] macmenders-bounces [email protected] macmenders-confirm [email protected] macmenders-join [email protected] macmenders-leave [email protected] macmenders-owner [email protected] macmenders-request [email protected] macmenders-subscribe [email protected] macmenders-unsubscribe # STANZA END: macmenders --snip-- when I look over in /var/lib/mailman/data: it also has a DIFFERENT virutal-mailman which is 0 byes (empty) and it also have a transport-mailman that contains --snip-- # STANZA START: macmenders # CREATED: Tue Aug 4 15:50:03 2015 [email protected] local [email protected] local [email protected] local [email protected] local [email protected] local [email protected] local [email protected] local [email protected] local [email protected] local [email protected] local # STANZA END: macmenders --snip-- now it sure seems like some of these must be wrong... also in the mailing list entry in ispconfig there is no defined email address for submissions - are we assuming its the list name @ domain of admin person??? no place to specify it within ispconfig any suggestions?
I note that the problem seems to be fixed - by altering postfix main.cf. I added the bold text at the end of alias_maps and now email to [email protected] goes to the proper place - and the mailling list gets the emails. --snip-- alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases --snip--
one more question - I put the mailling lists on one of my domains where I NEED Suexec (its running Wordpress). so when suexec is enabled, the mailman web interface fails. when suexec is disabled, mailman web interface works, wordpress does not LOL. Can I chmod 777 the mailman files and have suexec enabled and have all work? or will this cause other unanticipated problems? and if not which mailman folders need the 777 treatment? or should I create a subdomain (lists.mydomain.com) and have suexec disabled on it? if so now do I set that up soas not to conflict with mydomain.com which needes suexec?
This would cause all kind of problems and would allow everyne to take over your mailinglist system. Either that or let your users use the server hostname to access mailman.
Mailman is working fine now. to get the GUI to work right - and move everything to a subdomain so that I could have Suexe turned OFF - I had to modify mm_cfg.py in /etc/mailman to : #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'lists.mydomain.com' <- added lists to make subdomain controlled with ispconfig that has suexec OFF. BUT my urls were messed up in the gui and I could not navigate (or post properly) as the urls were not well formed. pages under lists.mydomain.com/mailman/ etcetc would have URLS in the page pointing to mydomain.com (without lists) etc etc.... turns out you have to: go to /usr/lib/mailman run bin/withlist -l -a -r fix_url to fix your existing lists. See the FAQ at <http://wiki.list.org/x/mIA9>. this corrects the lists AFTER the url change in mm_cfg.py so that the GUI works properly!