ugreport.cgi?bug=384016). I sent your
hint to debian's bug tracker system.
Thanks ;)
hjb :-?
--
Hans-Juergen Beie
[EMAIL PROTECTED]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-u
Hi,
Am Mi, 13.09.2006, 14:45, schrieb Tokio Kikuchi:
>> In short:
>> Replace the first line in /usr/lib/mailman/cron/senddigests
>> # ! /usr/bin/python
>> by
>> #! /usr/bin/python2.3
>> if you have a Python2.3 installed.
>>
>> As this problem appeared here (debian/etch, Mailman 2.1.8-2) after
Am Mi, 13.09.2006, 12:58, schrieb Hans-Juergen Beie:
> Am Do, 7.09.2006, 15:57, schrieb Mário Filipe:
>> Hello
>>
>> I have two problems with digests, and maybe you can help me:
>>
>> - on one mailing list some users complain that they don't get their own
&
File "/var/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: iso-
On Thu, August 18, 2005 2:23, Mark Sapiro said:
> Hans-Juergen Beie wrote:
>>In the first case use
>> add_virtualhost('www.ourdomain.com', 'newdomain.com')
>
> This will not work. add_virtualhost() is defined in Defaults.py and
> what it does
Forrest Aldrich wrote on 17.08.2005 20:45 Uhr:
> Let me clarify my setup.
>
> Our list server is at http://www.ourdomain.com/lists. The default
> domain we want added to new lists is "ourdomain.com". However, we have
> another domain that we want to use for a special list that we need to
> add
nt host/domain names for different lists, and that lists can be
run over different MX hosts, optionally. Additionally, the virtual domain
setup keeps lists in different domains separated from each other (and
that's new as of Mailman 2.1, I think). In other words: If one connects to
http://lis
Forrest Aldrich wrote on 16.08.2005 20:57:
> The Mailman instance I have installed runs under one primary domain -
> however, I want to set up a list that uses a different TLD (routed
> properly at our MX servers).
>
> What's the proper way to get this working under Mailman, where it
> respect
