George Sexton wrote:
>
>I went ahead and installed 2.1.9 and it seemed to resolve the issue. I'm
>guessing the problem was RFC-2231 file names that spanned multiple
>lines. The outbound message had REALLY long file names.
>
>Once I installed 2.1.9, the person was able to send the message.
Yes,
Tokio Kikuchi wrote:
>
>George Sexton wrote:
>
>>
>> When the IncomingRunner dies, the new message appears in the qfiles/in
>> folder with an extension of .bak. I've tried deleting and re-creating
>> the list and it still dies. If I remove the .bak message and re-start
>> Mailman, then any queu
You are correct. This was SuSE Linux 10.1, which appears to be 2.1.7
with a lot of patches.
I went ahead and installed 2.1.9 and it seemed to resolve the issue. I'm
guessing the problem was RFC-2231 file names that spanned multiple
lines. The outbound message had REALLY long file names.
Once I
Hi,
George Sexton wrote:
>
> When the IncomingRunner dies, the new message appears in the qfiles/in
> folder with an extension of .bak. I've tried deleting and re-creating
> the list and it still dies. If I remove the .bak message and re-start
> Mailman, then any queued messages are sent or d
I've got a situation with a list that is causing problems. I'm sorry
this is so long, but here's the things I've done. I've searched the
archives and I don't seem to see anything that applies.
I'm using Mailman 2.1.7 and I have a list that I can post to. Another
person cannot post to this list.
