I've done a quick scan of wiki.list.org, used grep and locate to try
to find config options, and still cannot determine how to adjust the
word-wrapping behaviour of Mailman.
I often send out long links to unsophisticated audiences, who then
tell me "the link is broken" when Mailman breaks the link in order to
wrap the line to some specific length. I'd rather not go the tinyurl
opaque reference route, since the links I send are meaningfully read
by my few sophisticated users.
Is there a place I can adjust the length to be much longer, or perhaps
to disable word-wrapping altogether?
Thanks!
:::: Jan Steinman, Communication Steward, EcoReality http://www.EcoReality.org
:::: 2152 Fulford-Ganges Road, Salt Spring Island, BC V8K 1Z7, +1
250.653.2024
Jan Steinman wrote:
I often send out long links to unsophisticated audiences, who then
tell me "the link is broken" when Mailman breaks the link in order to
wrap the line to some specific length. I'd rather not go the tinyurl
opaque reference route, since the links I send are meaningfully read
by my few sophisticated users.
You might consider preview.tinyurl.com links.
Is there a place I can adjust the length to be much longer, or perhaps
to disable word-wrapping altogether?
Mailman doesn't do line wrapping. There was an issue pre Mailman 2.1.10 with format=flowed being removed from the Content-Type header, which removes the instruction to the receiving MUA to unwrap the lines that were wrapped by the sending MUA, but this was fixed in Mailman 2.1.10.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 19 Jun 08, at 10:57, Mark Sapiro wrote:
Is there a place I can adjust the length to be much longer, or
perhaps to disable word-wrapping altogether?Mailman doesn't do line wrapping.
Interesting. The only email that I send out that gets wrapped is stuff
that goes through Mailman. I can send the exact same thing to a
postfix alias of exactly the same people, and it doesn't get wrapped.
So it may well be true that "Mailman doesn't do line wrapping," but
from my perspective, it's doing something that *causes* line wrapping
to happen!
In fact, I'd venture to guess that this email, which is sent to the
list and to Mark and I on the Cc: will show up wrapped on the list,
and not wrapped on the Cc's.
Regardless of who's doing it, any better ideas on how to keep it from
happening? Line-wrapping is so "VT-100" '80's. I'm staring at Mark's
email on my 1920-pixel screen, with about 9/10th of the screen showing
blank white.
:::: Jan Steinman, Communication Steward, EcoReality http://www.EcoReality.org
:::: 2152 Fulford-Ganges Road, Salt Spring Island, BC V8K 1Z7, +1
250.653.2024
On 19-Jun-08, at 2:46 PM, Jan Steinman wrote:
So it may well be true that "Mailman doesn't do line wrapping," but
from my perspective, it's doing something that *causes* line
wrapping to happen!
If Mailman is converting html->text, I think it does add line-
wrapping as a side effect of the conversion. I don't know if this is
what you're seeing, though.
Terri
Terri Oda wrote:
If Mailman is converting html->text, I think it does add line-wrapping as a side effect of the conversion. I don't know if this is what you're seeing, though.
But Mailman doesn't do the actual conversion itself. IIRC, it just calls "lynx" to do the line-wrapping. Either that, or the line-wrapping is done in an Python library for handling e-mail, which Mailman makes use of.
Either way, the responsible party here is not Mailman per se.
-- Brad Knowles <brad@python.org> Member of the Python.org Postmaster Team & Co-Moderator of the mailman-users and mailman-developers mailing lists
--On June 19, 2008 11:46:44 AM -0700 Jan Steinman <Jan@Bytesmiths.com> wrote:
In fact, I'd venture to guess that this email, which is sent to the list and to Mark and I on the Cc: will show up wrapped on the list, and not wrapped on the Cc's.
To which I reply:
For what it's worth, it didn't arrive line-wrapped at my end. The wider I made my mail window, the longer the lines got. Well, until I got it about 60% of my 2560-pixel wide screen, and then each of the four paragraphs in your text was on one line, so further widening made no more difference.
-- Steve Burling <mailto:srb@umich.edu> University of Michigan, ICPSR Voice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910
On 19 Jun 08, at 12:02, Steve Burling wrote:
--On June 19, 2008 11:46:44 AM -0700 Jan Steinman
<Jan@Bytesmiths.com> wrote:In fact, I'd venture to guess that this email, which is sent to the
list and to Mark and I on the Cc: will show up wrapped on the list, and
not wrapped on the Cc's.To which I reply:
For what it's worth, it didn't arrive line-wrapped at my end. The
wider I made my mail window, the longer the lines got.
Interestinger and interestinger... the text Steve says wasn't line- wrapped became so when quoted, above, but his reply text was not.
:::: Jan Steinman, Communication Steward, EcoReality http://www.EcoReality.org
:::: 2152 Fulford-Ganges Road, Salt Spring Island, BC V8K 1Z7, +1
250.653.2024
Jan Steinman wrote:
On 19 Jun 08, at 12:02, Steve Burling wrote:
For what it's worth, it didn't arrive line-wrapped at my end. The
wider I made my mail window, the longer the lines got.Interestinger and interestinger... the text Steve says wasn't line- wrapped became so when quoted, above, but his reply text was not.
I told you the answer in my initial reply, but to reiterate with more detail, the copy of your reply which I received by direct Cc: has the header:
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
This means that the text may have been (was in this case) wrapped and a trailing <space> added immediately preceding any inserted <CRLF>. See RFC 2646 <http://www.faqs.org/rfcs/rfc2646.html> for details.
Then, your first paragraph was sent as
Interesting. The only email that I send out that gets wrapped is stuff
that goes through Mailman. I can send the exact same thing to a
postfix alias of exactly the same people, and it doesn't get wrapped.
You may not see it, but the first two of the three lines end with two spaces. The format=flowed and delsp=yes parameters tell the receiving MUA that each line that ends in a space should have the space removed and be joined to the following line making
Interesting. The only email that I send out that gets wrapped is stuff that goes through Mailman. I can send the exact same thing to a postfix alias of exactly the same people, and it doesn't get wrapped.
The problem is that prior to Mailman 2.1.10, the format=flowed and delsp=yes parameters were not preserved in the outgoing message, thus the receiving MUA doesn't unwrap the lines per RFC 2646.
So, I suspect you are seeing this issue on a pre-2.1.10 Mailman. Note that the loss of the format=flowed and delsp=yes parameters most likely occurred when msg_header and/or msg_footer was added to the message, and if you set these 'empty', the problem will be avoided.
In fact, I'd venture to guess that this email, which is sent to the list and to Mark and I on the Cc: will show up wrapped on the list, and not wrapped on the Cc's.
So did you receive a copy from this 2.1.10 list? If so, what did it look like?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
Jan Steinman wrote:
Interesting. The only email that I send out that gets wrapped is stuff that goes through Mailman. I can send the exact same thing to a postfix alias of exactly the same people, and it doesn't get wrapped.
and
In fact, I'd venture to guess that this email, which is sent to the list and to Mark and I on the Cc: will show up wrapped on the list, and not wrapped on the Cc's.
For the record, the copy of my previous post to this thread that I received from the list had the above quoted lines not wrapped. I am sending this to the list only (w/o Ccs) so that everyone will receive it from the list and see that the quoted lines above aren't wrapped in this post either (This paragraph is wrapped, because that's the way this MUA works).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
Brad Knowles -
Jan Steinman -
Mark Sapiro -
Steve Burling -
Terri Oda