mailman/exim problem
Exim's conf file attached as well as /etc/aliases due to possible relevance
already checked man mailman
[EMAIL PROTECTED]:~# man mailman
No manual entry for mailman
[EMAIL PROTECTED]:~#
[EMAIL PROTECTED]:~# apt-cache search mailman docs
[EMAIL PROTECTED]:~# apt-cache search mailman doc
[EMAIL PROTECTED]:~# apt-cache search mailman man
lg-issue91 - Issue 91 of the Linux Gazette.
mailman - Powerful, web-based mailing list manager
gforge-lists-mailman - Collaborative development tool - mailing-lists
(using Mailman)
[EMAIL PROTECTED]:~#
No other documentation available (good gods that's horrible in and of
itself)
So here goes it.
I have mailman 90% working. Automated, mailman originated messages (such
as subscribe request confirmations originating at the server (ala the
invite tool)), admin and user interface works. I can send and recieve
mail via local user accounts ('ve tested this thoroughly). My exim.conf
(attached) looks to be pretty tight, and aliases (attached) appears to
be set up correctly.
Replying to administrivia/relaying normal list traffic is still broke,
as is access to the public archive (which really doesn't exist due to
the fact messages aren't being sent). I've sent about 4 test messages
that have caused this:
Envelope-to: [EMAIL PROTECTED]
From: Cron Daemon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Cron [EMAIL PROTECTED] if [ -x /usr/lib/exim/exim3 -a
-f /etc/exim/exim.conf ]; then
+/usr/lib/exim/exim3 -q ; fi
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: HOME=/var/mail
X-Cron-Env: PATH=/usr/bin:/bin
X-Cron-Env: LOGNAME=mail
2004-01-03 13:08:01 1AcqVM-0007Rx-00 Neither the system_aliases director
nor the address_pipe transport set a uid
+for local delivery of |/var/lib/mailman/mail/mailman post listadmins
Now, in aliases, I tried putting root one space after the colon (in
between the pipe to |var/lib/blah/blah and listadmin*:) and wound up
with frozen messages. Reloading mailman (forcibly at times) has not
helped with either the frozen messages or the above situation. I can't
decide if it's Debian related or purely mailman related. Any help would
be greatly appreciated.
--
Joseph A. Nagy, Jr.
Student at Motlow State Community College
Political Activist Extrodinaire
The only fallacy is the inaction on our part to stave off the worst of
horrors, the stripping of personal freedom.
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system administrator.
# This file originally generated by eximconfig at Mon Dec 22 12:10:09 CST 2003
# See exim info section for details of the things that can be configured here.
# Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file.
# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word end. The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.
##
#MAIN CONFIGURATION SETTINGS #
##
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.
qualify_domain = joseph-a-nagy-jr.homelinux.org
# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.
# qualify_recipient =
# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not want
# to do any local deliveries, uncomment the following line, but do not supply
# any data for it. This sets local_domains to an empty string, which is not
# the same as not mentioning it at all. An empty string specifies that there
# are no local domains; not setting it at all causes the default value (the
# setting of qualify_recipient) to be used.
local_domains = localhost:joseph-a-nagy-jr.homelinux.org
# Allow mail addressed to our hostname, or to our IP address.
local_domains_include_host = true
local_domains_include_host_literals = true
# Domains we relay for; that is domains that aren't considered local but we
# accept mail for them.
#relay_domains =
# If this is uncommented, we accept and relay mail for all domains we are
# in the DNS as an MX for.
Re: mailman/exim problem
On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote
Exim's conf file attached as well as /etc/aliases due to possible relevance
already checked man mailman
[EMAIL PROTECTED]:~# man mailman
No manual entry for mailman
[EMAIL PROTECTED]:~#
[EMAIL PROTECTED]:~# apt-cache search mailman docs
[EMAIL PROTECTED]:~# apt-cache search mailman doc
[EMAIL PROTECTED]:~# apt-cache search mailman man
lg-issue91 - Issue 91 of the Linux Gazette.
mailman - Powerful, web-based mailing list manager
gforge-lists-mailman - Collaborative development tool - mailing-lists
(using Mailman) [EMAIL PROTECTED]:~#
No other documentation available (good gods that's horrible in and
of itself)
Try below for more info:
www.list.org
So here goes it.
I have mailman 90% working. Automated, mailman originated messages
(such as subscribe request confirmations originating at the server
(ala the invite tool)), admin and user interface works. I can send
and recieve mail via local user accounts ('ve tested this thoroughly)
. My exim.conf
(attached) looks to be pretty tight, and aliases (attached) appears
to be set up correctly.
I've always had problems when I didn't put
user = list
in my exim.conf file.
This line is located near your system_aliases stanza.
hth,
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
On Sat, Jan 03, 2004 at 01:27:49PM -0600, Joseph A. Nagy, Jr. wrote: Exim's conf file attached as well as /etc/aliases due to possible relevance already checked man mailman [EMAIL PROTECTED]:~# man mailman No manual entry for mailman [EMAIL PROTECTED]:~# snip No other documentation available (good gods that's horrible in and of itself) Plenty of documentation and it should be right there on your machine: [EMAIL PROTECTED]:~$ ls -al /usr/share/doc/mailman/ total 152 drwxr-xr-x6 root root 4096 Nov 15 12:59 . drwxr-xr-x 286 root root 8192 Dec 17 15:12 .. -rw-r--r--1 root root 2166 May 20 2002 ACKNOWLEDGMENTS -rw-r--r--1 root root 686 Sep 22 2000 BUGS -rw-r--r--1 root root 9640 Apr 18 2002 FAQ -rw-r--r--1 root root20067 Nov 16 2000 INSTALL -rw-r--r--1 root root16652 May 20 2002 NEWS.gz -rw-r--r--1 root root 6155 Jan 3 2001 README -rw-r--r--1 root root 871 Jan 3 2001 README.BSD -rw-r--r--1 root root 3046 Sep 18 2002 README.Debian -rw-r--r--1 root root 9469 Sep 18 2002 README.EXIM -rw-r--r--1 root root 1059 Mar 12 2001 README.LINUX -rw-r--r--1 root root 1742 Jul 19 2000 README.NETSCAPE -rw-r--r--1 root root 2167 Oct 20 2000 README.QMAIL.gz -rw-r--r--1 root root 1528 Mar 21 2000 README.SENDMAIL -rw-r--r--1 root root 3991 Nov 10 2000 TODO.gz -rw-r--r--1 root root 3552 Mar 3 2001 UPGRADING.gz -rw-r--r--1 root root 6676 Sep 18 2002 changelog.Debian.gz -rw-r--r--1 root root 1248 Sep 18 2002 copyright drwxr-xr-x3 root root 4096 Nov 14 10:19 examples drwxr-xr-x3 root root 4096 Nov 14 10:19 html drwxr-xr-x2 root root 4096 Nov 14 10:19 images drwxr-xr-x2 root root 4096 Nov 14 10:19 src Also, this link is a great help: http://www.exim.org/howto/mailman.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
mike wrote:
On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote
Exim's conf file attached as well as /etc/aliases due to possible relevance
already checked man mailman
[EMAIL PROTECTED]:~# man mailman
No manual entry for mailman
[EMAIL PROTECTED]:~#
[EMAIL PROTECTED]:~# apt-cache search mailman docs
[EMAIL PROTECTED]:~# apt-cache search mailman doc
[EMAIL PROTECTED]:~# apt-cache search mailman man
lg-issue91 - Issue 91 of the Linux Gazette.
mailman - Powerful, web-based mailing list manager
gforge-lists-mailman - Collaborative development tool - mailing-lists
(using Mailman) [EMAIL PROTECTED]:~#
No other documentation available (good gods that's horrible in and
of itself)
Try below for more info:
www.list.org
I guess horribley inadequate documentation is better then none at all.
So here goes it.
I have mailman 90% working. Automated, mailman originated messages
(such as subscribe request confirmations originating at the server
(ala the invite tool)), admin and user interface works. I can send
and recieve mail via local user accounts ('ve tested this thoroughly)
. My exim.conf
(attached) looks to be pretty tight, and aliases (attached) appears
to be set up correctly.
I've always had problems when I didn't put
user = list
in my exim.conf file.
This line is located near your system_aliases stanza.
hth,
Mike
I think that did the trick. I restarted both exim and mailman and I'm
starting to get stuff from the test (soon to go live) list that I created.
--
Joseph A. Nagy, Jr.
Student at Motlow State Community College
Political Activist Extrodinaire
The only fallacy is the inaction on our part to stave off the worst of
horrors, the stripping of personal freedom.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
On Sat, Jan 03, 2004 at 05:43:29PM -0600, Joseph A. Nagy, Jr. wrote: mike wrote: On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote Exim's conf file attached as well as /etc/aliases due to possible relevance already checked man mailman [EMAIL PROTECTED]:~# man mailman No manual entry for mailman [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# apt-cache search mailman docs [EMAIL PROTECTED]:~# apt-cache search mailman doc [EMAIL PROTECTED]:~# apt-cache search mailman man lg-issue91 - Issue 91 of the Linux Gazette. mailman - Powerful, web-based mailing list manager gforge-lists-mailman - Collaborative development tool - mailing-lists (using Mailman) [EMAIL PROTECTED]:~# No other documentation available (good gods that's horrible in and of itself) Try below for more info: www.list.org I guess horribley inadequate documentation is better then none at all. What are you talking about? It is well documented! It does not get any better than this: http://www.exim.org/howto/mailman.html Also, did you see my other post? Look at /usr/share/doc/mailman It should be right there in front of you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman/exim problem
Andy Firman wrote: On Sat, Jan 03, 2004 at 05:43:29PM -0600, Joseph A. Nagy, Jr. wrote: mike wrote: On Sat, 03 Jan 2004 13:27:49 -0600, Joseph A. Nagy, Jr. wrote Exim's conf file attached as well as /etc/aliases due to possible relevance already checked man mailman [EMAIL PROTECTED]:~# man mailman No manual entry for mailman [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# apt-cache search mailman docs [EMAIL PROTECTED]:~# apt-cache search mailman doc [EMAIL PROTECTED]:~# apt-cache search mailman man lg-issue91 - Issue 91 of the Linux Gazette. mailman - Powerful, web-based mailing list manager gforge-lists-mailman - Collaborative development tool - mailing-lists (using Mailman) [EMAIL PROTECTED]:~# No other documentation available (good gods that's horrible in and of itself) Try below for more info: www.list.org I guess horribley inadequate documentation is better then none at all. What are you talking about? It is well documented! From a casual loo kat the website that is hard to tell. It does not get any better than this: http://www.exim.org/howto/mailman.html I saw that, it's geared towards source installs of mailman, not binary. The biggest difference is in setting of permissions and directories. Also, did you see my other post? Look at /usr/share/doc/mailman It should be right there in front of you! I saw, am gonna look at them this evening. I'm still having problems accessing the archives from the web. -- Joseph A. Nagy, Jr. Student at Motlow State Community College Political Activist Extrodinaire The only fallacy is the inaction on our part to stave off the worst of horrors, the stripping of personal freedom. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
