From: Simon Josefsson <jas@extundo.com>
Cc: "(ding)" <ding@gnus.org>
Subject: Re: Why does Gnus generates Lines: header in mail?
Date: Mon, 30 Sep 2002 13:23:58 +0200 [thread overview]
Message-ID: <ilu7kh390vl.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3ofage003.fsf@peorth.gweep.net> (Stainless Steel Rat's message of "29 Sep 2002 21:31:40 -0400")
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Simon Josefsson <jas@extundo.com> on Sun, 29 Sep 2002
> | X-* is blessed by the standard to contain experimental stuff, so I don't
> | see a problem there. Mail-Copies-To has value and even interoperates
> | fairly well. If Lines: has value, I won't continue argue it should be
> | removed, but I haven't understood where that value is.
>
> The purpose of Lines is quite simple: it gives a ballpark estimate as to
> the size of a message, thus allowing the client the ability not to download
> messages that exceed a particular size.
But it can't be used reliably since very few MUAs generate it.
> For example, POP does not have a mechanism by which it can determine the
> size of messages.
POP3 has.
> But it can get all the headers. A POP client can grab the headers
> of all messages, check the Lines headers for each, and skip any
> messages that exceed a user-defined threshold. This is useful, for
> example, if you happen to be a travelling sales engineer currently
> somewhere in India using a cellular/gsm phone at 9600 baud to
> download your mail but don't want the 150MB PowerPoint presentations
> that your manager sent out to everyone, at least not until you get
> back to your office and a T1. I am not making this up. I have an
> SE who routinely does this.
Is the manager who send 150MB powerpoint presentations using Gnus? I
strongly doubt Outlook sends a Lines: header in mail.
> On the Usenet side of things, Gnus Agent uses Lines headers the same way,
> to determine if a message qualifies as "long" and does not automatically
> retrieve articles that exceed the "long" threshold.
No, the agent is using NOV information.
next prev parent reply other threads:[~2002-09-30 11:23 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 14:01 Simon Josefsson
2002-09-29 14:14 ` Karl Kleinpaste
2002-09-29 14:32 ` Simon Josefsson
2002-09-29 17:08 ` Karl Kleinpaste
2002-09-29 17:51 ` Simon Josefsson
2002-09-30 1:31 ` Stainless Steel Rat
2002-09-30 1:57 ` Russ Allbery
2002-09-30 19:15 ` Stainless Steel Rat
2002-10-01 2:11 ` Russ Allbery
2002-10-01 3:27 ` Stainless Steel Rat
2002-10-01 3:38 ` Simon Josefsson
2002-10-01 3:57 ` Russ Allbery
2002-09-30 3:08 ` greg andruk
2002-09-30 19:17 ` Stainless Steel Rat
2002-09-30 11:23 ` Simon Josefsson [this message]
2002-10-07 21:58 ` Florian Weimer
2002-10-07 23:20 ` Simon Josefsson
2002-10-09 14:04 ` Per Abrahamsen
2002-10-02 16:46 ` Per Abrahamsen
2002-09-29 18:35 ` Russ Allbery
2002-09-29 18:51 ` Michael Cook
2002-09-29 19:45 ` Russ Allbery
2002-09-29 15:14 ` Kai Großjohann
2002-09-29 16:59 ` Simon Josefsson
2002-09-29 20:15 ` Kai Großjohann
2002-09-29 20:21 ` Jorgen Schaefer
2002-09-29 20:30 ` Simon Josefsson
2002-09-29 21:43 ` Jorgen Schaefer
2002-09-30 12:03 ` Clemens Fischer
2002-09-30 14:19 ` Kai Großjohann
2002-09-30 14:43 ` Simon Josefsson
2002-09-30 22:04 ` Clemens Fischer
2002-10-01 0:22 ` Josh Huber
2002-10-01 9:54 ` Clemens Fischer
2002-10-01 10:45 ` Kai Großjohann
2002-10-02 16:52 ` Paul Jarc
2002-10-01 14:05 ` Josh Huber
2002-10-01 18:12 ` Clemens Fischer
2002-10-02 18:38 ` Paul Jarc
2002-10-03 0:06 ` mail-followup-to, was " Clemens Fischer
2002-10-03 16:13 ` Paul Jarc
2002-10-02 16:49 ` Paul Jarc
2002-10-02 19:44 ` [despammed] " clemens fischer
2002-10-02 20:25 ` Paul Jarc
2002-10-02 23:16 ` Clemens Fischer
2002-10-03 16:30 ` Paul Jarc
2002-10-06 13:30 ` Clemens Fischer
2002-10-07 16:34 ` Paul Jarc
2002-10-07 23:44 ` Clemens Fischer
2002-10-08 15:34 ` Paul Jarc
2002-10-02 18:48 ` Reiner Steib
2002-10-03 0:13 ` Clemens Fischer
2002-10-08 12:07 ` Reiner Steib
2002-10-01 11:06 ` Kai Großjohann
2002-10-01 11:54 ` Kai Großjohann
2002-10-02 4:41 ` Dan Christensen
2002-12-29 15:59 ` Lars Magne Ingebrigtsen
2002-12-30 16:36 ` Romain FRANCOISE
2002-12-30 16:50 ` Lars Magne Ingebrigtsen
2002-12-30 22:06 ` Romain FRANCOISE
2002-12-30 20:46 ` No References header when using drafts (was: Why does Gnus generates Lines: header in mail?) Reiner Steib
2002-12-30 21:06 ` No References header when using drafts Lars Magne Ingebrigtsen
2002-12-30 21:59 ` Reiner Steib
2002-12-30 22:23 ` Lars Magne Ingebrigtsen
2002-12-31 14:43 ` Reiner Steib
2003-01-01 17:57 ` Lars Magne Ingebrigtsen
2003-01-01 18:49 ` Lars Magne Ingebrigtsen
2002-12-31 15:23 ` Kai Großjohann
2003-01-02 17:05 ` Simon Josefsson
2003-01-02 18:30 ` Lars Magne Ingebrigtsen
2003-01-02 20:53 ` Simon Josefsson
2003-01-02 21:04 ` Lars Magne Ingebrigtsen
2003-01-03 17:48 ` Kai Großjohann
2003-01-02 21:30 ` Kai Großjohann
2003-01-06 19:27 ` References Header (Re: Why does Gnus generates Lines: header in mail?) Mark Thomas
2003-01-07 4:56 ` Lars Magne Ingebrigtsen
2003-01-07 13:11 ` Mark Thomas
2003-01-07 18:12 ` Kai Großjohann
2003-01-08 4:10 ` Lars Magne Ingebrigtsen
2003-01-07 12:49 ` References Header Reiner Steib
2003-01-08 3:55 ` Lars Magne Ingebrigtsen
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=ilu7kh390vl.fsf@latte.josefsson.org \
--to=jas@extundo.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).