On 20/04/2010 18:14, Mark Sapiro wrote:
That is the normal way of dealing with messages containing From_ in the
message body. It's not just Mailman or pipermail, and it's problematic
to unescape them for display, because while the escaping is normal,
there is no standard for
Based on the comments received here, I have gone back and had another look
at this, and discovered I was wrong on a number of important issues.
Apologies for this, but I am (obviously) new to Mailman, and didn't
completely realise what I was seeing, the first time.
This time, having looked at the
Chris Malme wrote:
However, the Pipermail Archive does consistently split messages whenever a
message-body \nFrom occurs, as I described earlier, with the second part
being attributed to bo...@does.not.exist.com.
[...]
So it looks like my problem is with the dynamic creation of the Pipermail
What a star!
Thanks Mark, I will take a look at it later today.
Yes, it is Debian/Ubuntu - I must learn to specify this things from the start.
Chris
--
Mailman-Users mailing list Mailman-Users@python.org
Mark Sapiro wrote:
That said, I suspect the underlying OS here is Debian/Ubuntu and
Mailman is the Debian/Ubuntu package which has patches in this area
which are causing this.
As I have written on this forum before, the Debian/Ubuntu package
for Mailman has a large number of patches. One I
Hi all,
Newbie here.
I have recently moved a list over to Mailman running under Plesk on a VPS.
The version of Mailman that I currently have access to is 2.1.9.
I had a mbox file to import from my old mail-list system. Originally, I had
some problems - the mbox file was large (7 years of
Further to my earlier post.
Note that this is not just the archive - this actually affects messages
being sent to the subscribers - i.e. a message containing a newline followed
by From will be split in two before going out.
Further testing shows that this is incorrect. The problem affects
There's a program in bin called cleanarch that can be run on your
archive to fix this problem. It cleans up the offending From lines from
older mbox files so that you can run arch again and generate correct
html versions of the archives.
Terri
Chris Malme wrote:
Further to my earlier
Chris Malme wrote:
Further testing shows that this is incorrect. The problem affects only the
archive, not the mail-list messages going to the subscribers.
However, the archive problem is repeatable. Any instance in the message text
of From following a single newline is interpreted as a new
Terri Oda wrote:
There's a program in bin called cleanarch that can be run on your
archive to fix this problem. It cleans up the offending From lines from
older mbox files so that you can run arch again and generate correct
html versions of the archives.
Terri is correct. cleanarch will
Chris Malme wrote:
That is correct, I did it manually (or rather, with a quick script I wrote),
preceding each message text line that begins with a From with a . This
enabled the mbox to be imported into the Mailman Archive without splitting
messages as it did when I first tried it. However,
11 matches
Mail list logo
