From: Sharon Kimble <boudiccas@skimble.plus.com>
To: ding@gnus.org
Subject: line-wrapping failing?
Date: Sun, 19 Oct 2014 19:41:13 +0100 [thread overview]
Message-ID: <8761ffsy0m.fsf@skimble.plus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
I have the strange condition that when I email yahoo groups my message
that leaves me at line-wrapping at 68, does not line-wrap when it is
received back from the yahoo servers! Indeed, one email that I sent of
about 6 paragraphs, came back as just one block of text which made it
difficult to understand the argument in my email!
How can this situation be resolved please?
AFAIK, it leaves me OK, but the yahoo servers are picking up on the lack
of line-endings or something.
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.94.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next reply other threads:[~2014-10-19 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 18:41 Sharon Kimble [this message]
2014-10-19 21:21 ` Jorge A. Alfaro-Murillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761ffsy0m.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).