Re: Exim4 and mailman
On Fri, Nov 07, 2003 at 09:49:20AM -0500, Stephen Gran wrote: [snip] I am not sure I am doing things the 'Right Way', but I am only using /etc/aliases for my mailman lists, and they are working just fine. $listname: |/var/lib/mailman/mail/wrapper post $listname $listname-admin: |/var/lib/mailman/mail/wrapper mailowner $listname $listname-request: |/var/lib/mailman/mail/wrapper mailcmd $listname $listname-owner: $listname-admin Change $listname to the real mailing list localpart and it works out of the box. With Exim3 I did use the special routers and transports, but when I migrated to Exim4, I thought I would give this method a try, and it's working great. The only problem with this method isthat you don't get virtual domain settings, I suppose. Can anybody see any other problems with it? If you do things the way Dale E Martin did it, Exim automatically notices new lists. If you do things as above, you have to add those 4 lines to /etc/aliases every time you add a new list. -- Michael Wood [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 and mailman
On Fri, Nov 07, 2003 at 09:49:20AM -0500, Stephen Gran wrote: [snip] I am not sure I am doing things the 'Right Way', but I am only using /etc/aliases for my mailman lists, and they are working just fine. $listname: |/var/lib/mailman/mail/wrapper post $listname $listname-admin: |/var/lib/mailman/mail/wrapper mailowner $listname $listname-request: |/var/lib/mailman/mail/wrapper mailcmd $listname $listname-owner: $listname-admin Change $listname to the real mailing list localpart and it works out of the box. With Exim3 I did use the special routers and transports, but when I migrated to Exim4, I thought I would give this method a try, and it's working great. The only problem with this method isthat you don't get virtual domain settings, I suppose. Can anybody see any other problems with it? If you do things the way Dale E Martin did it, Exim automatically notices new lists. If you do things as above, you have to add those 4 lines to /etc/aliases every time you add a new list. -- Michael Wood [EMAIL PROTECTED]
Re: Exim4 and mailman
Just wondering if anyone has set up the Mailman mailing list package with exim4? Yes, did you have some specific question about it? Later, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Exim4 and mailman
Hi Yes, Im reading through a guide how to set this up but am getting a little confused with what/where to add/edit my exim4.conf file. Do you purhaps have an example of what you added? I'm very new to exim and mailman :) Thanks, Dave -Original Message- From: Dale E Martin [mailto:[EMAIL PROTECTED] Sent: 07 November 2003 03:12 To: Debian-ISP Subject: Re: Exim4 and mailman Just wondering if anyone has set up the Mailman mailing list package with exim4? Yes, did you have some specific question about it? Later, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 and mailman
(No need to copy me, I'm subscribed to the mailing list.)
Yes, Im reading through a guide how to set this up but am getting a little
confused with what/where to add/edit my exim4.conf file. Do you purhaps have
an example of what you added? I'm very new to exim and mailman :)
Sure. Let me mention two things before you take my example to heart too
much... First, I migrated this from exim 3 to exim 4 so maybe there is a
better way. Also, the Debian exim 4 packages distribute the configuration
file into bits in a directory structure - for good reasons, I'm sure. (For
example, if the mailmain maintainer gets on board then mailman could simply
install it's own bits in the to configuration heirarchy and it should work
out of the box.) However, I had a fairly customized exim setup and needed
it working quickly, so I went the monolothic file route and have a
/etc/exim4/exim4.conf Having said all of that, here you go -
anything in [] is my comments to you and not actually in the file.
[beginning of /etc/exim/exim4.conf]
# All macro definitions have been gathered here to ensure
# they precede any references to them.
MAILMAN_HOME=/var/lib/mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper
MAILMAN_UID=mail
MAILMAN_GID=list
[ skipping down to directors ]
##
# DIRECTORS CONFIGURATION #
# Specifies how local addresses are handled #
##
# ORDER DOES MATTER #
# A local address is passed to each in turn until it is accepted. #
##
# This allows local delivery to be forced, avoiding alias files and
# forwarding.
real_local:
driver = accept
check_local_user
local_part_prefix = real-
transport = local_delivery
# First we have mailman entries
# First 2 directors rewrite list-owner or owner-list to list-admin
# This is only done if the list exists.
# List existence checks are done by seeing if the file
# MAILMAN_HOME/lists//config.db
# exists.
list_owner_director:
driver = redirect
allow_defer
allow_fail
data = ${lc:[EMAIL PROTECTED]
local_part_suffix = -owner
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
owner_list_director:
driver = redirect
allow_defer
allow_fail
data = ${lc:[EMAIL PROTECTED]
local_part_prefix = owner-
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
##
## Next 3 directors direct admin, request and list mail to the appropriate
## transport. List existence is checked as above.
list_admin_director:
driver = accept
local_part_suffix = -admin
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
transport = list_admin_transport
list_request_director:
driver = accept
local_part_suffix = -request
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
transport = list_request_transport
list_director:
driver = accept
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
transport = list_transport
[ end of the mailman specific part of the directors ]
[ Next is the transport section, order here does not matter so I'm only
pasting in the relevant parts. ]
# Three transports for list mail, request mail and admin mail
# respectively
# Mailman is installed in MAILMAN_HOME
# Mailman is configured to be invoked as user exim
list_transport:
driver = pipe
command = MAILMAN_WRAP post ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID
list_request_transport:
driver = pipe
command = MAILMAN_WRAP mailcmd ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID
list_admin_transport:
driver = pipe
command = MAILMAN_WRAP mailowner ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID
[ that's it for the exim4.conf file ]
In addition to the exim4.conf file, then you have to setup lists. It's
been a while since I've down this, but I recall it being straightforward
simply following the docs.
Take care,
Dale
--
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
[EMAIL PROTECTED]
http://www.cliftonlabs.com
pgp key available
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 and mailman
This one time, at band camp, Dale E Martin said: (No need to copy me, I'm subscribed to the mailing list.) Yes, Im reading through a guide how to set this up but am getting a little confused with what/where to add/edit my exim4.conf file. Do you purhaps have an example of what you added? I'm very new to exim and mailman :) Sure. Let me mention two things before you take my example to heart too much... First, I migrated this from exim 3 to exim 4 so maybe there is a better way. Also, the Debian exim 4 packages distribute the configuration file into bits in a directory structure - for good reasons, I'm sure. (For example, if the mailmain maintainer gets on board then mailman could simply install it's own bits in the to configuration heirarchy and it should work out of the box.) However, I had a fairly customized exim setup and needed it working quickly, so I went the monolothic file route and have a /etc/exim4/exim4.conf Having said all of that, here you go - anything in [] is my comments to you and not actually in the file. I am not sure I am doing things the 'Right Way', but I am only using /etc/aliases for my mailman lists, and they are working just fine. $listname: |/var/lib/mailman/mail/wrapper post $listname $listname-admin: |/var/lib/mailman/mail/wrapper mailowner $listname $listname-request: |/var/lib/mailman/mail/wrapper mailcmd $listname $listname-owner: $listname-admin Change $listname to the real mailing list localpart and it works out of the box. With Exim3 I did use the special routers and transports, but when I migrated to Exim4, I thought I would give this method a try, and it's working great. The only problem with this method isthat you don't get virtual domain settings, I suppose. Can anybody see any other problems with it? -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgp0.pgp Description: PGP signature
Re: Exim4 and mailman
Just wondering if anyone has set up the Mailman mailing list package with exim4? Yes, did you have some specific question about it? Later, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available
RE: Exim4 and mailman
Hi Yes, Im reading through a guide how to set this up but am getting a little confused with what/where to add/edit my exim4.conf file. Do you purhaps have an example of what you added? I'm very new to exim and mailman :) Thanks, Dave -Original Message- From: Dale E Martin [mailto:[EMAIL PROTECTED] Sent: 07 November 2003 03:12 To: Debian-ISP Subject: Re: Exim4 and mailman Just wondering if anyone has set up the Mailman mailing list package with exim4? Yes, did you have some specific question about it? Later, Dale -- Dale E. Martin, Clifton Labs, Inc. Senior Computer Engineer [EMAIL PROTECTED] http://www.cliftonlabs.com pgp key available -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 and mailman
(No need to copy me, I'm subscribed to the mailing list.)
Yes, Im reading through a guide how to set this up but am getting a little
confused with what/where to add/edit my exim4.conf file. Do you purhaps have
an example of what you added? I'm very new to exim and mailman :)
Sure. Let me mention two things before you take my example to heart too
much... First, I migrated this from exim 3 to exim 4 so maybe there is a
better way. Also, the Debian exim 4 packages distribute the configuration
file into bits in a directory structure - for good reasons, I'm sure. (For
example, if the mailmain maintainer gets on board then mailman could simply
install it's own bits in the to configuration heirarchy and it should work
out of the box.) However, I had a fairly customized exim setup and needed
it working quickly, so I went the monolothic file route and have a
/etc/exim4/exim4.conf Having said all of that, here you go -
anything in [] is my comments to you and not actually in the file.
[beginning of /etc/exim/exim4.conf]
# All macro definitions have been gathered here to ensure
# they precede any references to them.
MAILMAN_HOME=/var/lib/mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper
MAILMAN_UID=mail
MAILMAN_GID=list
[ skipping down to directors ]
##
# DIRECTORS CONFIGURATION #
# Specifies how local addresses are handled #
##
# ORDER DOES MATTER #
# A local address is passed to each in turn until it is accepted. #
##
# This allows local delivery to be forced, avoiding alias files and
# forwarding.
real_local:
driver = accept
check_local_user
local_part_prefix = real-
transport = local_delivery
# First we have mailman entries
# First 2 directors rewrite list-owner or owner-list to list-admin
# This is only done if the list exists.
# List existence checks are done by seeing if the file
# MAILMAN_HOME/lists//config.db
# exists.
list_owner_director:
driver = redirect
allow_defer
allow_fail
data = ${lc:[EMAIL PROTECTED]
local_part_suffix = -owner
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
owner_list_director:
driver = redirect
allow_defer
allow_fail
data = ${lc:[EMAIL PROTECTED]
local_part_prefix = owner-
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
##
## Next 3 directors direct admin, request and list mail to the appropriate
## transport. List existence is checked as above.
list_admin_director:
driver = accept
local_part_suffix = -admin
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
transport = list_admin_transport
list_request_director:
driver = accept
local_part_suffix = -request
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
transport = list_request_transport
list_director:
driver = accept
require_files = MAILMAN_HOME/lists/${lc::$local_part}/config.db
retry_use_local_part
transport = list_transport
[ end of the mailman specific part of the directors ]
[ Next is the transport section, order here does not matter so I'm only
pasting in the relevant parts. ]
# Three transports for list mail, request mail and admin mail
# respectively
# Mailman is installed in MAILMAN_HOME
# Mailman is configured to be invoked as user exim
list_transport:
driver = pipe
command = MAILMAN_WRAP post ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID
list_request_transport:
driver = pipe
command = MAILMAN_WRAP mailcmd ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID
list_admin_transport:
driver = pipe
command = MAILMAN_WRAP mailowner ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID
[ that's it for the exim4.conf file ]
In addition to the exim4.conf file, then you have to setup lists. It's
been a while since I've down this, but I recall it being straightforward
simply following the docs.
Take care,
Dale
--
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
[EMAIL PROTECTED]
http://www.cliftonlabs.com
pgp key available
Re: Exim4 and mailman
This one time, at band camp, Dale E Martin said: (No need to copy me, I'm subscribed to the mailing list.) Yes, Im reading through a guide how to set this up but am getting a little confused with what/where to add/edit my exim4.conf file. Do you purhaps have an example of what you added? I'm very new to exim and mailman :) Sure. Let me mention two things before you take my example to heart too much... First, I migrated this from exim 3 to exim 4 so maybe there is a better way. Also, the Debian exim 4 packages distribute the configuration file into bits in a directory structure - for good reasons, I'm sure. (For example, if the mailmain maintainer gets on board then mailman could simply install it's own bits in the to configuration heirarchy and it should work out of the box.) However, I had a fairly customized exim setup and needed it working quickly, so I went the monolothic file route and have a /etc/exim4/exim4.conf Having said all of that, here you go - anything in [] is my comments to you and not actually in the file. I am not sure I am doing things the 'Right Way', but I am only using /etc/aliases for my mailman lists, and they are working just fine. $listname: |/var/lib/mailman/mail/wrapper post $listname $listname-admin: |/var/lib/mailman/mail/wrapper mailowner $listname $listname-request: |/var/lib/mailman/mail/wrapper mailcmd $listname $listname-owner: $listname-admin Change $listname to the real mailing list localpart and it works out of the box. With Exim3 I did use the special routers and transports, but when I migrated to Exim4, I thought I would give this method a try, and it's working great. The only problem with this method isthat you don't get virtual domain settings, I suppose. Can anybody see any other problems with it? -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgpFPbySv75MO.pgp Description: PGP signature
