Re: [Mailman-Users] virtual domain confusion
Quoting Mark Sapiro m...@msapiro.net: I didn't think to mention in my previous reply, but the above is only meaningful if you also are already using Mailman/Postfix integration - i.e. you have MTA = 'Postfix' in mm_cfg.py. Assuming you are doing this, you may also need to add Mailman's data/virtual-mailman (which will be created along with your first humansci.org list) to Postfix's virtual_alias_maps in main.cf. See http://www.list.org/mailman-install/postfix-virtual.html This, thankfully, is present. Unfortunately, there appear to be some boobytraps with Postfix's virtual_alias_maps that are forcing me to set this aside for now. My existing set-up hadn't been using them; trying to introduce them created some temporary failures and probably lost some (but not all) mail. There's simply way too much I don't understand with postfix. Thanks! -- David Benfell benf...@parts-unknown.org pgp89lUkgyU78.pgp Description: PGP Digital Signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain confusion
Quoting Mark Sapiro m...@msapiro.net:
On 03/24/2015 11:55 AM, David Benfell wrote:
I'm trying to figure out virtual domains with mailman (and, yes,
postfix). I have added
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['humansci.org']
to my mm_cfg.py
You probable also need
add_virtualhost('www.humansci.org', 'humansci.org')
Ah. This helps considerably. The documentation I was finding on that
declarative wasn't shedding any light for me.
in mm_cfg.py (assuming www.humansci.org is the web domain and
humansci.org is the email domain).
Go to http://www.humansci.org/mailman/create or whatever the appropriate
path is for Mailman CGIs in your installation with the web domain of
this host and create the list, or use bin/newlist with
--urlhost=www.humansci.org.
So that's the option to use even though my mailman installation is on
mail.parts-unknown.org.
Thanks very much!
--
David Benfell benf...@parts-unknown.org
pgpmf64Kr7hXO.pgp
Description: PGP Digital Signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain confusion
On 03/24/2015 11:24 PM, David Benfell wrote: Unfortunately, there appear to be some boobytraps with Postfix's virtual_alias_maps that are forcing me to set this aside for now. My existing set-up hadn't been using them; trying to introduce them created some temporary failures and probably lost some (but not all) mail. There's simply way too much I don't understand with postfix. You may also need to add the domain to Postfix's virtual_alias_domains -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain confusion
Quoting Mark Sapiro m...@msapiro.net: On 03/24/2015 11:24 PM, David Benfell wrote: Unfortunately, there appear to be some boobytraps with Postfix's virtual_alias_maps that are forcing me to set this aside for now. My existing set-up hadn't been using them; trying to introduce them created some temporary failures and probably lost some (but not all) mail. There's simply way too much I don't understand with postfix. You may also need to add the domain to Postfix's virtual_alias_domains It appears that for my purposes, I don't need to mess with virtual aliases at all. As near as I can tell mailman is perfectly happy to accept the alternative domain name in the general configuration screen and will send emails out using that domain. And of course the alias declarations are not domain specific (unless one wanders into virtual alias domains). That's *really* all I needed. Thanks! -- David Benfell benf...@parts-unknown.org pgpuwdLf7Zo26.pgp Description: PGP Digital Signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain confusion
On 03/24/2015 11:55 AM, David Benfell wrote: Hi all, I'm trying to figure out virtual domains with mailman (and, yes, postfix). I have added POSTFIX_STYLE_VIRTUAL_DOMAINS = ['humansci.org'] to my mm_cfg.py I didn't think to mention in my previous reply, but the above is only meaningful if you also are already using Mailman/Postfix integration - i.e. you have MTA = 'Postfix' in mm_cfg.py. Assuming you are doing this, you may also need to add Mailman's data/virtual-mailman (which will be created along with your first humansci.org list) to Postfix's virtual_alias_maps in main.cf. See http://www.list.org/mailman-install/postfix-virtual.html -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] virtual domain confusion
Hi all, I'm trying to figure out virtual domains with mailman (and, yes, postfix). I have added POSTFIX_STYLE_VIRTUAL_DOMAINS = ['humansci.org'] to my mm_cfg.py But when I go to my administration page, I see no option to create a list under that domain. How is this supposed to be done? Thanks! -- David Benfell benf...@parts-unknown.org pgpsN0poLvr71.pgp Description: PGP Digital Signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain confusion
On 03/24/2015 11:55 AM, David Benfell wrote:
I'm trying to figure out virtual domains with mailman (and, yes,
postfix). I have added
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['humansci.org']
to my mm_cfg.py
You probable also need
add_virtualhost('www.humansci.org', 'humansci.org')
in mm_cfg.py (assuming www.humansci.org is the web domain and
humansci.org is the email domain).
But when I go to my administration page, I see no option to create a
list under that domain. How is this supposed to be done?
Go to http://www.humansci.org/mailman/create or whatever the appropriate
path is for Mailman CGIs in your installation with the web domain of
this host and create the list, or use bin/newlist with
--urlhost=www.humansci.org.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain and alias_maps
Hey... reporting success! The problem has resolved after changing permissions for files residing in the /etc/mailman (data) directory to: mailman:mailman The timestamps were ok Well actually, mailman:mailman is what I did for the 'aliases' file but (accidentally) not for 'virtual mailman' (was root:mailman). But it all works! When you have exhausted your own supply of ideas, getting help this way from experts giving their time on an honorary basis is absolutely fantastic! For anyone searching the archives, the location of the data dir is actually specified in /usr/lib/mailman/Mailman/Defaults.py under 'CONFIG_DIR' Thanks again! Michael Mailman 2.1.9 What are the ownership and permissions on /etc/mailman/aliases.db. Is the time stamp of this as recent as that on /etc/mailman/aliases? Are there any Postfix log entries related to /etc/mailman/aliases? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain and alias_maps
Thanks for the advice; I found the *data directory* in /etc/mailman/,
along with the 'genaliases' produced files that I had been unable to
locate
So I reconfigured postfix with:
alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases
(I know someone said above this wasn't needed)
AND
virtual_alias_maps = hash:/etc/postfix/virtual,
hash:/etc/mailman/virtual-mailman
So, now, at least email sent to the list server address
(disc...@cpddomain.org.au) seems to reach the mailserver, but the maillog
shows its rejected as an unknown user:
to=disc...@main-domain.au, orig_to=disc...@cpddomain.org.au,
relay=local, delay=0.09, delays=0.08/0.01/0/0.01, dsn=5.1.1,
status=bounced (unknown user: discuss)
Where 'discuss@cpddomain' is the list-server email address given in the
welcome email, but which seems to be reconfigured as an email addressed to
the main (non-virtual) domain on the system
I don't have a specific entry in my vmailbox file for
disc...@cpddomain.org.au...I didn't think that was needed
The other anomaly is that the relevant alias entries appear both in
/etc/mailman/aliases:
# STANZA START: discuss
# CREATED: Fri Aug 16 16:38:08 2013
discuss: |/usr/lib/mailman/mail/mailman post discuss
discuss-admin: |/usr/lib/mailman/mail/mailman admin discuss
discuss-bounces: |/usr/lib/mailman/mail/mailman bounces discuss
discuss-confirm: |/usr/lib/mailman/mail/mailman confirm discuss
discuss-join:|/usr/lib/mailman/mail/mailman join discuss
discuss-leave: |/usr/lib/mailman/mail/mailman leave discuss
discuss-owner: |/usr/lib/mailman/mail/mailman owner discuss
discuss-request: |/usr/lib/mailman/mail/mailman request discuss
discuss-subscribe: |/usr/lib/mailman/mail/mailman subscribe discuss
discuss-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe discuss
# STANZA END: discuss
and in /etc/mailman/virtual-mailman:
# STANZA START: discuss
# CREATED: Fri Aug 16 16:38:08 2013
disc...@cpddomain.org.au discuss
discuss-ad...@cpddomain.org.audiscuss-admin
discuss-boun...@cpddomain.org.au discuss-bounces
discuss-conf...@cpddomain.org.au discuss-confirm
discuss-j...@cpddomain.org.au discuss-join
discuss-le...@cpddomain.org.audiscuss-leave
discuss-ow...@cpddomain.org.audiscuss-owner
discuss-requ...@cpddomain.org.au discuss-request
discuss-subscr...@cpddomain.org.audiscuss-subscribe
discuss-unsubscr...@cpddomain.org.au discuss-unsubscribe
# STANZA END: discuss
Hopefully a solution is not far away!
Michael
On 08/15/2013 07:02 PM, Dr Michael Daly wrote:
I should say the mailman version is 2.1.9, which was installed via an
'apt-get' command on a centos package.
Then I should say see the FAQ at http://wiki.list.org/x/OIDD.
In mm_cfg.py I have:
('cpddomain.org.au' is not the real domain name, but it is a virtual
one)
At present a subscriber can send a message to the list owner, but no
others, and the message does NOT have the expected Subject Line prefix
eg
[List name]
By addressing the owner's email or LISTNAME-owner@... ? Either way, the
lack of a subject_prefix is normal?
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values. #
# Note - if you're looking for something that is imported from mm_cfg,
but
you
# didn't find it above, it's probably in Defaults.py.
#
add_virtualhost('www.cpddomain.org.au', 'cpddomain.org.au')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cpddomain.org.au']
MTA = 'Postfix'
Is the host_name attribute on the list's General Options page
cpddomain.org.au?
With MTA = 'Postfix' genaliases will write Mailman's data/aliases file
with 10 aliases for each list as in item 3 of the FAQ at
http://wiki.list.org/x/A4E9. In addition, it will write
data/virtual-mailman with virtual mapping for each list whose host_name
is cpddomain.org.au. It will also invoke the commands defined in the
Defaults.py settings
POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/sbin/postmap'
to create/update data/aliases.db and data/virtual-mailman.db. If you
don't see this, it's because the data directory is not in
/usr/lib/mailman/. See the FAQ at http://wiki.list.org/x/KYCB
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/gp%40holisticgp.com.au
Dr Michael Daly MB, BS
GradDip(Integrative Medicine), GradCert(Evidence Based Practice),
M Bus(Information Innovation),
Re: [Mailman-Users] virtual domain and alias_maps
On 08/16/2013 01:17 AM, Dr Michael Daly wrote: So I reconfigured postfix with: alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases (I know someone said above this wasn't needed) And that was bad advice. It is needed. See below. AND virtual_alias_maps = hash:/etc/postfix/virtual, hash:/etc/mailman/virtual-mailman So, now, at least email sent to the list server address (disc...@cpddomain.org.au) seems to reach the mailserver, but the maillog shows its rejected as an unknown user: to=disc...@main-domain.au, orig_to=disc...@cpddomain.org.au, relay=local, delay=0.09, delays=0.08/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: discuss) Where 'discuss@cpddomain' is the list-server email address given in the welcome email, but which seems to be reconfigured as an email addressed to the main (non-virtual) domain on the system That is as it should be except for the ultimate 'unknown user' which I don't fully understand. I don't have a specific entry in my vmailbox file for disc...@cpddomain.org.au...I didn't think that was needed It's not. The other anomaly is that the relevant alias entries appear both in /etc/mailman/aliases: This is as it should be. # STANZA START: discuss # CREATED: Fri Aug 16 16:38:08 2013 discuss: |/usr/lib/mailman/mail/mailman post discuss discuss-admin: |/usr/lib/mailman/mail/mailman admin discuss discuss-bounces: |/usr/lib/mailman/mail/mailman bounces discuss discuss-confirm: |/usr/lib/mailman/mail/mailman confirm discuss discuss-join:|/usr/lib/mailman/mail/mailman join discuss discuss-leave: |/usr/lib/mailman/mail/mailman leave discuss discuss-owner: |/usr/lib/mailman/mail/mailman owner discuss discuss-request: |/usr/lib/mailman/mail/mailman request discuss discuss-subscribe: |/usr/lib/mailman/mail/mailman subscribe discuss discuss-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe discuss # STANZA END: discuss The above are the aliases that cause mail to the local addresses 'discuss' and 'discuss-*' to be appropriately piped to Mailman. and in /etc/mailman/virtual-mailman: # STANZA START: discuss # CREATED: Fri Aug 16 16:38:08 2013 disc...@cpddomain.org.au discuss discuss-ad...@cpddomain.org.audiscuss-admin discuss-boun...@cpddomain.org.au discuss-bounces discuss-conf...@cpddomain.org.au discuss-confirm discuss-j...@cpddomain.org.au discuss-join discuss-le...@cpddomain.org.audiscuss-leave discuss-ow...@cpddomain.org.audiscuss-owner discuss-requ...@cpddomain.org.au discuss-request discuss-subscr...@cpddomain.org.audiscuss-subscribe discuss-unsubscr...@cpddomain.org.au discuss-unsubscribe # STANZA END: discuss These are virtual mappings that map virtual addresses like discuss(-*)@cpddomain.org.au to local addresses discuss(-*). This part is working correctly per the part of the log message that says to=disc...@main-domain.au, orig_to=disc...@cpddomain.org.au,, however the part that says relay=local, ... status=bounced (unknown user: discuss) is saying that for some reason, the alias discuss: |/usr/lib/mailman/mail/mailman post discuss is not being processed by Postfix even though the message is being handled by the 'local' transport. What are the ownership and permissions on /etc/mailman/aliases.db. Is the time stamp of this as recent as that on /etc/mailman/aliases? Are there any Postfix log entries related to /etc/mailman/aliases? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] virtual domain and alias_maps
Hi I am having problems getting mail delivered to list members, on a virtual domain. This did not happen when a conventional ie non virtual, domain. Maybe there is a problem with aliases...I had to manually create the /usr/lib/mailman/data dir and both the 'alias' and 'virtual-mailman' files in that dir (not sure of what contents should be in the described 'alias' and 'virtual-mailman' files) But running genaliases does not create the expected .db files ownership /permissions on those two files are apache:mailman and 664 In postfix I have: alias_maps = hash:/etc/aliases, hash:/usr/lib/mailman/data/aliases virtual_alias_maps = hash:/etc/postfix/virtual, hash:/usr/lib/mailman/data/virtual-mailman and I have created the list and configured mm_cfg.py as specified Thanks Michael -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain and alias_maps
On 08/15/2013 06:06 AM, Dr Michael Daly wrote: and I have created the list and configured mm_cfg.py as specified And what is in mm_cfg.py? Specifically do you have MTA = 'Postfix' and POSTFIX_STYLE_VIRTUAL_DOMAINS = ['the.lists.email.hostname'] See http://www.list.org/mailman-install/node12.html. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain and alias_maps
Michael Daly wrote: Hi I am having problems getting mail delivered to list members, on a virtual domain. This did not happen when a conventional ie non virtual, domain. Maybe there is a problem with aliases...I had to manually create the /usr/lib/mailman/data dir and both the 'alias' and 'virtual-mailman' files in that dir (not sure of what contents should be in the described 'alias' and 'virtual-mailman' files) But running genaliases does not create the expected .db files What output do you get after running it? In postfix I have: alias_maps = hash:/etc/aliases, hash:/usr/lib/mailman/data/aliases Not required. virtual_alias_maps = hash:/etc/postfix/virtual, hash:/usr/lib/mailman/data/virtual-mailman Yes. and I have created the list and configured mm_cfg.py as specified So you set MTA to Postfix and populated POSTFIX_STYLE_VIRTUAL_DOMAINS to your virtual domains? Thanks. Andrew. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain and alias_maps
Hi
Running genaliases produces NO output, just a carriage return. Running
genaliases -h
produces the relevant help information
I should say the mailman version is 2.1.9, which was installed via an
'apt-get' command on a centos package.
In mm_cfg.py I have:
('cpddomain.org.au' is not the real domain name, but it is a virtual one)
At present a subscriber can send a message to the list owner, but no
others, and the message does NOT have the expected Subject Line prefix eg
[List name]
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.#
# Note - if you're looking for something that is imported from mm_cfg, but
you
# didn't find it above, it's probably in Defaults.py.
#
add_virtualhost('www.cpddomain.org.au', 'cpddomain.org.au')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cpddomain.org.au']
MTA = 'Postfix'
Thanks
Michael
Michael Daly wrote:
Hi
I am having problems getting mail delivered to list members, on a virtual
domain. This did not happen when a conventional ie non virtual, domain.
Maybe there is a problem with aliases...I had to manually create the
/usr/lib/mailman/data dir and both the 'alias' and 'virtual-mailman'
files in that dir
(not sure of what contents should be in the described 'alias' and
'virtual-mailman' files)
But running genaliases does not create the expected .db files
What output do you get after running it?
In postfix I have:
alias_maps = hash:/etc/aliases, hash:/usr/lib/mailman/data/aliases
Not required.
virtual_alias_maps = hash:/etc/postfix/virtual,
hash:/usr/lib/mailman/data/virtual-mailman
Yes.
and I have created the list and configured mm_cfg.py as specified
So you set MTA to Postfix and populated POSTFIX_STYLE_VIRTUAL_DOMAINS
to your virtual domains?
Thanks.
Andrew.
Dr Michael Daly MB, BS
GradDip(Integrative Medicine), GradCert(Evidence Based Practice),
M Bus(Information Innovation), GradDip(Document Management)
03 9521 0352
0413 879 029
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain and alias_maps
On 08/15/2013 07:02 PM, Dr Michael Daly wrote:
I should say the mailman version is 2.1.9, which was installed via an
'apt-get' command on a centos package.
Then I should say see the FAQ at http://wiki.list.org/x/OIDD.
In mm_cfg.py I have:
('cpddomain.org.au' is not the real domain name, but it is a virtual one)
At present a subscriber can send a message to the list owner, but no
others, and the message does NOT have the expected Subject Line prefix eg
[List name]
By addressing the owner's email or LISTNAME-owner@... ? Either way, the
lack of a subject_prefix is normal?
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values. #
# Note - if you're looking for something that is imported from mm_cfg, but
you
# didn't find it above, it's probably in Defaults.py.
#
add_virtualhost('www.cpddomain.org.au', 'cpddomain.org.au')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['cpddomain.org.au']
MTA = 'Postfix'
Is the host_name attribute on the list's General Options page
cpddomain.org.au?
With MTA = 'Postfix' genaliases will write Mailman's data/aliases file
with 10 aliases for each list as in item 3 of the FAQ at
http://wiki.list.org/x/A4E9. In addition, it will write
data/virtual-mailman with virtual mapping for each list whose host_name
is cpddomain.org.au. It will also invoke the commands defined in the
Defaults.py settings
POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/sbin/postmap'
to create/update data/aliases.db and data/virtual-mailman.db. If you
don't see this, it's because the data directory is not in
/usr/lib/mailman/. See the FAQ at http://wiki.list.org/x/KYCB
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] virtual domain https and admin interface
Hello, I have mailman 2.1.14 running on OS X Server 10.6.8 One list runs on a virtual domain. All webpages for the list are addressed via https. I achieved that with a redirect rule in apache, it simply redirects all http of that domain to https. That works fine so far, but when I try to approve the message of a moderated user nothing happens, the page just gets reloaded with no change. What I'm missing here? thanks Matthias -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain https and admin interface
Am 29.01.2013 um 18:27 schrieb Matthias Schmidt:
Hello,
I have mailman 2.1.14 running on OS X Server 10.6.8
One list runs on a virtual domain.
All webpages for the list are addressed via https.
I achieved that with a redirect rule in apache, it simply redirects all http
of that domain to https.
That works fine so far, but when I try to approve the message of a moderated
user nothing happens, the page just gets reloaded with no change.
What I'm missing here?
hmm, I found this:
http://wiki.list.org/display/DOC/4.27+Securing+Mailman's+web+GUI+by+using+Secure+HTTP-SSL
and followed these advice, but now it still doesn't work and on top of it I get
redicted to the default url host with the login page after trying to accept a
moderated mail.
mm_cfg.py looks like this:
MTA = 'Postfix'
DEFAULT_EMAIL_HOST = 'mcgregor.admilon.net'
DEFAULT_URL_HOST = 'mcgregor.admilon.net'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
VIRTUAL_HOSTS.clear()
add_virtualhost('www.virtualA.com', 'virtualA.com')
add_virtualhost('liste.virtualB.com', 'virtualB.com')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virtualA.com','virtualB.com']
thanks
Matthias
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain https and admin interface
Matthias Schmidt wrote:
hmm, I found this:
http://wiki.list.org/display/DOC/4.27+Securing+Mailman's+web+GUI+by+using+Secure+HTTP-SSL
and followed these advice, but now it still doesn't work and on top of it I
get redicted to the default url host with the login page after trying to
accept a moderated mail.
mm_cfg.py looks like this:
MTA = 'Postfix'
DEFAULT_EMAIL_HOST = 'mcgregor.admilon.net'
DEFAULT_URL_HOST = 'mcgregor.admilon.net'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
VIRTUAL_HOSTS.clear()
add_virtualhost('www.virtualA.com', 'virtualA.com')
add_virtualhost('liste.virtualB.com', 'virtualB.com')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virtualA.com','virtualB.com']
You need to run
bin/withlist -r fix_url -l LISTNAME -u xxx
where xxx is either www.virtualA.com or liste.virtualB.com as
appropriate for the list. It seems you ran fix_url, but without the -u
option for the list's web domain.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual Domain Hosting
On 08/10/2012 11:44, Mark Sapiro wrote: David Dodell wrote: Do I need to do something in postfix to get mailman to recognize these when the mailman list is virtual? See http://www.list.org/mailman-install/postfix-virtual.html. When to the link above and found the following paragraph. - start Note: This section describes how to integrate Mailman with Postfix for automatic generation of Postfix virtual_alias_maps for Mailman list addresses. Mailman's support of virtual domains is limited in that list names must be globally unique within a single Mailman instance, i.e., two lists may not have the same name even if they are in different domains. - end Is this true for all versions of mailman? So there is no way to have mailling list called supp...@example.com and support@example_two.com on the same server. Is there some work around? P.V.Anthony -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual Domain Hosting
P.V.Anthony writes: Is this true for all versions of mailman? All versions so far released by this project, yes. cPanel and maybe some other third-party distributions have patched versions of Mailman that allow one instance of Mailman to handle multiple domains with independent namespaces for lists. The patch is a kludge, not easy to get your hands on, and cPanel Mailman itself is a high price to pay (once you mention cPanel, you have to put up with references to the FAQ explaining why we often can't help with cPanel problems in every reply you get, and you probably lose a lot of people who wold otherwise be helpful as soon as you mention cPanel). There's another third-party patch, I believe; probably mentioned in the FAQ somewhere. Also a kludge, which looks fragile and has not been proved in heavy testing in practice (it's actually not as common a need as you might think, what with hosting on virtual machines). So despite occasional requests, it has never been added to the Mailman 2 distribution (the developers would rather devote the effort to Mailman 3). Speaking of which ... the virtual domain issue will be dealt with differently in Mailman 3. The whole infrastructure for dealing with lists and with users has been redesigned from the ground up. But Mailman 3 is most likely not ready for you -- come back in about a year. So there is no way to have mailling list called supp...@example.com and support@example_two.com on the same server. That's right. However, here, server refers to a set of OS processes and its associated metadata. You can serve multiple domains from a single *host* without worrying about namespace collisions, by keeping multiple installations of Mailman, one for each domain, and starting a new set of processes to serve each one. It might even be possible to have a single shared instance of Mailman, and arrange that host configuration data be private to each Mailman process. But that would be a little fragile, I think, and might require minor code changes. I would guess it probably scales to a few-score domains on the same hardware that would adequately support a given number of lists. The common case of a single server supporting a commercial domain and an open source domain for users without support contracts would be no sweat for this setup, even if you have a couple of products with their own domains. Steve -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual Domain Hosting
On 12/10/2012 00:29, Stephen J. Turnbull wrote: I would guess it probably scales to a few-score domains on the same hardware that would adequately support a given number of lists. The common case of a single server supporting a commercial domain and an open source domain for users without support contracts would be no sweat for this setup, even if you have a couple of products with their own domains. Thank you very much for the clear and detailed reply. I do appreciate it. P.V.Anthony -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Virtual Domain Hosting
I finally have Mailman working well on my OSX box ... as long as the domain I'm hosting the list is the main one for the box. I setup a testlist today under the name virtualt...@virtualdomain.org I host virtualdomain.org on my box. However, when mail is sent to virtualt...@virtualdomain.org; it is rejected as an unknown user. Do I need to do something in postfix to get mailman to recognize these when the mailman list is virtual? Thanks David -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual Domain Hosting
David Dodell wrote: Do I need to do something in postfix to get mailman to recognize these when the mailman list is virtual? See http://www.list.org/mailman-install/postfix-virtual.html. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] virtual domain list disclosure and list email link issue
Hello all!, I spent most of the day wrestling mailman and postfix into a multi site installation and now I have it working, except there are a few issues I am still trying to work out. The first is that even though I have VIRTUAL_HOST_OVERVIEW = Yes in my Mailman/mm_cfg.py file I am still able to disclose other lists on other domains through the url: http://virtual_domain/mailman/listinfo/list_name_not_in_virtual_domain. There must be a another way around this, if not it should be considered a minor security flaw. Can anyone point me in the right direction for preventing this? The second issue is that all emails from the list are coming with links from the wrong domain. How can I get these links to reflect the domain that the lists are for? Thanks in advance. -Dennis -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain list disclosure and list email linkissue
Dennison Williams wrote:
The first is that even though I have VIRTUAL_HOST_OVERVIEW = Yes in
my Mailman/mm_cfg.py file I am still able to disclose other lists on
other domains through the url:
http://virtual_domain/mailman/listinfo/list_name_not_in_virtual_domain.
There must be a another way around this, if not it should be considered
a minor security flaw. Can anyone point me in the right direction for
preventing this?
VIRTUAL_HOST_OVERVIEW controls what it's name implies, i.e. what lists
appear on the listinfo and admin overview page. It is true, that by
trying URLs such as you give above, that one could confirm the
existence of a list in another domain and find its domain name from
its listinfo page. If this is really a security issue for you, there
are two choices.
1) Modify all the Mailman/Cgi/*.py modules along the lines of the
attached listinfo.patch.txt, or
2) Install a separate Mailman instance for each domain.
The second issue is that all emails from the list are coming with links
from the wrong domain. How can I get these links to reflect the domain
that the lists are for?
Web links or email links? If the web links are wrong, the lists must
also appear on the wrong listinfo overview page. In any case, make
sure every host has a correct
add_virtualhost('hosts.web.domain', 'hosts.email.domain')
in mm_cfg.py. Then run Mailman's
bin/withlist -l -r fix_url listname -u web.host.for.this.list
for every list. This will fix both web and email domains. Or, if the
problem is only email domains, you can go to the web admin General
Options page for every list and set the correct host_name attribute
near the bottom of the page.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--- listinfo.py 2010-01-28 13:55:59.328125000 -0800
+++ listinfox.py2010-04-16 08:01:45.953125000 -0700
@@ -52,6 +52,15 @@
listinfo_overview(_('No such list em%(safelistname)s/em'))
syslog('error', 'No such list %s: %s', listname, e)
return
+hostname = Utils.get_domain()
+if mm_cfg.VIRTUAL_HOST_OVERVIEW and \
+ mlist.web_page_url.find('/%s/' % hostname) == -1:
+# List is for different identity of this host - say not found.
+# Avoid cross-site scripting attacks
+safelistname = Utils.websafe(listname)
+listinfo_overview(_('No such list em%(safelistname)s/em'))
+syslog('error', 'No such list %...@%s', listname, hostname)
+return
# See if the user want to see this page in other language
cgidata = cgi.FieldStorage()
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain list disclosure and list email linkissue
Thanks for your prompt response and your work on mailman.
Mark Sapiro wrote:
Dennison Williams wrote:
The first is that even though I have VIRTUAL_HOST_OVERVIEW = Yes in
my Mailman/mm_cfg.py file I am still able to disclose other lists on
other domains through the url:
http://virtual_domain/mailman/listinfo/list_name_not_in_virtual_domain.
There must be a another way around this, if not it should be considered
a minor security flaw. Can anyone point me in the right direction for
preventing this?
VIRTUAL_HOST_OVERVIEW controls what it's name implies, i.e. what lists
appear on the listinfo and admin overview page. It is true, that by
trying URLs such as you give above, that one could confirm the
existence of a list in another domain and find its domain name from
its listinfo page. If this is really a security issue for you, there
are two choices.
1) Modify all the Mailman/Cgi/*.py modules along the lines of the
attached listinfo.patch.txt, or
2) Install a separate Mailman instance for each domain.
OK. I think the proper method for this installation is separate mailman
installations.
The second issue is that all emails from the list are coming with links
from the wrong domain. How can I get these links to reflect the domain
that the lists are for?
Web links or email links? If the web links are wrong, the lists must
also appear on the wrong listinfo overview page. In any case, make
sure every host has a correct
add_virtualhost('hosts.web.domain', 'hosts.email.domain')
in mm_cfg.py. Then run Mailman's
bin/withlist -l -r fix_url listname -u web.host.for.this.list
for every list. This will fix both web and email domains. Or, if the
problem is only email domains, you can go to the web admin General
Options page for every list and set the correct host_name attribute
near the bottom of the page.
The issue was the link supplied in the bottom of emails from lists.
Your advise partially helped me fix it. The pointer to use seperate
email domains though is the solution that will properly solve this for
me. Thanks again.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: I will review your patch, and I used list-domain.tld instead of list.domain.tld, but I basically came to the same conclusion and just implemented same. I got the idea from http://mail.python.org/pipermail/mailman-users/2008-September/063254.html This really needs to be documented somewhere. And by somewhere I recommend you put it into the Mailman Wiki, probably just add it to the FAQs: http://wiki.list.org/display/DOC/Frequently+Asked+Questions I'm guessing it should be in site admin tasks: http://wiki.list.org/display/DOC/4+Site+administrator+tasks So here's a link to a page where you can cut and paste the info that you think should be recorded: http://wiki.list.org/pages/createpage.action?spaceKey=DOCfromPageId=4030488 So if you've got a minute to summarize the stuff and put it there, that would be awesome. Thanks! :) Terri -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Thu, 8 Oct 2009, Terri Oda wrote: Geoff Shang wrote: I will review your patch, and I used list-domain.tld instead of This really needs to be documented somewhere. And by somewhere I recommend you put it into the Mailman Wiki, probably just add it to the FAQs: I'll do this. I probably won't get a chance for a few days as we're still madly setting up stuff over here but I will definitely write up something. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Hi Mark, re multiple installs, On Mon, 5 Oct 2009, Mark Sapiro wrote: The post at http://mail.python.org/pipermail/mailman-users/2004-June/037443.html (linked from the FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030604) has good information. I don't thing there's anything better collected in one place. I'm now working through this and have hit a bit of a problem. The post in question reads as follows: Where thing may get more complicated is setting up your local MTA to support virtual hosts. For instance, aliases generated by the per-host copies of $per-host-prefix/bin/newlist will generate alias definitions that pipe to the correct per-host instance of the Mailman delivery agent script but getting your MTA to recognise the aliases belong to one host rather than another is not something I am familiar with. This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? This must be doable, because if it's not, then this defeats the whole point of doing this in the first place. Presumably I need to do this in postfix/main.cf somehow but I'm at a loss as to how to do this. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? This must be doable, because if it's not, then this defeats the whole point of doing this in the first place. Presumably I need to do this in postfix/main.cf somehow but I'm at a loss as to how to do this. Not sure if this will help you or not, but I'll share anywhere ... I have a multi setup for mailman to host multiple domains. All my list domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'. My mailman installations all go under /home/mailman/lists.$domain I don't know how this is done in postfix, but in sendmail I have the following: = /etc/mail/aliases/$domain-aliases mailman-lists.$domain \ |/home/mailman/lists.$domain/mail/$domain-mailman post mailman mailman-admin-lists.$domain:\ |/home/mailman/lists.$domain/mail/$domain-mailman admin mailman mailman-bounces-lists.$domain: \ |/home/mailman/lists.$domain/mail/$domain-mailman bounces mailman mailman-confirm-lists.$domain: \ |/home/mailman/lists.$domain/mail/$domain-mailman confirm mailman = /etc/mail/virtusertable mail...@lists.$domain mailman-lists.$domain mailman-ad...@lists.$domainmailman-admin-lists.$domain mailman-boun...@lists.$domain mailman-bounces-lists.$domain mailman-conf...@lists.$domain mailman-confirm-lists.$domain This ensures that an incoming e-mail to say for example 'mailman-ad...@lists.$domain' gets rerouted to 'mailman-admin-lists.$domain' which the alias then expands in to '|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman' This allows one to have various mailman@'various domains' going to the same server through the same MTA without it going nutso. Now you may be wondering why I renamed the 'mailman' binary to '$domain-mailman'. That's because of permissions within sendmail. Any binary that is going to be sending stuff out needs to be allowed by sendmail, and since I have multiple installations of mailman, in different paths, you can't just tell sendmail it's called 'mailman'. It will get utterly confused when the various lists are trying to send something out. So, by renaming each one to their respective $domain, it keeps sendmail from going bonkers. In my /usr/adm/sm.bin/ I have various symlinks to $domain-mailman which link back to /home/mailman/lists-$domain/mail/$domain-mailman Cheers -- W | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:ash...@pcraft.com . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 2901 55th Street http://www.pcraft.com . . .. Boulder, CO 80301, U.S.A. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote: Geoff Shang wrote: This would appear to be the sticking point. The aliases file doesn't generate fully-qualified Email addresses, only local parts. How do I ensure that a message to annou...@foo.com doesn't go to annou...@bar.org? [snip] I have a multi setup for mailman to host multiple domains. All my list domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'. My mailman installations all go under /home/mailman/lists.$domain I don't know how this is done in postfix, but in sendmail I have the following: = /etc/mail/aliases/$domain-aliases mailman-lists.$domain \ |/home/mailman/lists.$domain/mail/$domain-mailman post mailman mailman-admin-lists.$domain:\ |/home/mailman/lists.$domain/mail/$domain-mailman admin mailman Ok but how do you get Mailman to produce alias tables that look like that? Or don't you? Mine only have the list address part, not the fully qualified list address. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote:
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
I have a multi setup for mailman to host multiple domains. All my list
domains are configured as 'lists.$domain', for example 'lists.yeehaw.net'.
My mailman installations all go under /home/mailman/lists.$domain
I don't know how this is done in postfix, but in sendmail I have the
following:
= /etc/mail/aliases/$domain-aliases
mailman-lists.$domain \
|/home/mailman/lists.$domain/mail/$domain-mailman post mailman
mailman-admin-lists.$domain:\
|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman
Ok but how do you get Mailman to produce alias tables that look like that?
Or don't you? Mine only have the list address part, not the fully
qualified list address.
For Postfix integration, you need to do a few things.
Consider only the one mailman instance for the domain example.com. The
others will be analagous.
in mm_cfg.py, add
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com']
This will cause mailman to also write data/virtual-mailman with entries
like
l...@example.comlist
list-ad...@example.com list-admin
...
in addition to data/aliases with entries like
list: |path/to/wrapper post list
list-admin: |path/to/wrapper admin list
...
for each list. The data/virtual-mailman(.db) is analagous to Ashley's
/etc/mail/virtusertable.
There is still a problem in that there is a potential list name
conflict, so to resolve that, you need to make a patch (see attached
Postfix.patch.txt) to Mailman/MTA/Postfix to make virtual-mailman and
aliases look like
l...@example.comlist.example.com
list-ad...@example.com list-admin.example.com
...
and
list.example.com: |path/to/wrapper post list
list-admin.example.com: |path/to/wrapper admin list
...
Then you need the following in Postfix's main.cf
alias_maps = ...
hash:/path/to/example.com's/data/aliases
virtual_alias_domains ... example.com
virtual_alias_maps = ...
hash:/path/to/example.com's/data/virtual-mailman
And probably also if you don't have them anyway
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--- f:/test-mailman-2.1/Mailman/MTA/Postfix.py 2008-08-22 15:18:57.0
-0700
+++ f:/test-mailman/Mailman/MTA/Postfix.py 2009-10-07 17:24:52.21875
-0700
@@ -102,14 +102,16 @@
if mlist is None:
return
listname = mlist.internal_name()
+hostname = mlist.host_name
fieldsz = len(listname) + len('-unsubscribe')
# The text file entries get a little extra info
print fp, '# STANZA START:', listname
print fp, '# CREATED:', time.ctime(time.time())
# Now add all the standard alias entries
for k, v in makealiases(listname):
+qname = '%s.%s:' % (k, hostname)
# Format the text file nicely
-print fp, k + ':', ((fieldsz - len(k)) * ' ') + v
+print fp, qname, ((fieldsz - len(k)) * ' ') + v
# Finish the text file stanza
print fp, '# STANZA END:', listname
print fp
@@ -147,7 +149,7 @@
for k, v in makealiases(listname):
fqdnaddr = '%...@%s' % (k, hostname)
# Format the text file nicely
-print fp, fqdnaddr, ((fieldsz - len(k)) * ' '), k
+print fp, fqdnaddr, ((fieldsz - len(k)) * ' '), k + '.' + hostname
# Finish the text file stanza
print fp, '# STANZA END:', listname
print fp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Wed, 7 Oct 2009, Mark Sapiro wrote:
Geoff Shang wrote:
On Wed, 7 Oct 2009, Ashley M. Kirchner wrote:
= /etc/mail/aliases/$domain-aliases
mailman-lists.$domain \
|/home/mailman/lists.$domain/mail/$domain-mailman post mailman
mailman-admin-lists.$domain:\
|/home/mailman/lists.$domain/mail/$domain-mailman admin mailman
Ok but how do you get Mailman to produce alias tables that look like that?
Or don't you? Mine only have the list address part, not the fully
qualified list address.
{snip}
There is still a problem in that there is a potential list name
conflict, so to resolve that, you need to make a patch (see attached
ah...
I will review your patch, and I used list-domain.tld instead of
list.domain.tld, but I basically came to the same conclusion and just
implemented same. I got the idea from
http://mail.python.org/pipermail/mailman-users/2008-September/063254.html
This really needs to be documented somewhere.
does using a dash vs a dot as a separater make any difference re eventual
upgrade path? I'm still testing at this point but I'll be making a lot of
lists soon, so now's the time to change anything.
Thanks again,
Geoff.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: On Wed, 7 Oct 2009, Mark Sapiro wrote: There is still a problem in that there is a potential list name conflict, so to resolve that, you need to make a patch (see attached ah... I will review your patch, and I used list-domain.tld instead of list.domain.tld, but I basically came to the same conclusion and just implemented same. I got the idea from http://mail.python.org/pipermail/mailman-users/2008-September/063254.html This really needs to be documented somewhere. Yes. I'll see about a FAQ. Maybe you could help when you get it all worked through. does using a dash vs a dot as a separater make any difference re eventual upgrade path? I'm still testing at this point but I'll be making a lot of lists soon, so now's the time to change anything. I don't think so. I actually was going to use an underscore, but I went with the dot because Ashley was using a dot. Changing after the fact is not hard. You'd only need to change Mailman/MTA/Postfix.py and run bin/genaliases for each domain. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Mon, 5 Oct 2009, Mark Sapiro wrote: You seem to have done your homework well, and to have a good understanding of the issues. You can learn a lot in 5 hours of reading. :) I found http://ndim.fedorapeople.org/stuff/mailman-vhost/ which appears to contain the same patches that were at http://nix.lauft.net/htdocs/mailman/. Thanks for this. This stuff looks a bit old. It's patches against Mailman 2.1.7 and files seem to date back to 2006. The docs talk about what's going to happen in 2008. Does this code patch against 2.1.12? Is there newer code than this or should I get it from git? And is there any more documentation than the ReadMe files on this site? I thought I saw a branch up in the Launchpad project that deals with this. Is that a better place to start than these patches? Are these patches still the recommended way to achieve what I'm looking for? My concerns right now are: 1. I need to implement this on a production system, so it has to implement the ability to have the same list names on multiple domains and domain-specific site passwords. And it needs to be stable (i.e. it needs to work as advertised). 2. I need to deploy this pretty quickly so I need some documentation or at least people willing to help if I get stuck. and 3. I need to know if the changes proposed here (or anywhere) will be compatible with what will eventually be adopted in mainline, or at least that there will be some kind of migration path. I can't really afford to send us down a dead-end path. I'm sorry about all the questions but I'm a bit under the pump here, but I also want to do it right the first time. Any advice anyone can give will be most gratefully received. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
On Mon, 5 Oct 2009, Mark Sapiro wrote: I just applied the mailman-2.1.7-20060114-to-vhost.patch to the 2.1.12 base and it applied with only two rejects, both of which are easy to fix. Whether the patched code will actually work and meet your requirements, I can't say. I probably can't afford the luxury of testing it, at least not now. I thought I saw a branch up in the Launchpad project that deals with this. Is that a better place to start than these patches? Maybe, but I don't see one at https://code.launchpad.net/mailman?field.lifecycle=ALL. Well it was something like 3 in the morning when I was looking. Let me see... Ok, scrub that. Was something else. Are these patches still the recommended way to achieve what I'm looking for? I don't recommend any of these patches. Multiple Mailman instances is the recommended way for Mailman 2.1 ah. This is what I need to hear. My concerns right now are: 1. I need to implement this on a production system, so it has to implement the ability to have the same list names on multiple domains and domain-specific site passwords. And it needs to be stable (i.e. it needs to work as advertised). I don't see that these patches implement a domain specific site password. hmmm...I see it's listed as an outstanding issue. My recommendation would be to create separate Mailman instances per domain. I know you said originally 3. Multiple installs. I'd rather not do this if I can help it. Not only do I have to make sure that all of them play nice with the mail system (postfix), but I can see the day when we'll want to upgrade, and that's going to mean upgrading something like 7 installations. ergh. This may be a pain if you use a package that isn't designed for it, but I wouldn't do this with a package, I can't see how I could get it to install into different places without a *lot* of gymnastics like chroots. if you install from source and you have Mailman generating aliases and virtual maps for Postfix, all this means is you need to add 7 entries to alias_maps and virtual_alias_maps instead of just one. Ok...This is tarting to sound doable. It also means I can get the most important domains up quickly. Is there any documentation for doing this? I need to have 7 lots of everything, right? And as long as you keep track of your configure commands, upgrading a source install is very easy and straightforward. Upgrading 7 unpatched installations is probably easier than upgrading 1 patched one. Yeah I guess it would be. We know this works, and there will be a migration path to MM 3. That was my other concern about this approach - how to integrate into a unified install once it is officially supported. But if you will be providing an upgrade path from multiple installs then this makes me more comfortable with the idea. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Virtual domain support
Hello, Apologies for jumping onto the list and posting right away, I realise it's bad netiquette. I admin two servers for a large non-profit organisation. On Thursday, one of them died. At the time we were using a different mailing list manager, but had plans to gently migrate the dozens of lists to Mailman. Now what was going to be an orderly migration is now a frantic scramble, as mailing lists are the lifeblood of the workings of the organisation. But I've run into a problem. I'd assumed that Mailman could support virtual domains without list-name collisions, as I'd seen it done in a few places. But according to the FAQ and everything else I've read this evening, it's not the case. This is about all I know though. There seems to be much posted on the subject. It seems it'll be in version 3, and people have asked for it to be in version 2.2. I've seen mentions of multiple patches and multiple versions ranging over the last 6 years or so. And the WIKI FAQ entry, which itself was updated 2 years ago, points to a patch at http://nix.lauft.net/htdocs/mailman/ which is generating a Connection Refused error. So I'm a bit stuck and am not sure where to go next. I see I've only really got 4 choices: 1. Use some other list manager. I'm not keen on this. I very much like Mailman and so does everyone else with any influence in the technical area. Since we've struggled under the weight of an ancient version of EZMLM for 8 years, I'm *very* keen to move to Mailman ... and I'm not the only one. I expect a revolt if I even dare to suggest this. 2. Just install the Ubuntu package (2.1.9) as is and hope for the best. NOt a good idea. Since I will be supporting at least 7 domains and probably 40+ mailing lists, the chances of a name collision is pretty high. And I don't want to get the various list admins to put a prefix or suffix on their list names because people are bound to forget ... besides, there's also the domain-specific admin password that I also want. 3. Multiple installs. I'd rather not do this if I can help it. Not only do I have to make sure that all of them play nice with the mail system (postfix), but I can see the day when we'll want to upgrade, and that's going to mean upgrading something like 7 installations. ergh. 4. Use one of these patches. This is my prefered route. I can see I'm going to have to install from sources most likely unless there's a patched deb out there somewhere that's fairly current. But as long as the patch does what is eventually going to be merged into the mainline code so that our lists won't break when we can finally upgrade to it, I should be OK to run it. I thank you in advance for any advice anyone can give. I've got a lot of people waiting for this installation, but I've said that I'm not going to rush it. Still, I don't think I can stall too long either. Cheers, Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Virtual domain support
Hello, Apologies for jumping onto the list and posting right away, I realise it's bad netiquette. I admin two servers for a large non-profit organisation. On Thursday, one of them died. At the time we were using a different mailing list manager, but had plans to gently migrate the dozens of lists to Mailman. Now what was going to be an orderly migration is now a frantic scramble, as mailing lists are the lifeblood of the workings of the organisation. But I've run into a problem. I'd assumed that Mailman could support virtual domains without list-name collisions, as I'd seen it done in a few places. But according to the FAQ and everything else I've read this evening, it's not the case. This is about all I know though. There seems to be much posted on the subject. It seems it'll be in version 3, and people have asked for it to be in version 2.2. I've seen mentions of multiple patches and multiple versions ranging over the last 6 years or so. And the WIKI FAQ entry, which itself was updated 2 years ago, points to a patch at http://nix.lauft.net/htdocs/mailman/ which is generating a Connection Refused error. So I'm a bit stuck and am not sure where to go next. I see I've only really got 4 choices: 1. Use some other list manager. I'm not keen on this. I very much like Mailman and so does everyone else with any influence in the technical area. Since we've struggled under the weight of an ancient version of EZMLM for 8 years, I'm *very* keen to move to Mailman ... and I'm not the only one. I expect a revolt if I even dare to suggest this. 2. Just install the Ubuntu package (2.1.9) as is and hope for the best. NOt a good idea. Since I will be supporting at least 7 domains and probably 40+ mailing lists, the chances of a name collision is pretty high. And I don't want to get the various list admins to put a prefix or suffix on their list names because people are bound to forget ... besides, there's also the domain-specific admin password that I also want. 3. Multiple installs. I'd rather not do this if I can help it. Not only do I have to make sure that all of them play nice with the mail system (postfix), but I can see the day when we'll want to upgrade, and that's going to mean upgrading something like 7 installations. ergh. 4. Use one of these patches. This is my prefered route. I can see I'm going to have to install from sources most likely unless there's a patched deb out there somewhere that's fairly current. But as long as the patch does what is eventually going to be merged into the mainline code so that our lists won't break when we can finally upgrade to it, I should be OK to run it. I thank you in advance for any advice anyone can give. I've got a lot of people waiting for this installation, but I've said that I'm not going to rush it. Still, I don't think I can stall too long either. Cheers, Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: This is about all I know though. There seems to be much posted on the subject. It seems it'll be in version 3, and people have asked for it to be in version 2.2. I've seen mentions of multiple patches and multiple versions ranging over the last 6 years or so. And the WIKI FAQ entry, which itself was updated 2 years ago, points to a patch at http://nix.lauft.net/htdocs/mailman/ which is generating a Connection Refused error. So I'm a bit stuck and am not sure where to go next. You seem to have done your homework well, and to have a good understanding of the issues. I found http://ndim.fedorapeople.org/stuff/mailman-vhost/ which appears to contain the same patches that were at http://nix.lauft.net/htdocs/mailman/. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote This stuff looks a bit old. It's patches against Mailman 2.1.7 and files seem to date back to 2006. The docs talk about what's going to happen in 2008. Does this code patch against 2.1.12? Is there newer code than this or should I get it from git? And is there any more documentation than the ReadMe files on this site? I just applied the mailman-2.1.7-20060114-to-vhost.patch to the 2.1.12 base and it applied with only two rejects, both of which are easy to fix. Whether the patched code will actually work and meet your requirements, I can't say. I thought I saw a branch up in the Launchpad project that deals with this. Is that a better place to start than these patches? Maybe, but I don't see one at https://code.launchpad.net/mailman?field.lifecycle=ALL. Are these patches still the recommended way to achieve what I'm looking for? I don't recommend any of these patches. Multiple Mailman instances is the recommended way for Mailman 2.1 My concerns right now are: 1. I need to implement this on a production system, so it has to implement the ability to have the same list names on multiple domains and domain-specific site passwords. And it needs to be stable (i.e. it needs to work as advertised). I don't see that these patches implement a domain specific site password. 2. I need to deploy this pretty quickly so I need some documentation or at least people willing to help if I get stuck. I'm not aware of any documentation for this patch beyond what's in the README files. and 3. I need to know if the changes proposed here (or anywhere) will be compatible with what will eventually be adopted in mainline, or at least that there will be some kind of migration path. I can't really afford to send us down a dead-end path. My recommendation would be to create separate Mailman instances per domain. I know you said originally 3. Multiple installs. I'd rather not do this if I can help it. Not only do I have to make sure that all of them play nice with the mail system (postfix), but I can see the day when we'll want to upgrade, and that's going to mean upgrading something like 7 installations. ergh. This may be a pain if you use a package that isn't designed for it, but if you install from source and you have Mailman generating aliases and virtual maps for Postfix, all this means is you need to add 7 entries to alias_maps and virtual_alias_maps instead of just one. And as long as you keep track of your configure commands, upgrading a source install is very easy and straightforward. Upgrading 7 unpatched installations is probably easier than upgrading 1 patched one. We know this works, and there will be a migration path to MM 3. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain support
Geoff Shang wrote: Ok...This is tarting to sound doable. It also means I can get the most important domains up quickly. Is there any documentation for doing this? I need to have 7 lots of everything, right? The post at http://mail.python.org/pipermail/mailman-users/2004-June/037443.html (linked from the FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030604) has good information. I don't thing there's anything better collected in one place. You do need to have 7 complete installations of Mailman, but only one Postfix and one web server. You can start with just one or two instances, but give some thought to how you will name things before you start. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain not quite working on HTTP (but fine on SMTP)
Quoting Adam McGreggor (adam-mail...@amyl.org.uk):
# cat /var/www/gazette/.htaccess
redirect 301 /index.html
http://lists.linuxgazette.net/mailman/listinfo/
that 404's for me: have you got the Mailman Apache stanzas set-up in
lists.linuxgazette.net's vhost config? I've not had issues using
ServerAlias directives, fwiw.
Um, that's not 404, you're being 301-redirected by the .htaccess file
to a URL that _is_ 404 on account of Mailman not providing the virthost
there. Here, let's temporarily disable the .htaccess file, and see:
# cd /var/www/gazette/
linuxmafia:/var/www/gazette# mv .htaccess .htaccess-save
linuxmafia:/var/www/gazette# touch HELLO-WORLD
You'll please note that http://lists.linuxgazette.net/ (and
http://lists.linuxgazette.net/HELLO-WORLD ) are not, in fact, 404.
But anyway, since you ask, here's the relevant excerpt from the Apache
config:
VirtualHost lists.linuxgazette.net:80
DocumentRoot /var/www/gazette
/VirtualHost
Directory /var/www/gazette/
Options Indexes MultiViews FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
/Directory
I would not touch that. Even with the travesty that is Pkg-exim4, I
still use something along the lines (pretty much) of that per
http://exim.org/howto/mailman21.html
You know, that is very likely what I did in the prior incarnation of my
machine, and I'd certainly consider doing it again -- but being very
careful, because this is a production system. I'm glad to go with
anything that works: Trying first what the package maintainers and Debian
people recommend seemed worthwhile. In any event, the current setup is
just one small problem (http on the virthost) away from 100% success, so
maybe it can be debugged.
Also, since Exim-Mailman integration is working fine, and it's Mailman's
virthost communication with Apache that's broken, I'm not sure switching
to the admittedly far more elegant approach of
http://exim.org/howto/mailman21.html would address my current problem.
You may need a 'clear' clause before the line below: search the
archives of this list for discussions/thoughts/advice thereto.
VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}
[...]
Thanks. I'll try that.
(After restarting qrunning:) Nope. That didn't do it.
MTA = 'Postfix'
I'd change that, as you're using Exim.
I don't believe that's really right. The keyword Postfix in that
context just means use Postfix-style domain semantics, which are not
in any way Postfix-specific but are just a particular way of dealing
with aliases, if I understand correctly.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain not quite working on HTTP (but fine on SMTP)
Quoting Mark Sapiro (m...@msapiro.net): Yes it is. 'listinfo' is a CGI. You need a ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ The Apache conf has: ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ I didn't harp on that in either of my posts because I _had_ pointed out that the Mailman Web pages _do work_ for the default host -- and also invited people to have a look at http://linuxmafia.com/mailman/listinfo and subpages thereof, if they had any doubts. -=but=-, the above ScriptAlias was neatly tucked into the stanza for the default host. And: (or whatever the correct path is) in your httpd.conf where it will apply to the lists.linuxgazette.net host. I.e. it needs to be in the VirtualHost block for each host with lists or it needs to be outside of the virtual hosts section so it applies globally. That was it! Fixed, now. Damn. Bear in mind, I've just had a forced transition from Apache 1.3.x to Apache2 (on account of sudden destruction of the old box), so my excuse is that Debian's Apache2 conffile setup is rather different from what I was used to. Thank you, Mark. And thank you, good gentleman all. -- Cheers, Notice: The value of your Hofstadter's Constant Rick Moen(the average amount of time you spend each month r...@linuxmafia.com thinking about Hofstadter's Constant) has just McQ! (4x80) been adjusted upwards. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain not quite working on HTTP (but fine on SMTP)
On Tue, Jun 16, 2009 at 11:37:30PM -0700, Rick Moen wrote:
Greetings, good people. Problem summary: After server rebuild,
virtual hosts work for SMTP, but Mailman's Web pages are appearing
for the main host only and _not_ the virtual host.
[...]
After some fussing about concerning exim4/mailman integration, I
stumbled on details about POSTFIX_STYLE_VIRTUAL_DOMAINS and its use even
with non-Postfix MTAs. (I put the required plumbing into
/etc/exim4/conf.d/*. It works.) I did read the Debian folks'
/usr/share/doc/mailman/README.Exim4.Debian , which includes in part:
I would not touch that. Even with the travesty that is Pkg-exim4, I
still use something along the lines (pretty much) of that per
http://exim.org/howto/mailman21.html
Here's a way to integrate mailman with Exim4 that will automatically
play nice with mailman's virtual domains support and VERP. It does not
require dedicating domain(s) to mailman.
My kludges don't care about subdomains/list only domains.
http://files.technomage.net/postfix_mailman.txt -- and, consequently,
completed Exim integration by running /var/lib/mailman/bin/genaliases,
and, lo! /var/lib/mailman/data/{aliases|virtual-mailman} came into
existence, and Exim stopped generating errors. More important, the
Exim/Mailman jointly [re-]started processing mail for the mailing lists
within both domains. Life was good. Almost.
IMO, life's waaay too short to genaliases. the configs in
Nigel's doc makes that a thing of the past (it's probably worth
noting, I am a lazy sysadmin, and i automate as much as possible, and
just couldn't make sense of Postfix when i inherited a box with
postfix as its MTA: that got changed).
There remains the matter of Mailman's Web pages: Those for domain
linuxmafia.com are present. (See: http://linuxmafia.com/mailman/listinfo/)
Those for domain lists.linuxgazette.net are not. See:
http://lists.linuxgazette.net/mailman/listinfo/ -- as you'll notice,
Apache2 does recognise the domain. The Apache document root for that
location, /var/www/gazette, has an .htaccess file in it, as follows:
# cat /var/www/gazette/.htaccess
redirect 301 /index.html
http://lists.linuxgazette.net/mailman/listinfo/
that 404's for me: have you got the Mailman Apache stanzas set-up in
lists.linuxgazette.net's vhost config? I've not had issues using
ServerAlias directives, fwiw.
[...]
You may need a 'clear' clause before the line below: search the
archives of this list for discussions/thoughts/advice thereto.
VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}
[...]
MTA = 'Postfix'
I'd change that, as you're using Exim.
HTH
--
We used to quip that password is the most common password. Now
it's password1. Who said users haven't learned anything about
security?
(Bruce Schneier, December 2006)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Virtual domain not quite working on HTTP (but fineon SMTP)
Rick Moen wrote:
There remains the matter of Mailman's Web pages: Those for domain
linuxmafia.com are present. (See: http://linuxmafia.com/mailman/listinfo/)
Those for domain lists.linuxgazette.net are not. See:
http://lists.linuxgazette.net/mailman/listinfo/ -- as you'll notice,
Apache2 does recognise the domain. The Apache document root for that
location, /var/www/gazette, has an .htaccess file in it, as follows:
# cat /var/www/gazette/.htaccess
redirect 301 /index.html
http://lists.linuxgazette.net/mailman/listinfo/
If I mv .htaccess to .htacces-save for diagnostic purposes, I _do_
see the contents of /var/www/gazette/ in my browser, so this is not
an Apache vhost problem.
Yes it is. 'listinfo' is a CGI. You need a
ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
(or whatever the correct path is) in your httpd.conf where it will
apply to the lists.linuxgazette.net host. I.e. it needs to be in the
VirtualHost block for each host with lists or it needs to be outside
of the virtual hosts section so it applies globally.
Here is what I imagine is the relevant part of my current
/var/lib/mailman/Mailman/mm_cfg.py :
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'linuxmafia.com'
#-
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST = 'linuxmafia.com'
#-
# Required when setting any of its arguments.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.linuxgazette.net', 'lists.linuxgazette.net')
[...]
This looks good, but is not relevant to your issue, at least not until
you fix Apache so that http://lists.linuxgazette.net/mailman/listinfo/
gets you to the Mailman listinfo CGI.
# Uncomment if you use Postfix virtual domains, but be sure to
# see /usr/share/doc/mailman/README.Debian first.
# MTA='Postfix'
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/bin/true'
POSTFIX_MAP_CMD = 'chgrp Debian-exim'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['linuxmafia.com', 'lists.linuxgazette.net']
VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}
Get rid of the above line. It undoes everything you did with
add_virtualhost directives above.
VIRTUAL_HOST_OVERVIEW = 1
Here is what I imagine is the relevant part of my current
/var/lib/mailman/Mailman/Default.py:
# Virtual domains
#
# Set up your virtual host mappings here. This is primarily used for the
# thru-the-web list creation, so its effects are currently fairly limited.
# Use add_virtualhost() call to add new mappings. The keys are strings as
# determined by Utils.get_domain(), the values are as appropriate for
# DEFAULT_HOST_NAME.
VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}
Where did this come from. If you put it there, you shouldn't be
changing Defaults.py at all. If it's part of the Debian package, I
don't know what to say.
[...]
# MTA = 'Manual'
MTA = 'Postfix'
[...]
#POSTFIX_STYLE_VIRTUAL_DOMAINS = []
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['linuxmafia.com', 'lists.linuxgazette.net'
DON'T CHANGE Defaults.py
Make all your changes in mm_cfg.py.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Virtual domain not quite working on HTTP (but fine on SMTP)
Greetings, good people. Problem summary: After server rebuild,
virtual hosts work for SMTP, but Mailman's Web pages are appearing
for the main host only and _not_ the virtual host.
Details:
I've had Mailman running on Debian (serving up mailing lists for both
linuxmafia.com and lists.linuxgazette.net) since, oh, God was a
teenager, but a power spike destroyed my somewhat antique hardware in
April. I hastily deployed Debian lenny 5.0 on a spare box the same
day, and then copied back down my latest backup data and madly worked to
recreate the prior config.
That data restore including dropping back into place the former entire
/var/lib/mailman/lists/ tree (mailing list definitions), the
/var/lib/mailman/archives/ tree, etc. (As noted below, this data restore
was correct to the extent of making Mailman able to handle both
domains' mailing lists correctly concerning SMTP operation, and
linuxmafia.com's mailing lists concerning Mailman Web pages.)
Relevant package versions:
:r! dpkg -l | egrep 'mailman|apache2-mpm-prefork|exim4-base'
ii apache2-mpm-prefork 2.2.8-1Traditional
model for Apache HTTPD
ii exim4-base4.69-9 support files
for all Exim MTA (v4) packages
ii mailman 1:2.1.10~b3-1 Powerful,
web-based mailing list manager
Things are oddly different from Pleistocene times when I did the job
before (not a complaint!).
After some fussing about concerning exim4/mailman integration, I
stumbled on details about POSTFIX_STYLE_VIRTUAL_DOMAINS and its use even
with non-Postfix MTAs. (I put the required plumbing into
/etc/exim4/conf.d/*. It works.) I did read the Debian folks'
/usr/share/doc/mailman/README.Exim4.Debian , which includes in part:
Here's a way to integrate mailman with Exim4 that will automatically
play nice with mailman's virtual domains support and VERP. It does not
require dedicating domain(s) to mailman.
Configure your Mailman (in /etc/mailman/mm_cfg.py) with:
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/bin/true'
POSTFIX_MAP_CMD = 'chgrp Debian-exim'
and list all your Mailman domains in POSTFIX_STYLE_VIRTUAL_DOMAINS.
Please note that the chgrp command above will not work when creating a
list in the web interface: the user www-data will not be allowed to do
this. You can circumvent this problem by creating new lists with the
'newlist' command line command or using instead:
POSTFIX_MAP_CMD = 'chmod o+r'
This will allow local users (with shell access to the list server) to
see the list of all Mailman mailing lists, but not much more.
I also noted what appeared to be good advice at
http://files.technomage.net/postfix_mailman.txt -- and, consequently,
completed Exim integration by running /var/lib/mailman/bin/genaliases,
and, lo! /var/lib/mailman/data/{aliases|virtual-mailman} came into
existence, and Exim stopped generating errors. More important, the
Exim/Mailman jointly [re-]started processing mail for the mailing lists
within both domains. Life was good. Almost.
There remains the matter of Mailman's Web pages: Those for domain
linuxmafia.com are present. (See: http://linuxmafia.com/mailman/listinfo/)
Those for domain lists.linuxgazette.net are not. See:
http://lists.linuxgazette.net/mailman/listinfo/ -- as you'll notice,
Apache2 does recognise the domain. The Apache document root for that
location, /var/www/gazette, has an .htaccess file in it, as follows:
# cat /var/www/gazette/.htaccess
redirect 301 /index.html
http://lists.linuxgazette.net/mailman/listinfo/
If I mv .htaccess to .htacces-save for diagnostic purposes, I _do_
see the contents of /var/www/gazette/ in my browser, so this is not
an Apache vhost problem.
Here is what I imagine is the relevant part of my current
/var/lib/mailman/Mailman/mm_cfg.py :
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'linuxmafia.com'
#-
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST = 'linuxmafia.com'
#-
# Required when setting any of its arguments.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.linuxgazette.net', 'lists.linuxgazette.net')
[...]
# Uncomment if you use Postfix virtual domains, but be sure to
# see /usr/share/doc/mailman/README.Debian first.
# MTA='Postfix'
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/bin/true'
POSTFIX_MAP_CMD = 'chgrp Debian-exim'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['linuxmafia.com', 'lists.linuxgazette.net']
VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}
VIRTUAL_HOST_OVERVIEW = 1
Here is what I imagine is the relevant part of my current
/var/lib/mailman/Mailman/Default.py:
# Virtual domains
#
# Set up your virtual host mappings here. This is primarily used
[Mailman-Users] virtual domain
how to configure virtual domain in postfix + mailman? in my mm_cfg.py i configure like this MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['doma.ac.id','domb.ac.id'] in postfix/main.cf, configure like this virtual_alias_maps = hash:/etc/mailman/virtual-mailman alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases i have sucsess create new mailing list [EMAIL PROTECTED] i have sucsess subscribe member,but if a member send mail to [EMAIL PROTECTED], i have got error [EMAIL PROTECTED]Host or domain name not found. Name service error for name=doma.ac.id type=A: Host not found ___ Yahoo! sekarang memiliki alamat Email baru. Dapatkan nama yang selalu Anda inginkan di domain baru @ymail dan @rocketmail. Cepat sebelum diambil orang lain! http://mail.promotions.yahoo.com/newdomains/id/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] virtual domain
[mailed and posted] On Jun 27, 2008, at 5:27 AM, Dony Tata wrote: i have sucsess create new mailing list [EMAIL PROTECTED] i have sucsess subscribe member,but if a member send mail to [EMAIL PROTECTED] , i have got error [EMAIL PROTECTED]Host or domain name not found. Name service error for name=doma.ac.id type=A: Host not found This sounds like the problem is not with the mailman configuration at all, but that DNS is not set up properly for doma.ac.id to receive mail. Can mail be sent to non-list addresses at doma.ac.id? Cheers, -j -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] virtual domain
Dony Tata wrote: how to configure virtual domain in postfix + mailman? in my mm_cfg.py i configure like this MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['doma.ac.id','domb.ac.id'] in postfix/main.cf, configure like this virtual_alias_maps = hash:/etc/mailman/virtual-mailman alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases It's not a fatal mistake, but normally, you want hash:/etc/mailman/aliases only in alias_maps and not in alias_database. This is because Mailman runs postalias to update its aliases.db whenever Mailman changes its aliases, so you don't need to have Postfix do it whenever newaliases is run. i have sucsess create new mailing list [EMAIL PROTECTED] i have sucsess subscribe member,but if a member send mail to [EMAIL PROTECTED], i have got error [EMAIL PROTECTED]Host or domain name not found. Name service error for name=doma.ac.id type=A: Host not found As pointed out in another reply, this is a DNS issue. The sending MTA does not know where to deliver mail for the dom.ac.id domain because it has no MX or A record in DNS. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] virtual domain
On Jun 27, 2008, at 9:25 AM, Dony Tata wrote: I don't include doma.ac.id in DNS, must i include doma.ac.id in DNS? doma.ac.id is virtual domain in server xxx.mod..ac.id. If you want to people or other machines to be able to mail to @doma.ac.id, then there will need to be an MX record in DNS for doma.ac.id. The MX record can point to your server. I strongly recommend that work with someone at your university who is familiar with SMTP and DNS. You need to have some understanding of each to set up mailman and virtual domains. Cheers, -j -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] virtual domain setup with postfix
On Monday, January 29, 2007, at 04:18PM, Mark Sapiro [EMAIL PROTECTED] wrote: Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens after that. Presumably, that's because Postfix is delivering the mail to a local mailbox 'pctest' instead of piping it to Mailman's mail wrapper via the command /usr/local/mailman/mail/mailman post pctest. Yup. That is exactly what's happening (except that it's a virtual mailbox and not a local user account). This is really a Postfix question, not a Mailman question Yes and no. I'd say it's more of a clueless-pilot question, esp. since Postfix is doing exactly what it's told -- in this instance, deliver messages to [EMAIL PROTECTED] The problem here is mailman-specific, though I'm unsure whether the solution is in mailman configuration or some combo of postfix and mailman configs. I've read and reread and reread the mailman docs, and I don't see where and how virtual addresses get piped to the command above. The file /usr/local/mailman/data/aliases has commands like the above; the file /usr/local/mailman/data/virtual-mailman does not. For example, aliases has: pctest: |/usr/local/mailman/mail/mailman post pctest but virtual-mailman has: [EMAIL PROTECTED] pctest I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. , but you might find the post at http://mail.python.org/pipermail/mailman-users/2007-January/055502.html to be helpful. Thanks. That post in turn links to an earlier howto which covers aliases but not virtual-mailman. On Monday, January 29, 2007, at 05:47PM, Paul Fox [EMAIL PROTECTED] wrote: However, MM never distributes the mail to list subscribers. /var/log/maillog says each message is sent to [EMAIL PROTECTED]; however, the only files in /usr/local/mailman/logs that change are smtp and subscribe (and then only when list members are added). so it sounds like you have postfix aliases set up for pctest-*, but not pctest itself? is that right? Actually, the opposite. I'd set up a virtual mailbox for pctest but none of the rest of the pctest-* hierarchy. It's not covered in the docs, but from Mark's email I gather that I shouldn't need this step -- instead mail should be piped to the command Mark gave above. Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens after that. i don't use mysql, but my epiphany was when i realized i needed two separate mappings to be in place to get postfix and mailman working together. you need the virtual domain map (which i believe you have) and you need the map that takes the result of the virtual domain map, and turns it into a real destination. Right. That's really my question -- how is that done? thanks! /wsbs -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
david wrote: I've read and reread and reread the mailman docs, and I don't see where and how virtual addresses get piped to the command above. The file /usr/local/mailman/data/aliases has commands like the above; the file /usr/local/mailman/data/virtual-mailman does not. For example, aliases has: pctest: |/usr/local/mailman/mail/mailman post pctest but virtual-mailman has: [EMAIL PROTECTED] pctest I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. ... i don't use mysql, but my epiphany was when i realized i needed two separate mappings to be in place to get postfix and mailman working together. you need the virtual domain map (which i believe you have) and you need the map that takes the result of the virtual domain map, and turns it into a real destination. Right. That's really my question -- how is that done? as i understand it, it's done automatically by postfix, if you tell it about all the maps. if you weren't using mysql, the definition of virtual_alias_maps should include the alias maps for any virtual domains: virtual_alias_maps = hash:/usr/local/mailman/data/virtual-mailman and the postfix definition of alias_maps should refer to both /etc/aliases and /usr/local/mailman/data/aliases: alias_maps = hash:/etc/aliases hash:/usr/local/mailman/data/aliases postfix will resolve using first the virtual_alias_maps, and then the alias_maps. but i don't know how mysql affects any of that. paul =- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 24.8 degrees) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
[ cc'ing the list on reply ] orlando wrote: I think he still has to issue the genaliases command. oh, yes. in addition, all of the hash maps need to have postmap run on them. paul the virtual_alias_map is the one that should have a mysql entry: virtual_alias_maps = hash:/usr/local/mailman/data/virtual-mailman, mysql:/usr/local/etc/postfix/mysql/mysql_virtual_alias_maps.cf alias_maps = hash:/usr/local/mailman/data/aliases, hash:/usr/local/etc/postfix/aliases Orlando =- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 26.4 degrees) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
David Newman wrote: pctest: |/usr/local/mailman/mail/mailman post pctest but virtual-mailman has: [EMAIL PROTECTED] pctest I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. Do you have the appropriate alias_maps entry in your postfix configuration pointing to aliases as discussed in http://www.list.org/mailman-install/node13.html Do you have MTA = 'Postfix' in your mm_cfg.py and have you run bin/genaliases to create the appropriate entries in data/aliases* and data/virtual-mailman*? You have to do all the stuff in sec 6.1.1 of the manual as well as the stuff in sec 6.1.2 that you said you'd read many times. Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. I'm sure this can be improved. We'd appreciate the help. Actually, the opposite. I'd set up a virtual mailbox for pctest but none of the rest of the pctest-* hierarchy. It's not covered in the docs, but from Mark's email I gather that I shouldn't need this step -- instead mail should be piped to the command Mark gave above. You need entries in virtual-mailman* for addresses in your postfix virtual domains to map them to local addresses, AND you need entries in aliases* to cause these local addresses to be piped to the wrapper. If you have MTA = 'Postfix' Mailman should take care of maintaining data/aliases* and data/virtual-mailman* for you, but you need to reference them in the postfix config as discissed in http://www.list.org/mailman-install/node13.html and http://www.list.org/mailman-install/postfix-virtual.html -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
Paul Fox wrote: as i understand it, it's done automatically by postfix, if you tell it about all the maps. if you weren't using mysql, the definition of virtual_alias_maps should include the alias maps for any virtual domains: virtual_alias_maps = hash:/usr/local/mailman/data/virtual-mailman and the postfix definition of alias_maps should refer to both /etc/aliases and /usr/local/mailman/data/aliases: alias_maps = hash:/etc/aliases hash:/usr/local/mailman/data/aliases postfix will resolve using first the virtual_alias_maps, and then the alias_maps. but i don't know how mysql affects any of that. My understanding is that if you are using mysql, you might have something like alias_maps = mysql:/etc/aliases hash:/usr/local/mailman/data/aliases i.e., you could still use a hash for mailman's aliases and virtual-mailman. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
Paul Fox wrote: [ cc'ing the list on reply ] orlando wrote: I think he still has to issue the genaliases command. oh, yes. in addition, all of the hash maps need to have postmap run on them. Assuming MTA = 'Postfix', genaliases and list creation/deletion will run the commands defined by POSTFIX_ALIAS_CMD = '/usr/sbin/postalias' POSTFIX_MAP_CMD = '/usr/sbin/postmap' or whatever you may have redefined them to in mm_cfg.py. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
mark wrote: David Newman wrote: Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. I'm sure this can be improved. We'd appreciate the help. in that vein -- i never saw any yea or nay on the minor doc addition i submitted on a related aspect of lists at virtual domains. at the time i thought i might have sent the change to the wrong place (i.e. the users', not the developers' list) but now i'm just wondering if it fell through the cracks: http://www.mail-archive.com/mailman-users%40python.org/msg43083.html paul p.s. the searchable archives at mail-archive.com are nice, but they'd be a _lot_ more useful if they didn't obscure anything that looked like an email address. text describing mailman and postfix config is rendered practically useless because of it. at the least, they shouldn't obscure any address ending in .tld or example.com. ;-/ =- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 25.9 degrees) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
Paul Fox wrote: in that vein -- i never saw any yea or nay on the minor doc addition i submitted on a related aspect of lists at virtual domains. at the time i thought i might have sent the change to the wrong place (i.e. the users', not the developers' list) but now i'm just wondering if it fell through the cracks: http://www.mail-archive.com/mailman-users%40python.org/msg43083.html It's in my inbox. I haven't had time to do anything with it, but I at least have seen it. That said, it is probably better to post something like this to the patch tracker http://sourceforge.net/tracker/?group_id=103atid=300103, or if you think it needs discussion first, to the mailman-developers. p.s. the searchable archives at mail-archive.com are nice, but they'd be a _lot_ more useful if they didn't obscure anything that looked like an email address. text describing mailman and postfix config is rendered practically useless because of it. at the least, they shouldn't obscure any address ending in .tld or example.com. ;-/ Of course, we don't control mail-archive.com. It is our 'official' searchable archive (although google with site:mail.python.org inurl:mailman works pretty well), but if we ever get archive search integrated in Mailman OOTB, we might drop it. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix SOLVED
On 1/30/07 9:49 AM, Mark Sapiro wrote: David Newman wrote: pctest: |/usr/local/mailman/mail/mailman post pctest but virtual-mailman has: [EMAIL PROTECTED] pctest I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. Do you have the appropriate alias_maps entry in your postfix configuration pointing to aliases as discussed in http://www.list.org/mailman-install/node13.html Yes. This is the part that was missing. I was trying with alias_maps or virtual_alias_maps but not both. MM needs both in this setup. One final problem is that I got the 'Mailman expected the mail wrapper script to be executed as group nobody' error because MM for postfix installs with GID mailman. My hack was to uninstall, change the GID to 'nobody' in the FreeBSD ports Makefile, and reinstall. This may have security implications but I'm not sure about that. Do you have MTA = 'Postfix' in your mm_cfg.py and have you run bin/genaliases to create the appropriate entries in data/aliases* and data/virtual-mailman*? You have to do all the stuff in sec 6.1.1 of the manual as well as the stuff in sec 6.1.2 that you said you'd read many times. Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. Doing all of 6.1.1 and 6.1.2 is something I'll propose adding to 6.1.2. At one stage I did have alias_maps but took it out because it's not given in 6.1.2. Thanks all for your help in getting this set up. It will take me a day or two to write up suggested changes to 6.1.2, which I'll post to the list. thanks again /wsbs -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] virtual domain setup with postfix
MM 2.1.9, Postfix 2.3.5, cyrus-imap 2.3.7, all on FreeBSD 6.1 installed from
ports
Postfix already handles mail for multiple virtual domains defined in a MySQL
database. I believe virtual domain setup is OK, as individual users have been
sending and receiving mail for some time.
Having problems with Mailman, though. I've read these instructions many times:
http://www.list.org/mailman-install/postfix-virtual.html
Besides doing what's listed there, I also defined a virtual mailbox for a new
pctest list (without that, mail sent to [EMAIL PROTECTED] bounces).
However, MM never distributes the mail to list subscribers. /var/log/maillog
says each message is sent to [EMAIL PROTECTED]; however, the only files in
/usr/local/mailman/logs that change are smtp and subscribe (and then only when
list members are added).
Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens
after that.
Thanks in advance for clues on fixing this.
/wsbs
from virtual-mailman (note that I have run postmap on this and restarted
mailman and postfix multiple times, but no joy):
# STANZA START: pctest
# CREATED: Mon Jan 29 15:05:35 2007
[EMAIL PROTECTED] pctest
[EMAIL PROTECTED]pctest-admin
[EMAIL PROTECTED] pctest-bounces
[EMAIL PROTECTED] pctest-confirm
[EMAIL PROTECTED] pctest-join
[EMAIL PROTECTED]pctest-leave
[EMAIL PROTECTED]pctest-owner
[EMAIL PROTECTED] pctest-request
[EMAIL PROTECTED]pctest-subscribe
[EMAIL PROTECTED] pctest-unsubscribe
# STANZA END: pctest
from mm_cfg.py:
# Put YOUR site-specific settings below this line.
$SMTPHOST = virt1.tld
DEFAULT_EMAIL_HOST = 'virt1.tld'
DEFAULT_URL_HOST = 'virt1.tld'
IMAGE_LOGOS = '/icons/'
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt1.tld']
VIRTUAL_HOSTS.clear()
add_virtualhost('mail.virt1.tld', 'virt1.tld')
from main.cf:
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
virtual_alias_maps = mysql:/usr/local/etc/postfix/mysql_virtual_alias_maps.cf,
hash:/usr/local/mailman/data/virtual-mailman
from master.cf:
(nothing MM specific)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
David Newman wrote: Having problems with Mailman, though. I've read these instructions many times: http://www.list.org/mailman-install/postfix-virtual.html Besides doing what's listed there, I also defined a virtual mailbox for a new pctest list (without that, mail sent to [EMAIL PROTECTED] bounces). However, MM never distributes the mail to list subscribers. /var/log/maillog says each message is sent to [EMAIL PROTECTED]; however, the only files in /usr/local/mailman/logs that change are smtp and subscribe (and then only when list members are added). Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens after that. Presumably, that's because Postfix is delivering the mail to a local mailbox 'pctest' instead of piping it to Mailman's mail wrapper via the command /usr/local/mailman/mail/mailman post pctest. This is really a Postfix question, not a Mailman question, but you might find the post at http://mail.python.org/pipermail/mailman-users/2007-January/055502.html to be helpful. You might also find something of interest at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain setup with postfix
david wrote: Postfix already handles mail for multiple virtual domains defined in a MySQL database. I believe virtual domain setup is OK, as individual users have been sending and receiving mail for some time. Having problems with Mailman, though. I've read these instructions many times: http://www.list.org/mailman-install/postfix-virtual.html Besides doing what's listed there, I also defined a virtual mailbox for a new pctest list (without that, mail sent to [EMAIL PROTECTED] bounces). However, MM never distributes the mail to list subscribers. /var/log/maillog says each message is sent to [EMAIL PROTECTED]; however, the only files in /usr/local/mailman/logs that change are smtp and subscribe (and then only when list members are added). so it sounds like you have postfix aliases set up for pctest-*, but not pctest itself? is that right? Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens after that. i don't use mysql, but my epiphany was when i realized i needed two separate mappings to be in place to get postfix and mailman working together. you need the virtual domain map (which i believe you have) and you need the map that takes the result of the virtual domain map, and turns it into a real destination. paul =- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 15.1 degrees) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Virtual Domain / Postfix
Hello,
I am willing to configure Virtual Domains in Postfix, and followed
documentation available at:
http://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html
Other than correctly configuring Postfix and mm_cfg.py with
POSTFIX_STYLE_VIRTUAL_DOMAINS = pointing all my virtual domains, I
also added
add_virtualhost('www.XX.domain', 'XX.domain')
To mm_cfg.py after I tried without it. And in both cases (with and
without) I didn't work.
When I try to add a list which already exists in the main domain,
mailman states this list already exists. I am trying to create it via
Web...
Created the first list on:
http://www.domain.com.br/mailman/create
And want to create the second on
http://www.XX.domain.com.br/mailman/create
Mailman Web interface does not distinguishes that it is a different
domain (a subdomain in fact).
What am I missing? Is there a better documentation than the above
mentioned to try before asking for help?
Thank you a lot.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual Domain / Postfix
Eduardo Meyer wrote: When I try to add a list which already exists in the main domain, mailman states this list already exists. This is a limitation of Mailman. Even with virtual domains, list names must be unique within the installation, not just within the domain. What am I missing? Is there a better documentation than the above mentioned to try before asking for help? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.047.htp -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual Domain / Postfix
On 6/5/06, Mark Sapiro [EMAIL PROTECTED] wrote: Eduardo Meyer wrote: When I try to add a list which already exists in the main domain, mailman states this list already exists. This is a limitation of Mailman. Even with virtual domains, list names must be unique within the installation, not just within the domain. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.047.htp Very bad, because I am exactly migrating the enviroment from CPanel to non-cpanel. I will try Niedermann's patches. Thank you Sapiro for pointing out this limitation and references. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Virtual-domain support?
I've been away from the list for a while, and am curious: Will virtual domains support be included in Mailman 2.2...if they are not already? By virtual domain support I mean the ability to support email lists from multiple domains via one GNUMailman installation on one server. I manage virtual-domain-based servers, and would love to not to have install a different Mailman instance for every domain I support. (Mailman remains the only collaborative app I use--and I use a lot of them--which I deem not sufficiently virtual-domain capable.) -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
Matt England wrote: I've been away from the list for a while, and am curious: Will virtual domains support be included in Mailman 2.2...if they are not already? By virtual domain support I mean the ability to support email lists from multiple domains via one GNUMailman installation on one server. I manage virtual-domain-based servers, and would love to not to have install a different Mailman instance for every domain I support. (Mailman remains the only collaborative app I use--and I use a lot of them--which I deem not sufficiently virtual-domain capable.) I run multiple lists with Mailman, been doing so since v1.1 (or was it 1.2?). Anyway, virtual domains work for me. What virtual domain problem do you have with recent MM versions? -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
At 1/26/2006 07:47 PM, Jim Popovitch wrote: I run multiple lists with Mailman, been doing so since v1.1 (or was it 1.2?). Anyway, virtual domains work for me. What virtual domain problem do you have with recent MM versions? [EMAIL PROTECTED] and [EMAIL PROTECTED] (ie, same list name, different domains, different lists/reflectors) will not work for the same Mailman server...or at least, so I'm told. -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
Matt England wrote: At 1/26/2006 07:47 PM, Jim Popovitch wrote: I run multiple lists with Mailman, been doing so since v1.1 (or was it 1.2?). Anyway, virtual domains work for me. What virtual domain problem do you have with recent MM versions? [EMAIL PROTECTED] and [EMAIL PROTECTED] (ie, same list name, different domains, different lists/reflectors) will not work for the same Mailman server...or at least, so I'm told. That depends on a few things. For starters, does your MTA support [EMAIL PROTECTED] AND [EMAIL PROTECTED] If it does, then you will need to use the virtualization features of your MTA to map each list to a unique local email account. I.E.: in sendmail this would be the virtusertable where you would map [EMAIL PROTECTED] to list-a and [EMAIL PROTECTED] to list-b. Your sendmail aliases file would then contain entires like this: list-a:|/usr/local/mailman/mail/mailman post list-a list-a-admin: |/usr/local/mailman/mail/mailman admin list-a list-b:|/usr/local/mailman/mail/mailman post list-b list-b-admin: |/usr/local/mailman/mail/mailman admin list-b Additionally, using virtualization features of your MTA, you need to change sender (outbound) addresses so that email from list-a appears as coming from [EMAIL PROTECTED] not [EMAIL PROTECTED] In sendmail this is done in genericstable. At this point you can change each Mailman list settings so that emails aesthetically appear as from LIST instead of LIST-A or LIST-B (subject line, footer, subscription notice, etc). The real visible issue may arise in URLs that users will use (i.e. http://server/mailman/list). You will need to configure your webserver to redirect http://domain1.com/mailman/list to http://domain1.com/mailman/list-a AND http://domain2.com/mailman/list to redirect to http://domain2.com/mailman/list-b. I suppose you could also use proxy features of Apache to proxy http://domain2.com/mailman/list-b as http://domain2.com/mailman/list and the same for list-a. Shouldn't be too difficult. NONE of the above will ever completely hide the real list name from email headers, but who really looks at those these days? :-) Hth, -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
At 1/26/2006 09:09 PM, Jim Popovitch wrote: That depends on a few things. For starters, does your MTA support [EMAIL PROTECTED] AND [EMAIL PROTECTED] Yes. If it does, then you will need to use the virtualization features of your MTA to map each list to a unique local email account. Already done. vpopmail in qmail already has several different virtual domains running. I.E.: in sendmail this would be the virtusertable where you would map [EMAIL PROTECTED] to list-a and [EMAIL PROTECTED] to list-b. Your sendmail aliases file would then contain entires like this: list-a:|/usr/local/mailman/mail/mailman post list-a list-a-admin: |/usr/local/mailman/mail/mailman admin list-a list-b:|/usr/local/mailman/mail/mailman post list-b list-b-admin: |/usr/local/mailman/mail/mailman admin list-b sendmail. ** shudder ** [... rest of stuff deleted, not sure why we are talking about an MTA if it's a Mailman problem ...but yes, I know how to get my MTA to do this...] There's a sourceforge task/patch/faq somewhere talking about how this can be solved, but it required virtual-domain support. At this point you can change each Mailman list settings so that emails aesthetically appear as from LIST instead of LIST-A or LIST-B (subject line, footer, subscription notice, etc). The real visible issue may arise in URLs that users will use (i.e. http://server/mailman/list). You will need to configure your webserver to redirect http://domain1.com/mailman/list to http://domain1.com/mailman/list-a AND http://domain2.com/mailman/list to redirect to http://domain2.com/mailman/list-b. I suppose you could also use proxy features of Apache to proxy http://domain2.com/mailman/list-b as http://domain2.com/mailman/list and the same for list-a. Shouldn't be too difficult. I don't think I follow. Why do I need to use different listnames? TO BE CLEAR: I want Mailman changed to handle the virtual domainsso that I do NOT have to bend over backwards to do all the above stuff. And yes, I'm already managing all the virtual domains in Apache. NONE of the above will ever completely hide the real list name from email headers, but who really looks at those these days? :-) The point is: the REAL list name is associated with a domain, and list names are no longer represented without their domain name...if an appropriate fix is made...I hope. That's the point. We don't have to make any non-real list names. I don't want to hodge-podge Mailman. I want Mailman fixed to support this. Maybe I'm not understanding what your saying, Jim? Possibly vice versa? -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
Matt England wrote: sendmail. ** shudder ** Hey, no shudder here. I fully understand Sendmail, it works well and I sleep good at night. YMMV. [... rest of stuff deleted, not sure why we are talking about an MTA if it's a Mailman problem ...but yes, I know how to get my MTA to do this...] I mentioned the MTA because that is the crux of most peoples virtualization problems. Indeed 90% of using Mailman, with virtual domains, involves MTA config. There's a sourceforge task/patch/faq somewhere talking about how this can be solved, but it required virtual-domain support. Not sure what you are talking about here? Got URL? At this point you can change each Mailman list settings so that emails aesthetically appear as from LIST instead of LIST-A or LIST-B (subject line, footer, subscription notice, etc). The real visible issue may arise in URLs that users will use (i.e. http://server/mailman/list). You will need to configure your webserver to redirect http://domain1.com/mailman/list to http://domain1.com/mailman/list-a AND http://domain2.com/mailman/list to redirect to http://domain2.com/mailman/list-b. I suppose you could also use proxy features of Apache to proxy http://domain2.com/mailman/list-b as http://domain2.com/mailman/list and the same for list-a. Shouldn't be too difficult. I don't think I follow. Why do I need to use different listnames? TO BE CLEAR: I want Mailman changed to handle the virtual domainsso that I do NOT have to bend over backwards to do all the above stuff. Mailman stores list specific info in files names after each list. Therefore you can not have 2 identically named lists in Mailman. [snip] I don't want to hodge-podge Mailman. I want Mailman fixed to support this. It's not something that can be fixed in Mailman. Somethings in life are unique, Mailman's list names are one of those things. Changing Mailman to support 2 lists of the same name, would be akin to having a Linux server that supported 2 identical usernames (even though the MTA on that server supports virtual domains). It just isn't possible, and probably won't ever be due to the number of things that would have to be changed to support this. -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
Matt England wrote: [EMAIL PROTECTED] and [EMAIL PROTECTED] (ie, same list name, different domains, different lists/reflectors) will not work for the same Mailman server...or at least, so I'm told. You are correct, at least as far as the standard 2.1.x distribution is concerned. There are some patches around. See http://sourceforge.net/tracker/index.php?func=detailaid=943827group_id=103atid=300103. There is also a link to cPanel's patches at http://mail.python.org/pipermail/mailman-users/2005-January/041748.html. But reports from people who've tried these suggest that they may be an incomplete solution at best, and may not work at all. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
At 1/26/2006 09:43 PM, Mark Sapiro wrote: There are some patches around. See http://sourceforge.net/tracker/index.php?func=detailaid=943827group_id=103atid=300103. There is also a link to cPanel's patches at http://mail.python.org/pipermail/mailman-users/2005-January/041748.html. But reports from people who've tried these suggest that they may be an incomplete solution at best, and may not work at all. Ok, thanks. So the question is: is there any move afoot to change Mailman to support same list names across multiple domains? Why can't Mailman index it's list names such that the domain name is associated with the internal list name...thus allowing for the internal structure to have the same list name for different domains? I suspect the answer: it's hard because that support was not build into the architecture. And that's a fine answer for me. The followup question (assuming the above answer...which may or may not be a fair assumption): will this architecture ever be changed to remove this limitation? -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
Matt England wrote: So the question is: is there any move afoot to change Mailman to support same list names across multiple domains? Yes. See http://www.list.org/todo.html. Why can't Mailman index it's list names such that the domain name is associated with the internal list name...thus allowing for the internal structure to have the same list name for different domains? No reason. That's kind of what the patches I referred to in my earlier post do. I think the patches work by appending the virtual domain to the list name for internal purposes. It could also be done by adding a directory level, i.e. instead of lists/name/ use lists/domain/name/ and similarly for archives. I suspect the answer: it's hard because that support was not build into the architecture. And that's a fine answer for me. I think it's hard because it's hard to get it right everywhere, and the patches that are out there perhaps address everything that was important to someone, but not everything that could be important to anyone. The other issue is MTA related in that mail to [EMAIL PROTECTED] has to be delivered to Mailman in a way that it can be distinguished from mail to [EMAIL PROTECTED] I don't know enough about various MTAs to know how or even if this can be done with all MTAs. The followup question (assuming the above answer...which may or may not be a fair assumption): will this architecture ever be changed to remove this limitation? Yes again. I think you'll see it in Mailman 3, but as I'm sure you well know, I can't give you a timeline for that except to say that it isn't imminent. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual-domain support?
At 1/26/2006 10:38 PM, Mark Sapiro wrote: The followup question (assuming the above answer...which may or may not be a fair assumption): will this architecture ever be changed to remove this limitation? Yes again. I think you'll see it in Mailman 3, but as I'm sure you well know, I can't give you a timeline for that except to say that it isn't imminent. Ok, good. All my questions answered. Thanks! Best of luck with revs 2.2 and eventually 3. -Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain lists
Am Dienstag 28 Juni 2005 02:56 schrieb Mark Sapiro: Christian Anton wrote: i am running mailman 2.1.5 with the mailman-virtual patch for some virtual domains. Because of the usage of suexec on my Webserver i have every vhost running its CGI's with another UID on the system. For being able to access the mailman-binaries i have to create a new vhost that ist only for this, for example lists.domain.tld, configuring in this vhost that cgi's are executed with the UID 'mailman'. Now i want to create a mailinglist [EMAIL PROTECTED], but the URL host for seeing the webpages of the list must be [EMAIL PROTECTED] Do you mean lists.mglug.de? yes, i meant! I have read the documentation and i think that add_virtualhost(URL_HOST, MAIL_HOST) has to be what i want, so that when i create a list with the command: bin/newlist [EMAIL PROTECTED] If you carefully read 'bin/newlist --help' you will see the command you want is bin/newlist [EMAIL PROTECTED] i.e., [EMAIL PROTECTED], not [EMAIL PROTECTED] I know this is confusing and it has been addressed in 2.1.6 by adding new options so you could do bin/newlist list --urlhost=lists.mglug.de but this won't work in 2.1.5. Reading manuals is a fine thing... It runs, thank you very much! Christian -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domain lists
Christian Anton wrote: i am running mailman 2.1.5 with the mailman-virtual patch for some virtual domains. Because of the usage of suexec on my Webserver i have every vhost running its CGI's with another UID on the system. For being able to access the mailman-binaries i have to create a new vhost that ist only for this, for example lists.domain.tld, configuring in this vhost that cgi's are executed with the UID 'mailman'. Now i want to create a mailinglist [EMAIL PROTECTED], but the URL host for seeing the webpages of the list must be [EMAIL PROTECTED] Do you mean lists.mglug.de? I have read the documentation and i think that add_virtualhost(URL_HOST, MAIL_HOST) has to be what i want, so that when i create a list with the command: bin/newlist [EMAIL PROTECTED] If you carefully read 'bin/newlist --help' you will see the command you want is bin/newlist [EMAIL PROTECTED] i.e., [EMAIL PROTECTED], not [EMAIL PROTECTED] I know this is confusing and it has been addressed in 2.1.6 by adding new options so you could do bin/newlist list --urlhost=lists.mglug.de but this won't work in 2.1.5. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] virtual domain lists
Hi list,
i am running mailman 2.1.5 with the mailman-virtual patch for some virtual
domains.
Because of the usage of suexec on my Webserver i have every vhost running its
CGI's with another UID on the system. For being able to access the
mailman-binaries i have to create a new vhost that ist only for this, for
example lists.domain.tld, configuring in this vhost that cgi's are executed
with the UID 'mailman'.
Now i want to create a mailinglist [EMAIL PROTECTED], but the URL host for
seeing
the webpages of the list must be [EMAIL PROTECTED]
I have read the documentation and i think that add_virtualhost(URL_HOST,
MAIL_HOST) has to be what i want, so that when i create a list with the
command:
bin/newlist [EMAIL PROTECTED]
mailman understands that the webpages for this list are on
http://lists.mglug.de.
I tried this out with my configuration i added to this mail, but
add_virtualhost seems to not have any effect. Can you tell me pls what i am
doing wrong?
Thanks in advance
Christian
my mm_cfg.py:
[...]
###
# Here's where we get the distributed defaults.
from Defaults import *
##
# Put YOUR site-specific settings below this line.
DELIVERY_MODULE = 'SMTPDirect'
SMTPHOST = 'localhost'
SMTPPORT = 10025
SMTP_MAX_RCPTS = 1000
MTA = 'Postfix'
DEFAULT_EMAIL_HOST = 'gentix.de'
DEFAULT_URL_HOST = 'lists.gentix.de'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.citservice.de', 'lists.citservice.de')
add_virtualhost('lists.mglug.de', 'mglug.de')
DEFAULT_SERVER_LANGUAGE = 'de'
IMAGE_LOGOS = '/mailmanicons/'
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Virtual domain not displayed in footer
I managed to change the list URL in mm_cfg.py, so it applies to ALL lists on the server. How do I get it to display the actual virtual domain the list is supposed to use? Below is what I have now. I want to display 'www.damnspam.ca' in the footer on the resp list. The list name and email address come out correctly. === Cut === ## # Put YOUR site-specific settings below this line. DEFAULT_EMAIL_HOST = 'karico.ca' DEFAULT_URL_HOST = 'www.karico.ca' DEFAULT_URL_PATTERN = 'http://%s/mailman/' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) === Cut === Kari Suomela KARICO Business Services Toronto, ON Canada http://www.karico.ca - http://www.damnspam.ca ... Don't believe everything you hear or anything you say. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual domain not displayed in footer
[EMAIL PROTECTED] wrote:
I managed to change the list URL in mm_cfg.py, so it applies to ALL
lists on the server. How do I get it to display the actual virtual
domain the list is supposed to use?
Below is what I have now. I want to display 'www.damnspam.ca' in the
footer on the resp list. The list name and email address come out
correctly.
=== Cut ===
##
# Put YOUR site-specific settings below this line.
DEFAULT_EMAIL_HOST = 'karico.ca'
DEFAULT_URL_HOST = 'www.karico.ca'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
=== Cut ===
It is not clear to me from the above exactly what you're trying to
accomplish. My guess is you have some lists you want to be in the
www.karico.ca domain and some in the www.damnspam.ca domain. The
e-mail domain for the www.karico.ca lists is karico.ca, and (here I'm
really guessing) the e-mail domain for the www.damnspam.ca lists is
damnspam.ca.
Assuming that's what you want, you should have the following in
mm_cfg.py. Note you don't need
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
because you aren't changing it.
=== Cut ===
##
# Put YOUR site-specific settings below this line.
DEFAULT_EMAIL_HOST = 'karico.ca'
DEFAULT_URL_HOST = 'www.karico.ca'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('www.damnspam.ca', 'damnspam.ca')
=== Cut ===
The VIRTUAL_HOSTS.clear() is to remove the entry that was set in
Defaults.py, in case it wouldn't be replaced (same url host key) by
the two above.
Then (after doing 'bin/mailmanctl restart') to pick up these changes,
for each list in the www.karico.ca domain do
bin/withlist -l -r fix_url listname
and for each list in the www.damnspam.ca domain do
bin/withlist -l -r fix_url listname --urlhost=www.damnspam.ca
See FAQ article 4.29 for more info.
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
As I said, I may not understand what you're trying to do, so this may
not be the solution.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Virtual domain not displayed in footer
Wednesday March 16 2005 17:35, Mark Sapiro wrote to Kari Suomela: MS It is not clear to me from the above exactly what you're trying to MS accomplish. My guess is you have some lists you want to be in the MS www.karico.ca domain and some in the www.damnspam.ca domain. The You read my mind. :) Thx, Kari Suomela KARICO Business Services Toronto, ON Canada http://www.karico.ca - http://www.damnspam.ca -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Virtual domain setup problem
Postfix version 2.0.16 Fedora Core 1 mailman 2.1.15 First off none of my email accounts on my email server are local. All are virtual mailbox domains. Now I have a domain topguncomputers.com that accepts the most common email. the fqdn of my server is server.topguncomputers.com So in postfix $mydomain = topguncomputers.com $myhostname = server.topguncomputers.com $myorigin = $mydomain $mydestination = default postfix setting. $virtual_alias_maps = hash:/etc/postfix/valias,hash:/var/mailman/data/virtual-mailman $alias_maps=hash:/etc/aliases,hash:/var/mailman/data/aliases in mm_cfg.py DEFAULT_URL_HOST='topguncomputers.com' DEFAULT_EMAIL_HOST='list.topguncomputers.com' POSTFIX_STYLE_VIRTUAL_DOMAIN=['list.topguncompuers.com'] Ok now if I send an email to the following address [EMAIL PROTECTED] postfix finds it in the virtual-mailman table. and converts it to mail-owner The problem I'm having is that than it trys to append the domain name topguncomputers.com to that and hence forth can't find that email address cause it doesn't exist. So basically [EMAIL PROTECTED] gives me an error of unknown user [EMAIL PROTECTED] in my postfix queue. oh the ower of this mailling list is [EMAIL PROTECTED] And that account does exist and gets email regularly from my server. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Virtual domain problems, Mailman + sendmail
Hello! I need two lists with the same name on the same machine, but for two
different domains. Example: 'staff @ domain1.org' and 'staff @ domain2.org'.
Right now, they have different names ('domain1-staff' and 'domain2-staff') and
with some aliasing, members can post to 'staff @ domain1.org' using that
address, and Mailman will accept and deliver it. However, the url for web
administration is wrong, the welcome emails are wrong; really anything generated
by Mailman claims that the list is 'domain1-staff @ domain1.org' which is the
real internal name and is also *wrong*.
The left-hand-side of alias rules cannot have '@' symbols, so the aliases must
stay the way they are. I need Mailman to know that the lists' name is 'staff @
domain#.org' and perform accordingly.
How is this done?
--
Sunit M. Das : Developer/Analyst
ph# (907) 456-5581 : fax# (907) 456-3111
Engineering Environmental Internet Solutions, LLC
530 7th Ave. Suite #1 : Fairbanks, AK 99701
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virtual domain problems, Mailman + sendmail
S. M. Das wrote:
Hello! I need two lists with the same name on the same
machine, but for two different domains. Example: 'staff @
domain1.org' and 'staff @ domain2.org'.
With the standard installation of Mailman, you can't have the same list
name on more than one domain name. You can only do that if you're running
cPanel and their version of Mailman which they've changed to allow the same
list name on more than one domain.
I have no details on what cPanel changed to allow that, but it's similar to
what you're doing here, the list webpages end with listname_domain, instead
of just listname so Mailman sees the list as [EMAIL PROTECTED] but
aliases it to [EMAIL PROTECTED] in the list webpages and the welcome emails
and so on.
Right now, they have different names ('domain1-staff' and
'domain2-staff') and with some aliasing, members can post to
'staff @ domain1.org' using that address, and Mailman will
accept and deliver it. However, the url for web administration
is wrong, the welcome emails are wrong; really anything
generated by Mailman claims that the list is 'domain1-staff @
domain1.org' which is the real internal name and is also
*wrong*.
hth,
texas critter
--
EL-M FAQ: http://www.emaillist-managers.com/
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] virtual domain complete suppression
I am installing Mailman for the Dept of Comp Sci, Univ of Miami. It is running on a FreeBSD machine named sherman, and we have a firewall. Internally sherman is 172.20.0.2, but for access beyond the firewall it is also 192.31.89.3. The PIX firewall does the address translation. I also make public the pseudo-name i-sherman with IP 172.20.0.2. When using the Mailman http tools remotely, I set up an ssh tunnel into the department and refer to the web server by i-sherman. Mailman however distinguished between sherman and i-sherman. I think this is called virtual domains and I cannot use the web interface as I would like. I would like that Mailman treat sherman and i-sherman as complete synonyms, as aliases. Is there an option? -burt -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] virtual domain complete suppression
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 burton rosenberg wrote: I would like that Mailman treat sherman and i-sherman as complete synonyms, as aliases. If I understand you correctly (and I might not, it's still early in my day and the sugar hasn't kicked in yet), you want mailman to show you the same lists no matter what URL you visit. If so, one of the things you want to look at is the VIRTUAL_HOST_OVERVIEW setting, seen in the Defaults.py file and discussed here just 2 days ago. If you will be creating lists via the web interface, you probably want to make sure that mailman always uses the correct URL and domain what it creates the lists. I think just not having any additional virtual hosts defined will achieve this, but you should create a few test lists to be sure they end up with the settings you want. - -- ToddOpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp == Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE/2fCluv+09NZUB1oRAuYeAJ9I0QIoDZRCX4dpdCf/YwR+YgaSnQCfXznn O6DT/0vLggppiDXBKuee3uk= =75sc -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Virtual domain HOW TO/FAQ/support
Hello, I am kinda new to mailman, and was just wondering if there is a place I can read about how to configure mailman to use virtual domains. for example to show on all the web-pages [EMAIL PROTECTED] instead of [EMAIL PROTECTED] I tried to use aliases but they do not fix this problem. My MTA is sendmail, but i'd llike to know how this can be done for Postfix, Exim as well as Sendmail. Thanx -- KL -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual domain HOW TO/FAQ/support
This is documented multiple times in the list Archives. Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ The short answer is that for Sendmail you need to use the Generic Tables. In the end it is often easier to switch to Postfix. The support for virtual domains on Postfix is much better than for Sendmail Good Luck - Jon Carnes On Sat, 2002-12-14 at 12:38, Kyohere Luke wrote: Hello, I am kinda new to mailman, and was just wondering if there is a place I can read about how to configure mailman to use virtual domains. for example to show on all the web-pages [EMAIL PROTECTED] instead of [EMAIL PROTECTED] I tried to use aliases but they do not fix this problem. My MTA is sendmail, but i'd llike to know how this can be done for Postfix, Exim as well as Sendmail. Thanx -- KL -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual domain HOW TO/FAQ/support
* Jon Carnes [EMAIL PROTECTED] [2002-12-17 17:18:35 -0500]: The short answer is that for Sendmail you need to use the Generic Tables. In the end it is often easier to switch to Postfix. The support for virtual domains on Postfix is much better than for Sendmail He's asking about the email as it displays on the web pages; wouldn't this be a Mailman config issue rather than an MTA issue? -- John Buttery (Web page temporarily unavailable) msg13816/pgp0.pgp Description: PGP signature -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual domain HOW TO/FAQ/support
Good point, he did specifically mention the web pages - so why didn't you answer the question...? The best answer on the web page displays is to use the latest beta which has better support for virtual domains. On Tue, 2002-12-17 at 20:45, John Buttery wrote: * Jon Carnes [EMAIL PROTECTED] [2002-12-17 17:18:35 -0500]: The short answer is that for Sendmail you need to use the Generic Tables. In the end it is often easier to switch to Postfix. The support for virtual domains on Postfix is much better than for Sendmail He's asking about the email as it displays on the web pages; wouldn't this be a Mailman config issue rather than an MTA issue? -- John Buttery (Web page temporarily unavailable) -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Virtual domain HOW TO/FAQ/support
* Jon Carnes [EMAIL PROTECTED] [2002-12-17 22:28:08 -0500]: Good point, he did specifically mention the web pages - so why didn't you answer the question...? Well, mostly it's because most of the best answers on this list come from you, so I half-assumed my answer was misguided (I know it isn't wrong, because I have Mailman working using sendmail without having edited genericstable). Secondarily because I didn't know the answer. :) The best answer on the web page displays is to use the latest beta which has better support for virtual domains. Personally, I'm not really much help on this, due to the fact that it just worked out of the box for me. I'm using the hostname lists.domain.com instead of the machine's primary name and it works OK; I had to configure Mailman to use this hostname, but I didn't have to do any fancy footwork with it or the MTA... -- John Buttery (Web page temporarily unavailable) msg13823/pgp0.pgp Description: PGP signature -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Virtual domain
Hi To day I run a number of majordomo lists. They are set up on a server that's not hosting the domains for which it server as listserver. Fx an address [EMAIL PROTECTED] would forward to [EMAIL PROTECTED] corresponding a list called infolist_domain. Majordomo then sends to the list members as is the list was called [EMAIL PROTECTED] in a way that you would have to look at the raw headers to see that the real origin is not domain.com. Can this be done with mailman? - Jens -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virtual domain
* Jens W. Skov - JS Consult [EMAIL PROTECTED] [20020903 18:45]: wrote: Hi To day I run a number of majordomo lists. They are set up on a server that's not hosting the domains for which it server as listserver. Fx an address [EMAIL PROTECTED] would forward to [EMAIL PROTECTED] corresponding a list called infolist_domain. Majordomo then sends to the list members as is the list was called [EMAIL PROTECTED] in a way that you would have to look at the raw headers to see that the real origin is not domain.com. Can this be done with mailman? Hello Jens, I am also interested in this virtual hosting. Please CC me if you get any solution/suggestions. cheers - wash +--+-+ Odhiambo Washington, [EMAIL PROTECTED] . WANANCHI ONLINE LTD (Nairobi, KE) | http://ns2.wananchi.com/~wash/ . 1ere Etage, Loita Hse, Loita St., | GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI | +-+--+ Oh My God! They killed init! You Bastards! --from a /. post -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virtual domain
If your server is wrapping mailman in suexec, http://httpd.apache.org/docs/suexec.html then, your list admin will notresolve to your own domain name. It will look something like: http://ourserver.com/mailman/admin/list_virtualdomain.net instead of: http://virtualdomain.net/mailman/admin/list/ and http://virtualdomain.net/mailman/listinfo/list-users_virtualdomain.net/ .. This is all done because of precautions of plugging any holes for hackers to access. If your server owner does not use suexec, then, one mailman install should handle all domains lists on their own domain. tom - Original Message - From: Odhiambo Washington To: Jens W. Skov - JS Consult Cc: [EMAIL PROTECTED] Sent: Tuesday, September 03, 2002 11:55 AM Subject: Re: [Mailman-Users] Virtual domain * Jens W. Skov - JS Consult [EMAIL PROTECTED] [20020903 18:45]: wrote: Hi To day I run a number of majordomo lists. They are set up on a server that's not hosting the domains for which it server as listserver. Fx an address [EMAIL PROTECTED] would forward to [EMAIL PROTECTED] corresponding a list called infolist_domain. Majordomo then sends to the list members as is the list was called [EMAIL PROTECTED] in a way that you would have to look at the raw headers to see that the real origin is not domain.com. Can this be done with mailman?Hello Jens,I am also interested in this virtual hosting. Please CC me if you get anysolution/suggestions. cheers - wash
Re: [Mailman-Users] Virtual domain
* hotmail user [EMAIL PROTECTED] [20020903 19:19]: wrote: If your server is wrapping mailman in suexec, http://httpd.apache.org/docs/suexec.html then, your list admin will not resolve to your own domain name. It will look something like: http://ourserver.com/mailman/admin/list_virtualdomain.net instead of: http://virtualdomain.net/mailman/admin/list/ and http://virtualdomain.net/mailman/listinfo/list-users_virtualdomain.net/ .. This is all done because of precautions of plugging any holes for hackers to access. If your server owner does not use suexec, then, one mailman install should handle all domains lists on their own domain. Hello Tom, Do you have a short HOWTO on this option that doesn't use suexec? cheers - wash +--+-+ Odhiambo Washington, [EMAIL PROTECTED] . WANANCHI ONLINE LTD (Nairobi, KE) | http://ns2.wananchi.com/~wash/ . 1ere Etage, Loita Hse, Loita St., | GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI | +-+--+ Oh My God! They killed init! You Bastards! --from a /. post -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virtual domain
It is my understanding, that either; suexec is enabled or it's not enabled on the entire server. There isn't a way that I am aware of to"pick choose" suexec or not. It would be up to the server owner whether suexec is enabled or not; and unfortunately, for those small businesses that resell hosting, or otherwise use shared hosting, our hands are tied, so to speak. Server owners want to protect the server, naturally, and with that, comes sacrifice of running one install of mailman for multiple domains. I suppose, it would be feasable to install an itineration of mailman, in each virtual domain, which would then sacrifice space, and make upgrading a chore. So, no easy answer, unless Barry comes up with a workaround. If I'm off the base, here, maybe someone can enlighten me. I would love to have a solution, since, I don't yet host enough sites to warrant a dedicated server, but also, when I do grow and begin having resellers sharing MY server, I would be nice to have a solution, without compromising the security of the server. tom - Original Message - From: Odhiambo Washington To: hotmail user Cc: Odhiambo Washington ; Jens W. Skov - JS Consult ; [EMAIL PROTECTED] Sent: Tuesday, September 03, 2002 12:26 PM Subject: Re: [Mailman-Users] Virtual domain * hotmail user [EMAIL PROTECTED] [20020903 19:19]: wrote: If your server is wrapping mailman in suexec, http://httpd.apache.org/docs/suexec.html then, your list admin will not resolve to your own domain name. It will look something like: http://ourserver.com/mailman/admin/list_virtualdomain.net instead of: http://virtualdomain.net/mailman/admin/list/ and http://virtualdomain.net/mailman/listinfo/list-users_virtualdomain.net/ .. This is all done because of precautions of plugging any holes for hackers to access. If your server owner does not use suexec, then, one mailman install should handle all domains lists on their own domain. Hello Tom,Do you have a short HOWTO on this option that doesn't use suexec? cheers - wash
Re: [Mailman-Users] Virtual domain
The current version of Mailman leaves this to the MTA to figure out. If you were using Sendmail then you would setup the Generics tables with each list to indicate the domains that the lists should appear to be from. In postfix, exim, and qmail this is part of the standard install (correct me folks if I'm wrong). You'll have to read up on the MTA that you are going to be using in order to handle the virtual domains properly. HtH, Jon Carnes On Tue, 2002-09-03 at 11:43, Jens W. Skov - JS Consult wrote: Hi To day I run a number of majordomo lists. They are set up on a server that's not hosting the domains for which it server as listserver. Fx an address [EMAIL PROTECTED] would forward to [EMAIL PROTECTED] corresponding a list called infolist_domain. Majordomo then sends to the list members as is the list was called [EMAIL PROTECTED] in a way that you would have to look at the raw headers to see that the real origin is not domain.com. Can this be done with mailman? - Jens -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Virtual Domain
Hi all, I am new to Postfix and Mailman. I have Mailman running (sucessfully:-) on a machine somedomain.co.uk and this machine is also a virtual host for otherdomain.co.uk Can mailman run a list for [EMAIL PROTECTED] whilst still allowing Postfix to collect all other mail for otherdomain and send it to a POP3 box or relay it? Any ponters gratefully accepted... Simon North Staffordshire England On a lovely Autumn day -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] virtual domain
Hi there, OS: RedHat 7.1 I setup all domains as virtual and all the users are popuser. Server domain name is resolved to "maindomain.com" with ip address of 139.aaa.bbb.ccc there are two other virtual domains under this domain called: virtual-domain-1.com with ip address of 203.aaa.bbb.ccc virtual-domain-2.com with ip address of 203.eee.fff.ggg alias file for the main domain is in /etc/aliases alias file for the virtual domains are in: /etc/vmail/virtual-domain-1.com/aliases.virtual-domain-1.com /etc/vmail/virtual-domain-2.com/aliases.virtual-domain-2.com Remember there are no real users here only root and now mailman. action I installed mailman 2.0.1-2.rpm By default mailman is installed in /var/mailman mailman user is created:mailman uid and gid both are 41 and alias file in /etc/aliases is updated as follwed: mailman: postmaster mailman-owner: mailman ok, here I start to create a list: I edit mm_cfg to add my default domain name and URL, I type this: changed DEFAULT_HOST_NAME= ' virtual-domain-1.com' changed DEFAULT_URL= ' http://www.virtual-domain-1.com/mailman/' I left the rest as is and done the web setting for httpd.conf I want to use one of the virtual-domains, not the main server domain. next step I create a list: /var/mailman/bin/newlist call the list "test" then the name for the admin: [EMAIL PROTECTED] asked me for a pass word "test" the final message is: test: "|/var/mailman/mail/wrapper post test" test-admin:"|/var/mailman/mail/wrappermailowner test" test-request: "|/var/mailman/mail/wrappermailcmd test" test-owner:test-admin --- By reading the installation file I assume I have to add these 4 lines in /etc/aliases file I did and run newaliases to update the alias file. ***now test*** I add a user to the list call it "[EMAIL PROTECTED]; no problem The usere recived a notification and was accepted, *** problem here*** If that test-user send a posting to [EMAIL PROTECTED] the message get posted no error or bounce. mail log say the mail was send:ok But the user doesn't get the posted message. no matter how many valid users I add to the list the don't get postings. ** alternatives ** I add the previous 4 lines to the virtual-doman-1.com alias file to see where the problem is. Still no error and mail get send to the list, but still no posting coming back to the users. I check for problems in /var/mailman/logs no errors, and smtp and post say the message was accepted. Where these posting are getting stored? I don't see them anywhere!! Any clues? - Regards, Vania
[Mailman-Users] Virtual Domain problem
Hi there, OS: RedHat 7.1 I setup all domains as virtual and all the users are popuser. Server domain name is resolved to maindomain.com with ip address of 139.aaa.bbb.ccc there are two other virtual domains under this domain called: virtual-domain-1.com with ip address of 203.aaa.bbb.ccc virtual-domain-2.com with ip address of 203.eee.fff.ggg alias file for the main domain is in /etc/aliases alias file for the virtual domains are in: /etc/vmail/virtual-domain-1.com/aliases.virtual-domain-1.com /etc/vmail/virtual-domain-2.com/aliases.virtual-domain-2.com Remember there are no real users here only root and now mailman. action I installed mailman 2.0.1-2.rpm By default mailman is installed in /var/mailman mailman user is created: mailman uid and gid both are 41 and alias file in /etc/aliases is updated as follwed: mailman: postmaster mailman-owner: mailman ok, here I start to create a list: I edit mm_cfg to add my default domain name and URL, I type this: changed DEFAULT_HOST_NAME= ' virtual-domain-1.com' changed DEFAULT_URL= ' http://www.virtual-domain-1.com/mailman/' I left the rest as is and done the web setting for httpd.conf I want to use one of the virtual-domains, not the main server domain. next step I create a list: /var/mailman/bin/newlist call the list test then the name for the admin: [EMAIL PROTECTED] asked me for a pass word test the final message is: test:|/var/mailman/mail/wrapper post test test-admin: |/var/mailman/mail/wrapper mailowner test test-request:|/var/mailman/mail/wrapper mailcmd test test-owner: test-admin --- By reading the installation file I assume I have to add these 4 lines in /etc/aliases file I did and run newaliases to update the alias file. ***now test*** I add a user to the list call it [EMAIL PROTECTED]; no problem The usere recived a notification and was accepted, *** problem here*** If that test-user send a posting to [EMAIL PROTECTED] the message get posted no error or bounce. mail log say the mail was send:ok But the user doesn't get the posted message. no matter how many valid users I add to the list the don't get postings. ** alternatives ** I add the previous 4 lines to the virtual-doman-1.com alias file to see where the problem is. Still no error and mail get send to the list, but still no posting coming back to the users. I check for problems in /var/mailman/logs no errors, and smtp and post say the message was accepted. Where these posting are getting stored? I don't see them anywhere!! Any clues? - Regards, Vania -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
