Jesper Dybdal wrote:
>
>The only strange thing I now notice is that even if the digest consists
>of messages that were all originally in iso-8859-1 encoding, the digest
>is in usascii, with question marks substituted for non-usascii
>characters. Is it necessary to use MIME digests in order to get
On Sun, 4 Jan 2009 08:43:31 -0800, Mark Sapiro wrote:
>It is still not clear to me if this will also fix the
>
>>List: jdtest: problem processing /home/mailman/lists/jdtest/digest.mbox:
>>iso-8859-15
>
>issue. It may or may not. You can try running
>
> cron/senddigests -l jdtest
>
>manually as th
Jesper Dybdal wrote:
>
>Problem found and solved:
Good!
It is still not clear to me if this will also fix the
>List: jdtest: problem processing /home/mailman/lists/jdtest/digest.mbox:
>iso-8859-15
issue. It may or may not. You can try running
cron/senddigests -l jdtest
manually as the mailm
On Sat, 3 Jan 2009 16:48:40 -0800, Mark Sapiro wrote:
>Try to cd to the misc/ subdirectory of the directory that you unpacked
>and configured in and run
>
>make install-packages
Problem found and solved: I had run "make" as root, but "make install"
as "mailman", and "make install-packages", whic
Jesper Dybdal wrote:
>
>I think you've diagnosed the problem. There is a pythonlib directory,
>but it is empty.
Note that the Debian/Ubuntu Mailman package deletes mailman/pythonlib/
Mark Sapiro replied to a posting Wed, 10 Jan 2007 09:48:30 -0800:
>Some additional information:
>
>This is mailm
Jesper Dybdal wrote:
>
>I think you've diagnosed the problem. There is a pythonlib directory,
>but it is empty.
>
>I built Mailman as user "root" (knowing perfectly well that this is not
>the thing to do unless you choose to trust your software providers), but
>I ran "make install" as user "mailma
On Sat, 3 Jan 2009 10:19:17 -0800, Mark Sapiro wrote:
>I'm not sure about the digests problem. You could try 'bin/withlist -i'
>and then at the >>> prompt type
>
>unicode('abcde', 'iso-8859-15')
>
>if this prints
>
>u'abcde'
>
>Mailman is able to access the iso-8859-15 codecs and there should be
Jesper Dybdal wrote:
>
>On Sat, 3 Jan 2009 08:51:10 -0800, Mark Sapiro wrote:
>
>>Mailman 2.1.11 is not compatible with Python 2.6. Most of the errors
>>are deprecation warnings similar to those above and also involving
>>hashlib. You'll probably find lots more in Mailman's error log.
>
>Now I'm c
On Sat, 03 Jan 2009 00:51:33 +0100, I wrote:
>I currently have to digest subscribers, so I don't know if this a real
>problem.
That should have been "*no* digest subscribers" - sorry.
On Sat, 3 Jan 2009 08:51:10 -0800, Mark Sapiro wrote:
>Mailman 2.1.11 is not compatible with Python 2.6. Most
Jesper Dybdal wrote:
>I've just installed Mailman version 2.1.11.
>
>In general, it works fine.
Given the below, I'm surprised.
>Whenever my mailman cron job runs senddigests, I get the following
>warnings (on stdout or stderr, mailed to me by cron):
>
>>/home/mailman/Mailman/Handlers/Scrubber
I've just installed Mailman version 2.1.11.
In general, it works fine.
Whenever my mailman cron job runs senddigests, I get the following
warnings (on stdout or stderr, mailed to me by cron):
>/home/mailman/Mailman/Handlers/Scrubber.py:192: DeprecationWarning: get_type()
>deprecated; use get_co
11 matches
Mail list logo
