The following block of code was corrected to read:
system_aliases: driver = aliasfile file = /etc/mail/aliases search_type = lsearch user = daemon group = daemon file_transport = address_file pipe_transport = address_pipe
Where group=daemon, it used to say "guest".
The log file was what caught this. I opened a console and typed: ./usr/local/sbin/exim -d9 -bd
The error in the log looked like this:
Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "daemon", but the system's mail server executed the mail script as group "guest". Try tweaking the mail server to run the script as group "daemon", or re-run configure, providing the command line option `--with-mail-gid=guest'.
My question about mailman logs is still open in curiosity, -are here actual logs, or justmethods to check out what's going on?
-krb
At 09:43 AM 4/27/2004 +0100, Richard Barrett wrote:
On 27 Apr 2004, at 07:50, Karl R. Balsmeier wrote:
Creation and subscription to lists works great, email is making it from the mailman host to the mail server, but when I post to a list, (i have test users who have joined the list, etc.), nothing comes through?
Have you started $prefix/bin/mailmanctl (MM version 2.1.x) or installed the MM crontab (MM version 2.0.x)?
Where are the mailman logs? I'll check em out'...
$prefix/logs/ is a good place to look; and also check the MTA's mail log to check it is delivering to MM successfully
Are messages accumulating in any of the subdirectories of $prefix/qfiles/ ?
Take a look a some of the MM FAQ entries (see the link in the std footer of mail from the mailman-users list)
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
