Re: Mailman Broken
Op di, 28-12-2004 te 23:13 -0600, schreef W.AndrewLoeIII: [...] sed: -e expression #1, char 43: unterminated `s' command dpkg: error processing mailman (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: mailman E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED] I've tried apt-get --fix-broken, but haven't had any luck there. I've tried removing it and then searching my entire system for any remnants to remove, to no avail. I'm pretty sure this is probably my ignorance of how to properly use apt-get, Actually, this looks like a bug in the package to me. You'll want to use 'reportbug'. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mailman Broken
also sprach Wouter Verhelst [EMAIL PROTECTED] [2004.12.29.0936 +0100]: Actually, this looks like a bug in the package to me. You'll want to use 'reportbug'. sed -i -e '1aset -x' /var/lib/dpkg/info/mailman.postinst apt-get -f install and include the output of that command in the bug report. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
Mailman Broken
I'm asking this question here as more people on this list probably have experience with with mailman. I had mailman installed on my system, but stupidly apt-get --purge'd it. Now I cannot get it to re-install correctly: Selecting previously deselected package mailman. (Reading database ... 35297 files and directories currently installed.) Unpacking mailman (from .../mailman_2.1.5-4_i386.deb) ... Setting up mailman (2.1.5-4) ... Looking for enabled languages (this may take some time) ... done. Installing site language en done. Configuring mailman for domain mydomain1.com mydomain2com mydomain3.com ... sed: -e expression #1, char 43: unterminated `s' command dpkg: error processing mailman (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: mailman E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED] I've tried apt-get --fix-broken, but haven't had any luck there. I've tried removing it and then searching my entire system for any remnants to remove, to no avail. I'm pretty sure this is probably my ignorance of how to properly use apt-get, but the documentation is not helping me at all. Thank you for your time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mailman Broken
I'm asking this question here as more people on this list probably have experience with with mailman. I had mailman installed on my system, but stupidly apt-get --purge'd it. Now I cannot get it to re-install correctly: Selecting previously deselected package mailman. (Reading database ... 35297 files and directories currently installed.) Unpacking mailman (from .../mailman_2.1.5-4_i386.deb) ... Setting up mailman (2.1.5-4) ... Looking for enabled languages (this may take some time) ... done. Installing site language en done. Configuring mailman for domain mydomain1.com mydomain2com mydomain3.com ... sed: -e expression #1, char 43: unterminated `s' command dpkg: error processing mailman (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: mailman E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED] I've tried apt-get --fix-broken, but haven't had any luck there. I've tried removing it and then searching my entire system for any remnants to remove, to no avail. I'm pretty sure this is probably my ignorance of how to properly use apt-get, but the documentation is not helping me at all. Thank you for your time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Exim 4.20 + Mailman
Title: RE: Exim 4.20 + Mailman -Original Message- From: Kenny Duffus [mailto:[EMAIL PROTECTED]] Sent: 01 June 2004 10:34 To: debian-isp@lists.debian.org Subject: Re: Exim 4.20 + Mailman Has anyone set up Exim 4.20 and mailman successfully and if so do you mind if I take a look at your exim.conf? I've done this before with Exim 3 but am struggling to find working examples for exim4. Why do you need to mess with the exim config? Just add the lines that the newlist command gives you into your /etc/aliases something like: ## dmfs-discuss mailing list dmfs-discuss: |/var/lib/mailman/mail/mailman post dmfs-discuss dmfs-discuss-admin: |/var/lib/mailman/mail/mailman admin dmfs-discuss dmfs-discuss-bounces: |/var/lib/mailman/mail/mailman bounces dmfs-discuss dmfs-discuss-confirm: |/var/lib/mailman/mail/mailman confirm dmfs-discuss dmfs-discuss-join: |/var/lib/mailman/mail/mailman join dmfs-discuss dmfs-discuss-leave: |/var/lib/mailman/mail/mailman leave dmfs-discuss dmfs-discuss-owner: |/var/lib/mailman/mail/mailman owner dmfs-discuss dmfs-discuss-request: |/var/lib/mailman/mail/mailman request dmfs-discuss dmfs-discuss-subscribe: |/var/lib/mailman/mail/mailman subscribe dmfs-discuss dmfs-discuss-unsubscribe: |/var/lib/mailman/mail/mailman unsubscribe dmfs-discuss
Exim 4.20 + Mailman
Hi Has anyone set up Exim 4.20 and mailman successfully and if so do you mind if I take a look at your exim.conf? I've done this before with Exim 3 but am struggling to find working examples for exim4. Thanks Dave
Re: Exim 4.20 + Mailman
On Tue, Jun 01, 2004 at 10:25:03AM +0200, David Ross wrote:
Hi
Has anyone set up Exim 4.20 and mailman successfully and if so do you
mind if I take a look at your exim.conf? I've done this before with Exim
3 but am struggling to find working examples for exim4.
Hi
I followed the howto on the exim website:
http://www.exim.org/howto/mailman21.html
As I am using the split config with exim4 I created a transport called
091_mailman_transport:
mailman_transport:
driver = pipe
command = /var/lib/mailman/mail/mailman \
'${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
{post}}' \
$local_part
current_directory = /var/lib/mailman
home_directory = /var/lib/mailman
user = list
group = list
and a router called 091_mailman_router:
mailman_router:
driver = accept
domains = example.com
require_files = /var/lib/mailman/lists/$local_part/config.pck
local_part_suffix_optional
local_part_suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin : \
-subscribe : -unsubscribe
transport = mailman_transport
those numbers worked for me ensuring they were used before any alias
files.
Doing it that way means that you don't have to add aliases for each new
list as it checks the lists directory to see if there is a list called
whatever there.
Kenny
signature.asc
Description: Digital signature
Mailman on debian testing
I am having many problems running mailman on debian testing. Does anyone have an easier way of getting a package up and running? I have gone to the source, and sent the bug report below to the mailman lists, but I can't believe others haven't gone through this before. Thanks, -- Marco In many parts of the web interface I am getting the same mailman bug: It started when confirming a subscription through the online interface: File /usr/local/mailman/Mailman/OldStyleMemberships.py, line 312, in setMemberOption self.__mlist.user_options[memberkey] |= flag TypeError: unsupported operand type(s) for |=: 'list' and 'int' I fixed this by changing line 312 from above to : self.__mlist.user_options[memberkey][0] |= flags Now I can subscribe, but I get the same typeerror bug after logging into my options page for this new subscription: File /usr/local/mailman/Mailman/OldStyleMemberships.py, line 128, in getMemberOption return not not (option flag) TypeError: unsupported operand type(s) for : 'list' and 'int' Makes sense, fix it too, but I also get the same Typeerror when logging into the admin page: File /usr/local/mailman/Mailman/Gui/General.py, line 53, in GetConfigInfo optvals = [mlist.new_member_options bitfields[o] for o in OPTIONS] TypeError: unsupported operand type(s) for : 'list' and 'int' Is something else wrong, or should I go and fix all these. I am running mailman 2.1.4 on debian testing with python2.3 -- Marco - End forwarded message - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mailman on debian testing
I am having many problems running mailman on debian testing. Does anyone have an easier way of getting a package up and running? I have gone to the source, and sent the bug report below to the mailman lists, but I can't believe others haven't gone through this before. Thanks, -- Marco In many parts of the web interface I am getting the same mailman bug: It started when confirming a subscription through the online interface: File /usr/local/mailman/Mailman/OldStyleMemberships.py, line 312, in setMemberOption self.__mlist.user_options[memberkey] |= flag TypeError: unsupported operand type(s) for |=: 'list' and 'int' I fixed this by changing line 312 from above to : self.__mlist.user_options[memberkey][0] |= flags Now I can subscribe, but I get the same typeerror bug after logging into my options page for this new subscription: File /usr/local/mailman/Mailman/OldStyleMemberships.py, line 128, in getMemberOption return not not (option flag) TypeError: unsupported operand type(s) for : 'list' and 'int' Makes sense, fix it too, but I also get the same Typeerror when logging into the admin page: File /usr/local/mailman/Mailman/Gui/General.py, line 53, in GetConfigInfo optvals = [mlist.new_member_options bitfields[o] for o in OPTIONS] TypeError: unsupported operand type(s) for : 'list' and 'int' Is something else wrong, or should I go and fix all these. I am running mailman 2.1.4 on debian testing with python2.3 -- Marco - End forwarded message -
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]
Exim4 + Mailman
Hi, Has anyone set up mailman with exim4? I've been going through many configs and examples from friends and was wndering if anyone has a basic config example i could add to each section in the eixm.conf file. Any help would be greatly appreciated. Thanks! Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Exim4 + Mailman
Hi, Has anyone set up mailman with exim4? I've been going through many configs and examples from friends and was wndering if anyone has a basic config example i could add to each section in the eixm.conf file. Any help would be greatly appreciated. Thanks! Dave
Exim4 and mailman
Hi, Just wondering if anyone has set up the Mailman mailing list package with exim4? Thanks, Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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
Exim4 and mailman
Hi, Just wondering if anyone has set up the Mailman mailing list package with exim4? Thanks, Dave
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
Re: mailman
On Wed, Aug 27, 2003 at 02:01:14PM +0200, Peter Holm wrote: Hi, I am new to mailman and after apt-get install mailman following the INSTALL doc I tried a check_perms, that gave me lots of errors. Trying to fix these with -f gave even more errors. Is this normal? Did I something wrong? Are there any special things I have to do to get it running? Thanks for your attention! debian:/usr/lib/mailman/bin$ ./check_perms /var/lib/mailman/archives bad gid (has: list, expected anon gid 38) /var/lib/mailman/lists bad gid (has: list, expected anon gid 38) /var/lib/mailman/qfiles bad gid (has: list, expected anon gid 38) /var/lib/mailman/data bad gid (has: list, expected anon gid 38) Hmm... I'd chgrp 38 /var/lib/mailman/archives (-R if directory) etc ... ... and see if it works. Or create own debs from source. -- __ Yours sincerely, Christofer Algotsson - [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mailman
Hi, I am new to mailman and after apt-get install mailman following the INSTALL doc I tried a check_perms, that gave me lots of errors. Trying to fix these with -f gave even more errors. Is this normal? Did I something wrong? Are there any special things I have to do to get it running? Thanks for your attention! debian:/usr/lib/mailman/bin$ ./check_perms /var/lib/mailman/archives bad gid (has: list, expected anon gid 38) /var/lib/mailman/lists bad gid (has: list, expected anon gid 38) /var/lib/mailman/qfiles bad gid (has: list, expected anon gid 38) /var/lib/mailman/data bad gid (has: list, expected anon gid 38) /var/lib/mailman/spam bad gid (has: list, expected anon gid 38) /var/lib/mailman/icons bad gid (has: list, expected anon gid 38) /var/lib/mailman/templates bad gid (has: list, expected anon gid 38) /var/lib/mailman/logs bad gid (has: list, expected anon gid 38) /var/lib/mailman/locks bad gid (has: list, expected anon gid 38) /var/lib/mailman/Mailman bad gid (has: list, expected anon gid 38) /var/lib/mailman/bin bad gid (has: list, expected anon gid 38) /var/lib/mailman/cron bad gid (has: list, expected anon gid 38) /var/lib/mailman/filters bad gid (has: list, expected anon gid 38) /var/lib/mailman/mail bad gid (has: list, expected anon gid 38) /var/lib/mailman/scripts bad gid (has: list, expected anon gid 38) /var/lib/mailman/mailman bad gid (has: list, expected anon gid 38) /var/lib/mailman/archives/private bad gid (has: list, expected anon gid 38) /var/lib/mailman/archives/public bad gid (has: list, expected anon gid 38) /var/lib/mailman/data/pending_subscriptions.db bad gid (has: list, expected anon gid 38) /var/lib/mailman/data/last_mailman_version bad gid (has: list, expected anon gid 38) Problems found: 20 Re-run as uid 38 (or root) with -f flag to fix debian:/usr/lib/mailman/bin$ ./check_perms -f /var/lib/mailman/archives bad gid (has: list, expected anon gid 38) (fixing) Traceback (most recent call last): File ./check_perms, line 277, in ? checkall() File ./check_perms, line 137, in checkall os.path.walk(d, checkwalk, STATE) File /usr/lib/python2.1/posixpath.py, line 269, in walk func(arg, top, names) File ./check_perms, line 100, in checkwalk os.chown(path, -1, MAILMAN_GID) OSError: [Errno 1] Operation not permitted: '/var/lib/mailman/archives' Have a nice thread, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
AW: AW: Installing Mailman
Hi ! I'm a newbie when it comes to the more complex aspects of debian, so if you could send me step by step instructions on getting my install to work, that would be really appreciated. I haven't tried anything that I didn't know how to undo. I would like to get Mailman running Postfix if that makes a difference. Actually it was very easy, as most installs with deb. Packages are, to install mailman. For the : Apt-get install mailman worked out of the box. I am also running postfix and I have set up mailman with a couple of list under different domains. You don´t need to run ./configure anywhere The only thing I had to do was setting an alias for die mailman cgis . Anyway I don´t know if this is OT here ... __ Nik Engel NETWAYS GmbH Senior Systems Engineer Deutschherrnstr. 47a Fon.0911/92885-13 D-90429 Nürnberg Fax.0911/92885-33 [EMAIL PROTECTED] www.netways.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
AW: AW: Installing Mailman
Hi ! I'm a newbie when it comes to the more complex aspects of debian, so if you could send me step by step instructions on getting my install to work, that would be really appreciated. I haven't tried anything that I didn't know how to undo. I would like to get Mailman running Postfix if that makes a difference. Actually it was very easy, as most installs with deb. Packages are, to install mailman. For the : Apt-get install mailman worked out of the box. I am also running postfix and I have set up mailman with a couple of list under different domains. You don´t need to run ./configure anywhere The only thing I had to do was setting an alias for die mailman cgis . Anyway I don´t know if this is OT here ... __ Nik Engel NETWAYS GmbH Senior Systems Engineer Deutschherrnstr. 47a Fon.0911/92885-13 D-90429 Nürnberg Fax.0911/92885-33 [EMAIL PROTECTED] www.netways.de
AW: Installing Mailman
Any help on this would be great, thanks What are your problems ? I just finnished an installation ... Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing Mailman
Has anybody installed Mailman on debian? I'm a newbie and am having a lot of trouble getting it to work. All the instructions that I find for it are all for Linux and refer to files and data structures that don't match how the binaries were installed on my system. Any help on this would be great, thanks Alex
Re: Installing Mailman
On Tue, Mar 25, 2003 at 11:48:25AM -0500, Alex Salamon [EMAIL PROTECTED] wrote: Has anybody installed Mailman on debian? I'm a newbie and am having a lot of trouble getting it to work. All the instructions that I find for it are all for Linux and refer to files and data structures that don't match how the binaries were installed on my system. What's about apt-get install mailman?
Re: virtual domains and mailman with Postfix
On Tue, 10 Sep 2002 11:06, Henrik Hempelmann wrote: Now lists.example.com is a CNAME pointing to server.example.com. So why is mail sent from the local machine with mailx working, while a message sent on port 25 with the same content is rejected? External MTA are rewriting (canonifying) [EMAIL PROTECTED] to [EMAIL PROTECTED] because of the CNAME pointing to it. So your postfix will never see any [EMAIL PROTECTED] addresses. Thanks for the info, the CNAME was a large part of my problem. -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: virtual domains and mailman with Postfix
Russell Coker wrote: help message). But if I send mail from outside the network I get the following: [EMAIL PROTECTED]: mail for server.example.com loops back to myself Now lists.example.com is a CNAME pointing to server.example.com. So why is mail sent from the local machine with mailx working, while a message sent on port 25 with the same content is rejected? External MTA are rewriting (canonifying) [EMAIL PROTECTED] to [EMAIL PROTECTED] because of the CNAME pointing to it. So your postfix will never see any [EMAIL PROTECTED] addresses. RFC 2181 10.3. MX and NS records The domain name used as [...] part of the value of a MX resource record must not be an alias. So it's best to change the DNS records: server.example.com IN A w.x.y.z. lists.example.com IN MX server.example.com. Henrik
virtual domains and mailman with Postfix
In main.cf I have: virtual_maps = hash:/etc/postfix/virtual In /etc/postfix/virtual I have the following: # mailman lists.example.com virtual [EMAIL PROTECTED] example-listowner [EMAIL PROTECTED] list-testing [EMAIL PROTECTED] list-testing-admin [EMAIL PROTECTED] list-testing-request [EMAIL PROTECTED] list-testing-admin @lists.example.com example-listowner In /etc/aliases I have: # mailman example-listowner: rop, etbe ## testing mailing list ## created: 09-Sep-2002 root list-testing: |/var/lib/mailman/mail/wrapper post testing list-testing-admin: |/var/lib/mailman/mail/wrapper mailowner testing list-testing-request: |/var/lib/mailman/mail/wrapper mailcmd testing #list-testing-owner: testing-admin Now when I send mail from the local machine it all works as expected (I send mail to [EMAIL PROTECTED] with subject help and I get the help message). But if I send mail from outside the network I get the following: [EMAIL PROTECTED]: mail for server.example.com loops back to myself Now lists.example.com is a CNAME pointing to server.example.com. So why is mail sent from the local machine with mailx working, while a message sent on port 25 with the same content is rejected? -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: virtual domains and mailman with Postfix
[EMAIL PROTECTED]: mail for server.example.com loops back to myself Make sure that the mail server(s) for server.example.com know that server.example.com is a local domain. So why is mail sent from the local machine with mailx working, while a message sent on port 25 with the same content is rejected? I don't know. Not enough information. You may want to use real hostnames, so we can see for ourselves (as much as can be seen). Jeremy C. Reed ... BSD software, documentation, resources, news... http://bsd.reedmedia.net/
Mailman v1.1
Hi Fellas How do I get Mailman to archive my mail, so that we can view our html newsletters from the web ? At present the mail looks like its in plain text. Thanks ..Craig
Re: SSL and Mailman?, was Re: Mailing Lists
Hello! On Sun, Nov 11, 2001 at 10:02:10AM +1100, Craig Sanders wrote: ... you should be able to do that in your apache configuration - either deny access to unencrypted connections or send a redirect to the encrypted URL. ... Eric Jennings yet sent kindly the recipe :) And I rushed to implement it, when I realized that for survival reasons I am using the boa web server. it's not really mailman's job to do that. ... You are surely right, but, is there another boa-like small|fast web server which supports ssl? Is there some ssl-cgi-sandwich which allows to use ssl on servers that do not have built in support? Not really problems I have to live with right now, but I wonder,... Best Regards, Jorge-León -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSL and Mailman?, was Re: Mailing Lists
On Mon, Nov 12, 2001 at 10:34:57PM -0600, [EMAIL PROTECTED] wrote: Hello! On Sun, Nov 11, 2001 at 10:02:10AM +1100, Craig Sanders wrote: ... you should be able to do that in your apache configuration - either deny access to unencrypted connections or send a redirect to the encrypted URL. ... Eric Jennings yet sent kindly the recipe :) And I rushed to implement it, when I realized that for survival reasons I am using the boa web server. it's not really mailman's job to do that. ... You are surely right, but, is there another boa-like small|fast web server which supports ssl? Is there some ssl-cgi-sandwich which allows to use ssl on servers that do not have built in support? stunnel is your friend. Tim -- Tim Sailer (at home) Coastal Internet, Inc. Network and Systems Operations PO Box 671 http://www.buoy.comRidge, NY 11961 [EMAIL PROTECTED][EMAIL PROTECTED] (631) 924-3728 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mailman v1.1
Hi Fellas How do I get Mailman to archive my mail, so that we can view our html newsletters from the web ? At present the mail looks like its in plain text. Thanks ..Craig
Re: SSL and Mailman?, was Re: Mailing Lists
Hello! On Sun, Nov 11, 2001 at 10:02:10AM +1100, Craig Sanders wrote: ... you should be able to do that in your apache configuration - either deny access to unencrypted connections or send a redirect to the encrypted URL. ... Eric Jennings yet sent kindly the recipe :) And I rushed to implement it, when I realized that for survival reasons I am using the boa web server. it's not really mailman's job to do that. ... You are surely right, but, is there another boa-like small|fast web server which supports ssl? Is there some ssl-cgi-sandwich which allows to use ssl on servers that do not have built in support? Not really problems I have to live with right now, but I wonder,... Best Regards, Jorge-León
Re: SSL and Mailman?, was Re: Mailing Lists
On Mon, Nov 12, 2001 at 10:34:57PM -0600, [EMAIL PROTECTED] wrote: Hello! On Sun, Nov 11, 2001 at 10:02:10AM +1100, Craig Sanders wrote: ... you should be able to do that in your apache configuration - either deny access to unencrypted connections or send a redirect to the encrypted URL. ... Eric Jennings yet sent kindly the recipe :) And I rushed to implement it, when I realized that for survival reasons I am using the boa web server. it's not really mailman's job to do that. ... You are surely right, but, is there another boa-like small|fast web server which supports ssl? Is there some ssl-cgi-sandwich which allows to use ssl on servers that do not have built in support? stunnel is your friend. Tim -- Tim Sailer (at home) Coastal Internet, Inc. Network and Systems Operations PO Box 671 http://www.buoy.comRidge, NY 11961 [EMAIL PROTECTED]/[EMAIL PROTECTED] (631) 924-3728
Re: SSL and Mailman?, was Re: Mailing Lists
On Fri, Nov 09, 2001 at 09:22:17AM -0600, [EMAIL PROTECTED] wrote: I'm using mailman, but only at a *very* small scale. While beeing satisfied about the ease of configuration and managment of the lists, I am worried about the fact, that the list administrator is sending the list password in cleartext over the net when logging in. Of course I give the admins the advice to use https:// instead of http:// when logging in, but mailman does not enforce it. you should be able to do that in your apache configuration - either deny access to unencrypted connections or send a redirect to the encrypted URL. I think of diving into the code some day to see into it, but maybe I'm too paranoid or you have yet a solution to this... it's not really mailman's job to do that. craig -- craig sanders [EMAIL PROTECTED] Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSL and Mailman?, was Re: Mailing Lists
On Fri, Nov 09, 2001 at 09:22:17AM -0600, [EMAIL PROTECTED] wrote: I'm using mailman, but only at a *very* small scale. While beeing satisfied about the ease of configuration and managment of the lists, I am worried about the fact, that the list administrator is sending the list password in cleartext over the net when logging in. Of course I give the admins the advice to use https:// instead of http:// when logging in, but mailman does not enforce it. you should be able to do that in your apache configuration - either deny access to unencrypted connections or send a redirect to the encrypted URL. I think of diving into the code some day to see into it, but maybe I'm too paranoid or you have yet a solution to this... it's not really mailman's job to do that. craig -- craig sanders [EMAIL PROTECTED] Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch
SSL and Mailman?, was Re: Mailing Lists
Hello! I'm using mailman, but only at a *very* small scale. While beeing satisfied about the ease of configuration and managment of the lists, I am worried about the fact, that the list administrator is sending the list password in cleartext over the net when logging in. Of course I give the admins the advice to use https:// instead of http:// when logging in, but mailman does not enforce it. I think of diving into the code some day to see into it, but maybe I'm too paranoid or you have yet a solution to this... Any thoughts? Jorge-León On Thu, Nov 08, 2001 at 01:59:51PM +, Martin WHEELER wrote: On Thu, 8 Nov 2001, Andre Luis Lopes wrote: Em Qui 08 Nov 2001 10:19, Craigsc escreveu: ... It's worth it for the web-based administration and archiving alone. ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSL and Mailman?, was Re: Mailing Lists
In your Apache httpd.conf file, under the VirtualHost block that handles your mailman config, force Apache to use https instead of http, even when somebody types in http. You do it by adding the below 2 lines: (you have to have mod_rewrite compiled and installed in your Apache daemon) RewriteEngine on RewriteRule ^/(.+) https://www.somedomain.com/cgi-bin/mailmanconfig [R,L] HTH- Eric Hello! I'm using mailman, but only at a *very* small scale. While beeing satisfied about the ease of configuration and managment of the lists, I am worried about the fact, that the list administrator is sending the list password in cleartext over the net when logging in. Of course I give the admins the advice to use https:// instead of http:// when logging in, but mailman does not enforce it. I think of diving into the code some day to see into it, but maybe I'm too paranoid or you have yet a solution to this... Any thoughts? Jorge-León On Thu, Nov 08, 2001 at 01:59:51PM +, Martin WHEELER wrote: On Thu, 8 Nov 2001, Andre Luis Lopes wrote: Em Qui 08 Nov 2001 10:19, Craigsc escreveu: ... It's worth it for the web-based administration and archiving alone. ... -- 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]
SSL and Mailman?, was Re: Mailing Lists
Hello! I'm using mailman, but only at a *very* small scale. While beeing satisfied about the ease of configuration and managment of the lists, I am worried about the fact, that the list administrator is sending the list password in cleartext over the net when logging in. Of course I give the admins the advice to use https:// instead of http:// when logging in, but mailman does not enforce it. I think of diving into the code some day to see into it, but maybe I'm too paranoid or you have yet a solution to this... Any thoughts? Jorge-León On Thu, Nov 08, 2001 at 01:59:51PM +, Martin WHEELER wrote: On Thu, 8 Nov 2001, Andre Luis Lopes wrote: Em Qui 08 Nov 2001 10:19, Craigsc escreveu: ... It's worth it for the web-based administration and archiving alone. ...
Re: SSL and Mailman?, was Re: Mailing Lists
In your Apache httpd.conf file, under the VirtualHost block that handles your mailman config, force Apache to use https instead of http, even when somebody types in http. You do it by adding the below 2 lines: (you have to have mod_rewrite compiled and installed in your Apache daemon) RewriteEngine on RewriteRule ^/(.+) https://www.somedomain.com/cgi-bin/mailmanconfig [R,L] HTH- Eric Hello! I'm using mailman, but only at a *very* small scale. While beeing satisfied about the ease of configuration and managment of the lists, I am worried about the fact, that the list administrator is sending the list password in cleartext over the net when logging in. Of course I give the admins the advice to use https:// instead of http:// when logging in, but mailman does not enforce it. I think of diving into the code some day to see into it, but maybe I'm too paranoid or you have yet a solution to this... Any thoughts? Jorge-León On Thu, Nov 08, 2001 at 01:59:51PM +, Martin WHEELER wrote: On Thu, 8 Nov 2001, Andre Luis Lopes wrote: Em Qui 08 Nov 2001 10:19, Craigsc escreveu: ... It's worth it for the web-based administration and archiving alone. ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mailman within VHOST
Hello all, I'm attempting to setup Mailman for just one vhosted user. Once mailman was installed (via apt) I edited the mm_cfg.py to reflect the default url and host. I created a lists. subdomain vhost and made the DocumentRoot the mailman root (/usr/lib/mailman/cgi-bin). Then restarted Apache. When I went to lists.domain/listinfo I get a garbled output. Inbetween the mess I can see it complaining about the UIG/GID but alas the script doesn't tell me what gid/uid it's getting (looks like the script isn't being run correctly to me). Below is the vhost entry and it's corresponding Directory directive. Please forgive the dropping of domain/ip data, it's not needed. Note that I've attempted to use User and Group directives to set the uid/gid to: www-data (should be the default for any host w/o a user/group directive anyway) and the list user. I also set the MAILMAN_UID and MAILMAN_GID to list and www-data to no avail. Any insight would be wonderful. VirtualHost [IP] # User list - Also tried manually setting to www-data # Group list - Same as above DocumentRoot /usr/lib/mailman/cgi-bin ServerName lists.[domain] /VirtualHost Directory /usr/lib/mailman/cgi-bin Options ExecCGI /Directory --- A.Sleep -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mailman within VHOST
Hello all, I'm attempting to setup Mailman for just one vhosted user. Once mailman was installed (via apt) I edited the mm_cfg.py to reflect the default url and host. I created a lists. subdomain vhost and made the DocumentRoot the mailman root (/usr/lib/mailman/cgi-bin). Then restarted Apache. When I went to lists.domain/listinfo I get a garbled output. Inbetween the mess I can see it complaining about the UIG/GID but alas the script doesn't tell me what gid/uid it's getting (looks like the script isn't being run correctly to me). Below is the vhost entry and it's corresponding Directory directive. Please forgive the dropping of domain/ip data, it's not needed. Note that I've attempted to use User and Group directives to set the uid/gid to: www-data (should be the default for any host w/o a user/group directive anyway) and the list user. I also set the MAILMAN_UID and MAILMAN_GID to list and www-data to no avail. Any insight would be wonderful. VirtualHost [IP] # User list - Also tried manually setting to www-data # Group list - Same as above DocumentRoot /usr/lib/mailman/cgi-bin ServerName lists.[domain] /VirtualHost Directory /usr/lib/mailman/cgi-bin Options ExecCGI /Directory --- A.Sleep
multiple mailman for virtual domains
hello, is there a way of using the debian package mailman in woody for multiple mailman installs -- one mailman for each virtual domain. i would like to make a set up like discribed in the /usr/doc/mailman/README.EXIM.gz where it explains in the end to set up a mailman install per v-domain. do have to use the mailman sources in this cas ? thank you, -- jens-ingo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman exim
Hello Martin On 28 Aug 2001, at 12:50, Martin WHEELER wrote: 2001-08-28 12:14:52 15bhjt-SE-00 Neither the system_aliases director nor the address_pipe transport set a uid for local delivery of |/var/lib/mailman/mail/wrapper post listname-l Look in exim.conf for a block similar to this system_aliases: driver = aliasfile file_transport = address_file pipe_transport = address_pipe file = /etc/aliases search_type = lsearch user = list and add the last line user = list or perhaps user = mailman and see if that helps. Otherwise read the exim documentation. The FAQ on www.exim.org can be very useful. Have fun Ian Forbes - Ian Forbes ZSD http://www.zsd.co.za Office: +27 +21 683-1388 Fax: +27 +21 64-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mailman error
On Fri, 18 Aug 2000, Ed Kai wrote: I'm not sure why mailman is trying to use a majordomo script...Any help is you're using sendmail with smrsh enabled look at the smrsh root dir, and modify the ``wrapper'' link to point to mailman's wrapper instead of majordomo's wrapper -- [-] ``And there are plenty of other innovative pieces of software such as Napster and ICQ.'' -- comment on ``Systems Software Research is Irrelevant'' at http://freshmeat.net/news/2000/08/05/965534399.html
mailman error
Hello,
I'm trying to configure mailman on a machine running slink. When I try to
subscribe a user, I get this error:
- The following addresses had permanent fatal errors -
"|/var/lib/mailman/mail/wrapper mailcmd testlist"
(expanded from: [EMAIL PROTECTED])
- Transcript of session follows -
Traceback (innermost last):
File "/usr/lib/majordomo/mailcmd", line 49, in ?
list = MailList.MailList(sys.argv[1])
File "/usr/lib/mailman/Mailman/MailList.py", line 60, in __init__
self.Load()
File "/usr/lib/mailman/Mailman/MailList.py", line 771, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info
554 "|/var/lib/mailman/mail/wrapper mailcmd testlist"... unknown mailer
error 1
I'm not sure why mailman is trying to use a majordomo script...Any help is
appreciated. Thanks!
-Ed
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mailman error
Hello, I'm trying to configure mailman on a machine running slink. When I try to subscribe a user, I get this error: - The following addresses had permanent fatal errors - |/var/lib/mailman/mail/wrapper mailcmd testlist (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - Traceback (innermost last): File /usr/lib/majordomo/mailcmd, line 49, in ? list = MailList.MailList(sys.argv[1]) File /usr/lib/mailman/Mailman/MailList.py, line 60, in __init__ self.Load() File /usr/lib/mailman/Mailman/MailList.py, line 771, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info 554 |/var/lib/mailman/mail/wrapper mailcmd testlist... unknown mailer error 1 I'm not sure why mailman is trying to use a majordomo script...Any help is appreciated. Thanks! -Ed Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
