Re: [Mailman-Users] Mailman on multiple domains

2008-10-31 Thread Mark Sapiro
TGPlatt, WebMaster wrote:
>
>VIRTUAL_HOSTS = {'firstdomain.net':'firstdomain.net',
> 'seconddomain.com':'seconddomain.com',
> 'thirddomain.com':'thirddomain.com'}


Just FYI the abbove is EXACTLY eqiivalent to

VIRTUAL_HOSTS = {}
add_virtualhost('firstdomain.net', 'firstdomain.net')
add_virtualhost('seconddomain.com', 'seconddomain.com')
add_virtualhost('thirddomain.com', 'thirddomain.com')

I.e. all add_virtualhost() does is add an entry to the VIRTUAL_HOSTS
dictionary with key = the first arg and value = the second arg.


>At this point I only have the mailman list for one of these domains working.
>If I understand the requirements correctly, I will eventually need to add
>"add_virtualhost" lines for 
>
>add_virtualhost('www.seconddomain.com', 'seconddomain.com')
>add_virtualhost('www.thirddomain.com','thirddomain.com')


Actually, these conflict mildly with what you have. The issue is how
you want to access the web interface for these domains.
http://seconddomain.com/mailman/... or
http://www.seconddomain.com/mailman/... . If the former, you want what
you have now or what I indicated was equivalent. If the latter, you
want what you have immediately above, but you probably don't want both.


>Other than those changes which I expect to need to make, the way I have it
>configured now seems to be working. 
>
>There were also setup requirements in Apache's virtualhost definition files
>too. But the way this is setup is unique on Debian. So I won't try to
>explain it except to say Apache's VirtualHost definition files need these
>lines included:
>
>## Mailman Setup
>ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/


Yes, you need the above, but not necessarily in each 
section. You can have it just once outside of the 
sections.


>
>#AddDefaultCharset Off
>


The above 3 lines appear to do nothing.

-- 
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] Mailman on multiple domains

2008-10-31 Thread TGPlatt, WebMaster
I'm running MM 2.1.11 on Debian Etch4.0r3 with Postfix 2.3.8. I hesitate to
explain how I made this work... In fact perhaps I shouldn't. It could jinx
me. But in our case, I've got the individual LOCAL virtual email addresses
for each domain defined in the /etc/postfix/virtual file and I've allowed
mailman to define the local virtual email addresses IT needs for the same
domain in the /usr/local/mailman/data/virtual-mailman file. These lists are
mapped to postfix ".db" files /etc/postfix/virtual.db and
/usr/local/mailman/data/virtual-mailman.db

These files are defined this way in /etc/postfix/main.cf:

virtual_alias_maps = hash:/etc/postfix/virtual
hash:/usr/local/mailman/data/virtual-mailman

and in /usr/local/mailman/Mailman/mm_cfg.py they're defined this way:

#
# 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.example.com':'example.com',
#  'lists.somethingelse.com':'somethingelse.com'}

VIRTUAL_HOSTS = {'firstdomain.net':'firstdomain.net',
 'seconddomain.com':'seconddomain.com',
 'thirddomain.com':'thirddomain.com'}

IMAGE_LOGOS = '/icons/'

MTA = 'Postfix'

#
# added this line to enable POSTFIX_STYLE_VIRTUAL_DOMAINS # details see:
www.gnu.org/software/mailman/mailman-install/postfix-virtual.html
# also: www.howtoforge.com/forums/showthread.php?t=5311
# POSTFIX_STYLE_VIRTUAL_DOMAINS = ['',]

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['firstdomain.net', 'seconddomain.com',
'thirddomain.com']

# Are archives public or private by default?
# 0=public, 1=private
DEFAULT_ARCHIVE_PRIVATE = 1

# ARCHIVE_TO_MBOX
#-1 - do not do any archiving
# 0 - do not archive to mbox, use builtin mailman html archiving only # 1 -
do not use builtin mailman html archiving, archive to mbox only # 2 -
archive to both mbox and builtin mailman html archiving.
# See the settings below for PUBLIC_EXTERNAL_ARCHIVER and
# PRIVATE_EXTERNAL_ARCHIVER which can be used to replace mailman's
# builtin html archiving with an external archiver.  The flat mail
# mbox file can be useful for searching, and is another way to
# interface external archivers, etc.
ARCHIVE_TO_MBOX = 2

At this point I only have the mailman list for one of these domains working.
If I understand the requirements correctly, I will eventually need to add
"add_virtualhost" lines for 

add_virtualhost('www.seconddomain.com', 'seconddomain.com')
add_virtualhost('www.thirddomain.com','thirddomain.com')

Other than those changes which I expect to need to make, the way I have it
configured now seems to be working. 

There were also setup requirements in Apache's virtualhost definition files
too. But the way this is setup is unique on Debian. So I won't try to
explain it except to say Apache's VirtualHost definition files need these
lines included:

## Mailman Setup
ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/

#AddDefaultCharset Off


I HOPE I've got this right. Most of all, I hope this helps you, Scott.

Good Luck!

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 2:13 PM
To: Scott Race
Cc: mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman on multiple domains

Scott Race wrote:
>
>Thanks, fixed the domain name in the mm_cfg.py to read
['second-domain.com'].
>
>Running the /bin/genaliases doesn't return an error, but doesn't
>generate the /data/virtual-mailman file.  The mailman error logs don't
>show anything (no errors since Oct 22).
>
>Sounds like the virtual-mailman file missing is my main problem, huh?


Yes.

Go to the list's General Options page and look near the bottom at "Host
name this list prefers for email.". Does this match second-domain.com?

What you ultimately need to do to configure all this depends on whether
or not you will have multiple Mailman domains or a single Mailman
domain.

If there is only a single mailman domain = second-domain.com you want
something like

DEFAULT_URL_HOST = 'www.second-domain.com'
DEFAULT_EMAIL_HOST = 'second-domain.com'
add_virtual_hosts(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

in mm_cfg.py

and then run

bin/withlist -l -a -r fix_url

to fix the web_page_url and host_name attributes of all the lists.

If you have more Mailman domains, it's more complex, but until you have
the proper host_name for your lists, genaliases won't create/update
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/

Re: [Mailman-Users] Mailman on multiple domains

2008-10-31 Thread Scott Race
Checked the permissions:

Mailman directory:
drwxrwsr-x   2 root   mailman4096 Oct 31 16:41 mailman

Alias files:
-rw-rw-rw-  1 root   mailman 12582 Oct 31 16:41 aliases
-rw-rw-rw-  1 root   mailman 24576 Oct 31 16:41 aliases.db
-rw-rw  1 apache mailman  3689 Oct 31 16:41 virtual-mailman
-rw-r-  1 root   mailman 12288 Oct 31 15:44 virtual-mailman.db

Changed the file permissions to 660 on virtual-mailman.db and posts now
working!

Thanks a million.

Scott Race
 
 

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 3:11 PM
To: Scott Race
Cc: mailman-users@python.org
Subject: RE: [Mailman-Users] Mailman on multiple domains

Scott Race wrote:

>Now just hit one more slight snag, can no longer create new lists on
the
>second-domain.org.
>
>Fails with the Bug in Mailman version 2.1.5 - We're sorry, we hit a
bug!
>Error.
>
>/var/log/mailman error shows:
>
>admin(14722): RuntimeError: command failed: /usr/sbin/postmap
>/etc/mailman/virtual-mailman (status: 1, Operation not permitted)
>
>I noticed that apache is now trying to own the virtual-mailman file in
>/etc/mailman, didn't notice that before.  Changing the ownership to
>root:mailman doesn't work, when trying to create a list it fails and
>apache takes ownership back.


The owner doesn't matter except the owner of aliases.db probably needs
to be 'mailman'. the other owners (aliases, virtual-mailman and
virtual-mailman.db don't matter.

What does matter is /etc/mailman needs to be group mailman and g+rws
and all four of aliases, aliases.db, virtual-mailman and
virtual-mailman.db need to be group mailman and g+rw.

-- 
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] Mailman on multiple domains

2008-10-31 Thread Mark Sapiro
Scott Race wrote:

>Now just hit one more slight snag, can no longer create new lists on the
>second-domain.org.
>
>Fails with the Bug in Mailman version 2.1.5 - We're sorry, we hit a bug!
>Error.
>
>/var/log/mailman error shows:
>
>admin(14722): RuntimeError: command failed: /usr/sbin/postmap
>/etc/mailman/virtual-mailman (status: 1, Operation not permitted)
>
>I noticed that apache is now trying to own the virtual-mailman file in
>/etc/mailman, didn't notice that before.  Changing the ownership to
>root:mailman doesn't work, when trying to create a list it fails and
>apache takes ownership back.


The owner doesn't matter except the owner of aliases.db probably needs
to be 'mailman'. the other owners (aliases, virtual-mailman and
virtual-mailman.db don't matter.

What does matter is /etc/mailman needs to be group mailman and g+rws
and all four of aliases, aliases.db, virtual-mailman and
virtual-mailman.db need to be group mailman and g+rw.

-- 
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] Mailman on multiple domains

2008-10-31 Thread Mark Sapiro
Scott Race wrote:

>Sorry bout that...yes, RHLE server.


It isn't a question of the OS, but rather whether Mailman was
configured and installed from our source distribution or from a RedHat
RPM which differs significantly in terms of where things are found.


>With your direction, realizing I likely needed a reference to this
>virtual-mailman file in my virtual_alias_maps, I added it, and my test
>post went through!
>
>Not sure if I need the reference to virtual-mailman in my alias_maps
>too, didn't think so, and so I didn't add it.


Correct: alias_maps references the aliases and virtual_maps references
the virtual mapping.

-- 
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] Mailman on multiple domains

2008-10-31 Thread Scott Race
Now just hit one more slight snag, can no longer create new lists on the
second-domain.org.

Fails with the Bug in Mailman version 2.1.5 - We're sorry, we hit a bug!
Error.

/var/log/mailman error shows:

admin(14722): RuntimeError: command failed: /usr/sbin/postmap
/etc/mailman/virtual-mailman (status: 1, Operation not permitted)

I noticed that apache is now trying to own the virtual-mailman file in
/etc/mailman, didn't notice that before.  Changing the ownership to
root:mailman doesn't work, when trying to create a list it fails and
apache takes ownership back.

Scott


-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 2:16 PM
To: Scott Race
Cc: mailman-users@python.org
Subject: RE: [Mailman-Users] Mailman on multiple domains

Scott Race wrote:

>Thanks for the reply - so this will be a multiple mailman domain.
>Currently list working on first-domain.org, trying to get it working on
>second-domain.org.
>
>So yes, "Host name this list prefers for email" is correct as
>second-domain.org.
>
>My mm_cfg.py looks like this:
>
>   from socket import *
>   try:
>   fqdn = getfqdn()
>   except:
>   fqdn = 'mm_cfg_has_unknown_host_domains'
>
>   DEFAULT_URL_HOST   = fqdn
>   DEFAULT_EMAIL_HOST = fqdn
>
>   # Because we've overriden the virtual hosts above
>add_virtualhost
>   # MUST be called after they have been defined.
>
>   add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>   add_virtualhost('www.first-domain.org', 'first-domain.org')
>   add_virtualhost('www.second-domain.org',
>'second-domain.org')
>
>   ##
>   # 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.
>
>   POSTFIX_STYLE_VIRTUAL_DOMAINS = ['second-domain.org']
>
>   MTA = 'Postfix'
>
>
>So, I might be getting somewhere now...so I have a virtual-mailman file
>now, it's in /etc/mailman.


I don't recall your telling us that this was a RedHat package. These
things make a difference.


  It has the following entries:
>
># LOOP ADDRESSES START
>[EMAIL PROTECTED]  mailman-loop
># LOOP ADDRESSES END
>
># STANZA START: scott-test
># CREATED: Fri Oct 31 15:44:28 2008
>[EMAIL PROTECTED]  scott-test
>[EMAIL PROTECTED]scott-test-admin
>[EMAIL PROTECTED]  scott-test-bounces
>[EMAIL PROTECTED]  scott-test-confirm
>[EMAIL PROTECTED] scott-test-join
>[EMAIL PROTECTED]scott-test-leave
>[EMAIL PROTECTED]scott-test-owner
>[EMAIL PROTECTED]  scott-test-request
>[EMAIL PROTECTED]scott-test-subscribe
>[EMAIL PROTECTED]  scott-test-unsubscribe
># STANZA END: scott-test
>
>And the virtual-mailman.db is present and current (same date and time
as
>the virtual-mailman file).


That's good.


>So, getting closer, but a test to the list still bounces:
>The following recipient(s) could not be reached:
>
>  [EMAIL PROTECTED] on 10/31/2008 1:47 PM
>There was a SMTP communication problem with the recipient's
>email server.  Please contact your system administrator.
>:
>Recipient address rejected: User unknown in virtual alias table>
>
>
>At this point I'm wondering if since I'm using a second domain, I need
>to include the first domain in the virtual domain config?  Right now it
>seems like only my second-domain is in the virtual config.


That's probably not a problem.

Does your main.cf virtual_alias_maps point to
/etc/mailman/virtual-mailman where it is or does it point somewhere
else. How about alias_maps?

-- 
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] Mailman on multiple domains

2008-10-31 Thread Scott Race
Sorry bout that...yes, RHLE server.

/etc/postfix/main.cf has the following (in reference to the questions
below):


virtual_alias_maps = hash:/etc/postfix/virtual_alias_maps
virtual_alias_domains = hash:/etc/postfix/mydomains
alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases


With your direction, realizing I likely needed a reference to this
virtual-mailman file in my virtual_alias_maps, I added it, and my test
post went through!

Not sure if I need the reference to virtual-mailman in my alias_maps
too, didn't think so, and so I didn't add it.

Thanks a TON for the help!


Scott Race 
 

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 2:16 PM
To: Scott Race
Cc: mailman-users@python.org
Subject: RE: [Mailman-Users] Mailman on multiple domains

Scott Race wrote:

>Thanks for the reply - so this will be a multiple mailman domain.
>Currently list working on first-domain.org, trying to get it working on
>second-domain.org.
>
>So yes, "Host name this list prefers for email" is correct as
>second-domain.org.
>
>My mm_cfg.py looks like this:
>
>   from socket import *
>   try:
>   fqdn = getfqdn()
>   except:
>   fqdn = 'mm_cfg_has_unknown_host_domains'
>
>   DEFAULT_URL_HOST   = fqdn
>   DEFAULT_EMAIL_HOST = fqdn
>
>   # Because we've overriden the virtual hosts above
>add_virtualhost
>   # MUST be called after they have been defined.
>
>   add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>   add_virtualhost('www.first-domain.org', 'first-domain.org')
>   add_virtualhost('www.second-domain.org',
>'second-domain.org')
>
>   ##
>   # 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.
>
>   POSTFIX_STYLE_VIRTUAL_DOMAINS = ['second-domain.org']
>
>   MTA = 'Postfix'
>
>
>So, I might be getting somewhere now...so I have a virtual-mailman file
>now, it's in /etc/mailman.


I don't recall your telling us that this was a RedHat package. These
things make a difference.


  It has the following entries:
>
># LOOP ADDRESSES START
>[EMAIL PROTECTED]  mailman-loop
># LOOP ADDRESSES END
>
># STANZA START: scott-test
># CREATED: Fri Oct 31 15:44:28 2008
>[EMAIL PROTECTED]  scott-test
>[EMAIL PROTECTED]scott-test-admin
>[EMAIL PROTECTED]  scott-test-bounces
>[EMAIL PROTECTED]  scott-test-confirm
>[EMAIL PROTECTED] scott-test-join
>[EMAIL PROTECTED]scott-test-leave
>[EMAIL PROTECTED]scott-test-owner
>[EMAIL PROTECTED]  scott-test-request
>[EMAIL PROTECTED]scott-test-subscribe
>[EMAIL PROTECTED]  scott-test-unsubscribe
># STANZA END: scott-test
>
>And the virtual-mailman.db is present and current (same date and time
as
>the virtual-mailman file).


That's good.


>So, getting closer, but a test to the list still bounces:
>The following recipient(s) could not be reached:
>
>  [EMAIL PROTECTED] on 10/31/2008 1:47 PM
>There was a SMTP communication problem with the recipient's
>email server.  Please contact your system administrator.
>:
>Recipient address rejected: User unknown in virtual alias table>
>
>
>At this point I'm wondering if since I'm using a second domain, I need
>to include the first domain in the virtual domain config?  Right now it
>seems like only my second-domain is in the virtual config.


That's probably not a problem.

Does your main.cf virtual_alias_maps point to
/etc/mailman/virtual-mailman where it is or does it point somewhere
else. How about alias_maps?

-- 
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] Mailman on multiple domains

2008-10-31 Thread Mark Sapiro
Scott Race wrote:

>Thanks for the reply - so this will be a multiple mailman domain.
>Currently list working on first-domain.org, trying to get it working on
>second-domain.org.
>
>So yes, "Host name this list prefers for email" is correct as
>second-domain.org.
>
>My mm_cfg.py looks like this:
>
>   from socket import *
>   try:
>   fqdn = getfqdn()
>   except:
>   fqdn = 'mm_cfg_has_unknown_host_domains'
>
>   DEFAULT_URL_HOST   = fqdn
>   DEFAULT_EMAIL_HOST = fqdn
>
>   # Because we've overriden the virtual hosts above
>add_virtualhost
>   # MUST be called after they have been defined.
>
>   add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>   add_virtualhost('www.first-domain.org', 'first-domain.org')
>   add_virtualhost('www.second-domain.org',
>'second-domain.org')
>
>   ##
>   # 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.
>
>   POSTFIX_STYLE_VIRTUAL_DOMAINS = ['second-domain.org']
>
>   MTA = 'Postfix'
>
>
>So, I might be getting somewhere now...so I have a virtual-mailman file
>now, it's in /etc/mailman.


I don't recall your telling us that this was a RedHat package. These
things make a difference.


  It has the following entries:
>
># LOOP ADDRESSES START
>[EMAIL PROTECTED]  mailman-loop
># LOOP ADDRESSES END
>
># STANZA START: scott-test
># CREATED: Fri Oct 31 15:44:28 2008
>[EMAIL PROTECTED]  scott-test
>[EMAIL PROTECTED]scott-test-admin
>[EMAIL PROTECTED]  scott-test-bounces
>[EMAIL PROTECTED]  scott-test-confirm
>[EMAIL PROTECTED] scott-test-join
>[EMAIL PROTECTED]scott-test-leave
>[EMAIL PROTECTED]scott-test-owner
>[EMAIL PROTECTED]  scott-test-request
>[EMAIL PROTECTED]scott-test-subscribe
>[EMAIL PROTECTED]  scott-test-unsubscribe
># STANZA END: scott-test
>
>And the virtual-mailman.db is present and current (same date and time as
>the virtual-mailman file).


That's good.


>So, getting closer, but a test to the list still bounces:
>The following recipient(s) could not be reached:
>
>  [EMAIL PROTECTED] on 10/31/2008 1:47 PM
>There was a SMTP communication problem with the recipient's
>email server.  Please contact your system administrator.
>:
>Recipient address rejected: User unknown in virtual alias table>
>
>
>At this point I'm wondering if since I'm using a second domain, I need
>to include the first domain in the virtual domain config?  Right now it
>seems like only my second-domain is in the virtual config.


That's probably not a problem.

Does your main.cf virtual_alias_maps point to
/etc/mailman/virtual-mailman where it is or does it point somewhere
else. How about alias_maps?

-- 
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] Mailman on multiple domains

2008-10-31 Thread Scott Race
Thanks for the reply - so this will be a multiple mailman domain.
Currently list working on first-domain.org, trying to get it working on
second-domain.org.

So yes, "Host name this list prefers for email" is correct as
second-domain.org.

My mm_cfg.py looks like this:

from socket import *
try:
fqdn = getfqdn()
except:
fqdn = 'mm_cfg_has_unknown_host_domains'

DEFAULT_URL_HOST   = fqdn
DEFAULT_EMAIL_HOST = fqdn

# Because we've overriden the virtual hosts above
add_virtualhost
# MUST be called after they have been defined.

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('www.first-domain.org', 'first-domain.org')
add_virtualhost('www.second-domain.org',
'second-domain.org')

##
# 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.

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['second-domain.org']

MTA = 'Postfix'


So, I might be getting somewhere now...so I have a virtual-mailman file
now, it's in /etc/mailman.  It has the following entries:

# LOOP ADDRESSES START
[EMAIL PROTECTED]  mailman-loop
# LOOP ADDRESSES END

# STANZA START: scott-test
# CREATED: Fri Oct 31 15:44:28 2008
[EMAIL PROTECTED]  scott-test
[EMAIL PROTECTED]scott-test-admin
[EMAIL PROTECTED]  scott-test-bounces
[EMAIL PROTECTED]  scott-test-confirm
[EMAIL PROTECTED] scott-test-join
[EMAIL PROTECTED]scott-test-leave
[EMAIL PROTECTED]scott-test-owner
[EMAIL PROTECTED]  scott-test-request
[EMAIL PROTECTED]scott-test-subscribe
[EMAIL PROTECTED]  scott-test-unsubscribe
# STANZA END: scott-test

And the virtual-mailman.db is present and current (same date and time as
the virtual-mailman file).

So, getting closer, but a test to the list still bounces: 
The following recipient(s) could not be reached:

  [EMAIL PROTECTED] on 10/31/2008 1:47 PM
There was a SMTP communication problem with the recipient's
email server.  Please contact your system administrator.
:
Recipient address rejected: User unknown in virtual alias table>


At this point I'm wondering if since I'm using a second domain, I need
to include the first domain in the virtual domain config?  Right now it
seems like only my second-domain is in the virtual config.


Scott

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 1:13 PM
To: Scott Race
Cc: mailman-users@python.org
Subject: RE: [Mailman-Users] Mailman on multiple domains

Scott Race wrote:
>
>Thanks, fixed the domain name in the mm_cfg.py to read
['second-domain.com'].
>
>Running the /bin/genaliases doesn't return an error, but doesn't
>generate the /data/virtual-mailman file.  The mailman error logs don't
>show anything (no errors since Oct 22).
>
>Sounds like the virtual-mailman file missing is my main problem, huh?


Yes.

Go to the list's General Options page and look near the bottom at "Host
name this list prefers for email.". Does this match second-domain.com?

What you ultimately need to do to configure all this depends on whether
or not you will have multiple Mailman domains or a single Mailman
domain.

If there is only a single mailman domain = second-domain.com you want
something like

DEFAULT_URL_HOST = 'www.second-domain.com'
DEFAULT_EMAIL_HOST = 'second-domain.com'
add_virtual_hosts(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

in mm_cfg.py

and then run

bin/withlist -l -a -r fix_url

to fix the web_page_url and host_name attributes of all the lists.

If you have more Mailman domains, it's more complex, but until you have
the proper host_name for your lists, genaliases won't create/update
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://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] Mailman on multiple domains

2008-10-31 Thread Mark Sapiro
Scott Race wrote:
>
>Thanks, fixed the domain name in the mm_cfg.py to read ['second-domain.com'].
>
>Running the /bin/genaliases doesn't return an error, but doesn't
>generate the /data/virtual-mailman file.  The mailman error logs don't
>show anything (no errors since Oct 22).
>
>Sounds like the virtual-mailman file missing is my main problem, huh?


Yes.

Go to the list's General Options page and look near the bottom at "Host
name this list prefers for email.". Does this match second-domain.com?

What you ultimately need to do to configure all this depends on whether
or not you will have multiple Mailman domains or a single Mailman
domain.

If there is only a single mailman domain = second-domain.com you want
something like

DEFAULT_URL_HOST = 'www.second-domain.com'
DEFAULT_EMAIL_HOST = 'second-domain.com'
add_virtual_hosts(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

in mm_cfg.py

and then run

bin/withlist -l -a -r fix_url

to fix the web_page_url and host_name attributes of all the lists.

If you have more Mailman domains, it's more complex, but until you have
the proper host_name for your lists, genaliases won't create/update
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://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] Mailman on multiple domains

2008-10-31 Thread Scott Race
Thanks, fixed the domain name in the mm_cfg.py to read ['second-domain.com'].

Running the /bin/genaliases doesn't return an error, but doesn't generate the 
/data/virtual-mailman file.  The mailman error logs don't show anything (no 
errors since Oct 22).
 
Sounds like the virtual-mailman file missing is my main problem, huh?
 
Scott



From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Fri 10/31/2008 12:02 PM
To: Scott Race; mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman on multiple domains



Scott Race wrote:

>So I didn't have the entry for POSTFIX_STYLE_VIRTUAL_DOMAINS in my
>mm_cfg.py file.
>
>So I added the following:
>
>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['www.second-domain.com']


This domain has to match the host_name attribute of the list (the
'email host', not the 'url host'). It seems likely it should be
'second-domain.com', not 'www.second-domain.com'.


>Ran /bin/genaliases, no errors


But did it produce a data/virtual-mailman file?


>Mail still bounces with the following:
>
>Your message did not reach some or all of the intended recipients.
>
>  Subject: Test to list
>  Sent:10/30/2008 4:16 PM
>
>The following recipient(s) could not be reached:
>
>  [EMAIL PROTECTED] on 10/30/2008 4:16 PM
>There was a SMTP communication problem with the recipient's
>email server.  Please contact your system administrator.
>:
>Recipient address rejected: User unknown in virtual alias table
>
>
>Guess I still don't know how the virtual alias table gets updated when a
>list is createdthanks in advance for any thoughts.


If the list's host_name is in POSTFIX_STYLE_VIRTUAL_DOMAINS, the
appropriate virtual mappings are added to data/virtual-mailman and
POSTFIX_MAP_CMD (default '/usr/sbin/postmap') is run to update
data/virtual-mailman.db.

--
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] Mailman on multiple domains

2008-10-31 Thread Mark Sapiro
Scott Race wrote:

>So I didn't have the entry for POSTFIX_STYLE_VIRTUAL_DOMAINS in my
>mm_cfg.py file.
>
>So I added the following:
>
>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['www.second-domain.com']


This domain has to match the host_name attribute of the list (the
'email host', not the 'url host'). It seems likely it should be
'second-domain.com', not 'www.second-domain.com'.


>Ran /bin/genaliases, no errors


But did it produce a data/virtual-mailman file?


>Mail still bounces with the following:
>
>Your message did not reach some or all of the intended recipients.
>
>  Subject: Test to list
>  Sent:10/30/2008 4:16 PM
>
>The following recipient(s) could not be reached:
>
>  [EMAIL PROTECTED] on 10/30/2008 4:16 PM
>There was a SMTP communication problem with the recipient's
>email server.  Please contact your system administrator.
>:
>Recipient address rejected: User unknown in virtual alias table
>
>
>Guess I still don't know how the virtual alias table gets updated when a
>list is createdthanks in advance for any thoughts.


If the list's host_name is in POSTFIX_STYLE_VIRTUAL_DOMAINS, the
appropriate virtual mappings are added to data/virtual-mailman and
POSTFIX_MAP_CMD (default '/usr/sbin/postmap') is run to update
data/virtual-mailman.db.

-- 
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] Mailman receives posts but no sent them

2008-10-31 Thread Mark Sapiro
Brad Knowles wrote:

>NetBiker wrote:
>
>> I've the following errors when a subscribed user sent a post to the list:
>> 
>> logs/smtp
>> Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
>> associated with nodename')
>> Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
>> associated with nodename')
>> Oct 30 16:52:39 2008 (378)
>> <[EMAIL PROTECTED]> smtp for 3
>> recips, completed in 0.059 seconds
>
>Sounds like a problem with your hostname, but you should search the FAQ Wiki 
>for "troubleshooting".


This is an OS error having to do with DNS lookup of a host name by
Postfix during SMTP from mailman. My best guess is your host name in
the SMTP MAIL FROM command is not resolvable in DNS. This is normally
the host_name of the list(s) set from DEFAULT_EMAIL_HOST at list
creation.

-- 
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] Processing missed digests...

2008-10-31 Thread Mark Sapiro
John Gray wrote:
>
>But the mailman cron jobs didn't run for about a week.
>
>Is there a way for get senddigets to send out the digests for the 
>missing days?
>
>Or did senddigest send everything since the last digest?


There should be no missing digests. Assuming no digest was triggered on
'size' when cron/senddigests ran, it sent a digest containing all the
messages accumulated since the previous digest.

I.e., there were missing days, but no missing digest issue numbers and
no missing messages.

-- 
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] message delivery eating disk space ..

2008-10-31 Thread Mark Sapiro
faisal anif wrote:
> 
>is there a kind of temporary files that mailman doesn't cleanup? what can I do?


No. The only files are the queue files which hold the message as it is
processed and the archives. The queue files are removed when message
processing is complete.

As Brad says, you need to actually check to see which directory
hierarchy was using up the disk space?

-- 
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] Mailman receives posts but no sent them

2008-10-31 Thread Brad Knowles

NetBiker wrote:


I've enabled mailing lists with Mailman 2.1.2 and Postfix in a Mac OS
X Server 10.3.9


Search the FAQ Wiki for "mac os x".


I've the following errors when a subscribed user sent a post to the list:

logs/smtp
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:52:39 2008 (378)
<[EMAIL PROTECTED]> smtp for 3
recips, completed in 0.059 seconds


Sounds like a problem with your hostname, but you should search the FAQ Wiki 
for "troubleshooting".



Mailman FAQ: http://wiki.list.org/x/AgA3


Note that this line is included at the bottom of every single message that 
passes through this mailing list.  This FAQ Wiki is searchable.


--
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: 
--
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] Mailman on multiple domains

2008-10-31 Thread Scott Race
So I didn't have the entry for POSTFIX_STYLE_VIRTUAL_DOMAINS in my
mm_cfg.py file.

So I added the following:

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['www.second-domain.com']

Ran /bin/genaliases, no errors

Mail still bounces with the following:

Your message did not reach some or all of the intended recipients.

  Subject:  Test to list
  Sent: 10/30/2008 4:16 PM

The following recipient(s) could not be reached:

  [EMAIL PROTECTED] on 10/30/2008 4:16 PM
There was a SMTP communication problem with the recipient's
email server.  Please contact your system administrator.
:
Recipient address rejected: User unknown in virtual alias table


Guess I still don't know how the virtual alias table gets updated when a
list is createdthanks in advance for any thoughts.

Scott






-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Mark Sapiro
Sent: Wednesday, October 29, 2008 4:36 PM
To: Scott Race; mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman on multiple domains

Scott Racewrote:

>As a follow-up, I don't seem to have the virtual-mailman file on my
>server anywhere as stated in the documentation


Is the virtual domain in

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['the.virtual.domain']

in mm_cfg.py.

Is the host_name of the list = the.virtual.domain

Have you run Mailman's bin/genaliases since setting

MTA= 'Postfix'

and

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['the.virtual.domain']

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://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/webaccount%40jdaarc
h.com

Security Policy: http://wiki.list.org/x/QIA9
--
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] Mailman receives posts but no sent them

2008-10-31 Thread NetBiker
Hello,

I've enabled mailing lists with Mailman 2.1.2 and Postfix in a Mac OS
X Server 10.3.9

I've the following errors when a subscribed user sent a post to the list:

logs/smtp
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:52:39 2008 (378)
<[EMAIL PROTECTED]> smtp for 3
recips, completed in 0.059 seconds

logs/logs
Oct 30 16:52:39 2008 (378) post to prueba from [EMAIL PROTECTED],
size=2374, message-id=<[EMAIL PROTECTED]>,
3 failures

the list prueba has three subscribers

the same problem occurs with other messages in the list

logs/smtp
Oct 30 16:38:38 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:38:38 2008 (378) <[EMAIL PROTECTED]>
smtp for 1 recips, completed in 0.033 seconds

logs/post

Oct 30 16:38:38 2008 (378) post to prueba from
[EMAIL PROTECTED], size=605,
message-id=<[EMAIL PROTECTED]>, 1 failures

No messages or posts were sent since the list was created but in the
list archives we can see all the posts

Postfix is working fine with messages for the dom.ain domain in the
same Mac OS X server

we only added in the mm_cfg.py file:

DEFAULT_EMAIL_HOST = 'dom.ain'
DEFAULT_URL_HOST = 'lists.dom.ain'

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)


thank you very much
--
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] deletion reason in email template

2008-10-31 Thread Mark Sapiro
Fil wrote:
>
>is there a possibility to add, in the email template sent to the list
>owner when someone is deleted, the REASON (BYBOUNCE etc) ?


This is a good suggestion. I'll add it in 2.2 to include the 'whence'
argument to ApprovedDeleteMember() which is a phrase like 'email
confirmation', 'web confirmation', 'disabled address', etc.

-- 
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] Seeking qfiles/shunt recovery advice.

2008-10-31 Thread Mark Sapiro
TGPlatt, WebMaster wrote:
>
>My trouble here was I could find no docs about shunt to guide me and never
>realized unshunt existed until I saw your note. I went for help to the only
>place I knew of where mailman's command line utilities were listed:
>www.gnu.org/software/mailman/site.html Shunt isn't even mentioned there.
>Next, I checked the Installation Docs again. No mention of the command line
>utilities there at all. Then I tried going to "man shunt" and struck out
>there as well. 


You're right about the web page being incomplete. I'll try to update
it. There is a FAQ at  that has a more
complete list.


>You know, Mark, the trouble with the knowledge base surrounding mailman is
>there's an excess of knowledge but not enough "base" in any one spot to
>enable one to find the 'firmly grounded' answers one needs. It's way too
>'swampy' in many places.


The FAQ section of the wiki  is intended
to address this. If you find it lacking, you can help by updating 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://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] deletion reason in email template

2008-10-31 Thread Fil
Hello,

is there a possibility to add, in the email template sent to the list
owner when someone is deleted, the REASON (BYBOUNCE etc) ?

-- 
Fil
--
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] What happened to my archive? Why isn't the archive process running?

2008-10-31 Thread TGPlatt, WebMaster
Thanks, Mark. That's all I needed to know! 

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 12:59 AM
To: [EMAIL PROTECTED]; mailman-users@python.org
Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the
archive process running?

TGPlatt, WebMaster wrote:

>I've probably just misunderstood something here... blah... blah... blah...
>...when I asked about ownership and permissions and mentioned "the
>UserAccount/mailman directory", that's the directory I was referring to.
>Sorry if I confused you. :-(
>
>Should I just remove that "spare" mailman directory from the user's space
>now?

The only thing there is the mailman/mail/mailman wrapper whose sole
purpose is to be SETGID mailman so that mail delivery runs in the
mailman group. Since this wrapper isn't SETGID or group mailman, it
wouldn't work in this installation anyway, so yes, just remove this
directory.

-- 
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] Seeking qfiles/shunt recovery advice.

2008-10-31 Thread TGPlatt, WebMaster
As usual, you're right, Mark. That fixed it. As a result, I was able to
recover at least some of the archived messages from September and many of
the October messages that occurred during the "resurrection" and testing
period too. 

My trouble here was I could find no docs about shunt to guide me and never
realized unshunt existed until I saw your note. I went for help to the only
place I knew of where mailman's command line utilities were listed:
www.gnu.org/software/mailman/site.html Shunt isn't even mentioned there.
Next, I checked the Installation Docs again. No mention of the command line
utilities there at all. Then I tried going to "man shunt" and struck out
there as well. 

You know, Mark, the trouble with the knowledge base surrounding mailman is
there's an excess of knowledge but not enough "base" in any one spot to
enable one to find the 'firmly grounded' answers one needs. It's way too
'swampy' in many places. In fact, it reminds me of the way my father-in-law
(a lifelong soil scientist) used to describe the Rio Grande... Too thick to
drink and too thin to plow! ;-)

Without your patient and expert guidance, mailman would be nearly impossible
to install and use. Thanks again for your patience and help!


-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 31, 2008 1:04 AM
To: [EMAIL PROTECTED]; mailman-users@python.org
Subject: Re: [Mailman-Users] Seeking qfiles/shunt recovery advice.

TGPlatt, WebMaster wrote:

>Now that my archiver is working again, I have several files in qfiles/shunt
>that I'd like to recover and convince mailman to insert into my (now
>working) October archive. If it's possible to do so, I also have a few
>shunted files from the end of September that I'd like to recover and have
>included in the September archive as well.
>
>Can anyone point me to a post that explains how to retrieve and
>recover pck files from the qfiles/shunt directory and convince ARCHrunner
to try processing them again?

Run Mailman's bin/unshunt --help

In this case all you should need to do is put the old *.pck files from
the old shunt directory into the current shunt directory along with
the current shunted *.pck files and run 'bin/unshunt'.

-- 
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] Seeking qfiles/shunt recovery advice.

2008-10-31 Thread Mark Sapiro
TGPlatt, WebMaster wrote:

>Now that my archiver is working again, I have several files in qfiles/shunt
>that I'd like to recover and convince mailman to insert into my (now
>working) October archive. If it's possible to do so, I also have a few
>shunted files from the end of September that I'd like to recover and have
>included in the September archive as well.
>
> 
>
>Under the circumstances, I'd rather not attack this using a trial and error
>process. Can anyone point me to a post that explains how to retrieve and
>recover pck files from the qfiles/shunt directory and convince ARCHrunner to
>try processing them again?


Run Mailman's bin/unshunt --help

In this case all you should need to do is put the old *.pck files from
the old shunt directory into the current shunt directory along with
the current shunted *.pck files and run 'bin/unshunt'.

-- 
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