[Mailman-Users] Question about Mailman domain and OS X server set-up.
Hi Mark (Sapiro) and other members, While discussing some possible DNS set-up issues I might need to resolve on my server a certain IT professional mentioned to me that Mailman shouldn't be run using a virtual domain. I am not sure if this professional was referring to virtual domains in general or only those running on Mac OS X Server. Do you know if this is true ? Do you see any problems with Mailman running from a Virtual domain ? Let me make this a little clearer. I have a Mac server on a single IP address and host several domains. The primary domain name (the one returned when you do a search on my IP address) is domain1.com and the Mailman list is being run on domain2.com (one of several virtual domains hosted on the same server). Any Mac specialists on the list that know the answer to this question ? Thank you in advance, Joe -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Question about Mailman domain and OS X server set-up.
On Mar 28, 2011, at 1:31 AM, JRC Groups wrote: While discussing some possible DNS set-up issues I might need to resolve on my server a certain IT professional mentioned to me that Mailman shouldn't be run using a virtual domain. I am not sure if this professional was referring to virtual domains in general or only those running on Mac OS X Server. In general, there are absolutely no problems running Mailman on a machine that hosts multiple virtual domains. The machines at python.org do this today. While the official purpose of the machines is to serve the python.org domain and the mailing lists for this domain, there are lists for multiple other virtual domains that are also hosted there, and a single Mailman instance manages all those mailing lists just fine. There are some issues you need to be aware of with regards to using a single Mailman instance to handle mailing lists for multiple virtual domains, which are detailed in the FAQ wiki. But so long as you make sure that you don't ever try to create a mailing list by the same name in multiple different virtual domains that are handled by the same Mailman instance, there shouldn't be any major problems. However, the version of Mailman as shipped by Apple has some significant differences from the official version of Mailman as we provide for download from the list.org site (and mirrors). These issues are also covered in the FAQ Wiki, but the gist is that we cannot definitively provide answers for how the Apple-provided version of Mailman will work. Since they modified the code that is installed, if you want support for the Apple-provided version of Mailman, you would need to go to Apple for that. We can give you our best guess for how we think things should work in those kinds of situations, but that's about the best we can do. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] cannot add user or create mailing list
Although I have a few years of experience as a list administrator of lists hosted on other sites, so far I never managed a mailman server on my own. In our institute we manage small list via /etc/aliases :include:s Recently I decided to make an experiment, so I installed mailman 2.1.11 via the suse 11.3 distribution on my machine. I read carefully the PDF GNU Mailman Installation Manual release 2.1 by Barry Warsaw, and other stuff on the wiki, including those concerning sendmail (we are a sendmail site). I say experiment since I am testing it on my personal machine, although the target system will be one of the institute servers (in process of being upgraded). I thought to gain experience first in a simpler arrangement. -- I followed the manual except that at step 6 (6.3) I followed http://wiki.list.org/display/DOC/Integrating+Mailman+with+Sendmail+-+Method+2 and related links. The suse installation via yast2 installs mailman partly in /usr/lib/mailman, partly in /var/lib/mailman/ (and also /usr/share/man/man8 and /usr/share/doc/packages/mailman/), it also creates the user and group. It does not provide any automatic configuration for apache, so I did it manually (I actually like this better). I had to place in default-server.conf also this block Directory /usr/lib/mailman/cgi-bin AllowOverride None Options +ExecCGI -Includes Order allow,deny Allow from all /Directory in order to be able to execute the CGIs. I note that the startup script /etc/init.d/mailman gives a message Starting mailman (Warning: the Apache2 webinterface for Mailman has not been activated!) which seems to imply a flag missing in line APACHE_SERVER_FLAGS in /etc/sysconfig/apache2, but I have no documentation for it, and it seems that the site can be accessed ok (QUESTION 1) Any Suse user can confirm this is unnecessary ? -- Concerning sendmail, I followed the method 2 (WITHOUT mm_handler) because it seems to apply better to our institute arrangements. So I have a sudo wrapper script with the two lines /bin/cp /var/lib/mailman/data/aliases /etc/mail/mailman.aliases /usr/bin/newaliases a sendmail.cf with O AliasFile=/etc/mail/aliases,/etc/mail/mailman.aliases and the fake arrangement in mm_cfg.py MTA='Postfix' POSTFIX_ALIAS_CMD = '/usr/bin/sudo /usr/sbin/mailman.aliases' POSTFIX_STYLE_VIRTUAL_DOMAINS = [] I have verified the command /usr/lib/mailman/bin/genaliases works and touches the right files. I have also run /usr/lib/mailman/bin/newlist mailman to create the top list and it works (it said to have sent a mail, but actually it was just queued, and it was sent as soon as I started the qrunner from /etc/init.d I set my own e-mail as list owner, and set a password (incidentally the same test password used by /usr/lib/mailman/bin/mmsitepass) (QUESTION 2) I hope the fact I always use the same test password is not a problem -- At this point I entered the admin web page of such a list (for which I received the Your new mailing list message). It seems I can browse it OK. Then I wanted to subscribe myself to the list. If I do it via the Membership Management - Mass Subscription, and I enter my e-mail address in the form, I get no errors but nothing happens. If I try to subscribe via the mailman/listinfo/mailman page, I get instead an error you must supply a valid e-mail address (QUESTION 3) Why does that happen ? see also question 4 -- I tried also to create a new mailing list via the web interface (this requires supplying the site password as well) this gives me instead an error Unknown virtual host: sax.iasf-milano.inaf.it (QUESTION 4) This may have to do with our institute standard arrangement, and will apply also to the real arrangement on our target server. Unfortunately I cannot find the documentation for the keywords in mm_cfg.py so I am not sure what shall be tuned. This is the content of mm_cfg.py. The first 9-10 lines were added automatically by the suse yast installation, the rest was edited/added by me to suite our apache config and the sendmail method 2 DEFAULT_URL_PATTERN = 'http://%s/mailman/' DEFAULT_NNTP_HOST = 'poseidon.lambrate.inaf.it' DEFAULT_EMAIL_HOST = 'poseidon.lambrate.inaf.it' DEFAULT_URL_HOST = 'poseidon.lambrate.inaf.it' MTA = 'Postfix' DELIVERY_MODULE = 'SMTPDirect' SMTPHOST = 'localhost' SMTPPORT = '25' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #IMAGE_LOGOS = '/mailmanicons/' IMAGE_LOGOS = '/icons/' # changed lines above manually # inserted this stuff for sendmail POSTFIX_ALIAS_CMD = '/usr/bin/sudo /usr/sbin/mailman.aliases' I have to explain our configuration: - we have two domains. lambrate.inaf.it is the one where all A and PTR records are, and also a number of CNAMEs for various services. iasf-milano.inaf.it is a more formal domain alias, which contains just CNAMEs for the main
[Mailman-Users] GNU Mailman in the 2011 Google Summer of Code
Hi everyone, We're going to be participating in the Google Summer of Code again this year, but this time, under the Python Software Foundation's banner. Here's our wiki page for GSoC ideas, mentors, and students: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2011 and the PSF page with more details for signing up, etc. Application deadline for students is Friday, April 8, so please hurry! I believe student registration opened up today. Feel free contact us in mailman-develop...@python.org, or #mailman on freenode IRC. -Barry signature.asc Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Question about Mailman domain and OS X serverset-up.
JRC Groups wrote: While discussing some possible DNS set-up issues I might need to resolve on my server a certain IT professional mentioned to me that Mailman shouldn't be run using a virtual domain. I am not sure if this professional was referring to virtual domains in general or only those running on Mac OS X Server. Just a quick addendum to Brad's response. From the point of view of the mail server rather than Mailman, There should be full circle DNS. I.e., an rDNS lookup of the server's IP address should give a host/domain name and a lookup of that name should return an A record (not a CNAME) with the same IP. Also, when sending mail, the server should identify itself in HELO with the same name. These things should be true for any mail server regardless of Mailman. Now if a mailman list is in a virtual domain, the envelope sender of messages from that list will be the virtual domain. This is fine, but if the virtual domain publishes an SPF record, it needs to specify the server's name as a permitted sender. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
