Mailman and Xmail
To all, I'd like to apologize upfront because I'm a completely newbie with this and will be presumably be asking a lot of questions over the next couple of days.
Ok, so I'm trying to configure using MailMan with Xmail. I image that someone has done this before somewhere, so I would really prefer not to re-invent the wheel here. As much as possible, I'm going to try and limit the amount of Xmail specific issues I raise here, since this isn't the list for that.
Issue #1: I'm trying to set up email to be directed to email (the way it normally would using aliases). I've pretty much figured out how this might work from the Xmail side. But I'm having trouble while invoking the wrapper. That is, I'm not getting any response, feedback, etc that something is working (i.e. no emails, no changes to the log files, nada). I guess one question might be: is /usr/local/mailman/mail/mailman the proper way to invoke the wrapper? If not, what is? I know how one might do this for Sendmail, but not for Xmail.
The command line I'm trying currently, which doesn't work, is:
$ cat messagefile | /usr/local/mailman/mail/mailman action listwhere messagefile is an email message, action is a specific action (i.e. subscribe) and list is a specific list.
Issue #2: I know the big thing about mailman is that it has a great web interface, but we'd prefer for our users to use email commands, or a web interface that we would build (which would actually simply send email commands on to Mailman). We also would prefer not to run a web server on our mail server or create an NFS volume link on our currently Windows-based web server. Are there significant issues with not enabling the web aspects of Mailman? Is it possible to hide all references to the web interface from the administrative emails that are sent (i.e. subscriptions, unsubscriptions, etc).
Ok, that's it for now. If people have experience with both 1 & 2 meaning that we shouldn't use Mailman, what suggestions do people have? From my research, Mailman seems to be the most robust open source (or even non-open source) mailing list solution.
Thanks in advance for your help, Toby
Toby Reiter mailto:toby@breezing.com Breezing Internet Communications http://www.breezing.com 1106 West Main St phone:434.295.2050 Charlottesville, VA 22903 fax:603.843.6931
On Wed, 2003-04-30 at 10:26, Toby Reiter wrote:
Issue #1: I'm trying to set up email to be directed to email (the way it normally would using aliases). I've pretty much figured out how this might work from the Xmail side. But I'm having trouble while invoking the wrapper. That is, I'm not getting any response, feedback, etc that something is working (i.e. no emails, no changes to the log files, nada). I guess one question might be: is /usr/local/mailman/mail/mailman the proper way to invoke the wrapper? If not, what is? I know how one might do this for Sendmail, but not for Xmail.
The command line I'm trying currently, which doesn't work, is:
$ cat messagefile | /usr/local/mailman/mail/mailman action list
before doing this make sure you have su'ed as the user that xmail runs as. Also if you want Mailman to respond, make sure that you have mailmanctl running
I just tested it on a system running Mailman version 2.1.1 and postfix, su'ed as the user "mailman". It worked just fine.
where messagefile is an email message, action is a specific action (i.e. subscribe) and list is a specific list.
#1 is definitely an xmail issue. Here is a typical aliases section for a Mailman list called test3:
# STANZA START: test3 # CREATED: Fri Apr 11 16:19:46 2003 test3: "|/usr/local/mailman/mail/mailman post test3" test3-admin: "|/usr/local/mailman/mail/mailman admin test3" test3-bounces: "|/usr/local/mailman/mail/mailman bounces test3" test3-confirm: "|/usr/local/mailman/mail/mailman confirm test3" test3-join: "|/usr/local/mailman/mail/mailman join test3" test3-leave: "|/usr/local/mailman/mail/mailman leave test3" test3-owner: "|/usr/local/mailman/mail/mailman owner test3" test3-request: "|/usr/local/mailman/mail/mailman request test3" test3-subscribe: "|/usr/local/mailman/mail/mailman subscribe test3" test3-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe test3" # STANZA END: test3
Note:
Issue #2: I know the big thing about mailman is that it has a great web interface, but we'd prefer for our users to use email commands, or a web interface that we would build (which would actually simply send email commands on to Mailman). We also would prefer not to run a web server on our mail server or create an NFS volume link on our currently Windows-based web server. Are there significant issues with not enabling the web aspects of Mailman? Is it possible to hide all references to the web interface from the administrative emails that are sent (i.e. subscriptions, unsubscriptions, etc).
You will need/want to run the web-admin tool. If you are worried about it from a security stand point, then just run the web-interface locally or only allow specified ip's to access port 80.
Good Luck, and let us know what you needed to do to get Mailman running with Xmail.
Jon Carnes
participants (2)
-
Jon Carnes -
Toby Reiter