Re: [Mailman-Users] setting up a mailing list

2005-10-13 Thread Cogley, Rick
This is what I use, assuming memberlist is a list of members - 

#/usr/lib/mailman/binadd_members -r /path/to/memberlist -w n -a n listname

Best Regards,
Rick

--
Rick Cogley (mailto:[EMAIL PROTECTED])

Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475
(Outside Japan, remove leading zero -- +81-3-5940-6880)
English: http://www.esolia.com || Japanese: http://www.esolia.co.jp

Bilingual IT solutions and management firm -- eSolia.
--



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of vandenberg
Sent: Thursday, October 13, 2005 5:22 PM
To: mailman-users@python.org
Subject: [Mailman-Users] setting up a mailing list

How can I insert a large number of mailadresses into a mailing list?

 

met vriendelijke groet,

 

Thomas van den Berg

Herautstraat 61

8043AE Zwolle

tel 038-4605620

 

--
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/rick.cogley%40esolia.co
.jp

Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
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] unknown user

2005-09-07 Thread Cogley, Rick
I'm a beginner with Mailman, so I could be wrong, but I was getting this
sort of error until I confirmed my aliases were being created correctly. 
I changed MTAs to Postfix and followed the directions in the Mailman manual
or readme, to make the aliases autocreate when you create a list via the
web. 

Hope this serves as a hint.

Regards,
Rick Cogley
Tokyo, Japan

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Hugo Osorio
Sent: Thursday, September 08, 2005 7:57 AM
To: mailman-users@python.org
Subject: [Mailman-Users] unknown user

Hello community
 could you help me with this, i have created a list in mailman web
interface, but i send a message to the list, and is not delivered, it is
returning to me unknown user
what is the step after being created the list? thank you very much.
--
--
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] Rewriting Headers in 2.1.5

2005-07-25 Thread Cogley, Rick
Mark - thanks very much for your response and advice.

Make the another-list list anonymous. Then the From: address in the
message it sends back to the tracking system will be the address of the list
which can be a registered user in the tracking system. The original
submitter is still available in the From: header of the attached message.

Alternatively, if you can make the tracking system validate on envelope
sender, you only need to register [EMAIL PROTECTED] as a
user in the tracking system. Note that if you can do this, you might also be
able to have the rejected-as-unknown mail go directly back to the tracking
system depending on what the envelope sender of the rejected-as-unknown mail
is. 

It's now working, and here is what I did to get this working with
TrackStudio (the tracking system I use)- 

* created a single list [prereg] with a single member
[EMAIL PROTECTED], and set the list to anonymous
* set the tracking system reject mail address to [EMAIL PROTECTED]
* created a user in the tracking system with email address
[EMAIL PROTECTED], and granted it post permissions on a particular
folder - folder PREREG
* associated an email import rule on the PREREG folder - import mail with
subject that contains [prereg] 

Now when a mail comes in to [EMAIL PROTECTED], it is sent to the
tracking system, which looks at it to see if it can be processed. If it
cannot, the system rejects it sending it to the mailman list. The mainman
list reformats the subject line and From: address, making it look like the
mail is coming in from the list itself, and, resends to
[EMAIL PROTECTED] When the tracking system receives the second time,
it now recognizes the From address as being from a known user, and sees that
the mail's subject matches a string in one of the import rules, and thereby
imports to the correct folder. 

Now I have another potential problem that I would like to bounce off the
list. If an unknown user sends an email in, and includes no information in
the body of the text such as an informative signature or other text
indicating who they are, since the From: gets overwritten, we have a
potential situation where we cannot tell who sent the mail in. 

The tracking system is not an email client per se, and does not allow you to
view headers. Therefore I would like to grab the initial From: address (say,
[EMAIL PROTECTED]) and put it on the subject line, or, in the body. How can
I accomplish that with Mailman? Google and RTF FAQ etc have given some info
about VERP, but I would like to get some advice before embarking on a wild
goose chase. Also, for some reason the tracking system does not do very well
with importing footers, where I know you can place personalized info. Can I
add the original From: to the bottom of the body? 

Can someone kindly point me in the right direction? TIA!!

Best Regards,
Rick Cogley
Tokyo, Japan
--
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] Rewriting Headers in 2.1.5

2005-07-24 Thread Cogley, Rick
Hello everyone - 

I'm hoping someone more experienced than I can assist me. After a couple of
weeks working with the system I now understand the basic workings of Mailman
2.1.5 (loaded on Fedora Core 4 via RPM), but am hitting a wall with nested
or umbrella lists, and I suppose some specific settings. 

I am using Mailman to feed mails into an issue tracking system, which can
sort into its folders based on the subject. If my tracking system receives a
message from Mailman with a [somelist] tag, it will find the folder that is
set up with an import rule to recognize the string [somelist] and import.
There's a catch: this is only for registered users, as an anti-spam measure.
When the tracking system cannot import, it can be set to reject incoming
mail messages by forwarding them to another email address. 

I have created a user in the tracking system to act as a proxy user, or a
dummy user, for emails that come in from unknown / unregistered users. I
would like to have Mailman receive the reject mails, and then reroute back
into the tracking system making it look like the mail came from the proxy
user - a known user in the tracking system. Then, support people using the
tracking system can look at the mails in the unknowns folder, act on them,
and create tracking system accounts or whatever else is needed. I'll handle
incoming spam at the mail server level.

From what I read, it seems like this should be possible with umbrella lists
or some settings in Mailman, but I keep getting loops between the tracking
system and Mailman. 

Here is a specific scenario along with the mail headers of the rejected
mail sent by the tracking system: 

* John Doe [EMAIL PROTECTED] sends an email address to
[EMAIL PROTECTED] which is the address my group has provided
Acme to use for sending support requests to. 

* [EMAIL PROTECTED] is the alias in my Mailman system which maps
to the [acme-support] Mailman list. 

* The tracking system's address [EMAIL PROTECTED] is a member of the
[acme-support] list.

* Mails come in from [EMAIL PROTECTED], via [acme-support],
which distributes to [EMAIL PROTECTED] The tracking system tries to
process the mail, finds no user matching [EMAIL PROTECTED]
and so sends it to the email address I set as the reject email address -
[EMAIL PROTECTED] 

* Currently, acct-not-found@ is a normal email box, and here is a test mail
message from the unknown user, and its headers: 

=8==
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Date: Mon, 25 Jul 2005 05:37:18 +0900 (JST)
From: John Doe [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: Forwarded from  [EMAIL PROTECTED]: [acme-support] Test
from
 account unregistered in Tracking System
X-Priority: 1
precedence: bulk
X-TrackStudio: forwarded mail

[-- Attachment #1 --]
[-- Type: message/rfc822, Encoding: 7bit, Size: 2.2K --]

X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; d=acme.com; ... etc
Date: Mon, 25 Jul 2005 05:36:17 +0900
From: John Doe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [acme-support] Test from account unregistered in Tracking System
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Doe [EMAIL PROTECTED]
List-Id: acme-support acme-support.domainofmine.net
List-Unsubscribe:
http://www.domainofmine.net/mailman/listinfo/acme-support,
mailto:[EMAIL PROTECTED]
List-Post: mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://www.domainofmine.net/mailman/listinfo/acme-support,
mailto:[EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]

Test from account unregistered in Tracking System

===8

My questions are, is this even the right approach, and, will it work given
the header above which is what comes out of the tracking system? Can I go:

unknownuser - support Mailman list - tracking system email -
rejected-as-unknown - tracking system email
Or, for instance:
unknownuser - support Mailman list - tracking system email -
rejected-as-unknown - another-list -tracking system email

... and rewrite the headers somehow after the rejected as unknown step? If
so, could someone please direct me as to what I should be doing? 

Thanks very much for your kind consideration on this problem, and any advice
provided!

Sincerely,
Rick Cogley
Tokyo, Japan


--
Rick Cogley ([EMAIL PROTECTED])

Tel: 03-5940-6880 | Fax: 03-5940-6881 | Cell: 090-4423-5475
(Outside Japan, remove leading zero-+81-3-5940-6880)
English: www.esolia.com http://www.esolia.com/  | Japanese:
www.esolia.co.jp http://www.esolia.co.jp/ 

Bilingual IT solutions and management firm-eSolia.
--

--
Mailman-Users mailing list
Mailman-Users@python.org

[Mailman-Users] (no subject)

2005-07-22 Thread Cogley, Rick

--
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] Footer Personalization

2005-07-22 Thread Cogley, Rick
Hi All -

In the Mailman FAQ it mentions being able to personalize the footers if some
settings for VERP are made in mm_cfg.py, but does not go into much detail
about how to do the required changes. 

--
Q. Can I put the user's address in the footer that Mailman adds to each
message? 
A. Yes, in Mailman 2.1. The site admin needs to enable personalization by
setting the following variables in the mm_cfg.py file: 

VERP_PASSWORD_REMINDERS = 1 VERP_PERSONALIZED_DELIVERIES = 1
VERP_DELIVERY_INTERVAL = 1 VERP_CONFIRMATIONS = 1 

Once this is done, list admins can enable personalization for regular
delivery members (digest deliveries can't be personalized currently). A
personalized list can include the user's address in the footer. 
--

I would like to add the original sender's email address to the footer
section, copying that section from Defaults.py to mm_cfg.py, and then adding
some string (conceptually). What string do I need to add to get the sender?

Any advice warmly welcomed!

Thanks
Rick Cogley
Tokyo, Japan 
--
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] Mailman 2.1.5 - FQDN Question

2005-07-21 Thread Cogley, Rick
I dug around some more and was able to find out how to fix the symptoms. If
I run fix_url on the lists, they appear in the web interface. 

/path/to/withlist -l -r fix_url xyz-sales -u www.domainofmine.net -v

However, can anyone tell me why lists created in the web interface default
to www.domainofmine.net but lists created from the command line default to
localhost.localdomain? Of course, I can just run fix_url after every list
creation in the shell script, but, is there a template somewhere that I
can use to set it to use www.domainofmine.net for all lists? 

Hope someone can assist! Thanks in advance! 


Best Regards,
Rick

--
Rick Cogley (mailto:[EMAIL PROTECTED])

Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475
(Outside Japan, remove leading zero -- +81-3-5940-6880)
English: http://www.esolia.com || Japanese: http://www.esolia.co.jp

Bilingual IT solutions and management firm -- eSolia.
--



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Cogley, Rick
Sent: Thursday, July 21, 2005 1:55 PM
To: 'mailman-users@python.org'
Subject: Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

Apologies - it formatted wrong again, stringing the most relevant line
together making it looked remarked out. Once more, it is probably obvious to
you, this is the relevant line in the config: 

add_virtualhost('www.domainofmine.net', 'domainofmine.net') 

This is what works, as opposed to using the DEFAULT_URL_HOST etc above it. 

Thanks
Rick




-Original Message-
From: Cogley, Rick
Sent: Thursday, July 21, 2005 12:55 PM
To: 'mailman-users@python.org'
Cc: Cogley, Rick
Subject: Mailman 2.1.5 - FQDN Question

Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:

After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #: 

=8=
...
# DEFAULT_URL_HOST   = fqdn
# DEFAULT_EMAIL_HOST = fqdn

# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST   = domainofmine.net

# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST   = rcogley.user.myisp.com

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

# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net') ...
8=

I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.

Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]


8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists. 
...
echo mm-multi.sh - \$Revision: 0.1 $

# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
  echo
  echo Enter a short name for the client, no spaces, lowercase:
  read CSHORTNAME
  echo
  echo == SCRIPT PRESETS ==
  echo Location of Mailman scripts: $MMBIN
  echo Location of Mailman aliases: $MMALIASES
  echo List language: $MMLISTLANG
  echo List Owner Email: $MMOWNEREMAIL
  echo List Admin Password: $MMADMINPASS
  echo
  echo == USER ==
  echo Client Short Name: $CSHORTNAME
  echo
  echo Is this correct? (y/n)
  read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass
/path/to/genaliases /path/to/add_members -r memberlistfile -w n -a y
$CSHORTNAME-sales echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED

Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

2005-07-21 Thread Cogley, Rick
Thanks, Jim. I will start there to look.   



Best Regards,
Rick

--
Rick Cogley (mailto:[EMAIL PROTECTED])

Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475
(Outside Japan, remove leading zero -- +81-3-5940-6880)
English: http://www.esolia.com || Japanese: http://www.esolia.co.jp

Bilingual IT solutions and management firm -- eSolia.
--



-Original Message-
From: Jim Tittsler [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 21, 2005 9:02 PM
To: Cogley, Rick
Cc: 'mailman-users@python.org'
Subject: Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question


On Jul 21, 2005, at 15:38, Cogley, Rick wrote:
 # NOTE: bug with quotes
 # add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') 
 add_virtualhost('www.domainofmine.net', 'domainofmine.net')

Note that DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST are variable names not
strings, and so should not have been quoted:

DEFAULT_URL_HOST = 'www.example.com'
DEFAULT_EMAIL_HOST = 'example.com'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

 I dug around some more and was able to find out how to fix the 
 symptoms. If I run fix_url on the lists, they appear in the web 
 interface.

Any time you do something that changes the URL, you need to use fix_url to
update existing lists.

 However, can anyone tell me why lists created in the web interface 
 default to www.domainofmine.net but lists created from the command 
 line default to localhost.localdomain? Of course, I can just run 
 fix_url after every list creation in the shell script, but, is there a 
 template somewhere that I can use to set it to use 
 www.domainofmine.net for all lists?

I would guess that there is a value being added to the VIRTUAL_HOSTS  
dictionary in your Defaults.py that has the wrong DEFAULT_URL_HOST.   
'clear'ing it in your mm_cfg.py allows you to be explict about the entries.

-- 
Jim Tittsler http://www.OnJapan.net/  GPG: 0x01159DB6
Python Starship  http://Starship.Python.net/
Ringo MUG Tokyo  http://www.ringo.net/rss.html

--
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] Mailman 2.1.5 - FQDN Question

2005-07-21 Thread Cogley, Rick
Hi everyone - 

I was experimenting around with for in do, and there is a much cleaner way
to write this shell script. Try it short at first to get the concept: 

=
#!/bin/sh
for i in support 911 memo sales
Do
echo $i
Done 
=

This scriptlet will just echo four lines: 

support
911
memo
sales

That implied to me that if I can grab the four variable strings I wanted to
prepend the short company name to, I could do all the operations on them,
each loop:  


8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists. 
...
echo mm-multi.sh - \$Revision: 0.1 $

# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
  echo
  echo Enter a short name for the client, no spaces, lowercase:
  read CSN
...
  echo
  echo Is this correct? (y/n)
  read x
done

# Loop over strings after in

for i in support 911 memo sales
do 
echo = $CSN-$i =
echo
echo Creating list: $CSN-$i
$MMBIN/newlist -l $MMLISTLANG -q $CSN-$i $MMOWNEREMAIL $MMADMINPASS 

echo Generating Aliases...
$MMBIN/genaliases

echo Adding Members... 
$MMBIN/add_members -r $MMDMEMBERS -w n -a n $CSN-$i

echo Members of $CSN-$i:
$MMBIN/list_members $CSN-$i

echo Creating file for config_list...
echo description = '$CSN-$i' /tmp/mm-$CSN-$i
echo host_name = 'esolia.net' /tmp/mm-$CSN-$i
echo max_message_size = 0 /tmp/mm-$CSN-$i
echo available_languages = ['en', 'ja'] /tmp/mm-$CSN-$i
echo Configuring list...
$MMBIN/config_list -i /tmp/mm-$CSN-$i $CSN-$i

$MMBIN/withlist -l -r fix_url $CSN-$i -u www.domainofmine.net -v 
echo
done 

# cleanup
rm -f /tmp/mm-*

exit 0
==8

Hope this helps someone. 

Cheers,
Rick Cogley
Tokyo, Japan
--
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] Accept_these_nonmembers regexp

2005-07-21 Thread Cogley, Rick
Hello Everyone - 

I wonder if someone might be able to help with a regular expression
question. You can set the accept_these_nonmembers variable to something
like: 

[EMAIL PROTECTED]@(.+\.|)domainofmine\.co\.jp$

Which translates to, accept any posts from the domainofmine.co.jp domain. 

I would like to cover the bases, though, if I have:

domainofmine.com
domainofmine.co.jp
domainofmine.net

... In a single regular expression if possible. It would be enough to match
domainofmine. 

Can someone tell me how I can match anything after the dot after
domainofmine? Any advice warmly welcomed! Thanks!

Sincerely,

Rick Cogley
Tokyo, Japan
--
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] Mailman 2.1.5 - FQDN Question

2005-07-21 Thread Cogley, Rick
Interesting. That may well be the source of some wonky behavior, Steve and
thanks.  

My /etc/hosts has one line: 

200.100.10.1 rcogley.myispsdomain.com rcogley localhost

... Which man says is [IP, fqdn, alias, alias]

I have another domain I am hosting mail for on the machine, and postfix
sends out from root@ from this domain. 
Also, I have another IP as well. 

Can I just add to this file so it looks like: 

200.100.10.1 rcogley.myispsdomain.com rcogley localhost
200.100.10.1 www.domainofmine.net www

?

(and I thought having this schtuff in DNS was enough...)

Best Regards,
Rick

--
Rick Cogley (mailto:[EMAIL PROTECTED])

Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475
(Outside Japan, remove leading zero -- +81-3-5940-6880)
English: http://www.esolia.com || Japanese: http://www.esolia.co.jp

Bilingual IT solutions and management firm -- eSolia.
--



-Original Message-
From: Steve Burling [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 22, 2005 12:39 AM
To: Cogley, Rick
Subject: Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

--On July 21, 2005 3:38:30 PM +0900 Cogley, Rick 
[EMAIL PROTECTED] wrote:

 However, can anyone tell me why lists created in the web interface 
 default to www.domainofmine.net but lists created from the command 
 line default to localhost.localdomain? Of course, I can just run 
 fix_url after every list creation in the shell script, but, is there a 
 template somewhere that I can use to set it to use www.domainofmine.net
for all lists?

 Hope someone can assist! Thanks in advance!

To which I reply:

Just a wild-assed guess here, but what's your /etc/hosts look like?  Does it
have an entry for your the FQDN of your server, with its external IP
address?  I've stumbled over, or been bitten by, the localhost.localdomain
stuff on a bunch of red hat / fedora machines where /etc/hosts only has info
for the loopback interface.

-- 
Steve Burlingmailto:[EMAIL PROTECTED]
University of Michigan, ICPSRVoice: +1 734 615.3779
330 Packard Street   FAX:   +1 734 647.8700
Ann Arbor, MI 48104-2910
--
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] Mailman 2.1.5 - FQDN Question

2005-07-21 Thread Cogley, Rick
Perfect, Mark, thanks! I'll have to upgrade my script today, and put some
comments in it about the syntax change for when I can get a new RPM version.


Cheers,
Rick

-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 22, 2005 12:11 AM
To: Cogley, Rick; 'mailman-users@python.org'
Subject: Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

Cogley, Rick wrote:

However, can anyone tell me why lists created in the web interface 
default to www.domainofmine.net but lists created from the command line 
default to localhost.localdomain? Of course, I can just run fix_url 
after every list creation in the shell script, but, is there a 
template somewhere that I can use to set it to use www.domainofmine.net
for all lists?

Hope someone can assist! Thanks in advance! 

and

...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass

bin/newlist will create the list in the DEFAULT_URL_HOST domain unless you
specify another domain. In your case DEFAULT_URL_HOST is
localhost.localdomain because of your original work-around.

You can create the list in the correct domain with newlist in 2.1.5 using
the arcane syntax

/path/to/newlist -l en -q [EMAIL PROTECTED]
[EMAIL PROTECTED] s0m3pass

(note www.domainofmine.net, not domainofmine.net)

In 2.1.6 this syntax is deprecated in favor of

/path/to/newlist -l en -q -u www.domainofmine.net $CSHORTNAME-sales
[EMAIL PROTECTED] s0m3pass

--
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] Mailman 2.1.5 - FQDN Question

2005-07-21 Thread Cogley, Rick
Thanks Steve. I will ask the hosting company since the instance is on a
VPS'ed Fedora. They do some funkay stuff with networking...
Cheers,
Rick


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Steve Burling
Sent: Friday, July 22, 2005 5:06 AM
To: 'mailman-users@python.org'
Subject: Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

--On July 22, 2005 4:46:07 AM +0900 Cogley, Rick 
[EMAIL PROTECTED] wrote:

 My /etc/hosts has one line:

 200.100.10.1 rcogley.myispsdomain.com rcogley localhost

 ... Which man says is [IP, fqdn, alias, alias]

This still looks bogus to me -- localhost is more typically on a line by
itself, tied to the loopback interface, for example:

127.0.0.1   localhost.localdomain localhost

 I have another domain I am hosting mail for on the machine, and 
 postfix sends out from root@ from this domain.
 Also, I have another IP as well.

 Can I just add to this file so it looks like:

 200.100.10.1 rcogley.myispsdomain.com rcogley localhost
 200.100.10.1 www.domainofmine.net www

Other than moving the localhost to a line by itself, I *think* this is ok. 
I'm not a DNS god, though, so others may well correct me.

But I suspect that your ultimate problem is one that was suggested by
someone else (Mark?) -- you've got a bad value set for DEFAULT_URL_HOST. 
Fixing that in mm_cfg.py will probably help.

YMMV; I'm merely a dabbler in the mailman configuration business.

-- 
Steve Burlingmailto:[EMAIL PROTECTED]
University of Michigan, ICPSRVoice: +1 734 615.3779
330 Packard Street   FAX:   +1 734 647.8700
Ann Arbor, MI 48104-2910
--
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/rick.cogley%40esolia.co
.jp

Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
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] Mailman 2.1.5 - FQDN Question

2005-07-20 Thread Cogley, Rick
Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:

After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #: 

=8=
...
# DEFAULT_URL_HOST   = fqdn
# DEFAULT_EMAIL_HOST = fqdn

# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST   = domainofmine.net

# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST   = rcogley.user.myisp.com

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

# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net')
...
8=

I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.

Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]


8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists. 
...
echo mm-multi.sh - \$Revision: 0.1 $

# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
  echo
  echo Enter a short name for the client, no spaces, lowercase:
  read CSHORTNAME
  echo
  echo == SCRIPT PRESETS ==
  echo Location of Mailman scripts: $MMBIN
  echo Location of Mailman aliases: $MMALIASES
  echo List language: $MMLISTLANG
  echo List Owner Email: $MMOWNEREMAIL
  echo List Admin Password: $MMADMINPASS
  echo
  echo == USER ==
  echo Client Short Name: $CSHORTNAME
  echo
  echo Is this correct? (y/n)
  read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass 
/path/to/genaliases
/path/to/add_members -r memberlistfile -w n -a y $CSHORTNAME-sales
echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL 
PROTECTED]@(.+\\\.|)gmail\\\.com$']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
/path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp
$CSHORTNAME-sales 

[[repeat newlist through config_list for three more default list
names...]]

echo Lists Just Created: 
echo
/path/to/list_lists |grep $CSHORTNAME

# cleanup
rm -f /tmp/mm-multi*

exit 0
==8

A couple of observations: 

* After I used this script to create a set of test lists, it sent mail to
the owner (my account) FROM: [EMAIL PROTECTED] That indicates
to me something is wrong with a config file somewhere. The web
interface-created lists do NOT have this problem. They come in FROM:
[EMAIL PROTECTED] 

* Although Advertise this list when people ask what lists are on this
machine? is set to YES for these lists, all four that were autocreated by
the script are all not visible in the web list at
http://www.domainofmine.net/mailman/listinfo/. I can access them by typing
in the expected URL in the browser address bar:
http://www.domainofmine.net/mailman/admin/xyz-support/

* Even though I can bring up the admin area for the new lists by typing
their URLs in manually (the links are not visible) the links all have
localhost.localdomain in them, and so do not work. 

So my questions are: what do I set or focus on to make this
localhost.localdomain anomaly go away? Also, those regexps in
accept_these_nonmembers seem to overlap - does anyone know if there is a way
to set the regexp so that all mail from any domain with a certain string is
accepted? 

Any advice appreciated! THanks very much in advance...

Sincerely,
Rick Cogley
Tokyo 

Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

2005-07-20 Thread Cogley, Rick
Hope this formats ok this time. The relevant bit of the config file should
look like: 

...
# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') 
add_virtualhost('www.domainofmine.net', 'domainofmine.net') 

...
8=

This is what is working for me. 


Best Regards,
Rick

--
Rick Cogley (mailto:[EMAIL PROTECTED])

Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475
(Outside Japan, remove leading zero -- +81-3-5940-6880)
English: http://www.esolia.com || Japanese: http://www.esolia.co.jp

Bilingual IT solutions and management firm -- eSolia.
--



-Original Message-
From: Cogley, Rick 
Sent: Thursday, July 21, 2005 12:55 PM
To: 'mailman-users@python.org'
Cc: Cogley, Rick
Subject: Mailman 2.1.5 - FQDN Question

Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:

After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #: 

=8=
...
# DEFAULT_URL_HOST   = fqdn
# DEFAULT_EMAIL_HOST = fqdn

# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST   = domainofmine.net

# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST   = rcogley.user.myisp.com

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

# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net') ...
8=

I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.

Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]


8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists. 
...
echo mm-multi.sh - \$Revision: 0.1 $

# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
  echo
  echo Enter a short name for the client, no spaces, lowercase:
  read CSHORTNAME
  echo
  echo == SCRIPT PRESETS ==
  echo Location of Mailman scripts: $MMBIN
  echo Location of Mailman aliases: $MMALIASES
  echo List language: $MMLISTLANG
  echo List Owner Email: $MMOWNEREMAIL
  echo List Admin Password: $MMADMINPASS
  echo
  echo == USER ==
  echo Client Short Name: $CSHORTNAME
  echo
  echo Is this correct? (y/n)
  read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass
/path/to/genaliases /path/to/add_members -r memberlistfile -w n -a y
$CSHORTNAME-sales echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL 
PROTECTED]@(.+\\\.|)gmail\\\.com$']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
/path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp
$CSHORTNAME-sales 

[[repeat newlist through config_list for three more default list
names...]]

echo Lists Just Created: 
echo
/path/to/list_lists |grep $CSHORTNAME

# cleanup
rm -f /tmp/mm-multi*

exit 0
==8

A couple of observations: 

* After I used this script to create a set of test lists, it sent mail to
the owner (my account) FROM: [EMAIL PROTECTED] That indicates
to me something is wrong with a config file somewhere. The web
interface-created lists do NOT have this problem. They come in FROM:
[EMAIL PROTECTED] 

* Although Advertise this list when people ask what lists are on this
machine? is set

Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question

2005-07-20 Thread Cogley, Rick
Apologies - it formatted wrong again, stringing the most relevant line
together making it looked remarked out. Once more, it is probably obvious to
you, this is the relevant line in the config: 

add_virtualhost('www.domainofmine.net', 'domainofmine.net') 

This is what works, as opposed to using the DEFAULT_URL_HOST etc above it. 

Thanks
Rick




-Original Message-
From: Cogley, Rick
Sent: Thursday, July 21, 2005 12:55 PM
To: 'mailman-users@python.org'
Cc: Cogley, Rick
Subject: Mailman 2.1.5 - FQDN Question

Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:

After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #: 

=8=
...
# DEFAULT_URL_HOST   = fqdn
# DEFAULT_EMAIL_HOST = fqdn

# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST   = domainofmine.net

# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST   = rcogley.user.myisp.com

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

# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net') ...
8=

I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.

Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]


8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists. 
...
echo mm-multi.sh - \$Revision: 0.1 $

# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
  echo
  echo Enter a short name for the client, no spaces, lowercase:
  read CSHORTNAME
  echo
  echo == SCRIPT PRESETS ==
  echo Location of Mailman scripts: $MMBIN
  echo Location of Mailman aliases: $MMALIASES
  echo List language: $MMLISTLANG
  echo List Owner Email: $MMOWNEREMAIL
  echo List Admin Password: $MMADMINPASS
  echo
  echo == USER ==
  echo Client Short Name: $CSHORTNAME
  echo
  echo Is this correct? (y/n)
  read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass
/path/to/genaliases /path/to/add_members -r memberlistfile -w n -a y
$CSHORTNAME-sales echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL 
PROTECTED]@(.+\\\.|)gmail\\\.com$']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
/path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp
$CSHORTNAME-sales 

[[repeat newlist through config_list for three more default list
names...]]

echo Lists Just Created: 
echo
/path/to/list_lists |grep $CSHORTNAME

# cleanup
rm -f /tmp/mm-multi*

exit 0
==8

A couple of observations: 

* After I used this script to create a set of test lists, it sent mail to
the owner (my account) FROM: [EMAIL PROTECTED] That indicates
to me something is wrong with a config file somewhere. The web
interface-created lists do NOT have this problem. They come in FROM:
[EMAIL PROTECTED] 

* Although Advertise this list when people ask what lists are on this
machine? is set to YES for these lists, all four that were autocreated by
the script are all not visible in the web list at
http://www.domainofmine.net/mailman/listinfo/. I can access them by typing
in the expected URL in the browser address bar:
http://www.domainofmine.net/mailman/admin/xyz-support/

* Even though I can bring up the admin area