Re: [Mailman-Users] Mailman, Postfix & virtual domains

[Mark Sapiro]

On 6/24/2011 6:29 AM, Aranel Doriath wrote:
> Hi all. 
> I have Centos 5.5 server with Postfix, configured to work in AD, and i want 
> to add the mailman aliases:
> 
> main.cf:
> virtual_alias_maps = ldap:/etc/postfix/ldap-groups.cf, 
> ldap:/etc/postfix/ldap-groups2.cf, hash:/etc/postfix/valias
> 
> /etc/postfix/aliases looks like:
> mailman@pmz.local  "|/usr/lib/mailman/mail/mailman post mailman"


This alias is not correct. You should consider Mailman/Postfix
integration as discussed at
. In any case, the left
part of the alias (in alias_maps) should be a local_part only and
terminated with a colon as

mailman:"|/usr/lib/mailman/mail/mailman post mailman"

If you need virtual mappings (virtual_alias_maps), those entries look like

mailman@pmz.local  mailman

and map the virtual domain address mailman@pmz.local to the local
address mailman which is in turn mapped to the pipe by alias_maps.


> But i recieved this:
> 
> "|/usr/lib/mailman/mail/mailman post mailman"@melchior.kolos.local> (expanded 
> from ): unknown user: "|/usr/lib/mailman/mail/mailman post 
> mailman" 
> 
> How can i connect Mailman to Postfix? 


It is hard to say for sure without at least the output of 'postconf -n',
but it looks like you may have a file containing aliases that belongs in
alias_maps included in virtual_alias_maps instead or in addition.

There are many threads on this subject in the archives of this list. See
the FAQ at  for information on searching
the archives.

-- 
Mark Sapiro 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
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] Mailman, Postfix & virtual domains

[Aranel Doriath]

Hi all. 
I have Centos 5.5 server with Postfix, configured to work in AD, and i want to 
add the mailman aliases:

main.cf:
virtual_alias_maps = ldap:/etc/postfix/ldap-groups.cf, 
ldap:/etc/postfix/ldap-groups2.cf, hash:/etc/postfix/valias

/etc/postfix/aliases looks like:
mailman@pmz.local              "|/usr/lib/mailman/mail/mailman post mailman"

But i recieved this:

"|/usr/lib/mailman/mail/mailman post mailman"@melchior.kolos.local> (expanded 
from ): unknown user: "|/usr/lib/mailman/mail/mailman post 
mailman" 

How can i connect Mailman to Postfix? 
P.S. Sorry for my English :)
--
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] Mailman, postfix virtual domains and mysql

[Leon Kolchinsky]

> -Original Message-
> From: Brad Knowles [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 22, 2007 8:02 PM
> To: Peter Coolen; mailman-users@python.org
> Subject: Re: [Mailman-Users] Mailman, postfix virtual domains and mysql
> 
> At 3:24 PM +0100 1/22/07, Peter Coolen wrote:
> 
> >  Does someone have a manual for postfix virtual domains with mysql? I
> looked
> >  it up in the site administrators manual but that's all about virtual
> domains
> >  and not about mysql.. My config files are very different.
> 

You can look at my little howto here -
http://www.web-cyradm.org/pipermail/web-cyradm/2005-August/019307.html

It's an integration of Web-cyradm (postfix+cyrus+mysql virt. domains+web
interface) with mailman installation.



Best Regards,
Leon Kolchinsky


> This is a problem with postfix, and you're much more likely to get
> something useful from the documentation & FAQs at postfix.org, as
> well as reading the archives of the postfix-users mailing list,
> etc  If you still don't find the answers to your questions after
> going through all those resources, you might want to post your
> question to the postfix-users list.
> 
> Once you get your postfix issues straightened out, we might be able
> to help you with your Mailman issues.
> 
> --
> Brad Knowles <[EMAIL PROTECTED]>, Consultant & Author
> Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and
> Responsibilities"
> Founding Member and Platinum Individual Sponsor of LOPSA:
> <http://www.lopsa.org>
> Papers: <http://tinyurl.com/tj6q4> LinkedIn Profile:
> <http://tinyurl.com/y8kpxu>


--
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=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman, postfix virtual domains and mysql

[Brad Knowles]

At 3:24 PM +0100 1/22/07, Peter Coolen wrote:

>  Does someone have a manual for postfix virtual domains with mysql? I looked
>  it up in the site administrators manual but that's all about virtual domains
>  and not about mysql.. My config files are very different.

This is a problem with postfix, and you're much more likely to get 
something useful from the documentation & FAQs at postfix.org, as 
well as reading the archives of the postfix-users mailing list, 
etc  If you still don't find the answers to your questions after 
going through all those resources, you might want to post your 
question to the postfix-users list.

Once you get your postfix issues straightened out, we might be able 
to help you with your Mailman issues.

-- 
Brad Knowles <[EMAIL PROTECTED]>, Consultant & Author
Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and 
Responsibilities"
Founding Member and Platinum Individual Sponsor of LOPSA: 

Papers:  LinkedIn Profile: 

--
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=show&file=faq01.027.htp

[Mailman-Users] Mailman, postfix virtual domains and mysql

[Peter Coolen]

Hi All,
 
Mailman almost works... First some problems with the webserver but that's
almost solved (can't use the list creaters and adminstrator password)
 
Also got the following problem:
 
I have a working postfix, mysql and virtual domains on the testserver.. This
works fine and is also on the main server.. 
 
Now I want to install mailman (done) and integrate with my mailserver..
 
Does someone have a manual for postfix virtual domains with mysql? I looked
it up in the site administrators manual but that's all about virtual domains
and not about mysql.. My config files are very different.
 
I use mysql_virtual_alias_maps, mysql_virtual_domains_maps and
mysql_virtual_mailbox_maps files
 
In these files are the following lines (table, select_field and where_field
are different):
user = username
password = password
hosts = localhost
dbname = Databasename
table = mailbox
select_field = maildir
where_field = username
 
 
Can someone help me with this?
 
Thanks
 
--
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=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman + Postfix + virtual domains

[Jon Carnes]

Are you running Mailmanctl (the Mailman daemon)?
What do the Mailman logs show?

Jon Carnes

On Fri, 2003-09-19 at 20:39, Anthony Chavez wrote:
> I'm encountering a very peculiar issue here.
> 
> First off, my versioning information: mailman 2.1.2, Postfix 2.0.14 and
> FreeBSD 4.9-PRERELEASE.
> 
> If I create [EMAIL PROTECTED] and try to post to it, it ~seems~ to get
> passed along with no problems, according to /var/log/maillog:
> 
> Sep 19 18:12:53 athena postfix/local[82950]: 5C6FA253: to=<[EMAIL PROTECTED]>, 
> orig_to=<[EMAIL PROTECTED]>, relay=local, delay=1, status=sent 
> ("|/usr/local/mailman/mail/mailman post test")
> 
> But the post disappears entirely.  It doesn't even get placed in the
> archives!
> 
> Here are my configuration files.  I'm not sure if this is sufficient,
> but if you need more, please let me know.  I would very much appreciate
> some help with this!  Thanks!
> 
> mm_cfg.py:
> --8<---cut here---start->8---
> # -*- python -*-
> 
> # Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
> #
> # This program is free software; you can redistribute it and/or
> # modify it under the terms of the GNU General Public License
> # as published by the Free Software Foundation; either version 2
> # of the License, or (at your option) any later version.
> # 
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY; without even the implied warranty of
> # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> # GNU General Public License for more details.
> # 
> # You should have received a copy of the GNU General Public License
> # along with this program; if not, write to the Free Software 
> # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
> 
> """This module contains your site-specific settings.
> 
> From a brand new distribution it should be copied to mm_cfg.py.  If you
> already have an mm_cfg.py, be careful to add in only the new settings you
> want.  Mailman's installation procedure will never overwrite your mm_cfg.py
> file.
> 
> The complete set of distributed defaults, with documentation, are in the file
> Defaults.py.  In mm_cfg.py, override only those you want to change, after the
> 
>   from Defaults import *
> 
> line (see below).
> 
> Note that these are just default settings; many can be overridden via the
> administrator and user interfaces on a per-list or per-user basis.
> 
> """
> 
> ###
> # Here's where we get the distributed defaults.
> 
> From Defaults import *
> 
> ##
> # Put YOUR site-specific settings below this line.
> 
> MTA = 'Postfix'
> POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'bsdevents.org', 'gubug.org' ]
> DEFAULT_EMAIL_HOST = 'anthonychavez.org'
> DEFAULT_URL_HOST = 'www.anthonychavez.org'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> add_virtualhost('www.bsdevents.org', 'bsdevents.org')
> add_virtualhost('www.gubug.org', 'gubug.org')
> --8<---cut here---end--->8---
> 
> main.cf:
> --8<---cut here---start->8---
> # Global Postfix configuration file. This file lists only a subset
> # of all 300+ parameters. See the sample-xxx.cf files for a full list.
> # 
> # The general format is lines with parameter = value pairs. Lines
> # that begin with whitespace continue the previous line. A value can
> # contain references to other $names or ${name}s.
> #
> # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
> # POSTFIX STILL WORKS AFTER EVERY CHANGE.
> 
> # SOFT BOUNCE
> #
> # The soft_bounce parameter provides a limited safety net for
> # testing.  When soft_bounce is enabled, mail will remain queued that
> # would otherwise bounce. This parameter disables locally-generated
> # bounces, and prevents the SMTP server from rejecting mail permanently
> # (by changing 5xx replies into 4xx replies). However, soft_bounce
> # is no cure for address rewriting mistakes or mail routing mistakes.
> #
> #soft_bounce = no
> 
> # LOCAL PATHNAME INFORMATION
> #
> # The queue_directory specifies the location of the Postfix queue.
> # This is also the root directory of Postfix daemons that run chrooted.
> # See the files in examples/chroot-setup for setting up Postfix chroot
> # environments on different UNIX systems.
> #
> queue_directory = /var/spool/postfix
> 
> # The command_directory parameter specifies the location of all
> # postXXX commands.
> #
> command_directory = /usr/local/sbin
> 
> # The daemon_directory parameter specifies the location of all Postfix
> # daemon programs (i.e. programs listed in the master.cf file). This
> # directory must be owned by root.
> #
> daemon_directory = /usr/local/libexec/postfix
> 
> # QUEUE AND PROCESS OWNERSHIP
> #
> # The mail_owner parameter specifies the owner of the Postfix queue
> # and of most Postfix daemon processe

[Mailman-Users] Mailman + Postfix + virtual domains

[Anthony Chavez]

I'm encountering a very peculiar issue here.

First off, my versioning information: mailman 2.1.2, Postfix 2.0.14 and
FreeBSD 4.9-PRERELEASE.

If I create [EMAIL PROTECTED] and try to post to it, it ~seems~ to get
passed along with no problems, according to /var/log/maillog:

Sep 19 18:12:53 athena postfix/local[82950]: 5C6FA253: to=<[EMAIL PROTECTED]>, 
orig_to=<[EMAIL PROTECTED]>, relay=local, delay=1, status=sent 
("|/usr/local/mailman/mail/mailman post test")

But the post disappears entirely.  It doesn't even get placed in the
archives!

Here are my configuration files.  I'm not sure if this is sufficient,
but if you need more, please let me know.  I would very much appreciate
some help with this!  Thanks!

mm_cfg.py:
--8<---cut here---start->8---
# -*- python -*-

# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
# 
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
# 
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software 
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

"""This module contains your site-specific settings.

From a brand new distribution it should be copied to mm_cfg.py.  If you
already have an mm_cfg.py, be careful to add in only the new settings you
want.  Mailman's installation procedure will never overwrite your mm_cfg.py
file.

The complete set of distributed defaults, with documentation, are in the file
Defaults.py.  In mm_cfg.py, override only those you want to change, after the

  from Defaults import *

line (see below).

Note that these are just default settings; many can be overridden via the
administrator and user interfaces on a per-list or per-user basis.

"""

###
# Here's where we get the distributed defaults.

From Defaults import *

##
# Put YOUR site-specific settings below this line.

MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'bsdevents.org', 'gubug.org' ]
DEFAULT_EMAIL_HOST = 'anthonychavez.org'
DEFAULT_URL_HOST = 'www.anthonychavez.org'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('www.bsdevents.org', 'bsdevents.org')
add_virtualhost('www.gubug.org', 'gubug.org')
--8<---cut here---end--->8---

main.cf:
--8<---cut here---start->8---
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the sample-xxx.cf files for a full list.
# 
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
#
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.

# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing.  When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#
#soft_bounce = no

# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/local/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/local/libexec/postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes.  Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external fil

AW: [Mailman-Users] mailman + postfix + virtual domains

[Patrick Ben Koetter]

Hi Matthew,

your idea works like a charm.
Shame on me, I have the same book. :(
You have the book and the better understanding. :)

thanks,

p@rick

> >I have a postfix daemon running, accepting and delivering 
> mails for my
> >local domain and a few virtual domains.
> >Now I want to integrate mailman as listserver for one of 
> the virtual
> >(!) domains.
> >
> >My problem is:
> >The output generated by bin/newlist applies for 
> 'alias'-style maps and
> >not for a postfix 'virtual' map. And this is where my 
> problems start:
> 
> Now perusing the Postfix book it looks as if you should be 
> able to do what you
> want on one machine like this:
> 
> /etc/postfix/virtual
> 
> virtual.domain DOMAIN
> [EMAIL PROTECTED]list
> [EMAIL PROTECTED]  list-admin
> [EMAIL PROTECTED]list-request
> [EMAIL PROTECTED]  list-admin
> 
> another.domain DOMAIN
> [EMAIL PROTECTED]   thing
> [EMAIL PROTECTED] thing-admin
> [EMAIL PROTECTED]   thing-request
> [EMAIL PROTECTED] thing-admin
> 
> 
> /etc/postfix/aliases
> 
> list:"|/mailman/mail/wrapper post list"
> list-admin:  "|/mailman/mail/wrapper mailowner list"
> list-request:"|/mailman/mail/wrapper mailcmd list"
> list-owner:  list-admin
> 
> thing:   "|/mailman/mail/wrapper post thing"
> thing-admin: "|/mailman/mail/wrapper mailowner thing"
> thing-request:   "|/mailman/mail/wrapper mailcmd thing"
> thing-owner: thing-admin
> 
> 
> However since each "list" in a virtual domain points at a 
> local "user" and those
> local users must be unique so too the list names must be 
> unique over ALL the
> virtual domains:
> 
> ie you cannot have
> 
> [EMAIL PROTECTED]  and mylist@seconddomain.
> 
> 
> Mmm...  perhaps worth saying again, I'm looking at a book, 
> I *haven't* set it up
> like this myself.
> 
> 
> Matthew
> 
> NB: The book refered to is "Postfix", by Richard Blum, Sams 
> Publishing.  ISBN 0-672-32114-9

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] mailman + postfix + virtual domains

[matthew . malthouse]

On 29/01/2002 00:50:12 Patrick Ben Koetter wrote:

>I have a postfix daemon running, accepting and delivering mails for my
>local domain and a few virtual domains.
>Now I want to integrate mailman as listserver for one of the virtual
>(!) domains.
>
>My problem is:
>The output generated by bin/newlist applies for 'alias'-style maps and
>not for a postfix 'virtual' map. And this is where my problems start:

I'm uncertain how this might work on one machine as I host many virtual domains
on a relay while the list servers are on other machines.  However, for what it
might or might not be worth:

Relay's virtual file

lists.this.domain.tldDOMAIN
@lists.this.domain.tld @lists.real.address
# sends all mail for @lists to lists machine

On the lists machine aliases as normal.



Now perusing the Postfix book it looks as if you should be able to do what you
want on one machine like this:

/etc/postfix/virtual

virtual.domain DOMAIN
[EMAIL PROTECTED]list
[EMAIL PROTECTED]  list-admin
[EMAIL PROTECTED]list-request
[EMAIL PROTECTED]  list-admin

another.domain DOMAIN
[EMAIL PROTECTED]   thing
[EMAIL PROTECTED] thing-admin
[EMAIL PROTECTED]   thing-request
[EMAIL PROTECTED] thing-admin


/etc/postfix/aliases

list:"|/mailman/mail/wrapper post list"
list-admin:  "|/mailman/mail/wrapper mailowner list"
list-request:"|/mailman/mail/wrapper mailcmd list"
list-owner:  list-admin

thing:   "|/mailman/mail/wrapper post thing"
thing-admin: "|/mailman/mail/wrapper mailowner thing"
thing-request:   "|/mailman/mail/wrapper mailcmd thing"
thing-owner: thing-admin


However since each "list" in a virtual domain points at a local "user" and those
local users must be unique so too the list names must be unique over ALL the
virtual domains:

ie you cannot have

[EMAIL PROTECTED]  and mylist@seconddomain.


Mmm...  perhaps worth saying again, I'm looking at a book, I *haven't* set it up
like this myself.


Matthew

NB: The book refered to is "Postfix", by Richard Blum, Sams Publishing.  ISBN
0-672-32114-9




--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users

[Mailman-Users] mailman + postfix + virtual domains

[Patrick Ben Koetter]

Hi there,

I'm not sure if this is OT.

I have a postfix daemon running, accepting and delivering mails for my
local domain and a few virtual domains.
Now I want to integrate mailman as listserver for one of the virtual
(!) domains.

My problem is:
The output generated by bin/newlist applies for 'alias'-style maps and
not for a postfix 'virtual' map. And this is where my problems start:

1. alias_maps doesn't work for virtual domains
If I configure postfix to look up the lists in the alias_maps section
it cannot find the corresponding users because they belong to the
virtual domain.
Exception: I set the hostname in 'mydestination' which I am not
supposed to do when I run postfix with virtual domains the
'postfix-style'. H...

2. virtual_maps won't execute 'wrapper' correctly
So I moved the mailman-alias-map into postfix's virtual_map section
and edited the map file. I deleted the ':', added '@virtualdom.ain' to
the user names and left the paths to 'wrapper' including the commands
untouched.
Example:
[EMAIL PROTECTED]
"|/PATH_TO_MAILMAN/mailman/mail/wrapper post events"

Now postfix started complaining that it couldn't find the user,
because something went wrong when it tried to deliver to 'wrapper'.
DoubleH...

I think, that the virtual map does not support scripts to be executed
as I understand that alias maps on contrary do. to prove that I read
threads in the postfix lists and had a look at "Postfix" by Richard
Blum. I couldn't find anything to prove I'm wrong with my idea. Still
that doesn't fix my problem :-|

What am I doing the wrong way? Has anybody managed to integrate
mailman with postfix virtual domains?
Did I totally misunderstand something? Should I go to bed and get some
sleep ;-)

thanks for pointing me towards the right direction,


p@rick


--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users