[Mailman-Users] Python modules missing

[Christopher Glanville]

I have been running mailman on Fedora core 4 for some time but then it 
stopped.
Now when I try and run:
/etc/init.d/mailman start

I get:

-bash: /etc/init.d/mailman: No such file or directory
[EMAIL PROTECTED] ~]# /etc/init.d/mailmanctl start
Traceback (most recent call last):
  File "/etc/init.d/mailmanctl", line 105, in ?
import paths
ImportError: No module named paths

Does anyone know where this module has gone or what package it might be 
contained in?
THanks very much
de Chris G

--
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] where is mailman-bounces address defined?

[Mark Sapiro]

douglas repetto wrote:
>
>We've been getting many many strange mailman-bounces. It seems that
>somewhere the mailman-bounces address is mis-configured. It should be
>[EMAIL PROTECTED], but mail seems to be sent as
>[EMAIL PROTECTED] (note missing "u"). That's causing
>bounces to bounce all over the place...in our mail log we get messages like:
>
>
>
>Jul 19 12:02:50 roar postfix/smtp[18535]: 9F86883BE24:
>to=<[EMAIL PROTECTED]>, relay=none, delay=0,
>status=bounced (Host or domain name not found. Name service error for
>name=music.columbia.ed type=A: Host not found)
>
>but also:
>
>Jul 19 12:02:54 roar postfix/qmgr[10647]: E969F83BE2C:
>from=<[EMAIL PROTECTED]>, size=4419, nrcpt=1 (queue active)
>
>
>
>
>So both the correct address and the incorrect address are being
>used...I've poked around in all of our configs and I can't find the
>incorrect address anywhere.


The domain comes from the host_name attribute of the mailman list
(visible on the mailman list's admin->General Options page).


>My suspicion at this point is that there's a
>virus somewhere on a users computer that is propagating the incorrect
>address and that many of the messages are the result of spoofed mail.


I think this is likely. Presumably the mail that causes this

>Jul 19 12:02:50 roar postfix/smtp[18535]: 9F86883BE24:
>to=<[EMAIL PROTECTED]>, relay=none, delay=0,
>status=bounced (Host or domain name not found. Name service error for
>name=music.columbia.ed type=A: Host not found)

originates from within your network from someone or some thing
connecting to postfix on your server to send this mail. If it came
from outside, it would never get to your domain in the first place.
What are the other log entries with the same 9F86883BE24 id. They may
give you a clue as to the source of this message.

It is not at all unusual for 'harvested' email addresses to be
truncated.

-- 
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] admin web interface is not saving changes andasksme to re-enter password

[Mark Sapiro]

Cornils, Karin wrote:
>
>In the packet trace, you see the Mailman send out the cookie in both the
>Firefox and IE versions, but on the return, you see the Cookie sent from
>Firefox, but don't see it sent back from IE  (Please let me know if
>sending the tcp streams to you offline would be useful).


Probably not, at least at this time.


>(I don't see
>the cookie in IE - apparently the session cookies in IE are cached in
>memory).


I think that's correct.


>So it seems that something in the upgrade post-2.1.5 has some issues
>with IE, or I'm missing something in the configuration (I've tried both
>source and package installations, Apache and Apache2, getting the same
>problem).  


I think it may be a list config issue. Check the following:

What is the host name in the initial URL that produces the login page,
and is this constant throughout or does it change?

Look at the source of the login page and the action= parameter of the
form tag. This is normally a relative URL.

Look at the source of the admin page after login and the action=
parameter of the form tag. This should be a full URL and should be the
same URL (host name in particular) as the URL that invoked the page.
If the host names are different, IE is considering the cookie a 3rd
party cookie.

I don't know that this will reveal any problem, but let's see.

BTW, does the admindb interface work or does it have the same problem?
Have you tried running fix_url on the list (your litany of FAQs
implies you have, but just checking).

-- 
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] admin web interface is not saving changes and asksme to re-enter password

[Cornils, Karin]

Thanks Mark, you're right about the cookie.  I had tried different
workstations and IE 6 & 7 browser versions to no effect (even in Accept
All Cookies mode and setting the Mailman site as trusted). But when I
try it on Firefox and Safari, it works - the reauthentication problem
doesn't happen in either of those browsers.  And that's on the same
desktop where the problem happens in IE.  In fact, the same IE browser
works fine against an old version of the list (2.1.5) but fails with
2.1.9. 

In the packet trace, you see the Mailman send out the cookie in both the
Firefox and IE versions, but on the return, you see the Cookie sent from
Firefox, but don't see it sent back from IE  (Please let me know if
sending the tcp streams to you offline would be useful). (I don't see
the cookie in IE - apparently the session cookies in IE are cached in
memory).

So it seems that something in the upgrade post-2.1.5 has some issues
with IE, or I'm missing something in the configuration (I've tried both
source and package installations, Apache and Apache2, getting the same
problem).  

Since it's not an option for me to ask all the admins to use Firefox,
I'd like to know if anyone has a Debian/Mailman 2.1.9 config working
with the IE browser..

Thanks,
Karin 

-Original Message-

Cornils, Karin wrote:

>This is on a Debian 4 package installation of Mailman 2.1.9 w. Apache2.
>I have tried all the FAQ suggestions in the FAQs that seem to relate to
>this issue: 
>4.71
>4.45
>4.27
>4.2.9
>4.65
>4.69  
>All  to no avail - details below - does anyone have any other
>suggestions?



It has to be a cookie issue. When you enter a valid password, the
authentication page sets a session cookie with authentication data.
This cookie is for the domain of the authentication page and has a
name which is +. E.g., for login with the admin
password for mylist, the name of the cookie is mylist+admin. The
cookie data are used to validate the cookie.

Can you see this cookie in your browser after you log in? It is a
session cookie, and I don't think you can see it in MSIE, at least I
don't know how - it's not with the persistent cookies in "Temporary
Internet Files".

Have you tried different browsers, different computers?

The issue pretty much has to be that the cookie isn't getting to the
browser because it is blocked on the way, the browser isn't accepting
it, the browser isn't returning it because it's not for the right
domain, or it is being blocked on the way back to the web server.

Ideally, you could run a packet sniffer on the connection and see if
the cookie is going back and forth. This would at least localize the
problem to the work station or the host.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,

The information contained in this email message may be privileged, confidential 
and protected from disclosure. If you are not the intended recipient, any 
dissemination, distribution or copying is strictly prohibited. If you think 
that you have received this email message in error, please notify the sender by 
reply email and delete the message and any attachments.

--
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] enhancement patches

[Brian Kantor]

Yes, indeed it is probably larger than need be, but after
fighting with other approaches, I just did it brute force.

Probably my way of doing it shouldn't be included in a future
release, although the capability of using syslog would be
very useful here.

Thank you for your comments.
- Brian


On Wed, Jul 18, 2007 at 06:24:15PM -0700, Mark Sapiro wrote:
> Brian Kantor wrote:
> 
> >I have a patch for mailman 2.1.9 that makes it direct
> >all logging to the system syslog 'maillog'.  We have
> >found this useful.
> >
> >It can be viewed at
> >   http://noh.ucsd.edu/~brian/Mailman-syslog-patch
> >
> >How should I submit this patch for consideration to
> >be included in a future release?
> 
> 
> We're part way to moving to a new tracker at 
> but that is not yet useable and the move seems to be stalled at the
> moment, so the place for patches is still the sourceforge tracker at
> .
> 
> 
> There are some issues with your patch. I looked at it and it seems
> unnecessarily complex (or maybe just large). Why not do the whole
> thing in Mailman/Logging/Syslog.py by keeping syslog as the name of
> the _Syslog instance and importing the system syslog as another name?
> 
> Perhaps more importantly, logging has completely changed on the Mailman
> trunk (now called the 3.0 branch) to use the Python 'logging' module
> and all the Mailman/Logging/* modules are gone.
> 
> -- 
> 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/brian%40ucsd.edu
> 
> 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

[Mailman-Users] where is mailman-bounces address defined?

[douglas repetto]

Hello,

We've been getting many many strange mailman-bounces. It seems that
somewhere the mailman-bounces address is mis-configured. It should be
[EMAIL PROTECTED], but mail seems to be sent as
[EMAIL PROTECTED] (note missing "u"). That's causing
bounces to bounce all over the place...in our mail log we get messages like:



Jul 19 12:02:50 roar postfix/smtp[18535]: 9F86883BE24:
to=<[EMAIL PROTECTED]>, relay=none, delay=0,
status=bounced (Host or domain name not found. Name service error for
name=music.columbia.ed type=A: Host not found)

but also:

Jul 19 12:02:54 roar postfix/qmgr[10647]: E969F83BE2C:
from=<[EMAIL PROTECTED]>, size=4419, nrcpt=1 (queue active)




So both the correct address and the incorrect address are being
used...I've poked around in all of our configs and I can't find the
incorrect address anywhere. My suspicion at this point is that there's a
virus somewhere on a users computer that is propagating the incorrect
address and that many of the messages are the result of spoofed mail.
Can anyone help me to understand what's going on? Or suggest where I
might look to see if the mailman-bounces address is in fact
mis-configured? In mm_cfg.py we have:

mm_cfg.py:DEFAULT_EMAIL_HOST = 'music.columbia.edu'
mm_cfg.py:DEFAULT_URL_HOST = 'music.columbia.edu'


so that seems correct...


thanks,
douglas





-- 
... http://artbots.org
.douglas.irving http://dorkbot.org
.. http://music.columbia.edu/cmc/music-dsp
.. repetto... http://works.music.columbia.edu/organism
... http://music.columbia.edu/~douglas


--
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] searchable archive interface desired

[Datatude]

Mark Sapiro wrote, On 7/19/07 11:08 AM:
> Datatude wrote:
>> Not a big issue right now because the 20 or so subscribers are likely to 
>> simply keep all the emails anyhow. What I might do is maintain monthly 
>> mboxes and just offer any subscribers added to the list in the future 
>> mboxes for import into their email clients.
> 
> 
> Pipermail already does this (sort of). 

Thanks Mark!
--
kazar
--
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] searchable archive interface desired

[Mark Sapiro]

Datatude wrote:
>
>Not a big issue right now because the 20 or so subscribers are likely to 
>simply keep all the emails anyhow. What I might do is maintain monthly 
>mboxes and just offer any subscribers added to the list in the future 
>mboxes for import into their email clients.


Pipermail already does this (sort of). That's what the periodic
"Downloadable version" files are. Many headers have been removed, and
the From: address may be munged a bit ('@' -> ' at '), but it is a
mbox.

Also, the full listname.mbox/listname.mbox file can be linked from the
archive TOC page by setting

PUBLIC_MBOX = Yes

in mm_cfg.py (and even if it's not linked, it can still be retrieved
via a url like
).

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