Barry Finkel wrote:
>Mark Sapiro replied to one of my postings:
>
>>Quoting from section 5.1.1 of RFC 2045
>>
>> The boundary may be followed by zero or more characters of linear
>> whitespace. It is then terminated by either another CRLF and the
>> header fields for the next part, or by two CR
Mark Sapiro replied to one of my postings:
>Mailman (actually the Python email package) doesn,t like the fact that
>there is no intervening empty line between the terminating boundary of
>the message/rfc822 part and the terminating boundary of the outer
>message.
>
>Quoting from section 5.1.1 of R
Barry Finkel wrote:
>
> The directory /var/lib/mailman/qfiles contains files.
> It needs to be empty for the upgrade work properly.
>
>I looked at that directory, and I found a number of
>
> bounces/x.bak
>I looked at the logs and found an unparseable rejection message.
>I am inc
I built an Ubuntu package for the patched Mailman 2.1.9, and when
I tried to install it this morning, there was an error message
stating that
The directory /var/lib/mailman/qfiles contains files.
It needs to be empty for the upgrade work properly.
I looked at that directory, and I foun
