On Sun, Mar 11, 2001 at 07:37:06PM +, Mark Delany wrote:
[...]
A more sensible strategy might be to introduce a new "info" flag (say
'3' equals POP wire size) on the filename, eg, a 10,000 byte email has
a name something like this:
Maildir/new/980195114.16740.geex:2,RS3,1
From
A more sensible strategy might be to introduce a new "info" flag (say
'3' equals POP wire size) on the filename, eg, a 10,000 byte email has
a name something like this:
Maildir/new/980195114.16740.geex:2,RS3,1
From reading URL:http://cr.yp.to/proto/maildir.html, it is not clear
On Mon, Mar 12, 2001 at 11:03:33AM +, Mark Delany wrote:
To me that implies that a file in new cannot have an "info" section.
You're right. I didn't think the original point throuhgh.
Regards,
Vince.
Peter van Dijk wrote:
Not if it's calculated as the file is written to the Maildir.
True, but that hurts writing performance.
Have you tested this? It doesn't seem that qmail has ever been CPU bound --
and if the CPU has spare cycles while writing, then counting lines and adding
bytes for
On Mon, Mar 12, 2001 at 08:55:47AM -0500, Michael T. Babcock wrote:
Peter van Dijk wrote:
Not if it's calculated as the file is written to the Maildir.
True, but that hurts writing performance.
Have you tested this? It doesn't seem that qmail has ever been CPU bound --
and if the
John R. Levine wrote:
Pop3d just reports the file sizes, while it's clear
from the RFC that it's supposed to report the wire size of each
message,
i.e., the size using cr/lf as a line terminator, so the sizes it
reports
are too small.
Peter van Dijk replied:
Yes. This behaviour is
On Sat, Mar 10, 2001 at 05:47:29PM -0500, Scott Gifford wrote:
Peter van Dijk [EMAIL PROTECTED] writes:
On Sat, Mar 10, 2001 at 01:12:13PM -0500, John R Levine wrote:
The usual mailbox vs. maildir war has flared up on inet-access, and points
out a bug in qmail-pop3d. When you do a
On Sat, Mar 10, 2001 at 01:12:13PM -0500, John R Levine wrote:
The usual mailbox vs. maildir war has flared up on inet-access, and points
out a bug in qmail-pop3d. When you do a LIST command, it gives you the
size of each message. Pop3d just reports the file sizes, while it's clear
from the
Yes. This behaviour is known. Fixing it, however, involves a *huge*
performance downgrade of qmail-pop3d.
Not if it's calculated as the file is written to the Maildir.
'Usually, during the AUTHORIZATION state of the POP3 session, the POP3
server can calculate the size of each message in
On Sun, Mar 11, 2001 at 07:51:47PM +, Mark Delany wrote:
Yes. This behaviour is known. Fixing it, however, involves a *huge*
performance downgrade of qmail-pop3d.
Not if it's calculated as the file is written to the Maildir.
True, but that hurts writing performance.
'Usually,
On Sun, Mar 11, 2001 at 07:37:06PM +, Mark Delany wrote:
[snip]
I use courier-imap, and its POP daemon does get the sizes right,
presumably by reading the files and adding the number of \n characters.
A more sensible strategy might be to introduce a new "info" flag (say
'3' equals POP
Putting the linecount in there makes more sense. Some MUAs might be happy
about that, and it still allows easy calculation of wiresize (add
number of lines to physical size). More info, less bytes :)
Optimally the wire-size is calculated when the mail is written to
Maildir/tmp/ and then
On Sun, Mar 11, 2001 at 06:05:47PM -0500, John R. Levine wrote:
[snip]
Yes. Mind the performance penalty tho.
Not a bad idea. The performance penalty would be tiny, reading buffers
that are about to be written out won't cause an extra page fault.
True.
A possible complication with this
On Sun, Mar 11, 2001 at 06:05:47PM -0500, John R. Levine wrote:
Putting the linecount in there makes more sense. Some MUAs might be happy
about that, and it still allows easy calculation of wiresize (add
number of lines to physical size). More info, less bytes :)
Optimally the wire-size is
The usual mailbox vs. maildir war has flared up on inet-access, and points
out a bug in qmail-pop3d. When you do a LIST command, it gives you the
size of each message. Pop3d just reports the file sizes, while it's clear
from the RFC that it's supposed to report the wire size of each message,
On Sat, Mar 10, 2001 at 01:12:13PM -0500, John R Levine wrote:
The usual mailbox vs. maildir war has flared up on inet-access, and points
out a bug in qmail-pop3d. When you do a LIST command, it gives you the
size of each message. Pop3d just reports the file sizes, while it's clear
from the
On Sat, Mar 10, 2001 at 09:21:46PM +0100, Peter van Dijk wrote:
[snip]
'Usually, during the AUTHORIZATION state of the POP3 session, the POP3
server can calculate the size of each message in octets when it opens
the maildrop. . simply counts each occurance of this character in
a message
Peter van Dijk [EMAIL PROTECTED] writes:
On Sat, Mar 10, 2001 at 01:12:13PM -0500, John R Levine wrote:
The usual mailbox vs. maildir war has flared up on inet-access, and points
out a bug in qmail-pop3d. When you do a LIST command, it gives you the
size of each message. Pop3d just
18 matches
Mail list logo
