Delivery error to virtual list
Can someone please point me in the right direction. I have just recently built Mailman for virtual domains. I have followed the guidelines on section 6.2.12 (Virtual Domains) {http://www.list.org/mailman-install/node28.html}. I am using Exim 4.80 and Mailman 2.1.14 on a FreeBSD 9.1. The error on trying to deliver message to a created list comes back as "unknown user", eg.
exim -bt createdlist@mydomain.com createdlist@mydomain.com is undeliverable: Unknown user
I am not sure if my error is on my transport or router configuration. Would very much appreciate some help.
Many thanks,
Netsai.
On 12/16/2013 07:41 PM, MP Netsai wrote:
Those instructions assume you are running a separate Mailman instance for each domain. Is this what you want? The more usual case is a single instance with the restriction that list names must be globally unique.
Without seeing your Exim router and transport definitions for Mailman, we can't guess what the problem might be.
Also, see the note at the beginning of <http://www.list.org/mailman-install/node16.html>, i.e. follow <http://www.exim.org/howto/mailman21.html> rather than the Mailman installation manual for Exim 4
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 17/12/2013 09:11 AM, Mark Sapiro wrote:
What I would rather need to have is a single instance of Mailman handling several domains with their separate urls. Not sure if that makes any sense?
My current working configuration on the single domain has the following router:
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.pck
local_part_suffix_optional
local_part_suffix = -admin :
-bounces : -bounces+* :
-confirm : -confirm+* :
-join : -leave :
-owner : -request :
-subscribe : -unsubscribe
transport = mailman_transport
and its transport:
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
Which according to the instructions I mentioned previously I had changed the router part as:
require_files = /virtual/${domain}/mailman/lists/${lc:$local_part}/config.pck
and the transport part:
command = /virtual/${domain}/mailman/mail/mailman
${if def:local_part_suffix
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}}
{post}}
$local_part
current_directory = /virtual/${domain}/mailman
home_directory = /virtual/${domain}/mailman
These are the changes I made hoping that they would handle my virtual domains. That is when I started getting the delivery errors.
Noted. I am changing my configs accordingly according to this and see if there are any changes.
Many thanks,
Netsai.
On 12/18/2013 06:32 PM, MP Netsai wrote:
It makes sense, but it carries the restriction that list names must be globally unique. I.e. if you have a list1@domain.one, you can't have a separate list1@domain.two.
The above router and transport should be OK.
Because these assume each domain has it's own mailman instance in /virtual/DOMAIN.NAME/mailman and these didn't exist in your case.
In other words, you don't need to change anything in Exim for virtual domains with a single Mailman instance, but you do need an
add_virtualhost('virtual.web.domain', 'virtual.email.domain')
line in mm_cfg.py for each virtual host in addition to defining the hosts and their host specific Mailman stuff in the web server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/16/2013 07:41 PM, MP Netsai wrote:
Those instructions assume you are running a separate Mailman instance for each domain. Is this what you want? The more usual case is a single instance with the restriction that list names must be globally unique.
Without seeing your Exim router and transport definitions for Mailman, we can't guess what the problem might be.
Also, see the note at the beginning of <http://www.list.org/mailman-install/node16.html>, i.e. follow <http://www.exim.org/howto/mailman21.html> rather than the Mailman installation manual for Exim 4
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 17/12/2013 09:11 AM, Mark Sapiro wrote:
What I would rather need to have is a single instance of Mailman handling several domains with their separate urls. Not sure if that makes any sense?
My current working configuration on the single domain has the following router:
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.pck
local_part_suffix_optional
local_part_suffix = -admin :
-bounces : -bounces+* :
-confirm : -confirm+* :
-join : -leave :
-owner : -request :
-subscribe : -unsubscribe
transport = mailman_transport
and its transport:
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
Which according to the instructions I mentioned previously I had changed the router part as:
require_files = /virtual/${domain}/mailman/lists/${lc:$local_part}/config.pck
and the transport part:
command = /virtual/${domain}/mailman/mail/mailman
${if def:local_part_suffix
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}}
{post}}
$local_part
current_directory = /virtual/${domain}/mailman
home_directory = /virtual/${domain}/mailman
These are the changes I made hoping that they would handle my virtual domains. That is when I started getting the delivery errors.
Noted. I am changing my configs accordingly according to this and see if there are any changes.
Many thanks,
Netsai.
On 12/18/2013 06:32 PM, MP Netsai wrote:
It makes sense, but it carries the restriction that list names must be globally unique. I.e. if you have a list1@domain.one, you can't have a separate list1@domain.two.
The above router and transport should be OK.
Because these assume each domain has it's own mailman instance in /virtual/DOMAIN.NAME/mailman and these didn't exist in your case.
In other words, you don't need to change anything in Exim for virtual domains with a single Mailman instance, but you do need an
add_virtualhost('virtual.web.domain', 'virtual.email.domain')
line in mm_cfg.py for each virtual host in addition to defining the hosts and their host specific Mailman stuff in the web server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
MP Netsai