Re: Mailman setup
On Mon, 2005-01-24 at 12:39 -0500, Neil Joseph Schelly wrote: > What you want is for the mailman_director to be listed before the > system_aliases director, so that it will take charge of handling mailman > messages (and pass them through the mailman_transport) rather than the > system_aliases director. If the system_aliases director sees that message > first, it will just use the address_pipe transport, because: > >mailman: "|/usr/local/mailman/mail/mailman post mailman" > is just an address pipe as far as it is concerned. Dead on - you were exactly right. Many thanks. (Thanks to Mark as well, for pointing at the README.EXIM though I never found the README.Debian) -- Cole Tuininga <[EMAIL PROTECTED]> ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Mailman setup
On Monday 24 January 2005 09:38 am, Cole Tuininga wrote: > Whenever the exim -q runs from cron, I get something like the following: > > 2005-01-24 08:53:01 1Cs7ew-0005Tf-00 Neither the system_aliases director > nor the address_pipe transport set a uid for local delivery of > > |/usr/local/mailman/mail/mailman post mailman > > (Directors section) > mailman_director: > driver = smartuser > require_files = MAILMAN_HOME/lists/$local_part/config.pck > suffix_optional > suffix = -bounces : -bounces+* : \ > -confirm+* : -join : -leave : \ > -owner : -request : -admin > transport = mailman_transport > I have one suggestion to look for. The order of Directors matters. From the sound of that error, it looks as though the email is going through the address_pipe transport (for which no uid/gid is specified) rather than the mailman_transport. That probably means that a director above the mailman_director is taking control of the email. Perhaps the system_aliases director, since you put all those mailman addresses in the system aliases file. What you want is for the mailman_director to be listed before the system_aliases director, so that it will take charge of handling mailman messages (and pass them through the mailman_transport) rather than the system_aliases director. If the system_aliases director sees that message first, it will just use the address_pipe transport, because: >mailman: "|/usr/local/mailman/mail/mailman post mailman" is just an address pipe as far as it is concerned. HTH, -N ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Mailman setup
On Mon, Jan 24, 2005 at 09:38:35AM -0500, Cole Tuininga wrote: > Whenever the exim -q runs from cron, I get something like the following: > > 2005-01-24 08:53:01 1Cs7ew-0005Tf-00 Neither the system_aliases director > nor the address_pipe transport set a uid for local delivery of > |/usr/local/mailman/mail/mailman post mailman Yea, ran into this two weeks ago when setting it up on my box. Don't use /etc/aliases, and be sure to read the README.Debian and README.EXIM documentation that comes with Mailman. I'm using sarge, so there might be a few changes (I'm using Exim 4), but the docs are good for exim3 and 4. -Mark signature.asc Description: Digital signature
Mailman setup
Hi all - I'm setting up Mailman for the first time and have run into one
problem that even the great god "Google" can't seem to help me with. I
thought perhaps y'all could. 8)
Here's what I have: A debian (woody) box running exim 3.35. I hand
compiled python2.3 for it, and downloaded the latest stable Mailman
(2.1.5 I believe).
I followed the procedure for setting everything up, and so far as I can
tell, everything works.
However, there's one problem.
Whenever the exim -q runs from cron, I get something like the following:
2005-01-24 08:53:01 1Cs7ew-0005Tf-00 Neither the system_aliases director
nor the address_pipe transport set a uid for local delivery of
|/usr/local/mailman/mail/mailman post mailman
I've got the following bits in my exim.conf (as directed by the setup)
(Main config section)
MAILMAN_HOME=/usr/local/mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/mailman
MAILMAN_USER=mailman
MAILMAN_GROUP=mailman
(Transport section)
mailman_transport:
driver = pipe
command = MAILMAN_WRAP \
'${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
{post}}' \
$local_part
current_directory = MAILMAN_HOME
home_directory = MAILMAN_HOME
user = MAILMAN_USER
group = MAILMAN_GROUP
(Directors section)
mailman_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/$local_part/config.pck
suffix_optional
suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin
transport = mailman_transport
And finally, in my /etc/aliases (and yes, I did run "newaliases") I
have:
## mailman mailing list
mailman: "|/usr/local/mailman/mail/mailman post mailman"
mailman-admin:"|/usr/local/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman"
mailman-join: "|/usr/local/mailman/mail/mailman join mailman"
mailman-leave:"|/usr/local/mailman/mail/mailman leave mailman"
mailman-owner:"|/usr/local/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/local/mailman/mail/mailman request mailman"
mailman-subscribe:"|/usr/local/mailman/mail/mailman subscribe
mailman"
mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe
mailman"
Anybody have thoughts/hints/suggestions? Many thanks in advance...
--
Cole Tuininga <[EMAIL PROTECTED]>
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
