By the way, the mail client in question is Apple Mail 2.1, and I have
confirmed that this is normal behaviour for it.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http:/
Regarding my earlier query, regarding archive messages breaking, due to to
in message "\nFrom " text; I am pleased to say that Mark's suggestion worked
a treat, and fixed that archive woe. Many thanks.
However, it uncovered another problem, less serious, but fascinating. One of
my users uses a mai
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
http://mail.python.org/mailman/listinfo
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
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 escaping/unesc
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 affect
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 archive
