[Mailman-Users] Unkown user

[G. Armour Van Horn]

I did something, although I can't for the life of me figure out what, 
that broke my mailman server. The web presence hasn't changed any, user 
administration works fine, as does access to the archive, and monthly 
password reminders are being sent. But mail to any of the lists bounces. 
I'm running Mailman 2.1.9 (just upgraded from 2.1.8 tonight in hopes 
that the new install would fix the problem) with Postfix 2.2.5 on RedHat 
7.2.

The heart of the bounce is as follows:

<"|/home/mailman/mail/mailman post freehand"@domainvanhorn.com> (expanded from
<[EMAIL PROTECTED]>): unknown user:
"|/home/mailman/mail/mailman post freehand"


The aliases (/etc/postfix/aliases) for that list look like this:

## freehand mailing list
freehand:  "|/home/mailman/mail/mailman post freehand"
freehand-admin:"|/home/mailman/mail/mailman admin freehand"
freehand-bounces:  "|/home/mailman/mail/mailman bounces freehand"
freehand-confirm:  "|/home/mailman/mail/mailman confirm freehand"
freehand-join: "|/home/mailman/mail/mailman join freehand"
freehand-leave:"|/home/mailman/mail/mailman leave freehand"
freehand-owner:"|/home/mailman/mail/mailman owner freehand"
freehand-request:  "|/home/mailman/mail/mailman request freehand"
freehand-subscribe:"|/home/mailman/mail/mailman subscribe freehand"
freehand-unsubscribe:  "|/home/mailman/mail/mailman unsubscribe freehand"

Does this suggest anything to anybody?

Van




-- 
--
Sign up now for Quotes of the Day, a handful of quotations
on a theme delivered every morning.
Enlightenment! Daily, for free! 
mailto:[EMAIL PROTECTED]

For photography, web design, hosting, and maintenance, 
visit Van's home page: http://www.domainvanhorn.com/van/
---

--
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] Upgrading from 2.1.5 to 2.1.9

[Brad Knowles]

At 3:55 PM -0700 11/8/06, Ivan Fetch wrote:

> I'm wondering whether anyone has experience they'd like to share going
>  directly from 2.1.5 to 2.1.9 -- anything to be aware of in terms of the
>  upgrade process or user experiences (meaning list administrators and
>  members)?

I recently did the upgrade from 2.1.5 to 2.1.9 for the NTP Public 
Services Project at ntp.isc.org.  It really was this simple:

1.  Stop the web server (apache)
2.  Stop postfix
3.  Stop Mailman
4.  As root, do "cd /usr/ports/mail/mailman/; make install"
5.  Start Mailman
6.  Start postfix
7.  Start the web server
8.  Check everything to see that it all appears to be working
correctly.

Of course, I actually used the FreeBSD port system to install Mailman 
as opposed to installing from source, but the concept is the same. 
And this is no guarantee that things will be this clean for you.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

Trend Micro has announced that they will cancel the stop.mail-abuse.org
mail forwarding service as of 15 November 2006.  If you have an old
e-mail account for me at this domain, please make sure you correct that
with the current address.
--
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] us-ascii problem with new install in Ubuntu

[Mark Sapiro]

Kyle Sexton wrote:
>
>Thanks for your reply.  I realized after I sent the message that I left of
>the version numbers:
>
>mailman 2.1.8-2ubuntu2
>
>My Scrubber.py has a filesize of 22414, and I posted it here:
>http://pastebin.ca/243930.  Is it possible that there is a language pack or
>something missing in the default Ubuntu install that is a dependency I'm
>missing?


I looked at your Scrubber.py and the changes I see from the 2.1.8/2.1.9
base don't look like they would cause this problem. I also don't think
it is any sort of missing dependency, but I don't know what it is.

If you send me off list or put somewhere on the web, the
/usr/lib/mailman/qfiles/shunt/1163027059.0068791+6913355f30b2fbfb61b3469f5bf538e0ed51ecb9.pck
file, I'll try to look at this further.

-- 
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] Some of my Mailman mailing lists don't workbutsome do.

[Mark Sapiro]

[EMAIL PROTECTED] wrote:

>I do have access to the mailman installation and log files. Just not  
>sure exactly where to look, or what to look for.


First, I remembered there was a bug in Mailman prior to 2.1.9 which
would not send the welcome message from a mass subscribe unless the
list's send_welcome_message (on General Options) was Yes. This didn't
affect invitations as best as I can recall, although the
'notification' buttons on an 'invitatation' are really meaningless. No
notifications are sent with the invitation other than the invitation
itself, and when the user accepts the invitation, notifications ar
sent according to list settings

Could this be the problem?

If this is not the problem, then do I understand correctly that only
invitations and new subscriber welcome messages are missing, and only
for at least one 'old' list? Does this list function normally
otherwise?

If this is the case, Look in Mailman's 'error' and 'subscribe' logs.
Report any errors and also if the subscribes are logged or not. I
suspect they are logged and the user is subscribed even though the
welcome wasn't set. I'm leaning towards the above bug as the
explaination.

-- 
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] bcc problem

[stephen]

o omida parasita writes:

 > When using an email list if you send a message to the list but also do
 > a bcc /cc the message gets sent to moderator.

If the list address is in either To: or Cc:, it should not be
moderated for the reason "implicit destination".  Are you sure you are
actually sending "To:" the list?  Surely this only happens when you
"Bcc:" the list?

 > If I (a member of the list) send a message to [EMAIL PROTECTED]
 > and I bcc [EMAIL PROTECTED], the message gets sent to the
 > moderator for approval.

Surely it's the other way around?  You sent to john and bcc'd
production, right?

 > Is there a way to disable this feature/problem?

Go to the Privacy Options>Recipient Filters screen in the list
administration interface.  Set require_explicit_destination to off.

--
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] bcc problem

[Mark Sapiro]

o omida parasita wrote:
>
>If I (a member of the list) send a message to [EMAIL PROTECTED] and I
>bcc [EMAIL PROTECTED], the message gets sent to the moderator for
>approval. I would get a message saying that the message is being held until
>the list moderator can review it for approval.
>
>The reason it is being held:
>
>Message has implicit destination


Are you sure that's what's happening, and it's not the other way around.

In other words, if you send To: 'user' with Bcc: 'list' the implicit
destination hold is expected because the list address is not included
as a visible (To: or Cc:) recipient of the post. If you want such
posts to be accepted, set Privacy options...->Recipient
filters->require_explicit_destination to No.

On the other hand, if you send To: 'list' with Bcc: 'user' this should
be no different to Mailman than if you sent To: 'list' without the
Bcc:.

-- 
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] us-ascii problem with new install in Ubuntu

[Kyle Sexton]

On 11/8/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
> Kyle Sexton wrote:
>
> >Fresh install of mailman on an Ubuntu system and I get the following
> error
> >cropping up when I send a message to a list:
> >
> >Nov 08 17:04:20 2006 (9848) uncaught archiver exception at filepos: 0
> >Nov 08 17:04:20 2006 (9848) Uncaught runner exception: us-ascii
> >Nov 08 17:04:20 2006 (9848) Traceback (most recent call last):
> >  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
> >self._onefile(msg, msgdata)
> >  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
> >keepqueued = self._dispose(mlist, msg, msgdata)
> >  File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in
> _dispose
> >mlist.ArchiveMail(msg)
> >  File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 214, in
> >ArchiveMail
> >h.processUnixMailbox(f)
> >  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 564, in
> >processUnixMailbox
> >m = mbox.next()
> >  File "mailbox.py", line 35, in next
> >return self.factory(_Subfile(self.fp, start, stop))
> >  File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber
> >return mailbox.scrub(msg)
> >  File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub
> >return self._scrubber(self._mlist, msg)
> >  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 397, in
> process
> >replace_payload_by_text(msg, sep.join(text), charset)
> >  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in
> >replace_payload_by_text
> >msg.set_payload(text, charset)
>
>
>
> What Mailman version is this? The above line numbers in Scrubber.py
> don't match any of 2.1.7 (when replace_payload_by_text was first
> introduced) through 2.1.9. It looks like your version has a modified
> (by Ubuntu or ?) version of Scrubber.py that is broken - perhaps
> somewhere charset is being assigned us-ascii instead of 'us-ascii'.
>
>
> >  File "email/Message.py", line 218, in set_payload
> >  File "email/Message.py", line 242, in set_charset
> >TypeError: us-ascii
> >
> >Nov 08 17:04:20 2006 (9848) SHUNTING:
> >1163027059.0068791+6913355f30b2fbfb61b3469f5bf538e0ed51ecb9
> >
> >
> >It looks to me to be some type of language pack problem?  Mails go
> through
> >to the different users without issue, but never seem to make it to the
> >archive pool.
>
>
> The messages are shunted. Once you resolve the Scrubber.py issue, you
> can run bin/unshunt and they will be archived.
>
> --
> Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>
>
Mark,

Thanks for your reply.  I realized after I sent the message that I left of
the version numbers:

mailman 2.1.8-2ubuntu2

My Scrubber.py has a filesize of 22414, and I posted it here:
http://pastebin.ca/243930.  Is it possible that there is a language pack or
something missing in the default Ubuntu install that is a dependency I'm
missing?

-- 
Kyle Sexton
--
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] us-ascii problem with new install in Ubuntu

[Mark Sapiro]

Kyle Sexton wrote:

>Fresh install of mailman on an Ubuntu system and I get the following error
>cropping up when I send a message to a list:
>
>Nov 08 17:04:20 2006 (9848) uncaught archiver exception at filepos: 0
>Nov 08 17:04:20 2006 (9848) Uncaught runner exception: us-ascii
>Nov 08 17:04:20 2006 (9848) Traceback (most recent call last):
>  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
>self._onefile(msg, msgdata)
>  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose
>mlist.ArchiveMail(msg)
>  File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 214, in
>ArchiveMail
>h.processUnixMailbox(f)
>  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 564, in
>processUnixMailbox
>m = mbox.next()
>  File "mailbox.py", line 35, in next
>return self.factory(_Subfile(self.fp, start, stop))
>  File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber
>return mailbox.scrub(msg)
>  File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub
>return self._scrubber(self._mlist, msg)
>  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 397, in process
>replace_payload_by_text(msg, sep.join(text), charset)
>  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in
>replace_payload_by_text
>msg.set_payload(text, charset)



What Mailman version is this? The above line numbers in Scrubber.py
don't match any of 2.1.7 (when replace_payload_by_text was first
introduced) through 2.1.9. It looks like your version has a modified
(by Ubuntu or ?) version of Scrubber.py that is broken - perhaps
somewhere charset is being assigned us-ascii instead of 'us-ascii'.


>  File "email/Message.py", line 218, in set_payload
>  File "email/Message.py", line 242, in set_charset
>TypeError: us-ascii
>
>Nov 08 17:04:20 2006 (9848) SHUNTING:
>1163027059.0068791+6913355f30b2fbfb61b3469f5bf538e0ed51ecb9
>
>
>It looks to me to be some type of language pack problem?  Mails go through
>to the different users without issue, but never seem to make it to the
>archive pool.


The messages are shunted. Once you resolve the Scrubber.py issue, you
can run bin/unshunt and they will be archived.

-- 
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] debian/exim4/mailman

[Mark Sapiro]

Eric Walker wrote:

>JB/Mark,
>Well I sent in an email to godaddy. I asked them about the 533 error that 
>stated host was not a valid host in the rcpt list. They said that error would 
>show up when using a email client and I didn't have the button down that says 
>outgoing smtp server needs authentication. So, I am assuming this means that 
>my exim4 is not authenticating. How can I test to see if exim4 is sending out 
>the correct info to authenticate. I do have the paswd and username in my 
>passwd.client file.


I don't offhand know the answer to your Exim authentication issue or
even if it's possible, but this is an Exim question and beyond the
scope of the Mailman-users list.

However, I urge you to forget about delivering from Mailman to Exim to
godaddy to end recipients. If you don't want to take Ed's (JB) advice,
then just set up Mailman to use godaddy directly as the outgoing SMTP
server. See

and the 'authentication' patch in the post linked from that FAQ.

-- 
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] Can't send messages to list

[Dr. Scott S. Jones]

Mark: 

I made the changes that Lucaz mentioned, with the two files, replacing them
and now mailman SEEMS to be working. It is sending out to my list anyway. 

I am not sure that everything is working quite right though so I'll test
things more, for a few days. 

Scott

--
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] Can't send messages to list

[Mark Sapiro]

Lukasz Szybalski wrote:
>
>I put the original smtplib.py file back in /varlib/python.3/smtplib.py
>and i get the same problem again.
>
>Nov 08 16:41:31 2006 (13973) Low level smtp error: [Errno 9] Bad file
>descriptor, msgid:
><[EMAIL PROTECTED]>
>Nov 08 16:46:31 2006 (13973) delivery to [EMAIL PROTECTED] failed with
>code -1: [Errno 9] Bad file descriptor
>Nov 08 16:46:31 2006 (13973) Low level smtp error: [Errno 9] Bad file
>descriptor, msgid: <[EMAIL PROTECTED]>
>Nov 08 16:46:31 2006 (13973) delivery to [EMAIL PROTECTED] failed with
>code -1: [Errno 9] Bad file descriptor
>
>So i guess i will stick with the file i got from debian bug


Please post a 'diff -u' between the smtplib.py that works and the one
that doesn't work.

Lionel says that effectively all he changed in your working version was
writing debug output to sys.stderr instead of stdout, and when I
diffed Lionel's version with the Python 2.3.4 base, that's the only
change I saw, but there must be something else in your case or else
simply enabling the debug prints causes the problem because of the
writes to stdout, but then what caused the original problem.

In any case, I am very interested to see if there is some other change
in your original smtplib.py that is causing it to fail.

-- 
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] Upgrading from 2.1.5 to 2.1.9

[Ivan Fetch]

Hello,


IT's (past) time to upgrade our mailman 2.1.5 installation to version 
2.1.9.

I'm wondering whether anyone has experience they'd like to share going 
directly from 2.1.5 to 2.1.9 -- anything to be aware of in terms of the 
upgrade process or user experiences (meaning list administrators and 
members)?


Looking at the upgrade and news files, and searching the archives, the 
only thing I have found is some references to "versions 2.1.6 through 
2.1.8 had issues, try 2.1.9".  I'm not sure exactly what issues 2.1.6 
through 2.1.8 had (besides security issues I see that 2.1.9 fixed).


Thanks for the help,

- Ivan.

--
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] us-ascii problem with new install in Ubuntu

[Kyle Sexton]

Fresh install of mailman on an Ubuntu system and I get the following error
cropping up when I send a message to a list:

Nov 08 17:04:20 2006 (9848) uncaught archiver exception at filepos: 0
Nov 08 17:04:20 2006 (9848) Uncaught runner exception: us-ascii
Nov 08 17:04:20 2006 (9848) Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose
mlist.ArchiveMail(msg)
  File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 214, in
ArchiveMail
h.processUnixMailbox(f)
  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 564, in
processUnixMailbox
m = mbox.next()
  File "mailbox.py", line 35, in next
return self.factory(_Subfile(self.fp, start, stop))
  File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber
return mailbox.scrub(msg)
  File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub
return self._scrubber(self._mlist, msg)
  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 397, in process
replace_payload_by_text(msg, sep.join(text), charset)
  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in
replace_payload_by_text
msg.set_payload(text, charset)
  File "email/Message.py", line 218, in set_payload
  File "email/Message.py", line 242, in set_charset
TypeError: us-ascii

Nov 08 17:04:20 2006 (9848) SHUNTING:
1163027059.0068791+6913355f30b2fbfb61b3469f5bf538e0ed51ecb9


It looks to me to be some type of language pack problem?  Mails go through
to the different users without issue, but never seem to make it to the
archive pool.  I ran fixperms and the issue still is happening.  Any advice
or things to check would be greatly appreciated.  Setup is
Ubuntu+postfix+mailman.

Thanks!

-- 
Kyle Sexton
--
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] Can't send messages to list

[Lukasz Szybalski]

On 11/3/06, Lukasz Szybalski <[EMAIL PROTECTED]> wrote:
> > Lukasz Szybalski wrote:
> /var/lib/mailman/Mailman/Handlers/SMTPDirect.py
>
> >
> > >That is the file i patched SMTPDirect.py
> > >
> > > 57 class Connection:
> > > 58 def __init__(self):
> > > 59 self.__conn = None
> > > 60
> > > 61 def __connect(self):
> > > 62 self.__conn = smtplib.SMTP()
> > > 63 self.__conn.set_debuglevel(1)
> > > 64 self.__conn.connect(mm_cfg.SMTPHOST, mm_cfg.SMTPPORT)
> > > 65 self.__numsessions=mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION
>
>
> > >Is there a way to manually get the debug info from smtplib
> > >(conversation with postfix) within this file?
>
> Temporary SOLUTION.
>
> After placing a bug report in debian, i have been given two files to
> make debug information work.
>
> "replacements for /usr/lib/python2.3/smtplib.py
> and /usr/lib/mailman/Mailman/Logging/Utils.py that will enable
> smtplib-debugging to work (you still have to patch SMTPDirect.py) "
>
> I went in and renamed smtplib.py to smtplib.py.1
> put the new file in and deleted smtplib.pyc ad smtplib.pyo
> Then renamed /usr/lib/mailman/Mailman/Logging/Utils.py to Utils.py.1
> (make sure its this one...there is at least 5 files called Utils.py)
> put the new file in and deleted Utils.pyc and Utils.pyo
>
> then
> /etc/init.d/mailman restart
> tail -f /var/log/mailman/error
>
> while i was watching this i sent an emial to my testing group, etc.
>
> Long story short. I replaced these files, removed pyc and pyo and
> suddenly everything works like magic again. No more timeouts.
> I'll try to get originals back in place and see how that works. I'll
> keep you posted.
>

I put the original smtplib.py file back in /varlib/python.3/smtplib.py
and i get the same problem again.

Nov 08 16:41:31 2006 (13973) Low level smtp error: [Errno 9] Bad file
descriptor, msgid:
<[EMAIL PROTECTED]>
Nov 08 16:46:31 2006 (13973) delivery to [EMAIL PROTECTED] failed with
code -1: [Errno 9] Bad file descriptor
Nov 08 16:46:31 2006 (13973) Low level smtp error: [Errno 9] Bad file
descriptor, msgid: <[EMAIL PROTECTED]>
Nov 08 16:46:31 2006 (13973) delivery to [EMAIL PROTECTED] failed with
code -1: [Errno 9] Bad file descriptor

So i guess i will stick with the file i got from debian bug

> You can get the files from
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395493

Lukasz

>
>
> > And, why they stop is what we're trying to figure out, and I can't tell
> > you any more than I already have without additional information.
> >
> > --
> > Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
> > San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> >
>

-- 
Universal Information Crawler
http://uicrawler.sourceforge.net/
--
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] bcc problem

[o omida parasita]

When using an email list if you send a message to the list but also do
a bcc /cc the message gets sent to moderator.

So for example we have a private list for internal use:

[EMAIL PROTECTED]

If I (a member of the list) send a message to [EMAIL PROTECTED] and I
bcc [EMAIL PROTECTED], the message gets sent to the moderator for
approval. I would get a message saying that the message is being held until
the list moderator can review it for approval.

The reason it is being held:

Message has implicit destination


Is there a way to disable this feature/problem?
--
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] error: namazu - can't open the index

[Rusty Wilson]

Solution.

OK - i was being dense. I checked all the permissions *except* those on the 
top-level user directory. Once I made it readable, the cgi could get to the 
index files.

--Rusty

- Original Message 
From: Rusty Wilson <[EMAIL PROTECTED]>
To: mailman-users@python.org
Sent: Wednesday, November 8, 2006 12:19:35 PM
Subject: [Mailman-Users] error: namazu - can't open the index

Hello,

I'm relatively new to Linux, and Mailman and never used namazu before - please 
accept my apolgies for any ignorance... :)

PROBLEM: namazu error - can't open the index

I set up namazu following the instructions in this post:

mail.python.org/pipermail/mailman-users/2004_june/037580.html

but when i try to invoke the search from my archive page, i get the following 
error:


 Results:
References:  [  (can't open the index)  ]   
 No document matching your query.


I googled for some suggestions and came up with running the program from the 
command line - which works OK:

namazu foo /home/namazu/test1

so - i assume I have a permissions problem - am I on the right track?

This error seems to indicate that the CGI ran, but had error(s). Is this 
correct?

My .namazurc file is "stock" except I uncommented and changed 2 lines:
Index/home/namazu
Template/home/namazu/test1

The owner and group for namazu.cgi and .namazurc are mailman/mailman, and the 
permissions are: 755 for each.

the owner and group for /home/namazu/test1 are namazu/namazu and the permission 
on the directory is 775

Any suggestions on how to proceed would be appreciated. I chose this method 
since the author indicated no changes were required to mailman - and right now, 
thats important.

--Rusty




--
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] debian/exim4/mailman

[Eric Walker]

JB/Mark,
Well I sent in an email to godaddy. I asked them about the 533 error that 
stated host was not a valid host in the rcpt list. They said that error would 
show up when using a email client and I didn't have the button down that says 
outgoing smtp server needs authentication. So, I am assuming this means that my 
exim4 is not authenticating. How can I test to see if exim4 is sending out the 
correct info to authenticate. I do have the paswd and username in my 
passwd.client file.

Eric ...

"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: Actually Mark, I was going to 
reply to Eric direct BUT:

<
godaddy as its outgoing SMTP server.>>

his WAY easier and more affordable solution would be to change Server Company 
to www.bluehost.com !!

I did and I cannot express how much GREATER a "deal" much less how much BETTER 
any assistance required is!!!

I was on godaddy and IRATE.  In doing some searching and with a comment from a 
fried found bluehost.  PRIOR to doing anything wrote their Tech Section witha 
question.  Answer in TWO hours!!!  Replied w/another ? !  Reply in less than an 
hour!!  Replied to #2 w/1 more ?  TEN MINUTES!!!  Now mind you, I had NOT done 
the change nor signed up for anything!!!  They were making NO money by 
answering me!!!

Outside of this mailman list, I have NOT encountered and service like it in 
close to two decades!!!

AMAZING!!!

The owner Matt Heaton / President Bluehost.com even has his own blog to keep 
his customers' up to date!?!?

Ed

Very Happy Bluehost Customer Ed
--
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/sli1que%40yahoo.com

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


 
-
Sponsored Link

Try Netflix today! With plans starting at only $5.99 a month what are you 
waiting for?
--
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] error: namazu - can't open the index

[Rusty Wilson]

Hello,



I'm relatively new to Linux, and Mailman and never used namazu before - please 
accept my apolgies for any ignorance... :)



PROBLEM: namazu error - can't open the index



I set up namazu following the instructions in this post:

mail.python.org/pipermail/mailman-users/2004_june/037580.html


but when i try to invoke the search from my archive page, i get the following 
error:


 Results:

References:  [  (can't open the index)  ]   

 No document matching your query.

 


I googled for some suggestions and came up with running the program from the 
command line - which works OK:


namazu foo /home/namazu/test1



so - i assume I have a permissions problem - am I on the right track?


This error seems to indicate that the CGI ran, but had error(s). Is this 
correct?

My .namazurc file is "stock" except I uncommented and changed 2 lines:
Index/home/namazu
Template/home/namazu/test1

The owner and group for namazu.cgi and .namazurc are mailman/mailman, and the 
permissions are: 755 for each.

the owner and group for /home/namazu/test1 are namazu/namazu and the permission 
on the directory is 775

Any suggestions on how to proceed would be appreciated. I chose this method 
since the author indicated no changes were required to mailman - and right now, 
thats important.

--Rusty


--
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] Some of my Mailman mailing lists don't work butsome do.

[Mark Sapiro]

J.R. Constance wrote:

>I recently transfered hosting from one service to another. I have  
>hosted accounts that use mailman mailing lists. On one account  
>(domain) all of the mailing lists seem to be functional. On the other  
>at least one of the lists is not working. I can log in to the admin  
>section and from that side everything looks normal. I can send  
>invitations or subscribe members, and it tells me "Invitation sent  
>successfully" or "Subscription successful" but no invitation or  
>welcome emails are received.
>
>I have successfully created a new list on this account and it works  
>fine.


Do you have access to the actual Mailman installation and log files? If
not, this is probably something your hosting provider needs to address.

-- 
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] Some of my Mailman mailing lists don't work but some do.

[J.R. Constance]

I recently transfered hosting from one service to another. I have  
hosted accounts that use mailman mailing lists. On one account  
(domain) all of the mailing lists seem to be functional. On the other  
at least one of the lists is not working. I can log in to the admin  
section and from that side everything looks normal. I can send  
invitations or subscribe members, and it tells me "Invitation sent  
successfully" or "Subscription successful" but no invitation or  
welcome emails are received.

I have successfully created a new list on this account and it works  
fine.

Any ideas what might be the problem, and what I can do to fix, short  
of recreating the mailing list(s) that are not working?

Thanks,

J.R. Constance

--
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] Hit a but & use of VERP

[Mark Sapiro]

Henrik Rasmussen wrote:
> 
>Problem 2) When calling
>[mailmanserver]/mailman/options/nyhedsbrev/[EMAIL PROTECTED]
>  and
>other addresses, I get the message
> 
>We're sorry, we hit a bug!
> 
>This is described a lot of places, but not exactly my problem (maybe I
>just didn't find it yet).
> 
>The error log shows:
>admin(1354): [- Traceback --]
>admin(1354): Traceback (most recent call last):
>admin(1354):   File "/usr/lib/mailman/scripts/driver", line 101, in
>run_main
>admin(1354): main()
>admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line 239,
>in main
>admin(1354): loginpage(mlist, doc, user, language)
>admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line 813,
>in loginpage
>admin(1354): table.AddRow([_("""In order to change your membership
>option, you must
>admin(1354):   File "/usr/lib/mailman/Mailman/i18n.py", line 89, in _
>admin(1354): return tns % dict
>admin(1354): ValueError: unsupported format character 'p' (0x70) at
>index 105

The code at line 813 in options.py in the 2.1.5 base is (with some
lisnes wrapped)

table.AddRow([_("""In order to change your membership option, you
must
first log in by giving your %(extra)smembership password in the
section
below.  If you don't remember your membership password, you can
have it
emailed to you by clicking on the button below.  If you just want to
unsubscribe from this list, click on the Unsubscribe
button and a
confirmation message will be sent to you.

Important: From this point on, you
must have
cookies enabled in your browser, otherwise none of your changes
will take
effect.
""")])

It appears that this has been edited in the area of
"%(extra)smembership password" creating something like %(..)p

The "%(extra)s" is a substitution that receives either "email address
and " or nothing depending on context. It can be deleted, but it can't
be changed.

-- 
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] Hit a but & use of VERP

[Mark Sapiro]

Larry Stone wrote:

>On Wed, 8 Nov 2006, Henrik Rasmussen wrote:
>
>> I am new to Mailman. I currently have two problems.
>>
>> I am using Mailman version 2.1.5 with Postfix. I am able to send mails
>> to the list and the mails are sent to the subscribers. According to the
>> mail headers in the mails received from Mailman, Mailman actually uses
>> Postfix.
>>
>> Problem 1) I would like to use VERP. I have read a number of
>> documents[1] describing how to set this up, but so far Mailman is still
>> not using VERP, that is, the mails I receive from the list does not seem
>> to contain any VERPed headers.
>>
>> [1]http://www.exim.org/howto/mailman21.html
>> http://www.postfix.org/VERP_README.html
>>
>> Etc. Some describes to set VERP_CONFIRMATIONS = 1 (etc.) and other
>> documents explains to set VERP_CONFIRMATIONS = Yes ,but I have tried
>> both in ~mailman/Mailman/mm_cfg.py, without luck. I have also tried to
>> set it directly in Default.py (shame on me) but also no luck.
>
>I'm not an "expert" but I believe VERP_CONFIRMATIONS only controls
>confirmation messages like the parameter name implies.


Actually, in 2.1.5 VERP_CONFIRMATIONS only affects mass subscribe
invitations by putting the confirm token in the reply address and
creating a friendlier Subject:.


>Controlling VERPing
>of list messages is done by 1) turning on Personalization (non-digest
>options in the interface; not sure how it's done for digests) which firt
>requires OWNERS_CAN_ENABLE_PERSONALIZATION to be set in mm_cfg.py and 2)
>setting the variables VERP_PERSONALIZED_DELIVERIES and
>VERP_DELIVERY_INTERVAL in mm_cfg.py.



You don't need to personalize the list in order to use VERP. Set

VERP_DELIVERY_INTERVAL = 1

to VERP all regular deliveries, personalized or not.

Read the VERP section in Defaults.py for more information.

-- 
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] Hit a but & use of VERP

[Larry Stone]

On Wed, 8 Nov 2006, Henrik Rasmussen wrote:

> I am new to Mailman. I currently have two problems.
>
> I am using Mailman version 2.1.5 with Postfix. I am able to send mails
> to the list and the mails are sent to the subscribers. According to the
> mail headers in the mails received from Mailman, Mailman actually uses
> Postfix.
>
> Problem 1) I would like to use VERP. I have read a number of
> documents[1] describing how to set this up, but so far Mailman is still
> not using VERP, that is, the mails I receive from the list does not seem
> to contain any VERPed headers.
>
> [1]http://www.exim.org/howto/mailman21.html
> http://www.postfix.org/VERP_README.html
>
> Etc. Some describes to set VERP_CONFIRMATIONS = 1 (etc.) and other
> documents explains to set VERP_CONFIRMATIONS = Yes ,but I have tried
> both in ~mailman/Mailman/mm_cfg.py, without luck. I have also tried to
> set it directly in Default.py (shame on me) but also no luck.

I'm not an "expert" but I believe VERP_CONFIRMATIONS only controls
confirmation messages like the parameter name implies. Controlling VERPing
of list messages is done by 1) turning on Personalization (non-digest
options in the interface; not sure how it's done for digests) which firt
requires OWNERS_CAN_ENABLE_PERSONALIZATION to be set in mm_cfg.py and 2)
setting the variables VERP_PERSONALIZED_DELIVERIES and
VERP_DELIVERY_INTERVAL in mm_cfg.py.

> In postfix, I have tried to follow
> /usr/share/doc/postfix-2.2.10/README_FILES/VERP_READM ,but I am not sure
> where exactly to set up sendmail -V. I suppose it is mailman I should
> set up to use sendmail -V, but I am not sure where. I figured it would
> be in mm_cfg.py where I set SENDMAIL_CMD = '/usr/sbin/sendmail -V', but
> this didn't do any difference. The default (in Defaults.py) is
> SENDMAIL_CMD = '/usr/lib/sendmail' and I have tried this one with
> SENDMAIL_CMD = '/usr/lib/sendmail -V' also. Still no luck.

I do VERP with Postfix and there was no need for me to change SENDMAIL_CMD
to make it work.

> I recall something about that VERP should have been set up at
> installation, but isn't there any way to do it afterwards?

No. I added VERP much later.

-- Larry Stone
   [EMAIL PROTECTED]
--
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] Hit a but & use of VERP

[Henrik Rasmussen]

I am new to Mailman. I currently have two problems.
 
I am using Mailman version 2.1.5 with Postfix. I am able to send mails
to the list and the mails are sent to the subscribers. According to the
mail headers in the mails received from Mailman, Mailman actually uses
Postfix.
 
Problem 1) I would like to use VERP. I have read a number of
documents[1] describing how to set this up, but so far Mailman is still
not using VERP, that is, the mails I receive from the list does not seem
to contain any VERPed headers.
 
[1]http://www.exim.org/howto/mailman21.html
http://www.postfix.org/VERP_README.html
 
http://mail.python.org/pipermail/mailman-users/2004-April/036006.html
http://www.python.org/cgi-bin/faqw-mm.py?req=all
/usr/share/doc/postfix-2.2.10/README_FILES/VERP_READM

Etc. Some describes to set VERP_CONFIRMATIONS = 1 (etc.) and other
documents explains to set VERP_CONFIRMATIONS = Yes ,but I have tried
both in ~mailman/Mailman/mm_cfg.py, without luck. I have also tried to
set it directly in Default.py (shame on me) but also no luck.
 
In postfix, I have tried to follow
/usr/share/doc/postfix-2.2.10/README_FILES/VERP_READM ,but I am not sure
where exactly to set up sendmail -V. I suppose it is mailman I should
set up to use sendmail -V, but I am not sure where. I figured it would
be in mm_cfg.py where I set SENDMAIL_CMD = '/usr/sbin/sendmail -V', but
this didn't do any difference. The default (in Defaults.py) is
SENDMAIL_CMD = '/usr/lib/sendmail' and I have tried this one with
SENDMAIL_CMD = '/usr/lib/sendmail -V' also. Still no luck.
 
I recall something about that VERP should have been set up at
installation, but isn't there any way to do it afterwards?
 
 
Problem 2) When calling
[mailmanserver]/mailman/options/nyhedsbrev/[EMAIL PROTECTED]
  and
other addresses, I get the message
 
We're sorry, we hit a bug!
 
This is described a lot of places, but not exactly my problem (maybe I
just didn't find it yet).
 
The error log shows:
admin(1354): [- Traceback --]
admin(1354): Traceback (most recent call last):
admin(1354):   File "/usr/lib/mailman/scripts/driver", line 101, in
run_main
admin(1354): main()
admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line 239,
in main
admin(1354): loginpage(mlist, doc, user, language)
admin(1354):   File "/usr/lib/mailman/Mailman/Cgi/options.py", line 813,
in loginpage
admin(1354): table.AddRow([_("""In order to change your membership
option, you must
admin(1354):   File "/usr/lib/mailman/Mailman/i18n.py", line 89, in _
admin(1354): return tns % dict
admin(1354): ValueError: unsupported format character 'p' (0x70) at
index 105
admin(1354): [- Python Information -]
admin(1354): sys.version =   2.3.4 (#1, Feb  6 2006, 10:38:46)
[GCC 3.4.5 20051201 (Red Hat 3.4.5-2)]
admin(1354): sys.executable  =   /usr/bin/python
admin(1354): sys.prefix  =   /usr
admin(1354): sys.exec_prefix =   /usr
admin(1354): sys.path=   /usr
admin(1354): sys.platform=   linux2

What do I do wrong?
 
Henrik
--
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] how to enable TRACEBACK for mailman "bug" errors?

[stephen]

will trillich writes:

 > indeed it was -- permissions/ownership on the log files themselves
 > were making apache very unhappy. not sure if this was upstream or
 > debian-specific, but all is harmonious in mailman-land again.

I suspect this is Debian-specific.  Debian has a generic "list" user
and a generic "list" group, rather than Mailman, Majordomo, etc
users/groups.  They also seem to leave the tree owned by root rather
than list (which is what is recommended by Mailman), and maybe forget
a few chmod g+s's on the directories.

I don't use Debian's package myself but ran into this on another
system.  I had assumed that since check_perms was quite unhappy that
the other admin had installed halfway from source, but I've just run a
quick dpkg -L mailman informs me that that indeed was a debian
install.  I'll have to check their bug db later.



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