[Mailman-Users] RE:mailman wont send mail

2003-12-03 Thread Zimmermann Christian
Hello,
 
thanks for all the Tipps folks.
But when I say what the mistake was you all gona beet me up.
mailman wasn´t startet.
I could bite in my ass, I spend a lot of time to find whats wrong an then. argh.
I thought the service starts automaticly but anyway.
Thank to all.
 
Mit freundlichen Grüßen 
 
Christian Zimmermann
 
 _\|/_
 (@ @)
-oOOo-(_)-oOOo-
 
VitaNet GmbH
Industriestr. 50b
69190 Walldorf
 
Tel: 06227-35676961
Fax:06227-3567989
www.virtuelle-apotheke.de http://www.virtuelle-apotheke.de/ 
[EMAIL PROTECTED] 
 
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] htdig intregration problems

2003-12-03 Thread Paul Key
solaris 9
mailman 2.1.3
htdig  3.1.6
patches: indexing-2.1.3-0.1 and htdig-2.1.3-0.4
htdig is working.  from the command line i can do:

#/opt/www/htdig/bin/htsearch -c 
/usr/local/mailman/archives/htdig/mailman.conf

as users root , mailman and nobody and get the html search results 
correctly returned.

When I try and search from the web archive form i get:

 htdig Archives Access Failure

search failed -12-

If you want to make another attempt to access a list archive then go via 
the list users information page 
http://mailman.sghms.ac.uk/mailman//listinfo/mailman.

If this problem persists then please e-mail the following information to 
the [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]:

   http://mailman.sghms.ac.uk/pipermail/mailman/
   /mailman/mmsearch/mailman
if i run the nightly_htdig script from the command line it hangs with 'rundig failed for list mailman, exit code 134'

has anyone got any ideas where i can look to put things right...

thanks

paul





--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Upgrading lists 2.0.X - 2.1.X

2003-12-03 Thread Morgan Fletcher
Morgan Fletcher [EMAIL PROTECTED] writes:

 Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
 to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
 UPGRADING document, but when I try the upgrade with 2.0.8-era lists/ data,
 I get errors about missing properties. (fields?)

Anyone?

Morgan Fletcher

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] The causing a problem

2003-12-03 Thread gagel
I have a list with a  in the name, is this a dis-allowed character in
the list names?

I have recieved a message back indicating a problem with the use of
the  see below:
Final-Recipient: rfc822; arts[EMAIL PROTECTED] 
Action: failed 
Status: 5.0.0 
Diagnostic-Code: X-Postfix; Command died with status 127: 
/usr/local/mailman/mail/mailman request artsscience. Command
output: sh: 
science: command not found mailcmd script, list not found: arts 

Suggestions,comments,fixes?...


Kevin W. Gagel
Network Administrator
(250) 561-5848 local 448
(250) 562-2131 local 448

--
The College of New Caledonia, Visit us at http://www.cnc.bc.ca
Virus scanning is done on all incoming and outgoing email.
--

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] Multiple/Redundant Mailman servers

2003-12-03 Thread Charlie Watts
What's the Best Current Practice for running Multiple or Redundant
Mailman servers?

I have a distributed mail system - centralized local message store, and
many SMTP/POP heads. I'd *like* to be able to run Mailman on all of them,
with the same lists and configs.

Currently I NFS mount the configs for many other software packages, and it
works well.

I've tried NFS mounting /usr/local/mailman, and making qfiles a symlink to
a local directory on each machine. This doesn't work; I get messages
shunted because of Stale NFS filehandles and permission errors, even
though check_perms says I'm good.

If this simply isn't possible, I can shunt all of the mail to a central
list server, and just back-up mailman so I can bring it up elsewhere if
necessary.

But I'd love to have a way to do this.

-- 
Charlie Watts
Brainstorm Internet
970 247-1442 x113
[EMAIL PROTECTED]
http://www.brainstorminternet.net/

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The causing a problem

2003-12-03 Thread Simon White
03-Dec-03 at 10:08, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote :
 I have a list with a  in the name, is this a dis-allowed character in
 the list names?
 
 I have recieved a message back indicating a problem with the use of
 the  see below:
 Final-Recipient: rfc822; arts[EMAIL PROTECTED] 
 Action: failed 
 Status: 5.0.0 
 Diagnostic-Code: X-Postfix; Command died with status 127: 
 /usr/local/mailman/mail/mailman request artsscience. Command
 output: sh: 
 science: command not found mailcmd script, list not found: arts 

The  in shell has a special meaning, it would have to be escaped,
because

cd ..  ls

Means go up a directory then list it.  is a command separator or
something like that.  means execute the command that follows only if
the preceding command executes successfully.

Usernames should be A-Z, a-z, 0-9 and . _ with no other characters being
reliably passed in shell or by MTAs. That probably means list names
should be the same.

+ has a special meaning too, for VERP (variable envelope routing)

Regards,

-- 
Simon White. Internet Consultant, Linux/Windows Server Administration.
email, dns and web servers; php javascript perl asp; MySQL MSSQL Access
 Bridging the gap between management, HR and the tech team.

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The causing a problem

2003-12-03 Thread Vivek Khera
 SW == Simon White [EMAIL PROTECTED] writes:

SW The  in shell has a special meaning, it would have to be escaped,
SW because

If you read Business Week, the Tech  You column has a comment email
address of tech[EMAIL PROTECTED]

Just because the unix shell does something with  doesn't mean it is
invalid for local part of email addresses.  The Mailman aliases should
protect that in any case, because it could be used as a vector for
attack, even if it does require sysadmin assistance ;-)


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The causing a problem

2003-12-03 Thread Ed
While this is all true to some degree, don't overlook something even more 
obvious with regards to mailman, the web interface in trying to display 
that list name would actually be trying to display a page that takes a 
parameter. Apache / IIS would be significantly confused for sure.  's are 
not valid in HTML file names as they specify a part of a parameter list on 
the url.

It's always a good practice to stick with a-z 0-9 _-. only in names and 
you'll never have any sort of issue with email servers or web servers.

just my 0.02 worth
--Ed
At 03:08 PM 12/3/2003 -0500, you wrote:
 SW == Simon White [EMAIL PROTECTED] writes:

SW The  in shell has a special meaning, it would have to be escaped,
SW because
If you read Business Week, the Tech  You column has a comment email
address of tech[EMAIL PROTECTED]
Just because the unix shell does something with  doesn't mean it is
invalid for local part of email addresses.  The Mailman aliases should
protect that in any case, because it could be used as a vector for
attack, even if it does require sysadmin assistance ;-)
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/ed%40easent.net
__
EAS*Ent.Net - World Class Web Hosting and Email Box Services
www.easent.net
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The causing a problem

2003-12-03 Thread gagel
I'm getting more confused by the second...
I've removed the list and re-created it without the  in the name.

What happend is I'm transfering from an old server to a new mailman
server. The list created just fine and displays just fine. It seems
postfix is recieving the list name seperated as two names instead of a
single name. Messages to the old list server using the list name with
the  in it are not a problem with postfix. But mailman must be doing
or not doing something with postfix that caused the error.


- Original Message Follows -
 While this is all true to some degree, don't overlook something even
 more  obvious with regards to mailman, the web interface in trying
 to display  that list name would actually be trying to display a
 page that takes a  parameter. Apache / IIS would be significantly
 confused for sure.  's are  not valid in HTML file names as they
 specify a part of a parameter list on  the url.
 
 It's always a good practice to stick with a-z 0-9 _-. only in names
 and  you'll never have any sort of issue with email servers or web
 servers.
 
 just my 0.02 worth
 --Ed
 
 At 03:08 PM 12/3/2003 -0500, you wrote:
   SW == Simon White [EMAIL PROTECTED] writes:
 
 SW The  in shell has a special meaning, it would have to be
 escaped, SW because
 
 If you read Business Week, the Tech  You column has a comment
 email address of tech[EMAIL PROTECTED]
 
 Just because the unix shell does something with  doesn't mean it
 is invalid for local part of email addresses.  The Mailman aliases
 should protect that in any case, because it could be used as a
 vector for attack, even if it does require sysadmin assistance ;-)
 
 
 --
 Mailman-Users mailing list
 [EMAIL PROTECTED]
 http://mail.python.org/mailman/listinfo/mailman-users
 Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
 Searchable Archives:
 http://www.mail-archive.com/mailman-users%40python.org/ 
 This message was sent to: [EMAIL PROTECTED]
 Unsubscribe or change your options at
 http://mail.python.org/mailman/options/mailman-users/ed%40easent.ne
 t
 
 __
 EAS*Ent.Net - World Class Web Hosting and Email Box Services
 www.easent.net
 
 
 --
 Mailman-Users mailing list
 [EMAIL PROTECTED]
 http://mail.python.org/mailman/listinfo/mailman-users
 Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
 Searchable Archives:
 http://www.mail-archive.com/mailman-users%40python.org/
 
 This message was sent to: [EMAIL PROTECTED]
 Unsubscribe or change your options at

http://mail.python.org/mailman/options/mailman-users/gagel%40cnc.bc.ca


Kevin W. Gagel
Network Administrator
(250) 561-5848 local 448
(250) 562-2131 local 448

--
The College of New Caledonia, Visit us at http://www.cnc.bc.ca
Virus scanning is done on all incoming and outgoing email.
--

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] qrunner fails to start

2003-12-03 Thread Erick Mechler
I'm getting this error when I try to start the mailman qrunner daemon after
upgrading to 2.1.3 from 2.0.13.  Actually, I get this 10x, each one causing
the qrunner process to die and spawn anew:

Traceback (most recent call last):
  File /usr/local/mailman/bin/qrunner, line 270, in ?
main()
  File /usr/local/mailman/bin/qrunner, line 230, in main
qrunner.run()
  File /usr/local/mailman/Mailman/Queue/Runner.py, line 65, in run
filecnt = self._oneloop()
  File /usr/local/mailman/Mailman/Queue/Runner.py, line 93, in _oneloop
msg, msgdata = self._switchboard.dequeue(filebase)
  File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 158, in 
dequeue
data = self._ext_read(dbfile)
  File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 264, in 
_ext_read
dict = marshal.load(fp)
EOFError: EOF read where object expected

The corresponding entries in the qrunner log is this:

Dec 03 12:42:52 2003 (24329) IncomingRunner qrunner started.
Dec 03 12:42:52 2003 (24300) Master qrunner detected subprocess exit
(pid: 24329, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting]
Dec 03 12:42:52 2003 (24300) Qrunner IncomingRunner reached maximum restart 
limit of 10, not restarting.

This is on FreeBSD 4.9-STABLE (Tue Dec 2 16:27:33 PST 2003), mailman 2.1.3,
and Python 2.3.2 (both from ports).  Has anybody seen this before, or
perhaps know how I can do more debuggin'?

Cheers - Erick

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] The causing a problem

2003-12-03 Thread Vivek Khera
 e == ed  [EMAIL PROTECTED] writes:

e parameter. Apache / IIS would be significantly confused for sure.  's are 
e not valid in HTML file names as they specify a part of a parameter list on 
e the url.

If the code isn't URI escaping things when needed, then it is a
security breach waiting to happen.

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Upgrading lists 2.0.X - 2.1.X

2003-12-03 Thread Thomas Spuhler
I just did a
 ./bin/genaliases
and after that the existing mailing list were ok. 
Tom


On Wed, 2003-12-03 at 09:58, Morgan Fletcher wrote:
 Morgan Fletcher [EMAIL PROTECTED] writes:
 
  Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
  to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
  UPGRADING document, but when I try the upgrade with 2.0.8-era lists/ data,
  I get errors about missing properties. (fields?)
 
 Anyone?
 
 Morgan Fletcher
 
 --
 Mailman-Users mailing list
 [EMAIL PROTECTED]
 http://mail.python.org/mailman/listinfo/mailman-users
 Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
 
 This message was sent to: [EMAIL PROTECTED]
 Unsubscribe or change your options at
 http://mail.python.org/mailman/options/mailman-users/thomas%40btspuhler.com



signature.asc
Description: This is a digitally signed message part
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Upgrading lists 2.0.X - 2.1.X

2003-12-03 Thread Jon Carnes
On Wed, 2003-12-03 at 11:58, Morgan Fletcher wrote:
 Morgan Fletcher [EMAIL PROTECTED] writes:
 
  Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
  to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
  UPGRADING document, but when I try the upgrade with 2.0.8-era lists/ data,
  I get errors about missing properties. (fields?)
 
 Anyone?
 
 Morgan Fletcher

A problem that has been throughly discussed in archives sometimes goes
unanswered when asked for the umpteenth time

The first time that you access each list after an upgrade, Mailman will
see that the list is an older 2.0 version and will automatically update
the lists and the information in the list.

The old config files will still be there, but now there will be new .pck
configuration files that are used by Mailman 2.1.

In general, you should go into each of your lists using the web-admin
after an upgrade and make sure that the defaults used on that list are
the ones that you want and need.  Most of the problems occurring at this
point are due to your not editing the new ~mailman/Mailman/mm_cfg.py
file and adding the new sections that it expects (browse the Defaults.py
file for a clue as to what you need to add to this file after the
upgrade).

If you don't like the upgrade defaults (and most folks don't), and you
then change the defaults so that they are more to your liking, then
rename the generated .pck files and let mailman regenerate them again.

You can also simply go into the web-admin for the list and make any
changes there.

The most commonly mis-understood upgrade item is the way that virtual
domains are now done.  You must explicitly identify your domain and any
virtual domain that you use with any list.  The domain information
consists of the domain name used for mail and the web-address used for
the web-administration of the list.

Good luck - Jon Carnes


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] test mail if mailman work or not?

2003-12-03 Thread b udhi19
Hello there,
i'm new to mailman, 
i have installing mailman 2.1.3 on my FBSD 5.1 machine
and have postfix as my MTA, everything work well
till i add my e-mail to list,
but when i'm trying to send mail to my list,
it sent, but it's not sent to other members

i've try this :

jalak# ps -aux | grep mailmanctl | grep -v grep
mailman 14157  0.0  0.0  7408   12  ??  Is7:54AM   0:00.04 /usr/local/bin/python 
./mailmanctl 
start
jalak# ps -aux | grep cron | grep -v grep
root  416  0.0  0.3  1300  200  ??  Is   12:09AM   0:00.30 /usr/sbin/cron

and set newaliases, 
any idea what's wrong...?
i've been looking for archives and manual but maybe i'm not smart enough,
so i still get stuck... any suggestion?

regard,
Budhi



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Multiple/Redundant Mailman servers

2003-12-03 Thread Jon Carnes
On Wed, 2003-12-03 at 13:41, Charlie Watts wrote:
 What's the Best Current Practice for running Multiple or Redundant
 Mailman servers?
 
 I have a distributed mail system - centralized local message store, and
 many SMTP/POP heads. I'd *like* to be able to run Mailman on all of them,
 with the same lists and configs.
 
 Currently I NFS mount the configs for many other software packages, and it
 works well.
 
 I've tried NFS mounting /usr/local/mailman, and making qfiles a symlink to
 a local directory on each machine. This doesn't work; I get messages
 shunted because of Stale NFS filehandles and permission errors, even
 though check_perms says I'm good.
 
 If this simply isn't possible, I can shunt all of the mail to a central
 list server, and just back-up mailman so I can bring it up elsewhere if
 necessary.
 
 But I'd love to have a way to do this.

I use LVS at one site for this (you can search the archives and find all
the details you want), some folks use NFS and love it.  I'm comfortable
having one server as a master and only doing the changes to the master,
then echoing those changes out to the slaves.  One of the slaves takes
over as Master should the Master ever go down.

Take care - Jon Carnes


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org