Folks:
Turns out this problem was an incorrect setuid preference on the exim
binary. Applying 'chmod u+s' to the exim binary solved the problem.
Schoolboy error, it would appear!
Cheers
..Iain
> Folks:
>
> I've just 'completed' (hmmm) an installation of mailman with Exim 4.1 on
> MacOS X Server 10.2.3 and although mailman is configured and runs ok,
> mail messages are not getting from exim into Mailman.
>
> The error message(s) I get in Exim are:
>
> 2003-01-12 23:41:13 H8MK2L-0004F3-00 unable to set gid=1025 or uid=1027
> (euid=25): local delivery to test-list <[EMAIL PROTECTED]>
> transport=mailman_transport
> 2003-01-12 23:41:13 H8MK2L-0004F3-00 failed to read delivery status for
> [EMAIL PROTECTED] from delivery subprocess
>
> The gid and uid numbers are the mailman group and user respectively.
>
> Mailman is installed in a virtual host configuration with a separate
> copy of Mailman for each domain within the Mailman user directory, e.g.:
>
> /Users/mailman/neonnumbers.com contains the Mailman installation for
> neonnumbers.com
> /Users/mailman/other-domain.com contains the Mailman installation for
> other-domain.com
> Etc
>
> The config for Exim is from the 'how-to' docs and is a router as
> follows:
>
> ### Router forMailman mail lists ###
>
> mailman_router:
> driver = accept
> require_files = MAILMAN_HOME/${domain}/lists/$local_part/config.pck
> local_part_suffix_optional
> local_part_suffix = -bounces : -bounces+* : \
> -confirm+* : -join : -leave : \
> -owner : -request : -admin
> transport = mailman_transport
>
> Which I think is working fine. The problem seems to be in the transport
> configuration:
>
> ## Transport for Mailman ####
>
> mailman_transport:
> driver = pipe
> command = MAILMAN_HOME/${domain}/mail/mailman \
> '${if def:local_part_suffix \
> {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
> {post}}' \
> $local_part
> current_directory = MAILMAN_HOME/${domain}
> home_directory = MAILMAN_HOME/${domain}
> user = MAILMAN_USER
> group = MAILMAN_GROUP
>
> (where MAILMAN_HOME is /User/mailman and the MAILMAN_USER and
> MAILMAN_GROUP are 'mailman')
>
> I have checked all the configuration with respect to Mailman and all
> seems fine (e.g. Check_perms reports all is well).
>
> This looks like it's a permissions thing either in mailman or Exim, but
> I'm a bit stumped thus far - any help or guidance appreciated.
>
> Thanks in advance.
>
> ..Iain
> --
> Iain Donaldson
> [EMAIL PROTECTED]
>
>
> ------------------------------------------------------
> 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/
>
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/iain%40neonnumbers.com
------------------------------------------------------
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/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
