From: wmperry@aventail.com (William M. Perry)
Cc: "(ding)" <ding@gnus.org>
Subject: Re: pop3.el: Content-Length generation (was: bad (i.e. serious) mail problems
Date: 06 Apr 1999 13:59:02 -0500 [thread overview]
Message-ID: <86r9pxmv7t.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "Tue, 6 Apr 1999 14:37:13 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> Here is a patch against pop3 1.3q to bring it to 1.3r. It should
> generate a Content-Length header with the same value as the Lines header
> Gnus creates (which is converted to X-Content-Length by Gnus somewhere
> along the line). This should hopefully prevent unescaped envelopes from
> being a problem.
>
> Note: it uses `count-lines-buffer' from simple.el, which might not be
> part of FSF Emacs (it is part of XEmacs). If this is the case, does FSF
> Emacs have a more or less equivalently useful function, or am I going to
> have to roll my own?
Ummmm... content-length is supposed to be the byte count, is it not?
-Bill P.
next prev parent reply other threads:[~1999-04-06 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-06 18:37 Stainless Steel Rat
1999-04-06 18:59 ` William M. Perry [this message]
1999-04-06 19:29 ` Stainless Steel Rat
1999-04-06 19:35 ` Stainless Steel Rat
1999-04-06 19:10 ` paul stevenson
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=86r9pxmv7t.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.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).