At 8:47 PM +0100 3/27/07, Jock Coats wrote:
> Okay - I've done that. In fact I also installed Python 2.5 from
> source rather than relying on Sarge's 2.4 port just in case it was that.
No, you really want Python 2.4.4, not 2.3.anything or 2.5.anything.
The problem is that 2.3.anything is to o
On 27 Mar 2007, at 20:47, Jock Coats wrote:
> I guess I could maybe change the
> outbound mailhost somewhere in Mailman's config could I to see if
> that gets round it for now?
Setting SMTPHOST = 'FQDN' (even though it is actually localhost) does
appear to have worked. Until I have more leisu
On 27 Mar 2007, at 16:45, Mark Sapiro wrote:
> I'd go back to 2.1.9 because you have the same problem with the Debian
> package.
Okay - I've done that. In fact I also installed Python 2.5 from
source rather than relying on Sarge's 2.4 port just in case it was that.
I appear to have similar pr
Jock Coats wrote:
>
>I've been using Mailman 2.1.6 for some time now that I happily
>compiled and installed from source on my own server. Now I've needed
>to move to another server and at first I took the opportunity to
>upgrade to 2.1.9. But the OutgoingRunner NEVER worked - logging is
>
Hi all, hope someone can help...
I've been using Mailman 2.1.6 for some time now that I happily
compiled and installed from source on my own server. Now I've needed
to move to another server and at first I took the opportunity to
upgrade to 2.1.9. But the OutgoingRunner NEVER worked - logg
