The 'router drivers' in exim4 have been seriously revamped from the
exim3 routers and directors. There is in fact no longer a 'smartuser'
driver. I beleive some of its functionality has been incorporated into
the new 'accept' and 'redirect' router drivers.
Somewhere in the exim4 documentation there should be a document on
converting from exim3 to exim4, that will probably answer a lot of your
questions.
You could even make up a working exim3 config, and user the 'convert4r4'
utility included with exim4 - it not perfect, but it might get you to a
reasonable starting point. You'll have to fully understand how the
sample exim3 configs given with mailman work, and then have to research
how to accomplish the same thing in exim4.
I cant imagine that there isnt someone on this list successfully using
mailman with exim4, perhaps they will speak up with a sample exim4
config.. I have previously used mailman (with exim3) I have since
switched to exim4, but am no longer using mailman. I will be back in my
office Tuesday - if you havent got it my then drop me a line and I will
see if I can give some further help.
On 16 Jul 2002, Mike Gifford wrote:
> Hello Again,
>
> > | I'm assuming now that the Directors Config area in the runtime
> > | configuration file has been removed in 4.x
> > Correct. exim4 was revamped, and the router/director distinction was
> > removed.
>
> Ok.. So when mailman's README.EXIM tells me to put files in the
> Directors section, this should be the same as putting it in the ROUTERS
> CONFIGURATION section as exim is no longer distinguishing between the
> two.
>
> > | If so does anyone have any suggestions on the modifications required
> > | to a 4.05 setting to get mailman & exim cooperating?
> > Convert the example director to a router.
>
> I've tried to do this... I can't see how it would need any more
> configuration.. However exim 4.05 seems to dislike the driver =
> smartuser in the following (Now at the bottom of the Routers Config
> section):
>
> list_owner_director:
> driver = smartuser
> require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
> suffix = "-owner"
> new_address = "${lc:$local_part}-admin@${domain}"
>
>
> The error it gives me is as follows:
>
> [root@learningpartnership exim.mike]# bin/exim -C configure -bV
> Exim version 4.05 #3 built 13-Jul-2002 23:35:22
> Copyright (c) University of Cambridge 2002
> 2002-07-16 10:31:21 Exim configuration error in line 438:
> router list_owner_director: cannot find router driver "smartuser"
>
>
> I've been searching for info on this error, but I can't seem to find
> much of interest. Does exim 4.05 support a smartuser driver or has this
> concept too been revised.
>
> > The Mailman 2.1 CVS tree has instructions on using exim4.
>
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/README.EXIM?rev=2.4&content-type=text/vnd.viewcvs-markup
>
> >From this I'm guessing that
> driver = smartuser
> should be replaced by
> driver = accept
>
> But pretty much every line in the exim config looks like it would need
> to be rewritten as
> suffix = -request
> new_address = "${lc:$local_part}-admin@${domain}"
> (and likely others)
> prefix = "owner-"
>
> all need to be rewritten for 4.0.5
>
> > I'm sure you can combine the data in the mailman instructions and
> > exim's spec to create the necessary transports and routers tailored to
> > your usage of mailman. If you have specific questions about certain
> > options or something, then by all means ask.
>
> The are very different and I don't know enough about exim or mailman to
> wade through the code and try to find something that 'may' work via
> trial & error. Could take years..
>
> Is there a way to rewrite this easily for exim 4.05? What other
> instructions are no longer useful in the new exim and can I just replace
> them?
>
> list_owner_director:
> driver = smartuser
> require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
> suffix = "-owner"
> new_address = "${lc:$local_part}-admin@${domain}"
>
> owner_list_director:
> driver = smartuser
> require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
> prefix = "owner-"
> new_address = "${lc:$local_part}-admin@${domain}"
>
> ##
> ## Next 3 directors direct admin, request and list mail to the
> appropriate
> ## transport. List existence is checked as above.
>
> list_admin_director:
> driver = smartuser
> suffix = -admin
> require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
> transport = list_admin_transport
>
> list_request_director:
> driver = smartuser
> suffix = -request
> require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
> transport = list_request_transport
>
> list_director:
> driver = smartuser
> require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
> transport = list_transport
>
> > (I haven't personally
> > configured mailman so I can't really give any better info than that)
>
> That makes it harder.. I didn't think I was doing anything too
> groundbreaking here.. this isn't the alpha release of exim.. Had hoped
> that others using mailman had upgraded to a more current version of exim
> than 3.33 and would have experience (and config pointers) to share.
>
> Mike
> --
> Mike Gifford, OpenConcept Consulting, http://www.openconcept.ca
> Open Source Web Applications for Social Change.
> Featured Client - NDP Leadership Candidate - http://www.billblaikie.org
> "An unjust law is no law at all." - Saint Augustine
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>
