Re: [Mailman-Users] port number

[Richard Barrett]

On 17 Jun 2006, at 22:35, Gerrit Bosch wrote:

> Hello,
>
> Sorry to bother you out there with this newbie question:
> Is it possible to change the portnumber for the webinterface to
> anything else than 80?

See under heading "Non-standard web server ports" on:

  http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp

and then read the rest of the FAQ entry.

> Thus avoiding interference with another webserver on the  same subnet.

>
> Couldn't find the answer in the FAQ's.
>
> Thanks,
> Gerrit Bosch.
> ideeinbeeld.nl
>
> --
> 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/ 
> r.barrett%40openinfo.co.uk
>
> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? 
> req=show&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=show&file=faq01.027.htp

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Scott Thomson]

Hmm, well, after going through the FAQ, I think its working again, for some
reason restarting it with mailmanctl instead of service mailman restart
seems to have done the trick.  At least I think thats what fixed it, I could
be wrong about that.

Thanks for your help Mark!

Scott

On 6/17/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
> Mark Sapiro wrote:
> >
> >Also, as I look more closely at the original traceback, it is unusual
> >in that entries usually only have the pid and yours say 'mailowner
> >(pid)', and I don't know what 'mailowner' is.
> >
> >What do your sendmail aliases for Mailman look like? Normally, they all
> >pipe to /var/mailman/mail/mailman with different arguments. Do yours
> >pipe to other commands like maybe /var/mailman/mail/mailowner? If so,
> >is the file(s) group Mailman and SETGID?
>
>
> The light finally dawns :-)
>
> You upgraded from 2.0.x and you didn't change your Mailman aliases for
> Sendmail. See item 2 in
> 
> for an example of what the aliases should look like. Or, you can run
> bin/genaliases to print a list.
>
> --
> 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=show&file=faq01.027.htp

Re: [Mailman-Users] port number

[Mark Sapiro]

Gerrit Bosch wrote:
>
>Sorry to bother you out there with this newbie question:
>Is it possible to change the portnumber for the webinterface to 
>anything else than 80?
>Thus avoiding interference with another webserver on the  same subnet.


To make the links on the Mailman web pages include the port, you need
to add the port to DEFAULT_URL_PATTERN by putting something like the
following in mm_cfg.py

DEFAULT_URL_PATTERN = http://%s:8080/mailman/

(using port 8080 for example, and assuming no other change to the
default).

This will suffice for new lists, but for existing lists you need to run
fix_url to update the list and also bin/arch to fix absolute links in
the list's archives.

Run

bin/fix_url.py

standalone to get its usage, and

bin/arch --help

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

[Mailman-Users] port number

[Gerrit Bosch]

Hello,

Sorry to bother you out there with this newbie question:
Is it possible to change the portnumber for the webinterface to 
anything else than 80?
Thus avoiding interference with another webserver on the  same subnet.

Couldn't find the answer in the FAQ's.

Thanks,
Gerrit Bosch.
ideeinbeeld.nl

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Mark Sapiro]

Mark Sapiro wrote:
>
>Also, as I look more closely at the original traceback, it is unusual
>in that entries usually only have the pid and yours say 'mailowner
>(pid)', and I don't know what 'mailowner' is.
>
>What do your sendmail aliases for Mailman look like? Normally, they all
>pipe to /var/mailman/mail/mailman with different arguments. Do yours
>pipe to other commands like maybe /var/mailman/mail/mailowner? If so,
>is the file(s) group Mailman and SETGID?


The light finally dawns :-)

You upgraded from 2.0.x and you didn't change your Mailman aliases for
Sendmail. See item 2 in

for an example of what the aliases should look like. Or, you can run
bin/genaliases to print a list.

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

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Mark Sapiro]

Scott Thomson wrote:
>
>This is the bounce message we're getting by the way:
>
>The following recipient(s) could not be reached:
>
>  [EMAIL PROTECTED] on 6/16/2006 5:28 PM
>The e-mail system was unable to deliver the message, but did not
>report a specific reason.  Check the address and try again.  If it still
>fails, contact your system administrator.
>< sb1.uua.org #5.0.0 X-Unix; 1>


That's consistent with the traceback in your original post. The
traceback showed that the 'owner' script which would have been trying
to store a message to [EMAIL PROTECTED] could not create the queue
entry in the qfiles/in/ directory. It died and the wrapper reported
this back to the MTA.

Your original post showed that the message was shunted:

Jun 17 03:53:02 2006 (27701) SHUNTING:
1150530781.4040949+b05e0d8630edf39d7052ae94e9689917b1edabdf

Is there a file named
1150530781.4040949+b05e0d8630edf39d7052ae94e9689917b1edabdf
.pck in qfiles/shunt?

Also, as I look more closely at the original traceback, it is unusual
in that entries usually only have the pid and yours say 'mailowner
(pid)', and I don't know what 'mailowner' is.

What do your sendmail aliases for Mailman look like? Normally, they all
pipe to /var/mailman/mail/mailman with different arguments. Do yours
pipe to other commands like maybe /var/mailman/mail/mailowner? If so,
is the file(s) group Mailman and SETGID?

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

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Scott Thomson]

On 6/17/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
> Scott Thomson wrote:
> >
> >Thanks for the ideas, now I feel like I'm getting closer to the issue.
> >
> >check_perms came up clean, all the files in the in dir match these
> >permissions.
> >
> >2302ff99d3a89dc936c9e66497cb08201f0.pck
> >-rw-rw1 mail mailman 10043 Jun 17 14:08
> >1150567685.345078+9eff67
> >
> >/var/mailman/qfiles//in looks like this:
> >
> >drwxrws---2 root mailman 16384 Jun 17 14:54 in
> >
> >Should that be owned by root or by mailman like everything else in that
> >directory?  The virgin directory is also owned by root.
>
>
> Sometimes the owner is root and sometimes mailman depending on just how
> it was created. It's not important. The group is the important thing.
> It should always be mailman and /var/mailman/mail/mailman and all the
> files in /var/mailman/cgi-bin should be group mailman and SETGID.
> check_perms would have caught any problems here.
>
> Are you running SeLinux or anything else that would impose additional
> access controls?



Not to my knowlege.  Any other ideas?

This is the bounce message we're getting by the way:

The following recipient(s) could not be reached:

  [EMAIL PROTECTED] on 6/16/2006 5:28 PM
The e-mail system was unable to deliver the message, but did not
report a specific reason.  Check the address and try again.  If it still
fails, contact your system administrator.
< sb1.uua.org #5.0.0 X-Unix; 1>


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

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Mark Sapiro]

Scott Thomson wrote:
>
>Thanks for the ideas, now I feel like I'm getting closer to the issue.
>
>check_perms came up clean, all the files in the in dir match these
>permissions.
>
>2302ff99d3a89dc936c9e66497cb08201f0.pck
>-rw-rw1 mail mailman 10043 Jun 17 14:08
>1150567685.345078+9eff67
>
>/var/mailman/qfiles//in looks like this:
>
>drwxrws---2 root mailman 16384 Jun 17 14:54 in
>
>Should that be owned by root or by mailman like everything else in that
>directory?  The virgin directory is also owned by root.


Sometimes the owner is root and sometimes mailman depending on just how
it was created. It's not important. The group is the important thing.
It should always be mailman and /var/mailman/mail/mailman and all the
files in /var/mailman/cgi-bin should be group mailman and SETGID.
check_perms would have caught any problems here.

Are you running SeLinux or anything else that would impose additional
access controls?

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

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Mark Sapiro]

Scott Thomson wrote:

>So I upgraded mailman and sendmail yesterday, I'm running RHEL3 on a machine
>out at serverbeach.  The latest mailman is 2.1.5 via Red Hat Network.
>
>Now that I've upgraded to the latest versions of both available via up2date,
>I'm getting errors when sending to a list.
>
>This is what is in my /error log for mailman.
>
>Jun 17 03:53:02 2006 (27701) SHUNTING:
>1150530781.4040949+b05e0d8630edf39d7052ae94e9689917b1edabdf
>Jun 17 03:54:21 2006 mailowner(4097): Traceback (most recent call last):
>mailowner(4097):   File "/var/mailman/scripts/owner", line 67, in ?
>mailowner(4097):  main()
>mailowner(4097):   File "/var/mailman/scripts/owner", line 62, in main
>mailowner(4097):  toowner=1)
>mailowner(4097):   File "/var/mailman/Mailman/Queue/Switchboard.py", line
>126, in enqueue
>mailowner(4097):  fp = open(tmpfile, 'w')
>mailowner(4097): IOError :  [Errno 13] Permission denied:
>'/var/mailman/qfiles/in/1150530861.4845021+b8057e80f0ff22e8f65d4d330
>7e5f08a97a1e1a3.pck.tmp'


Clearly there is some permissions issue on at least the 'in' queue if
not all the qfiles/ directories.

Try running 'bin/check_perms -f' as root. You may need to run it more
than once until it runs error free.


>Jun 17 05:05:20 2006 (27520) No such list "sunday2002-l": (a whole lot of
>these errors)


Does this list exist? Is there a lists/sunday2002-l/ directory? This is
a 'normal' error if someone tries to access a non-existent list via
the web interface.

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

[Mailman-Users] Errors after upgrade via up2date to 2.1.5

[Scott Thomson]

So I upgraded mailman and sendmail yesterday, I'm running RHEL3 on a machine
out at serverbeach.  The latest mailman is 2.1.5 via Red Hat Network.

Now that I've upgraded to the latest versions of both available via up2date,
I'm getting errors when sending to a list.

This is what is in my /error log for mailman.

Jun 17 03:53:02 2006 (27701) SHUNTING:
1150530781.4040949+b05e0d8630edf39d7052ae94e9689917b1edabdf
Jun 17 03:54:21 2006 mailowner(4097): Traceback (most recent call last):
mailowner(4097):   File "/var/mailman/scripts/owner", line 67, in ?
mailowner(4097):  main()
mailowner(4097):   File "/var/mailman/scripts/owner", line 62, in main
mailowner(4097):  toowner=1)
mailowner(4097):   File "/var/mailman/Mailman/Queue/Switchboard.py", line
126, in enqueue
mailowner(4097):  fp = open(tmpfile, 'w')
mailowner(4097): IOError :  [Errno 13] Permission denied:
'/var/mailman/qfiles/in/1150530861.4845021+b8057e80f0ff22e8f65d4d330
7e5f08a97a1e1a3.pck.tmp'
Jun 17 05:05:20 2006 (27520) No such list "sunday2002-l": (a whole lot of
these errors)


Any ideas?

Scott Thomson
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Discarding nonmembers emails

[Mark Sapiro]

Todd C. Williams wrote:

>I have volunteered to train people on the use of Mailman version 2.1.7.cp2
>for PMI Portland (http://www.pmi-portland.org/).  
> 
>I do not understand the "Privacy options." "Sender filters", entry "List of
>non-member addresses whose postings will be automatically discarded".  I
>have entered an address and set the option "Should messages from
>non-members, which are automatically discarded, be forwarded to the list
>moderator?" to "no" and the administrators and moderators still get notices.

Notices that say that the post from the address in
discard_these_nonmembers was auto discarded, or some other notice?

There are 4 possible actions to be taken on a post from a non-member.

Accept - accept the post for the list
Hold - hold the post for review by a moderator - notify the
   owners/moderators in a daily summary and also immediately if
   General Options->admin_immed_notify is Yes. Also notify the
   poster of the hold.
Reject - do not accept the message but notify the poster.
Discard - do not accept the post and do not notify the poster.

The lists Privacy options...->Sender filters->*_these_nonmembers are
lists of non-member addresses and regular expressions matching
non-member addresses. The corresponding action will be applied to
posts from a non-member address that matches one of these lists.

Posts from non-member addresses that don't match one of the lists are
handled according to Privacy options...->Sender
filters->generic_nonmember_action.


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

[Mailman-Users] Discarding nonmembers emails

[Todd C. Williams]

I have volunteered to train people on the use of Mailman version 2.1.7.cp2
for PMI Portland (http://www.pmi-portland.org/).  
 
I do not understand the "Privacy options." "Sender filters", entry "List of
non-member addresses whose postings will be automatically discarded".  I
have entered an address and set the option "Should messages from
non-members, which are automatically discarded, be forwarded to the list
moderator?" to "no" and the administrators and moderators still get notices.

 
What am I missing.
 
Cheers,
  Todd C. Williams
eCameron, Inc.
www.ecaminc.com  
Office: 1-360-834-7361
Hand Ph: 1-360-521-9051

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Japanese Character encoding

[Lawrence Bowie]

Mark Sapiro wrote:
> Lawrence Bowie wrote:
> 
> 
>>Mark Sapiro wrote:
>>
>>>What does scripts/paths.py now contain?
>>>
>>
>># -*- python -*-
>>
>># Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
>>#
>># This program is free software; you can redistribute it and/or
>># modify it under the terms of the GNU General Public License
>># as published by the Free Software Foundation; either version 2
>># of the License, or (at your option) any later version.
>>#
>># This program is distributed in the hope that it will be useful,
>># but WITHOUT ANY WARRANTY; without even the implied warranty of
>># MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>># GNU General Public License for more details.
>>#
>># You should have received a copy of the GNU General Public License
>># along with this program; if not, write to the Free Software
>># Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
>>
>># This file becomes paths.py which is installed in may directories.  By
>># importing this module, sys.path gets `hacked' so that the $prefix/Mailman
>># directory is inserted at the start of that list.  That directory really
>># contains the Mailman modules in package form.  This file exports two
>># attributes that other modules may use to get the absolute path to the
>># installed Mailman distribution.
>>
>>import sys
>>import os
>>import japanese
> 
> 
> 
> This (import japanese) needs to be at the end after the sys.path
> manipulations.  I gave you the wrong info for testing this. It should
> have been
> 
> python -S scripts/paths.py
> 
> 
> 
>># some scripts expect this attribute to be in this module
>>prefix = '/usr/lib/mailman'
>>exec_prefix = '${prefix}'
>>
>># work around a bogus autoconf 2.12 bug
>>if exec_prefix == '${prefix}':
>>exec_prefix = prefix
>>
>># Hack the path to include the parent directory of the $prefix/Mailman package
>># directory.
>>sys.path.insert(0, prefix)
>>
>># We also need the pythonlib directory on the path to pick up any overrides of
>># standard modules and packages.  Note that these must go at the front of the
>># path for this reason.
>>sys.path.insert(0, os.path.join(prefix, 'pythonlib'))
>>
>># Include Python's site-packages directory.
>>sitedir = os.path.join(sys.prefix, 'lib', 'python'+sys.version[:3],
>>   'site-packages')
>>sys.path.append(sitedir)
>>
> 
> 
> 
> 

Since I put it at the end. It is seemingly working now. So I have placed,

import japanese

at the end of sys.path in the files {cron,tests,bin,scripts/paths.py and
it works.

Thanks Mark,

LDB

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp