From: Janne Rinta-Manty <jrm@iki.fi>
Subject: Re: B c with nnimap: extra newlines
Date: Thu, 13 Jan 2000 14:13:57 GMT [thread overview]
Message-ID: <xknogaqys7z.fsf@tahkokari.cs.Helsinki.FI> (raw)
In-Reply-To: <xknwvqgb9rm.fsf@tahkokari.cs.Helsinki.FI>
Janne Rinta-Manty 1999-12-17T10:10:27Z:
JRM> I have a problem with nnimap: moving articles (B m) to other
JRM> nnimap folders works fine, but copying (B c) doubles every
JRM> newline in the article, including headers.
I seem to have solved the problem now by commenting out the following
lines from nnimap-request-accept-article:
;; turn into rfc822 format (\r\n eol's)
; (with-current-buffer (current-buffer)
; (goto-char (point-min))
; (while (search-forward "\n" nil t)
; (replace-match "\r\n")))
Assuming the above code works for everybody else, I wonder what's
wrong with my setup. IMAP server? SSH? Or should imap-client-eol be
used instead of "\r\n" (I have set it to "\n")?
--
Janne Rinta-Mänty
next prev parent reply other threads:[~2000-01-13 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 13:42 Janne Rinta-Manty
2000-01-13 14:13 ` Janne Rinta-Manty [this message]
2000-01-13 14:39 ` Simon Josefsson
2000-01-14 12:05 ` Janne Rinta-Manty
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=xknogaqys7z.fsf@tahkokari.cs.Helsinki.FI \
--to=jrm@iki.fi \
/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).